From eleonorapiersanti at yahoo.it Sun Feb 1 05:30:00 2015 From: eleonorapiersanti at yahoo.it (Eleonora Piersanti) Date: Sun, 1 Feb 2015 10:30:00 +0000 (UTC) Subject: [Paraview] Gradient of 2D velocity field with paraview In-Reply-To: References: Message-ID: <250108449.382432.1422786600329.JavaMail.yahoo@mail.yahoo.com> Sorry to bother you again. But I need the gradient to make some verifications in my code. Then, the problem of accuracy is quite important. Is there any way to compute the gradient without using the Extract surface filter? Kind regards,Eleonora Il Venerd? 30 Gennaio 2015 11:48, Andy Bauer ha scritto: It looks like the Gradient of Unstructured Data Set filter isn't working properly with quadratic triangles. Try using the Extract Surface filter before computing gradients to convert them into linear triangles. If you want to get more familiar with using ParaView, the ParaView tutorial at http://www.paraview.org/Wiki/The_ParaView_Tutorial is a good place to start. Regards, Andy On Fri, Jan 30, 2015 at 6:25 AM, Eleonora Piersanti wrote: Thank you for the answer.I think that the dimension of the .vtk file was too big. You can download the .vtk file from: https://www.dropbox.com/s/o1wjo2brsaeu5ag/stability_realEigU_up0.vtk.tar.gz?dl=0 In which sense should I use the Slice filter? Sorry but I am quite new with paraview.Kind regards,Eleonora? Il Venerd? 30 Gennaio 2015 11:16, Eleonora Piersanti ha scritto: Thank you, for the answer.I attach the .vtk file. In which sense should I use the Slice filter? Sorry but I am quite new with paraview.Kind regards,Eleonora Il Venerd? 30 Gennaio 2015 10:59, Andy Bauer ha scritto: Your description is a bit vague to diagnose the issue. Can you share your data set? I was able to use the Wavelet source, use the Slice filter and then use the Gradient of Unstructured Data Set without any issues. Can you see if that works for you? Regards, Andy On Fri, Jan 30, 2015 at 5:26 AM, Eleonora Piersanti wrote: Hi to everyone!I computed with finite elements a 2D velocity field. I plotted without any problem the velocity field with paraview. I would like to compute the gradient. I tried Filters->Gradient of Unstructured Data Set but without succes.Can you help me?Thanks, Nora _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 felipe.bordeu at ec-nantes.fr Sun Feb 1 04:32:36 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu Weldt) Date: Sun, 1 Feb 2015 10:32:36 +0100 Subject: [Paraview] Memory use with Xdmf files In-Reply-To: References: Message-ID: hi, I think the best way is to write only one cell (with the correct position in the espace) for each picture and then apply each picture as a texture in each cell. For me this is the way to go. But technically I don?t know how to do it. Felipe Le 30 janv. 2015 ? 17:51, Michael Jackson a ?crit : > I have written an Xdmf file that uses the 3D CoRectMesh to display a montage of 54 gray scale images. They are laid out in a 9x6 fashion. Each Image is about 1292x968 pixels. We have run stitching algorithms on the images to find their correct coordinates in XYZ space so that they will form the montage correctly. > > The raw amount of memory is 67,535,424 bytes. If that has to be as RGBA for rendering then it is 270,141,696 bytes. > > Then ParaView has to create a "cell" for each pixel and then some other stuff. At one point ParaView spiked to 120GB of RAM and then fell back to about 36GB of RAM. This seems a bit excessive to me. This is with ParaView 4.3.1 on a Windows 8.1 workstation. Am I doing something wrong? Just seems like a lot of memory. > > Are their alternate ways of writing the Xdmf file so that each image is a single cell perhaps? > > Thanks for any insights. > > I can make the data set available to anyone who needs it. > _________________________________________________________ > Mike Jackson mike.jackson at bluequartz.net > BlueQuartz Software www.bluequartz.net > Principal Software Engineer Dayton, Ohio > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: Message signed with OpenPGP using GPGMail URL: From utkarsh.ayachit at kitware.com Sun Feb 1 09:35:24 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 1 Feb 2015 09:35:24 -0500 Subject: [Paraview] The ParaView Guide printed editions now available Message-ID: We just wanted to let everyone know that The ParaView Guide has been updated for version 4.3 and is available on Amazon! The guide is available in both color [1] and greyscale [2] versions. (For customers in Europe, it is also available on Amazon's sites for Spain, the United Kingdom, Germany, France, and Italy. Please see our website [3] for the links.) Be sure to check out the new guide! [1] http://amzn.com/1930934300 [2] http://amzn.com/1930934297 [3] http://www.kitware.com/products/books.php From grothausmann.roman at mh-hannover.de Mon Feb 2 05:41:41 2015 From: grothausmann.roman at mh-hannover.de (Dr. Roman Grothausmann) Date: Mon, 02 Feb 2015 11:41:41 +0100 Subject: [Paraview] [ITK-users] compile itk (VTKGlue ON) with vtk from paraview In-Reply-To: References: <54C0CF2E.3060106@mh-hannover.de> <54C2125D.7090801@mh-hannover.de> <54C6029C.4040600@mh-hannover.de> <54C8CFC2.4000305@mh-hannover.de> Message-ID: <54CF5465.9050009@mh-hannover.de> Hi Matt, On 31/01/15 17:25, Matt McCormick wrote: >>> I would recommend creating build instructions to build against a >>> ParaView build tree. I have just verified that ITK builds with the >>> ITKVtkGlue module ON when pointing VTK_DIR to the /VTK >>> directory. >> >> Did You use BUILD_SHARED_LIBS ON for both ITK and ParaView? ITK also >> compiles fine without any errors for me if I use BUILD_SHARED_LIBS OFF, >> however the problems then arise when compiling the plugin. > > I was using BUILD_SHARED_LIBS for both. What issue were you seeing? If I configure ITK with: BUILD_SHARED_LIBS ON Module_ITKVtkGlue ON VTK_DIR /opt/compilation/paraview-git_build/VTK/ cmake is happy but I get linker errors at the end of the compilation of ITK when the VTKGlue is due. After switching off all PV plugin builds leaves: Linking CXX shared library ../../../../lib/libITKVtkGlue-4.6.so /usr/bin/ld: cannot find -lvtkPVPythonCatalyst /usr/bin/ld: cannot find -lvtkUtilitiesPythonInitializer Both libraries seem to be missing entries in /opt/compilation/paraview-git_build/VTK/VTKTargets.cmake I guess that's why the linker cannot find these libraries which are there but with the ending *-pv4.3.so. So a cd /opt/compilation/paraview-git_build/lib/ for i in *-pv*.so; do ln -s $i ${i%-pv*}.so; done did the trick but I guess that's not the way it ought to be done. My guess is that either some lines need to be added to VTKTargets.cmake or that the ITK-build needs to be told that there is no need to link against these libraries for the ITKVtkGlue (if that is true). > Again, I think the best approach is to build VTK separately, then > build both ParaView and ITK against that version. OK, I tried that with vtk-git of today but then paraview cmake complains: cmake -DUSE_EXTERNAL_VTK:BOOL=ON ../paraview-git/ -- Determined Source Version : 4.3.1-18-g04df19f -- Using External VTK from "/opt/vtk-git_150202/lib/cmake/vtk-6.2" CMake Error at CMake/ParaViewModuleTop.cmake:61 (include): include could not find load file: vtkGroups Call Stack (most recent call first): CMakeLists.txt:605 (include) CMake Error at CMake/ParaViewModuleTop.cmake:184 (include): include could not find load file: TopologicalSort Call Stack (most recent call first): CMakeLists.txt:605 (include) CMake Error at CMake/ParaViewModuleTop.cmake:185 (topological_sort): Unknown CMake command "topological_sort". Call Stack (most recent call first): CMakeLists.txt:605 (include) -- Configuring incomplete, errors occurred! I also tried a VTK-6.1 but that just yielded other errors. How do I figure out what VTK-version ParaView needs? Otherwise I think this is not a suitable instruction to give in the publication as the VTK-Version needed is likely to change in future ParaView releases. Therefore I prefer instructions that use the VTK bundled with ParaView. What could be the reason that You did not have the linker problems when ITKVtkGlue was compiled? Again, many thanks for looking into this. Roman >> On 26/01/15 17:54, Matt McCormick wrote: >>> >>> Hi Roman, >>> >>> Thanks for the update. Great to hear about the Midas Journal article! >>> >>> I do not think the Midas Journal will be able to build your plugin. >>> >>> I would recommend creating build instructions to build against a >>> ParaView build tree. I have just verified that ITK builds with the >>> ITKVtkGlue module ON when pointing VTK_DIR to the /VTK >>> directory. >>> >>> I don't see the install tree VTKTargets.cmake file in my ParaView >>> build, either. In the long term, the ParaView CMake configuration >>> should be corrected. >>> >>> HTH, >>> Matt >>> >>> On Mon, Jan 26, 2015 at 4:02 AM, Dr. Roman Grothausmann >>> wrote: >>>> >>>> Hi Matt, >>>> >>>> >>>> Thank You very much for Your reply. >>>> I can only find one VTKTargets.cmake in >>>> /opt/compilation/paraview-git_build/VTK/ >>>> It seems though that it is lacking the relevant entries for the libraries >>>> that troubled me, e.g. vtkPVPythonCatalyst and >>>> vtkUtilitiesPythonInitializer. >>>> >>>> I'm about to publish the ITK-VTK PV plugin in the Midas Journal, what >>>> installation instructions should I give there? >>>> Will the testing environment be able to compile this plugin and its tests >>>> or >>>> should I disable automatic testing for this contribution? >>>> >>>> Many thanks for looking into this. >>>> Roman >>>> >>>> >>>> On 23/01/15 18:15, Matt McCormick wrote: >>>>> >>>>> >>>>> Hi Roman, >>>>> >>>>> Thanks for looking into the issue and reporting it to the mailing list. >>>>> >>>>> Paraview should be installing VTKTargets.cmake, which tells the build >>>>> system where to find the libraries. Note that there might be two >>>>> VTKTargets.cmake files that are generated -- one for the build tree >>>>> and one for the install tree. >>>>> >>>>> HTH, >>>>> Matt >>>>> >>>>> On Fri, Jan 23, 2015 at 4:20 AM, Dr. Roman Grothausmann >>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> On 22/01/15 11:21, Dr. Roman Grothausmann wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> Adding the abs. file locations to the build command does not help nor >>>>>>> does >>>>>>> -L/opt/paraview-4.3.1_git/lib/paraview-4.3/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> I figured that the vtk dynamic libraries of PV have the ending >>>>>> *-pv4.3.so >>>>>> which seems to be the reason why the linker does not find them. If I >>>>>> create >>>>>> symbolic links to these files without the extension: >>>>>> >>>>>> cd /opt/compilation/paraview-git_build/lib/ >>>>>> for i in *-pv*.so; do ln -s $i ${i%-pv*}.so; done >>>>>> >>>>>> and adding -L/opt/compilation/paraview-git_build/lib/ to >>>>>> CMAKE_CXX_FLAGS >>>>>> the compilation of ITK succeeds. >>>>>> >>>>>> I wonder, is that the way it's meant to be done? >>>>>> >>>>>> >>>>>> >>>>>>> What am I missing in my configuration of PV and ITK? >>>>>>> >>>>>>> When and where should I specify: >>>>>>> CMAKE_CXX_FLAGS -fPIC >>>>>>> BUILD_SHARED_LIBS ON/OFF >>>>>>> >>>>>>> Is this the right VTK_DIR specification for ITK: >>>>>>> /opt/compilation/ParaView-v4.3.1/build/VTK >>>>>>> or >>>>>>> /opt/paraview-4.3.1_git/lib/cmake/paraview-4.3 >>>>>>> >>>>>>> >>>>>>> >>>>>>> Many thanks for any help or hints. >>>>>>> Roman >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> Dr. Roman Grothausmann >>>>>> >>>>>> Tomographie und Digitale Bildverarbeitung >>>>>> Tomography and Digital Image Analysis >>>>>> >>>>>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120 >>>>>> Medizinische Hochschule Hannover >>>>>> Carl-Neuberg-Str. 1 >>>>>> D-30625 Hannover >>>>>> >>>>>> Tel. +49 511 532-9574 >>>>>> _____________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Kitware offers ITK Training Courses, for more information visit: >>>>>> http://www.kitware.com/products/protraining.php >>>>>> >>>>>> Please keep messages on-topic and check the ITK FAQ at: >>>>>> http://www.itk.org/Wiki/ITK_FAQ >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/insight-users >>>> >>>> >>>> >>>> -- >>>> Dr. Roman Grothausmann >>>> >>>> Tomographie und Digitale Bildverarbeitung >>>> Tomography and Digital Image Analysis >>>> >>>> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120 >>>> Medizinische Hochschule Hannover >>>> Carl-Neuberg-Str. 1 >>>> D-30625 Hannover >>>> >>>> Tel. +49 511 532-9574 >> >> >> -- >> Dr. Roman Grothausmann >> >> Tomographie und Digitale Bildverarbeitung >> Tomography and Digital Image Analysis >> >> Institut f?r Funktionelle und Angewandte Anatomie, OE 4120 >> Medizinische Hochschule Hannover >> Carl-Neuberg-Str. 1 >> D-30625 Hannover >> >> Tel. +49 511 532-9574 -- Dr. Roman Grothausmann Tomographie und Digitale Bildverarbeitung Tomography and Digital Image Analysis Institut f?r Funktionelle und Angewandte Anatomie, OE 4120 Medizinische Hochschule Hannover Carl-Neuberg-Str. 1 D-30625 Hannover Tel. +49 511 532-9574 From aluaces at udc.es Mon Feb 2 07:32:19 2015 From: aluaces at udc.es (Alberto Luaces) Date: Mon, 02 Feb 2015 13:32:19 +0100 Subject: [Paraview] Display user-defined point and cell IDs from Ensight6 file as labels References: <287077896.12441410.1421877526916.JavaMail.zimbra@udc.es> Message-ID: <87sieoebos.fsf@eps142.cdf.udc.es> Manuel Gonz?lez writes: > Hi, > > I need to display (as labels) the user-defined point IDs and cell IDs in ASCII Ensight6 geometry files. These IDs are neither zero-based nor contiguous. > > Ensight does it correctly, but Paraview displays zero-based contiguous IDs instead of the user-defined IDs given in the file. > The user-defined IDs neither show in the spreadsheet view of Paraview. >From VTK/IO/EnSight/vtkEnSight6Reader.cxx, line 1752, it can be seen that VTK discards explicit ids (the first element on the line): if (!(sscanf(line, " %*d %d %d %d", &intIds[0], &intIds[1],... Does VTK support unstructured IDs on cells? -- Alberto From f.veronesi at scsitaly.com Mon Feb 2 08:41:10 2015 From: f.veronesi at scsitaly.com (Federico Veronesi) Date: Mon, 2 Feb 2015 14:41:10 +0100 Subject: [Paraview] Issue with reset camera and parallel projection Message-ID: Dear all, I found a possible bug in both version 4.2 and 4.3.1: When parallel projection is checked the reset camera actions (reset and zoom to data) need to be clicked twice to have effect after a zoom (both wheel and right mouse button) . Moreover the "camera undo" do not work after a zoom in or out. Regards Federico -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Mon Feb 2 10:07:16 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Mon, 2 Feb 2015 10:07:16 -0500 Subject: [Paraview] Fwd: Visualization in ParaView/VisIt In-Reply-To: <54CA551C.5010306@gmail.com> References: <54CA551C.5010306@gmail.com> Message-ID: Hey folks, If you develop HDF5 readers based on h5py, please report results here. I am sure the community will love to hear from those using it in production. Also, for those that are thinking about using HDF5 in Python, I would highly recommend this book: http://shop.oreilly.com/product/0636920030249.do Best, -berk On Thu, Jan 29, 2015 at 10:43 AM, Armin Wehrfritz wrote: > I just stumbled across this interesting blog: > http://berkgeveci.github.io/2015/01/08/h5py-writer-reader/ > > If you have some kind of python knowledge, especially the "HDF5Reader" > part should be very interesting for you. > For this you don't even need the XDMF files. > > -Armin > > > > On 01/28/2015 10:55 PM, Martin Huarte Espinosa wrote: > >> Dear Armin and Dave: thanks for your replies. I will try. >> >> Martin. >> >> On Wed, Jan 28, 2015 at 2:30 PM, Armin Wehrfritz > > wrote: >> >> For such kind of data I typically write a custom made XDMF [1] file. >> XDMF is basically a XML wrapper that contains the description of the >> HDF5 data file. >> What comes in handy in your cases, is that you have the heavy data >> already in a HDF5 file. >> >> I typically write the XDMF file with a hand crafted python script >> since I typically deal with data sets from various source. >> However, there is also a XDMF library [2,3], which should provide >> some convenient advantages. >> >> The XDMF file format is very well supported by ParaView, or VisIt >> for that matter. >> >> I attached 2 XDMF files, so you get an idea what I'm talking of (the >> HDF5 data files are missing though). >> >> -Armin >> >> [1] http://www.xdmf.org/index.php/__Main_Page >> >> [2] http://www.xdmf.org/index.php/__Get_Xdmf >> >> [3] http://www.xdmf.org/index.php/__Write_Xdmf >> >> >> >> >> >> On 01/28/2015 09:52 PM, Mart?n Huarte E wrote: >> >> Dear Paraview community: Good day. I need assistance on >> visualizing a >> matlab file? Any tips will be greatly appreciated. Thanks. >> >> >> Details: >> I need to visualize temperature distribution in a volume. The >> volume is >> a wedge-like slice of a hollow cylinder (shown in the attached >> schematic). >> >> The calculations are made in MATLAB. The three-dimensional >> matrices of >> the solution (T) and the node-coordinates (X, Y and Z) are saved >> in a >> HDF5 file. >> >> So far, I have not been able to make ParaView to visualize the >> result in >> the actual geometry. They get the length, width and height of >> the volume >> and simply build a cuboid out of them. >> >> Thanks >> >> My best, Mart?n >> __ >> /Mart?n Huarte-Espinosa, Ph.D./ >> /Computational Physicist - //High Performance Computing >> Specialist/ >> /linkedin.com/pub/martin-__huarte-espinosa/59/6b7/13a >> >> > >/ >> >> >> >> >> >> _________________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/__opensource/opensource.html >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/__ParaView >> >> >> 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 >> >> >> >> >> -- >> >> My best, Mart?n >> __ >> /Mart?n Huarte-Espinosa, Ph.D./ >> /Computational Physicist - //High Performance Computing Specialist/ >> /linkedin.com/pub/martin-huarte-espinosa/59/6b7/13a >> / >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 elias.pipping at fu-berlin.de Mon Feb 2 10:11:57 2015 From: elias.pipping at fu-berlin.de (Elias Pipping) Date: Mon, 02 Feb 2015 15:11:57 +0000 Subject: [Paraview] Python interface: ExportView does not accept parameters Message-ID: Dear list, I'm trying to export vector graphics through paraview's python interface(*). To that end, from within paraview, I start a python trace, use the UI to export to an embedded postscript file (via File->Export scene), and stop the trace again. The relevant lines of the trace look something like this: renderView1 = GetActiveViewOrCreate('RenderView') ExportView('test.eps', view=renderView1) Now I can open a python interpreter, paste these lines and get the expected result. So far, so good. Now let me retrace the above steps: After selecting a location to save to, I'm presented with a setting of export options. In the above scenario, I left everything as-is. I can choose among "rasterize 3d geometry", "draw background", etc. (the latter is an advanced option). If I change those options, they're passed to ExportView, yielding a line like the following in the trace: ExportView('test.eps', view=renderView1, Drawbackground=0, Rasterize3Dgeometry=0) While saving from the UI continues to work even in this case, running the above from within the python interpreter does not. Here's what I get: File "[..]/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/site-packages/paraview/simple.py", line 1350, in ExportView SetProperties(proxy, **params) File "[..]/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/site-packages/paraview/simple.py", line 449, in SetProperties raise AttributeError("object has no property %s" % param) AttributeError: object has no property Drawbackground Neither the field Drawbackground nor Rasterize3Dgeometry is recognised. Is the python interface currently incomplete in this respect? Is this easily fixed or is there a workaround for this issue? Best regards, Elias Pipping (*) All of this concerns a paraview 4.3.1 binary for linux -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Feb 2 12:23:29 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 2 Feb 2015 12:23:29 -0500 Subject: [Paraview] Python interface: ExportView does not accept parameters In-Reply-To: References: Message-ID: This is indeed a bug. I've reported it here [1]. Attached script shows how to overcome this issue in 4.3. You'll need to add the following stub to your code. Note this is only a workaround. Once the bug is fixed, one should not use this hack. #----------------------------------------------- # HACK: Overcomes a bug# 15298 conn = servermanager.ActiveConnection misc = conn.Modules.misc servermanager.createModule("exporters", misc) #----------------------------------------------- [1] http://www.paraview.org/Bug/view.php?id=15298 On Mon, Feb 2, 2015 at 10:11 AM, Elias Pipping wrote: > Dear list, > > I'm trying to export vector graphics through paraview's python interface(*). > To that end, from within paraview, I start a python trace, use the UI to > export to an embedded postscript file (via File->Export scene), and stop the > trace again. > The relevant lines of the trace look something like this: > > renderView1 = GetActiveViewOrCreate('RenderView') > ExportView('test.eps', view=renderView1) > > Now I can open a python interpreter, paste these lines and get the expected > result. So far, so good. > > Now let me retrace the above steps: After selecting a location to save to, > I'm presented with a setting of export options. In the above scenario, I > left everything as-is. I can choose among "rasterize 3d geometry", "draw > background", etc. (the latter is an advanced option). > > If I change those options, they're passed to ExportView, yielding a line > like the following in the trace: > > ExportView('test.eps', view=renderView1, Drawbackground=0, > Rasterize3Dgeometry=0) > > While saving from the UI continues to work even in this case, running the > above from within the python interpreter does not. Here's what I get: > > File > "[..]/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/site-packages/paraview/simple.py", > line 1350, in ExportView > SetProperties(proxy, **params) > File > "[..]/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/site-packages/paraview/simple.py", > line 449, in SetProperties > raise AttributeError("object has no property %s" % param) > AttributeError: object has no property Drawbackground > > Neither the field Drawbackground nor Rasterize3Dgeometry is recognised. > > Is the python interface currently incomplete in this respect? Is this easily > fixed or is there a workaround for this issue? > > > Best regards, > > Elias Pipping > > (*) All of this concerns a paraview 4.3.1 binary for linux > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: sample.py Type: text/x-python Size: 980 bytes Desc: not available URL: From andy.bauer at kitware.com Mon Feb 2 13:13:47 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 2 Feb 2015 13:13:47 -0500 Subject: [Paraview] Gradient of 2D velocity field with paraview In-Reply-To: <250108449.382432.1422786600329.JavaMail.yahoo@mail.yahoo.com> References: <250108449.382432.1422786600329.JavaMail.yahoo@mail.yahoo.com> Message-ID: Hi, The Extract Surface filter will subdivide the quadratic triangles into 4 linear triangles so the resulting field will likely lose some accuracy but not as bad as just going from a quadratic triangle to a linear triangle. I added in a bug for our bug tracker at http://www.paraview.org/Bug/view.php?id=15299 so that gradients can be computed properly for quadratic triangles. I don't have an estimate of when this may get fixed though. If this is urgent enough, this is open-source software so you can try fixing it yourself and sending in a patch. Otherwise, Kitware does provide support contracts for fixing such bugs (see http://www.kitware.eu/products/support.html for more info). Regards, Andy On Sun, Feb 1, 2015 at 5:30 AM, Eleonora Piersanti < eleonorapiersanti at yahoo.it> wrote: > Sorry to bother you again. But I need the gradient to make some > verifications in my code. Then, the problem of accuracy is quite important. > Is there any way to compute the gradient without using the Extract surface > filter? > > Kind regards, > Eleonora > > > Il Venerd? 30 Gennaio 2015 11:48, Andy Bauer > ha scritto: > > > It looks like the Gradient of Unstructured Data Set filter isn't working > properly with quadratic triangles. Try using the Extract Surface filter > before computing gradients to convert them into linear triangles. > > If you want to get more familiar with using ParaView, the ParaView > tutorial at http://www.paraview.org/Wiki/The_ParaView_Tutorial is a good > place to start. > > Regards, > Andy > > On Fri, Jan 30, 2015 at 6:25 AM, Eleonora Piersanti < > eleonorapiersanti at yahoo.it> wrote: > > Thank you for the answer. > I think that the dimension of the .vtk file was too big. You can download > the .vtk file from: > > > https://www.dropbox.com/s/o1wjo2brsaeu5ag/stability_realEigU_up0.vtk.tar.gz?dl=0 > > In which sense should I use the Slice filter? Sorry but I am quite new > with paraview. > Kind regards, > Eleonora > > Il Venerd? 30 Gennaio 2015 11:16, Eleonora Piersanti < > eleonorapiersanti at yahoo.it> ha scritto: > > > Thank you, for the answer. > I attach the .vtk file. In which sense should I use the Slice filter? > Sorry but I am quite new with paraview. > Kind regards, > Eleonora > > > Il Venerd? 30 Gennaio 2015 10:59, Andy Bauer > ha scritto: > > > Your description is a bit vague to diagnose the issue. Can you share your > data set? I was able to use the Wavelet source, use the Slice filter and > then use the Gradient of Unstructured Data Set without any issues. Can you > see if that works for you? > > Regards, > Andy > > On Fri, Jan 30, 2015 at 5:26 AM, Eleonora Piersanti < > eleonorapiersanti at yahoo.it> wrote: > > Hi to everyone! > I computed with finite elements a 2D velocity field. I plotted without any > problem the velocity field with paraview. I would like to compute the > gradient. > I tried Filters->Gradient of Unstructured Data Set but without succes. > Can you help me? > Thanks, > Nora > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 g.brito at aia.rwth-aachen.de Mon Feb 2 14:00:42 2015 From: g.brito at aia.rwth-aachen.de (Gonzalo Brito Gadeschi) Date: Mon, 2 Feb 2015 20:00:42 +0100 Subject: [Paraview] Is there a way to reuse the preivous DataSet from RequestData Message-ID: In a reader plugin for unstructured grids, after the plugin opens a file, and paraview calls RequestData for the first time, I initialize the grid like: vtkInformation* outInfo = outputVector->GetInformationObject(0); vtkDataSet* output = vtkDataSet::GetData(outInfo); vtk_grid = vtkUnstructuredGrid::SafeDownCast(output); vtk_grid->Initialize(); vtk_grid->Allocate(0); vtkSmartPointer points = vtkSmartPointer::New(); vtk_grid->SetPoints(points); // create grid points, cells.. // load cell data fields (the user can control this via the plugin interface) If the user then decides to load/unload some fields, I would like to reuse the loaded points and cells, and just update/add/remove fields. The problem comes when in subsequent calls to RequestData: vtkInformation* outInfo = outputVector->GetInformationObject(0); vtkDataSet* output = vtkDataSet::GetData(outInfo); // this asserts works: assert(old_vtk_grid == vtkUnstructuredGrid::SafeDownCast(output)); // this assert fails: the number of points is 0.. assert(old_number_of_points == vtk_grid->GetNumberOfPoints()); // this produces a segmentation fault assert(old_number_of_cells == vtk_grid->GetCells()->GetNumberOfCells()); That is, even tho the grid pointer that gets passed to RequestData points to the same memory as before, it seems that the grid is "empty" (number of points is 0). Is there a way to preserve the grid state between calls to RequestData? Bests, Gonzalo -- Dipl.-Ing. Gonzalo Brito Gadeschi Institute of Aerodynamics and Chair of Fluid Mechanics RWTH Aachen University Wuellnerstra?e 5a D-52062 Aachen Germany Phone: ++49-(0)241-80-94821 Fax: ++49-(0)241-80-92257 E-mail: g.brito at aia.rwth-aachen.de Internet: www.aia.rwth-aachen.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Feb 2 14:02:09 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 2 Feb 2015 14:02:09 -0500 Subject: [Paraview] Python interface: ExportView does not accept parameters In-Reply-To: References: Message-ID: Attached is fix, which will get merged in git/master soon. Thanks for reporting. On Mon, Feb 2, 2015 at 12:23 PM, Utkarsh Ayachit wrote: > This is indeed a bug. I've reported it here [1]. Attached script shows > how to overcome this issue in 4.3. You'll need to add the following > stub to your code. Note this is only a workaround. Once the bug is > fixed, one should not use this hack. > > #----------------------------------------------- > # HACK: Overcomes a bug# 15298 > conn = servermanager.ActiveConnection > misc = conn.Modules.misc > servermanager.createModule("exporters", misc) > #----------------------------------------------- > > > [1] http://www.paraview.org/Bug/view.php?id=15298 > > On Mon, Feb 2, 2015 at 10:11 AM, Elias Pipping > wrote: >> Dear list, >> >> I'm trying to export vector graphics through paraview's python interface(*). >> To that end, from within paraview, I start a python trace, use the UI to >> export to an embedded postscript file (via File->Export scene), and stop the >> trace again. >> The relevant lines of the trace look something like this: >> >> renderView1 = GetActiveViewOrCreate('RenderView') >> ExportView('test.eps', view=renderView1) >> >> Now I can open a python interpreter, paste these lines and get the expected >> result. So far, so good. >> >> Now let me retrace the above steps: After selecting a location to save to, >> I'm presented with a setting of export options. In the above scenario, I >> left everything as-is. I can choose among "rasterize 3d geometry", "draw >> background", etc. (the latter is an advanced option). >> >> If I change those options, they're passed to ExportView, yielding a line >> like the following in the trace: >> >> ExportView('test.eps', view=renderView1, Drawbackground=0, >> Rasterize3Dgeometry=0) >> >> While saving from the UI continues to work even in this case, running the >> above from within the python interpreter does not. Here's what I get: >> >> File >> "[..]/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/site-packages/paraview/simple.py", >> line 1350, in ExportView >> SetProperties(proxy, **params) >> File >> "[..]/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/site-packages/paraview/simple.py", >> line 449, in SetProperties >> raise AttributeError("object has no property %s" % param) >> AttributeError: object has no property Drawbackground >> >> Neither the field Drawbackground nor Rasterize3Dgeometry is recognised. >> >> Is the python interface currently incomplete in this respect? Is this easily >> fixed or is there a workaround for this issue? >> >> >> Best regards, >> >> Elias Pipping >> >> (*) All of this concerns a paraview 4.3.1 binary for linux >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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: 0001-BUG-15298.-Fixes-exporters-in-Python.patch Type: text/x-patch Size: 8092 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Mon Feb 2 14:03:26 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 2 Feb 2015 14:03:26 -0500 Subject: [Paraview] Is there a way to reuse the preivous DataSet from RequestData In-Reply-To: References: Message-ID: The only way is to cache it in the reader itself. Create a new vtkUnstructuredGrid and ShallowCopy the contents of your "output" to it at the end of your RequestData(). Utkarsh On Mon, Feb 2, 2015 at 2:00 PM, Gonzalo Brito Gadeschi wrote: > In a reader plugin for unstructured grids, after the plugin opens a file, > and paraview calls RequestData for the first time, I initialize the grid > like: > > vtkInformation* outInfo = outputVector->GetInformationObject(0); > vtkDataSet* output = vtkDataSet::GetData(outInfo); > vtk_grid = vtkUnstructuredGrid::SafeDownCast(output); > > vtk_grid->Initialize(); > vtk_grid->Allocate(0); > vtkSmartPointer points = vtkSmartPointer::New(); > vtk_grid->SetPoints(points); > // create grid points, cells.. > // load cell data fields (the user can control this via the plugin > interface) > > If the user then decides to load/unload some fields, I would like to reuse > the loaded points and cells, and just update/add/remove fields. > > The problem comes when in subsequent calls to RequestData: > > vtkInformation* outInfo = outputVector->GetInformationObject(0); > vtkDataSet* output = vtkDataSet::GetData(outInfo); > > // this asserts works: > assert(old_vtk_grid == vtkUnstructuredGrid::SafeDownCast(output)); > // this assert fails: the number of points is 0.. > assert(old_number_of_points == vtk_grid->GetNumberOfPoints()); > // this produces a segmentation fault > assert(old_number_of_cells == vtk_grid->GetCells()->GetNumberOfCells()); > > That is, even tho the grid pointer that gets passed to RequestData points to > the same memory as before, it seems that the grid is "empty" (number of > points is 0). > > Is there a way to preserve the grid state between calls to RequestData? > > Bests, > Gonzalo > > -- > Dipl.-Ing. Gonzalo Brito Gadeschi > Institute of Aerodynamics and Chair of Fluid Mechanics > RWTH Aachen University > Wuellnerstra?e 5a > D-52062 Aachen > Germany > Phone: ++49-(0)241-80-94821 > Fax: ++49-(0)241-80-92257 > E-mail: g.brito at aia.rwth-aachen.de > Internet: www.aia.rwth-aachen.de > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From bruce.david.jones at gmail.com Mon Feb 2 14:36:00 2015 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Mon, 02 Feb 2015 19:36:00 +0000 Subject: [Paraview] Plugin with dropdown list crash Message-ID: Hi, I'm writing a paraview plugin based on a python programmable filter. To do this I'm using the excellent plugin generator described here, http://www.kitware.com/blog/home/post/534 I am trying to add a dropdown list to the plugin XML, as in here http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Drop_down_list However including the example code, or the code I actually need, in the XML causes paraview to crash when the filter is selected. Due to the way paraview is crashing, I can see the output messages but not select or scroll. One line seems pertinent which is Incorrect message received. missing xml_group and xml_name information Any suggestions? Cheers, Bruce -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Feb 2 14:46:21 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 2 Feb 2015 14:46:21 -0500 Subject: [Paraview] Plugin with dropdown list crash In-Reply-To: References: Message-ID: Mind sharing the generated XML that you're trying to load? It will be easier to debug. On Mon, Feb 2, 2015 at 2:36 PM, Bruce Jones wrote: > Hi, > > I'm writing a paraview plugin based on a python programmable filter. To do > this I'm using the excellent plugin generator described here, > http://www.kitware.com/blog/home/post/534 > > I am trying to add a dropdown list to the plugin XML, as in here > http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Drop_down_list > > However including the example code, or the code I actually need, in the XML > causes paraview to crash when the filter is selected. > > Due to the way paraview is crashing, I can see the output messages but not > select or scroll. One line seems pertinent which is > > Incorrect message received. missing xml_group and xml_name information > > Any suggestions? > > Cheers, > Bruce > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 bruce.david.jones at gmail.com Mon Feb 2 14:47:57 2015 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Mon, 02 Feb 2015 19:47:57 +0000 Subject: [Paraview] Plugin with dropdown list crash References: Message-ID: Sure, XML is attached. It expects VTKPolyData and outputs VTKImageData Cheers, Bruce On Mon Feb 02 2015 at 2:46:22 PM Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Mind sharing the generated XML that you're trying to load? It will be > easier to debug. > > On Mon, Feb 2, 2015 at 2:36 PM, Bruce Jones > wrote: > > Hi, > > > > I'm writing a paraview plugin based on a python programmable filter. To > do > > this I'm using the excellent plugin generator described here, > > http://www.kitware.com/blog/home/post/534 > > > > I am trying to add a dropdown list to the plugin XML, as in here > > http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Drop_down_list > > > > However including the example code, or the code I actually need, in the > XML > > causes paraview to crash when the filter is selected. > > > > Due to the way paraview is crashing, I can see the output messages but > not > > select or scroll. One line seems pertinent which is > > > > Incorrect message received. missing xml_group and xml_name information > > > > Any suggestions? > > > > Cheers, > > Bruce > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > 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: GridFromSPH.xml Type: text/xml Size: 10318 bytes Desc: not available URL: From bruce.david.jones at gmail.com Mon Feb 2 14:54:18 2015 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Mon, 02 Feb 2015 19:54:18 +0000 Subject: [Paraview] [bug] load -> remove -> load plugin nolonger appears in manager Message-ID: Hey, Not sure if this is the best place to report this. I have noticed that if you load a plugin (xml plugin at least), then remove the plugin, then load the same plugin again, it doesn't appear in the list of plugins in the manage plugins window. The plugin does however appear to load successfully and can be used. Cheers, Bruce -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Feb 2 15:01:18 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 2 Feb 2015 15:01:18 -0500 Subject: [Paraview] Plugin with dropdown list crash In-Reply-To: References: Message-ID: You're missing the "initial_string" attribute. Fixed XML attached. You may want to put the correct value for the intial_string. I just put "Mapping_Type". On Mon, Feb 2, 2015 at 2:47 PM, Bruce Jones wrote: > Sure, XML is attached. It expects VTKPolyData and outputs VTKImageData > > Cheers, > Bruce > > On Mon Feb 02 2015 at 2:46:22 PM Utkarsh Ayachit > wrote: >> >> Mind sharing the generated XML that you're trying to load? It will be >> easier to debug. >> >> On Mon, Feb 2, 2015 at 2:36 PM, Bruce Jones >> wrote: >> > Hi, >> > >> > I'm writing a paraview plugin based on a python programmable filter. To >> > do >> > this I'm using the excellent plugin generator described here, >> > http://www.kitware.com/blog/home/post/534 >> > >> > I am trying to add a dropdown list to the plugin XML, as in here >> > http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Drop_down_list >> > >> > However including the example code, or the code I actually need, in the >> > XML >> > causes paraview to crash when the filter is selected. >> > >> > Due to the way paraview is crashing, I can see the output messages but >> > not >> > select or scroll. One line seems pertinent which is >> > >> > Incorrect message received. missing xml_group and xml_name information >> > >> > Any suggestions? >> > >> > Cheers, >> > Bruce >> > >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > 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: GridFromSPH.xml Type: text/xml Size: 10357 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Mon Feb 2 15:04:06 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 2 Feb 2015 15:04:06 -0500 Subject: [Paraview] [bug] load -> remove -> load plugin nolonger appears in manager In-Reply-To: References: Message-ID: You should not unload plugins that way. "Remove" plugin simply forgets the plugin so it's state won't be saved. It's to be used to discard obsolete/temporary plugins. You'll need to restart ParaView to reload a plugin. While XML plugins, reloading may work fine, it will has weird issues with C++ plugins or in some other cases. On Mon, Feb 2, 2015 at 2:54 PM, Bruce Jones wrote: > Hey, > > Not sure if this is the best place to report this. > > I have noticed that if you load a plugin (xml plugin at least), then remove > the plugin, then load the same plugin again, it doesn't appear in the list > of plugins in the manage plugins window. > > The plugin does however appear to load successfully and can be used. > > Cheers, > Bruce > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 bruce.david.jones at gmail.com Mon Feb 2 15:14:57 2015 From: bruce.david.jones at gmail.com (Bruce Jones) Date: Mon, 02 Feb 2015 20:14:57 +0000 Subject: [Paraview] Plugin with dropdown list crash References: Message-ID: Thank you UtKarsh. It looks like the wiki needs updating to reflect this. Cheers, Bruce On Mon Feb 02 2015 at 3:01:19 PM Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > You're missing the "initial_string" attribute. Fixed XML attached. You > may want to put the correct value for the intial_string. I just put > "Mapping_Type". > > On Mon, Feb 2, 2015 at 2:47 PM, Bruce Jones > wrote: > > Sure, XML is attached. It expects VTKPolyData and outputs VTKImageData > > > > Cheers, > > Bruce > > > > On Mon Feb 02 2015 at 2:46:22 PM Utkarsh Ayachit > > wrote: > >> > >> Mind sharing the generated XML that you're trying to load? It will be > >> easier to debug. > >> > >> On Mon, Feb 2, 2015 at 2:36 PM, Bruce Jones < > bruce.david.jones at gmail.com> > >> wrote: > >> > Hi, > >> > > >> > I'm writing a paraview plugin based on a python programmable filter. > To > >> > do > >> > this I'm using the excellent plugin generator described here, > >> > http://www.kitware.com/blog/home/post/534 > >> > > >> > I am trying to add a dropdown list to the plugin XML, as in here > >> > http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Drop_down_list > >> > > >> > However including the example code, or the code I actually need, in > the > >> > XML > >> > causes paraview to crash when the filter is selected. > >> > > >> > Due to the way paraview is crashing, I can see the output messages but > >> > not > >> > select or scroll. One line seems pertinent which is > >> > > >> > Incorrect message received. missing xml_group and xml_name information > >> > > >> > Any suggestions? > >> > > >> > Cheers, > >> > Bruce > >> > > >> > > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > 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 g.brito at aia.rwth-aachen.de Mon Feb 2 15:21:52 2015 From: g.brito at aia.rwth-aachen.de (Gonzalo Brito Gadeschi) Date: Mon, 2 Feb 2015 21:21:52 +0100 Subject: [Paraview] Is there a way to reuse the preivous DataSet from RequestData In-Reply-To: <47a4fd96770a4d04a220eb00bc2e017e@HUB2.rwth-ad.de> References: <47a4fd96770a4d04a220eb00bc2e017e@HUB2.rwth-ad.de> Message-ID: Thanks, that solves it. On Mon, Feb 2, 2015 at 8:03 PM, Utkarsh Ayachit wrote: > The only way is to cache it in the reader itself. Create a new > vtkUnstructuredGrid and ShallowCopy the contents of your "output" to > it at the end of your RequestData(). > > Utkarsh > > On Mon, Feb 2, 2015 at 2:00 PM, Gonzalo Brito Gadeschi > wrote: > > In a reader plugin for unstructured grids, after the plugin opens a file, > > and paraview calls RequestData for the first time, I initialize the grid > > like: > > > > vtkInformation* outInfo = outputVector->GetInformationObject(0); > > vtkDataSet* output = vtkDataSet::GetData(outInfo); > > vtk_grid = vtkUnstructuredGrid::SafeDownCast(output); > > > > vtk_grid->Initialize(); > > vtk_grid->Allocate(0); > > vtkSmartPointer points = vtkSmartPointer::New(); > > vtk_grid->SetPoints(points); > > // create grid points, cells.. > > // load cell data fields (the user can control this via the plugin > > interface) > > > > If the user then decides to load/unload some fields, I would like to > reuse > > the loaded points and cells, and just update/add/remove fields. > > > > The problem comes when in subsequent calls to RequestData: > > > > vtkInformation* outInfo = outputVector->GetInformationObject(0); > > vtkDataSet* output = vtkDataSet::GetData(outInfo); > > > > // this asserts works: > > assert(old_vtk_grid == vtkUnstructuredGrid::SafeDownCast(output)); > > // this assert fails: the number of points is 0.. > > assert(old_number_of_points == vtk_grid->GetNumberOfPoints()); > > // this produces a segmentation fault > > assert(old_number_of_cells == > vtk_grid->GetCells()->GetNumberOfCells()); > > > > That is, even tho the grid pointer that gets passed to RequestData > points to > > the same memory as before, it seems that the grid is "empty" (number of > > points is 0). > > > > Is there a way to preserve the grid state between calls to RequestData? > > > > Bests, > > Gonzalo > > > > -- > > Dipl.-Ing. Gonzalo Brito Gadeschi > > Institute of Aerodynamics and Chair of Fluid Mechanics > > RWTH Aachen University > > Wuellnerstra?e 5a > > D-52062 Aachen > > Germany > > Phone: ++49-(0)241-80-94821 > > Fax: ++49-(0)241-80-92257 > > E-mail: g.brito at aia.rwth-aachen.de > > Internet: www.aia.rwth-aachen.de > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -- Dipl.-Ing. Gonzalo Brito Gadeschi Institute of Aerodynamics and Chair of Fluid Mechanics RWTH Aachen University Wuellnerstra?e 5a D-52062 Aachen Germany Phone: ++49-(0)241-80-94821 Fax: ++49-(0)241-80-92257 E-mail: g.brito at aia.rwth-aachen.de Internet: www.aia.rwth-aachen.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From timcfagan at gmail.com Mon Feb 2 21:30:08 2015 From: timcfagan at gmail.com (timcfagan .) Date: Tue, 3 Feb 2015 13:30:08 +1100 Subject: [Paraview] particle surface based on position In-Reply-To: References: Message-ID: Maybe I can implement something in that case, perhaps based from data created from a temporal particles to pathlines filter. Does anyone have any suggestions? cheers, Tim On Sat, Jan 31, 2015 at 4:40 PM, timcfagan . wrote: > I can generate surfaces but it seems none of them are based on particle > positions. Anyone know if this is part of paraview functionality? > > On Wed, Jan 28, 2015 at 3:55 PM, timcfagan . wrote: > >> Is there a way for paraview to generate a surface based on point >> positions? >> >> Viewing particle data as a surface, it just shows the points. One way I >> have generated a "surface" is to use a contour by mass on nodal points. But >> this is a bit iffy as changing the mass threshold will add or remove parts >> of the surface. >> >> Attached is an image for both of these. The contour looks okay, but >> probably isn't the right way to go about it... >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.kospach at gmx.at Tue Feb 3 06:37:48 2015 From: a.kospach at gmx.at (Alexander Kospach) Date: Tue, 3 Feb 2015 12:37:48 +0100 Subject: [Paraview] Problems with "Read zones" References: <54BF962A.3040903@mail.ru> <54BFA12E.7070103@mail.ru> <54C20AAC.9070601@mail.ru>, , Message-ID: An HTML attachment was scrubbed... URL: From fw248 at exeter.ac.uk Tue Feb 3 18:09:38 2015 From: fw248 at exeter.ac.uk (Wilczynski, Fryderyk) Date: Tue, 3 Feb 2015 23:09:38 +0000 Subject: [Paraview] 3D animation of a vector field (ParaView) In-Reply-To: References: Message-ID: <1423004976828.9896@exeter.ac.uk> QUESTION! I am trying to create an animation of a 3d vector field in ParaView. All my data is in three matrices (201 x 201 x 201) corresponding to vectors components in x,y,z directions. And it's calculated in MATLAB. If I do: B = cat(4,Bx,By,Bz); B = permute(B,[4 1 2 3]); fid = fopen('Bvec.raw','w'); fwrite(fid,B,'float'); fclose(fid); I can load Bvec.raw into ParaView and visualise the vector field at one instant of time. Now, how would I go about making an animation if I had say 100 (Bx, By, Bz) triples at different instants of time? Without creating 100 different raw files and loading them into paraview by hand. ALSO, I'm not set on using paraview, it's just the first software I tried, so if you think there's an easier/better/ more competent way of going about it I'd appreciate suggestions.? -------------- next part -------------- An HTML attachment was scrubbed... URL: From senocak at boisestate.edu Tue Feb 3 18:56:33 2015 From: senocak at boisestate.edu (Inanc Senocak) Date: Tue, 3 Feb 2015 16:56:33 -0700 Subject: [Paraview] visualizing xdmf/hdf5 files in parallel Message-ID: Hi Everybody, We have a parallel structured Cartesian grid flow solver. We output our solution file using xdmf/hdf5 format. File sizes are large (56 GB) so we need to render the flow solution in parallel. We are able to use VisIT to load and render the solution files (xdmf/hdf5) efficiently. But we haven't had luck with Paraview. We use version 4.3. Basically as we are loading the files, pvserver consumes all the memory per node (64TB) and then it crashes. We are able to use pvserver to render (in parallel) smaller simulation files (xdmf/hdf5) without any issues. We have tried several options building pvserver but it did not make any difference in rendering large files. Maybe there is a bug in the way our simulation code writes xdmf/hdf5 files. Does anyone have a large xdmf/hdf5 simulation file that we can download to verify our paraview installation and its parallel rendering performance? If you have any other tips/experiences regarding parallel rendering of large xdmf/hdf5 files, please let me know. Thank you! Inanc -- Inanc Senocak Associate Professor Mechanical & Biomedical Engineering Boise State University 1910 University Dr. Boise, ID 83725-2085 phone: (208) 426-4066 fax: (208) 426-4800 e-mail: senocak at boisestate.edu website: http://coen.boisestate.edu/senocak -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christophe.Dang at sidel.com Wed Feb 4 03:12:18 2015 From: Christophe.Dang at sidel.com (Dang, Christophe) Date: Wed, 4 Feb 2015 08:12:18 +0000 Subject: [Paraview] 3D animation of a vector field (ParaView) In-Reply-To: <1423004976828.9896@exeter.ac.uk> References: <1423004976828.9896@exeter.ac.uk> Message-ID: Hello, > De : Wilczynski, Fryderyk > Envoy? : mercredi 4 f?vrier 2015 00:10 > > Without creating 100 different raw files and loading them into paraview by hand. You just have to create your hundred files and name them Filename00.raw Filename01.raw Etc. And ParaView will automatically load them at once See the User Manual, chap. Loading Data, section Opening File / Time Series (p. 9) Hope this helps, regards -- Christophe Dang Ngoc Chan Mechanical calculation engineer This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. From hfklinac at hotmail.com Wed Feb 4 03:36:06 2015 From: hfklinac at hotmail.com (Hannah Klinac) Date: Wed, 4 Feb 2015 16:36:06 +0800 Subject: [Paraview] Paraview enabled VR Plugin not interacting via VRPN Message-ID: Hi, I recently compiled Paraview from the source code to enable the VR Plugin. I have built VRPN, and compiled Paraview using that VRPN's dependencies. However, when I add the connection and interaction in the VR Plugin in Paraview and press "Start", when I (for example) press the button I have registered down, the interaction doesn't happen. And on my server it says: "vrpn: Connection requiest received from 'IP address': 'IP address' 'Port'Get a new connection, reset virtual_Tracker" Any idea if I have just not setup my connection/interaction correctly in Paraview? The VRPN server works fine for other applications such as Vizard. Thanks in advance for any guidance,Hannah -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkxls23 at gmail.com Wed Feb 4 07:25:27 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Wed, 04 Feb 2015 14:25:27 +0200 Subject: [Paraview] visualizing xdmf/hdf5 files in parallel In-Reply-To: References: Message-ID: <54D20FB7.2060206@gmail.com> There has been a similar discussion half a year ago: http://public.kitware.com/pipermail/paraview/2014-June/031350.html I believe this is still investigated/ under development. -Armin On 02/04/2015 01:56 AM, Inanc Senocak wrote: > Hi Everybody, > > We have a parallel structured Cartesian grid flow solver. We output our > solution file using xdmf/hdf5 format. File sizes are large (56 GB) so we > need to render the flow solution in parallel. > > We are able to use VisIT to load and render the solution files > (xdmf/hdf5) efficiently. But we haven't had luck with Paraview. We use > version 4.3. Basically as we are loading the files, pvserver consumes > all the memory per node (64TB) and then it crashes. We are able to use > pvserver to render (in parallel) smaller simulation files (xdmf/hdf5) > without any issues. > > We have tried several options building pvserver but it did not make any > difference in rendering large files. Maybe there is a bug in the way our > simulation code writes xdmf/hdf5 files. > > Does anyone have a large xdmf/hdf5 simulation file that we can download > to verify our paraview installation and its parallel rendering performance? > > If you have any other tips/experiences regarding parallel rendering of > large xdmf/hdf5 files, please let me know. > > Thank you! > > Inanc > > > -- > Inanc Senocak > Associate Professor > Mechanical & Biomedical Engineering > Boise State University > 1910 University Dr. > Boise, ID 83725-2085 > phone: (208) 426-4066 > fax: (208) 426-4800 > e-mail: senocak at boisestate.edu > website: http://coen.boisestate.edu/senocak > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 stephen.wornom at inria.fr Wed Feb 4 09:51:06 2015 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Wed, 04 Feb 2015 15:51:06 +0100 Subject: [Paraview] PV4.1: plot over line using actual points rather than interpolated points Message-ID: <54D231DA.2070505@inria.fr> Plot over a line requests the number of points. I would like to use the actual mesh points, is this possible? Hope the question is clear, Stephen -- stephen.wornom at inria.fr 2004 route des lucioles - BP93 Sophia Antipolis 06902 CEDEX Tel: 04 92 38 50 54 Fax: 04 97 15 53 51 -------------- next part -------------- A non-text attachment was scrubbed... Name: stephen_wornom.vcf Type: text/x-vcard Size: 187 bytes Desc: not available URL: From nenasantos at hotmail.com Wed Feb 4 10:00:35 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Wed, 4 Feb 2015 15:00:35 +0000 Subject: [Paraview] Run a paraview-phyton scricpt in a windows batch file In-Reply-To: <54D231DA.2070505@inria.fr> References: <54D231DA.2070505@inria.fr> Message-ID: I try to run a paraview-phyton script in a batch file in windows but i get this error: C:\Users\madalenasantos\Desktop\Paraview>py Cone.pyTraceback (most recent call last): File "Cone.py", line 2, in from paraview.simple import *ImportError: No module named 'paraview' C:\Users\madalenasantos\Desktop\Paraview>PausePress any key to continue . . . Can any one could help me? Kind regardsMadalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Feb 4 11:11:10 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 4 Feb 2015 11:11:10 -0500 Subject: [Paraview] Paraview enabled VR Plugin not interacting via VRPN In-Reply-To: References: Message-ID: Hi Hannah, On Wed, Feb 4, 2015 at 3:36 AM, Hannah Klinac wrote: > Hi, > > I recently compiled Paraview from the source code to enable the VR Plugin. > > I have built VRPN, and compiled Paraview using that VRPN's dependencies. > > However, when I add the connection and interaction in the VR Plugin in > Paraview and press "Start", when I (for example) press the button I have > registered down, the interaction doesn't happen. And on my server it says: > > "vrpn: Connection requiest received from 'IP address': 'IP address' 'Port' > Get a new connection, reset virtual_Tracker" > Is it possible for you to share the VR state file? Or provide information on how you setup the VRPN server in the first place? Seems like a configuration issue. Also, helpful to know the version of ParaView and the OS you are using? > > Any idea if I have just not setup my connection/interaction correctly in > Paraview? The VRPN server works fine for other applications such as Vizard. > Thanks, > > Thanks in advance for any guidance, > Hannah > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Feb 4 11:52:19 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 4 Feb 2015 11:52:19 -0500 Subject: [Paraview] PV4.1: plot over line using actual points rather than interpolated points In-Reply-To: <54D231DA.2070505@inria.fr> References: <54D231DA.2070505@inria.fr> Message-ID: Not "over the line", but you can plot the all the actual point-data values themselves. Try applying the "Plot Data" filter. Then you can plot the point/cell values directly. Utkarsh On Wed, Feb 4, 2015 at 9:51 AM, Stephen Wornom wrote: > Plot over a line requests the number of points. > > I would like to use the actual mesh points, is this possible? > Hope the question is clear, > Stephen > > -- > stephen.wornom at inria.fr > 2004 route des lucioles - BP93 > Sophia Antipolis > 06902 CEDEX > > Tel: 04 92 38 50 54 > Fax: 04 97 15 53 51 > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Feb 4 11:56:41 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 4 Feb 2015 11:56:41 -0500 Subject: [Paraview] ANN: ParaView 4.3.1 is available for download In-Reply-To: <54D24E2C.5080009@cora.nwra.com> References: <54D24E2C.5080009@cora.nwra.com> Message-ID: Because I posted the wrong link :). I should have indeed posted the link you provided i.e. http://www.kitware.com/blog/home/post/825 The other one for "viewing" a post you're editing, which is only accessible when you're logged in. Utkarsh On Wed, Feb 4, 2015 at 11:51 AM, Orion Poplawski wrote: > On 01/20/2015 02:17 PM, Utkarsh Ayachit wrote: >> Folks, >> >> ParaView 4.3.1 is now available for download. Checkout the release >> notes on the Kitware blog [1]. >> >> As always, we look forward to your feedback [2]. >> >> Also stay tuned to the Kitware Blog [3] for upcoming features and >> enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much >> more! >> >> - The ParaView team >> >> [1] http://www.kitware.com/blog/posts/view/825 > > Why do I have to login to see this page? > > I don't to see: http://www.kitware.com/blog/home/post/825 > > > -- > Orion Poplawski > Technical Manager 303-415-9701 x222 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane orion at nwra.com > Boulder, CO 80301 http://www.nwra.com From orion at cora.nwra.com Wed Feb 4 11:51:56 2015 From: orion at cora.nwra.com (Orion Poplawski) Date: Wed, 04 Feb 2015 09:51:56 -0700 Subject: [Paraview] ANN: ParaView 4.3.1 is available for download In-Reply-To: References: Message-ID: <54D24E2C.5080009@cora.nwra.com> On 01/20/2015 02:17 PM, Utkarsh Ayachit wrote: > Folks, > > ParaView 4.3.1 is now available for download. Checkout the release > notes on the Kitware blog [1]. > > As always, we look forward to your feedback [2]. > > Also stay tuned to the Kitware Blog [3] for upcoming features and > enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much > more! > > - The ParaView team > > [1] http://www.kitware.com/blog/posts/view/825 Why do I have to login to see this page? I don't to see: http://www.kitware.com/blog/home/post/825 -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion at nwra.com Boulder, CO 80301 http://www.nwra.com From dave.demarle at kitware.com Wed Feb 4 17:14:38 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 4 Feb 2015 17:14:38 -0500 Subject: [Paraview] visualizing xdmf/hdf5 files in parallel In-Reply-To: References: Message-ID: Hi Inanc, Can you share the xdmf file with me? I can take a look and see what we are doing wrong with it and recommend a path forward in ParaView, be it xdmf3 or the python source or what not. thanks, David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Feb 3, 2015 at 6:56 PM, Inanc Senocak wrote: > Hi Everybody, > > We have a parallel structured Cartesian grid flow solver. We output our > solution file using xdmf/hdf5 format. File sizes are large (56 GB) so we > need to render the flow solution in parallel. > > We are able to use VisIT to load and render the solution files (xdmf/hdf5) > efficiently. But we haven't had luck with Paraview. We use version 4.3. > Basically as we are loading the files, pvserver consumes all the memory per > node (64TB) and then it crashes. We are able to use pvserver to render (in > parallel) smaller simulation files (xdmf/hdf5) without any issues. > > We have tried several options building pvserver but it did not make any > difference in rendering large files. Maybe there is a bug in the way our > simulation code writes xdmf/hdf5 files. > > Does anyone have a large xdmf/hdf5 simulation file that we can download to > verify our paraview installation and its parallel rendering performance? > > If you have any other tips/experiences regarding parallel rendering of > large xdmf/hdf5 files, please let me know. > > Thank you! > > Inanc > > > -- > Inanc Senocak > Associate Professor > Mechanical & Biomedical Engineering > Boise State University > 1910 University Dr. > Boise, ID 83725-2085 > phone: (208) 426-4066 > fax: (208) 426-4800 > e-mail: senocak at boisestate.edu > website: http://coen.boisestate.edu/senocak > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 g.brito at aia.rwth-aachen.de Thu Feb 5 07:03:35 2015 From: g.brito at aia.rwth-aachen.de (Gonzalo Brito Gadeschi) Date: Thu, 5 Feb 2015 13:03:35 +0100 Subject: [Paraview] CMake warning when linking plugin with library Message-ID: When using the following CMake code to link a library to a paraview plugin: > add_paraview_plugin(Reader "v1.0" > SERVER_MANAGER_XML vtkReaderServConf.xml > GUI_INTERFACES ${interfaces} > SERVER_MANAGER_SOURCES vtkReader.cxx > SOURCES ${sources} > REQUIRED_ON_SERVER) > > target_link_libraries(Reader ${READER_LIBS}) I get from CMake the following warning. CMake Warning (dev) at reader/CMakeLists.txt:22 (target_link_libraries): > PolicyCMP0023 is not set: Plain and keyword target_link_libraries > signatures cannot be mixed. Run "cmake --help-policy CMP0023" for policy > details. Use the cmake_policy command to set the policy and suppress this > warning. > The keyword signature for target_link_libraries has already been used with > the target "Reader". All uses of target_link_libraries with a target > should be either all-keyword or all-plain. > > The uses of the keyword signature are here: > * paraview_src/CMake/ParaViewPlugins.cmake:1096 (target_link_libraries) > * paraview_src/CMake/ParaViewPlugins.cmake:1099 (target_link_libraries) > > This warning is for project developers. Use -Wno-dev to suppress it. What am I doing wrong and how do I fix it? -- Dipl.-Ing. Gonzalo Brito Gadeschi Institute of Aerodynamics and Chair of Fluid Mechanics RWTH Aachen University Wuellnerstra?e 5a D-52062 Aachen Germany Phone: ++49-(0)241-80-94821 Fax: ++49-(0)241-80-92257 E-mail: g.brito at aia.rwth-aachen.de Internet: www.aia.rwth-aachen.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Thu Feb 5 07:14:55 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Thu, 5 Feb 2015 12:14:55 +0000 Subject: [Paraview] error paraview - run windows batch via phyton In-Reply-To: References: , Message-ID: Dear all,What i have to do to link the paraview libraries to phyton libraries ? I try to tun a paraview scrip invocing phyton in a Windos batch file and i have the following error: C:\Users\madalenasantos\Desktop\Paraview>python Cone.py"Error: Could not import vtkCommonComputationalGeometryPythonTraceback (most recent call last): File "Cone.py", line 2, in from paraview.simple import * File "C:\Python27\lib\site-packages\paraview\simple.py", line 39, in import servermanager File "C:\Python27\lib\site-packages\paraview\servermanager.py", line 48, in import paraview, re, os, os.path, new, sys, atexit, vtk File "C:\Python27\lib\site-packages\paraview\vtk\__init__.py", line 7, in from vtkCommonCorePython import *ImportError: No module named vtkCommonCorePython C:\Users\madalenasantos\Desktop\Paraview>PausePress any key to continue . . . Madalena From: g.brito at aia.rwth-aachen.de Date: Thu, 5 Feb 2015 13:03:35 +0100 To: paraview at paraview.org Subject: [Paraview] CMake warning when linking plugin with library When using the following CMake code to link a library to a paraview plugin: > add_paraview_plugin(Reader "v1.0" > SERVER_MANAGER_XML vtkReaderServConf.xml > GUI_INTERFACES ${interfaces} > SERVER_MANAGER_SOURCES vtkReader.cxx > SOURCES ${sources} > REQUIRED_ON_SERVER) > > target_link_libraries(Reader ${READER_LIBS}) I get from CMake the following warning. CMake Warning (dev) at reader/CMakeLists.txt:22 (target_link_libraries): > PolicyCMP0023 is not set: Plain and keyword target_link_libraries > signatures cannot be mixed. Run "cmake --help-policy CMP0023" for policy > details. Use the cmake_policy command to set the policy and suppress this > warning. > The keyword signature for target_link_libraries has already been used with > the target "Reader". All uses of target_link_libraries with a target > should be either all-keyword or all-plain. > > The uses of the keyword signature are here: > * paraview_src/CMake/ParaViewPlugins.cmake:1096 (target_link_libraries) > * paraview_src/CMake/ParaViewPlugins.cmake:1099 (target_link_libraries) > > This warning is for project developers. Use -Wno-dev to suppress it. What am I doing wrong and how do I fix it? -- Dipl.-Ing. Gonzalo Brito Gadeschi Institute of Aerodynamics and Chair of Fluid Mechanics RWTH Aachen University Wuellnerstra?e 5a D-52062 Aachen Germany Phone: ++49-(0)241-80-94821 Fax: ++49-(0)241-80-92257 E-mail: g.brito at aia.rwth-aachen.de Internet: www.aia.rwth-aachen.de _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Thu Feb 5 07:13:11 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Thu, 5 Feb 2015 12:13:11 +0000 Subject: [Paraview] CMake warning when linking plugin with library In-Reply-To: References: Message-ID: Dear all,What i have to do to link the paraview libraries to phyton libraries ? I try to tun a paraview scrip invocing phyton in a Windos batch file and i have the following error: C:\Users\madalenasantos\Desktop\Paraview>python Cone.py"Error: Could not import vtkCommonComputationalGeometryPythonTraceback (most recent call last): File "Cone.py", line 2, in from paraview.simple import * File "C:\Python27\lib\site-packages\paraview\simple.py", line 39, in import servermanager File "C:\Python27\lib\site-packages\paraview\servermanager.py", line 48, in import paraview, re, os, os.path, new, sys, atexit, vtk File "C:\Python27\lib\site-packages\paraview\vtk\__init__.py", line 7, in from vtkCommonCorePython import *ImportError: No module named vtkCommonCorePython C:\Users\madalenasantos\Desktop\Paraview>PausePress any key to continue . . . Madalena From: g.brito at aia.rwth-aachen.de Date: Thu, 5 Feb 2015 13:03:35 +0100 To: paraview at paraview.org Subject: [Paraview] CMake warning when linking plugin with library When using the following CMake code to link a library to a paraview plugin: > add_paraview_plugin(Reader "v1.0" > SERVER_MANAGER_XML vtkReaderServConf.xml > GUI_INTERFACES ${interfaces} > SERVER_MANAGER_SOURCES vtkReader.cxx > SOURCES ${sources} > REQUIRED_ON_SERVER) > > target_link_libraries(Reader ${READER_LIBS}) I get from CMake the following warning. CMake Warning (dev) at reader/CMakeLists.txt:22 (target_link_libraries): > PolicyCMP0023 is not set: Plain and keyword target_link_libraries > signatures cannot be mixed. Run "cmake --help-policy CMP0023" for policy > details. Use the cmake_policy command to set the policy and suppress this > warning. > The keyword signature for target_link_libraries has already been used with > the target "Reader". All uses of target_link_libraries with a target > should be either all-keyword or all-plain. > > The uses of the keyword signature are here: > * paraview_src/CMake/ParaViewPlugins.cmake:1096 (target_link_libraries) > * paraview_src/CMake/ParaViewPlugins.cmake:1099 (target_link_libraries) > > This warning is for project developers. Use -Wno-dev to suppress it. What am I doing wrong and how do I fix it? -- Dipl.-Ing. Gonzalo Brito Gadeschi Institute of Aerodynamics and Chair of Fluid Mechanics RWTH Aachen University Wuellnerstra?e 5a D-52062 Aachen Germany Phone: ++49-(0)241-80-94821 Fax: ++49-(0)241-80-92257 E-mail: g.brito at aia.rwth-aachen.de Internet: www.aia.rwth-aachen.de _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From 303343023 at qq.com Thu Feb 5 09:17:47 2015 From: 303343023 at qq.com (=?ISO-8859-1?B?MzAzMzQzMDIz?=) Date: Thu, 5 Feb 2015 22:17:47 +0800 Subject: [Paraview] Track massive particles over time, particle ID is known Message-ID: Hi everyone It troubles me for times. I have a series of particles vtk files at different time step. And I want to track certain particles and extract them or color them with a uniform color. I tried to use "find data" and include the particle id with "is one of " option. However, it crashed due to overload of compute capacity. About 8 thousand particles is intended for tracking. Furthermore, at the begining, the particles of interest located at the upper layer, coordinatesZ>0, for example. And I want to extract them from the whole. Could any one help me? Thanks in advance! Chenshu Hu -------------- next part -------------- An HTML attachment was scrubbed... URL: From timcfagan at gmail.com Thu Feb 5 18:46:10 2015 From: timcfagan at gmail.com (timcfagan .) Date: Fri, 6 Feb 2015 10:46:10 +1100 Subject: [Paraview] Track massive particles over time, particle ID is known In-Reply-To: References: Message-ID: I've tried to do the same thing Chenshu, this is how I ended up doing it: open vtk particle file generate ids (possibly apply it even if they already have ids) extract entire dataset with particles through threshold by generated ids for the particles you want (This can be done multiple times to select multiple sets of points, then append datasets to combine them to one) Temporal particles to pathlines Unfortunately I haven't found a better way to actually select the particles other than through selecting them by particle ids. Just extracting a selection doesn't work properly with the pathlines filter. But you can extract a selection and view their ids in spreadsheet form. I was doing this, writing it down and then applying the threshold. Also the generate id's filter was applying them in layers in z, so you may find thresholding for z>0 is easy as it might be one threshold in the id's. You just need to find the right id number. Maybe someone knows a better way though... On Fri, Feb 6, 2015 at 1:17 AM, 303343023 <303343023 at qq.com> wrote: > *Hi everyone* > * It troubles me for times. * > * I have a series of particles vtk files at different time step. And I > want to track certain particles and extract them or color them with a > uniform color. I tried to use "find data" and include the particle id with > "is one of " option. However, it crashed due to overload of compute > capacity. About 8 thousand particles is intended for tracking.* > * Furthermore, at the begining, the particles of interest located at the > upper layer, coordinatesZ>0, for example. And I want to extract them from > the whole.* > * Could any one help me? Thanks in advance!* > > Chenshu Hu > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 timcfagan at gmail.com Thu Feb 5 18:53:34 2015 From: timcfagan at gmail.com (timcfagan .) Date: Fri, 6 Feb 2015 10:53:34 +1100 Subject: [Paraview] Track massive particles over time, particle ID is known In-Reply-To: References: Message-ID: And to color them, the temporal particles to pathline filter has particles and pathlines separated. If you select solid color for either/both of them, you can change it to what you like. Also if you are having trouble viewing a large set of point data, perhaps view them using the point sprites plugin. Load this in the Tools > Manage Plugins. On Fri, Feb 6, 2015 at 10:46 AM, timcfagan . wrote: > I've tried to do the same thing Chenshu, this is how I ended up doing it: > > open vtk particle file > generate ids (possibly apply it even if they already have ids) > extract entire dataset with particles through > threshold by generated ids for the particles you want > (This can be done multiple times to select multiple sets of points, then > append datasets to combine them to one) > Temporal particles to pathlines > > Unfortunately I haven't found a better way to actually select the > particles other than through selecting them by particle ids. Just > extracting a selection doesn't work properly with the pathlines filter. But > you can extract a selection and view their ids in spreadsheet form. I was > doing this, writing it down and then applying the threshold. Also the > generate id's filter was applying them in layers in z, so you may find > thresholding for z>0 is easy as it might be one threshold in the id's. You > just need to find the right id number. > > Maybe someone knows a better way though... > > On Fri, Feb 6, 2015 at 1:17 AM, 303343023 <303343023 at qq.com> wrote: > >> *Hi everyone* >> * It troubles me for times. * >> * I have a series of particles vtk files at different time step. And I >> want to track certain particles and extract them or color them with a >> uniform color. I tried to use "find data" and include the particle id with >> "is one of " option. However, it crashed due to overload of compute >> capacity. About 8 thousand particles is intended for tracking.* >> * Furthermore, at the begining, the particles of interest located at >> the upper layer, coordinatesZ>0, for example. And I want to extract them >> from the whole.* >> * Could any one help me? Thanks in advance!* >> >> Chenshu Hu >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 ruggiero.guida at gmail.com Thu Feb 5 23:48:22 2015 From: ruggiero.guida at gmail.com (Ruggiero Guida) Date: Fri, 6 Feb 2015 08:48:22 +0400 Subject: [Paraview] Slice on arbitrary surface Message-ID: Dear Paraview users, How can I create a 'slice' with an arbitrary surface? My input file is in .case format (Ensight Gold) exported from StarCCM+. I would like to visualize the solution on a surface within the domain defined in STL or VTK format. The surface is not necessarily planar. Is it possible to do this? Thanks Ruggiero -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruggiero.guida at gmail.com Fri Feb 6 03:49:42 2015 From: ruggiero.guida at gmail.com (Ruggiero Guida) Date: Fri, 6 Feb 2015 12:49:42 +0400 Subject: [Paraview] Slice on arbitrary surface In-Reply-To: <54D47935.7020507@tu-dortmund.de> References: <54D47935.7020507@tu-dortmund.de> Message-ID: Dear Sven, Thanks for your help. Unfortunately it does not seem to work. I have tried with VTK, STL and CSV (applying TableTo points), but the only variables available for coloring are those of the mesh. I have selected the case file as input and the mesh as source. I have also tried to select the various options such (Pass Scalars, Fields, etc.). I think that the case file is fine because normal slices work as expected. If you have time to have a look at the files you can download them from here https://www.dropbox.com/s/s5foo4cph0tvkjn/Geometry.zip?dl=0 https://www.dropbox.com/s/f2ym5jva70jlcsc/simulations.zip?dl=0 Thanks a lot Ruggiero On 6 February 2015 at 12:20, Sven Buijssen wrote: > Ruggiero, > > I'd go with the filter "Resample With Dataset": Load both input file and > the intersecting surface, set the former as input and the latter as > source for the filter. Disable visibility of the two input data sets > afterwards. > > Hope that helps > Sven > > > Ruggiero Guida schrieb am 06.02.2015 um 05:48: > > Dear Paraview users, > > > > How can I create a 'slice' with an arbitrary surface? > > > > My input file is in .case format (Ensight Gold) exported from StarCCM+. > > > > I would like to visualize the solution on a surface within the domain > > defined in STL or VTK format. The surface is not necessarily planar. > > > > Is it possible to do this? > > > > Thanks > > Ruggiero > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > 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 sven.buijssen at tu-dortmund.de Fri Feb 6 04:13:51 2015 From: sven.buijssen at tu-dortmund.de (Sven Buijssen) Date: Fri, 06 Feb 2015 10:13:51 +0100 Subject: [Paraview] Slice on arbitrary surface In-Reply-To: References: <54D47935.7020507@tu-dortmund.de> Message-ID: <54D485CF.9060804@tu-dortmund.de> Ruggiero, Your Ensight case file is read in as a multi-block dataset. Please run the filter "Merge Blocks" prior to applying "Resample With Dataset". After that temperature and velocity from your Ensight case file are available as point data arrays on the intersecting surface. (It seems "Resample With Dataset" has still some difficulties with multi-block datasets. In older PV versions, it was not even directly applicable to a multi-block dataset.) Sven Ruggiero Guida schrieb am 06.02.2015 um 09:49: > Dear Sven, > > Thanks for your help. Unfortunately it does not seem to work. I have > tried with VTK, STL and CSV (applying TableTo points), but the only > variables available for coloring are those of the mesh. > > I have selected the case file as input and the mesh as source. I have > also tried to select the various options such (Pass Scalars, Fields, etc.). > > I think that the case file is fine because normal slices work as expected. > > If you have time to have a look at the files you can download them from here > > https://www.dropbox.com/s/s5foo4cph0tvkjn/Geometry.zip?dl=0 > https://www.dropbox.com/s/f2ym5jva70jlcsc/simulations.zip?dl=0 > > Thanks a lot > > Ruggiero > > > > > On 6 February 2015 at 12:20, Sven Buijssen > wrote: > > Ruggiero, > > I'd go with the filter "Resample With Dataset": Load both input file and > the intersecting surface, set the former as input and the latter as > source for the filter. Disable visibility of the two input data sets > afterwards. > > Hope that helps > Sven > > > Ruggiero Guida schrieb am 06.02.2015 um 05:48: > > Dear Paraview users, > > > > How can I create a 'slice' with an arbitrary surface? > > > > My input file is in .case format (Ensight Gold) exported from > StarCCM+. > > > > I would like to visualize the solution on a surface within the domain > > defined in STL or VTK format. The surface is not necessarily planar. > > > > Is it possible to do this? > > > > Thanks > > Ruggiero > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > 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 ruggiero.guida at gmail.com Fri Feb 6 04:27:36 2015 From: ruggiero.guida at gmail.com (Ruggiero Guida) Date: Fri, 6 Feb 2015 13:27:36 +0400 Subject: [Paraview] Slice on arbitrary surface In-Reply-To: <54D485CF.9060804@tu-dortmund.de> References: <54D47935.7020507@tu-dortmund.de> <54D485CF.9060804@tu-dortmund.de> Message-ID: It works! Thanks a lot Sven. Cheers Ruggiero On 6 February 2015 at 13:13, Sven Buijssen wrote: > Ruggiero, > > Your Ensight case file is read in as a multi-block dataset. Please run > the filter "Merge Blocks" prior to applying "Resample With Dataset". > After that temperature and velocity from your Ensight case file are > available as point data arrays on the intersecting surface. (It seems > "Resample With Dataset" has still some difficulties with multi-block > datasets. In older PV versions, it was not even directly applicable to a > multi-block dataset.) > > Sven > > > Ruggiero Guida schrieb am 06.02.2015 um 09:49: > > Dear Sven, > > > > Thanks for your help. Unfortunately it does not seem to work. I have > > tried with VTK, STL and CSV (applying TableTo points), but the only > > variables available for coloring are those of the mesh. > > > > I have selected the case file as input and the mesh as source. I have > > also tried to select the various options such (Pass Scalars, Fields, > etc.). > > > > I think that the case file is fine because normal slices work as > expected. > > > > If you have time to have a look at the files you can download them from > here > > > > https://www.dropbox.com/s/s5foo4cph0tvkjn/Geometry.zip?dl=0 > > https://www.dropbox.com/s/f2ym5jva70jlcsc/simulations.zip?dl=0 > > > > Thanks a lot > > > > Ruggiero > > > > > > > > > > On 6 February 2015 at 12:20, Sven Buijssen > > wrote: > > > > Ruggiero, > > > > I'd go with the filter "Resample With Dataset": Load both input file > and > > the intersecting surface, set the former as input and the latter as > > source for the filter. Disable visibility of the two input data sets > > afterwards. > > > > Hope that helps > > Sven > > > > > > Ruggiero Guida schrieb am 06.02.2015 um 05:48: > > > Dear Paraview users, > > > > > > How can I create a 'slice' with an arbitrary surface? > > > > > > My input file is in .case format (Ensight Gold) exported from > > StarCCM+. > > > > > > I would like to visualize the solution on a surface within the > domain > > > defined in STL or VTK format. The surface is not necessarily > planar. > > > > > > Is it possible to do this? > > > > > > Thanks > > > Ruggiero > > > > > > > > > _______________________________________________ > > > Powered by www.kitware.com > > > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > > > 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 sven.buijssen at tu-dortmund.de Fri Feb 6 03:20:05 2015 From: sven.buijssen at tu-dortmund.de (Sven Buijssen) Date: Fri, 06 Feb 2015 09:20:05 +0100 Subject: [Paraview] Slice on arbitrary surface In-Reply-To: References: Message-ID: <54D47935.7020507@tu-dortmund.de> Ruggiero, I'd go with the filter "Resample With Dataset": Load both input file and the intersecting surface, set the former as input and the latter as source for the filter. Disable visibility of the two input data sets afterwards. Hope that helps Sven Ruggiero Guida schrieb am 06.02.2015 um 05:48: > Dear Paraview users, > > How can I create a 'slice' with an arbitrary surface? > > My input file is in .case format (Ensight Gold) exported from StarCCM+. > > I would like to visualize the solution on a surface within the domain > defined in STL or VTK format. The surface is not necessarily planar. > > Is it possible to do this? > > Thanks > Ruggiero > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Fri Feb 6 13:15:25 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 6 Feb 2015 13:15:25 -0500 Subject: [Paraview] error paraview - run windows batch via phyton In-Reply-To: References: Message-ID: Here are the steps to figure this out: 1. Run pvpython 2. The type the following: import sys print sys.path 3. You should append any extra locations reported here to the sys.path variable in your script when running python.exe 4. You may need to set your environment variable PATH to point to the bin directory where all the dlls are present (I am not sure if this is needed, since I don't using Windows often, but it may be). Utkarsh On Thu, Feb 5, 2015 at 7:14 AM, Madalena S. Malhadas wrote: > Dear all, > What i have to do to link the paraview libraries to phyton libraries ? > > I try to tun a paraview scrip invocing phyton in a Windos batch file and i > have the following error: > > C:\Users\madalenasantos\Desktop\Paraview>python Cone.py" > Error: Could not import vtkCommonComputationalGeometryPython > Traceback (most recent call last): > File "Cone.py", line 2, in > from paraview.simple import * > File "C:\Python27\lib\site-packages\paraview\simple.py", line 39, in > > import servermanager > File "C:\Python27\lib\site-packages\paraview\servermanager.py", line 48, > in odule> > import paraview, re, os, os.path, new, sys, atexit, vtk > File "C:\Python27\lib\site-packages\paraview\vtk\__init__.py", line 7, in > ule> > from vtkCommonCorePython import * > ImportError: No module named vtkCommonCorePython > > C:\Users\madalenasantos\Desktop\Paraview>Pause > Press any key to continue . . . > > > > Madalena > > ________________________________ > From: g.brito at aia.rwth-aachen.de > Date: Thu, 5 Feb 2015 13:03:35 +0100 > To: paraview at paraview.org > Subject: [Paraview] CMake warning when linking plugin with library > > When using the following CMake code to link a library to a paraview plugin: > >> add_paraview_plugin(Reader "v1.0" >> SERVER_MANAGER_XML vtkReaderServConf.xml >> GUI_INTERFACES ${interfaces} >> SERVER_MANAGER_SOURCES vtkReader.cxx >> SOURCES ${sources} >> REQUIRED_ON_SERVER) >> >> target_link_libraries(Reader ${READER_LIBS}) > > I get from CMake the following warning. > > CMake Warning (dev) at reader/CMakeLists.txt:22 (target_link_libraries): > >> PolicyCMP0023 is not set: Plain and keyword target_link_libraries >> signatures cannot be mixed. Run "cmake --help-policy CMP0023" for >> policy >> details. Use the cmake_policy command to set the policy and suppress >> this >> warning. >> The keyword signature for target_link_libraries has already been used >> with >> the target "Reader". All uses of target_link_libraries with a target >> should be either all-keyword or all-plain. >> >> The uses of the keyword signature are here: >> * paraview_src/CMake/ParaViewPlugins.cmake:1096 (target_link_libraries) >> * paraview_src/CMake/ParaViewPlugins.cmake:1099 (target_link_libraries) >> >> This warning is for project developers. Use -Wno-dev to suppress it. > > What am I doing wrong and how do I fix it? > -- > Dipl.-Ing. Gonzalo Brito Gadeschi > Institute of Aerodynamics and Chair of Fluid Mechanics > RWTH Aachen University > Wuellnerstra?e 5a > D-52062 Aachen > Germany > Phone: ++49-(0)241-80-94821 > Fax: ++49-(0)241-80-92257 > E-mail: g.brito at aia.rwth-aachen.de > Internet: www.aia.rwth-aachen.de > > _______________________________________________ Powered by www.kitware.com > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html Please keep messages > on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > Search the list archives at: http://markmail.org/search/?q=ParaView Follow > this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Fri Feb 6 13:17:49 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 6 Feb 2015 13:17:49 -0500 Subject: [Paraview] CMake warning when linking plugin with library In-Reply-To: References: Message-ID: Fix it as: target_link_libraries(Reader LINK_PRIVATE ${READER_LIBS}) (Note the LINK_PRIVATE flag). See [1] for details. Utkarsh [1] http://www.cmake.org/cmake/help/v3.0/command/target_link_libraries.html On Thu, Feb 5, 2015 at 7:03 AM, Gonzalo Brito Gadeschi wrote: > When using the following CMake code to link a library to a paraview plugin: > >> add_paraview_plugin(Reader "v1.0" >> SERVER_MANAGER_XML vtkReaderServConf.xml >> GUI_INTERFACES ${interfaces} >> SERVER_MANAGER_SOURCES vtkReader.cxx >> SOURCES ${sources} >> REQUIRED_ON_SERVER) >> >> target_link_libraries(Reader ${READER_LIBS}) > > I get from CMake the following warning. > > CMake Warning (dev) at reader/CMakeLists.txt:22 (target_link_libraries): > >> PolicyCMP0023 is not set: Plain and keyword target_link_libraries >> signatures cannot be mixed. Run "cmake --help-policy CMP0023" for >> policy >> details. Use the cmake_policy command to set the policy and suppress >> this >> warning. >> The keyword signature for target_link_libraries has already been used >> with >> the target "Reader". All uses of target_link_libraries with a target >> should be either all-keyword or all-plain. >> >> The uses of the keyword signature are here: >> * paraview_src/CMake/ParaViewPlugins.cmake:1096 (target_link_libraries) >> * paraview_src/CMake/ParaViewPlugins.cmake:1099 (target_link_libraries) >> >> This warning is for project developers. Use -Wno-dev to suppress it. > > What am I doing wrong and how do I fix it? > > -- > Dipl.-Ing. Gonzalo Brito Gadeschi > Institute of Aerodynamics and Chair of Fluid Mechanics > RWTH Aachen University > Wuellnerstra?e 5a > D-52062 Aachen > Germany > Phone: ++49-(0)241-80-94821 > Fax: ++49-(0)241-80-92257 > E-mail: g.brito at aia.rwth-aachen.de > Internet: www.aia.rwth-aachen.de > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From bloring at lbl.gov Fri Feb 6 13:55:25 2015 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 06 Feb 2015 10:55:25 -0800 Subject: [Paraview] reducing startup time on cray Message-ID: <54D50E1D.4010202@lbl.gov> Hi All, I want to share a performance issue related to PV start up time, which in general on our cray's is significant usability issue, especially on Hopper. Earlier this week NERSC did some upgrades on one of our Crays which introduced some issues that prevent ParaView from starting. In the end we found that the issue is a system issue (file system or python problem) and not ParaView, but this exposed a performance issue in ParaView. ParaView would connect then hang when creating the render view. The debugger shows ParaView stuck in a python import call(stack is below) from vtkMatplotlibMathTextUtilities::CheckMPLAvailability. This function initializes the python interpreter and tries to "import matplotlib". Importing a python module (that's not built into the core of python) is an extremely expensive and unscalable operation in HPC setting. Software like python and ParaView, at least at NERSC, lives on slow remote file systems and in parallel the import hammers these file systems from each process. Python is essential for batch processing, but when using the interactive ParaView we should delay/avoid python imports as much as possible , especially during start up. This is a scalability issue in that most user aren't going to use the tex feature, but all users startup time is impacted, especially as job size grows. I think in the case of ParaView's matplotlib tex features the run time check for matplotlib could probably be deferred until someone actually tries to use tex. What do you think? This would help keep startup time fast. Burlen proc_set{0}: #0 0x00002aaaae6b8fd0 in __open_nocancel proc_set{0}: #1 0x00002aaaae65e483 in __GI__IO_file_open proc_set{0}: #2 0x00002aaaae65e5fb in _IO_new_file_fopen proc_set{0}: #3 0x00002aaaae6522f4 in __fopen_internal proc_set{0}: #4 0x00002aaaaddb833c in find_module at Python/import.c:1556 proc_set{0}: #5 0x00002aaaaddba470 in import_submodule at Python/import.c:2689 proc_set{0}: #6 0x00002aaaaddbb0e3 in load_next at Python/import.c:2515 proc_set{0}: #7 0x00002aaaaddbb0e3 in import_module_level at Python/import.c:2224 proc_set{0}: #8 0x00002aaaaddbb0e3 in PyImport_ImportModuleLevel at Python/import.c:2288 proc_set{0}: #9 0x00002aaaadd998cf in builtin___import__ at Python/bltinmodule.c:49 proc_set{0}: #10 0x00002aaaadceae93 in PyObject_Call at Objects/abstract.c:2529 proc_set{0}: #11 0x00002aaaadd9b327 in PyEval_CallObjectWithKeywords at Python/ceval.c:3890 proc_set{0}: #12 0x00002aaaadd9e296 in PyEval_EvalFrameEx at Python/ceval.c:2333 proc_set{0}: #13 0x00002aaaadda198d in PyEval_EvalCodeEx at Python/ceval.c:3253 proc_set{0}: #14 0x00002aaaadda1ac2 in PyEval_EvalCode at Python/ceval.c:667 proc_set{0}: #15 0x00002aaaaddb924c in PyImport_ExecCodeModuleEx at Python/import.c:709 proc_set{0}: #16 0x00002aaaaddb95ae in load_source_module at Python/import.c:1099 proc_set{0}: #17 0x00002aaaaddba4a9 in import_submodule at Python/import.c:2700 proc_set{0}: #18 0x00002aaaaddbb0e3 in load_next at Python/import.c:2515 proc_set{0}: #19 0x00002aaaaddbb0e3 in import_module_level at Python/import.c:2224 proc_set{0}: #20 0x00002aaaaddbb0e3 in PyImport_ImportModuleLevel at Python/import.c:2288 proc_set{0}: #21 0x00002aaaadd998cf in builtin___import__ at Python/bltinmodule.c:49 proc_set{0}: #22 0x00002aaaadceae93 in PyObject_Call at Objects/abstract.c:2529 proc_set{0}: #23 0x00002aaaadd9b327 in PyEval_CallObjectWithKeywords at Python/ceval.c:3890 proc_set{0}: #24 0x00002aaaadd9e296 in PyEval_EvalFrameEx at Python/ceval.c:2333 proc_set{0}: #25 0x00002aaaadda198d in PyEval_EvalCodeEx at Python/ceval.c:3253 proc_set{0}: #26 0x00002aaaadda1ac2 in PyEval_EvalCode at Python/ceval.c:667 proc_set{0}: #27 0x00002aaaaddb924c in PyImport_ExecCodeModuleEx at Python/import.c:709 proc_set{0}: #28 0x00002aaaaddb95ae in load_source_module at Python/import.c:1099 proc_set{0}: #29 0x00002aaaaddba4a9 in import_submodule at Python/import.c:2700 proc_set{0}: #30 0x00002aaaaddbb567 in load_next at Python/import.c:2519 proc_set{0}: #31 0x00002aaaaddbb567 in import_module_level at Python/import.c:2224 proc_set{0}: #32 0x00002aaaaddbb567 in PyImport_ImportModuleLevel at Python/import.c:2288 proc_set{0}: #33 0x00002aaaadd998cf in builtin___import__ at Python/bltinmodule.c:49 proc_set{0}: #34 0x00002aaaadceae93 in PyObject_Call at Objects/abstract.c:2529 proc_set{0}: #35 0x00002aaaadd9b327 in PyEval_CallObjectWithKeywords at Python/ceval.c:3890 proc_set{0}: #36 0x00002aaaadd9e296 in PyEval_EvalFrameEx at Python/ceval.c:2333 proc_set{0}: #37 0x00002aaaadda198d in PyEval_EvalCodeEx at Python/ceval.c:3253 proc_set{0}: #38 0x00002aaaadda1ac2 in PyEval_EvalCode at Python/ceval.c:667 proc_set{0}: #39 0x00002aaaaddb924c in PyImport_ExecCodeModuleEx at Python/import.c:709 proc_set{0}: #40 0x00002aaaaddb95ae in load_source_module at Python/import.c:1099 proc_set{0}: #41 0x00002aaaaddba9e9 in load_package at Python/import.c:1166 proc_set{0}: #42 0x00002aaaaddba4a9 in import_submodule at Python/import.c:2700 proc_set{0}: #43 0x00002aaaaddbb0e3 in load_next at Python/import.c:2515 proc_set{0}: #44 0x00002aaaaddbb0e3 in import_module_level at Python/import.c:2224 proc_set{0}: #45 0x00002aaaaddbb0e3 in PyImport_ImportModuleLevel at Python/import.c:2288 proc_set{0}: #46 0x00002aaaadd998cf in builtin___import__ at Python/bltinmodule.c:49 proc_set{0}: #47 0x00002aaaadceae93 in PyObject_Call at Objects/abstract.c:2529 proc_set{0}: #48 0x00002aaaadceafeb in call_function_tail at Objects/abstract.c:2561 proc_set{0}: #49 0x00002aaaadceafeb in PyObject_CallFunction at Objects/abstract.c:2585 proc_set{0}: #50 0x00002aaaaddbbeb2 in PyImport_Import at Python/import.c:2886 proc_set{0}: #51 0x00002aaaaddbc02a in PyImport_ImportModule at Python/import.c:2129 proc_set{0}: #52 0x0000000004766407 in vtkMatplotlibMathTextUtilities::CheckMPLAvailability at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Rendering/Matplotlib/vtkMatplotlibMathTextUtilities.cxx:75 proc_set{0}: #53 0x000000000476681a in vtkMatplotlibMathTextUtilities::New at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Rendering/Matplotlib/vtkMatplotlibMathTextUtilities.cxx:119 proc_set{0}: #54 0x000000000476abed in vtkObjectFactoryCreatevtkMatplotlibMathTextUtilities at /global/common/edison/graphics/ParaView/builds/PV-4.2.0/VTK/Rendering/Matplotlib/vtkRenderingMatplotlibObjectFactory.cxx:27 proc_set{0}: #55 0x0000000007336149 in vtkObjectFactory::CreateObject at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Common/Core/vtkObjectFactory.cxx:488 proc_set{0}: #56 0x0000000007334a8a in vtkObjectFactory::CreateInstance at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Common/Core/vtkObjectFactory.cxx:62 proc_set{0}: #57 0x0000000005a85a61 in vtkMathTextUtilities::GetInstance at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Rendering/FreeType/vtkMathTextUtilities.cxx:58 proc_set{0}: #58 0x0000000005a85566 in vtkMathTextFreeTypeTextRenderer::vtkMathTextFreeTypeTextRenderer at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Rendering/FreeType/vtkMathTextFreeTypeTextRenderer.cxx:489 proc_set{0}: #59 0x0000000005a81b35 in vtkMathTextFreeTypeTextRenderer::New at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Rendering/FreeType/vtkMathTextFreeTypeTextRenderer.cxx:26 proc_set{0}: #60 0x0000000005a8dc29 in vtkObjectFactoryCreatevtkMathTextFreeTypeTextRenderer at /global/common/edison/graphics/ParaView/builds/PV-4.2.0/VTK/Rendering/FreeType/vtkRenderingFreeTypeObjectFactory.cxx:27 proc_set{0}: #61 0x0000000007336149 in vtkObjectFactory::CreateObject at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Common/Core/vtkObjectFactory.cxx:488 proc_set{0}: #62 0x0000000007334a8a in vtkObjectFactory::CreateInstance at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Common/Core/vtkObjectFactory.cxx:62 proc_set{0}: #63 0x000000000601cec9 in vtkTextRenderer::GetInstance at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Rendering/Core/vtkTextRenderer.cxx:79 proc_set{0}: #64 0x0000000005a87f11 in vtkTextActor::vtkTextActor at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Rendering/FreeType/vtkTextActor.cxx:105 proc_set{0}: #65 0x0000000005a87a34 in vtkTextActor::New at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Rendering/FreeType/vtkTextActor.cxx:35 proc_set{0}: #66 0x000000000501535d in vtkTextRepresentation::vtkTextRepresentation at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Interaction/Widgets/vtkTextRepresentation.cxx:62 proc_set{0}: #67 0x00000000050152e0 in vtkTextRepresentation::New at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Interaction/Widgets/vtkTextRepresentation.cxx:54 proc_set{0}: #68 0x000000000386c735 in vtkNew::vtkNew at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Common/Core/vtkNew.h:66 proc_set{0}: #69 0x0000000003865225 in vtkPVRenderView::vtkPVRenderView at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:154 proc_set{0}: #70 0x0000000003864eac in vtkPVRenderView::New at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:140 proc_set{0}: #71 0x00000000032f9975 in vtkPVRenderViewClientServerNewCommand at /global/common/edison/graphics/ParaView/builds/PV-4.2.0/Wrapping/ClientServer/vtkPVRenderViewClientServer.cxx:13 proc_set{0}: #72 0x000000000474760f in vtkClientServerInterpreter::NewInstance at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:1068 proc_set{0}: #73 0x00000000036a1b80 in vtkSIProxy::CreateVTKObjects at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx:303 proc_set{0}: #74 0x00000000036a04cd in vtkSIProxy::Push at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx:112 proc_set{0}: #75 0x00000000036848bf in vtkPVSessionCore::PushStateInternal at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:486 proc_set{0}: #76 0x0000000003684b43 in vtkPVSessionCore::PushState at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:529 proc_set{0}: #77 0x0000000003681f69 in vtkPVSessionBase::PushState at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:142 proc_set{0}: #78 0x000000000368edf2 in vtkPVSessionServer::OnClientServerMessageRMI at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionServer.cxx:495 proc_set{0}: #79 0x000000000368d29c in at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionServer.cxx:56 proc_set{0}: #80 0x0000000004b0a589 in vtkMultiProcessController::ProcessRMI at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Parallel/Core/vtkMultiProcessController.cxx:774 proc_set{0}: #81 0x0000000004b0a145 in vtkMultiProcessController::ProcessRMIs at /global/common/edison/graphics/ParaView/builds/ParaView/VTK/Parallel/Core/vtkMultiProcessController.cxx:720 proc_set{0}: #82 0x00000000039c1f95 in vtkTCPNetworkAccessManager::ProcessEventsInternal at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx:268 proc_set{0}: #83 0x00000000039c1b32 in vtkTCPNetworkAccessManager::ProcessEvents at /global/common/edison/graphics/ParaView/builds/ParaView/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx:165 proc_set{0}: #84 0x0000000001e8c2e9 in RealMain at /global/common/edison/graphics/ParaView/builds/ParaView/CommandLineExecutables/pvserver_common.h:91 proc_set{0}: #85 0x0000000001e8c3b3 in main at /global/common/edison/graphics/ParaView/builds/ParaView/CommandLineExecutables/pvserver.cxx:27 From utkarsh.ayachit at kitware.com Fri Feb 6 14:14:19 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 6 Feb 2015 14:14:19 -0500 Subject: [Paraview] reducing startup time on cray In-Reply-To: <54D50E1D.4010202@lbl.gov> References: <54D50E1D.4010202@lbl.gov> Message-ID: > I think in the case of ParaView's matplotlib tex features the run time check > for matplotlib could probably be deferred until someone actually tries to > use tex. What do you think? This would help keep startup time fast. That makes total sense to me. From berk.geveci at kitware.com Fri Feb 6 15:19:25 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Fri, 6 Feb 2015 15:19:25 -0500 Subject: [Paraview] reducing startup time on cray In-Reply-To: References: <54D50E1D.4010202@lbl.gov> Message-ID: It makes sense to me too. Having said that, wouldn't it be better to go to the next step and use a frozen Python? If all of the commonly used Python modules are frozen to the build, loading them will become much faster. The solution that you are proposing only defers the cost to later. Given that we are depending on Python more and more, I'd like to see it be usable everywhere. Best, -berk On Fri, Feb 6, 2015 at 2:14 PM, Utkarsh Ayachit wrote: > > I think in the case of ParaView's matplotlib tex features the run time > check > > for matplotlib could probably be deferred until someone actually tries to > > use tex. What do you think? This would help keep startup time fast. > > That makes total sense to me. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 bloring at lbl.gov Fri Feb 6 16:34:16 2015 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 06 Feb 2015 13:34:16 -0800 Subject: [Paraview] reducing startup time on cray In-Reply-To: References: <54D50E1D.4010202@lbl.gov> Message-ID: <54D53358.5020209@lbl.gov> Utkarsh, Berk, > It makes sense to me too. Good, I will file a bug report so this doesn't get lost. > Having said that, wouldn't it be better to go to the next step and use > a frozen Python? Anything to improve the scalability of python would be huge and worth looking into. NERSC maintains python and thing like mpi4py, numpy, matplotlib, etc. They chose to add the later stuff externally to their base python install (maybe it doesn't matter). When I build ParaView I have those modules loaded and cmake finds things as it needs. When I run ParaView I load the modules to bring the right versions/components into the environment. I'm unfamiliar with freezing python and how it would work with pvserver, pvbatch, or pvpython. Question: how/what do we freeze in the pvserver case? Thanks Burlen On 02/06/2015 12:19 PM, Berk Geveci wrote: > It makes sense to me too. > > Having said that, wouldn't it be better to go to the next step and use > a frozen Python? If all of the commonly used Python modules are frozen > to the build, loading them will become much faster. The solution that > you are proposing only defers the cost to later. Given that we are > depending on Python more and more, I'd like to see it be usable > everywhere. > > Best, > -berk > > On Fri, Feb 6, 2015 at 2:14 PM, Utkarsh Ayachit > > wrote: > > > I think in the case of ParaView's matplotlib tex features the run time check > > for matplotlib could probably be deferred until someone actually > tries to > > use tex. What do you think? This would help keep startup time fast. > > That makes total sense to me. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 dave.demarle at kitware.com Fri Feb 6 17:34:35 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 6 Feb 2015 17:34:35 -0500 Subject: [Paraview] Memory use with Xdmf files In-Reply-To: References: Message-ID: Looks like ParaView doesn't know that it can treat these guys as images and give you the option of the Slice Representation. As such it has to do surface extraction (convert to unstructured) in order to show you the values. To demonstrate rid of all but one grid in your spatial collection and load that then look at memory inspector when you change to surface mode. Then take the spatial collection out to get the slice representation as an option. Not sure how to fix it without coding a bit. What you need to do is make sure it stays in structured format (as Felipe hinted at). I thought merge blocks would work, but that makes unstructured grids too. Sample to image data might work. You can probably use the python source hdf5 import path to do it directly. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Sun, Feb 1, 2015 at 4:32 AM, Felipe Bordeu Weldt < felipe.bordeu at ec-nantes.fr> wrote: > hi, > > I think the best way is to write only one cell (with the correct position > in the espace) for each picture and then apply each picture as a texture in > each cell. > For me this is the way to go. But technically I don?t know how to do it. > > Felipe > > Le 30 janv. 2015 ? 17:51, Michael Jackson a > ?crit : > > I have written an Xdmf file that uses the 3D CoRectMesh to display a > montage of 54 gray scale images. They are laid out in a 9x6 fashion. Each > Image is about 1292x968 pixels. We have run stitching algorithms on the > images to find their correct coordinates in XYZ space so that they will > form the montage correctly. > > The raw amount of memory is 67,535,424 bytes. If that has to be as RGBA > for rendering then it is 270,141,696 bytes. > > Then ParaView has to create a "cell" for each pixel and then some other > stuff. At one point ParaView spiked to 120GB of RAM and then fell back to > about 36GB of RAM. This seems a bit excessive to me. This is with ParaView > 4.3.1 on a Windows 8.1 workstation. Am I doing something wrong? Just seems > like a lot of memory. > > Are their alternate ways of writing the Xdmf file so that each image is a > single cell perhaps? > > Thanks for any insights. > > I can make the data set available to anyone who needs it. > _________________________________________________________ > Mike Jackson mike.jackson at bluequartz.net > BlueQuartz Software www.bluequartz.net > Principal Software Engineer Dayton, Ohio > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 cook47 at llnl.gov Fri Feb 6 19:23:24 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Sat, 7 Feb 2015 00:23:24 +0000 Subject: [Paraview] User trying to build with catalyst -- need guidance Message-ID: <356E8CE9-8210-41AC-BEB8-02773F9DD972@llnl.gov> Hello, We have not used catalyst here and I have a user that is interested in trying it out on our BG/Q machine with a huge code on hundreds of thousands of nodes. ;-) Is there a brave soul willing to hold our hands through this process? Thanks. -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Fri Feb 6 20:25:19 2015 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Fri, 6 Feb 2015 20:25:19 -0500 (EST) Subject: [Paraview] User trying to build with catalyst -- need guidance In-Reply-To: <356E8CE9-8210-41AC-BEB8-02773F9DD972@llnl.gov> Message-ID: <561709608.27732302.1423272319866.JavaMail.root@mail.gatech.edu> Hi Rich, There may be a few who are willing to help out if you can provide some specific questions or issues you run into. Have you looked through the documentation at http://www.paraview.org/in-situ/ ? I got Catalyst up and running in our code (not on a BG/Q but on different clusters) with the information in the documentation and by asking some specific questions here on the list. For me, the hardest part was converting our data into VTK data -- I did not have any exposure to VTK prior to taking the Catalyst leap. But it turned out to be (relatively) straight forward for what we are doing. I will be happy to answer things I can and for things I can't, hopefully somebody else will jump in. Tim ----- Original Message ----- From: "Rich Cook" To: paraview at paraview.org Sent: Friday, February 6, 2015 7:23:24 PM Subject: [Paraview] User trying to build with catalyst -- need guidance Hello, We have not used catalyst here and I have a user that is interested in trying it out on our BG/Q machine with a huge code on hundreds of thousands of nodes. ;-) Is there a brave soul willing to hold our hands through this process? Thanks. -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 dave.demarle at kitware.com Sat Feb 7 07:35:18 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Sat, 7 Feb 2015 07:35:18 -0500 Subject: [Paraview] User trying to build with catalyst -- need guidance In-Reply-To: <561709608.27732302.1423272319866.JavaMail.root@mail.gatech.edu> References: <356E8CE9-8210-41AC-BEB8-02773F9DD972@llnl.gov> <561709608.27732302.1423272319866.JavaMail.root@mail.gatech.edu> Message-ID: I've done the BGQ ParaView + Catalyst build and installs on Mira at ANL. I can chip in with tips regarding compilation. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Feb 6, 2015 at 8:25 PM, Tim Gallagher wrote: > Hi Rich, > > There may be a few who are willing to help out if you can provide some > specific questions or issues you run into. > > Have you looked through the documentation at > http://www.paraview.org/in-situ/ ? I got Catalyst up and running in our > code (not on a BG/Q but on different clusters) with the information in the > documentation and by asking some specific questions here on the list. For > me, the hardest part was converting our data into VTK data -- I did not > have any exposure to VTK prior to taking the Catalyst leap. But it turned > out to be (relatively) straight forward for what we are doing. > > I will be happy to answer things I can and for things I can't, hopefully > somebody else will jump in. > > Tim > > ------------------------------ > *From: *"Rich Cook" > *To: *paraview at paraview.org > *Sent: *Friday, February 6, 2015 7:23:24 PM > *Subject: *[Paraview] User trying to build with catalyst -- need guidance > > > Hello, > We have not used catalyst here and I have a user that is interested in > trying it out on our BG/Q machine with a huge code on hundreds of thousands > of nodes. ;-) > Is there a brave soul willing to hold our hands through this process? > Thanks. > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 303343023 at qq.com Sat Feb 7 09:39:10 2015 From: 303343023 at qq.com (=?gb18030?B?MzAzMzQzMDIz?=) Date: Sat, 7 Feb 2015 22:39:10 +0800 Subject: [Paraview] =?gb18030?b?u9i4tKO6ICBUcmFjayBtYXNzaXZlIHBhcnRpY2xl?= =?gb18030?q?s_over_time=2C_particle_ID_is_known?= In-Reply-To: References: Message-ID: Hi Thank you for your prompt reply. I have tried generate ids filter.However, the new generated id is changing every time step and it is hard for me to determine a threshhold.It is only at the beginning the particle I want to track locate all above z=0 plane. The python utility in paraview seems to be very powerful. I now try to seek solution from it. It will be very appreciated if you have new ideas about this topic. Chenshu ------------------ ???? ------------------ ???: "timcfagan .";; ????: 2015?2?6?(???) ??7:46 ???: ""<303343023 at qq.com>; ??: "paraview"; ??: Re: [Paraview] Track massive particles over time, particle ID is known I've tried to do the same thing Chenshu, this is how I ended up doing it: open vtk particle file generate ids (possibly apply it even if they already have ids) extract entire dataset with particles through threshold by generated ids for the particles you want (This can be done multiple times to select multiple sets of points, then append datasets to combine them to one) Temporal particles to pathlines Unfortunately I haven't found a better way to actually select the particles other than through selecting them by particle ids. Just extracting a selection doesn't work properly with the pathlines filter. But you can extract a selection and view their ids in spreadsheet form. I was doing this, writing it down and then applying the threshold. Also the generate id's filter was applying them in layers in z, so you may find thresholding for z>0 is easy as it might be one threshold in the id's. You just need to find the right id number. Maybe someone knows a better way though... On Fri, Feb 6, 2015 at 1:17 AM, 303343023 <303343023 at qq.com> wrote: Hi everyone It troubles me for times. I have a series of particles vtk files at different time step. And I want to track certain particles and extract them or color them with a uniform color. I tried to use "find data" and include the particle id with "is one of " option. However, it crashed due to overload of compute capacity. About 8 thousand particles is intended for tracking. Furthermore, at the begining, the particles of interest located at the upper layer, coordinatesZ>0, for example. And I want to extract them from the whole. Could any one help me? Thanks in advance! Chenshu Hu _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 timcfagan at gmail.com Sat Feb 7 22:59:55 2015 From: timcfagan at gmail.com (timcfagan .) Date: Sun, 8 Feb 2015 14:59:55 +1100 Subject: [Paraview] Track massive particles over time, particle ID is known In-Reply-To: References: Message-ID: It seems strange that it's changing... The particles should move around but their ID should remain the same. At least that's what I've found with the vtk particle data I've used. If you're still stuck you I'd be happy to have a look at a sample of your data and see if I can get it to work... I haven't used the python utility actually so I can't help with that. On Sun, Feb 8, 2015 at 1:39 AM, 303343023 <303343023 at qq.com> wrote: > *Hi* > *Thank you for your prompt reply.* > *I have tried generate ids filter.However, the new generated id is > changing every time step and it is hard for me to determine a threshhold.It > is only at the beginning the particle I want to track locate all above z=0 > plane.* > *The python utility in paraview seems to be very powerful. I now try to > seek solution from it. It will be very appreciated if you have new ideas > about this topic.* > *Chenshu* > > > ------------------ ???? ------------------ > *???:* "timcfagan .";; > *????:* 2015?2?6?(???) ??7:46 > *???:* ""<303343023 at qq.com>; > *??:* "paraview"; > *??:* Re: [Paraview] Track massive particles over time, particle ID is > known > > I've tried to do the same thing Chenshu, this is how I ended up doing it: > > open vtk particle file > generate ids (possibly apply it even if they already have ids) > extract entire dataset with particles through > threshold by generated ids for the particles you want > (This can be done multiple times to select multiple sets of points, then > append datasets to combine them to one) > Temporal particles to pathlines > > Unfortunately I haven't found a better way to actually select the > particles other than through selecting them by particle ids. Just > extracting a selection doesn't work properly with the pathlines filter. But > you can extract a selection and view their ids in spreadsheet form. I was > doing this, writing it down and then applying the threshold. Also the > generate id's filter was applying them in layers in z, so you may find > thresholding for z>0 is easy as it might be one threshold in the id's. You > just need to find the right id number. > > Maybe someone knows a better way though... > > On Fri, Feb 6, 2015 at 1:17 AM, 303343023 <303343023 at qq.com> wrote: > >> *Hi everyone* >> * It troubles me for times. * >> * I have a series of particles vtk files at different time step. And I >> want to track certain particles and extract them or color them with a >> uniform color. I tried to use "find data" and include the particle id with >> "is one of " option. However, it crashed due to overload of compute >> capacity. About 8 thousand particles is intended for tracking.* >> * Furthermore, at the begining, the particles of interest located at >> the upper layer, coordinatesZ>0, for example. And I want to extract them >> from the whole.* >> * Could any one help me? Thanks in advance!* >> >> Chenshu Hu >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Sun Feb 8 08:03:28 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Sun, 8 Feb 2015 08:03:28 -0500 Subject: [Paraview] User trying to build with catalyst -- need guidance In-Reply-To: References: <356E8CE9-8210-41AC-BEB8-02773F9DD972@llnl.gov> <561709608.27732302.1423272319866.JavaMail.root@mail.gatech.edu> Message-ID: Hi Rich, Where are you currently with this? Have you done any code integration with Catalyst yet? There's certainly a good distributed knowledge base that's getting built up. A bit more information about the simulation code characteristics would help in making sure the adaptor section design is sound. Regards, Andy On Sat, Feb 7, 2015 at 7:35 AM, David E DeMarle wrote: > I've done the BGQ ParaView + Catalyst build and installs on Mira at ANL. > > I can chip in with tips regarding compilation. > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Fri, Feb 6, 2015 at 8:25 PM, Tim Gallagher > wrote: > >> Hi Rich, >> >> There may be a few who are willing to help out if you can provide some >> specific questions or issues you run into. >> >> Have you looked through the documentation at >> http://www.paraview.org/in-situ/ ? I got Catalyst up and running in our >> code (not on a BG/Q but on different clusters) with the information in the >> documentation and by asking some specific questions here on the list. For >> me, the hardest part was converting our data into VTK data -- I did not >> have any exposure to VTK prior to taking the Catalyst leap. But it turned >> out to be (relatively) straight forward for what we are doing. >> >> I will be happy to answer things I can and for things I can't, hopefully >> somebody else will jump in. >> >> Tim >> >> ------------------------------ >> *From: *"Rich Cook" >> *To: *paraview at paraview.org >> *Sent: *Friday, February 6, 2015 7:23:24 PM >> *Subject: *[Paraview] User trying to build with catalyst -- need guidance >> >> >> Hello, >> We have not used catalyst here and I have a user that is interested in >> trying it out on our BG/Q machine with a huge code on hundreds of thousands >> of nodes. ;-) >> Is there a brave soul willing to hold our hands through this process? >> Thanks. >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA >> ? (office) (925) 423-9605 >> ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., >> Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 hfklinac at hotmail.com Sun Feb 8 21:50:46 2015 From: hfklinac at hotmail.com (Hannah Klinac) Date: Mon, 9 Feb 2015 10:50:46 +0800 Subject: [Paraview] Paraview enabled VR Plugin not interacting via VRPN In-Reply-To: References: , Message-ID: Hi, This is my process: Start Paraview serverStart VRPN serverStart Paraview clientAdd an object (box)Add VRPN connection in the VR PanelAdd VRPN interaction in the VR PanelPress "start" Is there anything I am missing?Elsewise I can give more information about my VRPN, however I'm assuming I'm doing something wrong/missing something with the Paraview setup. I have saved the project and VR state files and attached them. I am using Paraview 4.3.1 (32bit) on Windows 7 (64bit). Thanks for your help,Hannah Date: Wed, 4 Feb 2015 11:11:10 -0500 Subject: Re: [Paraview] Paraview enabled VR Plugin not interacting via VRPN From: aashish.chaudhary at kitware.com To: hfklinac at hotmail.com CC: paraview at paraview.org Hi Hannah, On Wed, Feb 4, 2015 at 3:36 AM, Hannah Klinac wrote: Hi, I recently compiled Paraview from the source code to enable the VR Plugin. I have built VRPN, and compiled Paraview using that VRPN's dependencies. However, when I add the connection and interaction in the VR Plugin in Paraview and press "Start", when I (for example) press the button I have registered down, the interaction doesn't happen. And on my server it says: "vrpn: Connection requiest received from 'IP address': 'IP address' 'Port'Get a new connection, reset virtual_Tracker" Is it possible for you to share the VR state file? Or provide information on how you setup the VRPN server in the first place? Seems like a configuration issue. Also, helpful to know the version of ParaView and the OS you are using? Any idea if I have just not setup my connection/interaction correctly in Paraview? The VRPN server works fine for other applications such as Vizard. Thanks, Thanks in advance for any guidance,Hannah _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: teststate.pvsm Type: application/octet-stream Size: 105675 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: testvrstate.pvvr Type: application/octet-stream Size: 608 bytes Desc: not available URL: From samuel.braun at kit.edu Mon Feb 9 02:46:24 2015 From: samuel.braun at kit.edu (Braun, Samuel (ITS)) Date: Mon, 9 Feb 2015 08:46:24 +0100 Subject: [Paraview] Visualize step attributes for H5PART (HDF5) Message-ID: <54D865D0.7070905@kit.edu> Hello everybody, I would like to know if there are any new suggestions concerning this topic (posted from Arno Mayrhofer arno.m at gmx.at; Wed Aug 10 09:34:17 EDT 2011) /"Hi all,// // //I am using the H5PART library to write my SPH data. Now besides particle // //values like pressure I also have one step attribute (which is the physical // //time). My question is quite simple, how can I extract this data in // //ParaView? Ideally I would use it in a similar fashion as the annotate time // //filter. Unfortunately I couldn't find any instruction by searching the web.// // //Thanks in advance,// //Arno//"/ Thank you, Samuel -- Karlsruher Institut f?r Technologie (KIT) Institut f?r Thermische Str?mungsmaschinen Dipl.-Ing. Samuel Braun Kaiserstra?e 12 Geb?ude 10.91 76131 Karlsruhe Telefon: +49 721 608-44183 Fax: +49 721 608-42767 E-Mail: samuel.braun at kit edu PGP-Key ID 0xB8F2DAD7 Web: http://www.kit.edu/ KIT ? Universit?t des Landes Baden-W?rttemberg und nationales Forschungszentrum in der Helmholtz-Gemeinschaft o _ _ _ --------- __o __o /\_ _ \\o (_)\__/o (_) ------- _`\<,_ _`\<,_ _>(_) (_)/<_ \_| \ _|/' \/ ------ (_)/ (_) (_)/ (_) (_) (_) (_) (_)' _\o_ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Es gibt 10 Arten von Menschen. Jene, die Bin?rcode verstehen, und jene, die ihn nicht verstehen. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Mon Feb 9 09:17:28 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 9 Feb 2015 09:17:28 -0500 Subject: [Paraview] Paraview enabled VR Plugin not interacting via VRPN In-Reply-To: References: Message-ID: Hannah, Thanks for sending the files. Couple of thigs: 1) Is this really a valid VRPN server Mouse0 at localhost? Can you use vrpn_print_devices program to communicate with it? 2) Looks like you the property you configured is visibility but the style you have chosen is vtkVRGrabWorldStyle which requires tracker or otherwise it won't do anything. Can you describe it in bit more detail on what exactly you are trying to achieve? What hardware you have? - Aashish On Sun, Feb 8, 2015 at 9:50 PM, Hannah Klinac wrote: > Hi, > > This is my process: > > > 1. Start Paraview server > 2. Start VRPN server > 3. Start Paraview client > 1. Add an object (box) > 2. Add VRPN connection in the VR Panel > 3. Add VRPN interaction in the VR Panel > 4. Press "start" > > > Is there anything I am missing? > Elsewise I can give more information about my VRPN, however I'm assuming > I'm doing something wrong/missing something with the Paraview setup. > > I have saved the project and VR state files and attached them. > > I am using Paraview 4.3.1 (32bit) on Windows 7 (64bit). > > Thanks for your help, > Hannah > > ------------------------------ > Date: Wed, 4 Feb 2015 11:11:10 -0500 > Subject: Re: [Paraview] Paraview enabled VR Plugin not interacting via VRPN > From: aashish.chaudhary at kitware.com > To: hfklinac at hotmail.com > CC: paraview at paraview.org > > > Hi Hannah, > > On Wed, Feb 4, 2015 at 3:36 AM, Hannah Klinac > wrote: > > Hi, > > I recently compiled Paraview from the source code to enable the VR Plugin. > > I have built VRPN, and compiled Paraview using that VRPN's dependencies. > > However, when I add the connection and interaction in the VR Plugin in > Paraview and press "Start", when I (for example) press the button I have > registered down, the interaction doesn't happen. And on my server it says: > > "vrpn: Connection requiest received from 'IP address': 'IP address' 'Port' > Get a new connection, reset virtual_Tracker" > > > Is it possible for you to share the VR state file? Or provide information > on how you setup the VRPN server in the first place? Seems like a > configuration issue. Also, helpful to know the version of ParaView and the > OS you are using? > > > > Any idea if I have just not setup my connection/interaction correctly in > Paraview? The VRPN server works fine for other applications such as Vizard. > > > Thanks, > > > > Thanks in advance for any guidance, > Hannah > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. * > *| http://www.kitware.com/company/team/chaudhary.html > * > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anton.Piccardo-Selg at tessella.com Mon Feb 9 09:58:00 2015 From: Anton.Piccardo-Selg at tessella.com (Anton.Piccardo-Selg at tessella.com) Date: Mon, 9 Feb 2015 14:58:00 +0000 Subject: [Paraview] Set of 3DText sources? Message-ID: An HTML attachment was scrubbed... URL: From i.krukow at tu-braunschweig.de Mon Feb 9 10:58:34 2015 From: i.krukow at tu-braunschweig.de (Ian Krukow) Date: Mon, 09 Feb 2015 16:58:34 +0100 Subject: [Paraview] Run a paraview-phyton scricpt in a windows batch file In-Reply-To: References: <54D231DA.2070505@inria.fr> Message-ID: <54D8D92A.20500@tu-braunschweig.de> Hi Madalena, are you using python or pvpython? 'Normal' python does not know where to locate the ParaView libraries. Therefore, you should use pvpython from the ParaView package, unless you have a special reason to do otherwise (then you have to set up your system accordingly). Kind regards Ian Am 04.02.2015 um 16:00 schrieb Madalena S. Malhadas: > > I try to run a paraview-phyton script in a batch file in windows but i > get this error: > > > C:\Users\madalenasantos\Desktop\Paraview>py Cone.py > Traceback (most recent call last): > File "Cone.py", line 2, in > from paraview.simple import * > ImportError: No module named 'paraview' > > C:\Users\madalenasantos\Desktop\Paraview>Pause > Press any key to continue . . . > > > Can any one could help me? > > Kind regards > Madalena > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 nenasantos at hotmail.com Mon Feb 9 11:02:09 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Mon, 9 Feb 2015 16:02:09 +0000 Subject: [Paraview] Run a paraview-phyton scricpt in a windows batch file In-Reply-To: <54D8D92A.20500@tu-braunschweig.de> References: <54D231DA.2070505@inria.fr> , <54D8D92A.20500@tu-braunschweig.de> Message-ID: Hello,I am using python but now I am testing with pvpython and works! Kind regardsMadalena > Date: Mon, 9 Feb 2015 16:58:34 +0100 > From: i.krukow at tu-braunschweig.de > To: nenasantos at hotmail.com; paraview at paraview.org > Subject: Re: [Paraview] Run a paraview-phyton scricpt in a windows batch file > > Hi Madalena, > > are you using python or pvpython? 'Normal' python does not know where to > locate the ParaView libraries. Therefore, you should use pvpython from > the ParaView package, unless you have a special reason to do otherwise > (then you have to set up your system accordingly). > > Kind regards > Ian > > > > Am 04.02.2015 um 16:00 schrieb Madalena S. Malhadas: > > > > I try to run a paraview-phyton script in a batch file in windows but i > > get this error: > > > > > > C:\Users\madalenasantos\Desktop\Paraview>py Cone.py > > Traceback (most recent call last): > > File "Cone.py", line 2, in > > from paraview.simple import * > > ImportError: No module named 'paraview' > > > > C:\Users\madalenasantos\Desktop\Paraview>Pause > > Press any key to continue . . . > > > > > > Can any one could help me? > > > > Kind regards > > Madalena > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > > > 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.d.rinehart at nasa.gov Mon Feb 9 10:51:43 2015 From: richard.d.rinehart at nasa.gov (Rinehart, Richard D. (GRC-VG00)[DB Consulting Group, Inc.]) Date: Mon, 9 Feb 2015 15:51:43 +0000 Subject: [Paraview] Defining new Variables Message-ID: <49F2A13558976D41882241B8CCCCF51B0F4116FE@NDJSMBX203.ndc.nasa.gov> Greetings! A relative newbie Paraview question[http://www.cfd-online.com/Forums/images/smilies/smile.gif]. In Ensight I use the calculator to define essentially a new variable, such as degrees F as computed from K. I've done that in Paraview but it doesn't seem to then be available to use. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1061 bytes Desc: image001.gif URL: From utkarsh.ayachit at kitware.com Mon Feb 9 11:25:50 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 9 Feb 2015 11:25:50 -0500 Subject: [Paraview] Defining new Variables In-Reply-To: <49F2A13558976D41882241B8CCCCF51B0F4116FE@NDJSMBX203.ndc.nasa.gov> References: <49F2A13558976D41882241B8CCCCF51B0F4116FE@NDJSMBX203.ndc.nasa.gov> Message-ID: Try using the Calculator filter. Also checkout Section 5.8 from the ParaView Guide. You can download the pdf version from http://www.paraview.org/documentation/ Utkarsh On Mon, Feb 9, 2015 at 10:51 AM, Rinehart, Richard D. (GRC-VG00)[DB Consulting Group, Inc.] wrote: > Greetings! > > A relative newbie Paraview question[image: > http://www.cfd-online.com/Forums/images/smilies/smile.gif]. In Ensight I > use the calculator to define essentially a new variable, such as degrees F > as computed from K. I've done that in Paraview but it doesn't seem to then > be available to use. ? > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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: image001.gif Type: image/gif Size: 1061 bytes Desc: not available URL: From kmorel at sandia.gov Mon Feb 9 12:06:09 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 9 Feb 2015 17:06:09 +0000 Subject: [Paraview] Defining new Variables Message-ID: Richard, Did you click the "Apply" button after entering the expression in the calculator filter? After you click the Apply button ParaView will evaluate your expression on all elements of your data. The new variable becomes part of the newly generated data set labeled as "Calculator1" or something similar in the pipeline browser (at the left of the GUI). The variable is available when showing that data in the view or adding subsequent filters to that. If this talk of filters is confusing, I suggest taking a look at the ParaView tutorial (http://www.paraview.org/Wiki/The_ParaView_Tutorial) and/or the ParaView guide as Utkarsh suggested earlier to learn the fundamental concepts of ParaView. -Ken From: , "Inc.]" > Date: Monday, February 9, 2015 at 8:51 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Defining new Variables Greetings! A relative newbie Paraview question[http://www.cfd-online.com/Forums/images/smilies/smile.gif]. In Ensight I use the calculator to define essentially a new variable, such as degrees F as computed from K. I've done that in Paraview but it doesn't seem to then be available to use. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1061 bytes Desc: image001.gif URL: From nenasantos at hotmail.com Mon Feb 9 12:38:55 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Mon, 9 Feb 2015 17:38:55 +0000 Subject: [Paraview] Set fill_value (e.g., -9e15) with transparency color In-Reply-To: References: Message-ID: Dear all,I try to represent a 3D clarifier with total suspended solids as property. My geometry have a fill value with -9e15 that appears on the bord of the structure. What i have to set a transparency color for fill value? kind regardsMadalena From: kmorel at sandia.gov To: richard.d.rinehart at nasa.gov; paraview at paraview.org Date: Mon, 9 Feb 2015 17:06:09 +0000 Subject: Re: [Paraview] Defining new Variables Richard, Did you click the "Apply" button after entering the expression in the calculator filter? After you click the Apply button ParaView will evaluate your expression on all elements of your data. The new variable becomes part of the newly generated data set labeled as "Calculator1" or something similar in the pipeline browser (at the left of the GUI). The variable is available when showing that data in the view or adding subsequent filters to that. If this talk of filters is confusing, I suggest taking a look at the ParaView tutorial (http://www.paraview.org/Wiki/The_ParaView_Tutorial) and/or the ParaView guide as Utkarsh suggested earlier to learn the fundamental concepts of ParaView. -Ken From: , "Inc.]" Date: Monday, February 9, 2015 at 8:51 AM To: "paraview at paraview.org" Subject: [EXTERNAL] [Paraview] Defining new Variables Greetings! A relative newbie Paraview question. In Ensight I use the calculator to define essentially a new variable, such as degrees F as computed from K. I've done that in Paraview but it doesn't seem to then be available to use. ? _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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: image001.gif Type: image/gif Size: 1061 bytes Desc: not available URL: From richard.d.rinehart at nasa.gov Mon Feb 9 12:50:26 2015 From: richard.d.rinehart at nasa.gov (Rinehart, Richard D. (GRC-VG00)[DB Consulting Group, Inc.]) Date: Mon, 9 Feb 2015 17:50:26 +0000 Subject: [Paraview] Defining new Variables In-Reply-To: References: Message-ID: <49F2A13558976D41882241B8CCCCF51B0F411A27@NDJSMBX203.ndc.nasa.gov> Thanks! Ahh.... Filters. But the variable did not seem available for use by subsequent filters after the filter application. That's confusing me. But I'll try again. -rich From: Moreland, Kenneth [mailto:kmorel at sandia.gov] Sent: Monday, February 09, 2015 12:06 PM To: Rinehart, Richard D. (GRC-VG00)[DB Consulting Group, Inc.]; paraview at paraview.org Subject: Re: [Paraview] Defining new Variables Richard, Did you click the "Apply" button after entering the expression in the calculator filter? After you click the Apply button ParaView will evaluate your expression on all elements of your data. The new variable becomes part of the newly generated data set labeled as "Calculator1" or something similar in the pipeline browser (at the left of the GUI). The variable is available when showing that data in the view or adding subsequent filters to that. If this talk of filters is confusing, I suggest taking a look at the ParaView tutorial (http://www.paraview.org/Wiki/The_ParaView_Tutorial) and/or the ParaView guide as Utkarsh suggested earlier to learn the fundamental concepts of ParaView. -Ken From: , "Inc.]" > Date: Monday, February 9, 2015 at 8:51 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Defining new Variables Greetings! A relative newbie Paraview question[http://www.cfd-online.com/Forums/images/smilies/smile.gif]. In Ensight I use the calculator to define essentially a new variable, such as degrees F as computed from K. I've done that in Paraview but it doesn't seem to then be available to use. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1061 bytes Desc: image001.gif URL: From kmorel at sandia.gov Mon Feb 9 12:54:39 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 9 Feb 2015 17:54:39 +0000 Subject: [Paraview] Defining new Variables Message-ID: The variable should be available for use by subsequent filters. I've never had a problem with that. Perhaps the calculator was not giving the variable the name you were expecting? (The default name is "Result".) -Ken From: , "Inc.]" > Date: Monday, February 9, 2015 at 10:50 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] Re: [Paraview] Defining new Variables Thanks! Ahh.... Filters. But the variable did not seem available for use by subsequent filters after the filter application. That's confusing me. But I'll try again. -rich From: Moreland, Kenneth [mailto:kmorel at sandia.gov] Sent: Monday, February 09, 2015 12:06 PM To: Rinehart, Richard D. (GRC-VG00)[DB Consulting Group, Inc.]; paraview at paraview.org Subject: Re: [Paraview] Defining new Variables Richard, Did you click the "Apply" button after entering the expression in the calculator filter? After you click the Apply button ParaView will evaluate your expression on all elements of your data. The new variable becomes part of the newly generated data set labeled as "Calculator1" or something similar in the pipeline browser (at the left of the GUI). The variable is available when showing that data in the view or adding subsequent filters to that. If this talk of filters is confusing, I suggest taking a look at the ParaView tutorial (http://www.paraview.org/Wiki/The_ParaView_Tutorial) and/or the ParaView guide as Utkarsh suggested earlier to learn the fundamental concepts of ParaView. -Ken From: , "Inc.]" > Date: Monday, February 9, 2015 at 8:51 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Defining new Variables Greetings! A relative newbie Paraview question[http://www.cfd-online.com/Forums/images/smilies/smile.gif]. In Ensight I use the calculator to define essentially a new variable, such as degrees F as computed from K. I've done that in Paraview but it doesn't seem to then be available to use. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1061 bytes Desc: image001.gif URL: From mickey.phy at gmail.com Mon Feb 9 13:35:33 2015 From: mickey.phy at gmail.com (Mickael Philit) Date: Mon, 09 Feb 2015 19:35:33 +0100 Subject: [Paraview] cgns - Paraview loader In-Reply-To: <54D8C198.50708@swl.rwth-aachen.de> References: <547EE70B.504@swl.rwth-aachen.de> <547F52B0.8050900@gmail.com> <54D8C198.50708@swl.rwth-aachen.de> Message-ID: <54D8FDF5.1040903@gmail.com> The CGNS plugin is not present in nighty builds. You may have an unrelated problem. Have you check your cgns file with the /cgnscheck/ utility ? Can you provide more information about the error output from ParaView ? Mickael On 09/02/2015 15:18, Manuel Gageik wrote: > Hi Mickael, > > I downloaded the nightly build > "ParaView-Linux-64bit-glibc-2.3.6-NIGHTLY.tar.gz" since it is not easy > for me to compile paraview on my computer. This build causes error > while loading cgns-files. Do you have any recent informations about > the status of the implementation of your patch to paraview? > > Kind regards > Manuel > > > Am 03.12.2014 um 19:13 schrieb Mickael Philit: >> Hello, >> >> right now there is no binary available. >> The plugin is in the master development branch of Paraview. Thus, the >> plugin should be released in the next ParaView but I am not sure >> that it will be there by default (You should ask on the ParaView user >> mainling list for confirmation by kitware guys). >> So, if you really need it now, your best option is to download >> ParaView sources through git and compile your own ParaView binary. >> >> Regards >> >> Mickael >> >> >> >> >> On 03/12/2014 11:33, Dipl.-Ing. Manuel Gageik wrote: >>> Hello, >>> >>> I have read in the forum "Paraview-developers" that you have develeoped >>> a ParaView reader for CGNS file format. I am very interested in it >>> since >>> I have large cgns-files to load. How do I get this plugin? Do you >>> have a >>> binary to download. Will it be released in ParaView 4.3 ? >>> >>> Kind regards >>> Manuel Gageik >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Mon Feb 9 14:14:09 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Mon, 9 Feb 2015 19:14:09 +0000 Subject: [Paraview] User trying to build with catalyst -- need guidance In-Reply-To: <6240FEA4-E498-4607-BE50-6EA4C1A300A1@llnl.gov> References: <696276497.27732258.1423272306498.JavaMail.root@mail.gatech.edu> <6240FEA4-E498-4607-BE50-6EA4C1A300A1@llnl.gov> Message-ID: <7FD9297C-87AE-4838-BB9F-070975DBFF2A@llnl.gov> Hello, Another very specific question: The instructions at http://www.paraview.org/Wiki/Build_Directions use cmake of course. How is this going to work in building a library intended to run on the backend nodes of BG/Q machines? Thanks. On Feb 9, 2015, at 9:49 AM, Cook, Rich > wrote: Thanks, I?ll follow your approach of using the mailing list and asking specific questions. My current question is this: which of these should I download? Since this is for a BG/Q machine, I believe I?m going to have to do a cross-compile. Thanks ? Rich On Feb 6, 2015, at 5:25 PM, Tim Gallagher > wrote: Hi Rich, There may be a few who are willing to help out if you can provide some specific questions or issues you run into. Have you looked through the documentation at http://www.paraview.org/in-situ/ ? I got Catalyst up and running in our code (not on a BG/Q but on different clusters) with the information in the documentation and by asking some specific questions here on the list. For me, the hardest part was converting our data into VTK data -- I did not have any exposure to VTK prior to taking the Catalyst leap. But it turned out to be (relatively) straight forward for what we are doing. I will be happy to answer things I can and for things I can't, hopefully somebody else will jump in. Tim ________________________________ From: "Rich Cook" > To: paraview at paraview.org Sent: Friday, February 6, 2015 7:23:24 PM Subject: [Paraview] User trying to build with catalyst -- need guidance Hello, We have not used catalyst here and I have a user that is interested in trying it out on our BG/Q machine with a huge code on hundreds of thousands of nodes. ;-) Is there a brave soul willing to hold our hands through this process? Thanks. -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Mon Feb 9 14:14:03 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Mon, 9 Feb 2015 19:14:03 +0000 Subject: [Paraview] User trying to build with catalyst -- need guidance In-Reply-To: <696276497.27732258.1423272306498.JavaMail.root@mail.gatech.edu> References: <696276497.27732258.1423272306498.JavaMail.root@mail.gatech.edu> Message-ID: <7CA71728-8DAE-47F2-B03D-D1B0E786163C@llnl.gov> Thanks, Tim, I?ll follow your approach of using the mailing list and asking specific questions. My current question is this: which of these should I download? [cid:D164A5EC-3645-415C-910E-BEB1C06A0600 at llnl.gov] Since this is for a BG/Q machine, I believe I?m going to have to do a cross-compile. Thanks ? Rich On Feb 6, 2015, at 5:25 PM, Tim Gallagher > wrote: Hi Rich, There may be a few who are willing to help out if you can provide some specific questions or issues you run into. Have you looked through the documentation at http://www.paraview.org/in-situ/ ? I got Catalyst up and running in our code (not on a BG/Q but on different clusters) with the information in the documentation and by asking some specific questions here on the list. For me, the hardest part was converting our data into VTK data -- I did not have any exposure to VTK prior to taking the Catalyst leap. But it turned out to be (relatively) straight forward for what we are doing. I will be happy to answer things I can and for things I can't, hopefully somebody else will jump in. Tim ________________________________ From: "Rich Cook" > To: paraview at paraview.org Sent: Friday, February 6, 2015 7:23:24 PM Subject: [Paraview] User trying to build with catalyst -- need guidance Hello, We have not used catalyst here and I have a user that is interested in trying it out on our BG/Q machine with a huge code on hundreds of thousands of nodes. ;-) Is there a brave soul willing to hold our hands through this process? Thanks. -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-5.png Type: image/png Size: 67461 bytes Desc: PastedGraphic-5.png URL: From dave.demarle at kitware.com Mon Feb 9 14:38:44 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 9 Feb 2015 14:38:44 -0500 Subject: [Paraview] Defining new Variables In-Reply-To: References: Message-ID: And make sure the subsequent filters start from the calculator filter, otherwise they, just like the calculator itself, will take in the output of the upstream source. (i.e. you've made a branching fan out pipeline) David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Feb 9, 2015 at 12:54 PM, Moreland, Kenneth wrote: > The variable should be available for use by subsequent filters. I've > never had a problem with that. Perhaps the calculator was not giving the > variable the name you were expecting? (The default name is "Result".) > > -Ken > > From: , "Inc.]" > Date: Monday, February 9, 2015 at 10:50 AM > To: "paraview at paraview.org" > Subject: [EXTERNAL] Re: [Paraview] Defining new Variables > > Thanks! Ahh?. Filters. But the variable did not seem available for > use by subsequent filters after the filter application. That?s confusing > me. But I?ll try again. > > -rich > > > > > > *From:* Moreland, Kenneth [mailto:kmorel at sandia.gov ] > *Sent:* Monday, February 09, 2015 12:06 PM > *To:* Rinehart, Richard D. (GRC-VG00)[DB Consulting Group, Inc.]; > paraview at paraview.org > *Subject:* Re: [Paraview] Defining new Variables > > > > Richard, > > > > Did you click the "Apply" button after entering the expression in the > calculator filter? After you click the Apply button ParaView will evaluate > your expression on all elements of your data. > > > > The new variable becomes part of the newly generated data set labeled as > "Calculator1" or something similar in the pipeline browser (at the left of > the GUI). The variable is available when showing that data in the view or > adding subsequent filters to that. > > > > If this talk of filters is confusing, I suggest taking a look at the > ParaView tutorial (http://www.paraview.org/Wiki/The_ParaView_Tutorial) > and/or the ParaView guide as Utkarsh suggested earlier to learn the > fundamental concepts of ParaView. > > > > -Ken > > > > *From: *, "Inc.]" > *Date: *Monday, February 9, 2015 at 8:51 AM > *To: *"paraview at paraview.org" > *Subject: *[EXTERNAL] [Paraview] Defining new Variables > > > > Greetings! > > A relative newbie Paraview question[image: > http://www.cfd-online.com/Forums/images/smilies/smile.gif]. In Ensight I > use the calculator to define essentially a new variable, such as degrees F > as computed from K. I've done that in Paraview but it doesn't seem to then > be available to use. ? > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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: image001.gif Type: image/gif Size: 1061 bytes Desc: not available URL: From richard.d.rinehart at nasa.gov Mon Feb 9 14:45:44 2015 From: richard.d.rinehart at nasa.gov (Rinehart, Richard D. (GRC-VG00)[DB Consulting Group, Inc.]) Date: Mon, 9 Feb 2015 19:45:44 +0000 Subject: [Paraview] Defining new Variables In-Reply-To: References: Message-ID: <49F2A13558976D41882241B8CCCCF51B0F411CD8@NDJSMBX203.ndc.nasa.gov> Thanks all, I have gotten it to work. And it does like I expect. In my early excursions using Paraview, it?s totally possible to do things that doesn?t crash it but otherwise hoses up subsequent downstream movements. I don?t say that to complain as it?s quite amazing for opensource and perhaps it?s mostly user error. It?s just wise sometimes to exit and reload I find ? -rich From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Monday, February 09, 2015 2:39 PM To: Moreland, Kenneth Cc: Rinehart, Richard D. (GRC-VG00)[DB Consulting Group, Inc.]; paraview at paraview.org Subject: Re: [Paraview] Defining new Variables And make sure the subsequent filters start from the calculator filter, otherwise they, just like the calculator itself, will take in the output of the upstream source. (i.e. you've made a branching fan out pipeline) David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Feb 9, 2015 at 12:54 PM, Moreland, Kenneth > wrote: The variable should be available for use by subsequent filters. I've never had a problem with that. Perhaps the calculator was not giving the variable the name you were expecting? (The default name is "Result".) -Ken From: , "Inc.]" > Date: Monday, February 9, 2015 at 10:50 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] Re: [Paraview] Defining new Variables Thanks! Ahh?. Filters. But the variable did not seem available for use by subsequent filters after the filter application. That?s confusing me. But I?ll try again. -rich From: Moreland, Kenneth [mailto:kmorel at sandia.gov] Sent: Monday, February 09, 2015 12:06 PM To: Rinehart, Richard D. (GRC-VG00)[DB Consulting Group, Inc.]; paraview at paraview.org Subject: Re: [Paraview] Defining new Variables Richard, Did you click the "Apply" button after entering the expression in the calculator filter? After you click the Apply button ParaView will evaluate your expression on all elements of your data. The new variable becomes part of the newly generated data set labeled as "Calculator1" or something similar in the pipeline browser (at the left of the GUI). The variable is available when showing that data in the view or adding subsequent filters to that. If this talk of filters is confusing, I suggest taking a look at the ParaView tutorial (http://www.paraview.org/Wiki/The_ParaView_Tutorial) and/or the ParaView guide as Utkarsh suggested earlier to learn the fundamental concepts of ParaView. -Ken From: , "Inc.]" > Date: Monday, February 9, 2015 at 8:51 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Defining new Variables Greetings! A relative newbie Paraview question[http://www.cfd-online.com/Forums/images/smilies/smile.gif]. In Ensight I use the calculator to define essentially a new variable, such as degrees F as computed from K. I've done that in Paraview but it doesn't seem to then be available to use. ? _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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: image001.gif Type: image/gif Size: 1061 bytes Desc: image001.gif URL: From jeffrey.c.becker at nasa.gov Mon Feb 9 15:18:11 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Mon, 9 Feb 2015 12:18:11 -0800 Subject: [Paraview] pvserver issue Message-ID: <54D91603.1090403@nasa.gov> Hi. I'm running a recent build of ParaView in client/server mode on a GPU cluster. I successfully launch the servers and connect a client on my desktop... $ mpirun -np 8 /usr/bin/env DISPLAY=:0 ./pvserver --client-host=pfe20 --use-offscreen-rendering --disable-xdisplay-test Waiting for client... Connection URL: cs://r219i0n1:11111 Accepting connection(s): r219i0n1:11111 Client connected. However, when I try to open a file (on the server file system) from the client, I get the following upon hitting "update". It looks like my display is bad, but I specified it above. How can I fix this? Thanks. -jeff MPI_FILE_SET_VIEW (line 62): **iobaddisp MPI_FILE_SET_VIEW (line 62): **iobaddisp MPI_FILE_SET_VIEW (line 62): **iobaddisp MPI_FILE_SET_VIEW (line 62): **iobaddisp MPI_FILE_SET_VIEW (line 62): **iobaddisp ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line 256 vtkPVImageReader (0x1c014f0): Received error when calling MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, const_cast("native"), MPI_INFO_NULL) Invalid argument MPI_FILE_SET_VIEW (line 62): **iobaddisp ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line 256 vtkPVImageReader (0x1bfa760): Received error when calling MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, const_cast("native"), MPI_INFO_NULL) Invalid argument MPI_FILE_SET_VIEW (line 62): **iobaddisp ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line 256 vtkPVImageReader (0x1c05eb0): Received error when calling MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, const_cast("native"), MPI_INFO_NULL) Invalid argument ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line 256 vtkPVImageReader (0x1c014e0): Received error when calling MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, const_cast("native"), MPI_INFO_NULL) Invalid argument ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line 256 vtkPVImageReader (0x1c09f50): Received error when calling MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, const_cast("native"), MPI_INFO_NULL) Invalid argument ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line 256 vtkPVImageReader (0x1bf9f00): Received error when calling MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, const_cast("native"), MPI_INFO_NULL) Invalid argument ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line 256 vtkPVImageReader (0x1bfa700): Received error when calling MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, const_cast("native"), MPI_INFO_NULL) Invalid argument MPI_FILE_SET_VIEW (line 62): **iobaddisp ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line 256 vtkPVImageReader (0x1bf9ff0): Received error when calling MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, const_cast("native"), MPI_INFO_NULL) Invalid argument From andy.bauer at kitware.com Mon Feb 9 15:19:01 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 9 Feb 2015 15:19:01 -0500 Subject: [Paraview] User trying to build with catalyst -- need guidance In-Reply-To: <7CA71728-8DAE-47F2-B03D-D1B0E786163C@llnl.gov> References: <696276497.27732258.1423272306498.JavaMail.root@mail.gatech.edu> <7CA71728-8DAE-47F2-B03D-D1B0E786163C@llnl.gov> Message-ID: Hi Rich, I'd suggest that initially just build ParaView from the full source code. The Catalyst editions are meant to be slimmed down versions of ParaView to reduce the memory load for specific configurations. See http://www.kitware.com/blog/home/post/606 for information on the Catalyst editions. Dave may have more information on building Catalyst as a library for the BG/Q but if the simulation code already uses CMake then see the CMakeLists.txt at https://github.com/Kitware/ParaViewCatalystExampleCode/blob/master/CxxFullExample/CMakeLists.txt. If the simulation code doesn't use CMake then the easiest thing is to create the adaptor as a library and build that with CMake and then just link the code to that library. An example of that is at https://github.com/acbauer/miniFE-2.0_ref_Catalyst where the adapter is built with CMake and links to Catalyst and the Makefile in src just points to the adapter library. Have you gone through the Catalyst User's Guide yet? It's available at http://www.paraview.org/Wiki/images/4/48/CatalystUsersGuide.pdf. I hope to have an updated version available in a week or two. Regards, Andy On Mon, Feb 9, 2015 at 2:14 PM, Cook, Rich wrote: > Thanks, Tim, I?ll follow your approach of using the mailing list and > asking specific questions. > > My current question is this: which of these should I download? > > > Since this is for a BG/Q machine, I believe I?m going to have to do a > cross-compile. > > Thanks > ? Rich > > On Feb 6, 2015, at 5:25 PM, Tim Gallagher > wrote: > > Hi Rich, > > There may be a few who are willing to help out if you can provide some > specific questions or issues you run into. > > Have you looked through the documentation at > http://www.paraview.org/in-situ/ ? I got Catalyst up and running in our > code (not on a BG/Q but on different clusters) with the information in the > documentation and by asking some specific questions here on the list. For > me, the hardest part was converting our data into VTK data -- I did not > have any exposure to VTK prior to taking the Catalyst leap. But it turned > out to be (relatively) straight forward for what we are doing. > > I will be happy to answer things I can and for things I can't, hopefully > somebody else will jump in. > > Tim > > ------------------------------ > *From: *"Rich Cook" > *To: *paraview at paraview.org > *Sent: *Friday, February 6, 2015 7:23:24 PM > *Subject: *[Paraview] User trying to build with catalyst -- need guidance > > Hello, > We have not used catalyst here and I have a user that is interested in > trying it out on our BG/Q machine with a huge code on hundreds of thousands > of nodes. ;-) > Is there a brave soul willing to hold our hands through this process? > Thanks. > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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: PastedGraphic-5.png Type: image/png Size: 67461 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Mon Feb 9 15:55:23 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 9 Feb 2015 15:55:23 -0500 Subject: [Paraview] pvserver issue In-Reply-To: <54D91603.1090403@nasa.gov> References: <54D91603.1090403@nasa.gov> Message-ID: I don't think this is a display issue, but more of a file issue. Can you try creating a builtin source like Sphere or Wavelet and see if that works? Utkarsh On Mon, Feb 9, 2015 at 3:18 PM, Jeff Becker wrote: > Hi. I'm running a recent build of ParaView in client/server mode on a GPU > cluster. I successfully launch the servers and connect a client on my > desktop... > > $ mpirun -np 8 /usr/bin/env DISPLAY=:0 ./pvserver --client-host=pfe20 > --use-offscreen-rendering --disable-xdisplay-test > Waiting for client... > Connection URL: cs://r219i0n1:11111 > Accepting connection(s): r219i0n1:11111 > Client connected. > > However, when I try to open a file (on the server file system) from the > client, I get the following upon hitting "update". It looks like my display > is bad, but I specified it above. How can I fix this? Thanks. > > -jeff > > MPI_FILE_SET_VIEW (line 62): **iobaddisp > MPI_FILE_SET_VIEW (line 62): **iobaddisp > MPI_FILE_SET_VIEW (line 62): **iobaddisp > MPI_FILE_SET_VIEW (line 62): **iobaddisp > MPI_FILE_SET_VIEW (line 62): **iobaddisp > ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line > 256 > vtkPVImageReader (0x1c014f0): Received error when calling > MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, > const_cast("native"), MPI_INFO_NULL) > > Invalid argument > > MPI_FILE_SET_VIEW (line 62): **iobaddisp > ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line > 256 > vtkPVImageReader (0x1bfa760): Received error when calling > MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, > const_cast("native"), MPI_INFO_NULL) > > Invalid argument > > MPI_FILE_SET_VIEW (line 62): **iobaddisp > ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line > 256 > vtkPVImageReader (0x1c05eb0): Received error when calling > MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, > const_cast("native"), MPI_INFO_NULL) > > Invalid argument > > ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line > 256 > vtkPVImageReader (0x1c014e0): Received error when calling > MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, > const_cast("native"), MPI_INFO_NULL) > > Invalid argument > > ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line > 256 > vtkPVImageReader (0x1c09f50): Received error when calling > MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, > const_cast("native"), MPI_INFO_NULL) > > Invalid argument > > ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line > 256 > vtkPVImageReader (0x1bf9f00): Received error when calling > MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, > const_cast("native"), MPI_INFO_NULL) > > Invalid argument > > ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line > 256 > vtkPVImageReader (0x1bfa700): Received error when calling > MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, > const_cast("native"), MPI_INFO_NULL) > > Invalid argument > > MPI_FILE_SET_VIEW (line 62): **iobaddisp > ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line > 256 > vtkPVImageReader (0x1bf9ff0): Received error when calling > MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, > const_cast("native"), MPI_INFO_NULL) > > Invalid argument > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 jeffrey.c.becker at nasa.gov Mon Feb 9 17:02:22 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Mon, 9 Feb 2015 14:02:22 -0800 Subject: [Paraview] pvserver issue In-Reply-To: References: <54D91603.1090403@nasa.gov> Message-ID: <54D92E6E.6030802@nasa.gov> On 02/09/2015 12:55 PM, Utkarsh Ayachit wrote: > I don't think this is a display issue, but more of a file issue. Can > you try creating a builtin source like Sphere or Wavelet and see if > that works? Sphere works. As do cylinder, and wavelet. I got a crash when I tried to volume render wavelet, but maybe that's expected. -jeff > > Utkarsh > > On Mon, Feb 9, 2015 at 3:18 PM, Jeff Becker wrote: >> Hi. I'm running a recent build of ParaView in client/server mode on a GPU >> cluster. I successfully launch the servers and connect a client on my >> desktop... >> >> $ mpirun -np 8 /usr/bin/env DISPLAY=:0 ./pvserver --client-host=pfe20 >> --use-offscreen-rendering --disable-xdisplay-test >> Waiting for client... >> Connection URL: cs://r219i0n1:11111 >> Accepting connection(s): r219i0n1:11111 >> Client connected. >> >> However, when I try to open a file (on the server file system) from the >> client, I get the following upon hitting "update". It looks like my display >> is bad, but I specified it above. How can I fix this? Thanks. >> >> -jeff >> >> MPI_FILE_SET_VIEW (line 62): **iobaddisp >> MPI_FILE_SET_VIEW (line 62): **iobaddisp >> MPI_FILE_SET_VIEW (line 62): **iobaddisp >> MPI_FILE_SET_VIEW (line 62): **iobaddisp >> MPI_FILE_SET_VIEW (line 62): **iobaddisp >> ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line >> 256 >> vtkPVImageReader (0x1c014f0): Received error when calling >> MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, >> const_cast("native"), MPI_INFO_NULL) >> >> Invalid argument >> >> MPI_FILE_SET_VIEW (line 62): **iobaddisp >> ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line >> 256 >> vtkPVImageReader (0x1bfa760): Received error when calling >> MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, >> const_cast("native"), MPI_INFO_NULL) >> >> Invalid argument >> >> MPI_FILE_SET_VIEW (line 62): **iobaddisp >> ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line >> 256 >> vtkPVImageReader (0x1c05eb0): Received error when calling >> MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, >> const_cast("native"), MPI_INFO_NULL) >> >> Invalid argument >> >> ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line >> 256 >> vtkPVImageReader (0x1c014e0): Received error when calling >> MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, >> const_cast("native"), MPI_INFO_NULL) >> >> Invalid argument >> >> ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line >> 256 >> vtkPVImageReader (0x1c09f50): Received error when calling >> MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, >> const_cast("native"), MPI_INFO_NULL) >> >> Invalid argument >> >> ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line >> 256 >> vtkPVImageReader (0x1bf9f00): Received error when calling >> MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, >> const_cast("native"), MPI_INFO_NULL) >> >> Invalid argument >> >> ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line >> 256 >> vtkPVImageReader (0x1bfa700): Received error when calling >> MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, >> const_cast("native"), MPI_INFO_NULL) >> >> Invalid argument >> >> MPI_FILE_SET_VIEW (line 62): **iobaddisp >> ERROR: In /u/jcbecker/ParaView/VTK/IO/MPIImage/vtkMPIImageReader.cxx, line >> 256 >> vtkPVImageReader (0x1bf9ff0): Received error when calling >> MPI_File_set_view(file.Handle, this->GetHeaderSize(file), MPI_BYTE, view, >> const_cast("native"), MPI_INFO_NULL) >> >> Invalid argument >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 Mon Feb 9 18:16:49 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 9 Feb 2015 18:16:49 -0500 Subject: [Paraview] pvserver issue In-Reply-To: <54D92E6E.6030802@nasa.gov> References: <54D91603.1090403@nasa.gov> <54D92E6E.6030802@nasa.gov> Message-ID: > Sphere works. As do cylinder, and wavelet. I got a crash when I tried to > volume render wavelet, but maybe that's expected. After creating the Sphere, try changing the Remote Render Threshold (in the Settings dialog) to 0 -- this will force remote rendering. I suspect this will segfault. For how to change the Remote Render Threshold, see Page 199 from The ParaView Guide (v4.3). You can download the guide from: http://www.paraview.org/documentation/. If pvserver is crashing when remote rendering (which is what happens when using Volume Rendering the Wavelet automatically), then there is a indeed display problem. Any reason why you're doing this "--disable-xdisplay-test"? Utkarsh From jeffrey.c.becker at nasa.gov Mon Feb 9 18:37:47 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Mon, 9 Feb 2015 15:37:47 -0800 Subject: [Paraview] pvserver issue In-Reply-To: References: <54D91603.1090403@nasa.gov> <54D92E6E.6030802@nasa.gov> Message-ID: <54D944CB.9010502@nasa.gov> On 02/09/2015 03:16 PM, Utkarsh Ayachit wrote: >> Sphere works. As do cylinder, and wavelet. I got a crash when I tried to >> volume render wavelet, but maybe that's expected. > After creating the Sphere, try changing the Remote Render Threshold > (in the Settings dialog) to 0 -- this will force remote rendering. I > suspect this will segfault. For how to change the Remote Render > Threshold, see Page 199 from The ParaView Guide (v4.3). You can > download the guide from: http://www.paraview.org/documentation/. Yup. All 8 MPI processes die with something similar to: ERROR: In /u/jcbecker/ParaView/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 530 vtkXOpenGLRenderWindow (0x1bf16f0): bad X server connection. DISPLAY=:0. Aborting. > > If pvserver is crashing when remote rendering (which is what happens > when using Volume Rendering the Wavelet automatically), then there is > a indeed display problem. Any reason why you're doing this > "--disable-xdisplay-test"? If I don't, I get a message on the client that says: Display is not accessible on server side. Remote rendering will be disabled. -jeff > > Utkarsh From hfklinac at hotmail.com Mon Feb 9 20:44:16 2015 From: hfklinac at hotmail.com (Hannah Klinac) Date: Tue, 10 Feb 2015 09:44:16 +0800 Subject: [Paraview] Paraview enabled VR Plugin not interacting via VRPN In-Reply-To: References: , , , Message-ID: Hi Aashish, Thanks for the prompt reply! 1) Yes it is a valid VRPN server, and the vrpn.cfg file is set up correctly. When I run vrpn_print_devices with "Mouse0 at localhost" as the argument I get correct button and analog feedback. I have read that in the VR Plugin, the address should be "@", therefore Mouse0 at localhost should be correct. 2) I am unsure of what to do for the interaction in the VR Plugin, there doesn't seem to be a lot of options available, is there some sort of example configuration you could give me as a starter? I do not have access to a tracker, is interaction achievable without one? Basically I just want to be able to move the camera, or interact with an object using devices through the VRPN. I am starting with the mouse (Mouse0) because I know it works on other applications and on the VRPN, so I am assuming the trouble I am having is with my Paraview configuration. After I have set up simple interaction with the mouse I will move onto other devices that VRPN supports, such as the 5DT Data Gloves. And an example of the interaction I want is to be able to turn the camera left when the mouse moves left, right when it moves right, forward, backward, and to be able to grab the object on click. Thanks,Hannah Date: Mon, 9 Feb 2015 09:17:28 -0500 Subject: Re: [Paraview] Paraview enabled VR Plugin not interacting via VRPN From: aashish.chaudhary at kitware.com To: hfklinac at hotmail.com CC: paraview at paraview.org Hannah, Thanks for sending the files. Couple of thigs: 1) Is this really a valid VRPN server Mouse0 at localhost? Can you use vrpn_print_devices program to communicate with it? 2) Looks like you the property you configured is visibility but the style you have chosen is vtkVRGrabWorldStyle which requires tracker or otherwise it won't do anything. Can you describe it in bit more detail on what exactly you are trying to achieve? What hardware you have? - Aashish On Sun, Feb 8, 2015 at 9:50 PM, Hannah Klinac wrote: Hi, This is my process: Start Paraview serverStart VRPN serverStart Paraview clientAdd an object (box)Add VRPN connection in the VR PanelAdd VRPN interaction in the VR PanelPress "start" Is there anything I am missing?Elsewise I can give more information about my VRPN, however I'm assuming I'm doing something wrong/missing something with the Paraview setup. I have saved the project and VR state files and attached them. I am using Paraview 4.3.1 (32bit) on Windows 7 (64bit). Thanks for your help,Hannah Date: Wed, 4 Feb 2015 11:11:10 -0500 Subject: Re: [Paraview] Paraview enabled VR Plugin not interacting via VRPN From: aashish.chaudhary at kitware.com To: hfklinac at hotmail.com CC: paraview at paraview.org Hi Hannah, On Wed, Feb 4, 2015 at 3:36 AM, Hannah Klinac wrote: Hi, I recently compiled Paraview from the source code to enable the VR Plugin. I have built VRPN, and compiled Paraview using that VRPN's dependencies. However, when I add the connection and interaction in the VR Plugin in Paraview and press "Start", when I (for example) press the button I have registered down, the interaction doesn't happen. And on my server it says: "vrpn: Connection requiest received from 'IP address': 'IP address' 'Port'Get a new connection, reset virtual_Tracker" Is it possible for you to share the VR state file? Or provide information on how you setup the VRPN server in the first place? Seems like a configuration issue. Also, helpful to know the version of ParaView and the OS you are using? Any idea if I have just not setup my connection/interaction correctly in Paraview? The VRPN server works fine for other applications such as Vizard. Thanks, Thanks in advance for any guidance,Hannah _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From foss at grueninger.de Mon Feb 9 23:57:31 2015 From: foss at grueninger.de (=?UTF-8?B?Q2hyaXN0b3BoIEdyw7xuaW5nZXI=?=) Date: Tue, 10 Feb 2015 05:57:31 +0100 Subject: [Paraview] CPack issue with hdf5/libhdf5.settings Message-ID: <54D98FBB.0@grueninger.de> Hi ParaView devs, I tried to build a openSuse RPM for ParaView 4.3.1 but I get the following error. I guess it is related to ParaView's CPack scripts: [ 6390s] Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/abuild/rpmbuild/BUILDROOT/paraview-4.3.1-30.1.x86_64 [ 6390s] error: Installed (but unpackaged) file(s) found: [ 6390s] /usr/share/cmake/hdf5/libhdf5.settings [ 6390s] [ 6390s] [ 6390s] RPM build errors: [ 6390s] Installed (but unpackaged) file(s) found: [ 6390s] /usr/share/cmake/hdf5/libhdf5.settings [ 6391s] ### WATCHDOG MARKER START ### Sorry for not providing a patch. Bye Christoph -- When you die, that does not mean that you lose to cancer, you beat cancer by how you live, why you live, and in the manner in which you live. -- Stuart Scott, 1965-2015 From dkxls23 at gmail.com Tue Feb 10 04:36:34 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Tue, 10 Feb 2015 11:36:34 +0200 Subject: [Paraview] CPack issue with hdf5/libhdf5.settings In-Reply-To: <54D98FBB.0@grueninger.de> References: <54D98FBB.0@grueninger.de> Message-ID: <54D9D122.6070809@gmail.com> Hi Christoph, How are you building the packages? I'm building packages for paraview 4.2.0 and 4.3.1 on the "openSUSE Build Service". If you want to compile ParaView with specific options you can copy my spec file and start from there: https://build.opensuse.org/package/view_file/home:dkxls:cfd/paraview43/paraview43.spec If it is nothing too exotic I can also enable your options for the packages. You can install them easily from here: http://software.opensuse.org/package/paraview43 -Armin Disclaimer: I'm not a ParaView developer, just a regular user. The packages above are neither supported by Kitware nor openSUSE and are just intended to ease the installation on the openSUSE workstations in our research group. On 02/10/2015 06:57 AM, Christoph Gr?ninger wrote: > Hi ParaView devs, > I tried to build a openSuse RPM for ParaView 4.3.1 but I get the > following error. I guess it is related to ParaView's CPack scripts: > > > [ 6390s] Checking for unpackaged file(s): /usr/lib/rpm/check-files > /home/abuild/rpmbuild/BUILDROOT/paraview-4.3.1-30.1.x86_64 > [ 6390s] error: Installed (but unpackaged) file(s) found: > [ 6390s] /usr/share/cmake/hdf5/libhdf5.settings > [ 6390s] > [ 6390s] > [ 6390s] RPM build errors: > [ 6390s] Installed (but unpackaged) file(s) found: > [ 6390s] /usr/share/cmake/hdf5/libhdf5.settings > [ 6391s] ### WATCHDOG MARKER START ### > > Sorry for not providing a patch. > > Bye > Christoph > From foss at grueninger.de Tue Feb 10 07:10:01 2015 From: foss at grueninger.de (=?UTF-8?Q?Christoph_Gr=C3=BCninger?=) Date: Tue, 10 Feb 2015 13:10:01 +0100 (CET) Subject: [Paraview] CPack issue with hdf5/libhdf5.settings In-Reply-To: <54D9D122.6070809@gmail.com> References: <54D98FBB.0@grueninger.de> <54D9D122.6070809@gmail.com> Message-ID: <1968868283.1759194.1423570201971.JavaMail.open-xchange@omgreatgod.store> Hi Armin, > How are you building the packages? with openSuse's buildservice. I branched the official ParaView package which is still ParaView 4.2 and tried to update it. After I replaced the sources and adjusted the spec file, I got the mentioned error. By quickly scanning your spec file, I couldn't find the obvious difference causing my error. Bye Christoph From anton.piccardo-selg at stfc.ac.uk Tue Feb 10 08:46:34 2015 From: anton.piccardo-selg at stfc.ac.uk (anton.piccardo-selg at stfc.ac.uk) Date: Tue, 10 Feb 2015 13:46:34 +0000 Subject: [Paraview] Paraview Programmable Source 3D Text Message-ID: <593AFCE559F11049B8F268BE84170A0DC11DA4@EXCHMBX03.fed.cclrc.ac.uk> Hi Roman, Did you succeed to implement a 3D Text annotation in the data set? I am currently also looking into adding this to our ParaView customization but I am a bit at a loss how this can be achieved programmatically in ParaView. If you have any hints or ideas how to tackle this, I would be very grateful to know. Many thanks and best regards, Anton From utkarsh.ayachit at kitware.com Tue Feb 10 09:20:09 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 10 Feb 2015 09:20:09 -0500 Subject: [Paraview] pvserver issue In-Reply-To: <54D944CB.9010502@nasa.gov> References: <54D91603.1090403@nasa.gov> <54D92E6E.6030802@nasa.gov> <54D944CB.9010502@nasa.gov> Message-ID: >> If pvserver is crashing when remote rendering (which is what happens >> when using Volume Rendering the Wavelet automatically), then there is >> a indeed display problem. Any reason why you're doing this >> "--disable-xdisplay-test"? > > If I don't, I get a message on the client that says: Display is not > accessible on server side. Remote rendering will be disabled. Jeff, that test is determining exactly what you're finding our eventually, and a little less gracefully :), because of display issues ParaView indeed cannot do remote rendering hence the warning and hence the segfault (when the warning is disabled). Are you sure you're X server is up and running on DISPLAY=:0? And is accessible? Try running something else, like glxgears with the mpirun call. Does that work? From utkarsh.ayachit at kitware.com Tue Feb 10 09:39:34 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 10 Feb 2015 09:39:34 -0500 Subject: [Paraview] Set of 3DText sources? In-Reply-To: References: Message-ID: There isn't a preexisting filter that does this, bug you can write a new filter that does exactly that -- givens a list of coorinates and labels, internally uses mulitple instances of vtkVectorText (which is what the 3D Text is ParaView uses) and then append the polydata returned by each of the vtkVectorText instances into a single polydata to put out as the output. Here's a simple Python script that you can use as the "Script" for a "Programmable Source" to see how such a filter could be written. # ------------------------------------------------------------------------------------------- # script for RequestData Script of the Programmable Source # ------------------------------------------------------------------------------------------- from vtk.vtkRenderingFreeType import vtkVectorText from vtk.vtkFiltersCore import vtkAppendPolyData from vtk.vtkFiltersGeneral import vtkTransformPolyDataFilter from vtk.vtkCommonTransforms import vtkTransform coords = [(0, 0, 0), (0, 10, 0)] labels = ["One", "Two"] def getText(pos, text): source = vtkVectorText() source.SetText(text) transform = vtkTransform() transform.Translate(pos) transformPD = vtkTransformPolyDataFilter() transformPD.SetTransform(transform) transformPD.SetInputConnection(source.GetOutputPort()) transformPD.Update() return transformPD.GetOutput() appender = vtkAppendPolyData() for coord, label in zip(coords, labels): pd = getText(coord, label) appender.AddInputDataObject(pd) appender.Update() output.ShallowCopy(appender.GetOutput()) ------------------------------------------------------------------------------------------- On Mon, Feb 9, 2015 at 9:58 AM, wrote: > Hi, > > I am currently working on a customization of ParaView. We plot > crystallographic data and would like to annotate some of the data points > directly in the view. > > I can see that the 3DText source can do this for a single data point. > Ideally, we don't want to create one 3DText source per data point though. > Hence my question: Is there a filter or technique for which we can supply a > set of coordinates and annotation labels to be able to print text next to > several data points at once in a convenient way? > > Many thanks and best regards, > > Anton > > This message is commercial in confidence and may be privileged. It is > intended for the > addressee(s) only. Access to this message by anyone else is unauthorized and > strictly prohibited. > If you have received this message in error, please inform the sender > immediately. Please note that > messages sent or received by the Tessella e-mail system may be monitored and > stored in an > information retrieval system. > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 ben.boeckel at kitware.com Tue Feb 10 16:48:50 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 10 Feb 2015 16:48:50 -0500 Subject: [Paraview] CPack issue with hdf5/libhdf5.settings In-Reply-To: <1968868283.1759194.1423570201971.JavaMail.open-xchange@omgreatgod.store> References: <54D98FBB.0@grueninger.de> <54D9D122.6070809@gmail.com> <1968868283.1759194.1423570201971.JavaMail.open-xchange@omgreatgod.store> Message-ID: <20150210214850.GB19584@megas.kitwarein.com> On Tue, Feb 10, 2015 at 13:10:01 +0100, Christoph Gr?ninger wrote: > > How are you building the packages? > > with openSuse's buildservice. I branched the official ParaView > package which is still ParaView 4.2 and tried to update it. After > I replaced the sources and adjusted the spec file, I got the > mentioned error. > > By quickly scanning your spec file, I couldn't find the obvious > difference causing my error. You need to update %files to account for new files which are now installed. --Ben From aashish.chaudhary at kitware.com Wed Feb 11 09:06:00 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 11 Feb 2015 09:06:00 -0500 Subject: [Paraview] Paraview enabled VR Plugin not interacting via VRPN In-Reply-To: References: Message-ID: Dear Hannah, On Mon, Feb 9, 2015 at 8:44 PM, Hannah Klinac wrote: > Hi Aashish, > > Thanks for the prompt reply! > > 1) Yes it is a valid VRPN server, and the vrpn.cfg file is set up > correctly. When I run vrpn_print_devices with "Mouse0 at localhost" as the > argument I get correct button and analog feedback. I have read that in the > VR Plugin, the address should be "@", therefore > Mouse0 at localhost should be correct. > RIght that is correct. > > 2) I am unsure of what to do for the interaction in the VR Plugin, there > doesn't seem to be a lot of options available, is there some sort of > example configuration you could give me as a starter? I do not have access > to a tracker, is interaction achievable without one? > We don't have many options. We only have two stylee: One used for the tracker and another one to use the tracker data to navigate around. > > Basically I just want to be able to move the camera, or interact with an > object using devices through the VRPN. I am starting with the mouse > (Mouse0) because I know it works on other applications and on the VRPN, so > I am assuming the trouble I am having is with my Paraview configuration. > Sure, What you can do is look at the TrackerStyle class. You can very easily add a new style class that can respond to mouse clicks or anything else. The current style won't work in your configuration because it needs tracker and 3 buttons for navigation. > After I have set up simple interaction with the mouse I will move onto > other devices that VRPN supports, such as the 5DT Data Gloves. And an > example of the interaction I want is to be able to turn the camera left > when the mouse moves left, right when it moves right, forward, backward, > and to be able to grab the object on click. > That would be great. I am willing to help you if you are willing to share the code and add a new class to ParaView. Please let me know. - Aashish > > Thanks, > Hannah > > ------------------------------ > Date: Mon, 9 Feb 2015 09:17:28 -0500 > > Subject: Re: [Paraview] Paraview enabled VR Plugin not interacting via VRPN > From: aashish.chaudhary at kitware.com > To: hfklinac at hotmail.com > CC: paraview at paraview.org > > Hannah, > > Thanks for sending the files. Couple of thigs: > > 1) Is this really a valid VRPN server Mouse0 at localhost? Can you use > vrpn_print_devices program to communicate with it? > > 2) Looks like you the property you configured is visibility but the style > you have chosen is vtkVRGrabWorldStyle which requires tracker or otherwise > it won't do anything. > > Can you describe it in bit more detail on what exactly you are trying to > achieve? What hardware you have? > > - Aashish > > On Sun, Feb 8, 2015 at 9:50 PM, Hannah Klinac > wrote: > > Hi, > > This is my process: > > > 1. Start Paraview server > 2. Start VRPN server > 3. Start Paraview client > 1. Add an object (box) > 2. Add VRPN connection in the VR Panel > 3. Add VRPN interaction in the VR Panel > 4. Press "start" > > > Is there anything I am missing? > Elsewise I can give more information about my VRPN, however I'm assuming > I'm doing something wrong/missing something with the Paraview setup. > > I have saved the project and VR state files and attached them. > > I am using Paraview 4.3.1 (32bit) on Windows 7 (64bit). > > Thanks for your help, > Hannah > > ------------------------------ > Date: Wed, 4 Feb 2015 11:11:10 -0500 > Subject: Re: [Paraview] Paraview enabled VR Plugin not interacting via VRPN > From: aashish.chaudhary at kitware.com > To: hfklinac at hotmail.com > CC: paraview at paraview.org > > > Hi Hannah, > > On Wed, Feb 4, 2015 at 3:36 AM, Hannah Klinac > wrote: > > Hi, > > I recently compiled Paraview from the source code to enable the VR Plugin. > > I have built VRPN, and compiled Paraview using that VRPN's dependencies. > > However, when I add the connection and interaction in the VR Plugin in > Paraview and press "Start", when I (for example) press the button I have > registered down, the interaction doesn't happen. And on my server it says: > > "vrpn: Connection requiest received from 'IP address': 'IP address' 'Port' > Get a new connection, reset virtual_Tracker" > > > Is it possible for you to share the VR state file? Or provide information > on how you setup the VRPN server in the first place? Seems like a > configuration issue. Also, helpful to know the version of ParaView and the > OS you are using? > > > > Any idea if I have just not setup my connection/interaction correctly in > Paraview? The VRPN server works fine for other applications such as Vizard. > > > Thanks, > > > > Thanks in advance for any guidance, > Hannah > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. * > *| http://www.kitware.com/company/team/chaudhary.html > * > > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. * > *| http://www.kitware.com/company/team/chaudhary.html > * > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Feb 11 09:15:40 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 11 Feb 2015 09:15:40 -0500 Subject: [Paraview] Fwd: Paraview enabled VR Plugin not interacting via VRPN In-Reply-To: <54DB626F.1040407@tu-braunschweig.de> References: <54DB626F.1040407@tu-braunschweig.de> Message-ID: Tao, Quick answer: Use Threshold filter in ParaView. - Aashish ---------- Forwarded message ---------- From: Tao Wu Date: Wed, Feb 11, 2015 at 9:08 AM Subject: Re: [Paraview] Paraview enabled VR Plugin not interacting via VRPN To: Aashish Chaudhary Hi Aashish, Sorry that I directly sent the E-mail to you since it always failed when I sent to paraview at paraview.org. The following is my question. Hi All, How can I only show the cells whose values (like displacement) are larger certain value, and remove (not show) cells whose values are smaller than certain values? Thank you. Regards, Tao -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Feb 11 09:26:19 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 11 Feb 2015 09:26:19 -0500 Subject: [Paraview] Fwd: Paraview enabled VR Plugin not interacting via VRPN In-Reply-To: <54DB6528.5000009@tu-braunschweig.de> References: <54DB626F.1040407@tu-braunschweig.de> <54DB6528.5000009@tu-braunschweig.de> Message-ID: Tao, Try "Reply All" (may be it won't bounce back this time). On Wed, Feb 11, 2015 at 9:20 AM, Tao Wu wrote: > Aashish, > > Thank you for the quick reply. I used the threshold filter. It can > remove cells if I define the material property for each cell in the VTK > file. > > I am using paraview to illustrate the mechanical results. Therefore, I > need show and remove some cells based on the displacements values of each > cell. > If you have displacements value per cell then you should be able to select that for thresholding. I am not sure what would be the problem there. - Aashish > > Do you have any idea? Thank you. > > Regards, > Tao > On 02/11/2015 03:15 PM, Aashish Chaudhary wrote: > > Tao, > > Quick answer: Use Threshold filter in ParaView. > > - Aashish > > ---------- Forwarded message ---------- > From: Tao Wu > Date: Wed, Feb 11, 2015 at 9:08 AM > Subject: Re: [Paraview] Paraview enabled VR Plugin not interacting via VRPN > To: Aashish Chaudhary > > > Hi Aashish, > > Sorry that I directly sent the E-mail to you since it always failed > when I sent to paraview at paraview.org. > > The following is my question. > > Hi All, > How can I only show the cells whose values (like displacement) are > larger certain value, and remove (not show) cells whose values are smaller > than > certain values? Thank you. > > Regards, > Tao > > > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. > * > *| http://www.kitware.com/company/team/chaudhary.html > * > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview > > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hertzberg at Colorado.EDU Wed Feb 11 14:01:29 2015 From: Hertzberg at Colorado.EDU (Jean Hertzberg) Date: Wed, 11 Feb 2015 12:01:29 -0700 Subject: [Paraview] Vorticity calc algorithm? Message-ID: Hi I asked this last week, but got zero response. Please help me, or point me towards the right documentation: Exactly what algorithm is used to calculate vorticity in the Compute Derivatives filter? Is it a first or a second order central difference scheme for gradients, or does it use the circulation method? Thanks Jean Hertzberg Dept. Mechanical Engineering University of Colorado, Boulder -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Feb 11 14:59:34 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 11 Feb 2015 14:59:34 -0500 Subject: [Paraview] Vorticity calc algorithm? In-Reply-To: References: Message-ID: I'm not sure of the exact algorithm. I think you'll need to look at the source code for that. The class name is vtkCellDerivatives ( http://www.vtk.org/doc/nightly/html/classvtkCellDerivatives.html). On Wed, Feb 11, 2015 at 2:01 PM, Jean Hertzberg wrote: > Hi > > I asked this last week, but got zero response. Please help me, or point me > towards the right documentation: > > Exactly what algorithm is used to calculate vorticity in the Compute > Derivatives filter? Is it a first or a second order central difference > scheme for gradients, or does it use the circulation method? > > > > Thanks > > > > Jean Hertzberg > > > > Dept. Mechanical Engineering > > University of Colorado, Boulder > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 Wed Feb 11 15:05:50 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Wed, 11 Feb 2015 20:05:50 +0000 Subject: [Paraview] Vorticity calc algorithm? Message-ID: The implementation of the compute derivatives filter has been around a while so the author probably hasn't seen your email. I'm not super familiar with the code, but I believe the vorticity is computed from the first order derivative of the vector field. It is not actually using a central difference scheme to compute the gradients. Instead, it is treating the field as a piecewise linear field (or piecewise quadratic or piecewise cubic depending on the cell type) based on the volumes of the cells. The derivatives are then computed in the middle of the piecewise C1 continuous parts of the cells from the known function. You can take a look at the source for the algorithm here: http://vtk.org/gitweb?p=VTK.git;a=blob;f=Filters/General/vtkCellDerivatives.cxx;h=4debdf45eeb7a11e98062ab2d9efa65e938433b6;hb=ab4dc579c340167b6b3ae6cd82b3fd645642796a Vorticity is computed between lines 169 and 216. -Ken From: Jean Hertzberg > Date: Wednesday, February 11, 2015 at 12:01 PM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Vorticity calc algorithm? Hi I asked this last week, but got zero response. Please help me, or point me towards the right documentation: Exactly what algorithm is used to calculate vorticity in the Compute Derivatives filter? Is it a first or a second order central difference scheme for gradients, or does it use the circulation method? Thanks Jean Hertzberg Dept. Mechanical Engineering University of Colorado, Boulder -------------- next part -------------- An HTML attachment was scrubbed... URL: From redkite at virgin.net Wed Feb 11 15:00:47 2015 From: redkite at virgin.net (redkite) Date: Wed, 11 Feb 2015 20:00:47 +0000 Subject: [Paraview] Plugin crashes if source filter is not applied In-Reply-To: <54D865D0.7070905@kit.edu> References: <54D865D0.7070905@kit.edu> Message-ID: <54DBB4EF.3090708@virgin.net> Hi, On function of my plugin operates on some point data on the surface of my model to create a new filter. This works well enough if the user selects points, uses the 'Extract Selection Filter' and remembers to click Apply. I can check if the active source filter is an 'ExtractSelection' easily enough by name, which is some help, but if the user has not clicked apply, ParaView likes to crash out (PV 4.1 on Windows 7 does anyway). Auto-apply is better avoided, especially for large models. Is there a way to check to check if the source data has (or has not) been extracted and applied? I've tried using UpdateVTKObjects() etc to force the apply, but no joy... regards, Richard From andy.bauer at kitware.com Wed Feb 11 19:18:56 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 11 Feb 2015 19:18:56 -0500 Subject: [Paraview] scale for threshold filter In-Reply-To: References: Message-ID: Hi, Can you supply a data set that you're using along with some steps to reproduce your problem? I'm not sure I understand what's going on. Regards, Andy On Wed, Feb 11, 2015 at 3:03 PM, Wu Tao wrote: > Hi Andy, > > When I use the threshold filter, only material identifier of cells are > shown. How can I output other variables, like displacement for mechanical > problem, as the scalar for the threshold filter`? Thank you. > Tao > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Wed Feb 11 19:19:04 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 11 Feb 2015 16:19:04 -0800 Subject: [Paraview] error building silo reader Message-ID: <54DBF178.6070204@nasa.gov> Please help me understand and fix the following build error. Thanks. -jeff [ 26%] Building CXX object Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloWriter.C.o [ 26%] Building CXX object Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?virtual void avtSiloFileFormat::PopulateDatabaseMetaData(avtDatabaseMetaData*)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: error: ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? was not declared in this scope /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1211: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?void avtSiloFileFormat::ReadCSGmeshes(DBfile*, int, char**, const char*, avtDatabaseMetaData*)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2532: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: error: ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? was not declared in this scope /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2535: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?void avtSiloFileFormat::FindMultiMeshAdjConnectivity(DBfile*, int&, int*&, int*&, int&, int*&, int&, int*&, bool, bool)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5442: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: error: ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? was not declared in this scope /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5450: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?void avtSiloFileFormat::AddCSGMultimesh(const char*, const char*, avtDatabaseMetaData*, avtSiloMultiMeshCacheEntry*, DBfile*)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5883: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: error: ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? was not declared in this scope /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5955: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?vtkDataArray* avtSiloFileFormat::GetAnnotIntNodelistsVar(int, std::string)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6765: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6767: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?vtkDataArray* avtSiloFileFormat::GetMrgTreeNodelistsVar(int, std::string)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6856: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6858: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?void avtSiloFileFormat::ExpandUcdvar(DBucdvar*, const char*, const char*, int)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8563: error: invalid conversion from ?float**? to ?void**? /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8575: error: invalid conversion from ?float**? to ?void**? /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?void avtSiloFileFormat::HandleGlobalZoneIds(const char*, int, void*, int, int)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:9136: error: invalid conversion from ?float**? to ?void**? /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?void avtSiloFileFormat::ReadInConnectivity(vtkUnstructuredGrid*, DBucdmesh*, const char*, int)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:10226: error: invalid conversion from ?float**? to ?void**? /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?void avtSiloFileFormat::ReadInArbConnectivity(const char*, vtkUnstructuredGrid*, DBucdmesh*, int, int)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:11349: error: invalid conversion from ?float**? to ?void**? /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?vtkDataArray* avtSiloFileFormat::GetGlobalNodeIds(int, const char*)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13751: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: error: ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? was not declared in this scope /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13754: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?vtkDataArray* avtSiloFileFormat::GetGlobalZoneIds(int, const char*)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13842: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: error: ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? was not declared in this scope /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13845: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?avtMaterial* avtSiloFileFormat::CalcMaterial(DBfile*, const char*, const char*, int)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14218: error: invalid conversion from ?float**? to ?void**? /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: In member function ?avtFacelist* avtSiloFileFormat::CalcExternalFacelist(DBfile*, const char*)?: /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14423: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: error: expected primary-expression before ?,? token /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: error: ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? was not declared in this scope /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14426: error: expected primary-expression before ?,? token make[2]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o] Error 1 make[1]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all] Error 2 make: *** [all] Error 2 From foss at grueninger.de Thu Feb 12 00:45:47 2015 From: foss at grueninger.de (=?UTF-8?B?Q2hyaXN0b3BoIEdyw7xuaW5nZXI=?=) Date: Thu, 12 Feb 2015 06:45:47 +0100 Subject: [Paraview] CPack issue with hdf5/libhdf5.settings In-Reply-To: <20150210214850.GB19584@megas.kitwarein.com> References: <54D98FBB.0@grueninger.de> <54D9D122.6070809@gmail.com> <1968868283.1759194.1423570201971.JavaMail.open-xchange@omgreatgod.store> <20150210214850.GB19584@megas.kitwarein.com> Message-ID: <54DC3E0B.3050905@grueninger.de> Hi Ben, let me rephrase my question: Is it save to add /usr/share/cmake/hdf5/ within the ParaView package? Or would it affect a HDF5 package? I am unsure, whether /usr/share/paraview/hdf5.setting wouldn't be safer. But I am alien to HDF5 and might be wrong. Bye Christoph From kilian.weishaupt at gmx.net Thu Feb 12 10:05:48 2015 From: kilian.weishaupt at gmx.net (Kilian Weishaupt) Date: Thu, 12 Feb 2015 16:05:48 +0100 Subject: [Paraview] PV 4.3.1 Color legend and Color discretization Message-ID: An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: colorlegend1.png Type: image/png Size: 14719 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: colorlegend2.png Type: image/png Size: 15158 bytes Desc: not available URL: From ben.boeckel at kitware.com Thu Feb 12 12:43:23 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 12 Feb 2015 12:43:23 -0500 Subject: [Paraview] CPack issue with hdf5/libhdf5.settings In-Reply-To: <54DC3E0B.3050905@grueninger.de> References: <54D98FBB.0@grueninger.de> <54D9D122.6070809@gmail.com> <1968868283.1759194.1423570201971.JavaMail.open-xchange@omgreatgod.store> <20150210214850.GB19584@megas.kitwarein.com> <54DC3E0B.3050905@grueninger.de> Message-ID: <20150212174323.GA6196@megas.kitwarein.com> On Thu, Feb 12, 2015 at 06:45:47 +0100, Christoph Gr?ninger wrote: > let me rephrase my question: > Is it save to add /usr/share/cmake/hdf5/ within the ParaView package? Or > would it affect a HDF5 package? It would likely conflict with a native HDF5 package. Is there a reason the system HDF5 isn't used? > I am unsure, whether /usr/share/paraview/hdf5.setting wouldn't be safer. > But I am alien to HDF5 and might be wrong. Directory ownership in RPM isn't really straightforward or obvious all the time :( . Fedora's guidelines are here: https://fedoraproject.org/wiki/Packaging:Guidelines#File_and_Directory_Ownership Here, I'd say the package you're making should own the directory and hdf5.settings. --Ben From cook47 at llnl.gov Thu Feb 12 14:06:07 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 12 Feb 2015 19:06:07 +0000 Subject: [Paraview] User trying to build with catalyst -- need guidance In-Reply-To: References: <356E8CE9-8210-41AC-BEB8-02773F9DD972@llnl.gov> <561709608.27732302.1423272319866.JavaMail.root@mail.gatech.edu> Message-ID: Thanks for your message. I?ve poked around a bit. I have built Catalyst successfully on ?normal? Linux and our BG/Q machine front end nodes. I?m ready to try a cross compile. I came across this and was wondering if it seems right to you: http://www.vtk.org/Wiki/CmakeBlueGene We have a build of cmake that includes some extra files I don?t really understand, provided for me by our local wizard Todd Gamblin. How could I use these files to good effect? :-) It?s probably a dumb question, but I ask it to try to move in the right direction. rcook at rzuseqlac2 (bgqos_0 ): cp cmake-3.0-bgq-experimental/share/cmake-3.0/Modules/Platform/BlueGene BlueGeneL.cmake BlueGeneP-static-GNU-Fortran.cmake BlueGeneQ-dynamic-XL-CXX.cmake BlueGeneP-base.cmake BlueGeneP-static-XL-C.cmake BlueGeneQ-dynamic-XL-Fortran.cmake BlueGeneP-dynamic-GNU-C.cmake BlueGeneP-static-XL-CXX.cmake BlueGeneQ-dynamic.cmake BlueGeneP-dynamic-GNU-CXX.cmake BlueGeneP-static-XL-Fortran.cmake BlueGeneQ-static-GNU-C.cmake BlueGeneP-dynamic-GNU-Fortran.cmake BlueGeneP-static.cmake BlueGeneQ-static-GNU-CXX.cmake BlueGeneP-dynamic-XL-C.cmake BlueGeneQ-base.cmake BlueGeneQ-static-GNU-Fortran.cmake BlueGeneP-dynamic-XL-CXX.cmake BlueGeneQ-base.cmake~ BlueGeneQ-static-XL-C.cmake BlueGeneP-dynamic-XL-Fortran.cmake BlueGeneQ-dynamic-GNU-C.cmake BlueGeneQ-static-XL-CXX.cmake BlueGeneP-dynamic.cmake BlueGeneQ-dynamic-GNU-CXX.cmake BlueGeneQ-static-XL-Fortran.cmake BlueGeneP-static-GNU-C.cmake BlueGeneQ-dynamic-GNU-Fortran.cmake BlueGeneQ-static.cmake BlueGeneP-static-GNU-CXX.cmake BlueGeneQ-dynamic-XL-C.cmake On Feb 7, 2015, at 4:35 AM, David E DeMarle > wrote: I've done the BGQ ParaView + Catalyst build and installs on Mira at ANL. I can chip in with tips regarding compilation. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Feb 6, 2015 at 8:25 PM, Tim Gallagher > wrote: Hi Rich, There may be a few who are willing to help out if you can provide some specific questions or issues you run into. Have you looked through the documentation at http://www.paraview.org/in-situ/ ? I got Catalyst up and running in our code (not on a BG/Q but on different clusters) with the information in the documentation and by asking some specific questions here on the list. For me, the hardest part was converting our data into VTK data -- I did not have any exposure to VTK prior to taking the Catalyst leap. But it turned out to be (relatively) straight forward for what we are doing. I will be happy to answer things I can and for things I can't, hopefully somebody else will jump in. Tim ________________________________ From: "Rich Cook" > To: paraview at paraview.org Sent: Friday, February 6, 2015 7:23:24 PM Subject: [Paraview] User trying to build with catalyst -- need guidance Hello, We have not used catalyst here and I have a user that is interested in trying it out on our BG/Q machine with a huge code on hundreds of thousands of nodes. ;-) Is there a brave soul willing to hold our hands through this process? Thanks. -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Thu Feb 12 14:36:37 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 12 Feb 2015 19:36:37 +0000 Subject: [Paraview] Fwd: User trying to build with catalyst -- need guidance References: Message-ID: <17B055C9-95A5-45CE-907E-56058B74520C@llnl.gov> Dear Paraview list, Got this response from Todd Gamblin. He asked me to share it with the list. Note the two attachments ? hopefully they are not too large for the list. ? Rich Begin forwarded message: From: Todd Gamblin > Subject: Re: [Paraview] User trying to build with catalyst -- need guidance Date: February 12, 2015 at 11:16:28 AM PST To: "Cook, Rich" >, David E DeMarle > Cc: "tim.gallagher at gatech.edu" >, ParaView list > Rich, The platform files are meant to work with CMake's cross-compile support. That is similar to the build instructions here: http://www.visitusers.org/index.php?title=Building_on_BlueGeneP#Example_toolchain_file In fact I wrote the BlueGene/P support for Cmake, and I contributed it back. I have not contributed the BG/Q files back because I don't feel like I've tested them adequately. They're used by several projects though, so maybe I should just thrown them over the fence to kitware already. There are TWO platforms you can use in your toolchain file (more on that at http://www.vtk.org/Wiki/CMake_Cross_Compiling). They are: BlueGeneQ-static BlueGeneQ-dynamic There are two because a lot of people like to build backend binaries as full static executables. CMake does not have good support for this, in that it will link an executable exactly one way per platform. If you choose BlueGeneQ-static, you get a platform that has no notion of dynamic libraries and that will link executables fully static. If you use BlueGeneQ-dynamic, you get a system that is much like a standard Linux install: it supports static and dynamic libraries, but it will link *executables* as dynamic executables. This is probably the one that will be most familiar if you are used to CMake on Linux. For anyone interested, the annoyances stem from the fact that on most platforms, dynamic executables are the default, and you supply a flag (-static, -full-static, etc) to make your exe static. On BlueGene, all is reversed, the default is full static, and you supply -dynamic (gcc) or -qnostaticlink (xlc). CMake knows nothing of this w/o these platform files. Anyway, that's the deal. If you need help using these, feel free to email me. I attached some example toolchain files that I use to build dynamically on BG/Q. These are more complicated maybe than what you need: all you really need to do in a toolchain file is set CMAKE_SYSTEM_NAME and the three CMAKE__COMPILER variables. My toolchains ensure that the discovered MPI compiler is consistent with the regular compiler. -Todd From: , Rich > Date: Thursday, February 12, 2015 at 11:06 AM To: David E DeMarle > Cc: "tim.gallagher at gatech.edu" >, ParaView list >, Todd Gamblin > Subject: Re: [Paraview] User trying to build with catalyst -- need guidance Thanks for your message. I?ve poked around a bit. I have built Catalyst successfully on ?normal? Linux and our BG/Q machine front end nodes. I?m ready to try a cross compile. I came across this and was wondering if it seems right to you: http://www.vtk.org/Wiki/CmakeBlueGene We have a build of cmake that includes some extra files I don?t really understand, provided for me by our local wizard Todd Gamblin. How could I use these files to good effect? :-) It?s probably a dumb question, but I ask it to try to move in the right direction. rcook at rzuseqlac2 (bgqos_0 ): cp cmake-3.0-bgq-experimental/share/cmake-3.0/Modules/Platform/BlueGene BlueGeneL.cmake BlueGeneP-static-GNU-Fortran.cmake BlueGeneQ-dynamic-XL-CXX.cmake BlueGeneP-base.cmake BlueGeneP-static-XL-C.cmake BlueGeneQ-dynamic-XL-Fortran.cmake BlueGeneP-dynamic-GNU-C.cmake BlueGeneP-static-XL-CXX.cmake BlueGeneQ-dynamic.cmake BlueGeneP-dynamic-GNU-CXX.cmake BlueGeneP-static-XL-Fortran.cmake BlueGeneQ-static-GNU-C.cmake BlueGeneP-dynamic-GNU-Fortran.cmake BlueGeneP-static.cmake BlueGeneQ-static-GNU-CXX.cmake BlueGeneP-dynamic-XL-C.cmake BlueGeneQ-base.cmake BlueGeneQ-static-GNU-Fortran.cmake BlueGeneP-dynamic-XL-CXX.cmake BlueGeneQ-base.cmake~ BlueGeneQ-static-XL-C.cmake BlueGeneP-dynamic-XL-Fortran.cmake BlueGeneQ-dynamic-GNU-C.cmake BlueGeneQ-static-XL-CXX.cmake BlueGeneP-dynamic.cmake BlueGeneQ-dynamic-GNU-CXX.cmake BlueGeneQ-static-XL-Fortran.cmake BlueGeneP-static-GNU-C.cmake BlueGeneQ-dynamic-GNU-Fortran.cmake BlueGeneQ-static.cmake BlueGeneP-static-GNU-CXX.cmake BlueGeneQ-dynamic-XL-C.cmake On Feb 7, 2015, at 4:35 AM, David E DeMarle > wrote: I've done the BGQ ParaView + Catalyst build and installs on Mira at ANL. I can chip in with tips regarding compilation. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Feb 6, 2015 at 8:25 PM, Tim Gallagher > wrote: Hi Rich, There may be a few who are willing to help out if you can provide some specific questions or issues you run into. Have you looked through the documentation at http://www.paraview.org/in-situ/ ? I got Catalyst up and running in our code (not on a BG/Q but on different clusters) with the information in the documentation and by asking some specific questions here on the list. For me, the hardest part was converting our data into VTK data -- I did not have any exposure to VTK prior to taking the Catalyst leap. But it turned out to be (relatively) straight forward for what we are doing. I will be happy to answer things I can and for things I can't, hopefully somebody else will jump in. Tim ________________________________ From: "Rich Cook" > To: paraview at paraview.org Sent: Friday, February 6, 2015 7:23:24 PM Subject: [Paraview] User trying to build with catalyst -- need guidance Hello, We have not used catalyst here and I have a user that is interested in trying it out on our BG/Q machine with a huge code on hundreds of thousands of nodes. ;-) Is there a brave soul willing to hold our hands through this process? Thanks. -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: BlueGeneQ-gnu.cmake Type: application/octet-stream Size: 1355 bytes Desc: BlueGeneQ-gnu.cmake URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: BlueGeneQ-xl.cmake Type: application/octet-stream Size: 1542 bytes Desc: BlueGeneQ-xl.cmake URL: From utkarsh.ayachit at kitware.com Thu Feb 12 15:03:09 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 12 Feb 2015 15:03:09 -0500 Subject: [Paraview] PV 4.3.1 Color legend and Color discretization In-Reply-To: References: Message-ID: Kilian, I suspect this is indeed an issue with the labeling. The color mapping is indeed behaving as expected (I verified by creating a calculator filter and making it produce the constant of interest and then coloring by it). I've reported a bug: http://www.paraview.org/Bug/view.php?id=15319 Utkarsh On Thu, Feb 12, 2015 at 10:05 AM, Kilian Weishaupt wrote: > I am trying to use the color discretization feature in order to get a color > legend that somehow resembles the one I have attached here > (colorlegend1.png). > It features 11 regions that each represent a temperature range of 10 K. > > My first idea was to use the "Blue to Red Rainbow" preset in combination > with 11 table values and a range of 280 to 390 K (see colorlegend2.png). > Maybe I am just missing a very simple point here but the temperature ranges > (or in other words: the "boxes of different colors" on the scale) do not > seem to fit to the label ticks (especially the one at 380 K). > > I have tried various combinations of the number of table values and the > number of ticks for the color scale but none of this worked. > > Do you have any ideas? > > Best regards > Kilian > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 cook47 at llnl.gov Thu Feb 12 17:33:46 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 12 Feb 2015 22:33:46 +0000 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q Message-ID: Hello, I have made a CMAKE_TOOLCHAIN_FILE which contains the following: rcook at rzuseqlac2 (catalyst_backend_crossbuild ): cat ../backend_toolchain.cmake #===================================== set(CMAKE_SYSTEM_NAME BlueGeneQ-dynamic) set(TOOLCHAIN_LOCATION /bgsys/drivers/ppcfloor/gnu-linux/bin) set(TOOLCHAIN_PREFIX powerpc64-bgq-linux-) set(CMAKE_C_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}gcc) set(CMAKE_CXX_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}g++) set(CMAKE_Fortran_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}gfortran) #===================================== When I try to use it to compile catalyst, I get an error which arises from a file in the Catalyst distribution and which I don?t understand. Can someone ?splain it? Thanks! rcook at rzuseqlac2 (catalyst_backend_crossbuild ): /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base/cmake.sh -DCMAKE_TOOLCHAIN_FILE=/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/backend_toolchain.cmake /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base Not searching for unused variables given on the command line. -- The C compiler identification is GNU 4.4.7 -- The CXX compiler identification is GNU 4.4.7 -- Check for working C compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc -- Check for working C compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ -- Check for working CXX compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Git: /usr/bin/git (found version "1.7.1") -- Determined Source Version : 4.3.1 CMake Error at CMakeLists.txt:94 (find_package): By not providing "FindParaViewCompileTools.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "ParaViewCompileTools", but CMake did not find one. Could not find a package configuration file provided by "ParaViewCompileTools" with any of the following names: ParaViewCompileToolsConfig.cmake paraviewcompiletools-config.cmake Add the installation prefix of "ParaViewCompileTools" to CMAKE_PREFIX_PATH or set "ParaViewCompileTools_DIR" to a directory containing one of the above files. If "ParaViewCompileTools" provides a separate development package or SDK, be sure it has been installed. -- Configuring incomplete, errors occurred! See also "/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/CMakeOutput.log?. This is odd because if I do not use the toolchain file, Catalyst compiles fine ----------------------------------------------------------------------- I?m attaching the log referenced, I don?t see anything in it that tips me off. -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CMakeOutput.log Type: application/octet-stream Size: 29914 bytes Desc: CMakeOutput.log URL: From dave.demarle at kitware.com Thu Feb 12 17:57:22 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 12 Feb 2015 17:57:22 -0500 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: References: Message-ID: ParaView/Catalyst/VTK build and run some helper executables during the build process of themselves. An example is vtkWrapPython, who's job during the compile process is to parse the C++ header files and spit out additional header and cxx files that make the originals callable from python. All of those c++ files are later compiled for the target environment. In cross compilation the helper executables have to be compiled to run in the host environment. The source code that the helpers produce has to be compiled to run in the compute environment. So build paraview (or better yet just the CompileTools target to save time) once for the host. Then in a different directory build paraview again, using the toolchain you are now using to tell it what compilers and libraries to use for the compute nodes, and in this build tell cmake where the host tools can be found. See the ParaViewSuperbuild project's CMake/crosscompile/bgq_gnu directory for how I set this up on mira. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Feb 12, 2015 at 5:33 PM, Cook, Rich wrote: > Hello, > I have made a CMAKE_TOOLCHAIN_FILE which contains the following: > > rcook at rzuseqlac2 (catalyst_backend_crossbuild ): cat > ../backend_toolchain.cmake > #===================================== > set(CMAKE_SYSTEM_NAME BlueGeneQ-dynamic) > > set(TOOLCHAIN_LOCATION /bgsys/drivers/ppcfloor/gnu-linux/bin) > set(TOOLCHAIN_PREFIX powerpc64-bgq-linux-) > > set(CMAKE_C_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}gcc) > set(CMAKE_CXX_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}g++) > set(CMAKE_Fortran_COMPILER > ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}gfortran) > #===================================== > > When I try to use it to compile catalyst, I get an error which arises > from a file in the Catalyst distribution and which I don?t understand. Can > someone ?splain it? Thanks! > > rcook at rzuseqlac2 (catalyst_backend_crossbuild ): > /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base/cmake.sh > -DCMAKE_TOOLCHAIN_FILE=/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/backend_toolchain.cmake > /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base > Not searching for unused variables given on the command line. > -- The C compiler identification is GNU 4.4.7 > -- The CXX compiler identification is GNU 4.4.7 > -- Check for working C compiler: > /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc > -- Check for working C compiler: > /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Detecting C compile features > -- Detecting C compile features - done > -- Check for working CXX compiler: > /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ > -- Check for working CXX compiler: > /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Found Git: /usr/bin/git (found version "1.7.1") > -- Determined Source Version : 4.3.1 > CMake Error at CMakeLists.txt:94 (find_package): > By not providing "FindParaViewCompileTools.cmake" in CMAKE_MODULE_PATH > this > project has asked CMake to find a package configuration file provided by > "ParaViewCompileTools", but CMake did not find one. > > Could not find a package configuration file provided by > "ParaViewCompileTools" with any of the following names: > > ParaViewCompileToolsConfig.cmake > paraviewcompiletools-config.cmake > > Add the installation prefix of "ParaViewCompileTools" to > CMAKE_PREFIX_PATH > or set "ParaViewCompileTools_DIR" to a directory containing one of the > above files. If "ParaViewCompileTools" provides a separate development > package or SDK, be sure it has been installed. > > > -- Configuring incomplete, errors occurred! > See also > "/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/CMakeOutput.log?. > > This is odd because if I do not use the toolchain file, Catalyst > compiles fine > ----------------------------------------------------------------------- > I?m attaching the log referenced, I don?t see anything in it that tips me > off. > > > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 cook47 at llnl.gov Thu Feb 12 18:32:52 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 12 Feb 2015 23:32:52 +0000 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: References: Message-ID: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> OK, thanks, that gets me a bit farther. I pointed it at a successful build of Catalyst. But now when I run cmake.sh, I get this error (and more later) -- Performing Test Support for 64 bit file systems CMake Error: TRY_RUN() invoked in cross-compiling mode, please set the following cache variables appropriately: CMAKE_REQUIRE_LARGE_FILE_SUPPORT (advanced) CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT (advanced) ? CMake Error: TRY_RUN() invoked in cross-compiling mode, please set the following cache variables appropriately: VTK_TYPE_CHAR_IS_SIGNED (advanced) For details see /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/TryRunResults.cmake What am I to make of these cryptic errors? Thanks ? Rich On Feb 12, 2015, at 2:57 PM, David E DeMarle > wrote: ParaView/Catalyst/VTK build and run some helper executables during the build process of themselves. An example is vtkWrapPython, who's job during the compile process is to parse the C++ header files and spit out additional header and cxx files that make the originals callable from python. All of those c++ files are later compiled for the target environment. In cross compilation the helper executables have to be compiled to run in the host environment. The source code that the helpers produce has to be compiled to run in the compute environment. So build paraview (or better yet just the CompileTools target to save time) once for the host. Then in a different directory build paraview again, using the toolchain you are now using to tell it what compilers and libraries to use for the compute nodes, and in this build tell cmake where the host tools can be found. See the ParaViewSuperbuild project's CMake/crosscompile/bgq_gnu directory for how I set this up on mira. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Feb 12, 2015 at 5:33 PM, Cook, Rich > wrote: Hello, I have made a CMAKE_TOOLCHAIN_FILE which contains the following: rcook at rzuseqlac2 (catalyst_backend_crossbuild ): cat ../backend_toolchain.cmake #===================================== set(CMAKE_SYSTEM_NAME BlueGeneQ-dynamic) set(TOOLCHAIN_LOCATION /bgsys/drivers/ppcfloor/gnu-linux/bin) set(TOOLCHAIN_PREFIX powerpc64-bgq-linux-) set(CMAKE_C_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}gcc) set(CMAKE_CXX_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}g++) set(CMAKE_Fortran_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}gfortran) #===================================== When I try to use it to compile catalyst, I get an error which arises from a file in the Catalyst distribution and which I don?t understand. Can someone ?splain it? Thanks! rcook at rzuseqlac2 (catalyst_backend_crossbuild ): /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base/cmake.sh -DCMAKE_TOOLCHAIN_FILE=/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/backend_toolchain.cmake /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base Not searching for unused variables given on the command line. -- The C compiler identification is GNU 4.4.7 -- The CXX compiler identification is GNU 4.4.7 -- Check for working C compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc -- Check for working C compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ -- Check for working CXX compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Git: /usr/bin/git (found version "1.7.1") -- Determined Source Version : 4.3.1 CMake Error at CMakeLists.txt:94 (find_package): By not providing "FindParaViewCompileTools.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "ParaViewCompileTools", but CMake did not find one. Could not find a package configuration file provided by "ParaViewCompileTools" with any of the following names: ParaViewCompileToolsConfig.cmake paraviewcompiletools-config.cmake Add the installation prefix of "ParaViewCompileTools" to CMAKE_PREFIX_PATH or set "ParaViewCompileTools_DIR" to a directory containing one of the above files. If "ParaViewCompileTools" provides a separate development package or SDK, be sure it has been installed. -- Configuring incomplete, errors occurred! See also "/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/CMakeOutput.log?. This is odd because if I do not use the toolchain file, Catalyst compiles fine ----------------------------------------------------------------------- I?m attaching the log referenced, I don?t see anything in it that tips me off. -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Feb 12 19:08:18 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 12 Feb 2015 19:08:18 -0500 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> References: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> Message-ID: These come from the way our build scripts ask cmake to runs _more_ helper executables at build time in order to introspect the machine that the code is going to run on (is it big or little endian, how big is a double on this CPU?, does the MPI there support feature X and stuff like that). In a host only build these aren't a problem, just build, run and take the output of the helper and continue. In a cross compile build it isn't so easy. The answers on the host and compute may be different (ex on a BGL or P), worse cmake can build it, but it does't know anything about how to submit a job to run the executable and then get results back from it. If you look at: /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/ catalyst_backend_crossbuild/TryRunResults.cmake It says things to the effect of: run this executable on the compute node, and paste its output back into this variable. You can do that, or copy someone else's answers for the test on a BGQ (see the PVSB/cmake/crosscompile/bgq_gnu/*TryRunResults.cmake), or fill in the details from what you know about the compute node architecture. However you do it, once you fill in that form just make again in the build tree, cmake will see that you've given it the details it needs, and finish. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Feb 12, 2015 at 6:32 PM, Cook, Rich wrote: > OK, thanks, that gets me a bit farther. I pointed it at a successful > build of Catalyst. But now when I run cmake.sh, I get this error (and more > later) > > -- Performing Test Support for 64 bit file systems > CMake Error: TRY_RUN() invoked in cross-compiling mode, please set the > following cache variables appropriately: > CMAKE_REQUIRE_LARGE_FILE_SUPPORT (advanced) > CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT (advanced) > ? > CMake Error: TRY_RUN() invoked in cross-compiling mode, please set the > following cache variables appropriately: > VTK_TYPE_CHAR_IS_SIGNED (advanced) > For details see > /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/TryRunResults.cmake > > What am I to make of these cryptic errors? > Thanks > ? Rich > > On Feb 12, 2015, at 2:57 PM, David E DeMarle > wrote: > > ParaView/Catalyst/VTK build and run some helper executables during the > build process of themselves. An example is vtkWrapPython, who's job during > the compile process is to parse the C++ header files and spit out > additional header and cxx files that make the originals callable from > python. All of those c++ files are later compiled for the target > environment. > > In cross compilation the helper executables have to be compiled to run > in the host environment. > The source code that the helpers produce has to be compiled to run in the > compute environment. > > So build paraview (or better yet just the CompileTools target to save > time) once for the host. > Then in a different directory build paraview again, using the toolchain > you are now using to tell it what compilers and libraries to use for the > compute nodes, and in this build tell cmake where the host tools can be > found. > > See the ParaViewSuperbuild project's CMake/crosscompile/bgq_gnu > directory for how I set this up on mira. > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Thu, Feb 12, 2015 at 5:33 PM, Cook, Rich wrote: > >> Hello, >> I have made a CMAKE_TOOLCHAIN_FILE which contains the following: >> >> rcook at rzuseqlac2 (catalyst_backend_crossbuild ): cat >> ../backend_toolchain.cmake >> #===================================== >> set(CMAKE_SYSTEM_NAME BlueGeneQ-dynamic) >> >> set(TOOLCHAIN_LOCATION /bgsys/drivers/ppcfloor/gnu-linux/bin) >> set(TOOLCHAIN_PREFIX powerpc64-bgq-linux-) >> >> set(CMAKE_C_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}gcc) >> set(CMAKE_CXX_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}g++) >> set(CMAKE_Fortran_COMPILER >> ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}gfortran) >> #===================================== >> >> When I try to use it to compile catalyst, I get an error which arises >> from a file in the Catalyst distribution and which I don?t understand. Can >> someone ?splain it? Thanks! >> >> rcook at rzuseqlac2 (catalyst_backend_crossbuild ): >> /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base/cmake.sh >> -DCMAKE_TOOLCHAIN_FILE=/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/backend_toolchain.cmake >> /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base >> Not searching for unused variables given on the command line. >> -- The C compiler identification is GNU 4.4.7 >> -- The CXX compiler identification is GNU 4.4.7 >> -- Check for working C compiler: >> /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc >> -- Check for working C compiler: >> /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc -- works >> -- Detecting C compiler ABI info >> -- Detecting C compiler ABI info - done >> -- Detecting C compile features >> -- Detecting C compile features - done >> -- Check for working CXX compiler: >> /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ >> -- Check for working CXX compiler: >> /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ -- works >> -- Detecting CXX compiler ABI info >> -- Detecting CXX compiler ABI info - done >> -- Detecting CXX compile features >> -- Detecting CXX compile features - done >> -- Found Git: /usr/bin/git (found version "1.7.1") >> -- Determined Source Version : 4.3.1 >> CMake Error at CMakeLists.txt:94 (find_package): >> By not providing "FindParaViewCompileTools.cmake" in CMAKE_MODULE_PATH >> this >> project has asked CMake to find a package configuration file provided by >> "ParaViewCompileTools", but CMake did not find one. >> >> Could not find a package configuration file provided by >> "ParaViewCompileTools" with any of the following names: >> >> ParaViewCompileToolsConfig.cmake >> paraviewcompiletools-config.cmake >> >> Add the installation prefix of "ParaViewCompileTools" to >> CMAKE_PREFIX_PATH >> or set "ParaViewCompileTools_DIR" to a directory containing one of the >> above files. If "ParaViewCompileTools" provides a separate development >> package or SDK, be sure it has been installed. >> >> >> -- Configuring incomplete, errors occurred! >> See also >> "/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/CMakeOutput.log?. >> >> This is odd because if I do not use the toolchain file, Catalyst >> compiles fine >> ----------------------------------------------------------------------- >> I?m attaching the log referenced, I don?t see anything in it that tips me >> off. >> >> >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA >> ? (office) (925) 423-9605 >> ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., >> Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Thu Feb 12 19:15:11 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Fri, 13 Feb 2015 00:15:11 +0000 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: References: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> Message-ID: Hmm, it does not say to run any executables. I really don?t understand what it?s asking me for so I don?t know what to just stick in the variables. Here is an example from that file: # CMAKE_REQUIRE_LARGE_FILE_SUPPORT # indicates whether the executable would have been able to run on its # target platform. If so, set CMAKE_REQUIRE_LARGE_FILE_SUPPORT to # the exit code (in many cases 0 for success), otherwise enter "FAILED_TO_RUN". # CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT # contains the text the executable would have printed on stdout and stderr. # If the executable would not have been able to run, set CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT empty. # Otherwise check if the output is evaluated by the calling CMake code. If so, # check what the source file would have printed when called with the given arguments. # The HAVE_CMAKE_REQUIRE_LARGE_FILE_SUPPORT variable holds the build result for this TRY_RUN(). # # Source file : /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/CMakeTmp/src.cxx # Executable : /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT # Run arguments : # Called from: [1] /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base/VTK/CMakeLists.txt set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT "PLEASE_FILL_OUT-FAILED_TO_RUN" CACHE STRING "Result from TRY_RUN" FORCE) set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "PLEASE_FILL_OUT-NOTFOUND" CACHE STRING "Output from TRY_RUN" FORCE) On Feb 12, 2015, at 4:08 PM, David E DeMarle > wrote: These come from the way our build scripts ask cmake to runs _more_ helper executables at build time in order to introspect the machine that the code is going to run on (is it big or little endian, how big is a double on this CPU?, does the MPI there support feature X and stuff like that). In a host only build these aren't a problem, just build, run and take the output of the helper and continue. In a cross compile build it isn't so easy. The answers on the host and compute may be different (ex on a BGL or P), worse cmake can build it, but it does't know anything about how to submit a job to run the executable and then get results back from it. If you look at: /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/TryRunResults.cmake It says things to the effect of: run this executable on the compute node, and paste its output back into this variable. You can do that, or copy someone else's answers for the test on a BGQ (see the PVSB/cmake/crosscompile/bgq_gnu/*TryRunResults.cmake), or fill in the details from what you know about the compute node architecture. However you do it, once you fill in that form just make again in the build tree, cmake will see that you've given it the details it needs, and finish. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Feb 12, 2015 at 6:32 PM, Cook, Rich > wrote: OK, thanks, that gets me a bit farther. I pointed it at a successful build of Catalyst. But now when I run cmake.sh, I get this error (and more later) -- Performing Test Support for 64 bit file systems CMake Error: TRY_RUN() invoked in cross-compiling mode, please set the following cache variables appropriately: CMAKE_REQUIRE_LARGE_FILE_SUPPORT (advanced) CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT (advanced) ? CMake Error: TRY_RUN() invoked in cross-compiling mode, please set the following cache variables appropriately: VTK_TYPE_CHAR_IS_SIGNED (advanced) For details see /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/TryRunResults.cmake What am I to make of these cryptic errors? Thanks ? Rich On Feb 12, 2015, at 2:57 PM, David E DeMarle > wrote: ParaView/Catalyst/VTK build and run some helper executables during the build process of themselves. An example is vtkWrapPython, who's job during the compile process is to parse the C++ header files and spit out additional header and cxx files that make the originals callable from python. All of those c++ files are later compiled for the target environment. In cross compilation the helper executables have to be compiled to run in the host environment. The source code that the helpers produce has to be compiled to run in the compute environment. So build paraview (or better yet just the CompileTools target to save time) once for the host. Then in a different directory build paraview again, using the toolchain you are now using to tell it what compilers and libraries to use for the compute nodes, and in this build tell cmake where the host tools can be found. See the ParaViewSuperbuild project's CMake/crosscompile/bgq_gnu directory for how I set this up on mira. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Feb 12, 2015 at 5:33 PM, Cook, Rich > wrote: Hello, I have made a CMAKE_TOOLCHAIN_FILE which contains the following: rcook at rzuseqlac2 (catalyst_backend_crossbuild ): cat ../backend_toolchain.cmake #===================================== set(CMAKE_SYSTEM_NAME BlueGeneQ-dynamic) set(TOOLCHAIN_LOCATION /bgsys/drivers/ppcfloor/gnu-linux/bin) set(TOOLCHAIN_PREFIX powerpc64-bgq-linux-) set(CMAKE_C_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}gcc) set(CMAKE_CXX_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}g++) set(CMAKE_Fortran_COMPILER ${TOOLCHAIN_LOCATION}/${TOOLCHAIN_PREFIX}gfortran) #===================================== When I try to use it to compile catalyst, I get an error which arises from a file in the Catalyst distribution and which I don?t understand. Can someone ?splain it? Thanks! rcook at rzuseqlac2 (catalyst_backend_crossbuild ): /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base/cmake.sh -DCMAKE_TOOLCHAIN_FILE=/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/backend_toolchain.cmake /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/base Not searching for unused variables given on the command line. -- The C compiler identification is GNU 4.4.7 -- The CXX compiler identification is GNU 4.4.7 -- Check for working C compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc -- Check for working C compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ -- Check for working CXX compiler: /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-g++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Git: /usr/bin/git (found version "1.7.1") -- Determined Source Version : 4.3.1 CMake Error at CMakeLists.txt:94 (find_package): By not providing "FindParaViewCompileTools.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "ParaViewCompileTools", but CMake did not find one. Could not find a package configuration file provided by "ParaViewCompileTools" with any of the following names: ParaViewCompileToolsConfig.cmake paraviewcompiletools-config.cmake Add the installation prefix of "ParaViewCompileTools" to CMAKE_PREFIX_PATH or set "ParaViewCompileTools_DIR" to a directory containing one of the above files. If "ParaViewCompileTools" provides a separate development package or SDK, be sure it has been installed. -- Configuring incomplete, errors occurred! See also "/collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/CMakeOutput.log?. This is odd because if I do not use the toolchain file, Catalyst compiles fine ----------------------------------------------------------------------- I?m attaching the log referenced, I don?t see anything in it that tips me off. -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Feb 12 19:19:20 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 12 Feb 2015 19:19:20 -0500 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: References: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> Message-ID: On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich wrote: > > /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT > Is the name of the executable to run. set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT > "PLEASE_FILL_OUT-FAILED_TO_RUN" > CACHE STRING "Result from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT 0 CACHE STRING "Result from TRY_RUN" FORCE) if the return code of that executable is 0 set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT > "PLEASE_FILL_OUT-NOTFOUND" > CACHE STRING "Output from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "I am the very model of a modern major general" CACHE STRING "Output from TRY_RUN" FORCE) If the console output of that executable was "I am the very model of a modern major general" David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Thu Feb 12 19:59:05 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Fri, 13 Feb 2015 00:59:05 +0000 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: References: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> Message-ID: <3F732214-8FB7-40D0-A626-ED7B50EE90CE@llnl.gov> Thanks for all your help! I?m now getting a compiler error. I?m checking with the code developer to determine which compiler chain he uses for his build. But if I wanted to add an argument to the compiler, how would I do so? Building CXX object VTK/IO/Core/CMakeFiles/vtkIOCoreObjects.dir/vtkArrayDataWriter.cxx.o [ 28%] Built target vtkFiltersCoreObjects /bgsys/drivers/toolchain/V1R2M2_base/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.7/../../../../powerpc64-bgq-linux/bin/ld: Common/DataModel/CMakeFiles/vtkCommonDataModelObjects.dir/vtkXMLDataElement.cxx.o(.text+0x2c7c): sibling call optimization to `std::basic_stringbuf, std::allocator >::~basic_stringbuf()' does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or make `std::basic_stringbuf, std::allocator >::~basic_stringbuf()' extern /bgsys/drivers/toolchain/V1R2M2_base/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.7/../../../../powerpc64-bgq-linux/bin/ld: Common/DataModel/CMakeFiles/vtkCommonDataModelObjects.dir/vtkXMLDataElement.cxx.o(.text+0x3880): sibling call optimization to `std::basic_stringbuf, std::allocator >::~basic_stringbuf()' does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or make `std::basic_stringbuf, std::allocator >::~basic_stringbuf()' extern /bgsys/drivers/toolchain/V1R2M2_base/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.7/../../../../powerpc64-bgq-linux/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status make[2]: *** [lib/libvtkCommon-pv4.3.so.1] Error 1 make[1]: *** [VTK/CMakeFiles/vtkCommon.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... [ 28%] Built target vtkIOCoreObjects make: *** [all] Error 2 On Feb 12, 2015, at 4:19 PM, David E DeMarle > wrote: On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich > wrote: /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT Is the name of the executable to run. set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT "PLEASE_FILL_OUT-FAILED_TO_RUN" CACHE STRING "Result from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT 0 CACHE STRING "Result from TRY_RUN" FORCE) if the return code of that executable is 0 set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "PLEASE_FILL_OUT-NOTFOUND" CACHE STRING "Output from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "I am the very model of a modern major general" CACHE STRING "Output from TRY_RUN" FORCE) If the console output of that executable was "I am the very model of a modern major general" David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Feb 12 20:12:00 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 12 Feb 2015 20:12:00 -0500 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: <3F732214-8FB7-40D0-A626-ED7B50EE90CE@llnl.gov> References: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> <3F732214-8FB7-40D0-A626-ED7B50EE90CE@llnl.gov> Message-ID: On Thu, Feb 12, 2015 at 7:59 PM, Cook, Rich wrote: > Thanks for all your help! > Sure. Looking forward to having it run on that monster. > I?m now getting a compiler error. I?m checking with the code developer to > determine which compiler chain he uses for his build. But if I wanted to > add an argument to the compiler, how would I do so? > > In the CMakeCache.txt of the cross build directory, add them to CMAKE_CXX_FLAGS and such. Or pass them in via -D when you start off. Building CXX object > VTK/IO/Core/CMakeFiles/vtkIOCoreObjects.dir/vtkArrayDataWriter.cxx.o > [ 28%] Built target vtkFiltersCoreObjects > /bgsys/drivers/toolchain/V1R2M2_base/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.7/../../../../powerpc64-bgq-linux/bin/ld: > Common/DataModel/CMakeFiles/vtkCommonDataModelObjects.dir/vtkXMLDataElement.cxx.o(.text+0x2c7c): > sibling call optimization to `std::basic_stringbuf std::char_traits, std::allocator >::~basic_stringbuf()' does > not allow automatic multiple TOCs; recompile with -mminimal-toc or > -fno-optimize-sibling-calls, or make `std::basic_stringbuf std::char_traits, std::allocator >::~basic_stringbuf()' extern > /bgsys/drivers/toolchain/V1R2M2_base/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.7/../../../../powerpc64-bgq-linux/bin/ld: > Common/DataModel/CMakeFiles/vtkCommonDataModelObjects.dir/vtkXMLDataElement.cxx.o(.text+0x3880): > sibling call optimization to `std::basic_stringbuf std::char_traits, std::allocator >::~basic_stringbuf()' does > not allow automatic multiple TOCs; recompile with -mminimal-toc or > -fno-optimize-sibling-calls, or make `std::basic_stringbuf std::char_traits, std::allocator >::~basic_stringbuf()' extern > /bgsys/drivers/toolchain/V1R2M2_base/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.7/../../../../powerpc64-bgq-linux/bin/ld: > final link failed: Bad value > collect2: ld returned 1 exit status > > Scary one there. I still have nightmares about "-mminimal-toc or -fno-optimize-sibling-calls". I started on Mira with XLC and banged my head against a very similar failure. In my case it no matter what I did it always failed to link pvbatch and other big executables. I never did fix it and instead switched over to the gnu compilers. If you get stuck similarly it may be time to call for backup from IBM. > On Feb 12, 2015, at 4:19 PM, David E DeMarle > wrote: > > > On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich wrote: > >> >> /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT > > > Is the name of the executable to run. > > set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT >> "PLEASE_FILL_OUT-FAILED_TO_RUN" >> CACHE STRING "Result from TRY_RUN" FORCE) > > > Change that to: > set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT > 0 > CACHE STRING "Result from TRY_RUN" FORCE) > > if the return code of that executable is 0 > > set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT >> "PLEASE_FILL_OUT-NOTFOUND" >> CACHE STRING "Output from TRY_RUN" FORCE) > > > Change that to: > set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT > "I am the very model of a modern major general" > CACHE STRING "Output from TRY_RUN" FORCE) > > If the console output of that executable was "I am the very model of a > modern major general" > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Thu Feb 12 20:18:25 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Fri, 13 Feb 2015 01:18:25 +0000 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: References: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> <3F732214-8FB7-40D0-A626-ED7B50EE90CE@llnl.gov> Message-ID: Thanks for the secret sauce again. Now that you mention it, I do remember now large_toc errors trying to get paraview building on our old AIX machine ?purple? a while back. Needed extensive hand-holding then. But this is gcc and friends, so perhaps GNU has gotten a bit pickier, or been infected with the AIX virus. On Feb 12, 2015, at 5:12 PM, David E DeMarle > wrote: On Thu, Feb 12, 2015 at 7:59 PM, Cook, Rich > wrote: Thanks for all your help! Sure. Looking forward to having it run on that monster. I?m now getting a compiler error. I?m checking with the code developer to determine which compiler chain he uses for his build. But if I wanted to add an argument to the compiler, how would I do so? In the CMakeCache.txt of the cross build directory, add them to CMAKE_CXX_FLAGS and such. Or pass them in via -D when you start off. Building CXX object VTK/IO/Core/CMakeFiles/vtkIOCoreObjects.dir/vtkArrayDataWriter.cxx.o [ 28%] Built target vtkFiltersCoreObjects /bgsys/drivers/toolchain/V1R2M2_base/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.7/../../../../powerpc64-bgq-linux/bin/ld: Common/DataModel/CMakeFiles/vtkCommonDataModelObjects.dir/vtkXMLDataElement.cxx.o(.text+0x2c7c): sibling call optimization to `std::basic_stringbuf, std::allocator >::~basic_stringbuf()' does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or make `std::basic_stringbuf, std::allocator >::~basic_stringbuf()' extern /bgsys/drivers/toolchain/V1R2M2_base/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.7/../../../../powerpc64-bgq-linux/bin/ld: Common/DataModel/CMakeFiles/vtkCommonDataModelObjects.dir/vtkXMLDataElement.cxx.o(.text+0x3880): sibling call optimization to `std::basic_stringbuf, std::allocator >::~basic_stringbuf()' does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or make `std::basic_stringbuf, std::allocator >::~basic_stringbuf()' extern /bgsys/drivers/toolchain/V1R2M2_base/gnu-linux/lib/gcc/powerpc64-bgq-linux/4.4.7/../../../../powerpc64-bgq-linux/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status Scary one there. I still have nightmares about "-mminimal-toc or -fno-optimize-sibling-calls". I started on Mira with XLC and banged my head against a very similar failure. In my case it no matter what I did it always failed to link pvbatch and other big executables. I never did fix it and instead switched over to the gnu compilers. If you get stuck similarly it may be time to call for backup from IBM. On Feb 12, 2015, at 4:19 PM, David E DeMarle > wrote: On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich > wrote: /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT Is the name of the executable to run. set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT "PLEASE_FILL_OUT-FAILED_TO_RUN" CACHE STRING "Result from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT 0 CACHE STRING "Result from TRY_RUN" FORCE) if the return code of that executable is 0 set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "PLEASE_FILL_OUT-NOTFOUND" CACHE STRING "Output from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "I am the very model of a modern major general" CACHE STRING "Output from TRY_RUN" FORCE) If the console output of that executable was "I am the very model of a modern major general" David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From biddisco at cscs.ch Fri Feb 13 01:55:59 2015 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Fri, 13 Feb 2015 06:55:59 +0000 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: References: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> Message-ID: <50320452A334BD42A5EC72BAD214509924EFE672@MBX210.d.ethz.ch> Rich On the BGQ, the compute nodes and login nodes are binary compatible, so you shouldn?t need to bother with most of the cross compiling stuff. the only thing to watch out for is the MPI and since vtkParseOGLExt and vtkWrapPython etc don?t touch that, you ought to be ok compiling _as if_ you were going to run on the host node. If you use the MPI wrappers (I don?t), then all will be taken care of. I don?t think that I have compiled pv+catalyst to run on BGQ, so my comment is only based on theory, but I can set a build going in a minute if it helps (except I?d need to setup mesa which may take a while, so maybe I won?t....) JB From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of David E DeMarle Sent: 13 February 2015 01:19 To: Cook, Rich Cc: ParaView list Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich > wrote: /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT Is the name of the executable to run. set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT "PLEASE_FILL_OUT-FAILED_TO_RUN" CACHE STRING "Result from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT 0 CACHE STRING "Result from TRY_RUN" FORCE) if the return code of that executable is 0 set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "PLEASE_FILL_OUT-NOTFOUND" CACHE STRING "Output from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "I am the very model of a modern major general" CACHE STRING "Output from TRY_RUN" FORCE) If the console output of that executable was "I am the very model of a modern major general" David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From j.dubsky at centrum.cz Fri Feb 13 06:03:55 2015 From: j.dubsky at centrum.cz (j.dubsky at centrum.cz) Date: Fri, 13 Feb 2015 12:03:55 +0100 Subject: [Paraview] =?utf-8?q?Loading_whole_time_series_in_ParaView_at_onc?= =?utf-8?q?e?= Message-ID: <20150213120355.A8F67F76@centrum.cz> Hi, I'm currently struggling with one problem in ParaView, where I didn't find any solution up to now. My problem looks like this: I have a transient OpenFOAM simulation and want to do postprocessing of my results. This itself is not a big problem. I can load the data and switch between the timesteps and it works. The problem is, that it works terribly slowly. As far as I understand it, the way how this work is, that with every switching from one step to the other Paraview has to load the results and the mesh every time. What I would prefere much more would be the option to let ParaView load all the time steps at once. Of course this would need much more resources, but exactly with the resources I'm not really limited (having a huge cluster with ~500 nodes). Therefore loading the whole time series and having the possibility to switch between the timesteps quickly without having to load the mesh/data all the time would be a great improvement for me. Is there any way how this could be done, or is it something that ParaView has not really been designed for? For example ine Ensight I do have this option and it makes the work with the transient results much better. Many thanks in advance for any help or advice on this issue. Regards Josef From yj.wang216 at gmail.com Fri Feb 13 07:14:49 2015 From: yj.wang216 at gmail.com (youjiang.wang) Date: Fri, 13 Feb 2015 13:14:49 +0100 Subject: [Paraview] Round off the fractional part when read from tecplot file Message-ID: <54DDEAB9.6080208@gmail.com> Hi, man Previously, there was no problem with my paraview. But yesterday, after I installed Kile (a latex editor), the paraview could not read the data from tecplot file correctly. The fractional part of my value is rounded off. This makes the smooth body look ugly. I have already removed the software Kile, but the problem is still unsolved. Have you encountered such a situation? Or do you know how to resolve it? The paraview version is 4.0.1, my OS is Ubuntu 14.04. Best Regards Wang From dkxls23 at gmail.com Fri Feb 13 07:40:14 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Fri, 13 Feb 2015 14:40:14 +0200 Subject: [Paraview] Loading whole time series in ParaView at once In-Reply-To: <20150213120355.A8F67F76@centrum.cz> References: <20150213120355.A8F67F76@centrum.cz> Message-ID: <54DDF0AE.4030509@gmail.com> Hi, I cannot directly answer your question, but I have a few remarks/questions: Which reader are you using for your OpenFOAM cases? There are two OpenFOAM readers for ParaView, a) the built-in reader in ParaView (file ending .foam) and b) the reader supplied with OpenFOAM (file ending .OpenFOAM). For my cases the built-in reader works much faster/efficient than the one from OpenFOAM (but that may very well be cases specific). With the ParaView built-in reader you also have the option to cache the mesh in memory. If you use the OpenFOAM command "paraFoam" you will by default use the reader that comes with OpenFOAM. To use the built-in reader from ParaView use "paraFoam -builtin". Alternatively just create a file with either ending (.foam or .OpenFOAM) to switch between the readers. -Armin On 02/13/2015 01:03 PM, j.dubsky at centrum.cz wrote: > Hi, I'm currently struggling with one problem in ParaView, where I > didn't find any solution up to now. > > My problem looks like this: I have a transient OpenFOAM simulation > and want to do postprocessing of my results. This itself is not a big > problem. I can load the data and switch between the timesteps and it > works. The problem is, that it works terribly slowly. As far as I > understand it, the way how this work is, that with every switching > from one step to the other Paraview has to load the results and the > mesh every time. > > What I would prefere much more would be the option to let ParaView > load all the time steps at once. Of course this would need much more > resources, but exactly with the resources I'm not really limited > (having a huge cluster with ~500 nodes). > > Therefore loading the whole time series and having the possibility to > switch between the timesteps quickly without having to load the > mesh/data all the time would be a great improvement for me. > > Is there any way how this could be done, or is it something that > ParaView has not really been designed for? For example ine Ensight I > do have this option and it makes the work with the transient results > much better. > > Many thanks in advance for any help or advice on this issue. > > Regards > > Josef _______________________________________________ Powered by > www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From dave.demarle at kitware.com Fri Feb 13 07:47:36 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 13 Feb 2015 07:47:36 -0500 Subject: [Paraview] Round off the fractional part when read from tecplot file In-Reply-To: <54DDEAB9.6080208@gmail.com> References: <54DDEAB9.6080208@gmail.com> Message-ID: Sounds like a locale problem. Specifically using "," versus "." for decimal point. Tweaking related environment settings on your system should get you back in business. On Friday, February 13, 2015, youjiang.wang wrote: > Hi, man > > Previously, there was no problem with my paraview. But yesterday, after I > installed Kile (a latex editor), the paraview could not read the data from > tecplot file correctly. The fractional part of my value is rounded off. > This makes the smooth body look ugly. > > I have already removed the software Kile, but the problem is still > unsolved. > > Have you encountered such a situation? Or do you know how to resolve it? > > The paraview version is 4.0.1, my OS is Ubuntu 14.04. > > Best Regards > Wang > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From j.dubsky at centrum.cz Fri Feb 13 08:07:07 2015 From: j.dubsky at centrum.cz (j.dubsky at centrum.cz) Date: Fri, 13 Feb 2015 14:07:07 +0100 Subject: [Paraview] =?utf-8?q?Loading_whole_time_series_in_ParaView_at_onc?= =?utf-8?q?e?= In-Reply-To: <54DDF0AE.4030509@gmail.com> References: <20150213120355.A8F67F76@centrum.cz> <54DDF0AE.4030509@gmail.com> Message-ID: <20150213140707.0D848F1E@centrum.cz> Hi Armin, thanks for your reply. I'm using the ParaView builtin reader. I always do "touch xxx.foam" in my OpenFOAM folder and after this I just start the paraview binary. But actually I'm not sure if this is the problem of the reader or ParaView itself. We have the same problem when loading other data formats too. Paraview always loads the time steps one by one. This is quite annoying if you're switching from one step to the other. I would be also happy to convert the OpenFOAM output to any other format, that would allow me to load the whole time series in memory, which would make the switching from one timestep to the other fast. However I didn't try the option you've mention. How can I tell ParaView to cache at least the mesh in memory? Regards Josef ______________________________________________________________ > Od: Armin Wehrfritz > Komu: > Datum: 13.02.2015 13:40 > P?edm?t: Re: [Paraview] Loading whole time series in ParaView at once > >Hi, > >I cannot directly answer your question, but I have a few remarks/questions: > >Which reader are you using for your OpenFOAM cases? > >There are two OpenFOAM readers for ParaView, a) the built-in reader in >ParaView (file ending .foam) and b) the reader supplied with OpenFOAM >(file ending .OpenFOAM). > >For my cases the built-in reader works much faster/efficient than the >one from OpenFOAM (but that may very well be cases specific). >With the ParaView built-in reader you also have the option to cache the >mesh in memory. > >If you use the OpenFOAM command "paraFoam" you will by default use the >reader that comes with OpenFOAM. To use the built-in reader from >ParaView use "paraFoam -builtin". >Alternatively just create a file with either ending (.foam or .OpenFOAM) >to switch between the readers. > > >-Armin > > > > > >On 02/13/2015 01:03 PM, j.dubsky at centrum.cz wrote: >> Hi, I'm currently struggling with one problem in ParaView, where I >> didn't find any solution up to now. >> >> My problem looks like this: I have a transient OpenFOAM simulation >> and want to do postprocessing of my results. This itself is not a big >> problem. I can load the data and switch between the timesteps and it >> works. The problem is, that it works terribly slowly. As far as I >> understand it, the way how this work is, that with every switching >> from one step to the other Paraview has to load the results and the >> mesh every time. >> >> What I would prefere much more would be the option to let ParaView >> load all the time steps at once. Of course this would need much more >> resources, but exactly with the resources I'm not really limited >> (having a huge cluster with ~500 nodes). >> >> Therefore loading the whole time series and having the possibility to >> switch between the timesteps quickly without having to load the >> mesh/data all the time would be a great improvement for me. >> >> Is there any way how this could be done, or is it something that >> ParaView has not really been designed for? For example ine Ensight I >> do have this option and it makes the work with the transient results >> much better. >> >> Many thanks in advance for any help or advice on this issue. >> >> Regards >> >> Josef _______________________________________________ Powered by >> www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 dkxls23 at gmail.com Fri Feb 13 08:23:25 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Fri, 13 Feb 2015 15:23:25 +0200 Subject: [Paraview] Loading whole time series in ParaView at once In-Reply-To: <20150213140707.0D848F1E@centrum.cz> References: <20150213120355.A8F67F76@centrum.cz> <54DDF0AE.4030509@gmail.com> <20150213140707.0D848F1E@centrum.cz> Message-ID: <54DDFACD.5080609@gmail.com> > thanks for your reply. I'm using the ParaView builtin reader. I > always do "touch xxx.foam" in my OpenFOAM folder and after this I > just start the paraview binary. > > But actually I'm not sure if this is the problem of the reader or > ParaView itself. We have the same problem when loading other data > formats too. Paraview always loads the time steps one by one. This is > quite annoying if you're switching from one step to the other. I agree, the "loading of a whole time series" issue is a ParaView limitation/feature and most likely not reader specific. > However I didn't try the option you've mention. How can I tell > ParaView to cache at least the mesh in memory? For the built-in ParaView reader, the default is to cache the mesh. There is a checkbox in the properties panel. Cheers, Armin From dave.demarle at kitware.com Fri Feb 13 09:44:39 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 13 Feb 2015 09:44:39 -0500 Subject: [Paraview] Loading whole time series in ParaView at once In-Reply-To: <54DDFACD.5080609@gmail.com> References: <20150213120355.A8F67F76@centrum.cz> <54DDF0AE.4030509@gmail.com> <20150213140707.0D848F1E@centrum.cz> <54DDFACD.5080609@gmail.com> Message-ID: Filters->Temporal Cache David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Feb 13, 2015 at 8:23 AM, Armin Wehrfritz wrote: > thanks for your reply. I'm using the ParaView builtin reader. I >> always do "touch xxx.foam" in my OpenFOAM folder and after this I >> just start the paraview binary. >> >> But actually I'm not sure if this is the problem of the reader or >> ParaView itself. We have the same problem when loading other data >> formats too. Paraview always loads the time steps one by one. This is >> quite annoying if you're switching from one step to the other. >> > > I agree, the "loading of a whole time series" issue is a ParaView > limitation/feature and most likely not reader specific. > > > However I didn't try the option you've mention. How can I tell >> ParaView to cache at least the mesh in memory? >> > For the built-in ParaView reader, the default is to cache the mesh. > There is a checkbox in the properties panel. > > > Cheers, > Armin > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ronald.fowler at stfc.ac.uk Fri Feb 13 09:42:34 2015 From: ronald.fowler at stfc.ac.uk (ronald.fowler at stfc.ac.uk) Date: Fri, 13 Feb 2015 14:42:34 +0000 Subject: [Paraview] Loading whole time series in ParaView at once Message-ID: <398242C76E3D3740BA94E23089B34E2C92E8BDA7@EXCHMBX03.fed.cclrc.ac.uk> I find that using ParaView in client server mode can make animations significantly faster. Even if the pvserver processes don't have access to graphics cards for rendering they can load the data and serve the geometry to the client faster than a single instance of ParaView can, if you have the memory and processors available. If you do one full pass through the animation to load the data then subsequent passes are much quicker, at least in my experience on smallish problems. I noticed that the gain from using multiple servers is only seen when using the distributed results, not the reconstructed case. Using the D3 filter on the reconstructed case might alter this, I haven't tried. Regards, Ron [forgot to include paraview at paraview.org previously, thanks Armin] -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Armin Wehrfritz Sent: 13 February 2015 13:23 To: j.dubsky at centrum.cz; paraview at paraview.org Subject: Re: [Paraview] Loading whole time series in ParaView at once > thanks for your reply. I'm using the ParaView builtin reader. I > always do "touch xxx.foam" in my OpenFOAM folder and after this I just > start the paraview binary. > > But actually I'm not sure if this is the problem of the reader or > ParaView itself. We have the same problem when loading other data > formats too. Paraview always loads the time steps one by one. This is > quite annoying if you're switching from one step to the other. I agree, the "loading of a whole time series" issue is a ParaView limitation/feature and most likely not reader specific. > However I didn't try the option you've mention. How can I tell > ParaView to cache at least the mesh in memory? For the built-in ParaView reader, the default is to cache the mesh. There is a checkbox in the properties panel. Cheers, Armin _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From dave.demarle at kitware.com Fri Feb 13 10:05:42 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 13 Feb 2015 10:05:42 -0500 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: <50320452A334BD42A5EC72BAD214509924EFE672@MBX210.d.ethz.ch> References: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> <50320452A334BD42A5EC72BAD214509924EFE672@MBX210.d.ethz.ch> Message-ID: Ugh, wish you had told me that about two years ago... In any case, we can simplify the build process substantially. All you have to do is make sure that the CMake search paths find the compute optimized versions of everything and you are good to go. Better still, not cross compiling means we can finally compile numpy on BlueGenes. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Feb 13, 2015 at 1:55 AM, Biddiscombe, John A. wrote: > Rich > > > > On the BGQ, the compute nodes and login nodes are binary compatible, so > you shouldn?t need to bother with most of the cross compiling stuff. the > only thing to watch out for is the MPI and since vtkParseOGLExt and > vtkWrapPython etc don?t touch that, you ought to be ok compiling > _*as if*_ you were going to run on the host node. If you use the MPI > wrappers (I don?t), then all will be taken care of. > > > > I don?t think that I have compiled pv+catalyst to run on BGQ, so my > comment is only based on theory, but I can set a build going in a minute if > it helps (except I?d need to setup mesa which may take a while, so maybe I > won?t....) > > > > JB > > > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *David > E DeMarle > *Sent:* 13 February 2015 01:19 > *To:* Cook, Rich > *Cc:* ParaView list > *Subject:* Re: [Paraview] Error cross-compiling Catalyst on BG/Q > > > > > > On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich wrote: > > > /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT > > > Is the name of the executable to run. > > > > set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT > "PLEASE_FILL_OUT-FAILED_TO_RUN" > CACHE STRING "Result from TRY_RUN" FORCE) > > > > Change that to: > > set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT > > 0 > > CACHE STRING "Result from TRY_RUN" FORCE) > > > > if the return code of that executable is 0 > > > > set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT > "PLEASE_FILL_OUT-NOTFOUND" > CACHE STRING "Output from TRY_RUN" FORCE) > > > > Change that to: > > set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT > > "I am the very model of a modern major general" > > CACHE STRING "Output from TRY_RUN" FORCE) > > > > If the console output of that executable was "I am the very model of a > modern major general" > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From j.dubsky at centrum.cz Fri Feb 13 10:06:57 2015 From: j.dubsky at centrum.cz (j.dubsky at centrum.cz) Date: Fri, 13 Feb 2015 16:06:57 +0100 Subject: [Paraview] =?utf-8?q?Loading_whole_time_series_in_ParaView_at_onc?= =?utf-8?q?e?= In-Reply-To: <54DDFACD.5080609@gmail.com> References: <20150213120355.A8F67F76@centrum.cz>, <54DDF0AE.4030509@gmail.com>, <20150213140707.0D848F1E@centrum.cz> <54DDFACD.5080609@gmail.com> Message-ID: <20150213160657.A9C9DF68@centrum.cz> Hi Armin, oh,I was thinking you had some switch for the command line or something similar on your mind. The "Cache Mesh" Option I do always have on, that's why I didn't realize it in the first second you mentioned it. I also tried to use the "Temporal Cache" filter (as David E DeMarle mentioned, thanks for that), which does help a bit, but still the loading of the data between the timesteps takes some time and you can also cache at most 10 steps, which is not really enough for me. So I suppose there are probably not many other options, are there? :-( Regards Josef ______________________________________________________________ > Od: Armin Wehrfritz > Komu: , > Datum: 13.02.2015 14:23 > P?edm?t: Re: [Paraview] Loading whole time series in ParaView at once > >> thanks for your reply. I'm using the ParaView builtin reader. I >> always do "touch xxx.foam" in my OpenFOAM folder and after this I >> just start the paraview binary. >> >> But actually I'm not sure if this is the problem of the reader or >> ParaView itself. We have the same problem when loading other data >> formats too. Paraview always loads the time steps one by one. This is >> quite annoying if you're switching from one step to the other. > >I agree, the "loading of a whole time series" issue is a ParaView >limitation/feature and most likely not reader specific. > > >> However I didn't try the option you've mention. How can I tell >> ParaView to cache at least the mesh in memory? >For the built-in ParaView reader, the default is to cache the mesh. >There is a checkbox in the properties panel. > > >Cheers, >Armin > From wascott at sandia.gov Fri Feb 13 15:08:46 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 13 Feb 2015 20:08:46 +0000 Subject: [Paraview] Tiff stack Message-ID: I am trying to read in a stack of tiffs, as a 3D cube. ParaView is reading these files as 2D, one tiff per timestep. How can I get ParaView to read these tiffs as a cube? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From pablo.antolin.sanchez at gmail.com Sun Feb 15 15:47:00 2015 From: pablo.antolin.sanchez at gmail.com (=?UTF-8?Q?Pablo_Antol=C3=ADn?=) Date: Sun, 15 Feb 2015 21:47:00 +0100 Subject: [Paraview] Reader plugin for isogeometric analysis Message-ID: Hi, I am currently developing a reader plugin for visualizing results coming from an isogeometric analysis (IGA) library. Very roughly speaking, IGA is similar to finite element analysis but using splines spaces for the basis functions (i.e. high order functions with high inter-element continuity). The idea is to read some data from a file, built the spline representation of the information we want to visualize (with our own library), tessellate it (with a user defined resolution) and to produce vtk grids. I have a minimal version working well, but I would like to extend its capabilities and there are some limiting issues I would like to fix: 1. We are working with high order functions that could present point data with discontinuities. For that reason we are using unstructured grids with duplicated points, in order to be able to represent these discontinuities. Except for this fact, our grids would match perfectly structured grid topologies. Anything we can do for using structured grids being able to shown discontinuities in the point data? 2. We would like to read a single input file and to output multiple grids, but the number of outputs only can be known at run-time (one the input file is parsed). I've reading for while the mailing list and it seems to be impossible. Any clue apart from multi-piece and multi-block solutions? 3. There are certain options that the user can set (e.g. the resolution of the tessellation of the grid). These options must be set in the properties panel. We would like to set these options independently for each one of the grids to be created. So, the properties menu would change depending on the number of outputs known at run-time. Is possible to do such kind of thing? This also would be necessary in the case we use multi-piece/block outputs: the options of each piece/block should be setup separately. Any help is much appreciated. Thank you very much. Pablo Antolin -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.fetzer at iws.uni-stuttgart.de Mon Feb 16 08:32:04 2015 From: thomas.fetzer at iws.uni-stuttgart.de (Thomas Fetzer) Date: Mon, 16 Feb 2015 14:32:04 +0100 Subject: [Paraview] Filename when saving data Message-ID: <54E1F154.50505@iws.uni-stuttgart.de> Hi, when I save data to a file, it always appends a '0' to my filename. I guess it is a bug. Especially the question whether I want to overwrite an existing file is misplaced: if I delete the ending zero in my filename before saving, it will not ask me, but will directly overwrite the existing file. I am using paraview 4.2.0. Best regards, Thomas -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Dipl. Ing. Thomas Fetzer Institut f?r Wasser- und Umweltsystemmodellierung (IWS) Lehrstuhl f?r Hydromechanik und Hydrosystemmodellierung Universit?t Stuttgart, Pfaffenwaldring 61, 70569 Stuttgart Email: thomas.fetzer at iws.uni-stuttgart.de Telefon: 0049-711-685-60103 ** fax: 0049-711-685-60430 http://www.hydrosys.uni-stuttgart.de %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% From berk.geveci at kitware.com Mon Feb 16 09:20:19 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Mon, 16 Feb 2015 09:20:19 -0500 Subject: [Paraview] Tiff stack In-Reply-To: References: Message-ID: Use MetaIO: http://www.itk.org/Wiki/ITK/MetaIO Note that this will work only if your TIFF files are not compressed. -berk On Fri, Feb 13, 2015 at 3:08 PM, Scott, W Alan wrote: > I am trying to read in a stack of tiffs, as a 3D cube. ParaView is > reading these files as 2D, one tiff per timestep. How can I get ParaView > to read these tiffs as a cube? > > 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 ganesh.iitm at gmail.com Mon Feb 16 09:41:39 2015 From: ganesh.iitm at gmail.com (Ganesh Vijayakumar) Date: Mon, 16 Feb 2015 09:41:39 -0500 Subject: [Paraview] Filename when saving data In-Reply-To: <54E1F154.50505@iws.uni-stuttgart.de> References: <54E1F154.50505@iws.uni-stuttgart.de> Message-ID: I don't know a solution to this.. but I do confirm this behaviour in an earlier version of paraview. On Mon, Feb 16, 2015 at 8:32 AM, Thomas Fetzer < thomas.fetzer at iws.uni-stuttgart.de> wrote: > Hi, > > when I save data to a file, it always appends a '0' to my filename. > I guess it is a bug. Especially the question whether I want to > overwrite an existing file is misplaced: if I delete the ending zero > in my filename before saving, it will not ask me, but will directly > overwrite the existing file. I am using paraview 4.2.0. > > Best regards, > Thomas > > -- > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > Dipl. Ing. Thomas Fetzer > Institut f?r Wasser- und Umweltsystemmodellierung (IWS) > Lehrstuhl f?r Hydromechanik und Hydrosystemmodellierung > Universit?t Stuttgart, Pfaffenwaldring 61, 70569 Stuttgart > Email: thomas.fetzer at iws.uni-stuttgart.de > Telefon: 0049-711-685-60103 ** fax: 0049-711-685-60430 > http://www.hydrosys.uni-stuttgart.de > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Feb 16 09:49:10 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 16 Feb 2015 09:49:10 -0500 Subject: [Paraview] Filename when saving data In-Reply-To: <54E1F154.50505@iws.uni-stuttgart.de> References: <54E1F154.50505@iws.uni-stuttgart.de> Message-ID: What format are you saving the file as? On Mon, Feb 16, 2015 at 8:32 AM, Thomas Fetzer wrote: > Hi, > > when I save data to a file, it always appends a '0' to my filename. > I guess it is a bug. Especially the question whether I want to > overwrite an existing file is misplaced: if I delete the ending zero > in my filename before saving, it will not ask me, but will directly > overwrite the existing file. I am using paraview 4.2.0. > > Best regards, > Thomas > > -- > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > Dipl. Ing. Thomas Fetzer > Institut f?r Wasser- und Umweltsystemmodellierung (IWS) > Lehrstuhl f?r Hydromechanik und Hydrosystemmodellierung > Universit?t Stuttgart, Pfaffenwaldring 61, 70569 Stuttgart > Email: thomas.fetzer at iws.uni-stuttgart.de > Telefon: 0049-711-685-60103 ** fax: 0049-711-685-60430 > http://www.hydrosys.uni-stuttgart.de > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From thomas.fetzer at iws.uni-stuttgart.de Mon Feb 16 09:49:46 2015 From: thomas.fetzer at iws.uni-stuttgart.de (Thomas Fetzer) Date: Mon, 16 Feb 2015 15:49:46 +0100 Subject: [Paraview] Filename when saving data In-Reply-To: References: <54E1F154.50505@iws.uni-stuttgart.de> Message-ID: <54E2038A.9010003@iws.uni-stuttgart.de> .csv %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Dipl. Ing. Thomas Fetzer Institut f?r Wasser- und Umweltsystemmodellierung (IWS) Lehrstuhl f?r Hydromechanik und Hydrosystemmodellierung Universit?t Stuttgart, Pfaffenwaldring 61, 70569 Stuttgart Email: thomas.fetzer at iws.uni-stuttgart.de Telefon: 0049-711-685-60103 ** fax: 0049-711-685-60430 http://www.hydrosys.uni-stuttgart.de %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Am 02/16/2015 um 03:49 PM schrieb Utkarsh Ayachit: > What format are you saving the file as? > > On Mon, Feb 16, 2015 at 8:32 AM, Thomas Fetzer > wrote: >> Hi, >> >> when I save data to a file, it always appends a '0' to my filename. >> I guess it is a bug. Especially the question whether I want to >> overwrite an existing file is misplaced: if I delete the ending zero >> in my filename before saving, it will not ask me, but will directly >> overwrite the existing file. I am using paraview 4.2.0. >> >> Best regards, >> Thomas >> >> -- >> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% >> Dipl. Ing. Thomas Fetzer >> Institut f?r Wasser- und Umweltsystemmodellierung (IWS) >> Lehrstuhl f?r Hydromechanik und Hydrosystemmodellierung >> Universit?t Stuttgart, Pfaffenwaldring 61, 70569 Stuttgart >> Email: thomas.fetzer at iws.uni-stuttgart.de >> Telefon: 0049-711-685-60103 ** fax: 0049-711-685-60430 >> http://www.hydrosys.uni-stuttgart.de >> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Mon Feb 16 10:02:16 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 16 Feb 2015 10:02:16 -0500 Subject: [Paraview] Reader plugin for isogeometric analysis In-Reply-To: References: Message-ID: > Anything we can do for using structured grids being able to > shown discontinuities in the point data? Not as far as I know. > We would like to read a single input file and to output multiple grids, but > the number of outputs only can be known at run-time (one the input file is > parsed). I've reading for while the mailing list and it seems to be > impossible. Any clue apart from multi-piece and multi-block solutions? That's correct. A reader/filter can't change the number of output ports at run-time based on the input file. You can change your filter to produce a vtkMultiBlockDataSet and each of the grids can be put out as a block in that multiblock dataset. There's really not much more to it. Look at vtkMultiBlockDataset API or vtkMultiBlockDataSetAlgorithm (and subclasses) for examples. > There are certain options that the user can set (e.g. the resolution of the > tessellation of the grid). These options must be set in the properties > panel. We would like to set these options independently for each one of the > grids to be created. So, the properties menu would change depending on the > number of outputs known at run-time. Is possible to do such kind of thing? > This also would be necessary in the case we use multi-piece/block outputs: > the options of each piece/block should be setup separately. In theory, yes. It will entail custom code, however. For starters, start will using same settings for all. Once you have that working, I can point you to possibilities based on the XML you produce for "shared" options. Utkarsh From utkarsh.ayachit at kitware.com Mon Feb 16 10:03:53 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 16 Feb 2015 10:03:53 -0500 Subject: [Paraview] error building silo reader In-Reply-To: <54DBF178.6070204@nasa.gov> References: <54DBF178.6070204@nasa.gov> Message-ID: Which version of Silo did you build? Can you attach your CMakeCache.txt please? Thanks On Wed, Feb 11, 2015 at 7:19 PM, Jeff Becker wrote: > Please help me understand and fix the following build error. Thanks. > > -jeff > > [ 26%] Building CXX object > Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloWriter.C.o > > [ 26%] Building CXX object > Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o > > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?virtual void > avtSiloFileFormat::PopulateDatabaseMetaData(avtDatabaseMetaData*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1211: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?void avtSiloFileFormat::ReadCSGmeshes(DBfile*, int, > char**, const char*, avtDatabaseMetaData*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2532: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2535: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?void > avtSiloFileFormat::FindMultiMeshAdjConnectivity(DBfile*, int&, int*&, int*&, > int&, int*&, int&, int*&, bool, bool)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5442: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5450: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?void avtSiloFileFormat::AddCSGMultimesh(const char*, > const char*, avtDatabaseMetaData*, avtSiloMultiMeshCacheEntry*, DBfile*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5883: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5955: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?vtkDataArray* > avtSiloFileFormat::GetAnnotIntNodelistsVar(int, std::string)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6765: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6767: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?vtkDataArray* > avtSiloFileFormat::GetMrgTreeNodelistsVar(int, std::string)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6856: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6858: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?void avtSiloFileFormat::ExpandUcdvar(DBucdvar*, const > char*, const char*, int)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8563: > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8575: > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?void avtSiloFileFormat::HandleGlobalZoneIds(const char*, > int, void*, int, int)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:9136: > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?void > avtSiloFileFormat::ReadInConnectivity(vtkUnstructuredGrid*, DBucdmesh*, > const char*, int)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:10226: > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?void avtSiloFileFormat::ReadInArbConnectivity(const > char*, vtkUnstructuredGrid*, DBucdmesh*, int, int)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:11349: > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?vtkDataArray* avtSiloFileFormat::GetGlobalNodeIds(int, > const char*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13751: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13754: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?vtkDataArray* avtSiloFileFormat::GetGlobalZoneIds(int, > const char*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13842: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13845: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?avtMaterial* avtSiloFileFormat::CalcMaterial(DBfile*, > const char*, const char*, int)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14218: > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > In member function ?avtFacelist* > avtSiloFileFormat::CalcExternalFacelist(DBfile*, const char*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14423: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14426: > error: expected primary-expression before ?,? token > make[2]: *** > [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o] > Error 1 > make[1]: *** > [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all] Error > 2 > make: *** [all] Error 2 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Mon Feb 16 10:06:23 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 16 Feb 2015 10:06:23 -0500 Subject: [Paraview] Filename when saving data In-Reply-To: <54E2038A.9010003@iws.uni-stuttgart.de> References: <54E1F154.50505@iws.uni-stuttgart.de> <54E2038A.9010003@iws.uni-stuttgart.de> Message-ID: Noted. Feel free to report a bug on the bug tracker (http://paraview.org/Bug). I am not sure how this could be addressed but let's see. The problem ends up being specific writers can pick filename variants based on the nature of the data they are writing and that information is not available to the UI when it shows the Save Data dialog. Thanks Utkarsh On Mon, Feb 16, 2015 at 9:49 AM, Thomas Fetzer wrote: > .csv > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > Dipl. Ing. Thomas Fetzer > Institut f?r Wasser- und Umweltsystemmodellierung (IWS) > Lehrstuhl f?r Hydromechanik und Hydrosystemmodellierung > Universit?t Stuttgart, Pfaffenwaldring 61, 70569 Stuttgart > Email: thomas.fetzer at iws.uni-stuttgart.de > Telefon: 0049-711-685-60103 ** fax: 0049-711-685-60430 > http://www.hydrosys.uni-stuttgart.de > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > > Am 02/16/2015 um 03:49 PM schrieb Utkarsh Ayachit: > >> What format are you saving the file as? >> >> On Mon, Feb 16, 2015 at 8:32 AM, Thomas Fetzer >> wrote: >>> >>> Hi, >>> >>> when I save data to a file, it always appends a '0' to my filename. >>> I guess it is a bug. Especially the question whether I want to >>> overwrite an existing file is misplaced: if I delete the ending zero >>> in my filename before saving, it will not ask me, but will directly >>> overwrite the existing file. I am using paraview 4.2.0. >>> >>> Best regards, >>> Thomas >>> >>> -- >>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% >>> Dipl. Ing. Thomas Fetzer >>> Institut f?r Wasser- und Umweltsystemmodellierung (IWS) >>> Lehrstuhl f?r Hydromechanik und Hydrosystemmodellierung >>> Universit?t Stuttgart, Pfaffenwaldring 61, 70569 Stuttgart >>> Email: thomas.fetzer at iws.uni-stuttgart.de >>> Telefon: 0049-711-685-60103 ** fax: 0049-711-685-60430 >>> http://www.hydrosys.uni-stuttgart.de >>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview From gabel.fabian at gmail.com Mon Feb 16 10:23:20 2015 From: gabel.fabian at gmail.com (Fabian Gabel) Date: Mon, 16 Feb 2015 16:23:20 +0100 Subject: [Paraview] Apply displaying options to multiple selected files from the pipeline browser Message-ID: <1424100200.4423.1.camel@gmail.com> Dear ParaView team, I use ParaView 4.1.0 to visualize .vtk files (Legacy Format). The files are written by a FORTRAN program and exhibit the following structure # vtk DataFile Version 3.0 grid ASCII DATASET STRUCTURED_GRID DIMENSIONS ... ... ... Points .... float ... CELL_DATA ... VECTORS UVW float ... SCALARS P float LOOKUP_TABLE DEFAULT ... My complete grid is block structured, but a .vtk file is generated for each block. When I load all .vtk files into Paraview I want to visualize them at the same time, i.e. if I choose to look at one variable, I want this to happen for all .vkt files / blocks simultaneously. Selecting all files disables the desired options from the display properties bar. I think python scripting could do the trick, but since I have never used this feature before, I could use some hints. Regards, Fabian From utkarsh.ayachit at kitware.com Mon Feb 16 10:27:50 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 16 Feb 2015 10:27:50 -0500 Subject: [Paraview] Apply displaying options to multiple selected files from the pipeline browser In-Reply-To: <1424100200.4423.1.camel@gmail.com> References: <1424100200.4423.1.camel@gmail.com> Message-ID: Try combining all of them into a sample multiblock dataset by selecting all the reader and then applying the "Group Datasets" filter. Now you can show/hide/color/filter the result of this filter alone to get the desired effect. Utkarsh On Mon, Feb 16, 2015 at 10:23 AM, Fabian Gabel wrote: > Dear ParaView team, > > I use ParaView 4.1.0 to visualize .vtk files (Legacy Format). The files > are written by a FORTRAN program and exhibit the following structure > > # vtk DataFile Version 3.0 > grid > ASCII > DATASET STRUCTURED_GRID > DIMENSIONS ... ... ... > Points .... float > ... > CELL_DATA ... > VECTORS UVW float > ... > SCALARS P float > LOOKUP_TABLE DEFAULT > ... > > My complete grid is block structured, but a .vtk file is generated for > each block. When I load all .vtk files into Paraview I want to visualize > them at the same time, i.e. if I choose to look at one variable, I want > this to happen for all .vkt files / blocks simultaneously. Selecting all > files disables the desired options from the display properties bar. > > I think python scripting could do the trick, but since I have never used > this feature before, I could use some hints. > > 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 felipe.bordeu at ec-nantes.fr Tue Feb 17 10:54:06 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu) Date: Tue, 17 Feb 2015 16:54:06 +0100 Subject: [Paraview] Catalyst simple test Message-ID: <54E3641E.60800@ec-nantes.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody, I 'm trying to connect my simulation code (a dummy simulation code for the moment) to paraview using Catalyst to do live visualization. Just make a mesh (2D structured, with 1 field), and send it to paraview without python. But I something is not working. The code runs, I can connect to paraview, pause the simulation but unable to sent the data for the visualization. So I'm doing this : for initialization create a vtkCPProcessor object and call Initialize(); create a vtkCPPipeline derived object class and added to the processor ( Processor->AddPipeline(pipeline.GetPointer()); ) . (why do I need a Pipeline if I'm going to send my raw data (in vtk format of course) to paraview?) in the CoProcess( vtkCPDataDescription* dataDescription) member function the only relevant lines are : vtkNew producer; vtkImageData* grid = vtkImageData::SafeDownCast(dataDescription->GetInputDescriptionByName("input")->GetGrid()); producer->SetOutput(grid,dataDescription->GetTime()); create a vtkLiveInsituLink LiveLink = vtkLiveInsituLink::New(); LiveLink->SetInsituPort(22222); LiveLink->SetHostname("localhost"); LiveLink->SetProcessType(vtkLiveInsituLink::INSITU); vtkSMProxyManager* proxyManager = vtkSMProxyManager::GetProxyManager(); vtkSMSessionProxyManager* sessionProxyManager = proxyManager->GetActiveSessionProxyManager(); LiveLink->Initialize(sessionProxyManager); then in each time-step I do : vtkCPDataDescription* dataDescription = vtkCPDataDescription::New(); dataDescription->AddInput("input"); dataDescription-> SetTimeData(time, timeStep); if(Processor->RequestDataDescription(dataDescription) != 0){ // Create a uniform grid vtkImageData* grid = vtkImageData::New(); .... ""setextent, create DoubleArray, fill the array, put the array in the grid"" ... dataDescription->GetInputDescriptionByName("input")->SetGrid(grid); grid->Delete(); Processor->CoProcess(dataDescription); (and also the LiveLink code, not sure about this) this is similar to the coprocessing.py while(true){ LiveLink->InsituUpdate(timeStep, time); LiveLink->InsituPostProcess(time, timeStep); if (LiveLink->GetSimulationPaused()){ if (LiveLink->WaitForLiveChange()){ break; } } else { break; } } I'm pretty sure I'm mixing the code for the different examples I found on the web and in the sources. I didn't find an example with pure c++ and live viz. How I can tell to the LiveLink with data I want to sent to paraview??? using ParaView 4.3.1 compiled from git source in linux. Thanks to all. - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU42QZAAoJEE/fMfNgU9/DCR8IAIfD2dR2h2RBx5vfpgii6N5q ws5vkG9AZf1Jsqdf3fxk25pcB2BJs615I3iEPmlY4SDTUkVmbVzVFvEXX4HXh8+2 AGX3yNSjfUfAX9RFPsz131FHLt5oG/7cJjmI8343b6JK+cxmznu+elgCpSRV38gp yjole85C0SxsZlBBGNXVNTaNyum0tjLVpWMi97fqjLtENTxXjp5gZTy0998edKr1 f6EqeZ9QySt+T/cWFB/gmQZsX3wwuoPg7fxlYjcMNvLIWBC2VSsAuHlBTRKkhwLn Q52A1DNLcMuJ8pOO24/sHr+FldTpzldccTkweRhhV8RQAybw0WWmUf377omk7FA= =q2lI -----END PGP SIGNATURE----- From jeffrey.c.becker at nasa.gov Tue Feb 17 11:30:39 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Tue, 17 Feb 2015 08:30:39 -0800 Subject: [Paraview] error building silo reader In-Reply-To: References: <54DBF178.6070204@nasa.gov> Message-ID: <54E36CAF.5010605@nasa.gov> On 02/16/2015 07:03 AM, Utkarsh Ayachit wrote: > Which version of Silo did you build? Can you attach your CMakeCache.txt please? Progress! I figured out that the version of silo I was using (4.10.2) was causing the error due to an incompatibility with the way ParaView was calling it. Thus I went to silo 4.9.1. Now I get the following QT related error. [ 88%] Building CXX object Qt/Core/CMakeFiles/pqCore.dir/pqOutputWindowModel.cxx.o /u/wk/jcbecker/ParaView/Qt/Core/pqOutputWindowModel.cxx: In member function ?void pqOutputWindowModel::ShowMessages(bool*)?: /u/wk/jcbecker/ParaView/Qt/Core/pqOutputWindowModel.cxx:246:14: error: ?class QList? has no member named ?reserve? this->Rows.reserve(_rowCount); ^ make[2]: *** [Qt/Core/CMakeFiles/pqCore.dir/pqOutputWindowModel.cxx.o] Error 1 make[1]: *** [Qt/Core/CMakeFiles/pqCore.dir/all] Error 2 make: *** [all] Error 2 Any ideas here? Thanks. I've attached CMakeCache.txt in case it helps. -jeff > > Thanks > > On Wed, Feb 11, 2015 at 7:19 PM, Jeff Becker wrote: >> Please help me understand and fix the following build error. Thanks. >> >> -jeff >> >> [ 26%] Building CXX object >> Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloWriter.C.o >> >> [ 26%] Building CXX object >> Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?virtual void >> avtSiloFileFormat::PopulateDatabaseMetaData(avtDatabaseMetaData*)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: >> error: >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1211: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void avtSiloFileFormat::ReadCSGmeshes(DBfile*, int, >> char**, const char*, avtDatabaseMetaData*)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2532: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: >> error: >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2535: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void >> avtSiloFileFormat::FindMultiMeshAdjConnectivity(DBfile*, int&, int*&, int*&, >> int&, int*&, int&, int*&, bool, bool)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5442: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: >> error: >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5450: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void avtSiloFileFormat::AddCSGMultimesh(const char*, >> const char*, avtDatabaseMetaData*, avtSiloMultiMeshCacheEntry*, DBfile*)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5883: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: >> error: >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5955: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?vtkDataArray* >> avtSiloFileFormat::GetAnnotIntNodelistsVar(int, std::string)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6765: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6767: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?vtkDataArray* >> avtSiloFileFormat::GetMrgTreeNodelistsVar(int, std::string)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6856: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6858: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void avtSiloFileFormat::ExpandUcdvar(DBucdvar*, const >> char*, const char*, int)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8563: >> error: invalid conversion from ?float**? to ?void**? >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8575: >> error: invalid conversion from ?float**? to ?void**? >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void avtSiloFileFormat::HandleGlobalZoneIds(const char*, >> int, void*, int, int)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:9136: >> error: invalid conversion from ?float**? to ?void**? >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void >> avtSiloFileFormat::ReadInConnectivity(vtkUnstructuredGrid*, DBucdmesh*, >> const char*, int)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:10226: >> error: invalid conversion from ?float**? to ?void**? >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void avtSiloFileFormat::ReadInArbConnectivity(const >> char*, vtkUnstructuredGrid*, DBucdmesh*, int, int)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:11349: >> error: invalid conversion from ?float**? to ?void**? >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?vtkDataArray* avtSiloFileFormat::GetGlobalNodeIds(int, >> const char*)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13751: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: >> error: >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13754: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?vtkDataArray* avtSiloFileFormat::GetGlobalZoneIds(int, >> const char*)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13842: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: >> error: >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13845: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?avtMaterial* avtSiloFileFormat::CalcMaterial(DBfile*, >> const char*, const char*, int)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14218: >> error: invalid conversion from ?float**? to ?void**? >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?avtFacelist* >> avtSiloFileFormat::CalcExternalFacelist(DBfile*, const char*)?: >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14423: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: >> error: expected primary-expression before ?,? token >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: >> error: >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14426: >> error: expected primary-expression before ?,? token >> make[2]: *** >> [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o] >> Error 1 >> make[1]: *** >> [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all] Error >> 2 >> make: *** [all] Error 2 >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- # This is the CMakeCache file. # For build in directory: /u/wk/jcbecker/ParaView-build # It was generated by CMake: /usr/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 ######################## //Value Computed by CMake AVT_DATABASE_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/Library/VisItLib/avt/Database //Value Computed by CMake AVT_DATABASE_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database //Value Computed by CMake AVT_DBATTS_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/Library/VisItLib/avt/DBAtts //Value Computed by CMake AVT_DBATTS_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/DBAtts //Value Computed by CMake AVT_MATH_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/Library/VisItLib/avt/Math //Value Computed by CMake AVT_MATH_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Math //Value Computed by CMake AVT_PIPELINE_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline //Value Computed by CMake AVT_PIPELINE_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline //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 //Build Verdict with shared libraries. BUILD_SHARED_LIBS:BOOL=ON //Build the testing tree. BUILD_TESTING:BOOL=ON //Build With User Defined Values BUILD_USER_DEFINED_LIBS:BOOL=OFF //Path to a program. BZRCOMMAND:FILEPATH=BZRCOMMAND-NOTFOUND //The directory containing a CMake configuration file for Boost. Boost_DIR:PATH=Boost_DIR-NOTFOUND //Path to a file. Boost_INCLUDE_DIR:PATH=/usr/include //Path to a file. CGNS_INCLUDE_DIR:PATH=CGNS_INCLUDE_DIR-NOTFOUND //Path to a library. CGNS_LIBRARY:FILEPATH=CGNS_LIBRARY-NOTFOUND //Path to a program. CMAKE_AR:FILEPATH=/usr/bin/ar //Choose the type of build. CMAKE_BUILD_TYPE:STRING=Release //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler. CMAKE_CXX_COMPILER:FILEPATH=/usr/local/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 minsize builds. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds (/MD /Ob1 /Oi // /Ot /Oy /Gs will produce slightly less optimized but smaller // files). CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during Release with Debug Info builds. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //C compiler. CMAKE_C_COMPILER:FILEPATH=/usr/local/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 minsize builds. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds (/MD /Ob1 /Oi // /Ot /Oy /Gs will produce slightly less optimized but smaller // files). CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during Release with Debug Info builds. 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/local/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 minsize builds. CMAKE_Fortran_FLAGS_MINSIZEREL:STRING=-Os //Flags used by the compiler during release builds (/MD /Ob1 /Oi // /Ot /Oy /Gs will produce slightly less optimized but smaller // files). CMAKE_Fortran_FLAGS_RELEASE:STRING=-O3 //Flags used by the compiler during Release with Debug Info builds. CMAKE_Fortran_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Use HP pthreads. CMAKE_HP_PTHREADS:BOOL= //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/usr/local //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 //Use the pthreads library. CMAKE_USE_PTHREADS:BOOL=1 //If true, cmake will use relative paths in makefiles and projects. CMAKE_USE_RELATIVE_PATHS:BOOL=OFF //Use sproc libs. CMAKE_USE_SPROC:BOOL= //Use the win32 thread library. CMAKE_USE_WIN32_THREADS:BOOL= //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 //X11 extra flags. CMAKE_X_CFLAGS:STRING= //Libraries and options used in X11 programs. CMAKE_X_LIBS:STRING=/usr/lib64/libSM.so;/usr/lib64/libICE.so;/usr/lib64/libX11.so;/usr/lib64/libXext.so //Path to the coverage program that CTest uses for performing coverage // inspection COVERAGE_COMMAND:FILEPATH=/usr/bin/gcov //Extra command line flags to pass to the coverage tool COVERAGE_EXTRA_FLAGS:STRING=-l //How many times to retry timed-out CTest submissions. CTEST_SUBMIT_RETRY_COUNT:STRING=3 //How long to wait between timed-out CTest submissions. CTEST_SUBMIT_RETRY_DELAY:STRING=5 //Maximum time allowed before CTest will kill the test. CTEST_TEST_TIMEOUT:STRING=3600 //Path to a program. CVSCOMMAND:FILEPATH=/usr/bin/cvs //Options passed to the cvs update command. CVS_UPDATE_OPTIONS:STRING=-d -A -P //Value Computed by CMake CatalystScriptGeneratorPlugin_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Plugins/CatalystScriptGenerator //Dependencies for the target CatalystScriptGeneratorPlugin_LIB_DEPENDS:STATIC=general;pqComponents; //Value Computed by CMake CatalystScriptGeneratorPlugin_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Plugins/CatalystScriptGenerator //Maximum time allowed before CTest will kill the test. DART_TESTING_TIMEOUT:STRING=3600 //Value Computed by CMake DICOMParser_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/Utilities/DICOMParser //Value Computed by CMake DICOMParser_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/Utilities/DICOMParser //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=/u/wk/jcbecker/ParaView/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=/u/wk/jcbecker/ParaView-build/Plugins/EyeDomeLighting //Value Computed by CMake EyeDomeLighting_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Plugins/EyeDomeLighting //Path to a program. GITCOMMAND:FILEPATH=/usr/bin/git //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=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GMV //Dependencies for the target GMVReader_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //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 //Dependencies for the target H5PartReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;/usr/local/lib/libhdf5.so;general;/usr/lib64/libz.so;general;/usr/lib64/libm.so;general;/usr/local/lib/libhdf5_hl.so;general;/usr/local/lib/libhdf5.so;general;vtksys; //Value Computed by CMake HDF5_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/hdf5/vtkhdf5 //Build Static Executabless HDF5_BUILD_STATIC_EXECS:BOOL=OFF //HDF5 C++ Wrapper compiler. Used only to detect HDF5 compile // flags. HDF5_CXX_COMPILER_EXECUTABLE:FILEPATH=/usr/local/bin/h5c++ //HDF5 Wrapper compiler. Used only to detect HDF5 compile flags. HDF5_C_COMPILER_EXECUTABLE:FILEPATH=/usr/local/bin/h5cc //Path to a file. HDF5_C_INCLUDE_DIR:PATH=/usr/local/include //HDF5 file differencing tool. HDF5_DIFF_EXECUTABLE:FILEPATH=/usr/bin/h5diff //The directory containing a CMake configuration file for HDF5. HDF5_DIR:PATH=HDF5_DIR-NOTFOUND //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 //Instrument The library HDF5_ENABLE_INSTRUMENT:BOOL=OFF //HDF5 Fortran Wrapper compiler. Used only to detect HDF5 compile // flags. HDF5_Fortran_COMPILER_EXECUTABLE:FILEPATH=HDF5_Fortran_COMPILER_EXECUTABLE-NOTFOUND //Value Computed by CMake HDF5_HL_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/hdf5/vtkhdf5/hl //Path to a file. HDF5_HL_INCLUDE_DIR:PATH=/usr/local/include //Value Computed by CMake HDF5_HL_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/hdf5/vtkhdf5/hl //Value Computed by CMake HDF5_HL_SRC_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/hdf5/vtkhdf5/hl/src //Value Computed by CMake HDF5_HL_SRC_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/hdf5/vtkhdf5/hl/src //HDF5 library compiled with parallel IO support HDF5_IS_PARALLEL:BOOL=FALSE //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=/u/wk/jcbecker/ParaView/VTK/ThirdParty/hdf5/vtkhdf5 //Value Computed by CMake HDF5_SRC_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/hdf5/vtkhdf5/src //Value Computed by CMake HDF5_SRC_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/hdf5/vtkhdf5/src //Execute tests with different VFDs HDF5_TEST_VFD:BOOL=OFF //Enable folder grouping of projects in IDEs. HDF5_USE_FOLDERS:BOOL=ON //Path to a library. HDF5_hdf5_LIBRARY_DEBUG:FILEPATH=HDF5_hdf5_LIBRARY_DEBUG-NOTFOUND //Path to a library. HDF5_hdf5_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libhdf5.so //Path to a library. HDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH=HDF5_hdf5_hl_LIBRARY_DEBUG-NOTFOUND //Path to a library. HDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libhdf5_hl.so //Path to a library. HDF5_m_LIBRARY_DEBUG:FILEPATH=HDF5_m_LIBRARY_DEBUG-NOTFOUND //Path to a library. HDF5_m_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libm.so //Path to a library. HDF5_z_LIBRARY_DEBUG:FILEPATH=HDF5_z_LIBRARY_DEBUG-NOTFOUND //Path to a library. HDF5_z_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libz.so //Path to a program. HGCOMMAND:FILEPATH=/usr/bin/hg //Value Computed by CMake JsonCpp_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Value Computed by CMake JsonCpp_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Command to build the project MAKECOMMAND:STRING=/usr/bin/gmake -i //Path to the memory checking command, used for memory error detection. MEMORYCHECK_COMMAND:FILEPATH=/usr/bin/valgrind //File that contains suppressions for the memory checker MEMORYCHECK_SUPPRESSIONS_FILE:FILEPATH= //Path to a file. MILI_INCLUDE_DIR:PATH=MILI_INCLUDE_DIR-NOTFOUND //Path to a library. MILI_LIBRARY:FILEPATH=MILI_LIBRARY-NOTFOUND //Dependencies for the target MobileRemoteControl_LIB_DEPENDS:STATIC=general;pqComponents;general;pqApplicationComponents;general;vtkPVClientServerCoreRendering;general;vtkPVServerManagerRendering; //Request building pqDeprecated Module_pqDeprecated:BOOL=OFF //Request building vtkAcceleratorsDax Module_vtkAcceleratorsDax:BOOL=OFF //Request building vtkAcceleratorsPiston Module_vtkAcceleratorsPiston:BOOL=OFF //Request building vtkCosmoHaloFinder Module_vtkCosmoHaloFinder:BOOL=OFF //Request building vtkDomainsChemistryOpenGL2 Module_vtkDomainsChemistryOpenGL2:BOOL=OFF //Request building vtkFiltersImaging Module_vtkFiltersImaging:BOOL=OFF //Request building vtkFiltersMatlab Module_vtkFiltersMatlab:BOOL=OFF //Request building vtkFiltersParallelFlowPaths Module_vtkFiltersParallelFlowPaths:BOOL=OFF //Request building vtkFiltersParallelGeometry Module_vtkFiltersParallelGeometry:BOOL=OFF //Request building vtkFiltersParallelImaging Module_vtkFiltersParallelImaging:BOOL=OFF //Request building vtkFiltersParallelMPI Module_vtkFiltersParallelMPI: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 vtkIOMPIImage Module_vtkIOMPIImage:BOOL=OFF //Request building vtkIOMPIParallel Module_vtkIOMPIParallel:BOOL=OFF //Request building vtkIOMySQL Module_vtkIOMySQL:BOOL=OFF //Request building vtkIOODBC Module_vtkIOODBC:BOOL=OFF //Request building vtkIOParallelNetCDF Module_vtkIOParallelNetCDF:BOOL=OFF //Request building vtkIOPostgreSQL Module_vtkIOPostgreSQL:BOOL=OFF //Request building vtkIOSQL Module_vtkIOSQL:BOOL=OFF //Request building vtkIOVideo Module_vtkIOVideo: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 vtkPVVTKExtensionsCosmoTools Module_vtkPVVTKExtensionsCosmoTools:BOOL=OFF //Request building vtkParaViewWebDocumentation Module_vtkParaViewWebDocumentation:BOOL=OFF //Request building vtkParallelMPI Module_vtkParallelMPI:BOOL=OFF //Request building vtkParallelMPI4Py Module_vtkParallelMPI4Py:BOOL=OFF //Request building vtkRenderingContextOpenGL2 Module_vtkRenderingContextOpenGL2:BOOL=OFF //Request building vtkRenderingExternal Module_vtkRenderingExternal:BOOL=OFF //Request building vtkRenderingFreeTypeFontConfig Module_vtkRenderingFreeTypeFontConfig:BOOL=OFF //Request building vtkRenderingFreeTypeOpenGL2 Module_vtkRenderingFreeTypeOpenGL2:BOOL=OFF //Request building vtkRenderingImage Module_vtkRenderingImage:BOOL=OFF //Request building vtkRenderingOpenGL2 Module_vtkRenderingOpenGL2:BOOL=OFF //Request building vtkRenderingParallelLIC Module_vtkRenderingParallelLIC:BOOL=OFF //Request building vtkRenderingQt Module_vtkRenderingQt:BOOL=OFF //Request building vtkRenderingTk Module_vtkRenderingTk:BOOL=OFF //Request building vtkRenderingVolumeOpenGL2 Module_vtkRenderingVolumeOpenGL2:BOOL=OFF //Request building vtkRenderingVolumeOpenGLNew Module_vtkRenderingVolumeOpenGLNew:BOOL=OFF //Request building vtkTclTk Module_vtkTclTk: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 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 vtkicet Module_vtkicet:BOOL=OFF //Request building vtklibproj4 Module_vtklibproj4:BOOL=OFF //Request building vtkmpi4py Module_vtkmpi4py: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 //Path to NVCONTROL headers (NVCtrlLib.h and NVCtrl.h) NVCtrlLib_INCLUDE_DIR:PATH=NVCtrlLib_INCLUDE_DIR-NOTFOUND //Path to NVCONTROL static library (libXNVCtrl.a) NVCtrlLib_LIBRARY:FILEPATH=NVCtrlLib_LIBRARY-NOTFOUND //Dependencies for the target NonOrthogonalSource_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //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 //Build Adaptors for various simulation codes PARAVIEW_BUILD_CATALYST_ADAPTORS:BOOL=OFF //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 CGNSReader Plugin PARAVIEW_BUILD_PLUGIN_CGNSReader:BOOL=FALSE //Build CatalystScriptGeneratorPlugin Plugin PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin:BOOL=TRUE //Build EyeDomeLighting Plugin PARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=TRUE //Build ForceTime Plugin PARAVIEW_BUILD_PLUGIN_ForceTime:BOOL=FALSE //Build GMVReader Plugin PARAVIEW_BUILD_PLUGIN_GMVReader: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 MobileRemoteControl Plugin PARAVIEW_BUILD_PLUGIN_MobileRemoteControl:BOOL=TRUE //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 PythonQtPlugin Plugin PARAVIEW_BUILD_PLUGIN_PythonQtPlugin:BOOL=FALSE //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 TemporalParallelismScriptGenerator Plugin PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator:BOOL=FALSE //Build UncertaintyRendering Plugin PARAVIEW_BUILD_PLUGIN_UncertaintyRendering: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 //Enable/Disable web documentation PARAVIEW_BUILD_WEB_DOCUMENTATION:BOOL=OFF //Turn on/off client tests that involve separate data and render // servers. PARAVIEW_CLIENT_RENDER_SERVER_TESTS:BOOL=ON //Add Collaboration testing PARAVIEW_COLLABORATION_TESTING: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 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 //Semi-colon seperated paths to extrenal plugin directories. PARAVIEW_EXTERNAL_PLUGIN_DIRS:STRING= //Freeze Python packages/modules into the application. PARAVIEW_FREEZE_PYTHON:BOOL=OFF //When enabled, "make install" will install development files PARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=OFF //Expected Qt version PARAVIEW_QT_VERSION:STRING=4 //Build ParaView with Dax many-core filters PARAVIEW_USE_DAX:BOOL=OFF //Enable MPI support for parallel computing PARAVIEW_USE_MPI: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=ON //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 //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.6 //Path to a library. PYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.6.so //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=/u/wk/jcbecker/ParaView-build //Value Computed by CMake ParaView_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView //Value Computed by CMake PointSpritePlugin_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Plugins/PointSprite //Value Computed by CMake PointSpritePlugin_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Plugins/PointSprite //Dependencies for the target PointSprite_Plugin_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkPointSpriteGraphics;general;vtkPointSpriteGraphicsCS;general;vtkPointSpriteRendering;general;vtkPointSpriteRenderingCS;general;vtkQvis;general;vtkPointSpriteGraphics;general;vtkPointSpriteRendering; //Path to a library. QT_ARTHURPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_ARTHURPLUGIN_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/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=/usr/lib64/qt4/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=/usr/lib64/qt4/plugins/designer/libcustomwidgetplugin.so //Path to a program. QT_DBUSCPP2XML_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/qdbuscpp2xml //Path to a program. QT_DBUSXML2CPP_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/qdbusxml2cpp //Path to a program. QT_DESIGNER_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/designer-qt4 //The location of the Qt docs QT_DOC_DIR:PATH=/usr/share/doc/qt4 //qhelpgenerator used to compile Qt help project files QT_HELP_GENERATOR:FILEPATH=/usr/lib64/qt4/bin/qhelpgenerator //The location of the Qt imports QT_IMPORTS_DIR:PATH=/usr/local/Trolltech/Qt-4.8.6/imports //Path to a program. QT_LINGUIST_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/linguist-qt4 //Path to a program. QT_LRELEASE_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/lrelease-qt4 //Path to a program. QT_LUPDATE_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/lupdate-qt4 //The location of the Qt mkspecs containing qconfig.pri QT_MKSPECS_DIR:PATH=/usr/lib64/qt4/mkspecs //Path to a program. QT_MOC_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/moc-qt4 //Path to a library. QT_PHONONWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_PHONONWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_PHONONWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/designer/libphononwidgets.so //Path to a file. QT_PHONON_INCLUDE_DIR:PATH=/usr/include/phonon //The Qt PHONON library QT_PHONON_LIBRARY:STRING=optimized;/usr/lib64/libphonon.so;debug;/usr/lib64/libphonon.so //Path to a library. QT_PHONON_LIBRARY_DEBUG:FILEPATH=QT_PHONON_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_PHONON_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libphonon.so //The location of the Qt plugins QT_PLUGINS_DIR:PATH=/usr/lib64/qt4/plugins //Path to a library. QT_QCNCODECS_PLUGIN_DEBUG:FILEPATH=QT_QCNCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCNCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/codecs/libqcncodecs.so //Path to a program. QT_QCOLLECTIONGENERATOR_EXECUTABLE:FILEPATH=/usr/lib64/qt4/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=QT_QGENERICBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QGIF_PLUGIN_DEBUG:FILEPATH=QT_QGIF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGIF_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/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=/usr/lib64/qt4/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=/usr/lib64/qt4/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=/usr/lib64/qt4/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=/usr/lib64/qt4/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=/usr/lib64/qt4/plugins/codecs/libqkrcodecs.so //Where can the qmake-qt4 library be found QT_QMAKE_EXECUTABLE:FILEPATH=/usr/local/Trolltech/Qt-4.8.6/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=/usr/lib64/qt4/plugins/imageformats/libqmng.so //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=/usr/lib64/qt4/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=/usr/lib64/qt4/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=/usr/lib64/qt4/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=/usr/lib64/qt4/plugins/designer/libqt3supportwidgets.so //Path to a file. QT_QT3SUPPORT_INCLUDE_DIR:PATH=/usr/include/Qt3Support //The Qt QT3SUPPORT library QT_QT3SUPPORT_LIBRARY:STRING=optimized;/usr/lib64/libQt3Support.so;debug;/usr/lib64/libQt3Support_debug.so //Path to a library. QT_QT3SUPPORT_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQt3Support_debug.so //Path to a library. QT_QT3SUPPORT_LIBRARY_RELEASE:FILEPATH=/usr/lib64/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=/usr/lib64/qt4/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=/usr/lib64/qt4/plugins/accessible/libqtaccessiblewidgets.so //Path to a file. QT_QTASSISTANTCLIENT_INCLUDE_DIR:PATH=/usr/include/QtAssistant //The Qt QTASSISTANTCLIENT library QT_QTASSISTANTCLIENT_LIBRARY:STRING=optimized;/usr/lib64/libQtAssistantClient.so;debug;/usr/lib64/libQtAssistantClient_debug.so //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtAssistantClient_debug.so //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtAssistantClient.so //Path to a file. QT_QTASSISTANT_INCLUDE_DIR:PATH=/usr/include/QtAssistant //The Qt QTASSISTANT library QT_QTASSISTANT_LIBRARY:STRING=optimized;/usr/lib64/libQtAssistantClient.so;debug;/usr/lib64/libQtAssistantClient_debug.so //Path to a library. QT_QTASSISTANT_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtAssistantClient_debug.so //Path to a library. QT_QTASSISTANT_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtAssistantClient.so //The Qt QTCLUCENE library QT_QTCLUCENE_LIBRARY:STRING=optimized;/usr/lib64/libQtCLucene.so;debug;/usr/lib64/libQtCLucene_debug.so //Path to a library. QT_QTCLUCENE_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtCLucene_debug.so //Path to a library. QT_QTCLUCENE_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtCLucene.so //Path to a file. QT_QTCORE_INCLUDE_DIR:PATH=/usr/include/QtCore //The Qt QTCORE library QT_QTCORE_LIBRARY:STRING=optimized;/usr/lib64/libQtCore.so;debug;/usr/lib64/libQtCore_debug.so //Path to a library. QT_QTCORE_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtCore_debug.so //Path to a library. QT_QTCORE_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtCore.so //Path to a file. QT_QTDBUS_INCLUDE_DIR:PATH=/usr/include/QtDBus //The Qt QTDBUS library QT_QTDBUS_LIBRARY:STRING=optimized;/usr/lib64/libQtDBus.so;debug;/usr/lib64/libQtDBus_debug.so //Path to a library. QT_QTDBUS_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtDBus_debug.so //Path to a library. QT_QTDBUS_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtDBus.so //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=/usr/include/QtDesigner //The Qt QTDESIGNERCOMPONENTS library QT_QTDESIGNERCOMPONENTS_LIBRARY:STRING=optimized;/usr/lib64/libQtDesignerComponents.so;debug;/usr/lib64/libQtDesignerComponents_debug.so //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtDesignerComponents_debug.so //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtDesignerComponents.so //Path to a file. QT_QTDESIGNER_INCLUDE_DIR:PATH=/usr/include/QtDesigner //The Qt QTDESIGNER library QT_QTDESIGNER_LIBRARY:STRING=optimized;/usr/lib64/libQtDesigner.so;debug;/usr/lib64/libQtDesigner_debug.so //Path to a library. QT_QTDESIGNER_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtDesigner_debug.so //Path to a library. QT_QTDESIGNER_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtDesigner.so //Path to a file. QT_QTGUI_INCLUDE_DIR:PATH=/usr/include/QtGui //The Qt QTGUI library QT_QTGUI_LIBRARY:STRING=optimized;/usr/lib64/libQtGui.so;debug;/usr/lib64/libQtGui_debug.so //Path to a library. QT_QTGUI_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtGui_debug.so //Path to a library. QT_QTGUI_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtGui.so //Path to a file. QT_QTHELP_INCLUDE_DIR:PATH=/usr/include/QtHelp //The Qt QTHELP library QT_QTHELP_LIBRARY:STRING=optimized;/usr/lib64/libQtHelp.so;debug;/usr/lib64/libQtHelp_debug.so //Path to a library. QT_QTHELP_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtHelp_debug.so //Path to a library. QT_QTHELP_LIBRARY_RELEASE:FILEPATH=/usr/lib64/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=/usr/lib64/qt4/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=/usr/include/QtMultimedia //The Qt QTMULTIMEDIA library QT_QTMULTIMEDIA_LIBRARY:STRING=optimized;/usr/lib64/libQtMultimedia.so;debug;/usr/lib64/libQtMultimedia_debug.so //Path to a library. QT_QTMULTIMEDIA_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtMultimedia_debug.so //Path to a library. QT_QTMULTIMEDIA_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtMultimedia.so //Path to a file. QT_QTNETWORK_INCLUDE_DIR:PATH=/usr/include/QtNetwork //The Qt QTNETWORK library QT_QTNETWORK_LIBRARY:STRING=optimized;/usr/lib64/libQtNetwork.so;debug;/usr/lib64/libQtNetwork_debug.so //Path to a library. QT_QTNETWORK_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtNetwork_debug.so //Path to a library. QT_QTNETWORK_LIBRARY_RELEASE:FILEPATH=/usr/lib64/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=/usr/include/QtOpenGL //The Qt QTOPENGL library QT_QTOPENGL_LIBRARY:STRING=optimized;/usr/lib64/libQtOpenGL.so;debug;/usr/lib64/libQtOpenGL_debug.so //Path to a library. QT_QTOPENGL_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtOpenGL_debug.so //Path to a library. QT_QTOPENGL_LIBRARY_RELEASE:FILEPATH=/usr/lib64/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=/usr/lib64/qt4/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=/usr/lib64/qt4/plugins/script/libqtscriptdbus.so //Path to a file. QT_QTSCRIPTTOOLS_INCLUDE_DIR:PATH=/usr/include/QtScriptTools //The Qt QTSCRIPTTOOLS library QT_QTSCRIPTTOOLS_LIBRARY:STRING=optimized;/usr/lib64/libQtScriptTools.so;debug;/usr/lib64/libQtScriptTools_debug.so //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtScriptTools_debug.so //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtScriptTools.so //Path to a file. QT_QTSCRIPT_INCLUDE_DIR:PATH=/usr/include/QtScript //The Qt QTSCRIPT library QT_QTSCRIPT_LIBRARY:STRING=optimized;/usr/lib64/libQtScript.so;debug;/usr/lib64/libQtScript_debug.so //Path to a library. QT_QTSCRIPT_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtScript_debug.so //Path to a library. QT_QTSCRIPT_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtScript.so //Path to a file. QT_QTSQL_INCLUDE_DIR:PATH=/usr/include/QtSql //The Qt QTSQL library QT_QTSQL_LIBRARY:STRING=optimized;/usr/lib64/libQtSql.so;debug;/usr/lib64/libQtSql_debug.so //Path to a library. QT_QTSQL_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtSql_debug.so //Path to a library. QT_QTSQL_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtSql.so //Path to a file. QT_QTSVG_INCLUDE_DIR:PATH=/usr/include/QtSvg //The Qt QTSVG library QT_QTSVG_LIBRARY:STRING=optimized;/usr/lib64/libQtSvg.so;debug;/usr/lib64/libQtSvg_debug.so //Path to a library. QT_QTSVG_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtSvg_debug.so //Path to a library. QT_QTSVG_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtSvg.so //Path to a file. QT_QTTEST_INCLUDE_DIR:PATH=/usr/include/QtTest //The Qt QTTEST library QT_QTTEST_LIBRARY:STRING=optimized;/usr/lib64/libQtTest.so;debug;/usr/lib64/libQtTest_debug.so //Path to a library. QT_QTTEST_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtTest_debug.so //Path to a library. QT_QTTEST_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtTest.so //Path to a file. QT_QTUITOOLS_INCLUDE_DIR:PATH=/usr/include/QtUiTools //The Qt QTUITOOLS library QT_QTUITOOLS_LIBRARY:STRING=optimized;/usr/lib64/libQtUiTools.a;debug;/usr/lib64/libQtUiTools_debug.a //Path to a library. QT_QTUITOOLS_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtUiTools_debug.a //Path to a library. QT_QTUITOOLS_LIBRARY_RELEASE:FILEPATH=/usr/lib64/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=/usr/lib64/qt4/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=/usr/include/QtXmlPatterns //The Qt QTXMLPATTERNS library QT_QTXMLPATTERNS_LIBRARY:STRING=optimized;/usr/lib64/libQtXmlPatterns.so;debug;/usr/lib64/libQtXmlPatterns_debug.so //Path to a library. QT_QTXMLPATTERNS_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtXmlPatterns_debug.so //Path to a library. QT_QTXMLPATTERNS_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libQtXmlPatterns.so //Path to a file. QT_QTXML_INCLUDE_DIR:PATH=/usr/include/QtXml //The Qt QTXML library QT_QTXML_LIBRARY:STRING=optimized;/usr/lib64/libQtXml.so;debug;/usr/lib64/libQtXml_debug.so //Path to a library. QT_QTXML_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libQtXml_debug.so //Path to a library. QT_QTXML_LIBRARY_RELEASE:FILEPATH=/usr/lib64/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=/usr/lib64/qt4/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=/usr/lib64/qt4/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=/usr/share/qt4/translations //Path to a program. QT_UIC3_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/uic3 //Path to a program. QT_UIC_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/uic-qt4 //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE:FILEPATH=/usr/lib64/qt4/plugins/designer/libworldtimeclockplugin.so //xmlpatterns used to generate html from Proxy documentation. QT_XMLPATTERNS_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/xmlpatterns //Dependencies for the target QVTKWidgetPlugin_LIB_DEPENDS:STATIC=optimized;/usr/lib64/libQtGui.so;debug;/usr/lib64/libQtGui_debug.so;optimized;/usr/lib64/libQtCore.so;debug;/usr/lib64/libQtCore_debug.so; //Value Computed by CMake QtTesting_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/ThirdParty/QtTesting/vtkqttesting //Dependencies for the target QtTesting_LIB_DEPENDS:STATIC=optimized;/usr/lib64/libQtGui.so;debug;/usr/lib64/libQtGui_debug.so;optimized;/usr/lib64/libQtCore.so;debug;/usr/lib64/libQtCore_debug.so; //Value Computed by CMake QtTesting_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/ThirdParty/QtTesting/vtkqttesting //Value Computed by CMake RGBZView_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/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=/u/wk/jcbecker/ParaView/Plugins/RGBZView //Path to scp command, used by CTest for submitting results to // a Dart server SCPCOMMAND:FILEPATH=/usr/bin/scp //Path to a file. SILO_INCLUDE_DIR:PATH=/usr/local/include //Path to a library. SILO_LIBRARY:FILEPATH=/usr/local/lib/libsiloh5.a //Name of the computer/site where compile is being run SITE:STRING=linux156.nas.nasa.gov //Dependencies for the target SLACTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Path to the SLURM sbatch executable SLURM_SBATCH_COMMAND:FILEPATH=SLURM_SBATCH_COMMAND-NOTFOUND //Path to the SLURM srun executable SLURM_SRUN_COMMAND:FILEPATH=SLURM_SRUN_COMMAND-NOTFOUND //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 //Path to a program. SVNCOMMAND:FILEPATH=/usr/bin/svn //Value Computed by CMake SciberQuestToolKit_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Plugins/SciberQuestToolKit //Dependencies for the target SciberQuestToolKit_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkSciberQuest;general;vtkSciberQuestCS;general;vtkFiltersFlowPaths;general;vtkSciberQuest;general;vtkPVServerManagerDefault;general;vtksys;general;pqComponents; //Value Computed by CMake SciberQuestToolKit_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Plugins/SciberQuestToolKit //Dependencies for the target SierraPlotTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVVTKExtensionsDefault; //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;vtkRenderingLIC; //Use HIDDEN visibility support if available. USE_COMPILER_HIDDEN_VISIBILITY:BOOL=ON //Dependencies for the target UncertaintyRendering_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkRenderingParallel; //Build VisIt Reader CGNS VISIT_BUILD_READER_CGNS:BOOL=OFF //Build VisIt Reader GMV VISIT_BUILD_READER_GMV:BOOL=OFF //Build VisIt Reader Mili VISIT_BUILD_READER_Mili:BOOL=OFF //Build VisIt Reader Silo VISIT_BUILD_READER_Silo:BOOL=ON //Disable compiler warnings VISIT_DISABLE_COMPILER_WARNINGS:BOOL=ON //Value Computed by CMake VPIC_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/VPIC //Dependencies for the target VPIC_LIB_DEPENDS:STATIC=general;vtksys; //Value Computed by CMake VPIC_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/VPIC //Value Computed by CMake VTKEXPAT_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake VTKEXPAT_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake VTKFREETYPE_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/freetype/vtkfreetype //Value Computed by CMake VTKFREETYPE_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/freetype/vtkfreetype //Value Computed by CMake VTKFTGL_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/ftgl //Value Computed by CMake VTKFTGL_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/ftgl //Value Computed by CMake VTKGL2PS_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKGL2PS_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKJPEG_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKJPEG_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKNETCDF_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKNETCDF_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKOGGTHEORA_BINARY_DIR:STATIC=/u/wk/jcbecker/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="/u/wk/jcbecker/ParaView/VTK/ThirdParty/oggtheora/vtkoggtheora/vtkoggtheora.vscript" //Value Computed by CMake VTKOGGTHEORA_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/oggtheora/vtkoggtheora //Value Computed by CMake VTKPNG_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/png/vtkpng //Value Computed by CMake VTKPNG_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/png/vtkpng //Value Computed by CMake VTKTIFF_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake VTKTIFF_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake VTKZLIB_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/zlib/vtkzlib //Value Computed by CMake VTKZLIB_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/zlib/vtkzlib //Build all vtkObject derived classes with object factory new methods. VTK_ALL_NEW_OBJECT_FACTORY:BOOL=OFF //Value Computed by CMake VTK_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK //Request to build all modules VTK_BUILD_ALL_MODULES:BOOL=OFF //Enable modules as needed for testing all the enabled modules VTK_BUILD_ALL_MODULES_FOR_TESTS:BOOL=OFF //Build a BenchmarkFreeTypeRendering test that benchmarks freetype // rendering performance. VTK_BUILD_FREETYPE_BENCHMARK: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 //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 //Path to a program. VTK_GHOSTSCRIPT_EXECUTABLE:FILEPATH=/usr/bin/gs //Location of the OpenGL extensions header file (glext.h). VTK_GLEXT_FILE:FILEPATH=/u/wk/jcbecker/ParaView/VTK/Utilities/ParseOGLExt/headers/glext.h //Location of the GLX extensions header file (glxext.h). VTK_GLXEXT_FILE:FILEPATH=/u/wk/jcbecker/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 //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 //Should all modules build instantiators VTK_MAKE_INSTANTIATORS:BOOL=OFF //Max number of threads vktMultiThreader will allocate. VTK_MAX_THREADS:STRING=64 //The OpenGL library being used supports off screen Mesa calls VTK_OPENGL_HAS_OSMESA:BOOL=OFF //Python version to use: 2, 2.x, or empty VTK_PYTHON_VERSION:STRING=2 VTK_QT_VERSION:STRING=4 //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, Simple, Kaapi or TBB VTK_SMP_IMPLEMENTATION_TYPE:STRING=Sequential //Value Computed by CMake VTK_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK //Build VTK with 64 bit ids VTK_USE_64BIT_IDS:BOOL=ON //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 system 'autobahn' Python package VTK_USE_SYSTEM_AUTOBAHN: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 HDF5 VTK_USE_SYSTEM_HDF5:BOOL=ON //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 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 VisItLib VTK_USE_SYSTEM_VISITLIB: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=ON //Build VPIC with MPI VTK_VPIC_USE_MPI:BOOL=OFF //Location of the WGL extensions header file (wglext.h). VTK_WGLEXT_FILE:FILEPATH=/u/wk/jcbecker/ParaView/VTK/Utilities/ParseOGLExt/headers/wglext.h //Path to a file. VTK_WRAP_HINTS:FILEPATH=/u/wk/jcbecker/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 //Value Computed by CMake VisItBridgePlugin_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/Library/VisItLib //Value Computed by CMake VisItBridgePlugin_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib //Value Computed by CMake VisItNETCDF_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/NETCDF //Value Computed by CMake VisItNETCDF_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF //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=/usr/include //Path to a library. X11_XTest_LIB:FILEPATH=/usr/lib64/libXtst.so //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=/usr/include //Path to a library. X11_Xcomposite_LIB:FILEPATH=/usr/lib64/libXcomposite.so //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=/usr/include //Path to a library. X11_Xmu_LIB:FILEPATH=/usr/lib64/libXmu.so //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=/usr/include //Path to a library. ZLIB_LIBRARY:FILEPATH=/usr/lib64/libz.so //Value Computed by CMake alglib_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/alglib //Value Computed by CMake alglib_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/alglib //Dependencies for the target avtdatabase_ser_LIB_DEPENDS:STATIC=general;avtdbatts;general;avtpipeline_ser;general;visit_vtk; //Dependencies for the target avtdbatts_LIB_DEPENDS:STATIC=general;visitcommon; //Dependencies for the target avtivp_LIB_DEPENDS:STATIC=general;avtmath;general;visitcommon;general;visit_vtk;general;vtkCommonCore;general;vtkFiltersGeneral; //Dependencies for the target avtmath_LIB_DEPENDS:STATIC=general;visitcommon;general;vtkCommonCore; //Dependencies for the target avtpipeline_ser_LIB_DEPENDS:STATIC=general;visitcommon;general;avtmath;general;avtdbatts;general;lightweight_visit_vtk;general;vtkFiltersCore;general;vtkInteractionStyle;general;vtkIOLegacy;general;vtkIOXML;general;vtkRenderingOpenGL;general;vtkFiltersGeometry;general;vtkzlib; //Value Computed by CMake lightweight_visit_vtk_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/Library/VisItLib/visit_vtk/lightweight //Dependencies for the target lightweight_visit_vtk_LIB_DEPENDS:STATIC=general;visitcommon;general;vtkCommonCore;general;vtkFiltersGeneral;general;vtkIOXML;general;vtkIOLegacy; //Value Computed by CMake lightweight_visit_vtk_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/visit_vtk/lightweight //Value Computed by CMake netcdf_cxx_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf/cxx //Value Computed by CMake netcdf_cxx_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/cxx //Value Computed by CMake netcdf_libdispatch_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_libdispatch_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_liblib_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_liblib_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_libsrc4_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc4_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Value Computed by CMake netcdf_libsrc_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Dependencies for the target pqApplicationComponents_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkGUISupportQt;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys; //Dependencies for the target pqComponents_LIB_DEPENDS:STATIC=general;pqCore;general;pqPython;general;vtkChartsCore;general;vtkIOImage;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys; //Dependencies for the target pqCore_LIB_DEPENDS:STATIC=general;pqWidgets;general;vtkGUISupportQt;general;vtkPVAnimation;general;vtkPVClientServerCoreDefault;general;vtkPVServerManagerApplication;general;vtkPVServerManagerDefault;general;vtksys;general;vtkTestingRendering;optimized;/usr/lib64/libQtUiTools.a;debug;/usr/lib64/libQtUiTools_debug.a;optimized;/usr/lib64/libQtGui.so;debug;/usr/lib64/libQtGui_debug.so;optimized;/usr/lib64/libQtXml.so;debug;/usr/lib64/libQtXml_debug.so;optimized;/usr/lib64/libQtCore.so;debug;/usr/lib64/libQtCore_debug.so; //Dependencies for the target pqPython_LIB_DEPENDS:STATIC=general;pqCore;general;vtkPythonInterpreter;general;vtkWrappingPythonCore;general;/usr/lib64/libpython2.6.so; //Dependencies for the target pqWidgets_LIB_DEPENDS:STATIC=general;vtkGUISupportQt;general;vtkPVServerManagerCore;general;QtTesting;optimized;/usr/lib64/libQtHelp.so;debug;/usr/lib64/libQtHelp_debug.so;optimized;/usr/lib64/libQtGui.so;debug;/usr/lib64/libQtGui_debug.so;optimized;/usr/lib64/libQtXml.so;debug;/usr/lib64/libQtXml_debug.so;optimized;/usr/lib64/libQtSql.so;debug;/usr/lib64/libQtSql_debug.so;optimized;/usr/lib64/libQtNetwork.so;debug;/usr/lib64/libQtNetwork_debug.so;optimized;/usr/lib64/libQtCore.so;debug;/usr/lib64/libQtCore_debug.so; //Dependencies for the target protobuf-lite_LIB_DEPENDS:STATIC=general;-lpthread; //Value Computed by CMake protobuf_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/ThirdParty/protobuf/vtkprotobuf //Dependencies for the target protobuf_LIB_DEPENDS:STATIC=general;-lpthread;general;/usr/lib64/libz.so; //Value Computed by CMake protobuf_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/ThirdParty/protobuf/vtkprotobuf //Path to smooth.flash data file. smooth_flash:FILEPATH=smooth_flash-NOTFOUND //Value Computed by CMake verdict_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/verdict/vtkverdict //Dependencies for target verdict_LIB_DEPENDS:STATIC= //Value Computed by CMake verdict_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/verdict/vtkverdict //Value Computed by CMake visit_vtk_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/Library/VisItLib/visit_vtk/full //Dependencies for the target visit_vtk_LIB_DEPENDS:STATIC=general;visitcommon;general;lightweight_visit_vtk;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersExtraction;general;vtkFiltersFlowPaths;general;vtkImagingHybrid;general;vtkInteractionStyle;general;vtkIOLegacy;general;vtkRenderingOpenGL; //Value Computed by CMake visit_vtk_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/visit_vtk/full //Value Computed by CMake visitcommon_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/Library/VisItLib/common //Dependencies for the target visitcommon_LIB_DEPENDS:STATIC=general;dl; //Value Computed by CMake visitcommon_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common //Dependencies for the target vtkChartsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkChartsCore; //Dependencies for the target vtkChartsCorePythonD_LIB_DEPENDS:STATIC=general;vtkChartsCore;general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkInfovisCorePythonD;general;vtkRenderingContext2DPythonD; //Dependencies for the target vtkChartsCorePython_LIB_DEPENDS:STATIC=general;vtkChartsCorePythonD; //Dependencies for the target vtkChartsCore_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkCommonColor;general;vtkInfovisCore; //Dependencies for the target vtkClientServer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/usr/lib64/libpython2.6.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;vtkCommonColor;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD; //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;vtkCommonComputationalGeometry;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD; //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;vtkCommonCore;general;vtkWrappingPythonCore; //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;vtkCommonDataModel;general;vtkWrappingPythonCore;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD; //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;vtkCommonExecutionModel;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD; //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;vtkCommonMath;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD; //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;vtkCommonMisc;general;vtkWrappingPythonCore;general;vtkCommonMathPythonD; //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;vtkCommonSystem;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD; //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;vtkCommonTransforms;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD; //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;vtkDomainsChemistry;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOXMLPythonD;general;vtkRenderingCorePythonD; //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=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/exodusII/vtkexodusII //Value Computed by CMake vtkExodus2_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/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; //Dependencies for the target vtkFiltersAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersAMR; //Dependencies for the target vtkFiltersAMRPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkParallelCorePythonD; //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;vtkFiltersCore;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD; //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;vtkFiltersExtraction;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersStatisticsPythonD; //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;vtkFiltersFlowPaths;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOCorePythonD; //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;vtkFiltersGeneral;general;vtkWrappingPythonCore;general;vtkCommonComputationalGeometryPythonD;general;vtkFiltersCorePythonD; //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;vtkFiltersGeneric;general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD; //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;vtkFiltersGeometry;general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD; //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;vtkFiltersHybrid;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingCorePythonD; //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;vtkFiltersHyperTree;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD; //Dependencies for the target vtkFiltersHyperTreePython_LIB_DEPENDS:STATIC=general;vtkFiltersHyperTreePythonD; //Dependencies for the target vtkFiltersHyperTree_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersModelingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersModeling; //Dependencies for the target vtkFiltersModelingPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersModeling;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD; //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 vtkFiltersParallelPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallel;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersModelingPythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD; //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;vtkFiltersParallelStatistics;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersStatisticsPythonD;general;vtkParallelCorePythonD; //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 vtkFiltersProgrammableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersProgrammable; //Dependencies for the target vtkFiltersProgrammablePythonD_LIB_DEPENDS:STATIC=general;vtkFiltersProgrammable;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD; //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;vtkFiltersPython;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD; //Dependencies for the target vtkFiltersPythonPython_LIB_DEPENDS:STATIC=general;vtkFiltersPythonPythonD; //Dependencies for the target vtkFiltersPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;/usr/lib64/libpython2.6.so;general;vtkWrappingPythonCore; //Dependencies for the target vtkFiltersSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersSources; //Dependencies for the target vtkFiltersSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersSources;general;vtkWrappingPythonCore;general;vtkCommonComputationalGeometryPythonD;general;vtkFiltersGeneralPythonD; //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;vtkFiltersStatistics;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingFourierPythonD; //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;vtkFiltersTexture;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD; //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;vtkFiltersVerdict;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD; //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 vtkGUISupportQt_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkInteractionStyle;general;vtkRenderingOpenGL;general;vtkFiltersExtraction;optimized;/usr/lib64/libQtGui.so;debug;/usr/lib64/libQtGui_debug.so;optimized;/usr/lib64/libQtNetwork.so;debug;/usr/lib64/libQtNetwork_debug.so;optimized;/usr/lib64/libQtCore.so;debug;/usr/lib64/libQtCore_debug.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;vtkIOAMR;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkParallelCorePythonD; //Dependencies for the target vtkIOAMRPython_LIB_DEPENDS:STATIC=general;vtkIOAMRPythonD; //Dependencies for the target vtkIOAMR_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkParallelCore;general;/usr/local/lib/libhdf5.so;general;/usr/lib64/libz.so;general;/usr/lib64/libm.so;general;/usr/local/lib/libhdf5_hl.so;general;/usr/local/lib/libhdf5.so;general;vtksys; //Dependencies for the target vtkIOCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOCore; //Dependencies for the target vtkIOCorePythonD_LIB_DEPENDS:STATIC=general;vtkIOCore;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD; //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;vtkIOEnSight;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD; //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;vtkIOExodus;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkIOXMLPythonD; //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 vtkIOExportPythonD_LIB_DEPENDS:STATIC=general;vtkIOExport;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersGeometryPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingGL2PSPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingOpenGLPythonD; //Dependencies for the target vtkIOExportPython_LIB_DEPENDS:STATIC=general;vtkIOExportPythonD; //Dependencies for the target vtkIOExport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkImagingCore;general;vtkRenderingAnnotation;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingGL2PS;general;vtkRenderingLabel;general;vtkRenderingOpenGL;general;vtkIOImage;general;vtkFiltersGeometry;general;vtkgl2ps; //Dependencies for the target vtkIOGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOGeometry; //Dependencies for the target vtkIOGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkIOGeometry;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD; //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;vtkjsoncpp;general;vtksys; //Dependencies for the target vtkIOImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImage; //Dependencies for the target vtkIOImagePythonD_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOCorePythonD; //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;vtkIOImport;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD; //Dependencies for the target vtkIOImportPython_LIB_DEPENDS:STATIC=general;vtkIOImportPythonD; //Dependencies for the target vtkIOImport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkFiltersSources; //Dependencies for the target vtkIOInfovisCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOInfovis; //Dependencies for the target vtkIOInfovisPythonD_LIB_DEPENDS:STATIC=general;vtkIOInfovis;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkInfovisCorePythonD; //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;vtkIOLSDyna;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkIOXMLPythonD; //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;vtkIOLegacy;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD; //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 vtkIOMovieCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMovie; //Dependencies for the target vtkIOMoviePythonD_LIB_DEPENDS:STATIC=general;vtkIOMovie;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD; //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;vtkIONetCDF;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD; //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;vtkIOPLY;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOGeometryPythonD; //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;vtkIOParallelExodus;general;vtkWrappingPythonCore;general;vtkIOExodusPythonD;general;vtkIOExodusPythonD;general;vtkParallelCorePythonD; //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;vtkIOParallelLSDyna;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkIOLSDynaPythonD;general;vtkParallelCorePythonD; //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 vtkIOParallelPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallel;general;vtkWrappingPythonCore;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkIONetCDFPythonD;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD; //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;vtkIOParallelXML;general;vtkWrappingPythonCore;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD; //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;vtkNetCDF;general;vtkNetCDF_cxx; //Dependencies for the target vtkIOVPICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOVPIC; //Dependencies for the target vtkIOVPICPythonD_LIB_DEPENDS:STATIC=general;vtkIOVPIC;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkParallelCorePythonD; //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 vtkIOVisItBridgeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOVisItBridge; //Dependencies for the target vtkIOVisItBridgePythonD_LIB_DEPENDS:STATIC=general;vtkIOVisItBridge;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersAMRPythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;general;vtkRenderingOpenGLPythonD; //Dependencies for the target vtkIOVisItBridgePython_LIB_DEPENDS:STATIC=general;vtkIOVisItBridgePythonD; //Dependencies for the target vtkIOVisItBridge_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersAMR;general;vtkParallelCore;general;/usr/local/lib/libhdf5.so;general;/usr/lib64/libz.so;general;/usr/lib64/libm.so;general;/usr/local/lib/libhdf5_hl.so;general;/usr/local/lib/libhdf5.so;general;vtkIOImage;general;vtkNetCDF;general;vtkNetCDF_cxx;general;vtkRenderingOpenGL;general;vtksys;general;vtkzlib;general;visitcommon;general;avtdatabase_ser;general;avtpipeline_ser;general;avtivp;general;visit_vtk;general;/usr/local/lib/libsiloh5.a; //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;vtkIOXMLParser;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD; //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;vtkIOXML;general;vtkWrappingPythonCore;general;vtkIOGeometryPythonD;general;vtkIOXMLParserPythonD; //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;vtkIOXdmf2;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD; //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;vtkImagingColor;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD; //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;vtkImagingCore;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD; //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;vtkImagingFourier;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD; //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;vtkImagingGeneral;general;vtkWrappingPythonCore;general;vtkImagingSourcesPythonD; //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;vtkImagingHybrid;general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkImagingCorePythonD; //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;vtkImagingMorphological;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD; //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;vtkImagingSources;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD; //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;vtkInfovisCore;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD; //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;vtkInteractionImage;general;vtkWrappingPythonCore;general;vtkImagingColorPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD; //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;vtkInteractionStyle;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD; //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;vtkInteractionWidgets;general;vtkWrappingPythonCore;general;vtkFiltersHybridPythonD;general;vtkFiltersModelingPythonD;general;vtkImagingGeneralPythonD;general;vtkImagingHybridPythonD;general;vtkInteractionStylePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingVolumePythonD; //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;/usr/local/lib/libhdf5.so;general;/usr/lib64/libz.so;general;/usr/lib64/libm.so;general;/usr/local/lib/libhdf5_hl.so;general;/usr/local/lib/libhdf5.so;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;vtkPVAnimation;general;vtkWrappingPythonCore;general;vtkIOMoviePythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerDefaultPythonD;general;vtkPVVTKExtensionsDefaultPythonD; //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;vtkPVCatalyst;general;vtkWrappingPythonCore;general;vtkPVServerManagerApplicationPythonD; //Dependencies for the target vtkPVCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVCatalystPythonD; //Dependencies for the target vtkPVCatalystTestDriverCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCatalystTestDriver; //Dependencies for the target vtkPVCatalystTestDriverPythonD_LIB_DEPENDS:STATIC=general;vtkPVCatalystTestDriver;general;vtkWrappingPythonCore;general;vtkPVCatalystPythonD; //Dependencies for the target vtkPVCatalystTestDriverPython_LIB_DEPENDS:STATIC=general;vtkPVCatalystTestDriverPythonD; //Dependencies for the target vtkPVCatalystTestDriver_LIB_DEPENDS:STATIC=general;vtkPVCatalyst; //Dependencies for the target vtkPVCatalyst_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtksys; //Dependencies for the target vtkPVClientServerCoreCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreCore; //Dependencies for the target vtkPVClientServerCoreCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCore;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersProgrammablePythonD;general;vtkPVCommonPythonD;general;vtkPVCommonPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkPythonInterpreterPythonD; //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;vtkPythonInterpreter;general;vtksys; //Dependencies for the target vtkPVClientServerCoreDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreDefault; //Dependencies for the target vtkPVClientServerCoreDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreDefault;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVVTKExtensionsDefaultPythonD; //Dependencies for the target vtkPVClientServerCoreDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreDefaultPythonD; //Dependencies for the target vtkPVClientServerCoreDefault_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVVTKExtensionsDefault;general;vtksys; //Dependencies for the target vtkPVClientServerCoreRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreRendering; //Dependencies for the target vtkPVClientServerCoreRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkWrappingPythonCore;general;vtkDomainsChemistryPythonD;general;vtkFiltersAMRPythonD;general;vtkPVClientServerCoreCorePythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkPVVTKExtensionsRenderingPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingVolumeAMRPythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkViewsContext2DPythonD;general;vtkViewsCorePythonD;general;vtkWebGLExporterPythonD; //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; //Dependencies for the target vtkPVCommonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCommon; //Dependencies for the target vtkPVCommonPythonD_LIB_DEPENDS:STATIC=general;vtkPVCommon;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOXMLParserPythonD; //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;vtkPVPythonCatalyst;general;vtkWrappingPythonCore;general;vtkPVCatalystPythonD;general;vtkPythonInterpreterPythonD; //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;vtkPVServerImplementationCore;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreCorePythonD; //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;vtkPVServerImplementationRendering;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVServerImplementationCorePythonD; //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;vtkPVServerManagerApplication;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;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;vtkIOMoviePythonD;general;vtkIONetCDFPythonD;general;vtkIOPLYPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelLSDynaPythonD;general;vtkIOVPICPythonD;general;vtkIOVisItBridgePythonD;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;vtkRenderingAnnotationPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypeOpenGLPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingLODPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkTestingRenderingPythonD;general;vtkViewsContext2DPythonD; //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;vtkCommonComputationalGeometryCS;general;vtkFiltersCoreCS;general;vtkFiltersGeneralCS;general;vtkIOCoreCS;general;vtkIOLegacyCS;general;vtkParallelCoreCS;general;vtkFiltersAMRCS;general;vtkImagingCoreCS;general;vtkImagingFourierCS;general;vtkFiltersStatisticsCS;general;vtkFiltersExtractionCS;general;vtkFiltersSourcesCS;general;vtkFiltersFlowPathsCS;general;vtkIOGeometryCS;general;vtkIOImageCS;general;vtkImagingHybridCS;general;vtkCommonColorCS;general;vtkFiltersGeometryCS;general;vtkRenderingCoreCS;general;vtkRenderingOpenGLCS;general;vtkRenderingVolumeCS;general;vtkRenderingVolumeOpenGLCS;general;vtkInteractionStyleCS;general;vtkFiltersModelingCS;general;vtkFiltersParallelCS;general;vtkFiltersProgrammableCS;general;vtkPythonInterpreterCS;general;vtkIOXMLParserCS;general;vtkPVCommonCS;general;vtkPVVTKExtensionsCoreCS;general;vtkPVClientServerCoreCoreCS;general;vtkPVServerImplementationCoreCS;general;vtkPVServerManagerCoreCS;general;vtkIOMovieCS;general;vtkIOXMLCS;general;vtkDomainsChemistryCS;general;vtkFiltersParallelStatisticsCS;general;vtkIOEnSightCS;general;vtkIOImportCS;general;vtkInfovisCoreCS;general;vtkIOInfovisCS;general;vtkIONetCDFCS;general;vtkIOParallelCS;general;vtkIOExodusCS;general;vtkIOParallelExodusCS;general;vtkIOParallelXMLCS;general;vtkImagingSourcesCS;general;vtkFiltersHybridCS;general;vtkImagingGeneralCS;general;vtkImagingColorCS;general;vtkRenderingFreeTypeCS;general;vtkRenderingAnnotationCS;general;vtkInteractionWidgetsCS;general;vtkRenderingContext2DCS;general;vtkChartsCoreCS;general;vtkFiltersGenericCS;general;vtkFiltersHyperTreeCS;general;vtkRenderingContextOpenGLCS;general;vtkRenderingGL2PSCS;general;vtkRenderingLabelCS;general;vtkIOExportCS;general;vtkRenderingFreeTypeOpenGLCS;general;vtkRenderingLICCS;general;vtkRenderingMatplotlibCS;general;vtkRenderingParallelCS;general;vtkPVVTKExtensionsRenderingCS;general;vtkPVVTKExtensionsDefaultCS;general;vtkRenderingVolumeAMRCS;general;vtkViewsCoreCS;general;vtkViewsContext2DCS;general;vtkWebGLExporterCS;general;vtkPVClientServerCoreRenderingCS;general;vtkPVClientServerCoreDefaultCS;general;vtkPVServerImplementationRenderingCS;general;vtkPVServerManagerRenderingCS;general;vtkTestingRenderingCS;general;vtkPVServerManagerDefaultCS;general;vtkPVAnimationCS;general;vtkFiltersPythonCS;general;vtkFiltersTextureCS;general;vtkFiltersVerdictCS;general;vtkIOAMRCS;general;vtkIOPLYCS;general;vtkIOLSDynaCS;general;vtkIOParallelLSDynaCS;general;vtkIOVPICCS;general;vtkIOVisItBridgeCS;general;vtkIOXdmf2CS;general;vtkImagingMorphologicalCS;general;vtkInteractionImageCS;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;vtkPVServerManagerCore;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkPVServerImplementationCorePythonD;general;vtkPythonInterpreterPythonD; //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;vtkPVServerManagerDefault;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreDefaultPythonD;general;vtkPVServerManagerRenderingPythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkTestingRenderingPythonD; //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;vtkPVServerManagerRendering;general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkPVServerImplementationRenderingPythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerCorePythonD; //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;vtksys;general;vtkCommonColor; //Dependencies for the target vtkPVVTKExtensionsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsCore; //Dependencies for the target vtkPVVTKExtensionsCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsCore;general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkPVCommonPythonD;general;vtkParallelCorePythonD; //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;vtkPVVTKExtensionsDefault;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkFiltersParallelStatisticsPythonD;general;vtkIOEnSightPythonD;general;vtkIOImportPythonD;general;vtkIOInfovisPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelXMLPythonD;general;vtkImagingFourierPythonD;general;vtkImagingSourcesPythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkPVVTKExtensionsRenderingPythonD; //Dependencies for the target vtkPVVTKExtensionsDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsDefaultPythonD; //Dependencies for the target vtkPVVTKExtensionsDefault_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkFiltersParallelStatistics;general;vtkIOEnSight;general;vtkIOImport;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; //Dependencies for the target vtkPVVTKExtensionsRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsRendering; //Dependencies for the target vtkPVVTKExtensionsRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsRendering;general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkCommonColorPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersParallelPythonD;general;vtkIOExportPythonD;general;vtkIOXMLPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypeOpenGLPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelPythonD; //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;vtkGUISupportQt;general;vtkIOExport;general;vtkIOXML;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkRenderingAnnotation;general;vtkRenderingFreeTypeOpenGL;general;vtkRenderingLIC;general;vtkRenderingMatplotlib;general;vtkRenderingOpenGL;general;vtkRenderingParallel;general;vtkCommonColor;general;vtkzlib; //Dependencies for the target vtkParaViewDocumentation_LIB_DEPENDS:STATIC=optimized;/usr/lib64/libQtGui.so;debug;/usr/lib64/libQtGui_debug.so;optimized;/usr/lib64/libQtNetwork.so;debug;/usr/lib64/libQtNetwork_debug.so;optimized;/usr/lib64/libQtCore.so;debug;/usr/lib64/libQtCore_debug.so; //Dependencies for the target vtkParaViewWebCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParaViewWebCore; //Dependencies for the target vtkParaViewWebCorePythonD_LIB_DEPENDS:STATIC=general;vtkParaViewWebCore;general;vtkWrappingPythonCore;general;vtkPVServerManagerDefaultPythonD;general;vtkWebCorePythonD;general;vtkWebGLExporterPythonD; //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;vtkParallelCore;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOLegacyPythonD; //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 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;vtkRenderingFreeTypeOpenGL;general;vtkRenderingOpenGL; //Dependencies for the target vtkPythonInterpreterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPythonInterpreter; //Dependencies for the target vtkPythonInterpreterPythonD_LIB_DEPENDS:STATIC=general;vtkPythonInterpreter;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD; //Dependencies for the target vtkPythonInterpreterPython_LIB_DEPENDS:STATIC=general;vtkPythonInterpreterPythonD; //Dependencies for the target vtkPythonInterpreter_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/usr/lib64/libpython2.6.so;general;vtksys; //Dependencies for the target vtkQvis_LIB_DEPENDS:STATIC=general;vtkCommonCore;optimized;/usr/lib64/libQtGui.so;debug;/usr/lib64/libQtGui_debug.so;optimized;/usr/lib64/libQtCore.so;debug;/usr/lib64/libQtCore_debug.so; //Dependencies for the target vtkRenderingAnnotationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingAnnotation; //Dependencies for the target vtkRenderingAnnotationPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingAnnotation;general;vtkWrappingPythonCore;general;vtkFiltersSourcesPythonD;general;vtkImagingColorPythonD;general;vtkRenderingFreeTypePythonD; //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;vtkRenderingContext2D;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD; //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;vtkRenderingContextOpenGL;general;vtkWrappingPythonCore;general;vtkRenderingContext2DPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD; //Dependencies for the target vtkRenderingContextOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGLPythonD; //Dependencies for the target vtkRenderingContextOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkRenderingOpenGL;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingCore; //Dependencies for the target vtkRenderingCorePythonD_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersSourcesPythonD; //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;vtkFiltersExtraction;general;vtksys; //Dependencies for the target vtkRenderingFreeTypeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingFreeTypeOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingFreeTypeOpenGL; //Dependencies for the target vtkRenderingFreeTypeOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypeOpenGL;general;vtkWrappingPythonCore;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD; //Dependencies for the target vtkRenderingFreeTypeOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypeOpenGLPythonD; //Dependencies for the target vtkRenderingFreeTypeOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingOpenGL; //Dependencies for the target vtkRenderingFreeTypePythonD_LIB_DEPENDS:STATIC=general;vtkRenderingFreeType;general;vtkWrappingPythonCore;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD; //Dependencies for the target vtkRenderingFreeTypePython_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypePythonD; //Dependencies for the target vtkRenderingFreeType_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkRenderingCore;general;vtkfreetype;general;vtkftgl; //Dependencies for the target vtkRenderingGL2PSCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingGL2PS; //Dependencies for the target vtkRenderingGL2PSPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingGL2PS;general;vtkWrappingPythonCore;general;vtkRenderingContextOpenGLPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD; //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; //Dependencies for the target vtkRenderingLICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLIC; //Dependencies for the target vtkRenderingLICPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingLIC;general;vtkWrappingPythonCore;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingOpenGLPythonD; //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; //Dependencies for the target vtkRenderingLODCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLOD; //Dependencies for the target vtkRenderingLODPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingLOD;general;vtkWrappingPythonCore;general;vtkFiltersModelingPythonD;general;vtkRenderingCorePythonD; //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;vtkRenderingLabel;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkRenderingFreeTypePythonD; //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;vtkRenderingMatplotlib;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkPythonInterpreterPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD; //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;vtkRenderingOpenGL;general;vtkWrappingPythonCore;general;vtkImagingHybridPythonD;general;vtkRenderingCorePythonD; //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;/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/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 vtkRenderingParallelPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingParallel;general;vtkWrappingPythonCore;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;general;vtkRenderingOpenGLPythonD; //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; //Dependencies for the target vtkRenderingVolumeAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeAMR; //Dependencies for the target vtkRenderingVolumeAMRPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeAMR;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkParallelCorePythonD;general;vtkRenderingVolumeOpenGLPythonD; //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;vtkRenderingVolumeOpenGL;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingVolumePythonD; //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; //Dependencies for the target vtkRenderingVolumePythonD_LIB_DEPENDS:STATIC=general;vtkRenderingVolume;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD; //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; //Dependencies for the target vtkTestingGenericBridge_LIB_DEPENDS:STATIC=general;vtkCommonDataModel; //Dependencies for the target vtkTestingRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkTestingRendering; //Dependencies for the target vtkTestingRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkTestingRendering;general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD; //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;vtkViewsContext2D;general;vtkWrappingPythonCore;general;vtkRenderingContext2DPythonD;general;vtkViewsCorePythonD; //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;vtkViewsCore;general;vtkWrappingPythonCore;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD; //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;vtkWebCore;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkIOCorePythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkWebGLExporterPythonD; //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/lib64/libpython2.6.so;general;vtkIOCore;general;vtkIOImage;general;vtkRenderingCore;general;vtkParallelCore;general;vtkWebGLExporter; //Dependencies for the target vtkWebGLExporterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkWebGLExporter; //Dependencies for the target vtkWebGLExporterPythonD_LIB_DEPENDS:STATIC=general;vtkWebGLExporter;general;vtkWrappingPythonCore;general;vtkFiltersGeometryPythonD;general;vtkIOExportPythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD; //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/lib64/libpython2.6.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 vtkftgl_LIB_DEPENDS:STATIC=general;/usr/lib64/libGL.so;general;vtkfreetype; //Dependencies for the target vtkgl2ps_LIB_DEPENDS:STATIC=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;m;general;vtkzlib;general;vtkpng;general;m; //Dependencies for the target vtkhdf5_LIB_DEPENDS:STATIC=general;m;general;dl;general;rt;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=/u/wk/jcbecker/ParaView-build/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=/u/wk/jcbecker/ParaView/VTK/ThirdParty/libxml2/vtklibxml2 //Value Computed by CMake vtkmetaio_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/Utilities/MetaIO/vtkmetaio //Dependencies for the target vtkmetaio_LIB_DEPENDS:STATIC=general;vtkzlib; //Value Computed by CMake vtkmetaio_SOURCE_DIR:STATIC=/u/wk/jcbecker/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=/u/wk/jcbecker/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=/u/wk/jcbecker/ParaView/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;/usr/local/lib/libhdf5.so;general;/usr/lib64/libz.so;general;/usr/lib64/libm.so;general;/usr/local/lib/libhdf5_hl.so;general;/usr/local/lib/libhdf5.so; //Dependencies for target vtkzlib_LIB_DEPENDS:STATIC= //Value Computed by CMake xdmf2_BINARY_DIR:STATIC=/u/wk/jcbecker/ParaView-build/VTK/ThirdParty/xdmf2/vtkxdmf2 //Value Computed by CMake xdmf2_SOURCE_DIR:STATIC=/u/wk/jcbecker/ParaView/VTK/ThirdParty/xdmf2/vtkxdmf2 ######################## # 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: BZRCOMMAND BZRCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Boost_DIR Boost_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Boost_INCLUDE_DIR Boost_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CGNS_INCLUDE_DIR CGNS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CGNS_LIBRARY CGNS_LIBRARY-ADVANCED:INTERNAL=1 //Have function clock_gettime CLOCK_GETTIME_IN_LIBC:INTERNAL= //Have library posix4 CLOCK_GETTIME_IN_LIBPOSIX4:INTERNAL= //Have library rt CLOCK_GETTIME_IN_LIBRT:INTERNAL=1 //Result of TRY_COMPILE CMAKE_ANSI_FOR_SCOPE:INTERNAL=TRUE //Have include iostream CMAKE_ANSI_STREAM_HEADERS:INTERNAL=1 //ADVANCED property for variable: CMAKE_AR CMAKE_AR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_BUILD_TOOL CMAKE_BUILD_TOOL-ADVANCED:INTERNAL=1 //What is the target build tool cmake is generating for. CMAKE_BUILD_TOOL:INTERNAL=/usr/bin/gmake //MODIFIED property for variable: CMAKE_BUILD_TYPE CMAKE_BUILD_TYPE-MODIFIED:INTERNAL=ON //STRINGS property for variable: CMAKE_BUILD_TYPE CMAKE_BUILD_TYPE-STRINGS:INTERNAL=Debug;Release;MinSizeRel;RelWithDebInfo //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=/u/wk/jcbecker/ParaView-build //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=2 //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=12 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/usr/local/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/usr/local/bin/cpack //ADVANCED property for variable: CMAKE_CTEST_COMMAND CMAKE_CTEST_COMMAND-ADVANCED:INTERNAL=1 //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/usr/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=/usr/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 //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 toolset. CMAKE_GENERATOR_TOOLSET:INTERNAL= //Result of TRY_COMPILE CMAKE_HAS_ANSI_STRING_STREAM:INTERNAL=TRUE //Is X11 around. CMAKE_HAS_X:INTERNAL=1 //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 include limits.h CMAKE_HAVE_LIMITS_H:INTERNAL=1 //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 //Have include sys/types.h;sys/prctl.h CMAKE_HAVE_SYS_PRCTL_H:INTERNAL=1 //Have include unistd.h CMAKE_HAVE_UNISTD_H:INTERNAL=1 //Start directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/u/wk/jcbecker/ParaView //ADVANCED property for variable: CMAKE_HP_PTHREADS CMAKE_HP_PTHREADS-ADVANCED:INTERNAL=1 //Install .so files without execute permission. CMAKE_INSTALL_SO_NO_EXE:INTERNAL=0 //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 ansi for scope. CMAKE_NO_ANSI_FOR_SCOPE:INTERNAL=0 //ADVANCED property for variable: CMAKE_NO_ANSI_STREAM_HEADERS CMAKE_NO_ANSI_STREAM_HEADERS-ADVANCED:INTERNAL=1 //Does the compiler support headers like iostream. CMAKE_NO_ANSI_STREAM_HEADERS:INTERNAL=0 //Does the compiler support sstream CMAKE_NO_ANSI_STRING_STREAM:INTERNAL=0 //Does the compiler support std::. CMAKE_NO_STD_NAMESPACE:INTERNAL=0 //number of local generators CMAKE_NUMBER_OF_LOCAL_GENERATORS:INTERNAL=402 //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=/u/wk/jcbecker/cmake-2.8.12.2 //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(char) CMAKE_SIZEOF_CHAR:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) CMAKE_SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) CMAKE_SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) CMAKE_SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(long) CMAKE_SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) CMAKE_SIZEOF_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(unsigned short) CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(void*) CMAKE_SIZEOF_VOID_P:INTERNAL=8 //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_USE_PTHREADS CMAKE_USE_PTHREADS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_USE_RELATIVE_PATHS CMAKE_USE_RELATIVE_PATHS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_USE_SPROC CMAKE_USE_SPROC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_USE_WIN32_THREADS CMAKE_USE_WIN32_THREADS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1 //Result of TEST_BIG_ENDIAN CMAKE_WORDS_BIGENDIAN:INTERNAL=0 //ADVANCED property for variable: CMAKE_X_CFLAGS CMAKE_X_CFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_X_LIBS CMAKE_X_LIBS-ADVANCED:INTERNAL=1 //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: COVERAGE_COMMAND COVERAGE_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: COVERAGE_EXTRA_FLAGS COVERAGE_EXTRA_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CTEST_SUBMIT_RETRY_COUNT CTEST_SUBMIT_RETRY_COUNT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CTEST_SUBMIT_RETRY_DELAY CTEST_SUBMIT_RETRY_DELAY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CVSCOMMAND CVSCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CVS_UPDATE_OPTIONS CVS_UPDATE_OPTIONS-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE CXX_HAVE_OFFSETOF:INTERNAL=TRUE //ADVANCED property for variable: DART_TESTING_TIMEOUT DART_TESTING_TIMEOUT-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE DEV_T_IS_SCALAR:INTERNAL=TRUE //ADVANCED property for variable: EXECINFO_LIB EXECINFO_LIB-ADVANCED:INTERNAL=1 EXECUTABLE_OUTPUT_PATH:INTERNAL=/u/wk/jcbecker/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: Eigen_DIR Eigen_DIR-ADVANCED: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.7.1()] //Details about finding HDF5 FIND_PACKAGE_MESSAGE_DETAILS_HDF5:INTERNAL=[/usr/local/lib/libhdf5.so;/usr/lib64/libz.so;/usr/lib64/libm.so;/usr/local/lib/libhdf5_hl.so;/usr/local/lib/libhdf5.so][/usr/local/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=[/usr/bin/python2][v2.6.6()] //Details about finding PythonLibs FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[/usr/lib64/libpython2.6.so][/usr/include/python2.6][v()] //Details about finding Qt4 FIND_PACKAGE_MESSAGE_DETAILS_Qt4:INTERNAL=[/usr/local/Trolltech/Qt-4.8.6/bin/qmake][/usr/lib64/qt4/bin/moc-qt4][/usr/lib64/qt4/bin/rcc][/usr/lib64/qt4/bin/uic-qt4][/usr/include][/usr/lib64][optimized;/usr/lib64/libQtCore.so;debug;/usr/lib64/libQtCore_debug.so][v4.8.6(4.7.0)] //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=[/usr/lib64/libz.so][/usr/include][v1.2.3()] //Result of TRY_COMPILE GETTIMEOFDAY_GIVES_TZ:INTERNAL=TRUE //ADVANCED property for variable: GITCOMMAND GITCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GIT_EXECUTABLE GIT_EXECUTABLE-ADVANCED:INTERNAL=1 //Test GLX_DECLARES_FUNCTION_glXGetProcAddress GLX_DECLARES_FUNCTION_glXGetProcAddress:INTERNAL=1 //Test GLX_DECLARES_FUNCTION_glXGetProcAddressARB GLX_DECLARES_FUNCTION_glXGetProcAddressARB:INTERNAL=1 //Test GLX_DECLARES_FUNCTION_glXGetProcAddressARB_AS_EMPTY GLX_DECLARES_FUNCTION_glXGetProcAddressARB_AS_EMPTY:INTERNAL= //Test GLX_DECLARES_FUNCTION_glXGetProcAddress_AS_EMPTY GLX_DECLARES_FUNCTION_glXGetProcAddress_AS_EMPTY:INTERNAL= //Test GLX_DEFINES_MACRO_GLX_ARB_get_proc_address GLX_DEFINES_MACRO_GLX_ARB_get_proc_address:INTERNAL=1 //Test GLX_DEFINES_MACRO_GLX_VERSION_1_1 GLX_DEFINES_MACRO_GLX_VERSION_1_1:INTERNAL=1 //Test GLX_DEFINES_MACRO_GLX_VERSION_1_2 GLX_DEFINES_MACRO_GLX_VERSION_1_2:INTERNAL=1 //Test GLX_DEFINES_MACRO_GLX_VERSION_1_3 GLX_DEFINES_MACRO_GLX_VERSION_1_3:INTERNAL=1 //Test GLX_DEFINES_MACRO_GLX_VERSION_1_4 GLX_DEFINES_MACRO_GLX_VERSION_1_4:INTERNAL=1 //Test GLX_DEFINES_TYPE_GLXFBConfig GLX_DEFINES_TYPE_GLXFBConfig:INTERNAL=1 //Test GLX_DEFINES_TYPE_GLXextFuncPtr GLX_DEFINES_TYPE_GLXextFuncPtr:INTERNAL=1 //Test GLX_DEFINES_TYPE_GLXextFuncPtr_AS_EMPTY GLX_DEFINES_TYPE_GLXextFuncPtr_AS_EMPTY:INTERNAL= //Test GLX_INCLUDES_GLXEXT GLX_INCLUDES_GLXEXT:INTERNAL=1 GLX_USES_MACRO_GLX_GLXEXT_LEGACY:INTERNAL=TRUE //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="ll" //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_CHAR:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_SIZEOF_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_SIZEOF_VOID_P: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 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 //Have includes ieeefp.h HAVE_IEEEFP_H:INTERNAL= //Have include inttypes.h HAVE_INTTYPES_H:INTERNAL=1 //Have function isascii HAVE_ISASCII:INTERNAL=1 //Result of TRY_COMPILE HAVE_KWSYS_SIZEOF_CHAR:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_KWSYS_SIZEOF___INT64:INTERNAL=FALSE //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 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_OFF64_T: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__BOOL:INTERNAL=TRUE //Have symbol snprintf HAVE_SNPRINTF:INTERNAL=1 //support for socklen_t HAVE_SOCKLEN_T:INTERNAL=1 //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 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 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 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 //Result of TRY_COMPILE HAVE_VTK_SIZEOF_CHAR:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTK_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTK_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTK_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTK_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTK_SIZEOF_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTK_SIZEOF_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTK_SIZEOF___INT64:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_VTK_UINTPTR_T:INTERNAL=TRUE //Have includes windows.h HAVE_WINDOWS_H:INTERNAL= //Result of TRY_COMPILE HAVE_WORDS_BIGENDIAN: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 //ADVANCED property for variable: HDF5_CXX_COMPILER_EXECUTABLE HDF5_CXX_COMPILER_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_C_COMPILER_EXECUTABLE HDF5_C_COMPILER_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_C_INCLUDE_DIR HDF5_C_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_DIFF_EXECUTABLE HDF5_DIFF_EXECUTABLE-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 //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 //ADVANCED property for variable: HDF5_ENABLE_INSTRUMENT HDF5_ENABLE_INSTRUMENT-ADVANCED:INTERNAL=1 //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 //Securely clear file buffers before writing to file HDF5_Enable_Clear_File_Buffers:INTERNAL=ON //Instrument The library HDF5_Enable_Instrument:INTERNAL=OFF //ADVANCED property for variable: HDF5_Fortran_COMPILER_EXECUTABLE HDF5_Fortran_COMPILER_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_HL_INCLUDE_DIR HDF5_HL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_IS_PARALLEL HDF5_IS_PARALLEL-ADVANCED:INTERNAL=1 //Used to pass variables between directories HDF5_LIBRARIES_TO_EXPORT:INTERNAL=vtkhdf5;vtkhdf5_hl //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 //Whether to perform strict file format checks HDF5_STRICT_FORMAT_CHECKS:INTERNAL=OFF //ADVANCED property for variable: HDF5_TEST_VFD HDF5_TEST_VFD-ADVANCED:INTERNAL=1 //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 //IF data accuracy is guaranteed during data conversions HDF5_WANT_DATA_ACCURACY:INTERNAL=ON //exception handling functions is checked during data conversions HDF5_WANT_DCONV_EXCEPTION:INTERNAL=ON //ADVANCED property for variable: HDF5_hdf5_LIBRARY_DEBUG HDF5_hdf5_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_hdf5_LIBRARY_RELEASE HDF5_hdf5_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_hdf5_hl_LIBRARY_DEBUG HDF5_hdf5_hl_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_hdf5_hl_LIBRARY_RELEASE HDF5_hdf5_hl_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_m_LIBRARY_DEBUG HDF5_m_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_m_LIBRARY_RELEASE HDF5_m_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_z_LIBRARY_DEBUG HDF5_z_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HDF5_z_LIBRARY_RELEASE HDF5_z_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HGCOMMAND HGCOMMAND-ADVANCED:INTERNAL=1 //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 //Result of TRY_RUN KWSYS_CHAR_IS_SIGNED:INTERNAL=0 //Result of TRY_COMPILE KWSYS_CHAR_IS_SIGNED_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_ARGUMENT_DEPENDENT_LOOKUP_COMPILED:INTERNAL=TRUE //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_CSTDDEF_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_FULL_SPECIALIZATION_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_LONG_LONG_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_MEMBER_TEMPLATES_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_NULL_TEMPLATE_ARGS_COMPILED:INTERNAL=FALSE //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_C_HAS_PTRDIFF_T_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_C_HAS_SSIZE_T_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_C_TYPE_MACROS_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_IOS_HAVE_BINARY_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_IOS_HAVE_STD_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_IOS_USE_ANSI_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_IOS_USE_SSTREAM_COMPILED:INTERNAL=TRUE //Result of TRY_RUN KWSYS_LFS_WORKS:INTERNAL=0 //Result of TRY_COMPILE KWSYS_LFS_WORKS_COMPILED:INTERNAL=TRUE //CHECK_TYPE_SIZE: sizeof(char) KWSYS_SIZEOF_CHAR:INTERNAL=1 //CHECK_TYPE_SIZE: __int64 unknown KWSYS_SIZEOF___INT64:INTERNAL= //Result of TRY_COMPILE KWSYS_STAT_HAS_ST_MTIM_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_STL_HAS_ALLOCATOR_MAX_SIZE_ARGUMENT_COMPILED:INTERNAL=FALSE //Result of TRY_COMPILE KWSYS_STL_HAS_ALLOCATOR_OBJECTS_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_STL_HAS_ALLOCATOR_REBIND_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_STL_HAS_ALLOCATOR_TEMPLATE_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_STL_HAS_ITERATOR_TRAITS_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_STL_HAS_WSTRING_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_STL_HAVE_STD_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_STL_STRING_HAVE_NEQ_CHAR_COMPILED:INTERNAL=TRUE //Have include sys/types.h;ifaddrs.h KWSYS_SYS_HAS_IFADDRS_H:INTERNAL=1 LIBRARY_OUTPUT_PATH:INTERNAL=/u/wk/jcbecker/ParaView-build/ThirdParty/protobuf/vtkprotobuf/bin //Result of TRY_COMPILE LONE_COLON:INTERNAL=TRUE //ADVANCED property for variable: MAKECOMMAND MAKECOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MEMORYCHECK_COMMAND MEMORYCHECK_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MEMORYCHECK_SUPPRESSIONS_FILE MEMORYCHECK_SUPPRESSIONS_FILE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MILI_INCLUDE_DIR MILI_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MILI_LIBRARY MILI_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_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 //Request building VisItLib Module_VisItLib:INTERNAL=OFF //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_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_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 //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 //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_vtkFiltersParallelFlowPaths Module_vtkFiltersParallelFlowPaths-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersParallelGeometry Module_vtkFiltersParallelGeometry-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersParallelImaging Module_vtkFiltersParallelImaging-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersParallelMPI Module_vtkFiltersParallelMPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersParallelStatistics Module_vtkFiltersParallelStatistics-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelStatistics Module_vtkFiltersParallelStatistics: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_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 //ADVANCED property for variable: Module_vtkIOMPIParallel Module_vtkIOMPIParallel-ADVANCED:INTERNAL=1 //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 //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_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 //Request building vtkIOVisItBridge Module_vtkIOVisItBridge:INTERNAL=OFF //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 //Request building vtkPVCatalystTestDriver Module_vtkPVCatalystTestDriver:INTERNAL=OFF //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_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_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 //ADVANCED property for variable: Module_vtkParallelMPI4Py Module_vtkParallelMPI4Py-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkParseOGLExt Module_vtkParseOGLExt-ADVANCED:INTERNAL=1 //Request building vtkParseOGLExt Module_vtkParseOGLExt:INTERNAL=OFF //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 //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_vtkRenderingFreeTypeOpenGL Module_vtkRenderingFreeTypeOpenGL-ADVANCED:INTERNAL=1 //Request building vtkRenderingFreeTypeOpenGL Module_vtkRenderingFreeTypeOpenGL:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingFreeTypeOpenGL2 Module_vtkRenderingFreeTypeOpenGL2-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_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_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_vtkRenderingOpenGL Module_vtkRenderingOpenGL-ADVANCED:INTERNAL=1 //Request building vtkRenderingOpenGL Module_vtkRenderingOpenGL:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingOpenGL2 Module_vtkRenderingOpenGL2-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 //ADVANCED property for variable: Module_vtkRenderingQt Module_vtkRenderingQt-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 //ADVANCED property for variable: Module_vtkRenderingVolumeOpenGLNew Module_vtkRenderingVolumeOpenGLNew-ADVANCED:INTERNAL=1 //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 //Request building vtkTestingGenericBridge Module_vtkTestingGenericBridge:INTERNAL=OFF //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_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_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_vtkftgl Module_vtkftgl-ADVANCED:INTERNAL=1 //Request building vtkftgl Module_vtkftgl: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 //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_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_vtkmpi4py Module_vtkmpi4py-ADVANCED:INTERNAL=1 //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= //ADVANCED property for variable: NVCtrlLib_INCLUDE_DIR NVCtrlLib_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NVCtrlLib_LIBRARY NVCtrlLib_LIBRARY-ADVANCED:INTERNAL=1 //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_BUILD_CATALYST_ADAPTORS PARAVIEW_BUILD_CATALYST_ADAPTORS-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_CGNSReader PARAVIEW_BUILD_PLUGIN_CGNSReader-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_EyeDomeLighting PARAVIEW_BUILD_PLUGIN_EyeDomeLighting-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ForceTime PARAVIEW_BUILD_PLUGIN_ForceTime-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_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_MobileRemoteControl PARAVIEW_BUILD_PLUGIN_MobileRemoteControl-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_PythonQtPlugin PARAVIEW_BUILD_PLUGIN_PythonQtPlugin-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_TemporalParallelismScriptGenerator PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator-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_VRPlugin PARAVIEW_BUILD_PLUGIN_VRPlugin-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 //ADVANCED property for variable: PARAVIEW_CLIENT_RENDER_SERVER_TESTS PARAVIEW_CLIENT_RENDER_SERVER_TESTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_COLLABORATION_TESTING PARAVIEW_COLLABORATION_TESTING-ADVANCED:INTERNAL=1 //List of modules to CS wrap PARAVIEW_CURRENT_CS_MODULES:INTERNAL=vtkCommonCore;vtkCommonMath;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkCommonDataModel;vtkCommonExecutionModel;vtkCommonComputationalGeometry;vtkFiltersCore;vtkFiltersGeneral;vtkIOCore;vtkIOLegacy;vtkParallelCore;vtkFiltersAMR;vtkImagingCore;vtkImagingFourier;vtkFiltersStatistics;vtkFiltersExtraction;vtkFiltersSources;vtkFiltersFlowPaths;vtkIOGeometry;vtkIOImage;vtkImagingHybrid;vtkCommonColor;vtkFiltersGeometry;vtkRenderingCore;vtkRenderingOpenGL;vtkRenderingVolume;vtkRenderingVolumeOpenGL;vtkInteractionStyle;vtkFiltersModeling;vtkFiltersParallel;vtkFiltersProgrammable;vtkPythonInterpreter;vtkIOXMLParser;vtkPVCommon;vtkPVVTKExtensionsCore;vtkPVClientServerCoreCore;vtkPVServerImplementationCore;vtkPVServerManagerCore;vtkIOMovie;vtkIOXML;vtkDomainsChemistry;vtkFiltersParallelStatistics;vtkIOEnSight;vtkIOImport;vtkInfovisCore;vtkIOInfovis;vtkIONetCDF;vtkIOParallel;vtkIOExodus;vtkIOParallelExodus;vtkIOParallelXML;vtkImagingSources;vtkFiltersHybrid;vtkImagingGeneral;vtkImagingColor;vtkRenderingFreeType;vtkRenderingAnnotation;vtkInteractionWidgets;vtkRenderingContext2D;vtkChartsCore;vtkFiltersGeneric;vtkFiltersHyperTree;vtkRenderingContextOpenGL;vtkRenderingGL2PS;vtkRenderingLabel;vtkIOExport;vtkRenderingFreeTypeOpenGL;vtkRenderingLIC;vtkRenderingMatplotlib;vtkRenderingParallel;vtkPVVTKExtensionsRendering;vtkPVVTKExtensionsDefault;vtkRenderingVolumeAMR;vtkViewsCore;vtkViewsContext2D;vtkWebGLExporter;vtkPVClientServerCoreRendering;vtkPVClientServerCoreDefault;vtkPVServerImplementationRendering;vtkPVServerManagerRendering;vtkTestingRendering;vtkPVServerManagerDefault;vtkPVAnimation;vtkFiltersPython;vtkFiltersTexture;vtkFiltersVerdict;vtkIOAMR;vtkIOPLY;vtkIOLSDyna;vtkIOParallelLSDyna;vtkIOVPIC;vtkIOVisItBridge;vtkIOXdmf2;vtkImagingMorphological;vtkInteractionImage;vtkRenderingLOD;vtkPVServerManagerApplication;vtkPVCatalyst;vtkPVCatalystTestDriver;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_MATPLOTLIB PARAVIEW_ENABLE_MATPLOTLIB-ADVANCED:INTERNAL=1 //MODIFIED property for variable: PARAVIEW_ENABLE_PYTHON PARAVIEW_ENABLE_PYTHON-MODIFIED: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_PLUGIN_DIRS PARAVIEW_EXTERNAL_PLUGIN_DIRS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_FREEZE_PYTHON PARAVIEW_FREEZE_PYTHON-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_QT_VERSION PARAVIEW_QT_VERSION-ADVANCED:INTERNAL=1 //STRINGS property for variable: PARAVIEW_QT_VERSION PARAVIEW_QT_VERSION-STRINGS:INTERNAL=4;5 //Server Manager XMLs PARAVIEW_SERVERMANAGER_XMLS:INTERNAL=/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/3d_widgets.xml;/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml;/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/internal_writers.xml;/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml;/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/rendering.xml;/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/sources.xml;/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml;/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/views_and_representations.xml;/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/writers.xml;/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/Default/settings.xml;/u/wk/jcbecker/ParaView/ParaViewCore/Animation/animation.xml;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/visit_readers.xml;/u/wk/jcbecker/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/pythonfilter.xml //MODIFIED property for variable: PARAVIEW_USE_VISITBRIDGE PARAVIEW_USE_VISITBRIDGE-MODIFIED:INTERNAL=ON //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_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_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=/usr/lib64/qt4/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=/usr/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=/usr/lib64 //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 //MODIFIED property for variable: QT_QMAKE_EXECUTABLE QT_QMAKE_EXECUTABLE-MODIFIED:INTERNAL=ON //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_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_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 //ADVANCED property for variable: SCPCOMMAND SCPCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SILO_INCLUDE_DIR SILO_INCLUDE_DIR-ADVANCED:INTERNAL=1 //MODIFIED property for variable: SILO_INCLUDE_DIR SILO_INCLUDE_DIR-MODIFIED:INTERNAL=ON //ADVANCED property for variable: SILO_LIBRARY SILO_LIBRARY-ADVANCED:INTERNAL=1 //MODIFIED property for variable: SILO_LIBRARY SILO_LIBRARY-MODIFIED:INTERNAL=ON //ADVANCED property for variable: SITE SITE-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(off64_t) SIZEOF_OFF64_T: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(_Bool) SIZEOF__BOOL:INTERNAL=1 //ADVANCED property for variable: SLURM_SBATCH_COMMAND SLURM_SBATCH_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SLURM_SRUN_COMMAND SLURM_SRUN_COMMAND-ADVANCED: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: SVNCOMMAND SVNCOMMAND-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= VISITBRIDGE_INCLUDE_DIRS:INTERNAL=/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/Library/VisItLib;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/Exceptions/Database;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/Exceptions/Pipeline;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/Exceptions/Plotter;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/comm;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/expr;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/icons;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/misc;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/parser;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/plugin;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/proxybase;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/state;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/utility;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/common/misc;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/common/plugin;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/common/state;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/common/common/utility;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/include;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Database;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Ghost;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/DBAtts/MetaData;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/DBAtts/SIL;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Math;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/VisWindow/VisWindow;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/IVP;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline/AbstractFilters;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline/Data;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline/Pipeline;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline/Sinks;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline/Sources;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/visit_vtk/full;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/Library/VisItLib/visit_vtk/lightweight;/usr/include //MODIFIED property for variable: VISIT_BUILD_READER_GMV VISIT_BUILD_READER_GMV-MODIFIED:INTERNAL=ON //MODIFIED property for variable: VISIT_BUILD_READER_Silo VISIT_BUILD_READER_Silo-MODIFIED:INTERNAL=ON //Result of TRY_COMPILE VISIT_COMPILER_FSTREAM_WORKAROUND:INTERNAL=FALSE //include directories VISIT_DB_INC_DIRS:INTERNAL=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ANSYS;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/AUXFile;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/BOV;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/CEAucd;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Chombo;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/CMAT;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/CTRL;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Curve2D;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/DDCMD;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Dyna3D;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Enzo;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ExtrudedVol;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/FLASH;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Fluent;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Gadget;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GTC;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GULP;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/H5Nimrod;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Image;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/LAMMPS;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/LAMMPS;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Lines;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3D;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIX;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIXCDF;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Miranda;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MM5;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NASTRAN;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Nek5000;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OpenFOAM;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OVERFLOW;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/PATRAN;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/PFLOTRAN;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Pixie;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/PLOT2D;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/PLOT3D;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Point3D;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ProteinDataBank;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/RAW;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAMRAI;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAR;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAS;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Spheral;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tetrad;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/TFT;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/TSurf;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/UNIC;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/VASP;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/VASP;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/VASP;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Velodyne;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/XYZ;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Claw;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo //visit sources for readers VISIT_DB_SOURCES:INTERNAL=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ANSYS/avtANSYSFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/AUXFile/avtAUXFileFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/AUXFile/avtAUXFileFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/BOV/avtBOVFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/CEAucd/avtCEAucdFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/CEAucd/FichierU.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/CEAucd/vtkCEAucdReader.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Chombo/avtChomboFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Chombo/avtChomboFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Chombo/avtChomboOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Chombo/avtChomboOptions.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Chombo/ChomboPluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Chombo/ChomboPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Chombo/ChomboEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Chombo/ChomboMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Chombo/ChomboCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/CMAT/avtCMATFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/CTRL/avtCTRLFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Curve2D/avtCurve2DFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/DDCMD/avtDDCMDFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/DDCMD/object.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/DDCMD/object.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/DDCMD/error.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/DDCMD/error.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Dyna3D/avtDyna3DFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Dyna3D/Dyna3DCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Dyna3D/Dyna3DEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Dyna3D/Dyna3DFile.cpp;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Dyna3D/Dyna3DMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Dyna3D/Dyna3DPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Dyna3D/MaterialProperties.cpp;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Enzo/avtEnzoFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Enzo/avtEnzoFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ExtrudedVol/avtExtrudedVolFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ExtrudedVol/avtExtrudedVolWriter.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ExtrudedVol/avtExtrudedVolOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ExtrudedVol/avtExtrudedVolOptions.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ExtrudedVol/ExtrudedVolPluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ExtrudedVol/ExtrudedVolPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ExtrudedVol/ExtrudedVolEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ExtrudedVol/ExtrudedVolMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ExtrudedVol/ExtrudedVolCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/FLASH/avtFLASHFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/FLASH/avtFLASHFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/FLASH/avtFLASHOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/FLASH/avtFLASHOptions.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/FLASH/FLASHPluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/FLASH/FLASHPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/FLASH/FLASHEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/FLASH/FLASHMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/FLASH/FLASHCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Fluent/avtFluentFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Fluent/avtFluentFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Gadget/avtGadgetFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/avtGGCMFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/avtGGCMOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/GGCMCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/GGCMEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/GGCMMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/GGCMPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/GGCMPluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/ggcm_grid.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/ggcm_grid_gse.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/ggcm_field_matrix.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/ggcm_mhd_gse.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/ggcm_read_mhd.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GGCM/matrix.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GTC/avtGTCFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/GULP/avtGULPFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/H5Nimrod/avtH5NimrodFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/H5Nimrod/H5utils.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Image/vtkStimulateReader.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Image/avtImageFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Image/avtImageOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Image/avtImagePluginWriter.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Image/ImageMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Image/ImagePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Image/ImageCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Image/ImageEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/LAMMPS/avtLAMMPSStructureFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/LAMMPS/avtLAMMPSDumpFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Lines/avtLinesFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3D/avtM3DFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1/avtM3DC1Field.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1/avtM3DC1FileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1/avtM3DC1FileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1/avtM3DC1Options.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1/avtM3DC1Options.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1/M3DC1PluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1/M3DC1PluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1/M3DC1EnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1/M3DC1MDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/M3DC1/M3DC1CommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIX/avtMFIXFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIX/avtMFIXFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIX/avtMFIXOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIX/avtMFIXFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIX/MFIXPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIX/MFIXEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIX/MFIXCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIX/MFIXMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIXCDF/avtMFIXCDFFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIXCDF/avtMFIXCDFFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIXCDF/avtMFIXCDFOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIXCDF/avtMFIXCDFFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIXCDF/MFIXCDFPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIXCDF/MFIXCDFEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIXCDF/MFIXCDFCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MFIXCDF/MFIXCDFMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Miranda/avtMirandaFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Miranda/avtMirandaFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Miranda/avtMirandaOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Miranda/avtMirandaOptions.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Miranda/MirandaPluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Miranda/MirandaPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Miranda/MirandaEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Miranda/MirandaMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Miranda/MirandaCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MM5/avtMM5FileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/MM5/MM5.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NASTRAN/avtNASTRANFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NASTRAN/avtNASTRANFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NASTRAN/avtNASTRANOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NASTRAN/avtNASTRANOptions.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NASTRAN/NASTRANPluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NASTRAN/NASTRANPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NASTRAN/NASTRANEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NASTRAN/NASTRANMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NASTRAN/NASTRANCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtBasicNETCDFFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtADAPTFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtLODIFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtLODIParticleFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtFVCOM_STSDFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtFVCOMParticleFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtFVCOM_MTSDFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtFVCOM_MTMDFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtCCSMFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtBOUTFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtNETCDFReaderBase.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtBasicNETCDFReader.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtCCSMReader.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/avtFVCOMReader.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/NETCDF/NETCDFFileObject.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Nek5000/avtNek5000FileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Nek5000/avtNek5000Options.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Nek5000/Nek5000CommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Nek5000/Nek5000EnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Nek5000/Nek5000MDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Nek5000/Nek5000PluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OpenFOAM/avtOpenFOAMFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OpenFOAM/avtOpenFOAMOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OpenFOAM/OpenFOAMCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OpenFOAM/OpenFOAMEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OpenFOAM/OpenFOAMMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OpenFOAM/OpenFOAMPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OpenFOAM/visit_vtkOpenFOAMReader.cxx;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OpenFOAM/visit_vtkPOpenFOAMReader.cxx;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/OVERFLOW/avtOVERFLOWFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/avtparaDISFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/avtparaDISOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/paraDISCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/paraDISEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/paraDISMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/paraDISPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/Dumpfile.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/parallelParaDIS.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/paraDIS_lib/paradis.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/paraDIS_lib/paradis_c_interface.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_c_lib/args.c;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_c_lib/debugutil.c;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_c_lib/fileutils.c;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_c_lib/inventor.c;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_cpp_lib/RangeList.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_cpp_lib/timer.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_cpp_lib/pathutil.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/avtparaDIS_tecplotFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_c_lib/args.c;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_c_lib/debugutil.c;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_c_lib/signals.c;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_c_lib/fileutils.c;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_c_lib/inventor.c;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_cpp_lib/RangeList.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_cpp_lib/timer.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/paraDIS/RC_cpp_lib/pathutil.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/PATRAN/avtPATRANFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/PFLOTRAN/avtPFLOTRANFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Pixie/avtPixieFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Pixie/avtPixieOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Pixie/PixieCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Pixie/PixieEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Pixie/PixieMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Pixie/PixiePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/PLOT2D/avtPLOT2DFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/PLOT3D/avtPLOT3DFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Point3D/avtPoint3DFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ProteinDataBank/avtProteinDataBankFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ProteinDataBank/avtProteinDataBankFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ProteinDataBank/avtProteinDataBankOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ProteinDataBank/avtProteinDataBankOptions.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ProteinDataBank/ProteinDataBankPluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ProteinDataBank/ProteinDataBankPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ProteinDataBank/ProteinDataBankEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ProteinDataBank/ProteinDataBankMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/ProteinDataBank/ProteinDataBankCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/RAW/avtRAWFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAMRAI/avtSAMRAIFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAMRAI/avtSAMRAIFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAMRAI/AutoArray.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAMRAI/SAMRAIEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAMRAI/SAMRAIPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAMRAI/SAMRAIPluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAMRAI/SAMRAICommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAMRAI/SAMRAIMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAR/avtSARFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/SAS/avtSASFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Spheral/avtSpheralFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/avtTecplotFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/avtTecplotOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/avtTecplotOptions.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/avtTecplotWriter.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/avtTecplotWriter.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/TecplotPluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/TecplotPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/TecplotEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/TecplotMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/TecplotCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/TecplotFile.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/TecplotFile.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/avtTecplotBinaryFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tecplot/TecplotFile.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tetrad/avtTetradFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Tetrad/avtTetradFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/TFT/avtTFTFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/TSurf/avtTSurfFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/UNIC/avtUNICFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/VASP/avtOUTCARFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/VASP/avtPOSCARFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/VASP/avtCHGCARFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Velodyne/avtVelodyneFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Velodyne/VelodyneReader.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/avtVsFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/avtVsOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsFilter.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsH5Attribute.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsH5Dataset.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsH5File.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsH5Group.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsH5Object.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsH5Reader.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsLog.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsMDMesh.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsMDVariable.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsMesh.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsRectilinearMesh.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsRegistry.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsRegistryObject.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsSchema.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsStructuredMesh.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsUniformMesh.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsUnstructuredMesh.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsUtils.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsVariable.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Vs/VsVariableWithMesh.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/avtXmdvFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/avtXmdvFileFormat.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/avtXmdvOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/avtXmdvOptions.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/avtXmdvWriter.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/avtXmdvWriter.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/XmdvPluginInfo.h;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/XmdvPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/XmdvEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/XmdvMDServerPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Xmdv/XmdvCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/XYZ/avtXYZFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Claw/avtClawFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloWriter.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloMBObjectCache.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloOptions.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/SiloPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/SiloCommonPluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/SiloEnginePluginInfo.C;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/SiloMDServerPluginInfo.C //ADVANCED property for variable: VISIT_DISABLE_COMPILER_WARNINGS VISIT_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1 //vtk classes to wrap for client server VISIT_SERVER_SOURCES:INTERNAL=/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/AvtAlgorithms/vtkAvtFileFormatAlgorithm.cxx;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/AvtAlgorithms/vtkAvtMTSDFileFormatAlgorithm.cxx;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/AvtAlgorithms/vtkAvtMTMDFileFormatAlgorithm.cxx;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/AvtAlgorithms/vtkAvtSTSDFileFormatAlgorithm.cxx;/u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/AvtAlgorithms/vtkAvtSTMDFileFormatAlgorithm.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItANSYSReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItANSYSReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItAuxFileReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItAuxFileReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItBOVReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItBOVReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCEAucdReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCEAucdReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItChomboReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItChomboReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCMATReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCMATReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCTRLReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCTRLReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCurve2DReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCurve2DReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItDDCMDReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItDDCMDReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItDyna3DReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItDyna3DReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItEnzoReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItEnzoReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItExtrudedVolReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItExtrudedVolReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFLASHReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFLASHReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFluentReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFluentReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItGadgetReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItGadgetReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItGGCMReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItGGCMReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItGTCReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItGTCReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItGULPReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItGULPReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItH5NimrodReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItH5NimrodReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItImageReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItImageReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItLAMMPSStructureReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItLAMMPSStructureReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItLAMMPSDumpReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItLAMMPSDumpReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItLinesReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItLinesReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItM3DReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItM3DReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItM3DC1Reader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItM3DC1Reader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItMFIXReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItMFIXReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItMFIXCDFReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItMFIXCDFReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItMirandaReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItMirandaReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItMM5Reader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItMM5Reader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItNASTRANReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItNASTRANReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItADAPTReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItADAPTReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItLODIReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItLODIReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItLODIParticleReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItLODIParticleReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFVCOM_STSDReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFVCOM_STSDReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFVCOM_MTMDReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFVCOM_MTMDReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFVCOM_MTSDReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFVCOM_MTSDReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFVCOMParticleReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItFVCOMParticleReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCCSM_MTSD_Reader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCCSM_MTSD_Reader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCCSM_STSD_Reader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCCSM_STSD_Reader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItBOUTReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItBOUTReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItNek5000Reader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItNek5000Reader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItOpenFOAMReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItOpenFOAMReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItOVERFLOWReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItOVERFLOWReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItParaDISReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItParaDISReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItParaDISTecplotReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItParaDISTecplotReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPATRANReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPATRANReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPFLOTRANReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPFLOTRANReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPixieReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPixieReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPLOT2DReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPLOT2DReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPLOT3DReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPLOT3DReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPoint3DReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPoint3DReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItProteinDataBankReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItProteinDataBankReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItRAWReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItRAWReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItSAMRAIReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItSAMRAIReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItSARReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItSARReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItSASReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItSASReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItSpheralReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItSpheralReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItTecplotReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItTecplotReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItTecplotBinaryReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItTecplotBinaryReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItTetradReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItTetradReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItTFTReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItTFTReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItTSurfReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItTSurfReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItUNICReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItUNICReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItOUTCARReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItOUTCARReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPOSCARReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItPOSCARReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCHGCARReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItCHGCARReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItVelodyneReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItVelodyneReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItVsReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItVsReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItXmdvReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItXmdvReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItXYZReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItXYZReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItClawReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItClawReader.h;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItSiloReader.cxx;/u/wk/jcbecker/ParaView-build/Utilities/VisItBridge/databases/vtkVisItSiloReader.h //Result of TRY_COMPILE VSNPRINTF_WORKS:INTERNAL=TRUE //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 //Result of TRY_COMPILE VTK_ANSI_STREAM_EOF_COMPILED:INTERNAL=TRUE //Result of TRY_RUN VTK_ANSI_STREAM_EOF_RESULT:INTERNAL=0 //ADVANCED property for variable: VTK_BUILD_ALL_MODULES VTK_BUILD_ALL_MODULES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_BUILD_ALL_MODULES_FOR_TESTS VTK_BUILD_ALL_MODULES_FOR_TESTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_BUILD_FREETYPE_BENCHMARK VTK_BUILD_FREETYPE_BENCHMARK-ADVANCED:INTERNAL=1 //Directory where python modules will be built VTK_BUILD_PYTHON_MODULE_DIR:INTERNAL=/u/wk/jcbecker/ParaView-build/lib/site-packages //Support for full template specialization syntax VTK_COMPILER_HAS_FULL_SPECIALIZATION: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_ENABLE_KITS VTK_ENABLE_KITS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_ENABLE_VTKPYTHON VTK_ENABLE_VTKPYTHON-ADVANCED:INTERNAL=1 //Support for C++ explict templates VTK_EXPLICIT_TEMPLATES:INTERNAL=1 //ADVANCED property for variable: VTK_EXTRA_COMPILER_WARNINGS VTK_EXTRA_COMPILER_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_GHOSTSCRIPT_EXECUTABLE VTK_GHOSTSCRIPT_EXECUTABLE-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 //Result of TRY_COMPILE VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS:INTERNAL=TRUE //OpenGL includes used to test glXGetProcAddressARB prototype. VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS_INCLUDES:INTERNAL=/usr/include //Already set VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS_TESTED: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-4.3/site-packages //Whether istream supports long long VTK_ISTREAM_SUPPORTS_LONG_LONG: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_MAKE_INSTANTIATORS VTK_MAKE_INSTANTIATORS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MAX_THREADS VTK_MAX_THREADS-ADVANCED:INTERNAL=1 //Disable Python Threads support VTK_NO_PYTHON_THREADS:INTERNAL=1 //ADVANCED property for variable: VTK_OPENGL_HAS_OSMESA VTK_OPENGL_HAS_OSMESA-ADVANCED:INTERNAL=1 //Whether ostream supports long long VTK_OSTREAM_SUPPORTS_LONG_LONG:INTERNAL=1 //ADVANCED property for variable: VTK_QT_VERSION VTK_QT_VERSION-ADVANCED:INTERNAL=1 //STRINGS property for variable: VTK_QT_VERSION VTK_QT_VERSION-STRINGS:INTERNAL=4;5 //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 //CHECK_TYPE_SIZE: sizeof(char) VTK_SIZEOF_CHAR:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) VTK_SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) VTK_SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) VTK_SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(long) VTK_SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long long) VTK_SIZEOF_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) VTK_SIZEOF_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: __int64 unknown VTK_SIZEOF___INT64:INTERNAL= //STRINGS property for variable: VTK_SMP_IMPLEMENTATION_TYPE VTK_SMP_IMPLEMENTATION_TYPE-STRINGS:INTERNAL=Sequential;Simple;Kaapi;TBB //Result of TRY_COMPILE VTK_TEST_SYNC_BUILTINS_COMPILED:INTERNAL=TRUE //Whether char is signed. VTK_TYPE_CHAR_IS_SIGNED:INTERNAL=1 //Result of TRY_COMPILE VTK_TYPE_CHAR_IS_SIGNED_COMPILED:INTERNAL=TRUE //CHECK_TYPE_SIZE: sizeof(uintptr_t) VTK_UINTPTR_T:INTERNAL=8 //ADVANCED property for variable: VTK_USE_64BIT_IDS VTK_USE_64BIT_IDS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_GCC_VISIBILITY VTK_USE_GCC_VISIBILITY-ADVANCED:INTERNAL=1 //Have function glXGetProcAddressARB VTK_USE_GLX_GET_PROC_ADDRESS_ARB:INTERNAL=1 //ADVANCED property for variable: VTK_USE_OFFSCREEN VTK_USE_OFFSCREEN-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_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_HDF5 VTK_USE_SYSTEM_HDF5-ADVANCED:INTERNAL=1 //MODIFIED property for variable: VTK_USE_SYSTEM_HDF5 VTK_USE_SYSTEM_HDF5-MODIFIED:INTERNAL=ON //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_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_VISITLIB VTK_USE_SYSTEM_VISITLIB-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_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 //Result of TEST_BIG_ENDIAN WORDS_BIGENDIAN:INTERNAL=0 //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 //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 ZLIB_LIBRARY-ADVANCED:INTERNAL=1 //Components requested for this build tree. _Boost_COMPONENTS_SEARCHED:INTERNAL= //Last used Boost_INCLUDE_DIR value. _Boost_INCLUDE_DIR_LAST:INTERNAL=/usr/include //Last used Boost_USE_MULTITHREADED value. _Boost_USE_MULTITHREADED_LAST:INTERNAL=TRUE //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 //ADVANCED property for variable: smooth_flash smooth_flash-ADVANCED:INTERNAL=1 From jeffrey.c.becker at nasa.gov Tue Feb 17 11:58:41 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Tue, 17 Feb 2015 08:58:41 -0800 Subject: [Paraview] error building silo reader In-Reply-To: <54E36CAF.5010605@nasa.gov> References: <54DBF178.6070204@nasa.gov> <54E36CAF.5010605@nasa.gov> Message-ID: <54E37341.8060809@nasa.gov> On 02/17/2015 08:30 AM, Jeff Becker wrote: > On 02/16/2015 07:03 AM, Utkarsh Ayachit wrote: >> Which version of Silo did you build? Can you attach your >> CMakeCache.txt please? > > Progress! I figured out that the version of silo I was using (4.10.2) > was causing the error due to an incompatibility with the way ParaView > was calling it. Thus I went to silo 4.9.1. Now I get the following QT > related error. > > [ 88%] Building CXX object > Qt/Core/CMakeFiles/pqCore.dir/pqOutputWindowModel.cxx.o > /u/wk/jcbecker/ParaView/Qt/Core/pqOutputWindowModel.cxx: In member > function ?void pqOutputWindowModel::ShowMessages(bool*)?: > /u/wk/jcbecker/ParaView/Qt/Core/pqOutputWindowModel.cxx:246:14: error: > ?class QList? has no member named ?reserve? > this->Rows.reserve(_rowCount); > ^ > make[2]: *** [Qt/Core/CMakeFiles/pqCore.dir/pqOutputWindowModel.cxx.o] > Error 1 > make[1]: *** [Qt/Core/CMakeFiles/pqCore.dir/all] Error 2 > make: *** [all] Error 2 > > Any ideas here? Thanks. I've attached CMakeCache.txt in case it helps. Looking at my CMakeCache.txt, it looks like setting a correct path for qmake isn't enough for ccmake to find the associated library paths. I'll try again with adding the correct path to LD_LIBRARY_PATH. -jeff > > -jeff >> >> Thanks >> >> On Wed, Feb 11, 2015 at 7:19 PM, Jeff Becker >> wrote: >>> Please help me understand and fix the following build error. Thanks. >>> >>> -jeff >>> >>> [ 26%] Building CXX object >>> Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloWriter.C.o >>> >>> >>> [ 26%] Building CXX object >>> Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o >>> >>> >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?virtual void >>> avtSiloFileFormat::PopulateDatabaseMetaData(avtDatabaseMetaData*)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: >>> >>> error: >>> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >>> >>> was not declared in this scope >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1211: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?void avtSiloFileFormat::ReadCSGmeshes(DBfile*, int, >>> char**, const char*, avtDatabaseMetaData*)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2532: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: >>> >>> error: >>> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >>> >>> was not declared in this scope >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2535: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?void >>> avtSiloFileFormat::FindMultiMeshAdjConnectivity(DBfile*, int&, >>> int*&, int*&, >>> int&, int*&, int&, int*&, bool, bool)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5442: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: >>> >>> error: >>> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >>> >>> was not declared in this scope >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5450: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?void avtSiloFileFormat::AddCSGMultimesh(const >>> char*, >>> const char*, avtDatabaseMetaData*, avtSiloMultiMeshCacheEntry*, >>> DBfile*)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5883: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: >>> >>> error: >>> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >>> >>> was not declared in this scope >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5955: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?vtkDataArray* >>> avtSiloFileFormat::GetAnnotIntNodelistsVar(int, std::string)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6765: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6767: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?vtkDataArray* >>> avtSiloFileFormat::GetMrgTreeNodelistsVar(int, std::string)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6856: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6858: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?void avtSiloFileFormat::ExpandUcdvar(DBucdvar*, >>> const >>> char*, const char*, int)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8563: >>> >>> error: invalid conversion from ?float**? to ?void**? >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8575: >>> >>> error: invalid conversion from ?float**? to ?void**? >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?void >>> avtSiloFileFormat::HandleGlobalZoneIds(const char*, >>> int, void*, int, int)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:9136: >>> >>> error: invalid conversion from ?float**? to ?void**? >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?void >>> avtSiloFileFormat::ReadInConnectivity(vtkUnstructuredGrid*, DBucdmesh*, >>> const char*, int)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:10226: >>> >>> error: invalid conversion from ?float**? to ?void**? >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?void avtSiloFileFormat::ReadInArbConnectivity(const >>> char*, vtkUnstructuredGrid*, DBucdmesh*, int, int)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:11349: >>> >>> error: invalid conversion from ?float**? to ?void**? >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?vtkDataArray* >>> avtSiloFileFormat::GetGlobalNodeIds(int, >>> const char*)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13751: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: >>> >>> error: >>> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >>> >>> was not declared in this scope >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13754: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?vtkDataArray* >>> avtSiloFileFormat::GetGlobalZoneIds(int, >>> const char*)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13842: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: >>> >>> error: >>> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >>> >>> was not declared in this scope >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13845: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?avtMaterial* >>> avtSiloFileFormat::CalcMaterial(DBfile*, >>> const char*, const char*, int)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14218: >>> >>> error: invalid conversion from ?float**? to ?void**? >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >>> >>> In member function ?avtFacelist* >>> avtSiloFileFormat::CalcExternalFacelist(DBfile*, const char*)?: >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14423: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: >>> >>> error: expected primary-expression before ?,? token >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: >>> >>> error: >>> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >>> >>> was not declared in this scope >>> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14426: >>> >>> error: expected primary-expression before ?,? token >>> make[2]: *** >>> [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o] >>> >>> Error 1 >>> make[1]: *** >>> [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all] Error >>> >>> 2 >>> make: *** [all] Error 2 >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Tue Feb 17 12:30:39 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Tue, 17 Feb 2015 17:30:39 +0000 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: <50320452A334BD42A5EC72BAD214509924EFE672@MBX210.d.ethz.ch> References: <6488BE07-FE67-45AD-B02D-FC19426CEE86@llnl.gov> <50320452A334BD42A5EC72BAD214509924EFE672@MBX210.d.ethz.ch> Message-ID: <3CB5EFD1-A9E0-4462-87A9-272195B79536@llnl.gov> Thanks for that information. Could be a life-saver! However, please note that I checked with a local expert and he says, "if you want any optimization on the compute nodes you should use the cross compilers. Likewise, if you use optimization on your frontend compile, you won't be able to run on the compute nodes. They're not fully binary compatible and they do not use the same OS. So your mileage will vary with this approach.? ? Rich On Feb 12, 2015, at 10:55 PM, Biddiscombe, John A. > wrote: Rich On the BGQ, the compute nodes and login nodes are binary compatible, so you shouldn?t need to bother with most of the cross compiling stuff. the only thing to watch out for is the MPI and since vtkParseOGLExt and vtkWrapPython etc don?t touch that, you ought to be ok compiling _as if_ you were going to run on the host node. If you use the MPI wrappers (I don?t), then all will be taken care of. I don?t think that I have compiled pv+catalyst to run on BGQ, so my comment is only based on theory, but I can set a build going in a minute if it helps (except I?d need to setup mesa which may take a while, so maybe I won?t....) JB From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of David E DeMarle Sent: 13 February 2015 01:19 To: Cook, Rich Cc: ParaView list Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich > wrote: /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT Is the name of the executable to run. set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT "PLEASE_FILL_OUT-FAILED_TO_RUN" CACHE STRING "Result from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT 0 CACHE STRING "Result from TRY_RUN" FORCE) if the return code of that executable is 0 set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "PLEASE_FILL_OUT-NOTFOUND" CACHE STRING "Output from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "I am the very model of a modern major general" CACHE STRING "Output from TRY_RUN" FORCE) If the console output of that executable was "I am the very model of a modern major general" David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanglinye at gmail.com Tue Feb 17 12:57:26 2015 From: hanglinye at gmail.com (Hanglin Ye) Date: Tue, 17 Feb 2015 12:57:26 -0500 Subject: [Paraview] Auto Rescale to Data Range in Animation Message-ID: Dear all, I am trying to create an animation of a cube under certain loading condition with paraview. During the animation, I hope that paraview could automatically re-scale the the color map to the data range of each time step. For example, in the 1st time step data range is [0,1], in the second it is [2,3], I am hoping the color map could change accordingly. However I could not find a way to realize that. Could anyone please let me know if there is a way to do that? Thank you very much. -- Hanglin Ye Ph.D.Student MANE, RPI -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Tue Feb 17 13:26:50 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 17 Feb 2015 13:26:50 -0500 Subject: [Paraview] error building silo reader In-Reply-To: <54E37341.8060809@nasa.gov> References: <54DBF178.6070204@nasa.gov> <54E36CAF.5010605@nasa.gov> <54E37341.8060809@nasa.gov> Message-ID: Hi Jeff, You'll need Qt version 4.8.6. https://download.qt.io/archive/qt/4.8/ QList<>::reserve has been introduced in version 4.7 so probably you have something earlier than that. See also http://www.paraview.org/Wiki/ParaView/Binaries for required versions for ParaView libraries. Dan On Tue, Feb 17, 2015 at 11:58 AM, Jeff Becker wrote: > On 02/17/2015 08:30 AM, Jeff Becker wrote: > > On 02/16/2015 07:03 AM, Utkarsh Ayachit wrote: > > Which version of Silo did you build? Can you attach your CMakeCache.txt > please? > > > Progress! I figured out that the version of silo I was using (4.10.2) was > causing the error due to an incompatibility with the way ParaView was > calling it. Thus I went to silo 4.9.1. Now I get the following QT related > error. > > [ 88%] Building CXX object > Qt/Core/CMakeFiles/pqCore.dir/pqOutputWindowModel.cxx.o > /u/wk/jcbecker/ParaView/Qt/Core/pqOutputWindowModel.cxx: In member > function ?void pqOutputWindowModel::ShowMessages(bool*)?: > /u/wk/jcbecker/ParaView/Qt/Core/pqOutputWindowModel.cxx:246:14: error: > ?class QList? has no member named ?reserve? > this->Rows.reserve(_rowCount); > ^ > make[2]: *** [Qt/Core/CMakeFiles/pqCore.dir/pqOutputWindowModel.cxx.o] > Error 1 > make[1]: *** [Qt/Core/CMakeFiles/pqCore.dir/all] Error 2 > make: *** [all] Error 2 > > Any ideas here? Thanks. I've attached CMakeCache.txt in case it helps. > > > Looking at my CMakeCache.txt, it looks like setting a correct path for > qmake isn't enough for ccmake to find the associated library paths. I'll > try again with adding the correct path to LD_LIBRARY_PATH. > > -jeff > > > -jeff > > > Thanks > > On Wed, Feb 11, 2015 at 7:19 PM, Jeff Becker > wrote: > > Please help me understand and fix the following build error. Thanks. > > -jeff > > [ 26%] Building CXX object > Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloWriter.C.o > > > [ 26%] Building CXX object > Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o > > > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?virtual void > avtSiloFileFormat::PopulateDatabaseMetaData(avtDatabaseMetaData*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: > > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1211: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?void avtSiloFileFormat::ReadCSGmeshes(DBfile*, int, > char**, const char*, avtDatabaseMetaData*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2532: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: > > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2535: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?void > avtSiloFileFormat::FindMultiMeshAdjConnectivity(DBfile*, int&, int*&, > int*&, > int&, int*&, int&, int*&, bool, bool)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5442: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: > > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5450: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?void avtSiloFileFormat::AddCSGMultimesh(const char*, > const char*, avtDatabaseMetaData*, avtSiloMultiMeshCacheEntry*, DBfile*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5883: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: > > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5955: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?vtkDataArray* > avtSiloFileFormat::GetAnnotIntNodelistsVar(int, std::string)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6765: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6767: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?vtkDataArray* > avtSiloFileFormat::GetMrgTreeNodelistsVar(int, std::string)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6856: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6858: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?void avtSiloFileFormat::ExpandUcdvar(DBucdvar*, const > char*, const char*, int)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8563: > > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8575: > > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?void avtSiloFileFormat::HandleGlobalZoneIds(const > char*, > int, void*, int, int)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:9136: > > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?void > avtSiloFileFormat::ReadInConnectivity(vtkUnstructuredGrid*, DBucdmesh*, > const char*, int)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:10226: > > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?void avtSiloFileFormat::ReadInArbConnectivity(const > char*, vtkUnstructuredGrid*, DBucdmesh*, int, int)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:11349: > > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?vtkDataArray* avtSiloFileFormat::GetGlobalNodeIds(int, > const char*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13751: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: > > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13754: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?vtkDataArray* avtSiloFileFormat::GetGlobalZoneIds(int, > const char*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13842: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: > > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13845: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?avtMaterial* avtSiloFileFormat::CalcMaterial(DBfile*, > const char*, const char*, int)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14218: > > error: invalid conversion from ?float**? to ?void**? > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: > > In member function ?avtFacelist* > avtSiloFileFormat::CalcExternalFacelist(DBfile*, const char*)?: > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14423: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: > > error: expected primary-expression before ?,? token > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: > > error: > ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? > > was not declared in this scope > /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14426: > > error: expected primary-expression before ?,? token > make[2]: *** > [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o] > > Error 1 > make[1]: *** > [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all] > Error > 2 > make: *** [all] Error 2 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 17 14:07:56 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 17 Feb 2015 19:07:56 +0000 Subject: [Paraview] Auto Rescale to Data Range in Animation Message-ID: My first advice is, don't rescale the color map over time. Such rescaling is extremely misleading, and this misses the whole point of visualization. If you turn on automatic rescaling in the situation you describe, then you'll get some blue and red coloring to some other blue and red coloring with absolutely no indication that the average field value quintupled. You are throwing out the main trend to look at residuals. Instead, set a range that works well over all time. You can click on the "Rescale to Custom Range" button to set the color range to one that works over all time steps (e.g. 0 to 3). You may also want to change the color map to have better dynamic range, and you can do that by clicking the Edit Color Map button. My second advice is, seriously, don't rescale the color map over time. If you open the color map editor, you can find a button that can automatically rescale the color map to cover all time steps. It can take a while for large data, but that does not sound like an issue with the data you describe. My third advice is, OK, fine, if you really, really, really want to do this (and I still don't recommend this), you can go to ParaView settings (Edit -> Setting on Windows and Linux, ParaView -> Preferences on Mac) under the General tab there is a combo box for an option labeled "Color/Opacity Map Range Options." By default, the color range is only adjusted when you Apply a visualization (or explicitly change it, of course). You can change that behavior to also rescale whenever the time step changes. -Ken From: Hanglin Ye > Date: Tuesday, February 17, 2015 at 10:57 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Auto Rescale to Data Range in Animation Dear all, I am trying to create an animation of a cube under certain loading condition with paraview. During the animation, I hope that paraview could automatically re-scale the the color map to the data range of each time step. For example, in the 1st time step data range is [0,1], in the second it is [2,3], I am hoping the color map could change accordingly. However I could not find a way to realize that. Could anyone please let me know if there is a way to do that? Thank you very much. -- Hanglin Ye Ph.D.Student MANE, RPI -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Feb 17 14:26:34 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 17 Feb 2015 14:26:34 -0500 Subject: [Paraview] error building silo reader In-Reply-To: References: <54DBF178.6070204@nasa.gov> <54E36CAF.5010605@nasa.gov> <54E37341.8060809@nasa.gov> Message-ID: Jeff, Also, if you're interested in trying out ParaView 4.3.1 (and not the bleeding edge), you should use the v4.3.1 tag. This change to the OutputWindow was added after the 4.3.1 release. Utkarsh On Tue, Feb 17, 2015 at 1:26 PM, Dan Lipsa wrote: > Hi Jeff, > You'll need Qt version 4.8.6. > > https://download.qt.io/archive/qt/4.8/ > > > QList<>::reserve has been introduced in version 4.7 so probably you have > something earlier than that. > > See also > http://www.paraview.org/Wiki/ParaView/Binaries > for required versions for ParaView libraries. > > Dan > > > On Tue, Feb 17, 2015 at 11:58 AM, Jeff Becker > wrote: >> >> On 02/17/2015 08:30 AM, Jeff Becker wrote: >> >> On 02/16/2015 07:03 AM, Utkarsh Ayachit wrote: >> >> Which version of Silo did you build? Can you attach your CMakeCache.txt >> please? >> >> >> Progress! I figured out that the version of silo I was using (4.10.2) was >> causing the error due to an incompatibility with the way ParaView was >> calling it. Thus I went to silo 4.9.1. Now I get the following QT related >> error. >> >> [ 88%] Building CXX object >> Qt/Core/CMakeFiles/pqCore.dir/pqOutputWindowModel.cxx.o >> /u/wk/jcbecker/ParaView/Qt/Core/pqOutputWindowModel.cxx: In member >> function ?void pqOutputWindowModel::ShowMessages(bool*)?: >> /u/wk/jcbecker/ParaView/Qt/Core/pqOutputWindowModel.cxx:246:14: error: >> ?class QList? has no member named ?reserve? >> this->Rows.reserve(_rowCount); >> ^ >> make[2]: *** [Qt/Core/CMakeFiles/pqCore.dir/pqOutputWindowModel.cxx.o] >> Error 1 >> make[1]: *** [Qt/Core/CMakeFiles/pqCore.dir/all] Error 2 >> make: *** [all] Error 2 >> >> Any ideas here? Thanks. I've attached CMakeCache.txt in case it helps. >> >> >> Looking at my CMakeCache.txt, it looks like setting a correct path for >> qmake isn't enough for ccmake to find the associated library paths. I'll try >> again with adding the correct path to LD_LIBRARY_PATH. >> >> -jeff >> >> >> -jeff >> >> >> Thanks >> >> On Wed, Feb 11, 2015 at 7:19 PM, Jeff Becker >> wrote: >> >> Please help me understand and fix the following build error. Thanks. >> >> -jeff >> >> [ 26%] Building CXX object >> >> Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloWriter.C.o >> >> [ 26%] Building CXX object >> >> Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o >> >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?virtual void >> avtSiloFileFormat::PopulateDatabaseMetaData(avtDatabaseMetaData*)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1195: >> error: >> >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:1211: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void avtSiloFileFormat::ReadCSGmeshes(DBfile*, int, >> char**, const char*, avtDatabaseMetaData*)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2532: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2533: >> error: >> >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:2535: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void >> avtSiloFileFormat::FindMultiMeshAdjConnectivity(DBfile*, int&, int*&, >> int*&, >> int&, int*&, int&, int*&, bool, bool)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5442: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5443: >> error: >> >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5450: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void avtSiloFileFormat::AddCSGMultimesh(const char*, >> const char*, avtDatabaseMetaData*, avtSiloMultiMeshCacheEntry*, DBfile*)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5883: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5884: >> error: >> >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:5955: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?vtkDataArray* >> avtSiloFileFormat::GetAnnotIntNodelistsVar(int, std::string)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6765: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6767: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?vtkDataArray* >> avtSiloFileFormat::GetMrgTreeNodelistsVar(int, std::string)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6856: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:6858: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void avtSiloFileFormat::ExpandUcdvar(DBucdvar*, const >> char*, const char*, int)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8563: >> error: invalid conversion from ?float**? to ?void**? >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:8575: >> error: invalid conversion from ?float**? to ?void**? >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void avtSiloFileFormat::HandleGlobalZoneIds(const >> char*, >> int, void*, int, int)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:9136: >> error: invalid conversion from ?float**? to ?void**? >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void >> avtSiloFileFormat::ReadInConnectivity(vtkUnstructuredGrid*, DBucdmesh*, >> const char*, int)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:10226: >> error: invalid conversion from ?float**? to ?void**? >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?void avtSiloFileFormat::ReadInArbConnectivity(const >> char*, vtkUnstructuredGrid*, DBucdmesh*, int, int)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:11349: >> error: invalid conversion from ?float**? to ?void**? >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?vtkDataArray* avtSiloFileFormat::GetGlobalNodeIds(int, >> const char*)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13751: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13752: >> error: >> >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13754: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?vtkDataArray* avtSiloFileFormat::GetGlobalZoneIds(int, >> const char*)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13842: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13843: >> error: >> >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:13845: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?avtMaterial* avtSiloFileFormat::CalcMaterial(DBfile*, >> const char*, const char*, int)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14218: >> error: invalid conversion from ?float**? to ?void**? >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C: >> In member function ?avtFacelist* >> avtSiloFileFormat::CalcExternalFacelist(DBfile*, const char*)?: >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14423: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: >> error: expected primary-expression before ?,? token >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14424: >> error: >> >> ?DBSetDataReadMask_is_replaced_with_DBSetDataReadMask2_using_unsigned_long_long? >> was not declared in this scope >> >> /u/wk/jcbecker/ParaView/Utilities/VisItBridge/databases/Silo/avtSiloFileFormat.C:14426: >> error: expected primary-expression before ?,? token >> make[2]: *** >> >> [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/Silo/avtSiloFileFormat.C.o] >> Error 1 >> make[1]: *** >> [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all] >> Error >> 2 >> make: *** [all] Error 2 >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 hanglinye at gmail.com Tue Feb 17 14:38:21 2015 From: hanglinye at gmail.com (Hanglin Ye) Date: Tue, 17 Feb 2015 14:38:21 -0500 Subject: [Paraview] Auto Rescale to Data Range in Animation In-Reply-To: References: Message-ID: Thank you very much for the useful advice ! I now know how to turn on the settings and I would keep in mind your opinions and be careful on the visualization. Many thanks to you. Best, Hanglin On Tue, Feb 17, 2015 at 2:07 PM, Moreland, Kenneth wrote: > My first advice is, don't rescale the color map over time. Such > rescaling is extremely misleading, and this misses the whole point of > visualization. If you turn on automatic rescaling in the situation you > describe, then you'll get some blue and red coloring to some other blue and > red coloring with absolutely no indication that the average field value > quintupled. You are throwing out the main trend to look at residuals. > Instead, set a range that works well over all time. You can click on the > "Rescale to Custom Range" button to set the color range to one that works > over all time steps (e.g. 0 to 3). You may also want to change the color > map to have better dynamic range, and you can do that by clicking the Edit > Color Map button. > > My second advice is, seriously, don't rescale the color map over time. > If you open the color map editor, you can find a button that can > automatically rescale the color map to cover all time steps. It can take a > while for large data, but that does not sound like an issue with the data > you describe. > > My third advice is, OK, fine, if you really, really, really want to do > this (and I still don't recommend this), you can go to ParaView settings > (Edit -> Setting on Windows and Linux, ParaView -> Preferences on Mac) > under the General tab there is a combo box for an option labeled > "Color/Opacity Map Range Options." By default, the color range is only > adjusted when you Apply a visualization (or explicitly change it, of > course). You can change that behavior to also rescale whenever the time > step changes. > > -Ken > > From: Hanglin Ye > Date: Tuesday, February 17, 2015 at 10:57 AM > To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Auto Rescale to Data Range in Animation > > Dear all, > > I am trying to create an animation of a cube under certain loading > condition with paraview. During the animation, I hope that paraview could > automatically re-scale the the color map to the data range of each time > step. For example, in the 1st time step data range is [0,1], in the second > it is [2,3], I am hoping the color map could change accordingly. However I > could not find a way to realize that. Could anyone please let me know if > there is a way to do that? > > Thank you very much. > > -- > Hanglin Ye > Ph.D.Student MANE, RPI > -- Hanglin Ye Ph.D.Student MANE, RPI -------------- next part -------------- An HTML attachment was scrubbed... URL: From johnpmooreiv at gmail.com Tue Feb 17 15:14:13 2015 From: johnpmooreiv at gmail.com (John Moore) Date: Tue, 17 Feb 2015 15:14:13 -0500 Subject: [Paraview] =?utf-8?q?Compile_error=3A_unknown_type_name_=E2=80=98?= =?utf-8?b?c2lnam1wX2J1ZuKAmQ==?= Message-ID: I get the following error when compiling on Ubuntu 14.04 /home/john/local/ParaView/4.3.1/ParaView-v4.3.1-source/VTK/ThirdParty/hdf5/vtkhdf5/src/H5detect.c:149:1: error: unknown type name ?sigjmp_buf? static H5JMP_BUF jbuf_g; I've installed HDF5 and its development tools. Any idea how I can fix this? Thank you, John -------------- next part -------------- An HTML attachment was scrubbed... URL: From biddisco at cscs.ch Tue Feb 17 15:20:52 2015 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Tue, 17 Feb 2015 20:20:52 +0000 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: <3CB5EFD1-A9E0-4462-87A9-272195B79536@llnl.gov> Message-ID: Yes indeed. What I really meant was you can just compile with cake and use the wrappers, there?s no need to setup a special toolchain and get all the cross-compilation stuff going because the wrappers do all that for you. On BGQ I am using clang instead of xlc o I?ve got a different setup. JB From: , "cook47 at llnl.gov" > Date: Tuesday 17 February 2015 18:30 To: cscs > Cc: David DeMarle >, "paraview at paraview.org" > Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q Thanks for that information. Could be a life-saver! However, please note that I checked with a local expert and he says, "if you want any optimization on the compute nodes you should use the cross compilers. Likewise, if you use optimization on your frontend compile, you won't be able to run on the compute nodes. They're not fully binary compatible and they do not use the same OS. So your mileage will vary with this approach.? ? Rich On Feb 12, 2015, at 10:55 PM, Biddiscombe, John A. > wrote: Rich On the BGQ, the compute nodes and login nodes are binary compatible, so you shouldn?t need to bother with most of the cross compiling stuff. the only thing to watch out for is the MPI and since vtkParseOGLExt and vtkWrapPython etc don?t touch that, you ought to be ok compiling _as if_ you were going to run on the host node. If you use the MPI wrappers (I don?t), then all will be taken care of. I don?t think that I have compiled pv+catalyst to run on BGQ, so my comment is only based on theory, but I can set a build going in a minute if it helps (except I?d need to setup mesa which may take a while, so maybe I won?t....) JB From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of David E DeMarle Sent: 13 February 2015 01:19 To: Cook, Rich Cc: ParaView list Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich > wrote: /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT Is the name of the executable to run. set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT "PLEASE_FILL_OUT-FAILED_TO_RUN" CACHE STRING "Result from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT 0 CACHE STRING "Result from TRY_RUN" FORCE) if the return code of that executable is 0 set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "PLEASE_FILL_OUT-NOTFOUND" CACHE STRING "Output from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "I am the very model of a modern major general" CACHE STRING "Output from TRY_RUN" FORCE) If the console output of that executable was "I am the very model of a modern major general" David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From biddisco at cscs.ch Tue Feb 17 15:40:26 2015 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Tue, 17 Feb 2015 20:40:26 +0000 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: Message-ID: NB cake = cmake + aggressive autocorrect From: , cscs > Date: Tuesday 17 February 2015 21:20 To: "cook47 at llnl.gov" > Cc: "paraview at paraview.org" > Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q Yes indeed. What I really meant was you can just compile with cake and use the wrappers, there?s no need to setup a special toolchain and get all the cross-compilation stuff going because the wrappers do all that for you. On BGQ I am using clang instead of xlc o I?ve got a different setup. JB From: , "cook47 at llnl.gov" > Date: Tuesday 17 February 2015 18:30 To: cscs > Cc: David DeMarle >, "paraview at paraview.org" > Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q Thanks for that information. Could be a life-saver! However, please note that I checked with a local expert and he says, "if you want any optimization on the compute nodes you should use the cross compilers. Likewise, if you use optimization on your frontend compile, you won't be able to run on the compute nodes. They're not fully binary compatible and they do not use the same OS. So your mileage will vary with this approach.? ? Rich On Feb 12, 2015, at 10:55 PM, Biddiscombe, John A. > wrote: Rich On the BGQ, the compute nodes and login nodes are binary compatible, so you shouldn?t need to bother with most of the cross compiling stuff. the only thing to watch out for is the MPI and since vtkParseOGLExt and vtkWrapPython etc don?t touch that, you ought to be ok compiling _as if_ you were going to run on the host node. If you use the MPI wrappers (I don?t), then all will be taken care of. I don?t think that I have compiled pv+catalyst to run on BGQ, so my comment is only based on theory, but I can set a build going in a minute if it helps (except I?d need to setup mesa which may take a while, so maybe I won?t....) JB From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of David E DeMarle Sent: 13 February 2015 01:19 To: Cook, Rich Cc: ParaView list Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich > wrote: /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT Is the name of the executable to run. set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT "PLEASE_FILL_OUT-FAILED_TO_RUN" CACHE STRING "Result from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT 0 CACHE STRING "Result from TRY_RUN" FORCE) if the return code of that executable is 0 set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "PLEASE_FILL_OUT-NOTFOUND" CACHE STRING "Output from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "I am the very model of a modern major general" CACHE STRING "Output from TRY_RUN" FORCE) If the console output of that executable was "I am the very model of a modern major general" David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Tue Feb 17 15:43:05 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 17 Feb 2015 15:43:05 -0500 Subject: [Paraview] Fwd: Catalyst simple test In-Reply-To: References: <54E3641E.60800@ec-nantes.fr> Message-ID: (just a forward of my previous response to the list) ---------- Forwarded message ---------- From: Dan Lipsa Date: Tue, Feb 17, 2015 at 12:19 PM Subject: Re: [Paraview] Catalyst simple test To: Felipe Bordeu Hi Felipe, Have you seen: http://www.kitware.com/blog/home/post/722? This blog post shows you how to setup a live connection and describe a simple pipeline using python. The pipeline was generated from Tools/Manage Plugins, Catalyst Script Generator Plugin, Load Selected. Then you can build your pipeline and export it using CoProcessing, Export State. We don't have an example with only C++. Setting up the visualization pipeline as well as the connection to catalyst live, while possible, is more involved in C++. Basically, you'll have write in C++ some of the code in simple.py and coprocessing.py. In your specific case, maybe you are missing the calls to coprocessor.DoLiveVisualization(datadescription, "localhost", 22222) or coprocessor.EnableLiveVisualization(True, 1) These are lines from the python coprocessing script that you'll have to rewrite in C++. Dan On Tue, Feb 17, 2015 at 10:54 AM, Felipe Bordeu wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi everybody, > > I 'm trying to connect my simulation code (a dummy simulation code for > the moment) to paraview using Catalyst to do live visualization. Just > make a mesh (2D structured, with 1 field), and send it to paraview > without python. But I something is not working. The code runs, I can > connect to paraview, pause the simulation but unable to sent the data > for the visualization. > > So I'm doing this : for initialization > > create a vtkCPProcessor object and call Initialize(); > create a vtkCPPipeline derived object class and added to the processor ( > Processor->AddPipeline(pipeline.GetPointer()); ) . > (why do I need a Pipeline if I'm going to send my raw data (in vtk > format of course) to paraview?) > in the CoProcess( vtkCPDataDescription* dataDescription) member function > the only relevant lines are : > vtkNew producer; > vtkImageData* grid = > > vtkImageData::SafeDownCast(dataDescription->GetInputDescriptionByName("input")->GetGrid()); > producer->SetOutput(grid,dataDescription->GetTime()); > > create a vtkLiveInsituLink > LiveLink = vtkLiveInsituLink::New(); > LiveLink->SetInsituPort(22222); > LiveLink->SetHostname("localhost"); > LiveLink->SetProcessType(vtkLiveInsituLink::INSITU); > vtkSMProxyManager* proxyManager = vtkSMProxyManager::GetProxyManager(); > vtkSMSessionProxyManager* sessionProxyManager = > proxyManager->GetActiveSessionProxyManager(); > LiveLink->Initialize(sessionProxyManager); > > > then in each time-step I do : > > vtkCPDataDescription* dataDescription = vtkCPDataDescription::New(); > dataDescription->AddInput("input"); > dataDescription-> SetTimeData(time, timeStep); > if(Processor->RequestDataDescription(dataDescription) != 0){ > // Create a uniform grid > vtkImageData* grid = vtkImageData::New(); > .... > ""setextent, create DoubleArray, fill the array, put the array in the > grid"" > ... > dataDescription->GetInputDescriptionByName("input")->SetGrid(grid); > grid->Delete(); > > Processor->CoProcess(dataDescription); > > > (and also the LiveLink code, not sure about this) this is similar to the > coprocessing.py > > while(true){ > LiveLink->InsituUpdate(timeStep, time); > > LiveLink->InsituPostProcess(time, timeStep); > > if (LiveLink->GetSimulationPaused()){ > if (LiveLink->WaitForLiveChange()){ > break; > } > } else { > break; > } > } > > > I'm pretty sure I'm mixing the code for the different examples I found > on the web and in the sources. I didn't find an example with pure c++ > and live viz. > How I can tell to the LiveLink with data I want to sent to paraview??? > > using ParaView 4.3.1 compiled from git source in linux. > > Thanks to all. > > - -- > Felipe Bordeu Weldt > Ing?nieur de Recherche > - ------------------------------------- > T?l. : 33 (0)2 40 37 16 57 > Fax. : 33 (0)2 40 74 74 06 > Felipe.Bordeu at ec-nantes.fr > Institut GeM - UMR CNRS 6183 > ?cole Centrale Nantes > 1 Rue de La No?, 44321 Nantes, FRANCE > - ------------------------------------- > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEcBAEBAgAGBQJU42QZAAoJEE/fMfNgU9/DCR8IAIfD2dR2h2RBx5vfpgii6N5q > ws5vkG9AZf1Jsqdf3fxk25pcB2BJs615I3iEPmlY4SDTUkVmbVzVFvEXX4HXh8+2 > AGX3yNSjfUfAX9RFPsz131FHLt5oG/7cJjmI8343b6JK+cxmznu+elgCpSRV38gp > yjole85C0SxsZlBBGNXVNTaNyum0tjLVpWMi97fqjLtENTxXjp5gZTy0998edKr1 > f6EqeZ9QySt+T/cWFB/gmQZsX3wwuoPg7fxlYjcMNvLIWBC2VSsAuHlBTRKkhwLn > Q52A1DNLcMuJ8pOO24/sHr+FldTpzldccTkweRhhV8RQAybw0WWmUf377omk7FA= > =q2lI > -----END PGP SIGNATURE----- > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 cook47 at llnl.gov Tue Feb 17 15:59:59 2015 From: cook47 at llnl.gov (Cook, Rich) Date: Tue, 17 Feb 2015 20:59:59 +0000 Subject: [Paraview] Error cross-compiling Catalyst on BG/Q In-Reply-To: References: Message-ID: Thanks! It turns out the customer has a few other things to do before he gets to the catalyst part. So I?ll be back in a few weeks/months with more questions! Thanks all ? Rich On Feb 17, 2015, at 12:40 PM, Biddiscombe, John A. > wrote: NB cake = cmake + aggressive autocorrect From: , cscs > Date: Tuesday 17 February 2015 21:20 To: "cook47 at llnl.gov" > Cc: "paraview at paraview.org" > Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q Yes indeed. What I really meant was you can just compile with cake and use the wrappers, there?s no need to setup a special toolchain and get all the cross-compilation stuff going because the wrappers do all that for you. On BGQ I am using clang instead of xlc o I?ve got a different setup. JB From: , "cook47 at llnl.gov" > Date: Tuesday 17 February 2015 18:30 To: cscs > Cc: David DeMarle >, "paraview at paraview.org" > Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q Thanks for that information. Could be a life-saver! However, please note that I checked with a local expert and he says, "if you want any optimization on the compute nodes you should use the cross compilers. Likewise, if you use optimization on your frontend compile, you won't be able to run on the compute nodes. They're not fully binary compatible and they do not use the same OS. So your mileage will vary with this approach.? ? Rich On Feb 12, 2015, at 10:55 PM, Biddiscombe, John A. > wrote: Rich On the BGQ, the compute nodes and login nodes are binary compatible, so you shouldn?t need to bother with most of the cross compiling stuff. the only thing to watch out for is the MPI and since vtkParseOGLExt and vtkWrapPython etc don?t touch that, you ought to be ok compiling _as if_ you were going to run on the host node. If you use the MPI wrappers (I don?t), then all will be taken care of. I don?t think that I have compiled pv+catalyst to run on BGQ, so my comment is only based on theory, but I can set a build going in a minute if it helps (except I?d need to setup mesa which may take a while, so maybe I won?t....) JB From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of David E DeMarle Sent: 13 February 2015 01:19 To: Cook, Rich Cc: ParaView list Subject: Re: [Paraview] Error cross-compiling Catalyst on BG/Q On Thu, Feb 12, 2015 at 7:15 PM, Cook, Rich > wrote: /collab/usr/global/tools/Kitware/Catalyst/bgqos_0/catalyst_backend_crossbuild/CMakeFiles/cmTryCompileExec2363604927-CMAKE_REQUIRE_LARGE_FILE_SUPPORT Is the name of the executable to run. set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT "PLEASE_FILL_OUT-FAILED_TO_RUN" CACHE STRING "Result from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT 0 CACHE STRING "Result from TRY_RUN" FORCE) if the return code of that executable is 0 set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "PLEASE_FILL_OUT-NOTFOUND" CACHE STRING "Output from TRY_RUN" FORCE) Change that to: set( CMAKE_REQUIRE_LARGE_FILE_SUPPORT__TRYRUN_OUTPUT "I am the very model of a modern major general" CACHE STRING "Output from TRY_RUN" FORCE) If the console output of that executable was "I am the very model of a modern major general" David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From arctica1963 at gmail.com Wed Feb 18 04:12:40 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Wed, 18 Feb 2015 09:12:40 +0000 Subject: [Paraview] Creating structured grid from CSV matrix - error Message-ID: Hello, I have tried various options for the model extents to try and get the data loaded and it keeps generating errors for the wrong number of rows. The data comprise X, Y, Z, value - all as .csv format: the table loads fine and looks correct in the view. Using Paraview v4.0.1 64-bit (Windows 7) Xmin/Xmax = -180/180 increment (0.5) dimension = 721 Ymin/Ymax = -90/90 increment (0.5) dimension = 361 Zmin/Zmax = -700/-25 increment (25) dimension = 28 Scalar = delta_Vs >From the above, the matrix should be 721 x 361 x 28 to give the table size of 7287868, however, pluggin the extents as: X: 0 721 Y: 0 361 Z: 0 28 Gives the error: ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Filters\General\vtkTableToStructuredGrid.cxx, line 97 vtkPTableToStructuredGrid (0000000009AA0140): The input table must have exactly 7579556 rows. Currently it has 7287868 rows. ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, line 754 vtkPVCompositeDataPipeline (000000000A213AB0): Algorithm vtkPTableToStructuredGrid(0000000009AA0140) returned failure for request: vtkInformation (000000000A284350) Debug: Off Modified Time: 235800 Reference Count: 1 Registered Events: (none) Request: REQUEST_DATA FROM_OUTPUT_PORT: 0 FORWARD_DIRECTION: 0 ALGORITHM_AFTER_FORWARD: 1 ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Filters\General\vtkTableToStructuredGrid.cxx, line 97 vtkPTableToStructuredGrid (0000000009AA0140): The input table must have exactly 7579556 rows. Currently it has 7287868 rows. ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, line 754 vtkPVCompositeDataPipeline (000000000A213AB0): Algorithm vtkPTableToStructuredGrid(0000000009AA0140) returned failure for request: vtkInformation (0000000009FE1B40) Debug: Off Modified Time: 238292 Reference Count: 1 Registered Events: (none) Request: REQUEST_DATA FROM_OUTPUT_PORT: 0 FORWARD_DIRECTION: 0 ALGORITHM_AFTER_FORWARD: 1 ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Filters\General\vtkTableToStructuredGrid.cxx, line 97 vtkPTableToStructuredGrid (0000000009AA0140): The input table must have exactly 7579556 rows. Currently it has 7287868 rows. ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx, line 754 vtkPVCompositeDataPipeline (000000000A213AB0): Algorithm vtkPTableToStructuredGrid(0000000009AA0140) returned failure for request: vtkInformation (0000000009FE1B40) Debug: Off Modified Time: 238322 Reference Count: 1 Registered Events: (none) Request: REQUEST_DATA FROM_OUTPUT_PORT: 0 FORWARD_DIRECTION: 0 ALGORITHM_AFTER_FORWARD: 1 Warning: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Common\DataModel\vtkDataObject.cxx, line 525 vtkTable (000000000957FA50): Attempted to ShallowCopy from null. I am not sure where the program is getting the matrix size as 7579556 rows when the loaded spreadsheet has 7287868 rows. Any help or pointers as to what I am doing wrong here would be great. Cheers Lester -------------- next part -------------- An HTML attachment was scrubbed... URL: From kkoenig11 at web.de Wed Feb 18 04:34:07 2015 From: kkoenig11 at web.de (=?windows-1252?Q?Karl_K=F6nig?=) Date: Wed, 18 Feb 2015 10:34:07 +0100 Subject: [Paraview] Creating structured grid from CSV matrix - error In-Reply-To: References: Message-ID: <54E45C8F.5010203@web.de> Lester, > From the above, the matrix should be 721 x 361 x 28 to give the table > size of 7287868, however, pluggin the extents as: > X: 0 721 > Y: 0 361 > Z: 0 28 > > Gives the error: > [...] > The input table must have exactly 7579556 rows. Currently it has > 7287868 rows. 7579556 = 722 x 362 x 29 I am sure you already see where this is going. Your extents should instead read: X: 0 720 Y: 0 360 Z: 0 27 Karl Lester Anderson schrieb am 18.02.2015 um 10:12: > Hello, > > I have tried various options for the model extents to try and get the > data loaded and it keeps generating errors for the wrong number of rows. > The data comprise X, Y, Z, value - all as .csv format: the table loads > fine and looks correct in the view. > > Using Paraview v4.0.1 64-bit (Windows 7) > > Xmin/Xmax = -180/180 increment (0.5) dimension = 721 > Ymin/Ymax = -90/90 increment (0.5) dimension = 361 > Zmin/Zmax = -700/-25 increment (25) dimension = 28 > Scalar = delta_Vs > > From the above, the matrix should be 721 x 361 x 28 to give the table > size of 7287868, however, pluggin the extents as: > X: 0 721 > Y: 0 361 > Z: 0 28 > > Gives the error: > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\Filters\General\vtkTableToStructuredGrid.cxx, > line 97 > vtkPTableToStructuredGrid (0000000009AA0140): The input table must have > exactly 7579556 rows. Currently it has 7287868 rows. > [...] > I am not sure where the program is getting the matrix size as 7579556 > rows when the loaded spreadsheet has 7287868 rows. > > Any help or pointers as to what I am doing wrong here would be great. > > Cheers > > Lester From arctica1963 at gmail.com Wed Feb 18 04:43:31 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Wed, 18 Feb 2015 09:43:31 +0000 Subject: [Paraview] Creating structured grid from CSV matrix - error In-Reply-To: <54E45C8F.5010203@web.de> References: <54E45C8F.5010203@web.de> Message-ID: Thanks Karl! That worked - sorry such a silly error :) Cheers Lester On 18 February 2015 at 09:34, Karl K?nig wrote: > Lester, > > > From the above, the matrix should be 721 x 361 x 28 to give the table > > size of 7287868, however, pluggin the extents as: > > X: 0 721 > > Y: 0 361 > > Z: 0 28 > > > > Gives the error: > > [...] > > The input table must have exactly 7579556 rows. Currently it has > > 7287868 rows. > > 7579556 = 722 x 362 x 29 > > I am sure you already see where this is going. > Your extents should instead read: > > X: 0 720 > Y: 0 360 > Z: 0 27 > > Karl > > > > Lester Anderson schrieb am 18.02.2015 um 10:12: > > Hello, > > > > I have tried various options for the model extents to try and get the > > data loaded and it keeps generating errors for the wrong number of rows. > > The data comprise X, Y, Z, value - all as .csv format: the table loads > > fine and looks correct in the view. > > > > Using Paraview v4.0.1 64-bit (Windows 7) > > > > Xmin/Xmax = -180/180 increment (0.5) dimension = 721 > > Ymin/Ymax = -90/90 increment (0.5) dimension = 361 > > Zmin/Zmax = -700/-25 increment (25) dimension = 28 > > Scalar = delta_Vs > > > > From the above, the matrix should be 721 x 361 x 28 to give the table > > size of 7287868, however, pluggin the extents as: > > X: 0 721 > > Y: 0 361 > > Z: 0 28 > > > > Gives the error: > > > > ERROR: In > > > C:\DBD\pvs-x64\paraview\src\paraview\VTK\Filters\General\vtkTableToStructuredGrid.cxx, > > line 97 > > vtkPTableToStructuredGrid (0000000009AA0140): The input table must have > > exactly 7579556 rows. Currently it has 7287868 rows. > > [...] > > I am not sure where the program is getting the matrix size as 7579556 > > rows when the loaded spreadsheet has 7287868 rows. > > > > Any help or pointers as to what I am doing wrong here would be great. > > > > Cheers > > > > Lester > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From felipe.bordeu at ec-nantes.fr Wed Feb 18 09:58:33 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu) Date: Wed, 18 Feb 2015 15:58:33 +0100 Subject: [Paraview] Fwd: Catalyst simple test In-Reply-To: References: <54E3641E.60800@ec-nantes.fr> Message-ID: <54E4A899.3000608@ec-nantes.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Dan, Yes I already saw the post, but is with python. I just want to send my data to paraview. I translated the related code for the live visu from python to c++. But I still missing something. Can some one look at the code (attached). It is a very simple adaptor with a very simple vtkCPVTKPipeline. The thing is I don't understand the way the vtkLiveInsituLink class know about the vtkPBTrivialProducer. Thanks to all. Felipe Le 17/02/2015 21:43, Dan Lipsa a ?crit : > (just a forward of my previous response to the list) > > ---------- Forwarded message ---------- > From: *Dan Lipsa* > > Date: Tue, Feb 17, 2015 at 12:19 PM > Subject: Re: [Paraview] Catalyst simple test > To: Felipe Bordeu > > > > Hi Felipe, > Have you seen: http://www.kitware.com/blog/home/post/722? > > This blog post shows you how to setup a live connection and describe a simple pipeline using python. > The pipeline was generated from Tools/Manage Plugins, Catalyst Script Generator Plugin, Load Selected. Then you can build your pipeline and export it using CoProcessing, Export State. > > We don't have an example with only C++. > Setting up the visualization pipeline as well as the connection to catalyst live, while possible, is more involved in C++. > Basically, you'll have write in C++ some of the code in simple.py and coprocessing.py. > > In your specific case, maybe you are missing the calls to > > coprocessor.DoLiveVisualization(datadescription, "localhost", 22222) > > or > coprocessor.EnableLiveVisualization(True, 1) > > These are lines from the python coprocessing script that you'll have to rewrite in C++. > > Dan > > > On Tue, Feb 17, 2015 at 10:54 AM, Felipe Bordeu > wrote: > > > Hi everybody, > > I 'm trying to connect my simulation code (a dummy simulation code for > the moment) to paraview using Catalyst to do live visualization. Just > make a mesh (2D structured, with 1 field), and send it to paraview > without python. But I something is not working. The code runs, I can > connect to paraview, pause the simulation but unable to sent the data > for the visualization. > > So I'm doing this : for initialization > > create a vtkCPProcessor object and call Initialize(); > create a vtkCPPipeline derived object class and added to the processor ( > Processor->AddPipeline(pipeline.GetPointer()); ) . > (why do I need a Pipeline if I'm going to send my raw data (in vtk > format of course) to paraview?) > in the CoProcess( vtkCPDataDescription* dataDescription) member function > the only relevant lines are : > vtkNew producer; > vtkImageData* grid = > vtkImageData::SafeDownCast(dataDescription->GetInputDescriptionByName("input")->GetGrid()); > producer->SetOutput(grid,dataDescription->GetTime()); > > create a vtkLiveInsituLink > LiveLink = vtkLiveInsituLink::New(); > LiveLink->SetInsituPort(22222); > LiveLink->SetHostname("localhost"); > LiveLink->SetProcessType(vtkLiveInsituLink::INSITU); > vtkSMProxyManager* proxyManager = vtkSMProxyManager::GetProxyManager(); > vtkSMSessionProxyManager* sessionProxyManager = > proxyManager->GetActiveSessionProxyManager(); > LiveLink->Initialize(sessionProxyManager); > > > then in each time-step I do : > > vtkCPDataDescription* dataDescription = vtkCPDataDescription::New(); > dataDescription->AddInput("input"); > dataDescription-> SetTimeData(time, timeStep); > if(Processor->RequestDataDescription(dataDescription) != 0){ > // Create a uniform grid > vtkImageData* grid = vtkImageData::New(); > .... > ""setextent, create DoubleArray, fill the array, put the array in the > grid"" > ... > dataDescription->GetInputDescriptionByName("input")->SetGrid(grid); > grid->Delete(); > > Processor->CoProcess(dataDescription); > > > (and also the LiveLink code, not sure about this) this is similar to the > coprocessing.py > > while(true){ > LiveLink->InsituUpdate(timeStep, time); > > LiveLink->InsituPostProcess(time, timeStep); > > if (LiveLink->GetSimulationPaused()){ > if (LiveLink->WaitForLiveChange()){ > break; > } > } else { > break; > } > } > > > I'm pretty sure I'm mixing the code for the different examples I found > on the web and in the sources. I didn't find an example with pure c++ > and live viz. > How I can tell to the LiveLink with data I want to sent to paraview??? > > using ParaView 4.3.1 compiled from git source in linux. > > Thanks to all. > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU5KiTAAoJEE/fMfNgU9/DHCoIAMGdM5drdHFmUIFIHf3T5U1D Pcvfa863Kv2FKAXABVULlICivJKBsDM2gfUOVeUWt5c/UQi+TePoQGWVkB7uch2x oZKSdz/sYaAsxmnebXJ9R5StBTl+IMIlPKEQclVIbrxj5+5bm2+YE+6lS4mU8aTJ xqzQl3ZVQtZnBwK7snoMGElDieuEljzIKT5Ygel8nnSwi28lnvxLbi86i4IBjFxR xW6XUABeMEz9xtJ+gtuwo2XIsqoMS7zfus/rlMlKyYnClEhD6RXLd8naCdBQ8NLD nECcrNp0nQBnnEG2+Y3sLtqT86nDJUgS471CQpKrONrRZtP8H8T8HP/IFtAPCsY= =a2l5 -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: C++LiveVisuTest.tar.gz Type: application/gzip Size: 2648 bytes Desc: not available URL: From dan.lipsa at kitware.com Wed Feb 18 10:18:07 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Wed, 18 Feb 2015 10:18:07 -0500 Subject: [Paraview] Fwd: Catalyst simple test In-Reply-To: <54E4A899.3000608@ec-nantes.fr> References: <54E3641E.60800@ec-nantes.fr> <54E4A899.3000608@ec-nantes.fr> Message-ID: Hi Felipe, I'll try to take a look at it today. Dan On Wed, Feb 18, 2015 at 9:58 AM, Felipe Bordeu wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Dan, > > Yes I already saw the post, but is with python. I just want to send my > data to paraview. > > I translated the related code for the live visu from python to c++. But I > still missing something. > > Can some one look at the code (attached). It is a very simple adaptor with > a very simple vtkCPVTKPipeline. > > The thing is I don't understand the way the vtkLiveInsituLink class know > about the vtkPBTrivialProducer. > > Thanks to all. > > Felipe > > > Le 17/02/2015 21:43, Dan Lipsa a ?crit : > > (just a forward of my previous response to the list) > > > > ---------- Forwarded message ---------- > > From: *Dan Lipsa* > > > > Date: Tue, Feb 17, 2015 at 12:19 PM > > Subject: Re: [Paraview] Catalyst simple test > > To: Felipe Bordeu > > > > > > > Hi Felipe, > > Have you seen: http://www.kitware.com/blog/home/post/722? > > > > This blog post shows you how to setup a live connection and describe a > simple pipeline using python. > > The pipeline was generated from Tools/Manage Plugins, Catalyst Script > Generator Plugin, Load Selected. Then you can build your pipeline and > export it using CoProcessing, Export State. > > > > We don't have an example with only C++. > > Setting up the visualization pipeline as well as the connection to > catalyst live, while possible, is more involved in C++. > > Basically, you'll have write in C++ some of the code in simple.py and > coprocessing.py. > > > > In your specific case, maybe you are missing the calls to > > > > coprocessor.DoLiveVisualization(datadescription, "localhost", 22222) > > > > or > > coprocessor.EnableLiveVisualization(True, 1) > > > > These are lines from the python coprocessing script that you'll have to > rewrite in C++. > > > > Dan > > > > > > On Tue, Feb 17, 2015 at 10:54 AM, Felipe Bordeu < > felipe.bordeu at ec-nantes.fr > > wrote: > > > > > > Hi everybody, > > > > I 'm trying to connect my simulation code (a dummy simulation code for > > the moment) to paraview using Catalyst to do live visualization. Just > > make a mesh (2D structured, with 1 field), and send it to paraview > > without python. But I something is not working. The code runs, I can > > connect to paraview, pause the simulation but unable to sent the data > > for the visualization. > > > > So I'm doing this : for initialization > > > > create a vtkCPProcessor object and call Initialize(); > > create a vtkCPPipeline derived object class and added to the processor ( > > Processor->AddPipeline(pipeline.GetPointer()); ) . > > (why do I need a Pipeline if I'm going to send my raw data (in vtk > > format of course) to paraview?) > > in the CoProcess( vtkCPDataDescription* dataDescription) member function > > the only relevant lines are : > > vtkNew producer; > > vtkImageData* grid = > > > vtkImageData::SafeDownCast(dataDescription->GetInputDescriptionByName("input")->GetGrid()); > > producer->SetOutput(grid,dataDescription->GetTime()); > > > > create a vtkLiveInsituLink > > LiveLink = vtkLiveInsituLink::New(); > > LiveLink->SetInsituPort(22222); > > LiveLink->SetHostname("localhost"); > > LiveLink->SetProcessType(vtkLiveInsituLink::INSITU); > > vtkSMProxyManager* proxyManager = > vtkSMProxyManager::GetProxyManager(); > > vtkSMSessionProxyManager* sessionProxyManager = > > proxyManager->GetActiveSessionProxyManager(); > > LiveLink->Initialize(sessionProxyManager); > > > > > > then in each time-step I do : > > > > vtkCPDataDescription* dataDescription = vtkCPDataDescription::New(); > > dataDescription->AddInput("input"); > > dataDescription-> SetTimeData(time, timeStep); > > if(Processor->RequestDataDescription(dataDescription) != 0){ > > // Create a uniform grid > > vtkImageData* grid = vtkImageData::New(); > > .... > > ""setextent, create DoubleArray, fill the array, put the array in the > > grid"" > > ... > > dataDescription->GetInputDescriptionByName("input")->SetGrid(grid); > > grid->Delete(); > > > > Processor->CoProcess(dataDescription); > > > > > > (and also the LiveLink code, not sure about this) this is similar to the > > coprocessing.py > > > > while(true){ > > LiveLink->InsituUpdate(timeStep, time); > > > > LiveLink->InsituPostProcess(time, timeStep); > > > > if (LiveLink->GetSimulationPaused()){ > > if (LiveLink->WaitForLiveChange()){ > > break; > > } > > } else { > > break; > > } > > } > > > > > > I'm pretty sure I'm mixing the code for the different examples I found > > on the web and in the sources. I didn't find an example with pure c++ > > and live viz. > > How I can tell to the LiveLink with data I want to sent to paraview??? > > > > using ParaView 4.3.1 compiled from git source in linux. > > > > Thanks to all. > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > - -- > Felipe Bordeu Weldt > Ing?nieur de Recherche > - ------------------------------------- > T?l. : 33 (0)2 40 37 16 57 > Fax. : 33 (0)2 40 74 74 06 > Felipe.Bordeu at ec-nantes.fr > Institut GeM - UMR CNRS 6183 > ?cole Centrale Nantes > 1 Rue de La No?, 44321 Nantes, FRANCE > - ------------------------------------- > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEcBAEBAgAGBQJU5KiTAAoJEE/fMfNgU9/DHCoIAMGdM5drdHFmUIFIHf3T5U1D > Pcvfa863Kv2FKAXABVULlICivJKBsDM2gfUOVeUWt5c/UQi+TePoQGWVkB7uch2x > oZKSdz/sYaAsxmnebXJ9R5StBTl+IMIlPKEQclVIbrxj5+5bm2+YE+6lS4mU8aTJ > xqzQl3ZVQtZnBwK7snoMGElDieuEljzIKT5Ygel8nnSwi28lnvxLbi86i4IBjFxR > xW6XUABeMEz9xtJ+gtuwo2XIsqoMS7zfus/rlMlKyYnClEhD6RXLd8naCdBQ8NLD > nECcrNp0nQBnnEG2+Y3sLtqT86nDJUgS471CQpKrONrRZtP8H8T8HP/IFtAPCsY= > =a2l5 > -----END PGP SIGNATURE----- > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 Wed Feb 18 10:40:14 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Wed, 18 Feb 2015 15:40:14 +0000 Subject: [Paraview] [Paraview-developers] min and max range mapping data in color map editor Message-ID: This question is probably more appropriate for the ParaView mailing list rather than the developer's list, so I'm replying to it there. I don't think there is enough information here to answer your question. Any chance you could post an example data set? -Ken On 2/18/15, 7:56 AM, "Laura Masse" wrote: >Hello everybody, > >I have a question about the limits in data range. I don?t understand how >paraview decide these limits, it seems there no any correspondence with >the >data value. > >For example, in my case, data is a cloud points in a ply file, my real x, >y >,z range are : > >X -1.3 to 14.6 >Y -1.28 to 2.19 >Z -60 to -50.1 > >Data range calculate by paraview is 159.49 to 382.243, I don?t understand >why . > >I'm looking and looking the data but I don?t get the solution. > >Anyone can help me ? > >Advanced thanks ! > >Laura > > > >-- >View this message in context: >http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/min-an >d-max-range-mapping-data-in-color-map-editor-tp3636.html >Sent from the The Unofficial ParaView Developers Forum mailing list >archive at Nabble.com. >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at >http://www.kitware.com/opensource/opensource.html > >Search the list archives at: >http://markmail.org/search/?q=Paraview-developers > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview-developers From ben.boeckel at kitware.com Wed Feb 18 11:02:13 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 18 Feb 2015 11:02:13 -0500 Subject: [Paraview] =?utf-8?q?Compile_error=3A_unknown_type_name_=E2=80=98?= =?utf-8?b?c2lnam1wX2J1ZuKAmQ==?= In-Reply-To: References: Message-ID: <20150218160213.GA20180@megas.kitwarein.com> On Tue, Feb 17, 2015 at 15:14:13 -0500, John Moore wrote: > I get the following error when compiling on Ubuntu 14.04 > > /home/john/local/ParaView/4.3.1/ParaView-v4.3.1-source/VTK/ThirdParty/hdf5/vtkhdf5/src/H5detect.c:149:1: > error: unknown type name ?sigjmp_buf? > static H5JMP_BUF jbuf_g; > > I've installed HDF5 and its development tools. Any idea how I can fix this? You can pass -DVTK_USE_SYSTEM_HDF5=ON to use your installed HDF5, but it looks like HDF5's configure checks are failing thinking it doesn't have setjmp.h (H5_HAVE_SETJMP_H) while it does manage to find sigjmp_buf (H5JMP_BUF). Are those H5* variables set in your CMakeCache.txt at all? Thanks, --Ben From johnpmooreiv at gmail.com Wed Feb 18 12:52:30 2015 From: johnpmooreiv at gmail.com (John Moore) Date: Wed, 18 Feb 2015 12:52:30 -0500 Subject: [Paraview] =?utf-8?q?Compile_error=3A_unknown_type_name_=E2=80=98?= =?utf-8?b?c2lnam1wX2J1ZuKAmQ==?= In-Reply-To: <20150218160213.GA20180@megas.kitwarein.com> References: <20150218160213.GA20180@megas.kitwarein.com> Message-ID: Thanks for the help, Ben. H5JMP_BUF is not found in CMakeCache.txt, but H5_HAVE_SETJMP_H is, as shown below: //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 I've tried to compile both with and without having HDF5 installed on my system, and both methods fail. I haven't tried -DVTK_USE_SYSTEM_HDF5=ON yet because I would like to be able to use the H5 included with VTK, if possible. Thanks, John On Wed, Feb 18, 2015 at 11:02 AM, Ben Boeckel wrote: > On Tue, Feb 17, 2015 at 15:14:13 -0500, John Moore wrote: > > I get the following error when compiling on Ubuntu 14.04 > > > > > /home/john/local/ParaView/4.3.1/ParaView-v4.3.1-source/VTK/ThirdParty/hdf5/vtkhdf5/src/H5detect.c:149:1: > > error: unknown type name ?sigjmp_buf? > > static H5JMP_BUF jbuf_g; > > > > I've installed HDF5 and its development tools. Any idea how I can fix > this? > > You can pass -DVTK_USE_SYSTEM_HDF5=ON to use your installed HDF5, but it > looks like HDF5's configure checks are failing thinking it doesn't have > setjmp.h (H5_HAVE_SETJMP_H) while it does manage to find sigjmp_buf > (H5JMP_BUF). Are those H5* variables set in your CMakeCache.txt at all? > > Thanks, > > --Ben > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Wed Feb 18 14:48:52 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 18 Feb 2015 14:48:52 -0500 Subject: [Paraview] =?utf-8?q?Compile_error=3A_unknown_type_name_=E2=80=98?= =?utf-8?b?c2lnam1wX2J1ZuKAmQ==?= In-Reply-To: References: <20150218160213.GA20180@megas.kitwarein.com> Message-ID: <20150218194852.GA15902@megas.kitwarein.com> On Wed, Feb 18, 2015 at 12:52:30 -0500, John Moore wrote: > H5JMP_BUF is not found in CMakeCache.txt, but H5_HAVE_SETJMP_H is, as shown > below: Ah, I see that H5JMP_BUF is defined at the top of the file, not by CMake and is controlled by H5_HAVE_SIGSETJMP (empty on my Fedora install) or H5_HAVE_SIGLONGJMP ('1' here) from the CMake cache file. > //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 > > I've tried to compile both with and without having HDF5 installed on my > system, and both methods fail. I haven't tried -DVTK_USE_SYSTEM_HDF5=ON yet > because I would like to be able to use the H5 included with VTK, if > possible. It is odd that it finds the header, but then (seems) to not include it. Could you insert an #error or something in H5private.h in the same block as #include to see if it is actually included? --Ben From burlen.loring at gmail.com Wed Feb 18 15:34:11 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Wed, 18 Feb 2015 12:34:11 -0800 Subject: [Paraview] [Paraview-developers] min and max range mapping data in color map editor In-Reply-To: References: Message-ID: <54E4F743.5010306@gmail.com> also, usually ParaView colors by a scalar value and from your question it seems you are looking at position arrays (x,y,z). Do you have any scalar arrays defined? As Ken said, would help to know more about your data. On 02/18/2015 07:40 AM, Moreland, Kenneth wrote: > This question is probably more appropriate for the ParaView mailing list > rather than the developer's list, so I'm replying to it there. > > I don't think there is enough information here to answer your question. > Any chance you could post an example data set? > > -Ken > > > > On 2/18/15, 7:56 AM, "Laura Masse" wrote: > >> Hello everybody, >> >> I have a question about the limits in data range. I don?t understand how >> paraview decide these limits, it seems there no any correspondence with >> the >> data value. >> >> For example, in my case, data is a cloud points in a ply file, my real x, >> y >> ,z range are : >> >> X -1.3 to 14.6 >> Y -1.28 to 2.19 >> Z -60 to -50.1 >> >> Data range calculate by paraview is 159.49 to 382.243, I don?t understand >> why . >> >> I'm looking and looking the data but I don?t get the solution. >> >> Anyone can help me ? >> >> Advanced thanks ! >> >> Laura >> >> >> >> -- >> View this message in context: >> http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/min-an >> d-max-range-mapping-data-in-color-map-editor-tp3636.html >> Sent from the The Unofficial ParaView Developers Forum mailing list >> archive at Nabble.com. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 johnpmooreiv at gmail.com Wed Feb 18 18:41:20 2015 From: johnpmooreiv at gmail.com (John Moore) Date: Wed, 18 Feb 2015 18:41:20 -0500 Subject: [Paraview] Help with LoadingState and python scripting Message-ID: So, this is what I would like to do, but am new to ParaView and can't figure out how to proceed. Any pointers would be greatly appreciated. I have unsteady data that that represents high-order finite elements. In order to visualize the high order elements, I subdivide them Nref times, and write the data in .pvtu format. In order to save disk space, I only write the high order data at each time step. For Nref refinements, if the elements are tets, this equates to a savings of 8^Nref in disk space. In order to visualize the data, I would first like to load a representative timestep (after re-naming the file to temp.pvtu), do all the manipulation in the GUI, and then save the state in a .pvsm file once satisfied. I would then like to loop over all the time steps, first creating the refined mesh and then post-processing said file for each timestep, and finally deleting the refined mesh files. The post processing at each timestep should use the same state as saved with the gui. I would like to script this all in python, and do the mesh refinement and post-processing on a remote server. I've managed to implement most of this, but the view does not seem to update after every call to pv.servermanager.LoadState(). Below is a pseudo-code: import paraview.simple; pv = paraview.simple; pv.Connect('Server'); for timestep in range(timestep_start,timestep_end+1): pv.servermanager.LoadState('dgsolution.pvsm'); -------------- next part -------------- An HTML attachment was scrubbed... URL: From johnpmooreiv at gmail.com Wed Feb 18 18:56:02 2015 From: johnpmooreiv at gmail.com (John Moore) Date: Wed, 18 Feb 2015 18:56:02 -0500 Subject: [Paraview] Help with LoadingState and python scripting In-Reply-To: References: Message-ID: Sorry about the pre-mature end to the last message. Apparently in gmail Tab takes you directly to the send button. Here's the pseudo-code: import paraview.simple; pv = paraview.simple; pv.Connect('Server'); for timestep in range(timestep_start,timestep_end): % Do the refinement on the server % Copy the parallel mesh file "dgsolution.pvtu" to "temp.pvtu", the same name what was read in by the GUI and then saved in the .pvsm file. pv.servermanager.LoadState('dgsolution.pvsm'); pv.SetActiveView(pv.GetRenderedView()); pv.Render(); pv.SaveScreenshot('screenshot_timestep%06d' % timestep); pv.Disconnect(); When I run the script, I get the solution at the first time step written out for each time step. So it seems that LoadState() is not re-loading the state, even though it's remote source files have changed. Another idea is that perhaps there is new view created for each time step, and I am only saving the first. I'm confident I'm doing something fundamentally wrong here, I just don't know what. Also, I want to be sure that the old data is deleted at each time step, otherwise the memory requirement would be huge. Any suggestions would be greatly appreciated. Thank you for your time! John On Wed, Feb 18, 2015 at 6:41 PM, John Moore wrote: > So, this is what I would like to do, but am new to ParaView and can't > figure out how to proceed. Any pointers would be greatly appreciated. > > I have unsteady data that that represents high-order finite elements. In > order to visualize the high order elements, I subdivide them Nref times, > and write the data in .pvtu format. In order to save disk space, I only > write the high order data at each time step. For Nref refinements, if the > elements are tets, this equates to a savings of 8^Nref in disk space. > > In order to visualize the data, I would first like to load a > representative timestep (after re-naming the file to temp.pvtu), do all the > manipulation in the GUI, and then save the state in a .pvsm file once > satisfied. > > I would then like to loop over all the time steps, first creating the > refined mesh and then post-processing said file for each timestep, and > finally deleting the refined mesh files. The post processing at each > timestep should use the same state as saved with the gui. > > I would like to script this all in python, and do the mesh refinement and > post-processing on a remote server. > > I've managed to implement most of this, but the view does not seem to > update after every call to pv.servermanager.LoadState(). > > Below is a pseudo-code: > > import paraview.simple; > pv = paraview.simple; > pv.Connect('Server'); > > for timestep in range(timestep_start,timestep_end+1): > pv.servermanager.LoadState('dgsolution.pvsm'); > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From johnpmooreiv at gmail.com Wed Feb 18 23:09:09 2015 From: johnpmooreiv at gmail.com (John Moore) Date: Wed, 18 Feb 2015 23:09:09 -0500 Subject: [Paraview] Help with LoadingState and python scripting In-Reply-To: References: Message-ID: I think I have it working. It turns out that I only needed to add : Delete(GetRenderView()) after generating the screenshots. But now, I have another question: is it possible to generate the screenshots on the remote server instead of the client? It would be nice if the screenshots didn't pop up on my local machine whenever the python script (run on my local machine) needs to take s screenshot. Thanks, John On Wed, Feb 18, 2015 at 6:56 PM, John Moore wrote: > Sorry about the pre-mature end to the last message. Apparently in gmail > Tab takes you directly to the send button. Here's the pseudo-code: > > > import paraview.simple; > pv = paraview.simple; > pv.Connect('Server'); > > for timestep in range(timestep_start,timestep_end): > > % Do the refinement on the server > % Copy the parallel mesh file "dgsolution.pvtu" to "temp.pvtu", the > same name what was read in by the GUI and then saved in the .pvsm file. > > pv.servermanager.LoadState('dgsolution.pvsm'); > pv.SetActiveView(pv.GetRenderedView()); > pv.Render(); > pv.SaveScreenshot('screenshot_timestep%06d' % timestep); > > pv.Disconnect(); > > When I run the script, I get the solution at the first time step > written out for each time step. So it seems that LoadState() is not > re-loading the state, even though it's remote source files have changed. > Another idea is that perhaps there is new view created for each time step, > and I am only saving the first. > > > I'm confident I'm doing something fundamentally wrong here, I just > don't know what. Also, I want to be sure that the old data is deleted at > each time step, otherwise the memory requirement would be huge. > > Any suggestions would be greatly appreciated. > > Thank you for your time! > > John > > > > > On Wed, Feb 18, 2015 at 6:41 PM, John Moore > wrote: > >> So, this is what I would like to do, but am new to ParaView and can't >> figure out how to proceed. Any pointers would be greatly appreciated. >> >> I have unsteady data that that represents high-order finite elements. In >> order to visualize the high order elements, I subdivide them Nref times, >> and write the data in .pvtu format. In order to save disk space, I only >> write the high order data at each time step. For Nref refinements, if the >> elements are tets, this equates to a savings of 8^Nref in disk space. >> >> In order to visualize the data, I would first like to load a >> representative timestep (after re-naming the file to temp.pvtu), do all the >> manipulation in the GUI, and then save the state in a .pvsm file once >> satisfied. >> >> I would then like to loop over all the time steps, first creating the >> refined mesh and then post-processing said file for each timestep, and >> finally deleting the refined mesh files. The post processing at each >> timestep should use the same state as saved with the gui. >> >> I would like to script this all in python, and do the mesh refinement and >> post-processing on a remote server. >> >> I've managed to implement most of this, but the view does not seem to >> update after every call to pv.servermanager.LoadState(). >> >> Below is a pseudo-code: >> >> import paraview.simple; >> pv = paraview.simple; >> pv.Connect('Server'); >> >> for timestep in range(timestep_start,timestep_end+1): >> pv.servermanager.LoadState('dgsolution.pvsm'); >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arctica1963 at gmail.com Thu Feb 19 04:14:26 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Thu, 19 Feb 2015 09:14:26 +0000 Subject: [Paraview] Precise clipping/slicing Message-ID: Hello, I have got a global dataset matrix and projected this into spherical coordinates so I could overlay a coastline file for interpretation. I can tweak the clipping by manual dragging but I was wondering what the best way is to do precise clips/slices e.g. a clip at 125 degrees east or an oblique slice that goes through know coordinates? I can see that the method is to work out the plane position (origin, normal), but not entirely clear on what the values represent. I have a clip plane defined as below: Origin: 372.352441878137 280.135672573806 -125.520109507155 Normal: 0.771596619611773 0.580503076333685 -0.260105430490818 The origin I assume refers to the plane intself in the spherical coordinates; are the normals in radians? This would plot through NW Australia and northwards through Timor on my data, but it would be useful to generate a series of slices that were say 120, 125, 130 degrees etc with the clip plane oriented perfectly normal to the sphere (if that sounds right). Hopefully this is not a difficult one; still learning! Cheers Lester -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.otte at gmail.com Thu Feb 19 06:16:48 2015 From: stefan.otte at gmail.com (Stefan Otte) Date: Thu, 19 Feb 2015 12:16:48 +0100 Subject: [Paraview] PCL plugin status and and support of newer PCL versions Message-ID: Hey, I just stumbled upon the PCL plugin [1,2] for ParaView and it looks amazing! I normally develop my perception modules for robots directly with PCL and ParaView & PCL plugin seem to be a promising way to speed up my process. However, I was wondering if there is any active development of the PCL plugin or any plans for such. According to [2] only PCL 1.5.1 and ParaView 3.14.1 are supported and I would prefer/need a newer PCL version. Cheers, Stefan [2] http://www.paraview.org/Wiki/ParaView/PCL_Plugin/Download_And_Build_Instructions [1] https://vimeo.com/43975225 From nenasantos at hotmail.com Thu Feb 19 07:44:05 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Thu, 19 Feb 2015 12:44:05 +0000 Subject: [Paraview] Interpolate nc file In-Reply-To: References: Message-ID: Dear all,I read a nc file to perform a 3D image generating a script. My results are ploted over coarse mesh and i want to interpolate the nc file data (cohesive sediments). How I add these feature in my script? Kind regardsMadalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From casey.goodlett at kitware.com Thu Feb 19 08:45:18 2015 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Thu, 19 Feb 2015 08:45:18 -0500 Subject: [Paraview] PCL plugin status and and support of newer PCL versions In-Reply-To: References: Message-ID: Hi Stefan, Thanks for your interest. I have used the plugin with newer versions of PCL and ParaView, although there are a few fixes needed. Its been on my TODO list for a while to get these made publicly available. I'll get back to you with where you can find those latest changes. On Thu, Feb 19, 2015 at 6:16 AM, Stefan Otte wrote: > Hey, > > I just stumbled upon the PCL plugin [1,2] for ParaView and it looks > amazing! I normally develop my perception modules for robots directly > with PCL and ParaView & PCL plugin seem to be a promising way to speed > up my process. However, I was wondering if there is any active > development of the PCL plugin or any plans for such. According to [2] > only PCL 1.5.1 and ParaView 3.14.1 are supported and I would > prefer/need a newer PCL version. > > > Cheers, > Stefan > > > [2] > http://www.paraview.org/Wiki/ParaView/PCL_Plugin/Download_And_Build_Instructions > [1] https://vimeo.com/43975225 > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Casey B Goodlett, PhD Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.otte at gmail.com Thu Feb 19 09:25:43 2015 From: stefan.otte at gmail.com (Stefan Otte) Date: Thu, 19 Feb 2015 15:25:43 +0100 Subject: [Paraview] PCL plugin status and and support of newer PCL versions In-Reply-To: References: Message-ID: Hey Casey, thanks for the quick reply. Looking forward for the changes! Are there any plans to incorporate the PCL plugin into ParaView by default? Cheers, Stefan From casey.goodlett at kitware.com Thu Feb 19 09:37:49 2015 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Thu, 19 Feb 2015 09:37:49 -0500 Subject: [Paraview] PCL plugin status and and support of newer PCL versions In-Reply-To: References: Message-ID: > > > Are there any plans to incorporate the PCL plugin into ParaView by default? > > I would love to see this happen. Currently the main challenge is making sure all the PCL dependencies (boost, eigen, flann, etc.) are built across all the needed platforms. Would you be able to help with dashboard builds, patches, etc? -- Casey B Goodlett, PhD Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.otte at gmail.com Thu Feb 19 09:48:53 2015 From: stefan.otte at gmail.com (Stefan Otte) Date: Thu, 19 Feb 2015 15:48:53 +0100 Subject: [Paraview] PCL plugin status and and support of newer PCL versions In-Reply-To: References: Message-ID: I'd evaluate the combination of ParaView&PCL more before I actually invest a lot of time. However, if it actually works as well as it seems then yes, I could contribute patches. Beste Gr??e, Stefan On Thu, Feb 19, 2015 at 3:37 PM, Casey Goodlett wrote: >> >> Are there any plans to incorporate the PCL plugin into ParaView by >> default? >> > > I would love to see this happen. Currently the main challenge is making > sure all the PCL dependencies (boost, eigen, flann, etc.) are built across > all the needed platforms. Would you be able to help with dashboard builds, > patches, etc? > > -- > Casey B Goodlett, PhD > Technical Leader > Kitware, Inc. - North Carolina Office > http://www.kitware.com > (919) 969-6990 x310 From casey.goodlett at kitware.com Thu Feb 19 10:01:58 2015 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Thu, 19 Feb 2015 10:01:58 -0500 Subject: [Paraview] PCL plugin status and and support of newer PCL versions In-Reply-To: References: Message-ID: Stefan, To help get you started the builds linked by this blog post contain a compiled version of the plugin. http://www.kitware.com/blog/home/post/650 On Thu, Feb 19, 2015 at 9:48 AM, Stefan Otte wrote: > I'd evaluate the combination of ParaView&PCL more before I actually > invest a lot of time. However, if it actually works as well as it > seems then yes, I could contribute patches. > > > Beste Gr??e, > Stefan > > > > On Thu, Feb 19, 2015 at 3:37 PM, Casey Goodlett > wrote: > >> > >> Are there any plans to incorporate the PCL plugin into ParaView by > >> default? > >> > > > > I would love to see this happen. Currently the main challenge is making > > sure all the PCL dependencies (boost, eigen, flann, etc.) are built > across > > all the needed platforms. Would you be able to help with dashboard > builds, > > patches, etc? > > > > -- > > Casey B Goodlett, PhD > > Technical Leader > > Kitware, Inc. - North Carolina Office > > http://www.kitware.com > > (919) 969-6990 x310 > -- Casey B Goodlett, PhD Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Feb 19 10:31:39 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 19 Feb 2015 15:31:39 +0000 Subject: [Paraview] [Paraview-developers] min and max range mapping data in color map editor Message-ID: I'm still confused about the question, but based on your screenshot it looks like your data has an RGB vector that is supposed to represent colors. However, ParaView by default assumes that all data are some physical quantity (like, for example, velocity). The default representation of a vector is to take its magnitude (length) and then feed that through a transfer function. That is where quantities like 29.5804 come from. That one in particular is the smallest magnitude of all your colors. I assume what you really want is to render the image using the RGB values as colors. There is an option in the Properties panel named "Map Scalars". Uncheck that box and ParaView should show the original colors without using the color map. -Ken On 2/19/15, 8:05 AM, "dragone" wrote: >Thanks Buren and Kenneth for the response, > >I reply the email directly to you because I didn?t see the way to do it >through the mailing list. > >I agree with you, I only have the position points (x,y,z) and the rgb >coordinates of the surface. As you can see in the attached picture, >paraview creates the scalar array value in the color map editor >(29.5804, 117.599, 256.322) and the thing I don?t understand is how >paraview calculate these values. > >I hope I explained everything well. > >Thanks you very much. > >Laura > > > >El 18/02/2015 a les 21:34, Burlen Loring ha escrit: >> also, usually ParaView colors by a scalar value and from your question >> it seems you are looking at position arrays (x,y,z). Do you have any >> scalar arrays defined? As Ken said, would help to know more about >> your data. >> >> On 02/18/2015 07:40 AM, Moreland, Kenneth wrote: >>> This question is probably more appropriate for the ParaView mailing >>>list >>> rather than the developer's list, so I'm replying to it there. >>> >>> I don't think there is enough information here to answer your question. >>> Any chance you could post an example data set? >>> >>> -Ken >>> >>> >>> >>> On 2/18/15, 7:56 AM, "Laura Masse" wrote: >>> >>>> Hello everybody, >>>> >>>> I have a question about the limits in data range. I don?t understand >>>> how >>>> paraview decide these limits, it seems there no any correspondence >>>>with >>>> the >>>> data value. >>>> >>>> For example, in my case, data is a cloud points in a ply file, my >>>> real x, >>>> y >>>> ,z range are : >>>> >>>> X -1.3 to 14.6 >>>> Y -1.28 to 2.19 >>>> Z -60 to -50.1 >>>> >>>> Data range calculate by paraview is 159.49 to 382.243, I don?t >>>> understand >>>> why . >>>> >>>> I'm looking and looking the data but I don?t get the solution. >>>> >>>> Anyone can help me ? >>>> >>>> Advanced thanks ! >>>> >>>> Laura >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> >>>>http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/min >>>>-an >>>> >>>> d-max-range-mapping-data-in-color-map-editor-tp3636.html >>>> Sent from the The Unofficial ParaView Developers Forum mailing list >>>> archive at Nabble.com. >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Search the list archives at: >>>> http://markmail.org/search/?q=Paraview-developers >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 pcxjf1 at nottingham.ac.uk Thu Feb 19 11:27:08 2015 From: pcxjf1 at nottingham.ac.uk (James Furness) Date: Thu, 19 Feb 2015 16:27:08 +0000 Subject: [Paraview] Error in Reader Example Message-ID: Hi, I am attempting to write a reader and have been following the example at: http://www.vtk.org/Wiki/ParaView/Examples/Plugins/Reader for reference. However it seems not to work. I have copy-pasted the contents into the various files and run ccmake in the directory to produce a make file. Attempting to build this does not compile and fails with the following error: MyReader.cxx:43:45: error: no member named 'GetProducerPort' in 'vtkPolyData' glyphFilter->SetInputConnection(polydata->GetProducerPort()); Looking at the vtk class help pages (http://www.vtk.org/doc/nightly/html/classvtkPolyData.html) it seems there is not method ?GetProducerPort()? in the class vtkPolyData. Have things changed since the example was written? How should I proceed with this? And are there any better guides for writing a custom reader. The documentation is sparse and quite unclear. Many thanks, James This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Thu Feb 19 12:15:54 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Thu, 19 Feb 2015 17:15:54 +0000 Subject: [Paraview] Interpolate nc file In-Reply-To: References: , Message-ID: Dear all,I read a nc file to perform a 3D image generating a script. My results are ploted over coarse mesh and i want to interpolate the nc file data (cohesive sediments). How I add these feature in my script? Kind regardsMadalena _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 Thu Feb 19 12:51:37 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 19 Feb 2015 17:51:37 +0000 Subject: [Paraview] Interpolate nc file Message-ID: I don't remember every possible netCDF convention, but I believe many of them read field data as cell data, which ParaView interprets as constant throughout the cell. That is probably how your data is read. Try adding the Cell Data to Point Data filter. That will estimate the field value on the points, which ParaView will then interpolate through the cells. -Ken From: "Madalena S. Malhadas" > Date: Thursday, February 19, 2015 at 10:15 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Interpolate nc file Dear all, I read a nc file to perform a 3D image generating a script. My results are ploted over coarse mesh and i want to interpolate the nc file data (cohesive sediments). How I add these feature in my script? Kind regards Madalena _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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 sandeepjella at gmail.com Thu Feb 19 18:56:02 2015 From: sandeepjella at gmail.com (Sandeep Jella) Date: Thu, 19 Feb 2015 18:56:02 -0500 Subject: [Paraview] Cumulative Distribution Function Message-ID: <000a01d04c9f$9e4a39c0$dadead40$@gmail.com> Hello, Is it possible to plot a cumulative distribution function for the histogram data in Paraview? Am trying to generate an 'S' Curve and superimpose on top of the histogram data. Thanks, LD -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Feb 19 19:12:35 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 20 Feb 2015 00:12:35 +0000 Subject: [Paraview] Cumulative Distribution Function Message-ID: LD, I don't think there is any built in function in ParaView, but you can convert a histogram to a cumulative distribution by applying the Python Programmable Filter with the following script: import numpy inarray = inputs[0].RowData['bin_values'] cumdist = numpy.cumsum(inarray) output.RowData.append(cumdist, 'cumulative_distribution') I noticed that when you apply the filter, ParaView wants to show it in a spreadsheet view. However, it works if you make it visible in the bar chart view created for the histogram. You can also create a line chart view and display it there. Hope that helps. -Ken From: Sandeep Jella > Date: Thursday, February 19, 2015 at 4:56 PM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Cumulative Distribution Function Hello, Is it possible to plot a cumulative distribution function for the histogram data in Paraview? Am trying to generate an 'S' Curve and superimpose on top of the histogram data. Thanks, LD -------------- next part -------------- An HTML attachment was scrubbed... URL: From canismajorwuff at gmail.com Thu Feb 19 20:05:58 2015 From: canismajorwuff at gmail.com (Canis Major) Date: Fri, 20 Feb 2015 02:05:58 +0100 Subject: [Paraview] Paraview input data format: CELL_DATA vs POINT_DATA Message-ID: I have a structured grid data, that is why I specify 'DATASET STRUCTURED_GRID' type at the output file. I have velocity and pressure as cell attribute, as a result I write CELL_DATA. But when I visualize the data in Paraview I cannot perform for example glyphs or streamlines filters. What is the difference in paraview interpretation of CELL_DATA and POINT_DATA? -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Feb 19 21:38:25 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 20 Feb 2015 02:38:25 +0000 Subject: [Paraview] Paraview input data format: CELL_DATA vs POINT_DATA In-Reply-To: References: Message-ID: <40BA124C-5834-4DDD-8EC4-972468FA957B@sandia.gov> Point data are samples of a continuous field. ParaView will interpolate the point data inside cells to estimate this continuous field. Cell data are a field integrated over the volume of each cell. These are discrete values for each cell. Many filters such as streamlines require a continuous field. Thus, they only work with point data. You can use the Cell Data To Point Data filter to convert a cell field to the point field these filters need. The glyph filter is a bit different. The Cell Data To Point Data trick will work fine with that, too. A slightly more accurate representation would be to instead use the Cell Centers filter instead. That trick will only work for the Glyph filter, and you probably won't be able to tell the difference between the two methods. -Ken Sent from my iPad so blame autocorrect. > On Feb 19, 2015, at 6:06 PM, Canis Major wrote: > > I have a structured grid data, that is why I specify 'DATASET STRUCTURED_GRID' type at the output file. > I have velocity and pressure as cell attribute, as a result I write CELL_DATA. > But when I visualize the data in Paraview I cannot perform for example glyphs or streamlines filters. > What is the difference in paraview interpretation of CELL_DATA and POINT_DATA? > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 matthew.jackson at ch.abb.com Fri Feb 20 04:31:17 2015 From: matthew.jackson at ch.abb.com (Matthew Jackson) Date: Fri, 20 Feb 2015 09:31:17 +0000 Subject: [Paraview] Data Label Representation Visibility Message-ID: Hello, I am trying to create Data Labels for groups of points with Python. Is there a way to tie the visibility of a DataLabelRepresentation object in Python to the visibility of a pipeline source? My goal is simply to have a pipeline object which represents the Data Labels and can be toggled on and off. Best Regards, Matthew Jackson -------------- next part -------------- An HTML attachment was scrubbed... URL: From arctica1963 at gmail.com Fri Feb 20 06:03:11 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Fri, 20 Feb 2015 11:03:11 +0000 Subject: [Paraview] Precise clipping/slicing In-Reply-To: References: Message-ID: Worked out how to solve the problem: specifying the Normal for the clip plane in terms of the cosine and sine function (X, Y) and now it is straightforward to "slice" on specific longitudes for example. It was not clear from the manual about this aspect and what the numbers were. So for 125 East : Origin: 0, 0, 0 Normal: 0.819152044288992 (cos 35), 0.573576436351046 (sin 35), 0 125 West: Origin: 0, 0, 0 Normal: -0.819152044288992 (cos 35), 0.573576436351046 (sin 35), 0 Same options apply if you want to slice along latitudes (or oblique views). Clip plane plots exactly where it should on the map :) Cheers On 19 February 2015 at 09:14, Lester Anderson wrote: > Hello, > > I have got a global dataset matrix and projected this into spherical > coordinates so I could overlay a coastline file for interpretation. > > I can tweak the clipping by manual dragging but I was wondering what the > best way is to do precise clips/slices e.g. a clip at 125 degrees east or > an oblique slice that goes through know coordinates? I can see that the > method is to work out the plane position (origin, normal), but not entirely > clear on what the values represent. > > I have a clip plane defined as below: > > Origin: 372.352441878137 280.135672573806 -125.520109507155 > Normal: 0.771596619611773 0.580503076333685 -0.260105430490818 > > The origin I assume refers to the plane intself in the spherical > coordinates; are the normals in radians? > > This would plot through NW Australia and northwards through Timor on my > data, but it would be useful to generate a series of slices that were say > 120, 125, 130 degrees etc with the clip plane oriented perfectly normal to > the sphere (if that sounds right). > > Hopefully this is not a difficult one; still learning! > > Cheers > > Lester > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From felipe.bordeu at ec-nantes.fr Fri Feb 20 07:25:33 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu) Date: Fri, 20 Feb 2015 13:25:33 +0100 Subject: [Paraview] Fwd: Catalyst simple test In-Reply-To: References: <54E3641E.60800@ec-nantes.fr> <54E4A899.3000608@ec-nantes.fr> Message-ID: <54E727BD.90103@ec-nantes.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I make it work but using the python interface(vtkCPPythonScriptPipeline). I think for my case is easier to build pipelines with the Catalyst plugin for paraview. And anyway my paraview is already compiled with python. Thanks to all for this great feature. Felipe Le 18/02/2015 16:18, Dan Lipsa a ?crit : > Hi Felipe, > I'll try to take a look at it today. > > Dan > > > On Wed, Feb 18, 2015 at 9:58 AM, Felipe Bordeu > wrote: > > > Hi Dan, > > Yes I already saw the post, but is with python. I just want to send my data to paraview. > > I translated the related code for the live visu from python to c++. But I still missing something. > > Can some one look at the code (attached). It is a very simple adaptor with a very simple vtkCPVTKPipeline. > > The thing is I don't understand the way the vtkLiveInsituLink class know about the vtkPBTrivialProducer. > > Thanks to all. > > Felipe > > > Le 17/02/2015 21:43, Dan Lipsa a ?crit : > > (just a forward of my previous response to the list) > > > ---------- Forwarded message ---------- > > From: *Dan Lipsa* > > > Date: Tue, Feb 17, 2015 at 12:19 PM > > Subject: Re: [Paraview] Catalyst simple test > > To: Felipe Bordeu > > > > > Hi Felipe, > > Have you seen: http://www.kitware.com/blog/home/post/722? > > > This blog post shows you how to setup a live connection and describe a simple pipeline using python. > > The pipeline was generated from Tools/Manage Plugins, Catalyst Script Generator Plugin, Load Selected. Then you can build your pipeline and export it using CoProcessing, Export State. > > > We don't have an example with only C++. > > Setting up the visualization pipeline as well as the connection to catalyst live, while possible, is more involved in C++. > > Basically, you'll have write in C++ some of the code in simple.py and coprocessing.py. > > > In your specific case, maybe you are missing the calls to > > > coprocessor.DoLiveVisualization(datadescription, "localhost", 22222) > > > or > > coprocessor.EnableLiveVisualization(True, 1) > > > These are lines from the python coprocessing script that you'll have to rewrite in C++. > > > Dan > > > > On Tue, Feb 17, 2015 at 10:54 AM, Felipe Bordeu > wrote: > > > > Hi everybody, > > > I 'm trying to connect my simulation code (a dummy simulation code for > > the moment) to paraview using Catalyst to do live visualization. Just > > make a mesh (2D structured, with 1 field), and send it to paraview > > without python. But I something is not working. The code runs, I can > > connect to paraview, pause the simulation but unable to sent the data > > for the visualization. > > > So I'm doing this : for initialization > > > create a vtkCPProcessor object and call Initialize(); > > create a vtkCPPipeline derived object class and added to the processor ( > > Processor->AddPipeline(pipeline.GetPointer()); ) . > > (why do I need a Pipeline if I'm going to send my raw data (in vtk > > format of course) to paraview?) > > in the CoProcess( vtkCPDataDescription* dataDescription) member function > > the only relevant lines are : > > vtkNew producer; > > vtkImageData* grid = > > vtkImageData::SafeDownCast(dataDescription->GetInputDescriptionByName("input")->GetGrid()); > > producer->SetOutput(grid,dataDescription->GetTime()); > > > create a vtkLiveInsituLink > > LiveLink = vtkLiveInsituLink::New(); > > LiveLink->SetInsituPort(22222); > > LiveLink->SetHostname("localhost"); > > LiveLink->SetProcessType(vtkLiveInsituLink::INSITU); > > vtkSMProxyManager* proxyManager = vtkSMProxyManager::GetProxyManager(); > > vtkSMSessionProxyManager* sessionProxyManager = > > proxyManager->GetActiveSessionProxyManager(); > > LiveLink->Initialize(sessionProxyManager); > > > > then in each time-step I do : > > > vtkCPDataDescription* dataDescription = vtkCPDataDescription::New(); > > dataDescription->AddInput("input"); > > dataDescription-> SetTimeData(time, timeStep); > > if(Processor->RequestDataDescription(dataDescription) != 0){ > > // Create a uniform grid > > vtkImageData* grid = vtkImageData::New(); > > .... > > ""setextent, create DoubleArray, fill the array, put the array in the > > grid"" > > ... > > dataDescription->GetInputDescriptionByName("input")->SetGrid(grid); > > grid->Delete(); > > > Processor->CoProcess(dataDescription); > > > > (and also the LiveLink code, not sure about this) this is similar to the > > coprocessing.py > > > while(true){ > > LiveLink->InsituUpdate(timeStep, time); > > > LiveLink->InsituPostProcess(time, timeStep); > > > if (LiveLink->GetSimulationPaused()){ > > if (LiveLink->WaitForLiveChange()){ > > break; > > } > > } else { > > break; > > } > > } > > > > I'm pretty sure I'm mixing the code for the different examples I found > > on the web and in the sources. I didn't find an example with pure c++ > > and live viz. > > How I can tell to the LiveLink with data I want to sent to paraview??? > > > using ParaView 4.3.1 compiled from git source in linux. > > > Thanks to all. > > > > > _______________________________________________ > > Powered by www.kitware.com > > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > > 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 > > - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU5yetAAoJEE/fMfNgU9/DpdEH/ipOx/aHWDpTVOOvQG7p58He goKZiQnY/ZqLYlI9m4RqUoht2idqinxClHlRmDv3aPRuMz5HKmUR2hi02vIMJvu9 WhOfx1seUkpME3RDmr+TZlanWJ/myomDbO1pH4nh1GHWmQvobSWKtBaklroXvorC 9Ou0PvwAcuT3YBbtyIyw3WJfyKBDUS6t5XEAfND8tasaa8rmZR8jp4FTFCazz+QS RZA8VdyS5vba1MMNVTPVLwoW6RtfQO1/KcMFtVSOfvvJTNPO5oElxjmY7Gk8fRhi ppkmpWLhHUebqbe8Jvvo9gDvqzEHfKFJZPqZFiDk5piNx0gcMCvoA1N9cJ7TXxs= =Y8TT -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.thomas at imperial.ac.uk Fri Feb 20 08:05:50 2015 From: c.thomas at imperial.ac.uk (Thomas, Christian) Date: Fri, 20 Feb 2015 13:05:50 +0000 Subject: [Paraview] Paraview/Python script speed extracting data Message-ID: <226974D5-0C60-4679-B719-DC14F378F724@Imperial.ac.uk> Hi I'm writing a python script that uses several paraview filters. I then extract data from the final filter for further analysis in python. However, I'm having a problem with the speed of the data extraction (can take several minutes). I have tried writing to a file (createwriter) and then reading the file. I have also tried servermanager.Fetch() and GetPoints? Although I am able to get data with both methods, they are both very slow. I was wondering if there was anything obvious in my paraview/python script that was slowing the process or if anyone has a suggestion at how I may speed things up. (I realise this could just be down to the size of my initial input, for small data files Mesh - 15MB, solution - 50MB). The script is below. Any suggestions would be greatly appreciated. Regards Christian TBR = TAUMeshReader( FileName=Dir+'Mesh' ) TBR.SurfaceMeshOnly = 0 TBR.SolutionFileName = Dir+'solution' MB = MergeBlocks(Input = TBR) T1 = Transform(Input = MB) T1.Transform.Rotate = [-float(Rot/2.0), 0.0, Sweep] ISO = IsoVolume(Input = T1) ISO.ThresholdRange = [MIN_Tot_Pre, BLE_Tot_Pre] ISO.InputScalars = ['POINTS','total_pressure'] SL = Slice(Input = T1) SL.SliceType="Plane" SL.SliceOffsetValues = n SL.SliceType.Origin = Inboard SL.SliceType.Normal = Normal Con = Contour(Input = SL) Con.PointMergeMethod = "Uniform Binning" Con.ContourBy = ['POINTS', 'total_pressure'] Con.Isosurfaces = [BLE_Tot_Pre] Pass = PassArrays(Con) Pass.PointDataArrays = ['wall_distance'] h=CreateWriter(Dir+'Edge.csv',Pass) h.FieldAssociation = "Points" h.Precision = 15 h.UpdatePipeline() ?.read Edge.csv file for further analysis From nazca.nsk at gmail.com Fri Feb 20 10:01:36 2015 From: nazca.nsk at gmail.com (Nsk Nsk) Date: Fri, 20 Feb 2015 15:01:36 +0000 Subject: [Paraview] VTI AppendData Multi piece Message-ID: Hi I'm trying to manually write a vti file containing many blocks, each one of them containing several appended DataArray, my current file looks like this: ....etc _[#bytes_array1_Piece1][DATA_array1_Piece1][#bytes_array2_Piece1] [DATA_array2_Piece1][#bytes_array3_Piece1][DATA_array3_Piece1] [#bytes_array1_Piece2][DATA_array1_Piece2][#bytes_array2_Piece2][DATA_array2 _Piece2][#bytes_array3_Piece2][DATA_array3_Piece2]...etc.. Paraview is able to load the file but the array values seem corrupted. Is there any special requirement for the AppendData block of multiple pieces ImageData? Many thanks, Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Fri Feb 20 10:06:14 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Fri, 20 Feb 2015 10:06:14 -0500 Subject: [Paraview] Fwd: Catalyst simple test In-Reply-To: <54E727BD.90103@ec-nantes.fr> References: <54E3641E.60800@ec-nantes.fr> <54E4A899.3000608@ec-nantes.fr> <54E727BD.90103@ec-nantes.fr> Message-ID: I am glad you made it work. Indeed using python would be a lot easier. Dan On Fri, Feb 20, 2015 at 7:25 AM, Felipe Bordeu wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I make it work but using the python interface(vtkCPPythonScriptPipeline). > I think for my case is easier to build pipelines with the Catalyst plugin > for paraview. And anyway my paraview is already compiled with python. > > Thanks to all for this great feature. > > Felipe > > > Le 18/02/2015 16:18, Dan Lipsa a ?crit : > > Hi Felipe, > > I'll try to take a look at it today. > > > > Dan > > > > > > On Wed, Feb 18, 2015 at 9:58 AM, Felipe Bordeu < > felipe.bordeu at ec-nantes.fr > > wrote: > > > > > > Hi Dan, > > > > Yes I already saw the post, but is with python. I just want to send my > data to paraview. > > > > I translated the related code for the live visu from python to c++. But > I still missing something. > > > > Can some one look at the code (attached). It is a very simple adaptor > with a very simple vtkCPVTKPipeline. > > > > The thing is I don't understand the way the vtkLiveInsituLink class know > about the vtkPBTrivialProducer. > > > > Thanks to all. > > > > Felipe > > > > > > Le 17/02/2015 21:43, Dan Lipsa a ?crit : > > > (just a forward of my previous response to the list) > > > > > ---------- Forwarded message ---------- > > > From: *Dan Lipsa* > > > > > > Date: Tue, Feb 17, 2015 at 12:19 PM > > > Subject: Re: [Paraview] Catalyst simple test > > > To: Felipe Bordeu > > > > > > > > > > Hi Felipe, > > > Have you seen: http://www.kitware.com/blog/home/post/722? > > > > > This blog post shows you how to setup a live connection and describe a > simple pipeline using python. > > > The pipeline was generated from Tools/Manage Plugins, Catalyst Script > Generator Plugin, Load Selected. Then you can build your pipeline and > export it using CoProcessing, Export State. > > > > > We don't have an example with only C++. > > > Setting up the visualization pipeline as well as the connection to > catalyst live, while possible, is more involved in C++. > > > Basically, you'll have write in C++ some of the code in simple.py and > coprocessing.py. > > > > > In your specific case, maybe you are missing the calls to > > > > > coprocessor.DoLiveVisualization(datadescription, "localhost", 22222) > > > > > or > > > coprocessor.EnableLiveVisualization(True, 1) > > > > > These are lines from the python coprocessing script that you'll have > to rewrite in C++. > > > > > Dan > > > > > > > On Tue, Feb 17, 2015 at 10:54 AM, Felipe Bordeu < > felipe.bordeu at ec-nantes.fr > > > > wrote: > > > > > > > Hi everybody, > > > > > I 'm trying to connect my simulation code (a dummy simulation code for > > > the moment) to paraview using Catalyst to do live visualization. Just > > > make a mesh (2D structured, with 1 field), and send it to paraview > > > without python. But I something is not working. The code runs, I can > > > connect to paraview, pause the simulation but unable to sent the data > > > for the visualization. > > > > > So I'm doing this : for initialization > > > > > create a vtkCPProcessor object and call Initialize(); > > > create a vtkCPPipeline derived object class and added to the processor > ( > > > Processor->AddPipeline(pipeline.GetPointer()); ) . > > > (why do I need a Pipeline if I'm going to send my raw data (in vtk > > > format of course) to paraview?) > > > in the CoProcess( vtkCPDataDescription* dataDescription) member > function > > > the only relevant lines are : > > > vtkNew producer; > > > vtkImageData* grid = > > > > vtkImageData::SafeDownCast(dataDescription->GetInputDescriptionByName("input")->GetGrid()); > > > producer->SetOutput(grid,dataDescription->GetTime()); > > > > > create a vtkLiveInsituLink > > > LiveLink = vtkLiveInsituLink::New(); > > > LiveLink->SetInsituPort(22222); > > > LiveLink->SetHostname("localhost"); > > > LiveLink->SetProcessType(vtkLiveInsituLink::INSITU); > > > vtkSMProxyManager* proxyManager = > vtkSMProxyManager::GetProxyManager(); > > > vtkSMSessionProxyManager* sessionProxyManager = > > > proxyManager->GetActiveSessionProxyManager(); > > > LiveLink->Initialize(sessionProxyManager); > > > > > > > then in each time-step I do : > > > > > vtkCPDataDescription* dataDescription = vtkCPDataDescription::New(); > > > dataDescription->AddInput("input"); > > > dataDescription-> SetTimeData(time, timeStep); > > > if(Processor->RequestDataDescription(dataDescription) != 0){ > > > // Create a uniform grid > > > vtkImageData* grid = vtkImageData::New(); > > > .... > > > ""setextent, create DoubleArray, fill the array, put the array in the > > > grid"" > > > ... > > > dataDescription->GetInputDescriptionByName("input")->SetGrid(grid); > > > grid->Delete(); > > > > > Processor->CoProcess(dataDescription); > > > > > > > (and also the LiveLink code, not sure about this) this is similar to > the > > > coprocessing.py > > > > > while(true){ > > > LiveLink->InsituUpdate(timeStep, time); > > > > > LiveLink->InsituPostProcess(time, timeStep); > > > > > if (LiveLink->GetSimulationPaused()){ > > > if (LiveLink->WaitForLiveChange()){ > > > break; > > > } > > > } else { > > > break; > > > } > > > } > > > > > > > I'm pretty sure I'm mixing the code for the different examples I found > > > on the web and in the sources. I didn't find an example with pure c++ > > > and live viz. > > > How I can tell to the LiveLink with data I want to sent to paraview??? > > > > > using ParaView 4.3.1 compiled from git source in linux. > > > > > Thanks to all. > > > > > > > > > _______________________________________________ > > > Powered by www.kitware.com > > > > > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > > 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 > > > > > > > - -- > Felipe Bordeu Weldt > Ing?nieur de Recherche > - ------------------------------------- > T?l. : 33 (0)2 40 37 16 57 > Fax. : 33 (0)2 40 74 74 06 > Felipe.Bordeu at ec-nantes.fr > Institut GeM - UMR CNRS 6183 > ?cole Centrale Nantes > 1 Rue de La No?, 44321 Nantes, FRANCE > - ------------------------------------- > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEcBAEBAgAGBQJU5yetAAoJEE/fMfNgU9/DpdEH/ipOx/aHWDpTVOOvQG7p58He > goKZiQnY/ZqLYlI9m4RqUoht2idqinxClHlRmDv3aPRuMz5HKmUR2hi02vIMJvu9 > WhOfx1seUkpME3RDmr+TZlanWJ/myomDbO1pH4nh1GHWmQvobSWKtBaklroXvorC > 9Ou0PvwAcuT3YBbtyIyw3WJfyKBDUS6t5XEAfND8tasaa8rmZR8jp4FTFCazz+QS > RZA8VdyS5vba1MMNVTPVLwoW6RtfQO1/KcMFtVSOfvvJTNPO5oElxjmY7Gk8fRhi > ppkmpWLhHUebqbe8Jvvo9gDvqzEHfKFJZPqZFiDk5piNx0gcMCvoA1N9cJ7TXxs= > =Y8TT > -----END PGP SIGNATURE----- > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.otte at gmail.com Fri Feb 20 10:41:58 2015 From: stefan.otte at gmail.com (Stefan Otte) Date: Fri, 20 Feb 2015 16:41:58 +0100 Subject: [Paraview] PCL plugin status and and support of newer PCL versions In-Reply-To: References: Message-ID: Wow, I'm really impressed. I just recreated a little vision pipeline that took me a couple of days with PCL. With ParaView and the PCL plugin it took just about an hour, given that knew where I wanted to go and I only tested it on a limited dataset but without prior ParaView experience. I have a few questions/remarks: - Only a small part of PCL is wrapped :( Let's change that! - Sadly, the TangoParaView binary does not include the OpenNI source. I would have loved to test my pipeline on the real problem. - ROS (Robot Operating System) [1] is pretty popular in the robotics community. It's basically a middle ware (and much more) to transfer all kinds of data such as point clouds. I guess it should not be too difficult to write a) a source that subscribes to the point cloud data, and b) a plugin that publishes the results of the pipeline (e.g., the bounding boxes or the resulting cloud). Is that the right way to go? - The dev guide of the PCL plugin only mentions "tbd." in the "Contributing to the PCL Plugin" section. So how does it work? Where is the code? :) - Is it possible to "export" the pipeline and have it run as its own process? Cheers Stefan [1] http://ros.org/ On Thu, Feb 19, 2015 at 4:01 PM, Casey Goodlett wrote: > Stefan, > > To help get you started the builds linked by this blog post contain a > compiled version of the plugin. > > http://www.kitware.com/blog/home/post/650 > > On Thu, Feb 19, 2015 at 9:48 AM, Stefan Otte wrote: >> >> I'd evaluate the combination of ParaView&PCL more before I actually >> invest a lot of time. However, if it actually works as well as it >> seems then yes, I could contribute patches. >> >> >> Beste Gr??e, >> Stefan >> >> >> >> On Thu, Feb 19, 2015 at 3:37 PM, Casey Goodlett >> wrote: >> >> >> >> Are there any plans to incorporate the PCL plugin into ParaView by >> >> default? >> >> >> > >> > I would love to see this happen. Currently the main challenge is making >> > sure all the PCL dependencies (boost, eigen, flann, etc.) are built >> > across >> > all the needed platforms. Would you be able to help with dashboard >> > builds, >> > patches, etc? >> > >> > -- >> > Casey B Goodlett, PhD >> > Technical Leader >> > Kitware, Inc. - North Carolina Office >> > http://www.kitware.com >> > (919) 969-6990 x310 > > > > > -- > Casey B Goodlett, PhD > Technical Leader > Kitware, Inc. - North Carolina Office > http://www.kitware.com > (919) 969-6990 x310 From nazca.nsk at gmail.com Fri Feb 20 10:51:34 2015 From: nazca.nsk at gmail.com (Nsk Nsk) Date: Fri, 20 Feb 2015 15:51:34 +0000 Subject: [Paraview] VTI AppendData Multi piece In-Reply-To: References: Message-ID: I've just realized that my issue is actually related to: http://paraview.markmail.org/thread/nsgch2mmqlkfu7zv When the WholeExtent is not covered by , the missing values are random. Is there a way to stop this from happening? Cheers Nick On Fri, Feb 20, 2015 at 3:01 PM, Nsk Nsk wrote: > Hi > > I'm trying to manually write a vti file containing many blocks, > each one of them containing several appended DataArray, my current file > looks like this: > > > > > > > > offset="0" /> > offset="36" /> > offset="72" /> > > > > > offset="108" /> > offset="176" /> > offset="244" /> > > > > ....etc > > > > _[#bytes_array1_Piece1][DATA_array1_Piece1][#bytes_array2_Piece1] > [DATA_array2_Piece1][#bytes_array3_Piece1][DATA_array3_Piece1] > [#bytes_array1_Piece2][DATA_array1_Piece2][#bytes_array2_Piece2] > [DATA_array2_Piece2][#bytes_array3_Piece2][DATA_array3_Piece2]...etc.. > > > > Paraview is able to load the file but the array values seem corrupted. Is > there any special requirement for the AppendData block of multiple pieces > ImageData? > Many thanks, > > Nick > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhtzeng at yahoo.com Fri Feb 20 14:21:54 2015 From: mhtzeng at yahoo.com (Michael Tzeng) Date: Fri, 20 Feb 2015 19:21:54 +0000 (UTC) Subject: [Paraview] Loading FIle Types Message-ID: <1076396467.1120327.1424460114453.JavaMail.yahoo@mail.yahoo.com> Hello Paraview Community, I'm an undergraduate student at George Washington University working on research in a Bio-fluids lab in the Mechanical Engineering Department. I've been tasked to learn how to use Paraview to read various types of lab data. I've been learning from the tutorial and playing with the provided files from the Paraview website. The file type I've been learning from is .ex2 or Exodus II. I've tried to load Tecplot files saved in the .dat format, but I was never able to successfully display any data.? My main question is does data have to be converted to certain files for Paraview to be able to read them or is there an in between step that you can perform that will allow Paraview to read the file that is trying to be loaded? Of course the file types that I tried to load are all the file types Paraview claim they can read.? What I did. I opened my selected Tecplot file and Paraview then asked "Open Data With.." and a list of file types would be presented to me. This is screenshot number one. I tried all the options, but the option that seemed to almost produce a result was "Tecplot files". After I select "Tecplot Files" I would load all the variables and hit apply. An error report would pop up and I would be unable to see my data. This can be seen in screenshot number two. The Tecplot file I tried opening is included in this email and is called 85 Waves_trans_Coher.dat. I tried approaching this problem with another method. I opened one of the saved files I had been working on from the tutorial in Notepad++. I thought if I changed my existing file to match how the data was written in the .ex2 file Paraview would be able to read it. I edited the Tecplot file I was working on in excel to match the .ex2 file. I tried opening it and it still didn't work. I knew Paraview is able to read .CSV files so I then edited my file in excel to match the format of .CSV. I opened the file and hit apply. It displayed my data as seen in screenshot number 3. I then used the command, ctrl + space, and searched for Table to Points. I set my three variables to the X, Y, Z column and hit apply. I was able to display my data at last! This can be seen in screenshot number 4. But I want to know how I'm able to display my data in it's original file type without having to manipulate it. And I want to know how I can color my displayed data in .CSV by variable. For some reason it doesn't give me the option of selecting color by variables.? All the files are saved online. I will provide a link that will take you to the files. https://www.dropbox.com/sh/wlpspkk3qc29ms0/AAA8t0Wlu-oHE1WTUwgEmA4ea?dl=0 Let me know what I'm doing wrong. Thank you! H -------------- next part -------------- An HTML attachment was scrubbed... URL: From samuelkey at bresnan.net Fri Feb 20 10:51:42 2015 From: samuelkey at bresnan.net (Samuel Key) Date: Fri, 20 Feb 2015 08:51:42 -0700 Subject: [Paraview] Precise clipping/slicing In-Reply-To: References: Message-ID: <54E7580E.30805@bresnan.net> An HTML attachment was scrubbed... URL: From kilian.weishaupt at gmx.net Sat Feb 21 13:00:24 2015 From: kilian.weishaupt at gmx.net (Kilian Weishaupt) Date: Sat, 21 Feb 2015 19:00:24 +0100 Subject: [Paraview] PV 4.3.1 Color legend and Color discretization In-Reply-To: References: Message-ID: <54E8C7B8.4020806@gmx.net> Thanks Utkarsh! Since the color mapping seems to work correctly I found a workaround by just disabling the ticks and adding annotations at each 10 K manually to the legend. Here, the same problem occurs. If you add for instance an annotation for the value 350 K it does not appear exactly at the beginning of the 350 -360 K interval but slightly shifted. You can circumvent this issue by setting a slightly lower value (or higher if the annotation appears below where it should) by trial and error. Not a very elegant solution but it should work as long as the bug has not been fixed. Best regards Kilian Am 12.02.2015 um 21:03 schrieb Utkarsh Ayachit: > Kilian, > > I suspect this is indeed an issue with the labeling. The color mapping > is indeed behaving as expected (I verified by creating a calculator > filter and making it produce the constant of interest and then > coloring by it). > > I've reported a bug: http://www.paraview.org/Bug/view.php?id=15319 > > Utkarsh > > On Thu, Feb 12, 2015 at 10:05 AM, Kilian Weishaupt > wrote: >> I am trying to use the color discretization feature in order to get a color >> legend that somehow resembles the one I have attached here >> (colorlegend1.png). >> It features 11 regions that each represent a temperature range of 10 K. >> >> My first idea was to use the "Blue to Red Rainbow" preset in combination >> with 11 table values and a range of 280 to 390 K (see colorlegend2.png). >> Maybe I am just missing a very simple point here but the temperature ranges >> (or in other words: the "boxes of different colors" on the scale) do not >> seem to fit to the label ticks (especially the one at 380 K). >> >> I have tried various combinations of the number of table values and the >> number of ticks for the color scale but none of this worked. >> >> Do you have any ideas? >> >> Best regards >> Kilian >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 arctica1963 at gmail.com Sat Feb 21 13:15:58 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Sat, 21 Feb 2015 18:15:58 +0000 Subject: [Paraview] SEG-Y seismic data loading Message-ID: Hello, Is there anyway to get SEG-Y data into Paraview or some workaround to this ? Downloaded the latest version and I could not see an obvious route for this. Thanks Lester -------------- next part -------------- An HTML attachment was scrubbed... URL: From asche.j at googlemail.com Sun Feb 22 06:11:51 2015 From: asche.j at googlemail.com (Jonas Asche) Date: Sun, 22 Feb 2015 12:11:51 +0100 Subject: [Paraview] change text color in python script Message-ID: Hello, i am working on a script that makes screenshots. I need to use a white background and therefore i want to change the font color of the color legend to black. I have tried to get the necesarry commands via the trace function but i have not seen any command that would help me. It would be enough to set the color palette to "print" but that also gives no command in the trace. Any help is appreciated Regards, Jonas -------------- next part -------------- An HTML attachment was scrubbed... URL: From gda at tacc.utexas.edu Sun Feb 22 14:42:19 2015 From: gda at tacc.utexas.edu (Greg Abram) Date: Sun, 22 Feb 2015 19:42:19 +0000 Subject: [Paraview] Crash loading Catalyst plugin Message-ID: <50BFCD8E-9D7F-47C7-9DAD-498D4B595E90@tacc.utexas.edu> Hey y'all - We're seeing a crash that seems to be caused by the Catalyst plugin - when you try to connect the GUI to an external server with the Catalyst plugin loaded, the GUI crashes. If you do not have the plugin loaded, you can connect and then load the plugin. Just us? Greg Gregory D. Abram, Ph.D. Research Engineering/Scientist Associate Texas Advanced Computing Center The University of Texas at Austin (512) 471-8196 gda at tacc.utexas.edu [TACC Website] Connect With TACC -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Sun Feb 22 17:23:56 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Sun, 22 Feb 2015 17:23:56 -0500 Subject: [Paraview] Crash loading Catalyst plugin In-Reply-To: <50BFCD8E-9D7F-47C7-9DAD-498D4B595E90@tacc.utexas.edu> References: <50BFCD8E-9D7F-47C7-9DAD-498D4B595E90@tacc.utexas.edu> Message-ID: The Catalyst script generator plugin should only be needed on the client side. I'll try and reproduce the problem here and see about getting it fixed. Thanks for the info. Andy On Sun, Feb 22, 2015 at 2:42 PM, Greg Abram wrote: > Hey y'all - > > We're seeing a crash that seems to be caused by the Catalyst plugin - > when you try to connect the GUI to an external server with the Catalyst > plugin loaded, the GUI crashes. If you do not have the plugin loaded, > you can connect and *then *load the plugin. > > Just us? > > Greg > > > Gregory D. Abram, Ph.D. > Research Engineering/Scientist Associate > Texas Advanced Computing Center > The University of Texas at Austin > (512) 471-8196 > gda at tacc.utexas.edu > > [image: TACC Website] > > Connect With TACC > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 ruqingxuwork at gmail.com Sun Feb 22 18:23:41 2015 From: ruqingxuwork at gmail.com (Xu, Ruqing) Date: Sun, 22 Feb 2015 17:23:41 -0600 Subject: [Paraview] Fwd: Volume rendering with RGBA data In-Reply-To: References: Message-ID: Hello, I'm displaying my simple 3D data set on a structured grid. With a 4-component unsigned integer vector on each point, and after turning off the "map scalar" option in the displays, I have been able to present my data with the given RGBA values in the "surface" or "points" mode. In the "volume" mode, however, this breaks down and the colors & opacity are still mapped from the individual components of the 4-vectors as scalars. Am I missing anything? Or is this a known issue? I'm using ParaView 4.3.1, Thanks. -Ruq -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfiorillo at lara.unb.br Mon Feb 23 07:54:02 2015 From: dfiorillo at lara.unb.br (David Fiorillo) Date: Mon, 23 Feb 2015 09:54:02 -0300 Subject: [Paraview] Ep_g from region in paraview Message-ID: Dears, Anyone could suggest how to plot average Ep_g over time over a region of interest in the paraview? [image: Imagem inline 1] Best regards, David -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ROI.png Type: image/png Size: 14982 bytes Desc: not available URL: From dkxls23 at gmail.com Mon Feb 23 08:06:35 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Mon, 23 Feb 2015 15:06:35 +0200 Subject: [Paraview] Ep_g from region in paraview In-Reply-To: References: Message-ID: <54EB25DB.1050903@gmail.com> A couple of weeks back has been a similar discussion, see more here: http://public.kitware.com/pipermail/paraview/2015-January/033104.html -Armin On 02/23/2015 02:54 PM, David Fiorillo wrote: > Dears, > > Anyone could suggest how to plot average Ep_g over time over a region of > interest in the paraview? > > Imagem inline 1 > > Best regards, > > David > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Mon Feb 23 09:12:38 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 23 Feb 2015 09:12:38 -0500 Subject: [Paraview] reducing startup time on cray In-Reply-To: <54D53358.5020209@lbl.gov> References: <54D50E1D.4010202@lbl.gov> <54D53358.5020209@lbl.gov> Message-ID: Burlen, > I'm unfamiliar with freezing python and how it would work with pvserver, > pvbatch, or pvpython. Question: how/what do we freeze in the pvserver case? Check this out: http://www.kitware.com/blog/home/post/517 Utkarsh From sandeepjella at gmail.com Mon Feb 23 11:16:03 2015 From: sandeepjella at gmail.com (Sandeep Jella) Date: Mon, 23 Feb 2015 11:16:03 -0500 Subject: [Paraview] Looping over blocks in a multiblock data set and printing to a table or graph Message-ID: Hello, I have a list of surfaces that I would like to automatically loop over and calculate means and standard deviations of a variable on each and then plot to a single plot. I guess I'd have to do this in a programmable filter attached to the multiblock entity* but need some guidance on the code/macro that will loop over the surfaces. * (I used the "Extract block" functionality which selects a bunch of surfaces from a much larger dataset) Many thanks, Sandeep. -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Feb 23 13:53:45 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 23 Feb 2015 13:53:45 -0500 Subject: [Paraview] Looping over blocks in a multiblock data set and printing to a table or graph In-Reply-To: References: Message-ID: It'll be something like follows: Programmable Filter: OutputDataSetType= "vtkTable". ============================================== Script ============================================== import numpy as np size = 0 for input_block in inputs[0]: size += 1 meanArray = np.zeros(size, dtype = np.float64) index = 0 for input_block in inputs[0]: mean = np.mean(input_block.PointData["Elevation"]) meanArray[index] = mean index += 1 output.RowData.append(meanArray, "MeanElevation") A 4.3.1 state file attached. Utkarsh On Mon, Feb 23, 2015 at 11:16 AM, Sandeep Jella wrote: > Hello, > > I have a list of surfaces that I would like to automatically loop over and > calculate means and standard deviations of a variable on each and then plot > to a single plot. > > I guess I'd have to do this in a programmable filter attached to the > multiblock entity* but need some guidance on the code/macro that will loop > over the surfaces. > > * (I used the "Extract block" functionality which selects a bunch of > surfaces from a much larger dataset) > > Many thanks, > > Sandeep. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 Mon Feb 23 13:54:06 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 23 Feb 2015 13:54:06 -0500 Subject: [Paraview] Looping over blocks in a multiblock data set and printing to a table or graph In-Reply-To: References: Message-ID: On Mon, Feb 23, 2015 at 1:53 PM, Utkarsh Ayachit wrote: > It'll be something like follows: > > Programmable Filter: OutputDataSetType= "vtkTable". > ============================================== > Script > ============================================== > import numpy as np > > size = 0 > for input_block in inputs[0]: > size += 1 > meanArray = np.zeros(size, dtype = np.float64) > > index = 0 > for input_block in inputs[0]: > mean = np.mean(input_block.PointData["Elevation"]) > meanArray[index] = mean > index += 1 > output.RowData.append(meanArray, "MeanElevation") > > A 4.3.1 state file attached. > > Utkarsh > > On Mon, Feb 23, 2015 at 11:16 AM, Sandeep Jella wrote: >> Hello, >> >> I have a list of surfaces that I would like to automatically loop over and >> calculate means and standard deviations of a variable on each and then plot >> to a single plot. >> >> I guess I'd have to do this in a programmable filter attached to the >> multiblock entity* but need some guidance on the code/macro that will loop >> over the surfaces. >> >> * (I used the "Extract block" functionality which selects a bunch of >> surfaces from a much larger dataset) >> >> Many thanks, >> >> Sandeep. >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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: PlotMeanPerBlock.pvsm Type: application/octet-stream Size: 45960 bytes Desc: not available URL: From wascott at sandia.gov Mon Feb 23 16:28:27 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 23 Feb 2015 21:28:27 +0000 Subject: [Paraview] [EXTERNAL] Fwd: Volume rendering with RGBA data In-Reply-To: References: Message-ID: Ruq, Volume rendering vectors appears to have multiple bugs. And you are correct ? volume rendering a non map scalar vector appears to turn on map scalars. I wrote up bugs. http://www.paraview.org/Bug/view.php?id=15340 http://www.paraview.org/Bug/view.php?id=15339 I marked a duplicate, 14242, as targeted for PV 4.4. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Xu, Ruqing Sent: Sunday, February 22, 2015 4:24 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Fwd: Volume rendering with RGBA data Hello, I'm displaying my simple 3D data set on a structured grid. With a 4-component unsigned integer vector on each point, and after turning off the "map scalar" option in the displays, I have been able to present my data with the given RGBA values in the "surface" or "points" mode. In the "volume" mode, however, this breaks down and the colors & opacity are still mapped from the individual components of the 4-vectors as scalars. Am I missing anything? Or is this a known issue? I'm using ParaView 4.3.1, Thanks. -Ruq -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Feb 23 16:50:39 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 23 Feb 2015 16:50:39 -0500 Subject: [Paraview] Crash loading Catalyst plugin In-Reply-To: References: <50BFCD8E-9D7F-47C7-9DAD-498D4B595E90@tacc.utexas.edu> Message-ID: Hi Greg, I tried this with PV master as of today. If the server is running with more than a single process I get a crash when connecting to it if the Catalyst script generator plugin is already loaded. If the server is just a single process though this works fine as well as loading the plugin after connecting to the server. Luckily this isn't a show-stopper but it needs to get fixed. I added a bug report (http://www.paraview.org/Bug/view.php?id=15341). Thanks for the info. Regards, Andy On Sun, Feb 22, 2015 at 5:23 PM, Andy Bauer wrote: > The Catalyst script generator plugin should only be needed on the client > side. I'll try and reproduce the problem here and see about getting it > fixed. > > Thanks for the info. > > Andy > > On Sun, Feb 22, 2015 at 2:42 PM, Greg Abram wrote: > >> Hey y'all - >> >> We're seeing a crash that seems to be caused by the Catalyst plugin - >> when you try to connect the GUI to an external server with the Catalyst >> plugin loaded, the GUI crashes. If you do not have the plugin loaded, >> you can connect and *then *load the plugin. >> >> Just us? >> >> Greg >> >> >> Gregory D. Abram, Ph.D. >> Research Engineering/Scientist Associate >> Texas Advanced Computing Center >> The University of Texas at Austin >> (512) 471-8196 >> gda at tacc.utexas.edu >> >> [image: TACC Website] >> >> Connect With TACC >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 anlaufb at de.ibm.com Tue Feb 24 05:14:57 2015 From: anlaufb at de.ibm.com (Benedikt Anlauf) Date: Tue, 24 Feb 2015 10:14:57 +0000 (UTC) Subject: [Paraview] =?utf-8?q?Compile_error=3A_unknown_type_name_=E2=80=98?= =?utf-8?b?c2lnam1wX2J1ZuKAmQ==?= References: <20150218160213.GA20180@megas.kitwarein.com> <20150218194852.GA15902@megas.kitwarein.com> Message-ID: Ben Boeckel kitware.com> writes: > > On Wed, Feb 18, 2015 at 12:52:30 -0500, John Moore wrote: > > H5JMP_BUF is not found in CMakeCache.txt, but H5_HAVE_SETJMP_H is, as shown > > below: > > Ah, I see that H5JMP_BUF is defined at the top of the file, not by CMake > and is controlled by H5_HAVE_SIGSETJMP (empty on my Fedora install) or > H5_HAVE_SIGLONGJMP ('1' here) from the CMake cache file. > > > //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 > > > > I've tried to compile both with and without having HDF5 installed on my > > system, and both methods fail. I haven't tried -DVTK_USE_SYSTEM_HDF5=ON yet > > because I would like to be able to use the H5 included with VTK, if > > possible. > > It is odd that it finds the header, but then (seems) to not include it. > Could you insert an #error or something in H5private.h in the same block > as #include to see if it is actually included? > > --Ben > Hi, I've got the same problem, compiling Paraview 4.3.1 on Ubuntu 14.04. fails. I've done what you've suggested 125 #ifdef H5_HAVE_SETJMP_H 126 /* Added to test whether including works */ 127 #error("setjmp.h is included") 128 # include 129 #endif and subsequently the compilation fails with In file included from /dev/shm/anlaufb/ParaView-v4.3.1- source/VTK/ThirdParty/hdf5/vtkhdf5/src/H5make_libsettings.c:46:0: /dev/shm/anlaufb/ParaView-v4.3.1-source/VTK/ThirdParty/hdf5/vtkhdf5/src/ H5private.h:127:2: error: #error ("setjmp.h is included") #error("setjmp.h is included") ^ so the include-mechanism seems to work fine. All the mentioned variables are identical to the values you've provided. Can you provide any insights how to fix this? Thanks in advance Benedikt From arctica1963 at gmail.com Tue Feb 24 05:37:04 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Tue, 24 Feb 2015 10:37:04 +0000 Subject: [Paraview] GMT grids to 3D surface Message-ID: Hello, I can see how to load a GMT (netCDF) grid into Paraview but cannot seem to see how to translate it into an elevation surface. The data is a gridded surface of a subducting slab geometry, with X, Y as longitude and latitude respectively, and Z as the depth range 0 to -700 km. Here the Z value represents the scalar depth. Do I need to pre-process the data prior to loading into Paraview? When loaded the Z-dimension is 1 so it is still essentially a 2D surface. Loading point data (eg earthquake solutions) is fine as I can edit the data table, but not sure what else I need to get a slab surface in correctly: for plotting the Z-dimension would need to have an extent of 0 to 699 (d=700). Be good to know how I can solve this simply. Cheers Lester -------------- next part -------------- An HTML attachment was scrubbed... URL: From houssen at ipgp.fr Tue Feb 24 08:47:24 2015 From: houssen at ipgp.fr (houssen) Date: Tue, 24 Feb 2015 14:47:24 +0100 Subject: [Paraview] =?utf-8?q?How_to_visualize_Hexahedron_27_elements_in_P?= =?utf-8?q?araview_using_XDMF_=3F?= Message-ID: <8bc5f9dcd49ed5ea882dd7d95ce559cc@imap.ipgp.fr> Hello, How to visualize Hexahedron 27 elements in Paraview using XDMF ? I didn't find the answer in the documentation. I looked in the source code (tar.gz) but it didn't help. I tested several possibilities without success... Can somebody help me on this ? Thanks, FH -------------- next part -------------- A non-text attachment was scrubbed... Name: h27.xmf Type: application/xml Size: 1652 bytes Desc: not available URL: From houssen at ipgp.fr Tue Feb 24 08:59:49 2015 From: houssen at ipgp.fr (houssen) Date: Tue, 24 Feb 2015 14:59:49 +0100 Subject: [Paraview] =?utf-8?q?Fwd=3A_How_to_visualize_Hexahedron_27_elemen?= =?utf-8?q?ts_in_Paraview_using_XDMF_=3F?= Message-ID: <69470b7b2a83f0c72f253c9e02f09fec@imap.ipgp.fr> Hello, How to visualize Hexahedron 27 elements in Paraview using XDMF ? I didn't find the answer in the documentation. I looked in the source code (tar.gz) but it didn't help. I tested several possibilities without success... Can somebody help me on this ? Thanks, FH -------------- next part -------------- A non-text attachment was scrubbed... Name: h27.xmf Type: application/xml Size: 1652 bytes Desc: not available URL: From wascott at sandia.gov Tue Feb 24 12:59:03 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 24 Feb 2015 17:59:03 +0000 Subject: [Paraview] rhel5 vs rhel6 Message-ID: <83881be303f14aa28834f57a1c6c0451@ES05AMSNLNT.srn.sandia.gov> Can builds of ParaView run only on the version of rhel that they were built for, or can they move between OS versions? Also, what was the Kitware Linux build - rhel5 or rhel6? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From felipe.bordeu at ec-nantes.fr Tue Feb 24 12:58:53 2015 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu) Date: Tue, 24 Feb 2015 18:58:53 +0100 Subject: [Paraview] Fwd: How to visualize Hexahedron 27 elements in Paraview using XDMF ? In-Reply-To: <69470b7b2a83f0c72f253c9e02f09fec@imap.ipgp.fr> References: <69470b7b2a83f0c72f253c9e02f09fec@imap.ipgp.fr> Message-ID: <54ECBBDD.5090405@ec-nantes.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 attached a working file, and also a picture of my hexa 27 , you can print it and build it. Felipe Le 24/02/2015 14:59, houssen a ?crit : > Hello, > > How to visualize Hexahedron 27 elements in Paraview using XDMF ? > > I didn't find the answer in the documentation. I looked in the source code (tar.gz) but it didn't help. I tested several possibilities without success... Can somebody help me on this ? > > Thanks, > > FH > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU7LvXAAoJEE/fMfNgU9/DHNkIAJM1F2ePsBiyY1T+3XZFXUvW o6rtmvsPUod5TYFDIEb5ZVSH5RXo/QSugPWK6WhyTd1r5MnHNMaEF4FotmXAIKru izwhljezyqHwvNNKG7OZlec/zhjvXRk8Qo7cDcwRhbv80d31VG8DpVhTRmBFDqth 2y/NQSNOI7ew2Xi++BOkSxz8rq3M0gHnr7OmrXb+CjXZp1CaYF8L0vX3ml6kEPIz F5SDAauP30mQ31DaHCITAriRFD8cgZN+FpvFquTv4Wik4W8rSHsE1b33EY+l2Pnb 32Aq5yT2v2rYzQswVUlppP2UL+iQqvZvIs1nkataD2AlhafCCjf49TZ5sJo04CI= =lMQi -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: h27.xmf Type: audio/x-xmf Size: 2060 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 24022015963.jpg Type: image/jpeg Size: 142478 bytes Desc: not available URL: From richard.c.angelini.civ at mail.mil Tue Feb 24 13:03:45 2015 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US)) Date: Tue, 24 Feb 2015 18:03:45 +0000 Subject: [Paraview] rhel5 vs rhel6 Message-ID: Alan ? I build on a RHEL5 system and it seems to work on RHEL6 systems ? or at least I haven?t heard anyone complain ?. 8-) ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 From: , Alan Scott > Date: Tuesday, February 24, 2015 at 12:59 PM To: "paraview at paraview.org" > Subject: [Paraview] rhel5 vs rhel6 Can builds of ParaView run only on the version of rhel that they were built for, or can they move between OS versions? Also, what was the Kitware Linux build ? rhel5 or rhel6? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From pnav at tacc.utexas.edu Tue Feb 24 16:18:43 2015 From: pnav at tacc.utexas.edu (Paul Navratil) Date: Tue, 24 Feb 2015 21:18:43 +0000 Subject: [Paraview] EGPGV Visualization Showcase deadline Feb 28 Message-ID: <72439132-6DE6-4D2E-BFB0-CD02CDEC43B7@tacc.utexas.edu> Hello ParaView Users, One last reminder about the new EGPGV Visualization Showcase track, submissions due this Friday. All best, Paul Navratil Texas Advanced Computing Center Scientific Visualization Showcase This year we present a new track for EGPGV 2015, which provides a forum for the year's most instrumental movies in parallel graphics and visualization. Finalists will compete for the Best Visualization Award, and each finalist will present his or her movie during a dedicated session at EGPGV ?15 in a 10-minute presentation. Movies are judged based on how their movie illuminates science, by the quality of the movie, and for innovations in the process used for creating the movie. The accepted submissions will appear as short papers in the symposium proceedings. Review and selection process: Submission should include ?Visualization Showcase:? at the beginning of the paper title. Submissions needed to include a movie (up to 150MB in size) and a short paper (up to 4 pages including references). The short paper should describe the scientific story conveyed by the movie, how the visualization helps scientific discovery, and the "state-of-the-practice" information behind making the movie. The short paper should be submitted using the Eurographics Conference style (https://srmv2.eg.org/COMFy/Conference/PGV_2015/GetConferenceFile?fileID=6146). Please use this linked version, which contains the correct details for EGPGV. Each submission will be peer reviewed by the EGPGV Paper Chairs. Criteria for revision include: 1. Compelling visualization 2. Visualizing data involving parallel graphics and/or visualization in a significant way (e.g., data size, parallel processing, parallel rendering) 3. Meaningful and compelling science story 4. Description of visualization techniques necessary to accomplish the movie The expected schedule is as follows: * Showcase Submission Due: February 28, 2014 * Author Notification: March 27, 2014 * Camera-Ready Paper Due: April 8, 2014 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.nahshon at navy.mil Tue Feb 24 17:59:12 2015 From: ken.nahshon at navy.mil (Nahshon, Ken Dr. CIV NSWCCD West Bethesda MD, 664) Date: Tue, 24 Feb 2015 22:59:12 +0000 Subject: [Paraview] Getting File Names from PVD File Message-ID: <98A5EBA39B71F24790656277413FB27E0D9DA395@NAEAPAXRXM03V.nadsusea.nads.navy.mil> Hi, I am trying to recover the file names of the .vtu files that are contained within a .pvd XML file that I am reading in. I am only able to see the timestep data and file name of the PVD itself. Does anyone know where the file= attribute located in the .pvd file stored within Paraview? Ultimately I am trying to read in a series of .pvtr files (pointing to vtr files) and export the data as a series of Exodus files with one .e file per timestep. Trying to generate one big .e file directly generates an error due to what appears to be a format error (I assume from the lack of timestep associated the core data beyond the pvd file). Any advice would be appreciated. Thanks for the help. Best, Ken ******************************************** Ken Nahshon, Ph.D. Research Engineer Code 664 - Hull Response and Protection Branch Naval Surface Warfare Center Carderock Division (NSWCCD) Tel: 301-227-1800 Fax: 301-227-1323 ******************************************** -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5602 bytes Desc: not available URL: From djortley at gmail.com Tue Feb 24 18:13:39 2015 From: djortley at gmail.com (David Ortley) Date: Tue, 24 Feb 2015 16:13:39 -0700 Subject: [Paraview] Smooth seams in SILO files Message-ID: Hello all, We have a CFD code that generates silo files using the silo library. For each dump in the simulation, there are multiple files per dump (one file per processor) and a single master file. When we use Visit to visualize a contour, the contours look good. When using Paraview (any version), there exist obvious seams at the file boundaries. To visualize in Paraview, we use the 'CellDatatoPointData' filter followed by the 'Contour' filter. I'm currently trying to track down if either Visit is magically healing over a bug in our implementation, or if the problem lies with Paraview somehow...or with how I'm trying to generate the contour (via the 'CellDatatoPointData' filter.) It almost looks like Paraview is treating the edge of each file as if it were an open boundary regardless of whether it is buttressed up against another file. Thanks for any help in this. -David Ortley -------------- next part -------------- An HTML attachment was scrubbed... URL: From sandeepjella at gmail.com Tue Feb 24 23:08:25 2015 From: sandeepjella at gmail.com (Sandeep Jella) Date: Tue, 24 Feb 2015 23:08:25 -0500 Subject: [Paraview] Looping over blocks in a multiblock data set and printing to a table or graph In-Reply-To: References: Message-ID: Hi Utkarsh, this works perfectly! I have a related question... I created a custom filter that I'd like to call from within the loop (over the blocks). Being able to call other filters within the loop would tremendously save time...is there such a possibility? Many thanks again for your fast response earlier, Sandeep. On Mon, Feb 23, 2015 at 1:54 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > On Mon, Feb 23, 2015 at 1:53 PM, Utkarsh Ayachit > wrote: > > It'll be something like follows: > > > > Programmable Filter: OutputDataSetType= "vtkTable". > > ============================================== > > Script > > ============================================== > > import numpy as np > > > > size = 0 > > for input_block in inputs[0]: > > size += 1 > > meanArray = np.zeros(size, dtype = np.float64) > > > > index = 0 > > for input_block in inputs[0]: > > mean = np.mean(input_block.PointData["Elevation"]) > > meanArray[index] = mean > > index += 1 > > output.RowData.append(meanArray, "MeanElevation") > > > > A 4.3.1 state file attached. > > > > Utkarsh > > > > On Mon, Feb 23, 2015 at 11:16 AM, Sandeep Jella > wrote: > >> Hello, > >> > >> I have a list of surfaces that I would like to automatically loop over > and > >> calculate means and standard deviations of a variable on each and then > plot > >> to a single plot. > >> > >> I guess I'd have to do this in a programmable filter attached to the > >> multiblock entity* but need some guidance on the code/macro that will > loop > >> over the surfaces. > >> > >> * (I used the "Extract block" functionality which selects a bunch of > >> surfaces from a much larger dataset) > >> > >> Many thanks, > >> > >> Sandeep. > >> > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: > >> http://paraview.org/Wiki/ParaView > >> > >> 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 ruqingxuwork at gmail.com Wed Feb 25 02:18:29 2015 From: ruqingxuwork at gmail.com (Xu, Ruqing) Date: Wed, 25 Feb 2015 01:18:29 -0600 Subject: [Paraview] Minimum system requirement for PV 4.3 volume rendering? Message-ID: Hello, I've installed PV 4.3 on a few PCs, all of them running Win 7 64-bit. What I've found is that volume rendering, curiously, works on some of them and fails on others. The error messages I got look like this: ========================================= ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\VolumeOpenGL\vtkOpenGLProjectedTetrahedraMapper.cxx, line 188 vtkOpenGLProjectedTetrahedraMapper (0000000013AB80B0): The required extensions are not supported. Warning: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLExtensionManager.cxx, line 781 vtkOpenGLExtensionManager (0000000013567D60): Attempting to load GL_ARB_multitexture, which is not supported. ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLExtensionManager.cxx, line 787 vtkOpenGLExtensionManager (0000000013567D60): Extension GL_ARB_multitexture could not be loaded. =============================================== This seems to only happen to the relatively old PCs (~ 4 or 5 years old). For example one of them has graphics card of ATI Radeon HD 3450 (Microsoft Corporation WDDM 1.1), driver version 7.14.10.0018; another laptop has Intel HD graphics, driver version 8.15.10.2559. - I'm wondering if these are considered insufficient for volume rendering to work with PV 4.3. More curiously, volume rendering seems to run OK with PV 4.2 on these machines. Thanks, -Ruq -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Feb 25 09:17:20 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 25 Feb 2015 09:17:20 -0500 Subject: [Paraview] GMT grids to 3D surface In-Reply-To: References: Message-ID: Have you tried the "Warp By Scalar" filter? The filter allows you to select the scalar to warp with as well as the normal along which to warp the mesh. Utkarsh On Tue, Feb 24, 2015 at 5:37 AM, Lester Anderson wrote: > Hello, > > I can see how to load a GMT (netCDF) grid into Paraview but cannot seem to > see how to translate it into an elevation surface. > > The data is a gridded surface of a subducting slab geometry, with X, Y as > longitude and latitude respectively, and Z as the depth range 0 to -700 km. > Here the Z value represents the scalar depth. > > Do I need to pre-process the data prior to loading into Paraview? When > loaded the Z-dimension is 1 so it is still essentially a 2D surface. Loading > point data (eg earthquake solutions) is fine as I can edit the data table, > but not sure what else I need to get a slab surface in correctly: for > plotting the Z-dimension would need to have an extent of 0 to 699 (d=700). > > Be good to know how I can solve this simply. > > Cheers > > Lester > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Feb 25 09:23:19 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 25 Feb 2015 09:23:19 -0500 Subject: [Paraview] Getting File Names from PVD File In-Reply-To: <98A5EBA39B71F24790656277413FB27E0D9DA395@NAEAPAXRXM03V.nadsusea.nads.navy.mil> References: <98A5EBA39B71F24790656277413FB27E0D9DA395@NAEAPAXRXM03V.nadsusea.nads.navy.mil> Message-ID: Ken, > I am trying to recover the file names of the .vtu files that are contained within a .pvd XML file that I am reading in. I am only able to see the timestep data and file name of the PVD itself. Does anyone know where the file= attribute located in the .pvd file stored within Paraview? The files are placed in the path indicated by the 'file" attribute relative to the location of the pvd file itself. > Ultimately I am trying to read in a series of .pvtr files (pointing to vtr files) and export the data as a series of Exodus files with one .e file per timestep. Trying to generate one big .e file directly generates an error due to what appears to be a format error (I assume from the lack of timestep associated the core data beyond the pvd file). Any advice would be appreciated. You should try using the Python scripting API to open the files and write them out. Something like this could work: for i in range(100): r = OpenDataFile("foo_%s..." % i) UpdatePipeline(r) SaveData("foo_%s.e" % i, r) Delete(r) Utkarsh From utkarsh.ayachit at kitware.com Wed Feb 25 09:26:36 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 25 Feb 2015 09:26:36 -0500 Subject: [Paraview] Smooth seams in SILO files In-Reply-To: References: Message-ID: Try applying "Merge Blocks" and before applying the CellDatatoPointData. ParaView indeed treats each block separately. When you do "Merge Blocks", it will merge all the blocks into a single unstructured grid. This will make it possible to get a more reliable CellDataToPointData conversion across the block seams and hence avoid the seams on contouring. Utkarsh On Tue, Feb 24, 2015 at 6:13 PM, David Ortley wrote: > Hello all, > > We have a CFD code that generates silo files using the silo library. For > each dump in the simulation, there are multiple files per dump (one file per > processor) and a single master file. > > When we use Visit to visualize a contour, the contours look good. When > using Paraview (any version), there exist obvious seams at the file > boundaries. To visualize in Paraview, we use the 'CellDatatoPointData' > filter followed by the 'Contour' filter. > > I'm currently trying to track down if either Visit is magically healing over > a bug in our implementation, or if the problem lies with Paraview > somehow...or with how I'm trying to generate the contour (via the > 'CellDatatoPointData' filter.) > > > It almost looks like Paraview is treating the edge of each file as if it > were an open boundary regardless of whether it is buttressed up against > another file. > > Thanks for any help in this. > > -David Ortley > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Feb 25 09:27:42 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 25 Feb 2015 09:27:42 -0500 Subject: [Paraview] [EXTERNAL] Fwd: Volume rendering with RGBA data In-Reply-To: References: Message-ID: As a side note, this is indeed going to be supported by the upcoming changes to upgrade VTK's rendering pipeline to use OpenGL 2 features (Aashish, please correct me if I am wrong). Utkarsh On Mon, Feb 23, 2015 at 4:28 PM, Scott, W Alan wrote: > Ruq, > > Volume rendering vectors appears to have multiple bugs. And you are correct > ? volume rendering a non map scalar vector appears to turn on map scalars. > > I wrote up bugs. > > > > http://www.paraview.org/Bug/view.php?id=15340 > > http://www.paraview.org/Bug/view.php?id=15339 > > > > I marked a duplicate, 14242, as targeted for PV 4.4. > > > > > > Alan > > > > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Xu, > Ruqing > Sent: Sunday, February 22, 2015 4:24 PM > To: paraview at paraview.org > Subject: [EXTERNAL] [Paraview] Fwd: Volume rendering with RGBA data > > > > Hello, > > > > I'm displaying my simple 3D data set on a structured grid. With a > 4-component unsigned integer vector on each point, and after turning off the > "map scalar" option in the displays, I have been able to present my data > with the given RGBA values in the "surface" or "points" mode. In the > "volume" mode, however, this breaks down and the colors & opacity are still > mapped from the individual components of the 4-vectors as scalars. > > Am I missing anything? Or is this a known issue? I'm using ParaView 4.3.1, > Thanks. > > -Ruq > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 ken.nahshon at navy.mil Wed Feb 25 09:30:07 2015 From: ken.nahshon at navy.mil (Nahshon, Ken Dr. CIV NSWCCD West Bethesda MD, 664) Date: Wed, 25 Feb 2015 14:30:07 +0000 Subject: [Paraview] Getting File Names from PVD File In-Reply-To: References: <98A5EBA39B71F24790656277413FB27E0D9DA395@NAEAPAXRXM03V.nadsusea.nads.navy.mil> Message-ID: <98A5EBA39B71F24790656277413FB27E0D9F3B5E@NAEAPAXRXM03V.nadsusea.nads.navy.mil> Utkarsh, Thank you for your reply. I realize I can open the .pvtr or .pvt files directly and parse the time data from the .pvd file but that is a round-about way of doing things. What I am looking for is how to return, within the Python Paraview shell, the 'file' attribute of the .pvd file I have open. Unfortunately, I can only locate the attribute containing the filename of the .pvd file itself. Best, Ken -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Wednesday, February 25, 2015 9:23 AM To: Nahshon, Ken Dr. CIV NSWCCD West Bethesda MD, 664 Cc: paraview at paraview.org Subject: Re: [Paraview] Getting File Names from PVD File Ken, > I am trying to recover the file names of the .vtu files that are contained within a .pvd XML file that I am reading in. I am only able to see the timestep data and file name of the PVD itself. Does anyone know where the file= attribute located in the .pvd file stored within Paraview? The files are placed in the path indicated by the 'file" attribute relative to the location of the pvd file itself. > Ultimately I am trying to read in a series of .pvtr files (pointing to vtr files) and export the data as a series of Exodus files with one .e file per timestep. Trying to generate one big .e file directly generates an error due to what appears to be a format error (I assume from the lack of timestep associated the core data beyond the pvd file). Any advice would be appreciated. You should try using the Python scripting API to open the files and write them out. Something like this could work: for i in range(100): r = OpenDataFile("foo_%s..." % i) UpdatePipeline(r) SaveData("foo_%s.e" % i, r) Delete(r) Utkarsh -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5602 bytes Desc: not available URL: From djortley at gmail.com Wed Feb 25 10:51:30 2015 From: djortley at gmail.com (David Ortley) Date: Wed, 25 Feb 2015 08:51:30 -0700 Subject: [Paraview] Smooth seams in SILO files In-Reply-To: References: Message-ID: Utkarsh: Thanks. That did the trick. I had to add a 'Threshold' filter in the mix to remove the ghost cells, which were confusing the 'Merge Blocks' filter. I've actually been staring at those boundary lines for over a year and a half and I've very glad to finally have them gone Again, thank you very much. -David Ortley On Wed, Feb 25, 2015 at 7:26 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Try applying "Merge Blocks" and before applying the > CellDatatoPointData. ParaView indeed treats each block separately. > When you do "Merge Blocks", it will merge all the blocks into a single > unstructured grid. This will make it possible to get a more reliable > CellDataToPointData conversion across the block seams and hence avoid > the seams on contouring. > > Utkarsh > > On Tue, Feb 24, 2015 at 6:13 PM, David Ortley wrote: > > Hello all, > > > > We have a CFD code that generates silo files using the silo library. For > > each dump in the simulation, there are multiple files per dump (one file > per > > processor) and a single master file. > > > > When we use Visit to visualize a contour, the contours look good. When > > using Paraview (any version), there exist obvious seams at the file > > boundaries. To visualize in Paraview, we use the 'CellDatatoPointData' > > filter followed by the 'Contour' filter. > > > > I'm currently trying to track down if either Visit is magically healing > over > > a bug in our implementation, or if the problem lies with Paraview > > somehow...or with how I'm trying to generate the contour (via the > > 'CellDatatoPointData' filter.) > > > > > > It almost looks like Paraview is treating the edge of each file as if it > > were an open boundary regardless of whether it is buttressed up against > > another file. > > > > Thanks for any help in this. > > > > -David Ortley > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > 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 anton.piccardo-selg at stfc.ac.uk Wed Feb 25 11:17:10 2015 From: anton.piccardo-selg at stfc.ac.uk (anton.piccardo-selg at stfc.ac.uk) Date: Wed, 25 Feb 2015 16:17:10 +0000 Subject: [Paraview] How to force an update of the time information? Message-ID: <593AFCE559F11049B8F268BE84170A0DC13151@EXCHMBX03.fed.cclrc.ac.uk> Hi, I am currently working on a customization of ParaView (PV 3.98.1) which uses its animation capabilities. Hence I need to set TIME_STEPS in the requestInformation method of my source plugin. It works quite nicely in fact. An issue occurs, when I create a second instance of the same type of source. The second source has different time information compared to the original source. I would like to use this second time information. But it seems that the time information is not updated when the requestInformation method is called for the new source. In the requestData method I retrieve the time information via time =outInfo->Get(vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()); This returns the old time information. How can I enforce an update in ParaView? I believe something similar was discussed in: http://public.kitware.com/pipermail/paraview/2010-November/019492.html. But unfortunately the answer seems to be cut off. Any ideas or help is very much appreciated. Many thanks and best regards, Anton From louie.cardone-noott at linacre.ox.ac.uk Wed Feb 25 11:06:21 2015 From: louie.cardone-noott at linacre.ox.ac.uk (Louie Cardone-Noott) Date: Wed, 25 Feb 2015 16:06:21 +0000 Subject: [Paraview] VTK parallel unstructured grid and halo elements In-Reply-To: <1a180a02-4f10-4dff-91fe-a7a9ce1918ed@HUB06.ad.oak.ox.ac.uk> References: <1a180a02-4f10-4dff-91fe-a7a9ce1918ed@HUB06.ad.oak.ox.ac.uk> Message-ID: Hi again list, Inspired by David Ortley's recent success (see "Smooth seams in SILO files") I wonder if perhaps the way I'm doing it is correct, but Paraview is incorrectly considering the values at hidden nodes when calculating data ranges. Essentially my "option 3" (writing a vtkGhostLevels array) appears to work as it should, and the "seams" are hidden in my parallel data. But, if I then Extract Surface and look at the Data Arrays -> Data Ranges I see values which can only be from non-surface nodes. I suspect they are probably from nodes on the (hidden) interior surfaces. This is obviously a bug. I could probably provide a minimal example if useful. Best wishes, Louie On 17 January 2015 at 16:26, Louie Cardone-Noott < louie.cardone-noott at linacre.ox.ac.uk> wrote: > Hi Paraview list, > > I use a finite element code that generates VTK output, but I'm having > trouble dealing with halo (ghost) nodes/elements correctly. > > We currently partition meshes node-wise, and each process writes all its > owned nodes and one level of halo nodes to a chunk. Once all the chunks are > loaded there is a "double layer" of internal boundaries between processes. > I'd really like to be able to use the Extract Surface filter correctly but > as you would expect it also finds all the internal surfaces. From searching > I've tried: > > * Clean To Grid, but this removes both sides of the double layer leaving > unsightly gaps. > * Writing a vtkGhostPoints array (on nodes) but this seems not to be used > by this filter (or Paraview at all?) > * Writing a vtkGhostLevels array (on elements). This correctly hides all > the ghost elements at the internal boundaries (great!) but still doesn't > let me do everything I want to. For example, the extracted surface looks > right, but the array limits still seem to be based on the max/min of the > external AND internal surfaces, so I suspect the internal ones are just > "hidden from view". > > What's the right way to deal with this? > > Thanks in advance. > > Louie > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 berk.geveci at kitware.com Wed Feb 25 13:27:59 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 25 Feb 2015 13:27:59 -0500 Subject: [Paraview] Paraview/Python script speed extracting data In-Reply-To: <226974D5-0C60-4679-B719-DC14F378F724@Imperial.ac.uk> References: <226974D5-0C60-4679-B719-DC14F378F724@Imperial.ac.uk> Message-ID: Hi Christian, Did you identify where the performance bottleneck occurs? Does it perform well if you take out the writing or Fetch? Best, -berk On Fri, Feb 20, 2015 at 8:05 AM, Thomas, Christian wrote: > Hi > > I'm writing a python script that uses several paraview filters. I then > extract data from the final filter for further analysis in python. However, > I'm having a problem with the speed of the data extraction (can take > several minutes). I have tried writing to a file (createwriter) and then > reading the file. I have also tried servermanager.Fetch() and GetPoints? > Although I am able to get data with both methods, they are both very slow. > I was wondering if there was anything obvious in my paraview/python script > that was slowing the process or if anyone has a suggestion at how I may > speed things up. > (I realise this could just be down to the size of my initial input, for > small data files Mesh - 15MB, solution - 50MB). > > The script is below. Any suggestions would be greatly appreciated. > > Regards > Christian > > > > TBR = TAUMeshReader( FileName=Dir+'Mesh' ) > TBR.SurfaceMeshOnly = 0 > TBR.SolutionFileName = Dir+'solution' > MB = MergeBlocks(Input = TBR) > T1 = Transform(Input = MB) > T1.Transform.Rotate = [-float(Rot/2.0), 0.0, Sweep] > ISO = IsoVolume(Input = T1) > ISO.ThresholdRange = [MIN_Tot_Pre, BLE_Tot_Pre] > ISO.InputScalars = ['POINTS','total_pressure'] > SL = Slice(Input = T1) > SL.SliceType="Plane" > SL.SliceOffsetValues = n > SL.SliceType.Origin = Inboard > SL.SliceType.Normal = Normal > Con = Contour(Input = SL) > Con.PointMergeMethod = "Uniform Binning" > Con.ContourBy = ['POINTS', 'total_pressure'] > Con.Isosurfaces = [BLE_Tot_Pre] > Pass = PassArrays(Con) > Pass.PointDataArrays = ['wall_distance'] > h=CreateWriter(Dir+'Edge.csv',Pass) > h.FieldAssociation = "Points" > h.Precision = 15 > h.UpdatePipeline() > > ?.read Edge.csv file for further analysis > > > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 berk.geveci at kitware.com Wed Feb 25 13:31:05 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 25 Feb 2015 13:31:05 -0500 Subject: [Paraview] VTK parallel unstructured grid and halo elements In-Reply-To: References: <1a180a02-4f10-4dff-91fe-a7a9ce1918ed@HUB06.ad.oak.ox.ac.uk> Message-ID: Hi Louie, Ghost/halo nodes are considered valid (but duplicated) so they are taken into account when calculating ranges, statistics etc. What you need is to mark them as invalid, it sounds like? We are making slow progress towards having an infrastructure that supports this but currently it is only partially support for structured grids and AMR meshes and a subset of filters. Best, -berk On Wed, Feb 25, 2015 at 11:06 AM, Louie Cardone-Noott < louie.cardone-noott at linacre.ox.ac.uk> wrote: > Hi again list, > > Inspired by David Ortley's recent success (see "Smooth seams in SILO > files") I wonder if perhaps the way I'm doing it is correct, but Paraview > is incorrectly considering the values at hidden nodes when calculating data > ranges. > > Essentially my "option 3" (writing a vtkGhostLevels array) appears to work > as it should, and the "seams" are hidden in my parallel data. But, if I > then Extract Surface and look at the Data Arrays -> Data Ranges I see > values which can only be from non-surface nodes. I suspect they are > probably from nodes on the (hidden) interior surfaces. This is obviously a > bug. > > I could probably provide a minimal example if useful. > > Best wishes, > Louie > > > On 17 January 2015 at 16:26, Louie Cardone-Noott < > louie.cardone-noott at linacre.ox.ac.uk> wrote: > >> Hi Paraview list, >> >> I use a finite element code that generates VTK output, but I'm having >> trouble dealing with halo (ghost) nodes/elements correctly. >> >> We currently partition meshes node-wise, and each process writes all its >> owned nodes and one level of halo nodes to a chunk. Once all the chunks are >> loaded there is a "double layer" of internal boundaries between processes. >> I'd really like to be able to use the Extract Surface filter correctly but >> as you would expect it also finds all the internal surfaces. From searching >> I've tried: >> >> * Clean To Grid, but this removes both sides of the double layer leaving >> unsightly gaps. >> * Writing a vtkGhostPoints array (on nodes) but this seems not to be used >> by this filter (or Paraview at all?) >> * Writing a vtkGhostLevels array (on elements). This correctly hides all >> the ghost elements at the internal boundaries (great!) but still doesn't >> let me do everything I want to. For example, the extracted surface looks >> right, but the array limits still seem to be based on the max/min of the >> external AND internal surfaces, so I suspect the internal ones are just >> "hidden from view". >> >> What's the right way to deal with this? >> >> Thanks in advance. >> >> Louie >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 jeffrey.c.becker at nasa.gov Wed Feb 25 14:01:21 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 25 Feb 2015 11:01:21 -0800 Subject: [Paraview] pvserver running out of memory Message-ID: <54EE1C01.3020303@nasa.gov> Hi. I am trying to run ParaView 4.3.1 in client/server mode. After the client connects, I try to open a SILO data file (I built paraview with the SILO reader option). Then, I can see pvserver growing in memory use to 91% (of 48G!) using top. At that point the job scheduler kills my job. Anyone know what might be causing this memory consumption? BTW, if I try to open the same SILO file with ParaView 4.3.1 running standalone on my desktop, it works fine. Thanks. -jeff From arctica1963 at gmail.com Wed Feb 25 14:35:12 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Wed, 25 Feb 2015 19:35:12 +0000 Subject: [Paraview] GMT grids to 3D surface In-Reply-To: References: Message-ID: Thanks Utkarsh, that solved the issue fine :) Cheers Lester On 25 February 2015 at 14:17, Utkarsh Ayachit wrote: > Have you tried the "Warp By Scalar" filter? The filter allows you to > select the scalar to warp with as well as the normal along which to > warp the mesh. > > Utkarsh > > On Tue, Feb 24, 2015 at 5:37 AM, Lester Anderson > wrote: > > Hello, > > > > I can see how to load a GMT (netCDF) grid into Paraview but cannot seem > to > > see how to translate it into an elevation surface. > > > > The data is a gridded surface of a subducting slab geometry, with X, Y as > > longitude and latitude respectively, and Z as the depth range 0 to -700 > km. > > Here the Z value represents the scalar depth. > > > > Do I need to pre-process the data prior to loading into Paraview? When > > loaded the Z-dimension is 1 so it is still essentially a 2D surface. > Loading > > point data (eg earthquake solutions) is fine as I can edit the data > table, > > but not sure what else I need to get a slab surface in correctly: for > > plotting the Z-dimension would need to have an extent of 0 to 699 > (d=700). > > > > Be good to know how I can solve this simply. > > > > Cheers > > > > Lester > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Feb 25 15:01:49 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 25 Feb 2015 15:01:49 -0500 Subject: [Paraview] pvserver running out of memory In-Reply-To: <54EE1C01.3020303@nasa.gov> References: <54EE1C01.3020303@nasa.gov> Message-ID: Odd...are you running a parallel server or a single processes pvserver? What is the remote rendering threshold set to i.e. are you doing remote rendering or local rendering (see [1] is you're unsure how to determine that)?. [1] http://www.kitware.com/blog/home/post/686 On Wed, Feb 25, 2015 at 2:01 PM, Jeff Becker wrote: > Hi. I am trying to run ParaView 4.3.1 in client/server mode. After the > client connects, I try to open a SILO data file (I built paraview with the > SILO reader option). Then, I can see pvserver growing in memory use to 91% > (of 48G!) using top. At that point the job scheduler kills my job. Anyone > know what might be causing this memory consumption? > > BTW, if I try to open the same SILO file with ParaView 4.3.1 running > standalone on my desktop, it works fine. > > Thanks. > > -jeff > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 bloring at lbl.gov Wed Feb 25 15:22:07 2015 From: bloring at lbl.gov (Burlen Loring) Date: Wed, 25 Feb 2015 12:22:07 -0800 Subject: [Paraview] Minimum system requirement for PV 4.3 volume rendering? In-Reply-To: References: Message-ID: <54EE2EEF.4050102@lbl.gov> Hi Ruq, I'm not sure why it works in 4.2 and not 4.3. I assume someone else reading this who knows about the recent changes could comment. The error message shows some missing open gl extensions. Are you sure you have the latest driver installed? GL_ARB_multitexture is not typically an issue, unless you are using the default MS driver. Also are you sure the error messages are the same on both systems? If not, it would be helpful to see all the messages on both systems. Note: the AMD drivers have a bug that prevents projected tetrahedra from working. This should be disabled on the system with the AMD card. In general when you have issues with one volume rendering method you could work around it by using a different one. In the "properties panel" under the "display" group there are some controls relating to the volume renderer. One labeled "select mapper" lets you chose different algorithms. For instance try to change it to "Bunyk Ray Cast". In general the "ray cast" options are slower but more dependable. Burlen On 02/24/2015 11:18 PM, Xu, Ruqing wrote: > Hello, > > I've installed PV 4.3 on a few PCs, all of them running Win 7 64-bit. > What I've found is that volume rendering, curiously, works on some of > them and fails on others. The error messages I got look like this: > ========================================= > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\VolumeOpenGL\vtkOpenGLProjectedTetrahedraMapper.cxx, > line 188 > > vtkOpenGLProjectedTetrahedraMapper (0000000013AB80B0): The required > extensions are not supported. > > > > Warning: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLExtensionManager.cxx, > line 781 > > vtkOpenGLExtensionManager (0000000013567D60): Attempting to load > GL_ARB_multitexture, which is not supported. > > > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLExtensionManager.cxx, > line 787 > > vtkOpenGLExtensionManager (0000000013567D60): Extension > GL_ARB_multitexture could not be loaded. > > =============================================== > > > This seems to only happen to the relatively old PCs (~ 4 or 5 years > old). For example one of them has graphics card of ATI Radeon HD 3450 > (Microsoft Corporation WDDM 1.1), driver version 7.14.10.0018; another > laptop has Intel HD graphics, driver version 8.15.10.2559. - I'm > wondering if these are considered insufficient for volume rendering to > work with PV 4.3. > > More curiously, volume rendering seems to run OK with PV 4.2 on these > machines. > > Thanks, > > -Ruq > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > 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 jeffrey.c.becker at nasa.gov Wed Feb 25 16:47:55 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 25 Feb 2015 13:47:55 -0800 Subject: [Paraview] pvserver running out of memory In-Reply-To: References: <54EE1C01.3020303@nasa.gov> Message-ID: <54EE430B.6010101@nasa.gov> On 02/25/2015 12:01 PM, Utkarsh Ayachit wrote: > Odd...are you running a parallel server or a single processes > pvserver? What is the remote rendering threshold set to i.e. are you > doing remote rendering or local rendering (see [1] is you're unsure > how to determine that)?. Here's my command on the server: (I want a baseline for a multi-server parallel back-end) $ mpirun -np 1 /usr/bin/env DISPLAY=pfe20:31.0 ./mylocal/bin/pvserver --client-host=pfe20 --use-offscreen-rendering I didn't touch the default remote rendering setting in the client. > > > [1] http://www.kitware.com/blog/home/post/686 > > On Wed, Feb 25, 2015 at 2:01 PM, Jeff Becker wrote: >> Hi. I am trying to run ParaView 4.3.1 in client/server mode. After the >> client connects, I try to open a SILO data file (I built paraview with the >> SILO reader option). Then, I can see pvserver growing in memory use to 91% >> (of 48G!) using top. At that point the job scheduler kills my job. Anyone >> know what might be causing this memory consumption? >> >> BTW, if I try to open the same SILO file with ParaView 4.3.1 running >> standalone on my desktop, it works fine. >> >> Thanks. >> >> -jeff >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 arctica1963 at gmail.com Wed Feb 25 17:39:56 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Wed, 25 Feb 2015 22:39:56 +0000 Subject: [Paraview] GMT grids to 3D surface In-Reply-To: References: Message-ID: Hello, I rechecked the GMT grids and the Warp by Scalar only seems to work on some data (if the reference frame is cartesian), but not with longitude-latitude grids. I checked both the classic GMT netCDF format (cf) and the new format (nf) and although there is no problem loading the data, the warp by scalar is greyed out. I generated a topo grid from Sandwell & Smith (area = 10/10/-10/10) at 1 arc minute cell size and it loads as a structured (curvilinear) grid. The Z values are correct for the bathymetry and topography. In this case, the surface is curved as expected for a section on the sphere, so maybe that is why the warp by scalar is not available? The file I got to work before was a simple flat surface in cartesian units. This grid was defined as an image (uniform rectilinear grid) before the warp was applied. Still not sure about this one. Lester On 25 February 2015 at 19:35, Lester Anderson wrote: > Thanks Utkarsh, that solved the issue fine :) > > Cheers > Lester > > On 25 February 2015 at 14:17, Utkarsh Ayachit > wrote: > >> Have you tried the "Warp By Scalar" filter? The filter allows you to >> select the scalar to warp with as well as the normal along which to >> warp the mesh. >> >> Utkarsh >> >> On Tue, Feb 24, 2015 at 5:37 AM, Lester Anderson >> wrote: >> > Hello, >> > >> > I can see how to load a GMT (netCDF) grid into Paraview but cannot seem >> to >> > see how to translate it into an elevation surface. >> > >> > The data is a gridded surface of a subducting slab geometry, with X, Y >> as >> > longitude and latitude respectively, and Z as the depth range 0 to -700 >> km. >> > Here the Z value represents the scalar depth. >> > >> > Do I need to pre-process the data prior to loading into Paraview? When >> > loaded the Z-dimension is 1 so it is still essentially a 2D surface. >> Loading >> > point data (eg earthquake solutions) is fine as I can edit the data >> table, >> > but not sure what else I need to get a slab surface in correctly: for >> > plotting the Z-dimension would need to have an extent of 0 to 699 >> (d=700). >> > >> > Be good to know how I can solve this simply. >> > >> > Cheers >> > >> > Lester >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > 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 arctica1963 at gmail.com Wed Feb 25 17:57:34 2015 From: arctica1963 at gmail.com (Lester Anderson) Date: Wed, 25 Feb 2015 22:57:34 +0000 Subject: [Paraview] GMT grids to 3D surface In-Reply-To: References: Message-ID: Reloading the GMT grid and not selecting spherical coordinates will "trick" it to work the warp, but recognises the dimensions as lat-long. In other words, applying a flat earth model works! So I guess the question that arises is, how do you do warping (exagerated elevations) on a sphere? Cheers Lester On 25 February 2015 at 22:39, Lester Anderson wrote: > Hello, > > I rechecked the GMT grids and the Warp by Scalar only seems to work on > some data (if the reference frame is cartesian), but not with > longitude-latitude grids. I checked both the classic GMT netCDF format (cf) > and the new format (nf) and although there is no problem loading the data, > the warp by scalar is greyed out. > > I generated a topo grid from Sandwell & Smith (area = 10/10/-10/10) at 1 > arc minute cell size and it loads as a structured (curvilinear) grid. The Z > values are correct for the bathymetry and topography. In this case, the > surface is curved as expected for a section on the sphere, so maybe that is > why the warp by scalar is not available? > > The file I got to work before was a simple flat surface in cartesian > units. This grid was defined as an image (uniform rectilinear grid) before > the warp was applied. > > Still not sure about this one. > > Lester > > On 25 February 2015 at 19:35, Lester Anderson > wrote: > >> Thanks Utkarsh, that solved the issue fine :) >> >> Cheers >> Lester >> >> On 25 February 2015 at 14:17, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> Have you tried the "Warp By Scalar" filter? The filter allows you to >>> select the scalar to warp with as well as the normal along which to >>> warp the mesh. >>> >>> Utkarsh >>> >>> On Tue, Feb 24, 2015 at 5:37 AM, Lester Anderson >>> wrote: >>> > Hello, >>> > >>> > I can see how to load a GMT (netCDF) grid into Paraview but cannot >>> seem to >>> > see how to translate it into an elevation surface. >>> > >>> > The data is a gridded surface of a subducting slab geometry, with X, Y >>> as >>> > longitude and latitude respectively, and Z as the depth range 0 to >>> -700 km. >>> > Here the Z value represents the scalar depth. >>> > >>> > Do I need to pre-process the data prior to loading into Paraview? When >>> > loaded the Z-dimension is 1 so it is still essentially a 2D surface. >>> Loading >>> > point data (eg earthquake solutions) is fine as I can edit the data >>> table, >>> > but not sure what else I need to get a slab surface in correctly: for >>> > plotting the Z-dimension would need to have an extent of 0 to 699 >>> (d=700). >>> > >>> > Be good to know how I can solve this simply. >>> > >>> > Cheers >>> > >>> > Lester >>> > >>> > _______________________________________________ >>> > Powered by www.kitware.com >>> > >>> > Visit other Kitware open-source projects at >>> > http://www.kitware.com/opensource/opensource.html >>> > >>> > Please keep messages on-topic and check the ParaView Wiki at: >>> > http://paraview.org/Wiki/ParaView >>> > >>> > 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 jeffrey.c.becker at nasa.gov Wed Feb 25 18:32:24 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 25 Feb 2015 15:32:24 -0800 Subject: [Paraview] pvserver running out of memory In-Reply-To: <54EE430B.6010101@nasa.gov> References: <54EE1C01.3020303@nasa.gov> <54EE430B.6010101@nasa.gov> Message-ID: <54EE5B88.3090000@nasa.gov> On 02/25/2015 01:47 PM, Jeff Becker wrote: > On 02/25/2015 12:01 PM, Utkarsh Ayachit wrote: >> Odd...are you running a parallel server or a single processes >> pvserver? What is the remote rendering threshold set to i.e. are you >> doing remote rendering or local rendering (see [1] is you're unsure >> how to determine that)?. > > Here's my command on the server: (I want a baseline for a multi-server > parallel back-end) > > $ mpirun -np 1 /usr/bin/env DISPLAY=pfe20:31.0 ./mylocal/bin/pvserver > --client-host=pfe20 --use-offscreen-rendering > > I didn't touch the default remote rendering setting in the client. The threshold is zero. I was able to remote render the disk_out_ref.ex2 tutorial example just fine. Perhaps there's some issue with the SILO reader used in pvserver? Thanks. -jeff >> >> >> [1] http://www.kitware.com/blog/home/post/686 >> >> On Wed, Feb 25, 2015 at 2:01 PM, Jeff Becker >> wrote: >>> Hi. I am trying to run ParaView 4.3.1 in client/server mode. After the >>> client connects, I try to open a SILO data file (I built paraview >>> with the >>> SILO reader option). Then, I can see pvserver growing in memory use >>> to 91% >>> (of 48G!) using top. At that point the job scheduler kills my job. >>> Anyone >>> know what might be causing this memory consumption? >>> >>> BTW, if I try to open the same SILO file with ParaView 4.3.1 running >>> standalone on my desktop, it works fine. >>> >>> Thanks. >>> >>> -jeff >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> 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 kit.chambers.kc at gmail.com Thu Feb 26 03:43:30 2015 From: kit.chambers.kc at gmail.com (Kit Chambers) Date: Thu, 26 Feb 2015 08:43:30 +0000 Subject: [Paraview] Using custom data types in Paraview pipeline Message-ID: <54EEDCB2.5070204@googlemail.com> Hi Everyone, I have a custom data type that does not fit that nicely into any of the standard VTK data types. My thinking is the best way to handle it would be to create a plugin that has a derived data type of the "nearest" VTK data object and possibly some associated filters+ representations. Is this possible and or a good idea? Does anyone have experience or examples of this? Cheers Kit From tdallapiazza at digger.ch Thu Feb 26 04:18:16 2015 From: tdallapiazza at digger.ch (Dalla Piazza Thomas) Date: Thu, 26 Feb 2015 10:18:16 +0100 Subject: [Paraview] Plot calculator result over time Message-ID: <54EEE4D8.5080502@digger.ch> Hi all, I have a simple problem that is easy to reproduce. My objective is to produce a plot of average temperature of a volume over time (simple heat diffusion case). I'll take a straight forward example based on laplacianfoam OpenFOAM case. 1) Run the case 2) Run Paraview and load the data for internalMesh region 3) select filter "Integrate variables" that produce integrated temperature over the entire volume (Tv in the following) and integrated volume over volume being the total region volume (Volume in the following) 4) select filter "Calculator" 5) based on cell data, compute averaged temperature of the volume Tv/Volume (both results of integration filter) 6) select calculator result and choose filter "Plot selection over time" Problem: Up to the calculator, everything looks fine. Integrated volume is not changing over time, itegrated temperature is growing normally as well as averaged temperature... But in the spreadsheet view of "Plot selection over time", only the initial value at T=0 is right, for the next time steps, volume is changing like randomly and averaged temperature is completely messed up... Is it a bug of "PlotSelectionOverTime" filter or did I made a mistake in my procedure? Thanks for any help, Thomas -- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TDP_030314.png Type: image/png Size: 12331 bytes Desc: not available URL: From c.thomas at imperial.ac.uk Thu Feb 26 07:04:44 2015 From: c.thomas at imperial.ac.uk (Thomas, Christian) Date: Thu, 26 Feb 2015 12:04:44 +0000 Subject: [Paraview] Fwd: Paraview/Python script speed extracting data References: <226974D5-0C60-4679-B719-DC14F378F724@Imperial.ac.uk> Message-ID: <6C8BFABD-3338-4E43-BA9E-73592ABC9321@Imperial.ac.uk> Hi all, I have sorted out my bottleneck/time processing speed issue. I'm sure the following method\script is well known to many python/paraview users. I had to include delete (source_name) and del source_ name, once each source was no longer needed. This was particularly useful when running loops around several filters. Example: delete(T1), del T1 I also included the clip filter several times to reduce the size of the mesh\data file. C1 = Clip(Input = T1) C1.ClipType = "Plane" C1.ClipType.Origin = [0.0, 0.0, ZMin[0]] C1.ClipType.Normal = [0.0, 0.0, 1.0] Regards Christian Dr. Christian Thomas Postdoctoral Research Associate Department of Mathematics Room 737, Huxley Building 180, Queen?s Gate Imperial College London SW7 2AZ c.thomas at imperial.ac.uk Begin forwarded message: Subject: Paraview/Python script speed extracting data Date: 20 February 2015 13:05:48 GMT To: > Hi I'm writing a python script that uses several paraview filters. I then extract data from the final filter for further analysis in python. However, I'm having a problem with the speed of the data extraction (can take several minutes). I have tried writing to a file (createwriter) and then reading the file. I have also tried servermanager.Fetch() and GetPoints? Although I am able to get data with both methods, they are both very slow. I was wondering if there was anything obvious in my paraview/python script that was slowing the process or if anyone has a suggestion at how I may speed things up. (I realise this could just be down to the size of my initial input, for small data files Mesh - 15MB, solution - 50MB). The script is below. Any suggestions would be greatly appreciated. Regards Christian TBR = TAUMeshReader( FileName=Dir+'Mesh' ) TBR.SurfaceMeshOnly = 0 TBR.SolutionFileName = Dir+'solution' MB = MergeBlocks(Input = TBR) T1 = Transform(Input = MB) T1.Transform.Rotate = [-float(Rot/2.0), 0.0, Sweep] ISO = IsoVolume(Input = T1) ISO.ThresholdRange = [MIN_Tot_Pre, BLE_Tot_Pre] ISO.InputScalars = ['POINTS','total_pressure'] SL = Slice(Input = T1) SL.SliceType="Plane" SL.SliceOffsetValues = n SL.SliceType.Origin = Inboard SL.SliceType.Normal = Normal Con = Contour(Input = SL) Con.PointMergeMethod = "Uniform Binning" Con.ContourBy = ['POINTS', 'total_pressure'] Con.Isosurfaces = [BLE_Tot_Pre] Pass = PassArrays(Con) Pass.PointDataArrays = ['wall_distance'] h=CreateWriter(Dir+'Edge.csv',Pass) h.FieldAssociation = "Points" h.Precision = 15 h.UpdatePipeline() ?.read Edge.csv file for further analysis -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Feb 26 09:04:31 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 26 Feb 2015 09:04:31 -0500 Subject: [Paraview] pvserver running out of memory In-Reply-To: <54EE5B88.3090000@nasa.gov> References: <54EE1C01.3020303@nasa.gov> <54EE430B.6010101@nasa.gov> <54EE5B88.3090000@nasa.gov> Message-ID: > The threshold is zero. I was able to remote render the disk_out_ref.ex2 > tutorial example just fine. Perhaps there's some issue with the SILO reader > used in pvserver? Thanks. Possible, but you said it works fine when you load locally on the client and not in client-server mode. But given that this is just a single MPI rank for pvserver, I wonder what's different. Try not using "--use-offscreen-rendering" argument. Does that make any difference? Utkarsh From asche.j at googlemail.com Thu Feb 26 09:13:55 2015 From: asche.j at googlemail.com (Jonas Asche) Date: Thu, 26 Feb 2015 15:13:55 +0100 Subject: [Paraview] Python script - change font color Message-ID: Hello all, is there a command to change the font color for a view? I have a white Background so i can print cutplanes but the font color of my color legend is white by default. If it is easy and i just have not found the command or if it is not possible, please give me a quick answer so i can think about an other solution. Jonas -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Thu Feb 26 09:33:47 2015 From: jfavre at cscs.ch (Favre Jean) Date: Thu, 26 Feb 2015 14:33:47 +0000 Subject: [Paraview] Python script - change font color In-Reply-To: References: Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F68317D4CFD@MBX111.d.ethz.ch> #Suppose you're displaying a variable called "scalar" scalarLUT = GetColorTransferFunction('scalar') view = GetRenderView() sBAR = GetScalarBar(scalarLUT, view) sBAR.LabelColor=[0.,0.,0.] Render() ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Feb 26 11:29:25 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 26 Feb 2015 11:29:25 -0500 Subject: [Paraview] Using custom data types in Paraview pipeline In-Reply-To: <54EEDCB2.5070204@googlemail.com> References: <54EEDCB2.5070204@googlemail.com> Message-ID: Yes possible. There is some support in the code to add new data types, but the path is kind of obscure (I'ld have to look too) because the need doesn't arise all that often. The 5 main vtkDataSet types are pretty capable after all. A recent example of a new data type to be added was vtkPistonDataObject. You might grep that to see that path. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Feb 26, 2015 at 3:43 AM, Kit Chambers wrote: > Hi Everyone, > > I have a custom data type that does not fit that nicely into any of the > standard VTK data types. My thinking is the best way to handle it would be > to create a plugin that has a derived data type of the "nearest" VTK data > object and possibly some associated filters+ representations. Is this > possible and or a good idea? > > Does anyone have experience or examples of this? > > Cheers > > Kit > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 jeffrey.c.becker at nasa.gov Thu Feb 26 12:10:35 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Thu, 26 Feb 2015 09:10:35 -0800 Subject: [Paraview] pvserver running out of memory In-Reply-To: References: <54EE1C01.3020303@nasa.gov> <54EE430B.6010101@nasa.gov> <54EE5B88.3090000@nasa.gov> Message-ID: <54EF538B.2000501@nasa.gov> On 02/26/2015 06:04 AM, Utkarsh Ayachit wrote: >> The threshold is zero. I was able to remote render the disk_out_ref.ex2 >> tutorial example just fine. Perhaps there's some issue with the SILO reader >> used in pvserver? Thanks. > Possible, but you said it works fine when you load locally on the > client and not in client-server mode. But given that this is just a > single MPI rank for pvserver, I wonder what's different. Try not > using "--use-offscreen-rendering" argument. Does that make any > difference? Still runs out of memory. -jeff > > Utkarsh From nenasantos at hotmail.com Thu Feb 26 12:34:00 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Thu, 26 Feb 2015 17:34:00 +0000 Subject: [Paraview] Insert text source into view in a script In-Reply-To: <54EF538B.2000501@nasa.gov> References: <54EE1C01.3020303@nasa.gov> <54EE430B.6010101@nasa.gov> <54EE5B88.3090000@nasa.gov>, , <54EF538B.2000501@nasa.gov> Message-ID: How i can include a text source, for example a title (e.g., "my paraview script") into a view in a paraview scrip? Kind regardsMadalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Feb 26 12:41:49 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 26 Feb 2015 17:41:49 +0000 Subject: [Paraview] Insert text source into view in a script Message-ID: Try using the ParaView tracing feature (Tools -> Start Trace, Stop Trace) to learn script commands that mimic things you do in the GUI. Using ParaView 4.3.1, I started script tracing, created a text source, and stopped the tracing. I got the following commands: # create a new 'Text' text1 = Text() # Properties modified on text1 text1.Text = 'my paraview script' # get active view renderView1 = GetActiveViewOrCreate('RenderView') # uncomment following to set a specific view size # renderView1.ViewSize = [856, 589] # show data in view text1Display = Show(text1, renderView1) -Ken From: "Madalena S. Malhadas" > Date: Thursday, February 26, 2015 at 10:34 AM To: Jeff Becker >, Utkarsh Ayachit > Cc: ParaView > Subject: [EXTERNAL] [Paraview] Insert text source into view in a script How i can include a text source, for example a title (e.g., "my paraview script") into a view in a paraview scrip? Kind regards Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Thu Feb 26 12:47:39 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Thu, 26 Feb 2015 17:47:39 +0000 Subject: [Paraview] Insert text source into view in a script In-Reply-To: References: Message-ID: Ok. Thank you very much. I have a scrip that read a nc file and plot the sediments cloud from a clarifier . The script already save each image from each instant of my nc file. Now i want to include in each slide the data. So, i want that the scrip associate and write the correc data text in each slide. How can include these feature in my script? Can you help me? Kind regards Madalena From: kmorel at sandia.gov To: nenasantos at hotmail.com; jeffrey.c.becker at nasa.gov; utkarsh.ayachit at kitware.com CC: paraview at paraview.org Subject: Re: [Paraview] Insert text source into view in a script Date: Thu, 26 Feb 2015 17:41:49 +0000 Try using the ParaView tracing feature (Tools -> Start Trace, Stop Trace) to learn script commands that mimic things you do in the GUI. Using ParaView 4.3.1, I started script tracing, created a text source, and stopped the tracing. I got the following commands: # create a new 'Text' text1 = Text() # Properties modified on text1 text1.Text = 'my paraview script' # get active view renderView1 = GetActiveViewOrCreate('RenderView') # uncomment following to set a specific view size # renderView1.ViewSize = [856, 589] # show data in view text1Display = Show(text1, renderView1) -Ken From: "Madalena S. Malhadas" Date: Thursday, February 26, 2015 at 10:34 AM To: Jeff Becker , Utkarsh Ayachit Cc: ParaView Subject: [EXTERNAL] [Paraview] Insert text source into view in a script How i can include a text source, for example a title (e.g., "my paraview script") into a view in a paraview scrip? Kind regards Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Thu Feb 26 14:19:44 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Thu, 26 Feb 2015 11:19:44 -0800 Subject: [Paraview] reducing startup time on cray In-Reply-To: References: <54D50E1D.4010202@lbl.gov> <54D53358.5020209@lbl.gov> Message-ID: <54EF71D0.6010904@gmail.com> Thanks! I enabled this in my 4.3.1 installs. On 02/23/2015 06:12 AM, Utkarsh Ayachit wrote: > Burlen, > >> I'm unfamiliar with freezing python and how it would work with pvserver, >> pvbatch, or pvpython. Question: how/what do we freeze in the pvserver case? > Check this out: http://www.kitware.com/blog/home/post/517 > > Utkarsh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From matei.stroila at gmail.com Thu Feb 26 15:03:20 2015 From: matei.stroila at gmail.com (Matei Stroila) Date: Thu, 26 Feb 2015 14:03:20 -0600 Subject: [Paraview] problem wirh python shell in Paraview 4.3.1 and Python 2.7.9 on Mac OS X 10.10 Message-ID: Not sure if other people have seen this. Using Python from Homebrew on Mac OS X 10.10, got the same error on two different Macs. Python 2.7.9 (default, Dec 19 2014, 06:00:59) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin >>> from paraview.simple import * Traceback (most recent call last): File "", line 1, in File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/simple.py", line 39, in import servermanager File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", line 3184, in __initialize() File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", line 3175, in __initialize c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", line 1932, in __init__ _createModules(self.Modules) File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", line 2564, in _createModules m.filters = createModule('filters') File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", line 2626, in createModule if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' >>> Thanks for any suggestion. Matei -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Feb 26 15:10:06 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 26 Feb 2015 15:10:06 -0500 Subject: [Paraview] problem wirh python shell in Paraview 4.3.1 and Python 2.7.9 on Mac OS X 10.10 In-Reply-To: References: Message-ID: How was ParaView built? I am not sure if Homebrew Python is different from the one packaged in OsX, but binaries on paraview.org are built using OsX default Python. Also, do you have any plugins that are being auto-loaded? If you're running pvpython, try running with "-dr" argument. That will avoid loading any auto-load plugins. Does that help? Utkarsh On Thu, Feb 26, 2015 at 3:03 PM, Matei Stroila wrote: > Not sure if other people have seen this. Using Python from Homebrew on Mac > OS X 10.10, got the same error on two different Macs. > > Python 2.7.9 (default, Dec 19 2014, 06:00:59) > > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin > >>>> from paraview.simple import * > > Traceback (most recent call last): > > File "", line 1, in > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/simple.py", > line 39, in > > import servermanager > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > line 3184, in > > __initialize() > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > line 3175, in __initialize > > c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > line 1932, in __init__ > > _createModules(self.Modules) > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > line 2564, in _createModules > > m.filters = createModule('filters') > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > line 2626, in createModule > > if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ > > AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' > >>>> > > Thanks for any suggestion. > > > Matei > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 matei.stroila at gmail.com Thu Feb 26 15:53:24 2015 From: matei.stroila at gmail.com (Matei Stroila) Date: Thu, 26 Feb 2015 14:53:24 -0600 Subject: [Paraview] problem wirh python shell in Paraview 4.3.1 and Python 2.7.9 on Mac OS X 10.10 In-Reply-To: References: Message-ID: I do not have any plugin auto-loaded. Also I just tried now with the OS X default Python and I get the same errors. Could be a 10.10 issue? I built ParaView on a 10.9 machine yesterday with no issues (ParaView from git, the release branch, 4.3.1). Matei On Thu, Feb 26, 2015 at 2:10 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > How was ParaView built? I am not sure if Homebrew Python is different > from the one packaged in OsX, but binaries on paraview.org are built > using OsX default Python. > > Also, do you have any plugins that are being auto-loaded? If you're > running pvpython, try running with "-dr" argument. That will avoid > loading any auto-load plugins. Does that help? > > Utkarsh > > On Thu, Feb 26, 2015 at 3:03 PM, Matei Stroila > wrote: > > Not sure if other people have seen this. Using Python from Homebrew on > Mac > > OS X 10.10, got the same error on two different Macs. > > > > Python 2.7.9 (default, Dec 19 2014, 06:00:59) > > > > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin > > > >>>> from paraview.simple import * > > > > Traceback (most recent call last): > > > > File "", line 1, in > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/simple.py", > > line 39, in > > > > import servermanager > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > > line 3184, in > > > > __initialize() > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > > line 3175, in __initialize > > > > c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > > line 1932, in __init__ > > > > _createModules(self.Modules) > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > > line 2564, in _createModules > > > > m.filters = createModule('filters') > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > > line 2626, in createModule > > > > if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ > > > > AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' > > > >>>> > > > > Thanks for any suggestion. > > > > > > Matei > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > 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 26 16:06:38 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 26 Feb 2015 16:06:38 -0500 Subject: [Paraview] problem wirh python shell in Paraview 4.3.1 and Python 2.7.9 on Mac OS X 10.10 In-Reply-To: References: Message-ID: It is believable, let me see if I can find a 10.10 here to reproduce the problem. Another thing to try: 1. edit "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py" 2. before line 2626, add the following: print groupName, proxyName, propName Let's see which proxy this is failing for. Utkarsh On Thu, Feb 26, 2015 at 3:53 PM, Matei Stroila wrote: > I do not have any plugin auto-loaded. Also I just tried now with the OS X > default Python and I get the same errors. > Could be a 10.10 issue? I built ParaView on a 10.9 machine yesterday with no > issues (ParaView from git, the release branch, 4.3.1). > > Matei > > On Thu, Feb 26, 2015 at 2:10 PM, Utkarsh Ayachit > wrote: >> >> How was ParaView built? I am not sure if Homebrew Python is different >> from the one packaged in OsX, but binaries on paraview.org are built >> using OsX default Python. >> >> Also, do you have any plugins that are being auto-loaded? If you're >> running pvpython, try running with "-dr" argument. That will avoid >> loading any auto-load plugins. Does that help? >> >> Utkarsh >> >> On Thu, Feb 26, 2015 at 3:03 PM, Matei Stroila >> wrote: >> > Not sure if other people have seen this. Using Python from Homebrew on >> > Mac >> > OS X 10.10, got the same error on two different Macs. >> > >> > Python 2.7.9 (default, Dec 19 2014, 06:00:59) >> > >> > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin >> > >> >>>> from paraview.simple import * >> > >> > Traceback (most recent call last): >> > >> > File "", line 1, in >> > >> > File >> > >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/simple.py", >> > line 39, in >> > >> > import servermanager >> > >> > File >> > >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", >> > line 3184, in >> > >> > __initialize() >> > >> > File >> > >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", >> > line 3175, in __initialize >> > >> > c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) >> > >> > File >> > >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", >> > line 1932, in __init__ >> > >> > _createModules(self.Modules) >> > >> > File >> > >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", >> > line 2564, in _createModules >> > >> > m.filters = createModule('filters') >> > >> > File >> > >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", >> > line 2626, in createModule >> > >> > if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ >> > >> > AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' >> > >> >>>> >> > >> > Thanks for any suggestion. >> > >> > >> > Matei >> > >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > 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 matei.stroila at gmail.com Thu Feb 26 16:44:14 2015 From: matei.stroila at gmail.com (Matei Stroila) Date: Thu, 26 Feb 2015 15:44:14 -0600 Subject: [Paraview] problem wirh python shell in Paraview 4.3.1 and Python 2.7.9 on Mac OS X 10.10 In-Reply-To: References: Message-ID: Here is the output: Python 2.7.6 (default, Sep 9 2014, 15:04:36) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.39)] on darwin >>> from paraview.simple import * sources AMRGaussianPulseSource Dimension sources AMRGaussianPulseSource PulseAmplitude sources AMRGaussianPulseSource RefinementRatio sources AMRGaussianPulseSource Root Spacing sources AMRGaussianPulseSource XPulseOrigin sources AMRGaussianPulseSource XPulseWidth sources AMRGaussianPulseSource YPulseOrigin sources AMRGaussianPulseSource YPulseWidth sources AMRGaussianPulseSource ZPulseOrigin sources AMRGaussianPulseSource ZPulseWidth sources AVSucdSeriesReader FileNameInfo sources AVSucdSeriesReader FileNames sources AVSucdSeriesReader TimestepValues sources AVSucdSeriesReader CellArrayInfo sources AVSucdSeriesReader CellArrayStatus sources AVSucdSeriesReader PointArrayInfo sources AVSucdSeriesReader PointArrayStatus sources ArrowSource Invert sources ArrowSource ShaftRadius sources ArrowSource ShaftResolution sources ArrowSource TipLength sources ArrowSource TipRadius sources ArrowSource TipResolution sources Axes Origin sources Axes ScaleFactor sources Axes Symmetric sources BlockSelectionSource Blocks sources BlockSelectionSource ContainingCells sources BlockSelectionSource FieldType sources BlockSelectionSource InsideOut sources CMLMoleculeReader FileName sources CSVReader FileName sources CSVReader FileNameInfo sources CSVReader TimestepValues sources CSVReader DetectNumericColumns sources CSVReader FieldDelimiterCharacters sources CSVReader HaveHeaders sources CSVReader MergeConsecutiveDelimiters sources CSVReader UseStringDelimiter sources CompositeDataIDSelectionSource ContainingCells sources CompositeDataIDSelectionSource FieldType sources CompositeDataIDSelectionSource IDs sources CompositeDataIDSelectionSource InsideOut sources ConeSource Capping sources ConeSource Center sources ConeSource Direction sources ConeSource Height sources ConeSource Radius sources ConeSource Resolution sources CubeSource Center sources CubeSource XLength sources CubeSource YLength sources CubeSource ZLength sources CylinderSource Capping sources CylinderSource Center sources CylinderSource Height sources CylinderSource Radius sources CylinderSource Resolution sources DEMReader FileName sources DICOMReader FileName sources DICOMReaderSingle FileName sources DataObjectGenerator Program sources DiskSource CircumferentialResolution sources DiskSource InnerRadius sources DiskSource OuterRadius sources DiskSource RadialResolution sources DistributedTrivialProducer UpdateDataset sources DistributedTrivialProducer WholeExtent sources EnzoParticlesReader FileNameInfo sources EnzoParticlesReader FileNames sources EnzoParticlesReader TimestepValues sources EnzoParticlesReader FilterLocation sources EnzoParticlesReader Frequency sources EnzoParticlesReader MaxLocation sources EnzoParticlesReader MinLocation sources EnzoParticlesReader NumParticles sources EnzoParticlesReader ParticleArrayStatus sources EnzoParticlesReader ParticleType sources EnzoReader FileNameInfo sources EnzoReader FileNames sources EnzoReader TimestepValues sources EnzoReader CellArrayStatus sources EnzoReader ConvertToCGS sources EnzoReader EnableCaching sources EnzoReader Level sources EnzoReader NumBlocks sources EnzoReader NumLevels sources EnzoReader PointArrayStatus sources ExodusIIReader FileName sources ExodusIIReader FileNameInfo sources ExodusIIReader TimestepValues sources ExodusIIReader UseMetaFile sources ExodusIIReader AnimateVibrations sources ExodusIIReader ApplyDisplacements sources ExodusIIReader DisplacementMagnitude sources ExodusIIReader EdgeBlocks sources ExodusIIReader EdgeBlocksInfo sources ExodusIIReader EdgeMapArrayStatus sources ExodusIIReader EdgeMapInfo sources ExodusIIReader EdgeSetArrayStatus sources ExodusIIReader EdgeSetInfo sources ExodusIIReader EdgeSetResultArrayInfo sources ExodusIIReader EdgeSetResultArrayStatus sources ExodusIIReader EdgeVariables sources ExodusIIReader EdgeVariablesInfo sources ExodusIIReader ElementBlocks sources ExodusIIReader ElementMapArrayStatus sources ExodusIIReader ElementMapInfo sources ExodusIIReader ElementSetArrayStatus sources ExodusIIReader ElementSetInfo sources ExodusIIReader ElementSetResultArrayInfo sources ExodusIIReader ElementSetResultArrayStatus sources ExodusIIReader ElementVariables sources ExodusIIReader ElementVariablesInfo sources ExodusIIReader FaceBlocks sources ExodusIIReader FaceBlocksInfo sources ExodusIIReader FaceMapArrayStatus sources ExodusIIReader FaceMapInfo sources ExodusIIReader FaceSetArrayStatus sources ExodusIIReader FaceSetInfo sources ExodusIIReader FaceSetResultArrayInfo sources ExodusIIReader FaceSetResultArrayStatus sources ExodusIIReader FaceVariables sources ExodusIIReader FaceVariablesInfo sources ExodusIIReader FilePattern sources ExodusIIReader FilePatternInfo sources ExodusIIReader FilePrefix sources ExodusIIReader FilePrefixInfo sources ExodusIIReader FileRange sources ExodusIIReader FileRangeInfo sources ExodusIIReader GenerateGlobalElementIdArray sources ExodusIIReader GenerateGlobalNodeIdArray sources ExodusIIReader GenerateObjectIdCellArray sources ExodusIIReader GlobalVariables sources ExodusIIReader GlobalVariablesInfo sources ExodusIIReader HasModeShapes sources ExodusIIReader ModeShape sources ExodusIIReader ModeShapesRangeInfo sources ExodusIIReader NodeMapArrayStatus sources ExodusIIReader NodeMapInfo sources ExodusIIReader NodeSetArrayStatus sources ExodusIIReader NodeSetInfo sources ExodusIIReader NodeSetResultArrayInfo sources ExodusIIReader NodeSetResultArrayStatus sources ExodusIIReader PointVariables sources ExodusIIReader PointVariablesInfo sources ExodusIIReader Refresh sources ExodusIIReader SILUpdateStamp sources ExodusIIReader SideSetArrayStatus sources ExodusIIReader SideSetInfo sources ExodusIIReader SideSetResultArrayInfo sources ExodusIIReader SideSetResultArrayStatus sources ExodusIIReader XMLFileName sources ExodusIIReader XMLFileNameInfo sources ExodusRestartReader FileName sources ExodusRestartReader FileNameInfo sources ExodusRestartReader TimestepValues sources ExodusRestartReader UseMetaFile sources ExodusRestartReader AnimateVibrations sources ExodusRestartReader ApplyDisplacements sources ExodusRestartReader DisplacementMagnitude sources ExodusRestartReader EdgeBlocks sources ExodusRestartReader EdgeBlocksInfo sources ExodusRestartReader EdgeMapArrayStatus sources ExodusRestartReader EdgeMapInfo sources ExodusRestartReader EdgeSetArrayStatus sources ExodusRestartReader EdgeSetInfo sources ExodusRestartReader EdgeSetResultArrayInfo sources ExodusRestartReader EdgeSetResultArrayStatus sources ExodusRestartReader EdgeVariables sources ExodusRestartReader EdgeVariablesInfo sources ExodusRestartReader ElementBlocks sources ExodusRestartReader ElementMapArrayStatus sources ExodusRestartReader ElementMapInfo sources ExodusRestartReader ElementSetArrayStatus sources ExodusRestartReader ElementSetInfo sources ExodusRestartReader ElementSetResultArrayInfo sources ExodusRestartReader ElementSetResultArrayStatus sources ExodusRestartReader ElementVariables sources ExodusRestartReader ElementVariablesInfo sources ExodusRestartReader FaceBlocks sources ExodusRestartReader FaceBlocksInfo sources ExodusRestartReader FaceMapArrayStatus sources ExodusRestartReader FaceMapInfo sources ExodusRestartReader FaceSetArrayStatus sources ExodusRestartReader FaceSetInfo sources ExodusRestartReader FaceSetResultArrayInfo sources ExodusRestartReader FaceSetResultArrayStatus sources ExodusRestartReader FaceVariables sources ExodusRestartReader FaceVariablesInfo sources ExodusRestartReader FilePattern sources ExodusRestartReader FilePatternInfo sources ExodusRestartReader FilePrefix sources ExodusRestartReader FilePrefixInfo sources ExodusRestartReader FileRange sources ExodusRestartReader FileRangeInfo sources ExodusRestartReader GenerateGlobalElementIdArray sources ExodusRestartReader GenerateGlobalNodeIdArray sources ExodusRestartReader GenerateObjectIdCellArray sources ExodusRestartReader GlobalVariables sources ExodusRestartReader GlobalVariablesInfo sources ExodusRestartReader HasModeShapes sources ExodusRestartReader ModeShape sources ExodusRestartReader ModeShapesRangeInfo sources ExodusRestartReader NodeMapArrayStatus sources ExodusRestartReader NodeMapInfo sources ExodusRestartReader NodeSetArrayStatus sources ExodusRestartReader NodeSetInfo sources ExodusRestartReader NodeSetResultArrayInfo sources ExodusRestartReader NodeSetResultArrayStatus sources ExodusRestartReader PointVariables sources ExodusRestartReader PointVariablesInfo sources ExodusRestartReader Refresh sources ExodusRestartReader SILUpdateStamp sources ExodusRestartReader SideSetArrayStatus sources ExodusRestartReader SideSetInfo sources ExodusRestartReader SideSetResultArrayInfo sources ExodusRestartReader SideSetResultArrayStatus sources ExodusRestartReader XMLFileName sources ExodusRestartReader XMLFileNameInfo sources FLUENTReader FileName sources FLUENTReader CellArrayInfo sources FLUENTReader CellArrayStatus sources FacetReader FileName sources FlashParticlesReader FileNameInfo sources FlashParticlesReader FileNames sources FlashParticlesReader TimestepValues sources FlashParticlesReader FilterLocation sources FlashParticlesReader Frequency sources FlashParticlesReader MaxLocation sources FlashParticlesReader MinLocation sources FlashParticlesReader NumParticles sources FlashParticlesReader ParticleArrayStatus sources FlashReader FileNameInfo sources FlashReader FileNames sources FlashReader TimestepValues sources FlashReader CellArrayStatus sources FlashReader EnableCaching sources FlashReader Level sources FlashReader NumBlocks sources FlashReader NumLevels sources FlashReader PointArrayStatus sources FrustumSelectionSource ContainingCells sources FrustumSelectionSource FieldType sources FrustumSelectionSource Frustum sources FrustumSelectionSource InsideOut sources GlobalIDSelectionSource ContainingCells sources GlobalIDSelectionSource FieldType sources GlobalIDSelectionSource IDs sources GlobalIDSelectionSource InsideOut sources GlyphSource2D Center sources GlyphSource2D Filled sources GlyphSource2D GlyphType sources HierarchicalDataIDSelectionSource ContainingCells sources HierarchicalDataIDSelectionSource FieldType sources HierarchicalDataIDSelectionSource IDs sources HierarchicalDataIDSelectionSource InsideOut sources HierarchicalFractal Asymetric sources HierarchicalFractal Dimensions sources HierarchicalFractal FractalValue sources HierarchicalFractal GhostLevels sources HierarchicalFractal MaximumLevel sources HierarchicalFractal RectilinearGrids sources HierarchicalFractal TimeStep sources HierarchicalFractal TimeStepRangeInfo sources HierarchicalFractal TwoDimensional sources HyperTreeGridSource BranchFactor sources HyperTreeGridSource Descriptor sources HyperTreeGridSource Dimension sources HyperTreeGridSource GridScale sources HyperTreeGridSource GridSize sources HyperTreeGridSource MaximumLevel sources IDSelectionSource ContainingCells sources IDSelectionSource FieldType sources IDSelectionSource IDs sources IDSelectionSource InsideOut sources ImageMandelbrotSource MaximumNumberOfIterations sources ImageMandelbrotSource OriginCX sources ImageMandelbrotSource ProjectionAxes sources ImageMandelbrotSource SizeCX sources ImageMandelbrotSource SubsampleRate sources ImageMandelbrotSource WholeExtent sources ImageReader DataByteOrder sources ImageReader DataExtent sources ImageReader DataOrigin sources ImageReader DataScalarType sources ImageReader DataSpacing sources ImageReader FileDimensionality sources ImageReader FileLowerLeft sources ImageReader FilePattern sources ImageReader FilePrefix sources ImageReader NumberOfScalarComponents sources ImageReader ScalarArrayName sources JPEGSeriesReader FileNames sources JPEGSeriesReader TimestepValues sources LSDynaReader BeamArrayInfo sources LSDynaReader BeamArrayStatus sources LSDynaReader DeformedMesh sources LSDynaReader FileName sources LSDynaReader PartArrayInfo sources LSDynaReader PartArrayStatus sources LSDynaReader ParticleArrayInfo sources LSDynaReader ParticleArrayStatus sources LSDynaReader PointArrayInfo sources LSDynaReader PointArrayStatus sources LSDynaReader RemoveDeletedCells sources LSDynaReader RigidBodyArrayInfo sources LSDynaReader RigidBodyArrayStatus sources LSDynaReader RoadSurfaceArrayInfo sources LSDynaReader RoadSurfaceArrayStatus sources LSDynaReader ShellArrayInfo sources LSDynaReader ShellArrayStatus sources LSDynaReader SolidArrayInfo sources LSDynaReader SolidArrayStatus sources LSDynaReader ThickShellArrayInfo sources LSDynaReader ThickShellArrayStatus sources LSDynaReader TimestepValues sources LegacyVTKFileReader FileNameInfo sources LegacyVTKFileReader FileNames sources LegacyVTKFileReader TimestepValues sources LineSource Point1 sources LineSource Point2 sources LineSource Resolution sources LocationSelectionSource ContainingCells sources LocationSelectionSource FieldType sources LocationSelectionSource InsideOut sources LocationSelectionSource Locations sources MFIXReader CellArrayInfo sources MFIXReader CellArrayStatus sources MFIXReader FileName sources MFIXReader TimestepValues sources MPASReader CellArrayInfo sources MPASReader CellArrayStatus sources MPASReader CenterLon sources MPASReader CenterLonRangeInfo sources MPASReader FileName sources MPASReader IsAtmosphere sources MPASReader LayerThickness sources MPASReader LayerThicknessRangeInfo sources MPASReader PointArrayInfo sources MPASReader PointArrayStatus sources MPASReader ProjectLatLon sources MPASReader ShowMultilayerView sources MPASReader TimestepValues sources MPASReader VerticalLevel sources MPASReader VerticalLevelRangeInfo sources MetaImageReader FileNameInfo sources MetaImageReader FileNames sources MetaImageReader TimestepValues sources MultiServerProxy DependencyLink sources NetCDFCAMReader FileName sources NetCDFCAMReader FileNameInfo sources NetCDFCAMReader TimestepValues sources NetCDFCAMReader CellLayerRight sources NetCDFCAMReader ConnectivityFileName sources NetCDFCAMReader SingleLevel sources NetCDFPOPReader FileName sources NetCDFPOPReader FileNameInfo sources NetCDFPOPReader TimestepValues sources NetCDFPOPReader Stride sources NetCDFPOPReader VariableArrayInfo sources NetCDFPOPReader VariableArrayStatus sources NetworkImageSource FileName sources NrrdReader DataVOI sources NrrdReader FileName sources OctreeFractal Dimension sources OctreeFractal MaximumLevel sources OctreeFractal MaximumNumberOfIterations sources OctreeFractal MinimumLevel sources OctreeFractal OriginCX sources OctreeFractal ProjectionAxes sources OctreeFractal SizeCX sources OctreeFractal Threshold sources OpenFOAMReader AddDimensionsToArrayNames sources OpenFOAMReader CacheMesh sources OpenFOAMReader CaseType sources OpenFOAMReader CellArrayInfo sources OpenFOAMReader CellArrays sources OpenFOAMReader CreateCellToPoint sources OpenFOAMReader DecomposePolyhedra sources OpenFOAMReader FileName sources OpenFOAMReader LagrangianArrayInfo sources OpenFOAMReader LagrangianArrays sources OpenFOAMReader ListTimeStepsByControlDict sources OpenFOAMReader MeshRegions sources OpenFOAMReader PatchArrayInfo sources OpenFOAMReader PointArrayInfo sources OpenFOAMReader PointArrays sources OpenFOAMReader PositionsIsIn13Format sources OpenFOAMReader ReadZones sources OpenFOAMReader Refresh sources OpenFOAMReader TimestepValues sources OutlineSource Bounds sources P3DReader FileNameInfo sources P3DReader QFileName sources P3DReader TimestepValues sources P3DReader AutoDetectFormat sources P3DReader BinaryFile sources P3DReader ByteOrder sources P3DReader DoublePrecision sources P3DReader FileName sources P3DReader ForceRead sources P3DReader FunctionFileName sources P3DReader Functions sources P3DReader HasByteCount sources P3DReader IBlanking sources P3DReader MultiGrid sources P3DReader TwoDimensionalGeometry sources PNGSeriesReader FileNames sources PNGSeriesReader TimestepValues sources PVDReader FileName sources PVDReader TimestepValues sources PVTrivialProducer WholeExtent sources ParticleReader FileName sources ParticleReader FileNameInfo sources ParticleReader TimestepValues sources ParticleReader ByteOrder sources ParticleReader DataType sources ParticleReader FileType sources ParticleReader HasScalar sources PedigreeIDSelectionSource ContainingCells sources PedigreeIDSelectionSource FieldType sources PedigreeIDSelectionSource IDs sources PedigreeIDSelectionSource InsideOut sources PedigreeIDSelectionSource StringIDs sources PhastaReader FileName sources PhastaReader TimestepValues sources PlaneSource Origin sources PlaneSource Point1 sources PlaneSource Point2 sources PlaneSource XResolution sources PlaneSource YResolution sources Plot3DMetaReader FileName sources Plot3DMetaReader TimestepValues sources PointSource Center sources PointSource NumberOfPoints sources PointSource Radius sources ProStarReader FileName sources ProStarReader ScaleFactor sources ProgrammableSource InformationScript sources ProgrammableSource OutputDataSetType sources ProgrammableSource Parameters sources ProgrammableSource PythonPath sources ProgrammableSource Script sources RTAnalyticSource Center sources RTAnalyticSource Maximum sources RTAnalyticSource StandardDeviation sources RTAnalyticSource SubsampleRate sources RTAnalyticSource WholeExtent sources RTAnalyticSource XFreq sources RTAnalyticSource XMag sources RTAnalyticSource YFreq sources RTAnalyticSource YMag sources RTAnalyticSource ZFreq sources RTAnalyticSource ZMag sources RTXMLPolyDataReader FileName sources RTXMLPolyDataReader Location sources RTXMLPolyDataReader NewDataAvailable sources RTXMLPolyDataReader NextFileName sources RTXMLPolyDataReader ResetReader sources RTXMLPolyDataReader UpdateToNextFile sources Ruler Point1 sources Ruler Point2 sources SLACParticleReader FileName sources SLACParticleReader TimestepValues sources SLACReader FrequencyScale sources SLACReader FrequencyScaleInfo sources SLACReader MeshFileName sources SLACReader ModeFileName sources SLACReader PhaseShift sources SLACReader PhaseShiftInfo sources SLACReader ReadExternalSurface sources SLACReader ReadInternalVolume sources SLACReader ReadMidpoints sources SLACReader TimeRange sources SLACReader TimestepValues sources SPCTHRestartReader FileName sources SPCTHRestartReader TimestepValues sources SPCTHRestartReader UseMetaFile sources SPCTHRestartReader CellArrayInfo sources SPCTHRestartReader CellArrayStatus sources SPCTHRestartReader DistributeFiles sources SPCTHRestartReader DownConvertVolumeFraction sources SPCTHRestartReader GenerateActiveBlockArray sources SPCTHRestartReader GenerateBlockIdArray sources SPCTHRestartReader GenerateLevelArray sources SPCTHRestartReader GenerateMarkers sources SPCTHRestartReader GenerateTracers sources SelectionQuerySource CompositeIndex sources SelectionQuerySource FieldType sources SelectionQuerySource HierarchicalIndex sources SelectionQuerySource HierarchicalLevel sources SelectionQuerySource InsideOut sources SelectionQuerySource ProcessID sources SelectionQuerySource QueryString sources SelectionQuerySource UserFriendlyText sources SelectionSourceBase ContainingCells sources SelectionSourceBase FieldType sources SelectionSourceBase InsideOut sources SphereSource Center sources SphereSource EndPhi sources SphereSource EndTheta sources SphereSource PhiResolution sources SphereSource Radius sources SphereSource StartPhi sources SphereSource StartTheta sources SphereSource ThetaResolution sources SplineSource ParametricFunction sources SuperquadricSource Center sources SuperquadricSource PhiResolution sources SuperquadricSource PhiRoundness sources SuperquadricSource Scale sources SuperquadricSource Size sources SuperquadricSource ThetaResolution sources SuperquadricSource ThetaRoundness sources SuperquadricSource Thickness sources SuperquadricSource Toroidal sources TIFFReader FileName sources TIFFSeriesReader FileNames sources TIFFSeriesReader TimestepValues sources TecplotReader FileNameInfo sources TecplotReader FileNames sources TecplotReader TimestepValues sources TecplotReader DataArrayInfo sources TecplotReader DataArrayStatus sources Test3DWidget Resolution sources TextSource Text sources ThresholdSelectionSource ArrayName sources ThresholdSelectionSource ContainingCells sources ThresholdSelectionSource FieldType sources ThresholdSelectionSource InsideOut sources ThresholdSelectionSource Thresholds sources TimeSource Analytic sources TimeSource Growing sources TimeSource TimestepValues sources TimeSource X Amplitude sources TimeSource Y Amplitude sources TimeToTextConvertorSource Format sources UnstructuredPOPReader FileName sources UnstructuredPOPReader FileNameInfo sources UnstructuredPOPReader TimestepValues sources UnstructuredPOPReader Stride sources UnstructuredPOPReader VOI sources UnstructuredPOPReader VerticalVelocity sources VPICReader DefaultXExtent sources VPICReader DefaultYExtent sources VPICReader DefaultZExtent sources VPICReader FileName sources VPICReader PointArrayInfo sources VPICReader PointArrayStatus sources VPICReader SetStride sources VPICReader TimestepValues sources VPICReader XExtent sources VPICReader YExtent sources VPICReader ZExtent sources VectorText Text sources WindBladeReader Filename sources WindBladeReader PointArrayInfo sources WindBladeReader PointArrayStatus sources WindBladeReader TimestepValues sources XMLHierarchicalBoxDataReader FileName sources XMLHierarchicalBoxDataReader FileNameInfo sources XMLHierarchicalBoxDataReader TimestepValues sources XMLImageDataReader FileName sources XMLImageDataReader FileNameInfo sources XMLImageDataReader TimestepValues sources XMLImageDataReader CellArrayInfo sources XMLImageDataReader CellArrayStatus sources XMLImageDataReader PointArrayInfo sources XMLImageDataReader PointArrayStatus sources XMLMultiBlockDataReader FileName sources XMLMultiBlockDataReader FileNameInfo sources XMLMultiBlockDataReader TimestepValues sources XMLPImageDataReader FileName sources XMLPImageDataReader FileNameInfo sources XMLPImageDataReader TimestepValues sources XMLPImageDataReader CellArrayInfo sources XMLPImageDataReader CellArrayStatus sources XMLPImageDataReader PointArrayInfo sources XMLPImageDataReader PointArrayStatus sources XMLPPolyDataReader FileName sources XMLPPolyDataReader FileNameInfo sources XMLPPolyDataReader TimestepValues sources XMLPPolyDataReader CellArrayInfo sources XMLPPolyDataReader CellArrayStatus sources XMLPPolyDataReader PointArrayInfo sources XMLPPolyDataReader PointArrayStatus sources XMLPRectilinearGridReader FileName sources XMLPRectilinearGridReader FileNameInfo sources XMLPRectilinearGridReader TimestepValues sources XMLPRectilinearGridReader CellArrayInfo sources XMLPRectilinearGridReader CellArrayStatus sources XMLPRectilinearGridReader PointArrayInfo sources XMLPRectilinearGridReader PointArrayStatus sources XMLPStructuredGridReader FileName sources XMLPStructuredGridReader FileNameInfo sources XMLPStructuredGridReader TimestepValues sources XMLPStructuredGridReader CellArrayInfo sources XMLPStructuredGridReader CellArrayStatus sources XMLPStructuredGridReader PointArrayInfo sources XMLPStructuredGridReader PointArrayStatus sources XMLPUnstructuredGridReader FileName sources XMLPUnstructuredGridReader FileNameInfo sources XMLPUnstructuredGridReader TimestepValues sources XMLPUnstructuredGridReader CellArrayInfo sources XMLPUnstructuredGridReader CellArrayStatus sources XMLPUnstructuredGridReader PointArrayInfo sources XMLPUnstructuredGridReader PointArrayStatus sources XMLPolyDataEnsembleReader FileIndex sources XMLPolyDataEnsembleReader FileIndexRange sources XMLPolyDataEnsembleReader MetaFileName sources XMLPolyDataEnsembleReader TimestepValues sources XMLPolyDataEnsembleReader CellArrayInfo sources XMLPolyDataEnsembleReader CellArrayStatus sources XMLPolyDataEnsembleReader PointArrayInfo sources XMLPolyDataEnsembleReader PointArrayStatus sources XMLPolyDataEnsembleReader UseMetaFile sources XMLPolyDataReader FileName sources XMLPolyDataReader FileNameInfo sources XMLPolyDataReader TimestepValues sources XMLPolyDataReader CellArrayInfo sources XMLPolyDataReader CellArrayStatus sources XMLPolyDataReader PointArrayInfo sources XMLPolyDataReader PointArrayStatus sources XMLRectilinearGridReader FileName sources XMLRectilinearGridReader FileNameInfo sources XMLRectilinearGridReader TimestepValues sources XMLRectilinearGridReader CellArrayInfo sources XMLRectilinearGridReader CellArrayStatus sources XMLRectilinearGridReader PointArrayInfo sources XMLRectilinearGridReader PointArrayStatus sources XMLStructuredGridReader FileName sources XMLStructuredGridReader FileNameInfo sources XMLStructuredGridReader TimestepValues sources XMLStructuredGridReader CellArrayInfo sources XMLStructuredGridReader CellArrayStatus sources XMLStructuredGridReader PointArrayInfo sources XMLStructuredGridReader PointArrayStatus sources XMLUniformGridAMRReader FileName sources XMLUniformGridAMRReader FileNameInfo sources XMLUniformGridAMRReader TimestepValues sources XMLUniformGridAMRReader DefaultNumberOfLevels sources XMLUnstructuredGridReader FileName sources XMLUnstructuredGridReader FileNameInfo sources XMLUnstructuredGridReader TimestepValues sources XMLUnstructuredGridReader CellArrayInfo sources XMLUnstructuredGridReader CellArrayStatus sources XMLUnstructuredGridReader PointArrayInfo sources XMLUnstructuredGridReader PointArrayStatus sources XdmfReader FileNameInfo sources XdmfReader FileNames sources XdmfReader TimestepValues sources XdmfReader CellArrayInfo sources XdmfReader CellArrayStatus sources XdmfReader GridInfo sources XdmfReader GridStatus sources XdmfReader PointArrayInfo sources XdmfReader PointArrayStatus sources XdmfReader SILTimeStamp sources XdmfReader SetInfo sources XdmfReader SetStatus sources XdmfReader Stride sources byureader FileName sources ensight CaseFileName sources ensight CellArrayInfo sources ensight CellArrayStatus sources ensight PointArrayInfo sources ensight PointArrayStatus sources ensight TimestepValues sources ensightMS ByteOrder sources ensightMS CaseFileName sources ensightMS CellArrayInfo sources ensightMS CellArrayStatus sources ensightMS PointArrayInfo sources ensightMS PointArrayStatus sources ensightMS SetTimeValue sources ensightMS TimestepValues sources gaussiancubereader BScale sources gaussiancubereader FileName sources gaussiancubereader HBScale sources netCDFReader FileName sources netCDFReader TimestepValues sources netCDFReader DimensionInfo sources netCDFReader Dimensions sources netCDFReader OutputType sources netCDFReader ReplaceFillValueWithNan sources netCDFReader SphericalCoordinates sources netCDFReader VariableArrayInfo sources netCDFReader VariableDimensionInfo sources netCDFReader VerticalBias sources netCDFReader VerticalScale sources objreader FileName sources pdbreader FileName sources plyreader FileName sources pvtkfile FileName sources spcthhistoryreader CommentCharacter sources spcthhistoryreader Delimeter sources spcthhistoryreader FileName sources spcthhistoryreader TimestepValues sources spcthreader CellArrayInfo sources spcthreader CellArrayStatus sources spcthreader ComputeDerivedVariables sources spcthreader DistributeFiles sources spcthreader DownConvertVolumeFraction sources spcthreader FileName sources spcthreader GenerateActiveBlockArray sources spcthreader GenerateBlockIdArray sources spcthreader GenerateLevelArray sources spcthreader GenerateMarkers sources spcthreader GenerateTracers sources spcthreader MergeXYZComponents sources spcthreader TimestepValues sources stlreader FileNameInfo sources stlreader FileNames sources stlreader TimestepValues sources vrmlreader FileName sources xyzreader FileName sources xyzreader TimeStep filters AMRConnectivity Input filters AMRConnectivity Propagate Ghosts filters AMRConnectivity Resolve Blocks filters AMRConnectivity SelectMaterialArrays filters AMRConnectivity VolumeFractionSurfaceValue filters AMRCutPlane Center filters AMRCutPlane Input filters AMRCutPlane LevelOfResolution filters AMRCutPlane Normal filters AMRCutPlane UseNativeCutter filters AMRDualClip Input filters AMRDualClip InternalDecimation filters AMRDualClip MergePoints filters AMRDualClip MultiprocessCommunication filters AMRDualClip SelectMaterialArrays filters AMRDualClip VolumeFractionSurfaceValue filters AMRDualContour Capping filters AMRDualContour DegenerateCells filters AMRDualContour Input filters AMRDualContour MergePoints filters AMRDualContour MultiprocessCommunication filters AMRDualContour SelectMaterialArrays filters AMRDualContour SkipGhostCopy filters AMRDualContour Triangulate filters AMRDualContour VolumeFractionSurfaceValue filters AMRFragmentIntegration Input filters AMRFragmentIntegration SelectMassArrays filters AMRFragmentIntegration SelectMassWeightedArrays filters AMRFragmentIntegration SelectMaterialArrays filters AMRFragmentIntegration SelectVolumeWeightedArrays filters AMRFragmentsFilter Extract Surface filters AMRFragmentsFilter Input filters AMRFragmentsFilter Integrate Fragments filters AMRFragmentsFilter SelectMassArrays filters AMRFragmentsFilter SelectMassWeightedArrays filters AMRFragmentsFilter SelectMaterialArrays filters AMRFragmentsFilter SelectVolumeWeightedArrays filters AMRFragmentsFilter Use Watertight Surface filters AMRFragmentsFilter VolumeFractionSurfaceValue filters AMRResampleFilter Demand-Driven Mode filters AMRResampleFilter Input filters AMRResampleFilter Max filters AMRResampleFilter Min filters AMRResampleFilter Number of Samples filters AMRResampleFilter NumberOfPartitions filters AMRResampleFilter TransferToNodes filters AMRSlice EnablePrefetching filters AMRSlice ForwardUpstream filters AMRSlice Input filters AMRSlice Level filters AMRSlice Normal filters AMRSlice OffSet filters AMRToMultiBlock Input filters AnnotateAttributeData ArrayAssociation filters AnnotateAttributeData ArrayName filters AnnotateAttributeData ElementId filters AnnotateAttributeData Input filters AnnotateAttributeData Prefix filters AnnotateAttributeData ProcessId filters AnnotateGlobalData Input filters AnnotateGlobalData Prefix filters AnnotateGlobalData SelectArrays filters Append Input filters AppendAttributes Input filters AppendPolyData Input filters ArbitrarySourceStreamTracer ComputeVorticity filters ArbitrarySourceStreamTracer InitialIntegrationStep filters ArbitrarySourceStreamTracer Input filters ArbitrarySourceStreamTracer IntegrationDirection filters ArbitrarySourceStreamTracer IntegrationStepUnit filters ArbitrarySourceStreamTracer IntegratorType filters ArbitrarySourceStreamTracer MaximumError filters ArbitrarySourceStreamTracer MaximumIntegrationStep filters ArbitrarySourceStreamTracer MaximumNumberOfSteps filters ArbitrarySourceStreamTracer MaximumPropagation filters ArbitrarySourceStreamTracer MinimumIntegrationStep filters ArbitrarySourceStreamTracer SelectInputVectors filters ArbitrarySourceStreamTracer Source filters ArbitrarySourceStreamTracer TerminalSpeed filters AttributeDataToTableFilter AddMetaData filters AttributeDataToTableFilter FieldAssociation filters AttributeDataToTableFilter Input filters BlockIdScalars Input filters BrownianPoints Input filters BrownianPoints MaximumSpeed filters BrownianPoints MinimumSpeed filters CTHPart CapSurfaces filters CTHPart ClipPlane filters CTHPart GenerateTriangles filters CTHPart Input filters CTHPart RemoveGhostCells filters CTHPart VolumeArrays filters CTHPart VolumeFractionSurfaceValue filters CTHSurface Input filters CacheKeeper CacheTime filters CacheKeeper CachingEnabled filters CacheKeeper Input filters CacheKeeper RemoveAllCaches filters Calculator AttributeMode filters Calculator CoordinateResults filters Calculator Function filters Calculator Input filters Calculator ReplaceInvalidValues filters Calculator ReplacementValue filters Calculator ResultArrayName filters Calculator ResultNormals filters Calculator ResultTCoords filters CellCenters Input filters CellCenters VertexCells filters CellDataToPointData Input filters CellDataToPointData PassCellData filters CellDataToPointData PieceInvariant filters CellDerivatives Input filters CellDerivatives OutputTensorType filters CellDerivatives OutputVectorType filters CellDerivatives SelectInputScalars filters CellDerivatives SelectInputVectors filters CleanPolyData AbsoluteTolerance filters CleanPolyData ConvertLinesToPoints filters CleanPolyData ConvertPolysToLines filters CleanPolyData ConvertStripsToPolys filters CleanPolyData Input filters CleanPolyData PieceInvariant filters CleanPolyData PointMerging filters CleanPolyData Tolerance filters CleanPolyData ToleranceIsAbsolute filters CleanUnstructuredGrid Input filters CleanUnstructuredGridCells Input filters ClientServerMoveData Input filters ClientServerMoveData OutputDataType filters ClientServerMoveData WholeExtent filters Clip ClipFunction filters Clip Input filters Clip InputBounds filters Clip InsideOut filters Clip PreserveInputCells filters Clip SelectInputScalars filters Clip UseValueAsOffset filters Clip Value filters ClipClosedSurface BaseColor filters ClipClosedSurface ClipColor filters ClipClosedSurface ClippingPlane filters ClipClosedSurface GenerateFaces filters ClipClosedSurface GenerateOutline filters ClipClosedSurface Input filters ClipClosedSurface InsideOut filters ClipClosedSurface ScalarMode filters ClipClosedSurface Tolerance filters ColorByArray Input filters ColorByArray LookupTable filters ColorByArray NaNColor filters ColorByArray OutputFormat filters ColorByArray SelectInputScalars filters ComputeQuartiles Input filters ContingencyStatistics AttributeMode filters ContingencyStatistics Input filters ContingencyStatistics ModelInput filters ContingencyStatistics SelectArrays filters ContingencyStatistics Task filters ContingencyStatistics TrainingFraction filters Contour ComputeGradients filters Contour ComputeNormals filters Contour ComputeScalars filters Contour ContourValues filters Contour GenerateTriangles filters Contour Input filters Contour Locator filters Contour SelectInputScalars filters ConvertSelection ArrayNames filters ConvertSelection DataInput filters ConvertSelection Input filters ConvertSelection MatchAnyValues filters ConvertSelection OutputType filters Curvatures CurvatureType filters Curvatures Input filters Curvatures InvertMeanCurvature filters Cut ContourValues filters Cut CutFunction filters Cut Input filters Cut InputBounds filters Cut PreserveInputCells filters Cut Triangulate the slice filters CutEverything ContourValues filters CutEverything CutFunction filters CutEverything Input filters CutEverything InputBounds filters DataSetSurfaceFilter Input filters DataSetSurfaceFilter NonlinearSubdivisionLevel filters DataSetSurfaceFilter PieceInvariant filters DataSetTriangleFilter Input filters DecimatePro BoundaryVertexDeletion filters DecimatePro FeatureAngle filters DecimatePro Input filters DecimatePro PreserveTopology filters DecimatePro TargetReduction filters Delaunay2D Alpha filters Delaunay2D BoundingTriangulation filters Delaunay2D Input filters Delaunay2D Offset filters Delaunay2D ProjectionPlaneMode filters Delaunay2D Tolerance filters Delaunay3D Alpha filters Delaunay3D AlphaLines filters Delaunay3D AlphaTets filters Delaunay3D AlphaTris filters Delaunay3D AlphaVerts filters Delaunay3D BoundingTriangulation filters Delaunay3D Input filters Delaunay3D Offset filters Delaunay3D Tolerance filters DescriptiveStatistics AttributeMode filters DescriptiveStatistics Input filters DescriptiveStatistics ModelInput filters DescriptiveStatistics SelectArrays filters DescriptiveStatistics SignedDeviations filters DescriptiveStatistics Task filters DescriptiveStatistics TrainingFraction filters ElevationFilter HighPoint filters ElevationFilter Input filters ElevationFilter LowPoint filters ElevationFilter ScalarRange filters ExtractBagPlots Input filters ExtractBagPlots RobustPCA filters ExtractBagPlots SelectArrays filters ExtractBagPlots Sigma filters ExtractBagPlots TransposeTable filters ExtractBlock BlockIndices filters ExtractBlock Input filters ExtractBlock MaintainStructure filters ExtractBlock PruneOutput filters ExtractEdges Input filters ExtractFieldDataOverTime Input filters ExtractGeometry Extract intersected filters ExtractGeometry Extract only intersected filters ExtractGeometry ExtractInside filters ExtractGeometry ImplicitFunction filters ExtractGeometry Input filters ExtractGeometry InputBounds filters ExtractGrid IncludeBoundary filters ExtractGrid Input filters ExtractGrid SampleRateI filters ExtractGrid SampleRateJ filters ExtractGrid SampleRateK filters ExtractGrid VOI filters ExtractHierarchicalDataSets Input filters ExtractHierarchicalDataSets SelectedDataSets filters ExtractHierarchicalLevel Input filters ExtractHierarchicalLevel Levels filters ExtractHistogram BinCount filters ExtractHistogram CalculateAverages filters ExtractHistogram Component filters ExtractHistogram CustomBinRanges filters ExtractHistogram Input filters ExtractHistogram SelectInputArray filters ExtractHistogram UseCustomBinRanges filters ExtractLocation Input filters ExtractLocation Location filters ExtractLocation Mode filters ExtractSelection Input filters ExtractSelection PreserveTopology filters ExtractSelection Selection filters ExtractSelection ShowBounds filters ExtractSelectionOverTime Input filters ExtractSelectionOverTime Only Report Selection Statistics filters ExtractSelectionOverTime Selection filters FFTSelectionOverTime Input filters FFTSelectionOverTime Selection filters FeatureEdges BoundaryEdges filters FeatureEdges Coloring filters FeatureEdges FeatureAngle filters FeatureEdges FeatureEdges filters FeatureEdges Input filters FeatureEdges ManifoldEdges filters FeatureEdges NonManifoldEdges filters FlattenFilter Input filters GaussianSplatter Accumulation Mode filters GaussianSplatter CapValue filters GaussianSplatter Capping filters GaussianSplatter Eccentricity filters GaussianSplatter ExponentFactor filters GaussianSplatter Input filters GaussianSplatter ModelBounds filters GaussianSplatter NormalWarping filters GaussianSplatter NullValue filters GaussianSplatter Radius filters GaussianSplatter SampleDimensions filters GaussianSplatter ScalarWarping filters GaussianSplatter ScaleFactor filters GaussianSplatter SelectInputScalars filters GenerateIdScalars ArrayName filters GenerateIdScalars Input filters GenericClip ClipFunction filters GenericClip Input filters GenericClip InputBounds filters GenericClip InsideOut filters GenericClip SelectInputScalars filters GenericClip Value filters GenericContour ComputeGradients filters GenericContour ComputeNormals filters GenericContour ComputeScalars filters GenericContour ContourValues filters GenericContour Input filters GenericContour Locator filters GenericContour SelectInputScalars filters GenericCut ContourValues filters GenericCut CutFunction filters GenericCut Input filters GenericCut InputBounds filters GenericGeometryFilter Input filters GenericGeometryFilter PassThroughCellIds filters GenericOutlineFilter Input filters GenericStreamTracer InitialIntegrationStep filters GenericStreamTracer Input filters GenericStreamTracer IntegrationDirection filters GenericStreamTracer IntegrationStepUnit filters GenericStreamTracer IntegratorType filters GenericStreamTracer MaximumError filters GenericStreamTracer MaximumIntegrationStep filters GenericStreamTracer MaximumNumberOfSteps filters GenericStreamTracer MaximumPropagation filters GenericStreamTracer MinimumIntegrationStep filters GenericStreamTracer SelectInputVectors filters GenericStreamTracer Source filters GenericStreamTracer TerminalSpeed filters GenericTessellator Input filters GeometryFilter ForceStrips filters GeometryFilter Input filters GeometryFilter NonlinearSubdivisionLevel filters GeometryFilter PassThroughIds filters GeometryFilter PassThroughPointIds filters GeometryFilter UseOutline filters GeometryFilter UseStrips filters Glyph GlyphMode filters Glyph GlyphTransform filters Glyph Input filters Glyph MaximumNumberOfSamplePoints filters Glyph Orient filters Glyph Scalars filters Glyph ScaleFactor filters Glyph ScaleMode filters Glyph Seed filters Glyph Source filters Glyph Stride filters Glyph Vectors filters GlyphWithCustomSource GlyphMode filters GlyphWithCustomSource GlyphTransform filters GlyphWithCustomSource Input filters GlyphWithCustomSource MaximumNumberOfSamplePoints filters GlyphWithCustomSource Orient filters GlyphWithCustomSource Scalars filters GlyphWithCustomSource ScaleFactor filters GlyphWithCustomSource ScaleMode filters GlyphWithCustomSource Seed filters GlyphWithCustomSource Source filters GlyphWithCustomSource Stride filters GlyphWithCustomSource Vectors filters Gradient Dimensionality filters Gradient Input filters Gradient SelectInputScalars filters GradientMagnitude Dimensionality filters GradientMagnitude Input filters GridConnectivity Input filters GroupDataSets Input filters ImageClip Input filters ImageClip OutputWholeExtent filters ImageDataToAMR Input filters ImageDataToAMR MaximumNumberOfLevels filters ImageDataToAMR NumberOfLevels filters ImageDataToAMR RefinementRatio filters ImageDataToPointSet Input filters ImageDataToUniformGrid Input filters ImageDataToUniformGrid Reverse filters ImageDataToUniformGrid SelectInputScalars filters ImageResampling CustomSamplingBounds filters ImageResampling Input filters ImageResampling SamplingDimension filters ImageResampling UseInputBounds filters ImageShrink Averaging filters ImageShrink Input filters ImageShrink ShrinkFactors filters IntegrateAttributes Input filters IntegrateFlowThroughSurface Input filters IntegrateFlowThroughSurface SelectInputVectors filters IntersectFragments CutFunction filters IntersectFragments Input filters IntersectFragments Source filters IsoVolume Input filters IsoVolume SelectInputScalars filters IsoVolume ThresholdBetween filters KMeans AttributeMode filters KMeans Input filters KMeans K filters KMeans MaxNumIterations filters KMeans ModelInput filters KMeans SelectArrays filters KMeans Task filters KMeans Tolerance filters KMeans TrainingFraction filters LegacyArbitrarySourceGlyph Input filters LegacyArbitrarySourceGlyph KeepRandomPoints filters LegacyArbitrarySourceGlyph MaximumNumberOfPoints filters LegacyArbitrarySourceGlyph RandomMode filters LegacyArbitrarySourceGlyph SelectInputScalars filters LegacyArbitrarySourceGlyph SelectInputVectors filters LegacyArbitrarySourceGlyph SetOrient filters LegacyArbitrarySourceGlyph SetScaleFactor filters LegacyArbitrarySourceGlyph SetScaleMode filters LegacyArbitrarySourceGlyph Source filters LegacyArbitrarySourceGlyph UseMaskPoints filters LegacyGlyph GlyphTransform filters LegacyGlyph Input filters LegacyGlyph KeepRandomPoints filters LegacyGlyph MaximumNumberOfPoints filters LegacyGlyph RandomMode filters LegacyGlyph SelectInputScalars filters LegacyGlyph SelectInputVectors filters LegacyGlyph SetOrient filters LegacyGlyph SetScaleFactor filters LegacyGlyph SetScaleMode filters LegacyGlyph Source filters LegacyGlyph UseMaskPoints filters LinearExtrusionFilter Capping filters LinearExtrusionFilter Input filters LinearExtrusionFilter PieceInvariant filters LinearExtrusionFilter ScaleFactor filters LinearExtrusionFilter Vector filters LoopSubdivisionFilter Input filters LoopSubdivisionFilter NumberOfSubdivisions filters MPIMoveData Input filters MPIMoveData MoveMode filters MPIMoveData OutputDataType filters MaskPoints GenerateVertices filters MaskPoints Input filters MaskPoints MaximumNumberOfPoints filters MaskPoints Offset filters MaskPoints OnRatio filters MaskPoints ProportionalMaximumNumberOfPoints filters MaskPoints RandomMode filters MaskPoints RandomModeType filters MaskPoints SingleVertexPerCell filters MaterialInterfaceFilter ClipFunction filters MaterialInterfaceFilter ComputeOBB filters MaterialInterfaceFilter Input filters MaterialInterfaceFilter InvertVolumeFraction filters MaterialInterfaceFilter MaterialFractionThreshold filters MaterialInterfaceFilter OutputBaseName filters MaterialInterfaceFilter SelectMassArray filters MaterialInterfaceFilter SelectMassWtdAvgArray filters MaterialInterfaceFilter SelectMaterialArray filters MaterialInterfaceFilter SelectVolumeWtdAvgArray filters MaterialInterfaceFilter WriteGeometryOutput filters MaterialInterfaceFilter WriteStatisticsOutput filters Median Input filters Median KernelSize filters Median SelectInputScalars filters MergeBlocks Input filters MergeBlocks MergePoints filters MergeBlocks SubTreeCompositeIndex filters MeshQuality HexQualityMeasure filters MeshQuality Input filters MeshQuality QuadQualityMeasure filters MeshQuality TetQualityMeasure filters MeshQuality TriangleQualityMeasure filters MinMax Input filters MinMax Operation filters MulticorrelativeStatistics AttributeMode filters MulticorrelativeStatistics Input filters MulticorrelativeStatistics ModelInput filters MulticorrelativeStatistics SelectArrays filters MulticorrelativeStatistics Task filters MulticorrelativeStatistics TrainingFraction filters NonOverlappingLevelIdScalars Input filters NormalGlyphs Consistency filters NormalGlyphs Glyph Max. Points filters NormalGlyphs Glyph Scale Factor filters NormalGlyphs Input filters NormalGlyphs InvertArrow filters OctreeDepthLimit Input filters OctreeDepthLimit MaximumLevel filters OctreeDepthScalars Input filters OrderedCompositeDistributor Input filters OrderedCompositeDistributor OutputType filters OrderedCompositeDistributor PKdTree filters OrderedCompositeDistributor PassThrough filters OutlineCornerFilter CornerFactor filters OutlineCornerFilter Input filters OutlineFilter Input filters OverlappingLevelIdScalars Input filters PCAStatistics AttributeMode filters PCAStatistics BasisEnergy filters PCAStatistics BasisScheme filters PCAStatistics BasisSize filters PCAStatistics Input filters PCAStatistics ModelInput filters PCAStatistics NormalizationScheme filters PCAStatistics RobustPCA filters PCAStatistics SelectArrays filters PCAStatistics Task filters PCAStatistics TrainingFraction filters PVConnectivityFilter ColorRegions filters PVConnectivityFilter ExtractionMode filters PVConnectivityFilter Input filters PVExtractSelection Input filters PVExtractSelection Selection filters ParticlePath ComputeVorticity filters ParticlePath DisableResetCache filters ParticlePath ForceReinjectionEveryNSteps filters ParticlePath Input filters ParticlePath SelectInputVectors filters ParticlePath Source filters ParticlePath StaticMesh filters ParticlePath StaticSeeds filters ParticlePath TerminationTime filters ParticlePath TimestepValues filters ParticlePathLines IdChannelArray filters ParticlePathLines Input filters ParticlePathLines MaskPoints filters ParticlePathLines MaxStepDistance filters ParticlePathLines MaxTrackLength filters ParticlePathLines Selection filters ParticleTracer ComputeVorticity filters ParticleTracer ForceReinjectionEveryNSteps filters ParticleTracer Input filters ParticleTracer SelectInputVectors filters ParticleTracer Source filters ParticleTracer StaticMesh filters ParticleTracer StaticSeeds filters ParticleTracer TimestepValues filters PassArrays CellDataArrays filters PassArrays FieldDataArrays filters PassArrays Input filters PassArrays PointDataArrays filters PassArrays SelectedFieldTypes filters PassArrays UseFieldTypes filters PassThrough Input filters PlotAttributes Input filters PlotOnIntersectionCurves Input filters PlotOnIntersectionCurves Slice Type filters PlotOnSortedLines Input filters PointDataToCellData Input filters PointDataToCellData PassPointData filters PolyDataNormals ComputeCellNormals filters PolyDataNormals Consistency filters PolyDataNormals FeatureAngle filters PolyDataNormals FlipNormals filters PolyDataNormals Input filters PolyDataNormals NonManifoldTraversal filters PolyDataNormals PieceInvariant filters PolyDataNormals Splitting filters PolyLineToRectilinearGrid Input filters Probe ComputeTolerance filters Probe Input filters Probe PassCellArrays filters Probe PassFieldArrays filters Probe PassPointArrays filters Probe Source filters Probe Tolerance filters ProbeLine ComputeTolerance filters ProbeLine Input filters ProbeLine PassPartialArrays filters ProbeLine Source filters ProbeLine Tolerance filters ProbePoint ComputeTolerance filters ProbePoint Input filters ProbePoint PassFieldArrays filters ProbePoint Source filters ProbePoint Tolerance filters ProcessIdScalars Input filters ProcessIdScalars RandomMode filters ProgrammableFilter CopyArrays filters ProgrammableFilter InformationScript filters ProgrammableFilter Input filters ProgrammableFilter OutputDataSetType filters ProgrammableFilter Parameters filters ProgrammableFilter PythonPath filters ProgrammableFilter Script filters ProgrammableFilter UpdateExtentScript filters PythonAnnotation AnnotationValue filters PythonAnnotation ArrayAssociation filters PythonAnnotation Expression filters PythonAnnotation Input filters PythonCalculator ArrayAssociation filters PythonCalculator ArrayName filters PythonCalculator CopyArrays filters PythonCalculator Expression filters PythonCalculator Input filters QuadraturePointInterpolator Input filters QuadraturePointInterpolator QuadratureSchemeDefinition filters QuadraturePointsGenerator Input filters QuadraturePointsGenerator QuadratureSchemeDefinition filters QuadratureSchemeDictionaryGenerator Input filters QuadricClustering CopyCellData filters QuadricClustering Input filters QuadricClustering NumberOfDivisions filters QuadricClustering UseFeatureEdges filters QuadricClustering UseFeaturePoints filters QuadricClustering UseInputPoints filters QuadricClustering UseInternalTriangles filters RandomAttributeGenerator AttributesConstantPerBlock filters RandomAttributeGenerator ComponentRange filters RandomAttributeGenerator DataType filters RandomAttributeGenerator GenerateCellScalars filters RandomAttributeGenerator GenerateCellVectors filters RandomAttributeGenerator GeneratePointScalars filters RandomAttributeGenerator GeneratePointVectors filters RandomAttributeGenerator Input filters RectilinearGridConnectivity AddDoubleVolumeArrayName filters RectilinearGridConnectivity AddFloatVolumeArrayName filters RectilinearGridConnectivity AddUnsignedCharVolumeArrayName filters RectilinearGridConnectivity Input filters RectilinearGridConnectivity VolumeFractionSurfaceValue filters RectilinearGridGeometryFilter Input filters RectilinearGridToPointSet Input filters ReductionFilter GenerateProcessIds filters ReductionFilter Input filters ReductionFilter PassThrough filters ReductionFilter PostGatherHelper filters ReductionFilter PostGatherHelperName filters ReductionFilter PreGatherHelper filters ReductionFilter PreGatherHelperName filters ReflectionFilter Center filters ReflectionFilter CopyInput filters ReflectionFilter Input filters ReflectionFilter Plane filters RibbonFilter Angle filters RibbonFilter DefaultNormal filters RibbonFilter Input filters RibbonFilter SelectInputScalars filters RibbonFilter SelectInputVectors filters RibbonFilter UseDefaultNormal filters RibbonFilter VaryWidth filters RibbonFilter Width filters RotationalExtrusionFilter Angle filters RotationalExtrusionFilter Capping filters RotationalExtrusionFilter DeltaRadius filters RotationalExtrusionFilter Input filters RotationalExtrusionFilter Resolution filters RotationalExtrusionFilter Translation filters ScatterPlot Input filters ShrinkFilter Input filters ShrinkFilter ShrinkFactor filters SliceAlongPolyLine Dataset filters SliceAlongPolyLine PolyLine filters SliceAlongPolyLine Tolerance filters SmoothPolyDataFilter Convergence filters SmoothPolyDataFilter Input filters SmoothPolyDataFilter NumberOfIterations filters StreakLine ComputeVorticity filters StreakLine DisableResetCache filters StreakLine ForceReinjectionEveryNSteps filters StreakLine Input filters StreakLine SelectInputVectors filters StreakLine Source filters StreakLine StaticMesh filters StreakLine StaticSeeds filters StreakLine TerminationTime filters StreakLine TimestepValues filters StreamTracer ComputeVorticity filters StreamTracer InitialIntegrationStep filters StreamTracer Input filters StreamTracer IntegrationDirection filters StreamTracer IntegrationStepUnit filters StreamTracer IntegratorType filters StreamTracer InterpolatorType filters StreamTracer MaximumError filters StreamTracer MaximumIntegrationStep filters StreamTracer MaximumNumberOfSteps filters StreamTracer MaximumPropagation filters StreamTracer MinimumIntegrationStep filters StreamTracer SelectInputVectors filters StreamTracer Source filters StreamTracer TerminalSpeed filters Stripper Input filters Stripper MaximumLength filters StructuredGridOutlineFilter Input filters Subdivide Input filters Subdivide NumberOfSubdivisions filters SurfaceVectors ConstraintMode filters SurfaceVectors Input filters SurfaceVectors SelectInputVectors filters TableFFT Input filters TableToPolyData Create2DPoints filters TableToPolyData Input filters TableToPolyData KeepAllDataArrays filters TableToPolyData XColumn filters TableToPolyData YColumn filters TableToPolyData ZColumn filters TableToStructuredGrid Input filters TableToStructuredGrid WholeExtent filters TableToStructuredGrid XColumn filters TableToStructuredGrid YColumn filters TableToStructuredGrid ZColumn filters TemporalCache CacheSize filters TemporalCache Input filters TemporalCache TimestepValues filters TemporalInterpolator DiscreteTimeStepInterval filters TemporalInterpolator Input filters TemporalInterpolator TimeRange filters TemporalInterpolator TimestepValues filters TemporalShiftScale Input filters TemporalShiftScale MaximumNumberOfPeriods filters TemporalShiftScale Periodic filters TemporalShiftScale PeriodicEndCorrection filters TemporalShiftScale PostShift filters TemporalShiftScale PreShift filters TemporalShiftScale Scale filters TemporalShiftScale TimestepValues filters TemporalSnapToTimeStep Input filters TemporalSnapToTimeStep SnapMode filters TemporalSnapToTimeStep TimestepValues filters TemporalStatistics ComputeAverage filters TemporalStatistics ComputeMaximum filters TemporalStatistics ComputeMinimum filters TemporalStatistics ComputeStandardDeviation filters TemporalStatistics Input filters TensorGlyph ColorGlyphs filters TensorGlyph ColorMode filters TensorGlyph ExtractEigenvalues filters TensorGlyph Input filters TensorGlyph LimitScalingByEigenvalues filters TensorGlyph MaxScaleFactor filters TensorGlyph ScaleFactor filters TensorGlyph SelectInputScalars filters TensorGlyph SelectInputTensors filters TensorGlyph Source filters TensorGlyph Symmetric filters TensorGlyph ThreeGlyphs filters TessellatorFilter ChordError filters TessellatorFilter FieldError2 filters TessellatorFilter Input filters TessellatorFilter MaximumNumberOfSubdivisions filters TessellatorFilter MergePoints filters TessellatorFilter OutputDimension filters TessellatorFilter ResetFieldCriteria filters TextureMapToCylinder Input filters TextureMapToCylinder PreventSeam filters TextureMapToPlane Input filters TextureMapToSphere Input filters TextureMapToSphere PreventSeam filters Threshold AllScalars filters Threshold Input filters Threshold SelectInputScalars filters Threshold ThresholdBetween filters Threshold UseContinuousCellRange filters TimeToTextConvertor Format filters TimeToTextConvertor Input filters TimeToTextConvertor Scale filters TimeToTextConvertor Shift filters TransformFilter Input filters TransformFilter Transform filters TransposeTable AddIdColumn filters TransposeTable DoNotTranspose filters TransposeTable Input filters TransposeTable SelectArrays filters TransposeTable UseIdColumn filters TriangleFilter Input filters TubeFilter Capping filters TubeFilter DefaultNormal filters TubeFilter Input filters TubeFilter NumberOfSides filters TubeFilter Radius filters TubeFilter RadiusFactor filters TubeFilter SelectInputScalars filters TubeFilter SelectInputVectors filters TubeFilter UseDefaultNormal filters TubeFilter VaryRadius filters UnstructuredGradient ComputeQCriterion filters UnstructuredGradient ComputeVorticity filters UnstructuredGradient FasterApproximation filters UnstructuredGradient Input filters UnstructuredGradient QCriterionArrayName filters UnstructuredGradient ResultArrayName filters UnstructuredGradient SelectInputScalars filters UnstructuredGradient VorticityArrayName filters UpdateSuppressor2 Enabled filters UpdateSuppressor2 ForceUpdate filters UpdateSuppressor2 Input filters UpdateSuppressor2 UpdateTime filters WarpScalar Input filters WarpScalar Normal filters WarpScalar ScaleFactor filters WarpScalar SelectInputScalars filters WarpScalar UseNormal filters WarpScalar XYPlane filters WarpVector Input filters WarpVector ScaleFactor filters WarpVector SelectInputVectors filters YoungsMaterialInterface AxisSymetric filters YoungsMaterialInterface FillMaterial filters YoungsMaterialInterface Input filters YoungsMaterialInterface InverseNormal filters YoungsMaterialInterface NormalArrays filters YoungsMaterialInterface NumberOfDomainsInformation filters YoungsMaterialInterface OnionPeel filters YoungsMaterialInterface OrderingArrays filters YoungsMaterialInterface ReverseMaterialOrder filters YoungsMaterialInterface UseFractionAsDistance filters YoungsMaterialInterface VolumeFractionArrays filters YoungsMaterialInterface VolumeFractionRange filters GlyphSpeed Input filters GlyphSpeed Scalars Traceback (most recent call last): File "", line 1, in File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/simple.py", line 39, in import servermanager File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", line 3185, in __initialize() File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", line 3176, in __initialize c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", line 1932, in __init__ _createModules(self.Modules) File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", line 2564, in _createModules m.filters = createModule('filters') File "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", line 2627, in createModule if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' >>> On Thu, Feb 26, 2015 at 3:06 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > It is believable, let me see if I can find a 10.10 here to reproduce > the problem. > > Another thing to try: > > 1. edit > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py" > 2. before line 2626, add the following: > print groupName, proxyName, propName > > Let's see which proxy this is failing for. > > Utkarsh > > > > > On Thu, Feb 26, 2015 at 3:53 PM, Matei Stroila > wrote: > > I do not have any plugin auto-loaded. Also I just tried now with the OS X > > default Python and I get the same errors. > > Could be a 10.10 issue? I built ParaView on a 10.9 machine yesterday > with no > > issues (ParaView from git, the release branch, 4.3.1). > > > > Matei > > > > On Thu, Feb 26, 2015 at 2:10 PM, Utkarsh Ayachit > > wrote: > >> > >> How was ParaView built? I am not sure if Homebrew Python is different > >> from the one packaged in OsX, but binaries on paraview.org are built > >> using OsX default Python. > >> > >> Also, do you have any plugins that are being auto-loaded? If you're > >> running pvpython, try running with "-dr" argument. That will avoid > >> loading any auto-load plugins. Does that help? > >> > >> Utkarsh > >> > >> On Thu, Feb 26, 2015 at 3:03 PM, Matei Stroila > > >> wrote: > >> > Not sure if other people have seen this. Using Python from Homebrew on > >> > Mac > >> > OS X 10.10, got the same error on two different Macs. > >> > > >> > Python 2.7.9 (default, Dec 19 2014, 06:00:59) > >> > > >> > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin > >> > > >> >>>> from paraview.simple import * > >> > > >> > Traceback (most recent call last): > >> > > >> > File "", line 1, in > >> > > >> > File > >> > > >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/simple.py", > >> > line 39, in > >> > > >> > import servermanager > >> > > >> > File > >> > > >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > >> > line 3184, in > >> > > >> > __initialize() > >> > > >> > File > >> > > >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > >> > line 3175, in __initialize > >> > > >> > c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) > >> > > >> > File > >> > > >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > >> > line 1932, in __init__ > >> > > >> > _createModules(self.Modules) > >> > > >> > File > >> > > >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > >> > line 2564, in _createModules > >> > > >> > m.filters = createModule('filters') > >> > > >> > File > >> > > >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > >> > line 2626, in createModule > >> > > >> > if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ > >> > > >> > AttributeError: 'NoneType' object has no attribute > 'GetInformationOnly' > >> > > >> >>>> > >> > > >> > Thanks for any suggestion. > >> > > >> > > >> > Matei > >> > > >> > > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > 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 26 16:55:20 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 26 Feb 2015 16:55:20 -0500 Subject: [Paraview] problem wirh python shell in Paraview 4.3.1 and Python 2.7.9 on Mac OS X 10.10 In-Reply-To: References: Message-ID: The "GlyphSpeed" filter seems to be the culprit. It's not a standard ParaView filter. Any ideas where it's coming from? I suspect it has a property named "Scalars" that is exposed, but doesn't really exist or something to that effect. Utkarsh On Thu, Feb 26, 2015 at 4:44 PM, Matei Stroila wrote: > Here is the output: > > > Python 2.7.6 (default, Sep 9 2014, 15:04:36) > > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.39)] on darwin > >>>> from paraview.simple import * > > sources AMRGaussianPulseSource Dimension > > sources AMRGaussianPulseSource PulseAmplitude > > sources AMRGaussianPulseSource RefinementRatio > > sources AMRGaussianPulseSource Root Spacing > > sources AMRGaussianPulseSource XPulseOrigin > > sources AMRGaussianPulseSource XPulseWidth > > sources AMRGaussianPulseSource YPulseOrigin > > sources AMRGaussianPulseSource YPulseWidth > > sources AMRGaussianPulseSource ZPulseOrigin > > sources AMRGaussianPulseSource ZPulseWidth > > sources AVSucdSeriesReader FileNameInfo > > sources AVSucdSeriesReader FileNames > > sources AVSucdSeriesReader TimestepValues > > sources AVSucdSeriesReader CellArrayInfo > > sources AVSucdSeriesReader CellArrayStatus > > sources AVSucdSeriesReader PointArrayInfo > > sources AVSucdSeriesReader PointArrayStatus > > sources ArrowSource Invert > > sources ArrowSource ShaftRadius > > sources ArrowSource ShaftResolution > > sources ArrowSource TipLength > > sources ArrowSource TipRadius > > sources ArrowSource TipResolution > > sources Axes Origin > > sources Axes ScaleFactor > > sources Axes Symmetric > > sources BlockSelectionSource Blocks > > sources BlockSelectionSource ContainingCells > > sources BlockSelectionSource FieldType > > sources BlockSelectionSource InsideOut > > sources CMLMoleculeReader FileName > > sources CSVReader FileName > > sources CSVReader FileNameInfo > > sources CSVReader TimestepValues > > sources CSVReader DetectNumericColumns > > sources CSVReader FieldDelimiterCharacters > > sources CSVReader HaveHeaders > > sources CSVReader MergeConsecutiveDelimiters > > sources CSVReader UseStringDelimiter > > sources CompositeDataIDSelectionSource ContainingCells > > sources CompositeDataIDSelectionSource FieldType > > sources CompositeDataIDSelectionSource IDs > > sources CompositeDataIDSelectionSource InsideOut > > sources ConeSource Capping > > sources ConeSource Center > > sources ConeSource Direction > > sources ConeSource Height > > sources ConeSource Radius > > sources ConeSource Resolution > > sources CubeSource Center > > sources CubeSource XLength > > sources CubeSource YLength > > sources CubeSource ZLength > > sources CylinderSource Capping > > sources CylinderSource Center > > sources CylinderSource Height > > sources CylinderSource Radius > > sources CylinderSource Resolution > > sources DEMReader FileName > > sources DICOMReader FileName > > sources DICOMReaderSingle FileName > > sources DataObjectGenerator Program > > sources DiskSource CircumferentialResolution > > sources DiskSource InnerRadius > > sources DiskSource OuterRadius > > sources DiskSource RadialResolution > > sources DistributedTrivialProducer UpdateDataset > > sources DistributedTrivialProducer WholeExtent > > sources EnzoParticlesReader FileNameInfo > > sources EnzoParticlesReader FileNames > > sources EnzoParticlesReader TimestepValues > > sources EnzoParticlesReader FilterLocation > > sources EnzoParticlesReader Frequency > > sources EnzoParticlesReader MaxLocation > > sources EnzoParticlesReader MinLocation > > sources EnzoParticlesReader NumParticles > > sources EnzoParticlesReader ParticleArrayStatus > > sources EnzoParticlesReader ParticleType > > sources EnzoReader FileNameInfo > > sources EnzoReader FileNames > > sources EnzoReader TimestepValues > > sources EnzoReader CellArrayStatus > > sources EnzoReader ConvertToCGS > > sources EnzoReader EnableCaching > > sources EnzoReader Level > > sources EnzoReader NumBlocks > > sources EnzoReader NumLevels > > sources EnzoReader PointArrayStatus > > sources ExodusIIReader FileName > > sources ExodusIIReader FileNameInfo > > sources ExodusIIReader TimestepValues > > sources ExodusIIReader UseMetaFile > > sources ExodusIIReader AnimateVibrations > > sources ExodusIIReader ApplyDisplacements > > sources ExodusIIReader DisplacementMagnitude > > sources ExodusIIReader EdgeBlocks > > sources ExodusIIReader EdgeBlocksInfo > > sources ExodusIIReader EdgeMapArrayStatus > > sources ExodusIIReader EdgeMapInfo > > sources ExodusIIReader EdgeSetArrayStatus > > sources ExodusIIReader EdgeSetInfo > > sources ExodusIIReader EdgeSetResultArrayInfo > > sources ExodusIIReader EdgeSetResultArrayStatus > > sources ExodusIIReader EdgeVariables > > sources ExodusIIReader EdgeVariablesInfo > > sources ExodusIIReader ElementBlocks > > sources ExodusIIReader ElementMapArrayStatus > > sources ExodusIIReader ElementMapInfo > > sources ExodusIIReader ElementSetArrayStatus > > sources ExodusIIReader ElementSetInfo > > sources ExodusIIReader ElementSetResultArrayInfo > > sources ExodusIIReader ElementSetResultArrayStatus > > sources ExodusIIReader ElementVariables > > sources ExodusIIReader ElementVariablesInfo > > sources ExodusIIReader FaceBlocks > > sources ExodusIIReader FaceBlocksInfo > > sources ExodusIIReader FaceMapArrayStatus > > sources ExodusIIReader FaceMapInfo > > sources ExodusIIReader FaceSetArrayStatus > > sources ExodusIIReader FaceSetInfo > > sources ExodusIIReader FaceSetResultArrayInfo > > sources ExodusIIReader FaceSetResultArrayStatus > > sources ExodusIIReader FaceVariables > > sources ExodusIIReader FaceVariablesInfo > > sources ExodusIIReader FilePattern > > sources ExodusIIReader FilePatternInfo > > sources ExodusIIReader FilePrefix > > sources ExodusIIReader FilePrefixInfo > > sources ExodusIIReader FileRange > > sources ExodusIIReader FileRangeInfo > > sources ExodusIIReader GenerateGlobalElementIdArray > > sources ExodusIIReader GenerateGlobalNodeIdArray > > sources ExodusIIReader GenerateObjectIdCellArray > > sources ExodusIIReader GlobalVariables > > sources ExodusIIReader GlobalVariablesInfo > > sources ExodusIIReader HasModeShapes > > sources ExodusIIReader ModeShape > > sources ExodusIIReader ModeShapesRangeInfo > > sources ExodusIIReader NodeMapArrayStatus > > sources ExodusIIReader NodeMapInfo > > sources ExodusIIReader NodeSetArrayStatus > > sources ExodusIIReader NodeSetInfo > > sources ExodusIIReader NodeSetResultArrayInfo > > sources ExodusIIReader NodeSetResultArrayStatus > > sources ExodusIIReader PointVariables > > sources ExodusIIReader PointVariablesInfo > > sources ExodusIIReader Refresh > > sources ExodusIIReader SILUpdateStamp > > sources ExodusIIReader SideSetArrayStatus > > sources ExodusIIReader SideSetInfo > > sources ExodusIIReader SideSetResultArrayInfo > > sources ExodusIIReader SideSetResultArrayStatus > > sources ExodusIIReader XMLFileName > > sources ExodusIIReader XMLFileNameInfo > > sources ExodusRestartReader FileName > > sources ExodusRestartReader FileNameInfo > > sources ExodusRestartReader TimestepValues > > sources ExodusRestartReader UseMetaFile > > sources ExodusRestartReader AnimateVibrations > > sources ExodusRestartReader ApplyDisplacements > > sources ExodusRestartReader DisplacementMagnitude > > sources ExodusRestartReader EdgeBlocks > > sources ExodusRestartReader EdgeBlocksInfo > > sources ExodusRestartReader EdgeMapArrayStatus > > sources ExodusRestartReader EdgeMapInfo > > sources ExodusRestartReader EdgeSetArrayStatus > > sources ExodusRestartReader EdgeSetInfo > > sources ExodusRestartReader EdgeSetResultArrayInfo > > sources ExodusRestartReader EdgeSetResultArrayStatus > > sources ExodusRestartReader EdgeVariables > > sources ExodusRestartReader EdgeVariablesInfo > > sources ExodusRestartReader ElementBlocks > > sources ExodusRestartReader ElementMapArrayStatus > > sources ExodusRestartReader ElementMapInfo > > sources ExodusRestartReader ElementSetArrayStatus > > sources ExodusRestartReader ElementSetInfo > > sources ExodusRestartReader ElementSetResultArrayInfo > > sources ExodusRestartReader ElementSetResultArrayStatus > > sources ExodusRestartReader ElementVariables > > sources ExodusRestartReader ElementVariablesInfo > > sources ExodusRestartReader FaceBlocks > > sources ExodusRestartReader FaceBlocksInfo > > sources ExodusRestartReader FaceMapArrayStatus > > sources ExodusRestartReader FaceMapInfo > > sources ExodusRestartReader FaceSetArrayStatus > > sources ExodusRestartReader FaceSetInfo > > sources ExodusRestartReader FaceSetResultArrayInfo > > sources ExodusRestartReader FaceSetResultArrayStatus > > sources ExodusRestartReader FaceVariables > > sources ExodusRestartReader FaceVariablesInfo > > sources ExodusRestartReader FilePattern > > sources ExodusRestartReader FilePatternInfo > > sources ExodusRestartReader FilePrefix > > sources ExodusRestartReader FilePrefixInfo > > sources ExodusRestartReader FileRange > > sources ExodusRestartReader FileRangeInfo > > sources ExodusRestartReader GenerateGlobalElementIdArray > > sources ExodusRestartReader GenerateGlobalNodeIdArray > > sources ExodusRestartReader GenerateObjectIdCellArray > > sources ExodusRestartReader GlobalVariables > > sources ExodusRestartReader GlobalVariablesInfo > > sources ExodusRestartReader HasModeShapes > > sources ExodusRestartReader ModeShape > > sources ExodusRestartReader ModeShapesRangeInfo > > sources ExodusRestartReader NodeMapArrayStatus > > sources ExodusRestartReader NodeMapInfo > > sources ExodusRestartReader NodeSetArrayStatus > > sources ExodusRestartReader NodeSetInfo > > sources ExodusRestartReader NodeSetResultArrayInfo > > sources ExodusRestartReader NodeSetResultArrayStatus > > sources ExodusRestartReader PointVariables > > sources ExodusRestartReader PointVariablesInfo > > sources ExodusRestartReader Refresh > > sources ExodusRestartReader SILUpdateStamp > > sources ExodusRestartReader SideSetArrayStatus > > sources ExodusRestartReader SideSetInfo > > sources ExodusRestartReader SideSetResultArrayInfo > > sources ExodusRestartReader SideSetResultArrayStatus > > sources ExodusRestartReader XMLFileName > > sources ExodusRestartReader XMLFileNameInfo > > sources FLUENTReader FileName > > sources FLUENTReader CellArrayInfo > > sources FLUENTReader CellArrayStatus > > sources FacetReader FileName > > sources FlashParticlesReader FileNameInfo > > sources FlashParticlesReader FileNames > > sources FlashParticlesReader TimestepValues > > sources FlashParticlesReader FilterLocation > > sources FlashParticlesReader Frequency > > sources FlashParticlesReader MaxLocation > > sources FlashParticlesReader MinLocation > > sources FlashParticlesReader NumParticles > > sources FlashParticlesReader ParticleArrayStatus > > sources FlashReader FileNameInfo > > sources FlashReader FileNames > > sources FlashReader TimestepValues > > sources FlashReader CellArrayStatus > > sources FlashReader EnableCaching > > sources FlashReader Level > > sources FlashReader NumBlocks > > sources FlashReader NumLevels > > sources FlashReader PointArrayStatus > > sources FrustumSelectionSource ContainingCells > > sources FrustumSelectionSource FieldType > > sources FrustumSelectionSource Frustum > > sources FrustumSelectionSource InsideOut > > sources GlobalIDSelectionSource ContainingCells > > sources GlobalIDSelectionSource FieldType > > sources GlobalIDSelectionSource IDs > > sources GlobalIDSelectionSource InsideOut > > sources GlyphSource2D Center > > sources GlyphSource2D Filled > > sources GlyphSource2D GlyphType > > sources HierarchicalDataIDSelectionSource ContainingCells > > sources HierarchicalDataIDSelectionSource FieldType > > sources HierarchicalDataIDSelectionSource IDs > > sources HierarchicalDataIDSelectionSource InsideOut > > sources HierarchicalFractal Asymetric > > sources HierarchicalFractal Dimensions > > sources HierarchicalFractal FractalValue > > sources HierarchicalFractal GhostLevels > > sources HierarchicalFractal MaximumLevel > > sources HierarchicalFractal RectilinearGrids > > sources HierarchicalFractal TimeStep > > sources HierarchicalFractal TimeStepRangeInfo > > sources HierarchicalFractal TwoDimensional > > sources HyperTreeGridSource BranchFactor > > sources HyperTreeGridSource Descriptor > > sources HyperTreeGridSource Dimension > > sources HyperTreeGridSource GridScale > > sources HyperTreeGridSource GridSize > > sources HyperTreeGridSource MaximumLevel > > sources IDSelectionSource ContainingCells > > sources IDSelectionSource FieldType > > sources IDSelectionSource IDs > > sources IDSelectionSource InsideOut > > sources ImageMandelbrotSource MaximumNumberOfIterations > > sources ImageMandelbrotSource OriginCX > > sources ImageMandelbrotSource ProjectionAxes > > sources ImageMandelbrotSource SizeCX > > sources ImageMandelbrotSource SubsampleRate > > sources ImageMandelbrotSource WholeExtent > > sources ImageReader DataByteOrder > > sources ImageReader DataExtent > > sources ImageReader DataOrigin > > sources ImageReader DataScalarType > > sources ImageReader DataSpacing > > sources ImageReader FileDimensionality > > sources ImageReader FileLowerLeft > > sources ImageReader FilePattern > > sources ImageReader FilePrefix > > sources ImageReader NumberOfScalarComponents > > sources ImageReader ScalarArrayName > > sources JPEGSeriesReader FileNames > > sources JPEGSeriesReader TimestepValues > > sources LSDynaReader BeamArrayInfo > > sources LSDynaReader BeamArrayStatus > > sources LSDynaReader DeformedMesh > > sources LSDynaReader FileName > > sources LSDynaReader PartArrayInfo > > sources LSDynaReader PartArrayStatus > > sources LSDynaReader ParticleArrayInfo > > sources LSDynaReader ParticleArrayStatus > > sources LSDynaReader PointArrayInfo > > sources LSDynaReader PointArrayStatus > > sources LSDynaReader RemoveDeletedCells > > sources LSDynaReader RigidBodyArrayInfo > > sources LSDynaReader RigidBodyArrayStatus > > sources LSDynaReader RoadSurfaceArrayInfo > > sources LSDynaReader RoadSurfaceArrayStatus > > sources LSDynaReader ShellArrayInfo > > sources LSDynaReader ShellArrayStatus > > sources LSDynaReader SolidArrayInfo > > sources LSDynaReader SolidArrayStatus > > sources LSDynaReader ThickShellArrayInfo > > sources LSDynaReader ThickShellArrayStatus > > sources LSDynaReader TimestepValues > > sources LegacyVTKFileReader FileNameInfo > > sources LegacyVTKFileReader FileNames > > sources LegacyVTKFileReader TimestepValues > > sources LineSource Point1 > > sources LineSource Point2 > > sources LineSource Resolution > > sources LocationSelectionSource ContainingCells > > sources LocationSelectionSource FieldType > > sources LocationSelectionSource InsideOut > > sources LocationSelectionSource Locations > > sources MFIXReader CellArrayInfo > > sources MFIXReader CellArrayStatus > > sources MFIXReader FileName > > sources MFIXReader TimestepValues > > sources MPASReader CellArrayInfo > > sources MPASReader CellArrayStatus > > sources MPASReader CenterLon > > sources MPASReader CenterLonRangeInfo > > sources MPASReader FileName > > sources MPASReader IsAtmosphere > > sources MPASReader LayerThickness > > sources MPASReader LayerThicknessRangeInfo > > sources MPASReader PointArrayInfo > > sources MPASReader PointArrayStatus > > sources MPASReader ProjectLatLon > > sources MPASReader ShowMultilayerView > > sources MPASReader TimestepValues > > sources MPASReader VerticalLevel > > sources MPASReader VerticalLevelRangeInfo > > sources MetaImageReader FileNameInfo > > sources MetaImageReader FileNames > > sources MetaImageReader TimestepValues > > sources MultiServerProxy DependencyLink > > sources NetCDFCAMReader FileName > > sources NetCDFCAMReader FileNameInfo > > sources NetCDFCAMReader TimestepValues > > sources NetCDFCAMReader CellLayerRight > > sources NetCDFCAMReader ConnectivityFileName > > sources NetCDFCAMReader SingleLevel > > sources NetCDFPOPReader FileName > > sources NetCDFPOPReader FileNameInfo > > sources NetCDFPOPReader TimestepValues > > sources NetCDFPOPReader Stride > > sources NetCDFPOPReader VariableArrayInfo > > sources NetCDFPOPReader VariableArrayStatus > > sources NetworkImageSource FileName > > sources NrrdReader DataVOI > > sources NrrdReader FileName > > sources OctreeFractal Dimension > > sources OctreeFractal MaximumLevel > > sources OctreeFractal MaximumNumberOfIterations > > sources OctreeFractal MinimumLevel > > sources OctreeFractal OriginCX > > sources OctreeFractal ProjectionAxes > > sources OctreeFractal SizeCX > > sources OctreeFractal Threshold > > sources OpenFOAMReader AddDimensionsToArrayNames > > sources OpenFOAMReader CacheMesh > > sources OpenFOAMReader CaseType > > sources OpenFOAMReader CellArrayInfo > > sources OpenFOAMReader CellArrays > > sources OpenFOAMReader CreateCellToPoint > > sources OpenFOAMReader DecomposePolyhedra > > sources OpenFOAMReader FileName > > sources OpenFOAMReader LagrangianArrayInfo > > sources OpenFOAMReader LagrangianArrays > > sources OpenFOAMReader ListTimeStepsByControlDict > > sources OpenFOAMReader MeshRegions > > sources OpenFOAMReader PatchArrayInfo > > sources OpenFOAMReader PointArrayInfo > > sources OpenFOAMReader PointArrays > > sources OpenFOAMReader PositionsIsIn13Format > > sources OpenFOAMReader ReadZones > > sources OpenFOAMReader Refresh > > sources OpenFOAMReader TimestepValues > > sources OutlineSource Bounds > > sources P3DReader FileNameInfo > > sources P3DReader QFileName > > sources P3DReader TimestepValues > > sources P3DReader AutoDetectFormat > > sources P3DReader BinaryFile > > sources P3DReader ByteOrder > > sources P3DReader DoublePrecision > > sources P3DReader FileName > > sources P3DReader ForceRead > > sources P3DReader FunctionFileName > > sources P3DReader Functions > > sources P3DReader HasByteCount > > sources P3DReader IBlanking > > sources P3DReader MultiGrid > > sources P3DReader TwoDimensionalGeometry > > sources PNGSeriesReader FileNames > > sources PNGSeriesReader TimestepValues > > sources PVDReader FileName > > sources PVDReader TimestepValues > > sources PVTrivialProducer WholeExtent > > sources ParticleReader FileName > > sources ParticleReader FileNameInfo > > sources ParticleReader TimestepValues > > sources ParticleReader ByteOrder > > sources ParticleReader DataType > > sources ParticleReader FileType > > sources ParticleReader HasScalar > > sources PedigreeIDSelectionSource ContainingCells > > sources PedigreeIDSelectionSource FieldType > > sources PedigreeIDSelectionSource IDs > > sources PedigreeIDSelectionSource InsideOut > > sources PedigreeIDSelectionSource StringIDs > > sources PhastaReader FileName > > sources PhastaReader TimestepValues > > sources PlaneSource Origin > > sources PlaneSource Point1 > > sources PlaneSource Point2 > > sources PlaneSource XResolution > > sources PlaneSource YResolution > > sources Plot3DMetaReader FileName > > sources Plot3DMetaReader TimestepValues > > sources PointSource Center > > sources PointSource NumberOfPoints > > sources PointSource Radius > > sources ProStarReader FileName > > sources ProStarReader ScaleFactor > > sources ProgrammableSource InformationScript > > sources ProgrammableSource OutputDataSetType > > sources ProgrammableSource Parameters > > sources ProgrammableSource PythonPath > > sources ProgrammableSource Script > > sources RTAnalyticSource Center > > sources RTAnalyticSource Maximum > > sources RTAnalyticSource StandardDeviation > > sources RTAnalyticSource SubsampleRate > > sources RTAnalyticSource WholeExtent > > sources RTAnalyticSource XFreq > > sources RTAnalyticSource XMag > > sources RTAnalyticSource YFreq > > sources RTAnalyticSource YMag > > sources RTAnalyticSource ZFreq > > sources RTAnalyticSource ZMag > > sources RTXMLPolyDataReader FileName > > sources RTXMLPolyDataReader Location > > sources RTXMLPolyDataReader NewDataAvailable > > sources RTXMLPolyDataReader NextFileName > > sources RTXMLPolyDataReader ResetReader > > sources RTXMLPolyDataReader UpdateToNextFile > > sources Ruler Point1 > > sources Ruler Point2 > > sources SLACParticleReader FileName > > sources SLACParticleReader TimestepValues > > sources SLACReader FrequencyScale > > sources SLACReader FrequencyScaleInfo > > sources SLACReader MeshFileName > > sources SLACReader ModeFileName > > sources SLACReader PhaseShift > > sources SLACReader PhaseShiftInfo > > sources SLACReader ReadExternalSurface > > sources SLACReader ReadInternalVolume > > sources SLACReader ReadMidpoints > > sources SLACReader TimeRange > > sources SLACReader TimestepValues > > sources SPCTHRestartReader FileName > > sources SPCTHRestartReader TimestepValues > > sources SPCTHRestartReader UseMetaFile > > sources SPCTHRestartReader CellArrayInfo > > sources SPCTHRestartReader CellArrayStatus > > sources SPCTHRestartReader DistributeFiles > > sources SPCTHRestartReader DownConvertVolumeFraction > > sources SPCTHRestartReader GenerateActiveBlockArray > > sources SPCTHRestartReader GenerateBlockIdArray > > sources SPCTHRestartReader GenerateLevelArray > > sources SPCTHRestartReader GenerateMarkers > > sources SPCTHRestartReader GenerateTracers > > sources SelectionQuerySource CompositeIndex > > sources SelectionQuerySource FieldType > > sources SelectionQuerySource HierarchicalIndex > > sources SelectionQuerySource HierarchicalLevel > > sources SelectionQuerySource InsideOut > > sources SelectionQuerySource ProcessID > > sources SelectionQuerySource QueryString > > sources SelectionQuerySource UserFriendlyText > > sources SelectionSourceBase ContainingCells > > sources SelectionSourceBase FieldType > > sources SelectionSourceBase InsideOut > > sources SphereSource Center > > sources SphereSource EndPhi > > sources SphereSource EndTheta > > sources SphereSource PhiResolution > > sources SphereSource Radius > > sources SphereSource StartPhi > > sources SphereSource StartTheta > > sources SphereSource ThetaResolution > > sources SplineSource ParametricFunction > > sources SuperquadricSource Center > > sources SuperquadricSource PhiResolution > > sources SuperquadricSource PhiRoundness > > sources SuperquadricSource Scale > > sources SuperquadricSource Size > > sources SuperquadricSource ThetaResolution > > sources SuperquadricSource ThetaRoundness > > sources SuperquadricSource Thickness > > sources SuperquadricSource Toroidal > > sources TIFFReader FileName > > sources TIFFSeriesReader FileNames > > sources TIFFSeriesReader TimestepValues > > sources TecplotReader FileNameInfo > > sources TecplotReader FileNames > > sources TecplotReader TimestepValues > > sources TecplotReader DataArrayInfo > > sources TecplotReader DataArrayStatus > > sources Test3DWidget Resolution > > sources TextSource Text > > sources ThresholdSelectionSource ArrayName > > sources ThresholdSelectionSource ContainingCells > > sources ThresholdSelectionSource FieldType > > sources ThresholdSelectionSource InsideOut > > sources ThresholdSelectionSource Thresholds > > sources TimeSource Analytic > > sources TimeSource Growing > > sources TimeSource TimestepValues > > sources TimeSource X Amplitude > > sources TimeSource Y Amplitude > > sources TimeToTextConvertorSource Format > > sources UnstructuredPOPReader FileName > > sources UnstructuredPOPReader FileNameInfo > > sources UnstructuredPOPReader TimestepValues > > sources UnstructuredPOPReader Stride > > sources UnstructuredPOPReader VOI > > sources UnstructuredPOPReader VerticalVelocity > > sources VPICReader DefaultXExtent > > sources VPICReader DefaultYExtent > > sources VPICReader DefaultZExtent > > sources VPICReader FileName > > sources VPICReader PointArrayInfo > > sources VPICReader PointArrayStatus > > sources VPICReader SetStride > > sources VPICReader TimestepValues > > sources VPICReader XExtent > > sources VPICReader YExtent > > sources VPICReader ZExtent > > sources VectorText Text > > sources WindBladeReader Filename > > sources WindBladeReader PointArrayInfo > > sources WindBladeReader PointArrayStatus > > sources WindBladeReader TimestepValues > > sources XMLHierarchicalBoxDataReader FileName > > sources XMLHierarchicalBoxDataReader FileNameInfo > > sources XMLHierarchicalBoxDataReader TimestepValues > > sources XMLImageDataReader FileName > > sources XMLImageDataReader FileNameInfo > > sources XMLImageDataReader TimestepValues > > sources XMLImageDataReader CellArrayInfo > > sources XMLImageDataReader CellArrayStatus > > sources XMLImageDataReader PointArrayInfo > > sources XMLImageDataReader PointArrayStatus > > sources XMLMultiBlockDataReader FileName > > sources XMLMultiBlockDataReader FileNameInfo > > sources XMLMultiBlockDataReader TimestepValues > > sources XMLPImageDataReader FileName > > sources XMLPImageDataReader FileNameInfo > > sources XMLPImageDataReader TimestepValues > > sources XMLPImageDataReader CellArrayInfo > > sources XMLPImageDataReader CellArrayStatus > > sources XMLPImageDataReader PointArrayInfo > > sources XMLPImageDataReader PointArrayStatus > > sources XMLPPolyDataReader FileName > > sources XMLPPolyDataReader FileNameInfo > > sources XMLPPolyDataReader TimestepValues > > sources XMLPPolyDataReader CellArrayInfo > > sources XMLPPolyDataReader CellArrayStatus > > sources XMLPPolyDataReader PointArrayInfo > > sources XMLPPolyDataReader PointArrayStatus > > sources XMLPRectilinearGridReader FileName > > sources XMLPRectilinearGridReader FileNameInfo > > sources XMLPRectilinearGridReader TimestepValues > > sources XMLPRectilinearGridReader CellArrayInfo > > sources XMLPRectilinearGridReader CellArrayStatus > > sources XMLPRectilinearGridReader PointArrayInfo > > sources XMLPRectilinearGridReader PointArrayStatus > > sources XMLPStructuredGridReader FileName > > sources XMLPStructuredGridReader FileNameInfo > > sources XMLPStructuredGridReader TimestepValues > > sources XMLPStructuredGridReader CellArrayInfo > > sources XMLPStructuredGridReader CellArrayStatus > > sources XMLPStructuredGridReader PointArrayInfo > > sources XMLPStructuredGridReader PointArrayStatus > > sources XMLPUnstructuredGridReader FileName > > sources XMLPUnstructuredGridReader FileNameInfo > > sources XMLPUnstructuredGridReader TimestepValues > > sources XMLPUnstructuredGridReader CellArrayInfo > > sources XMLPUnstructuredGridReader CellArrayStatus > > sources XMLPUnstructuredGridReader PointArrayInfo > > sources XMLPUnstructuredGridReader PointArrayStatus > > sources XMLPolyDataEnsembleReader FileIndex > > sources XMLPolyDataEnsembleReader FileIndexRange > > sources XMLPolyDataEnsembleReader MetaFileName > > sources XMLPolyDataEnsembleReader TimestepValues > > sources XMLPolyDataEnsembleReader CellArrayInfo > > sources XMLPolyDataEnsembleReader CellArrayStatus > > sources XMLPolyDataEnsembleReader PointArrayInfo > > sources XMLPolyDataEnsembleReader PointArrayStatus > > sources XMLPolyDataEnsembleReader UseMetaFile > > sources XMLPolyDataReader FileName > > sources XMLPolyDataReader FileNameInfo > > sources XMLPolyDataReader TimestepValues > > sources XMLPolyDataReader CellArrayInfo > > sources XMLPolyDataReader CellArrayStatus > > sources XMLPolyDataReader PointArrayInfo > > sources XMLPolyDataReader PointArrayStatus > > sources XMLRectilinearGridReader FileName > > sources XMLRectilinearGridReader FileNameInfo > > sources XMLRectilinearGridReader TimestepValues > > sources XMLRectilinearGridReader CellArrayInfo > > sources XMLRectilinearGridReader CellArrayStatus > > sources XMLRectilinearGridReader PointArrayInfo > > sources XMLRectilinearGridReader PointArrayStatus > > sources XMLStructuredGridReader FileName > > sources XMLStructuredGridReader FileNameInfo > > sources XMLStructuredGridReader TimestepValues > > sources XMLStructuredGridReader CellArrayInfo > > sources XMLStructuredGridReader CellArrayStatus > > sources XMLStructuredGridReader PointArrayInfo > > sources XMLStructuredGridReader PointArrayStatus > > sources XMLUniformGridAMRReader FileName > > sources XMLUniformGridAMRReader FileNameInfo > > sources XMLUniformGridAMRReader TimestepValues > > sources XMLUniformGridAMRReader DefaultNumberOfLevels > > sources XMLUnstructuredGridReader FileName > > sources XMLUnstructuredGridReader FileNameInfo > > sources XMLUnstructuredGridReader TimestepValues > > sources XMLUnstructuredGridReader CellArrayInfo > > sources XMLUnstructuredGridReader CellArrayStatus > > sources XMLUnstructuredGridReader PointArrayInfo > > sources XMLUnstructuredGridReader PointArrayStatus > > sources XdmfReader FileNameInfo > > sources XdmfReader FileNames > > sources XdmfReader TimestepValues > > sources XdmfReader CellArrayInfo > > sources XdmfReader CellArrayStatus > > sources XdmfReader GridInfo > > sources XdmfReader GridStatus > > sources XdmfReader PointArrayInfo > > sources XdmfReader PointArrayStatus > > sources XdmfReader SILTimeStamp > > sources XdmfReader SetInfo > > sources XdmfReader SetStatus > > sources XdmfReader Stride > > sources byureader FileName > > sources ensight CaseFileName > > sources ensight CellArrayInfo > > sources ensight CellArrayStatus > > sources ensight PointArrayInfo > > sources ensight PointArrayStatus > > sources ensight TimestepValues > > sources ensightMS ByteOrder > > sources ensightMS CaseFileName > > sources ensightMS CellArrayInfo > > sources ensightMS CellArrayStatus > > sources ensightMS PointArrayInfo > > sources ensightMS PointArrayStatus > > sources ensightMS SetTimeValue > > sources ensightMS TimestepValues > > sources gaussiancubereader BScale > > sources gaussiancubereader FileName > > sources gaussiancubereader HBScale > > sources netCDFReader FileName > > sources netCDFReader TimestepValues > > sources netCDFReader DimensionInfo > > sources netCDFReader Dimensions > > sources netCDFReader OutputType > > sources netCDFReader ReplaceFillValueWithNan > > sources netCDFReader SphericalCoordinates > > sources netCDFReader VariableArrayInfo > > sources netCDFReader VariableDimensionInfo > > sources netCDFReader VerticalBias > > sources netCDFReader VerticalScale > > sources objreader FileName > > sources pdbreader FileName > > sources plyreader FileName > > sources pvtkfile FileName > > sources spcthhistoryreader CommentCharacter > > sources spcthhistoryreader Delimeter > > sources spcthhistoryreader FileName > > sources spcthhistoryreader TimestepValues > > sources spcthreader CellArrayInfo > > sources spcthreader CellArrayStatus > > sources spcthreader ComputeDerivedVariables > > sources spcthreader DistributeFiles > > sources spcthreader DownConvertVolumeFraction > > sources spcthreader FileName > > sources spcthreader GenerateActiveBlockArray > > sources spcthreader GenerateBlockIdArray > > sources spcthreader GenerateLevelArray > > sources spcthreader GenerateMarkers > > sources spcthreader GenerateTracers > > sources spcthreader MergeXYZComponents > > sources spcthreader TimestepValues > > sources stlreader FileNameInfo > > sources stlreader FileNames > > sources stlreader TimestepValues > > sources vrmlreader FileName > > sources xyzreader FileName > > sources xyzreader TimeStep > > filters AMRConnectivity Input > > filters AMRConnectivity Propagate Ghosts > > filters AMRConnectivity Resolve Blocks > > filters AMRConnectivity SelectMaterialArrays > > filters AMRConnectivity VolumeFractionSurfaceValue > > filters AMRCutPlane Center > > filters AMRCutPlane Input > > filters AMRCutPlane LevelOfResolution > > filters AMRCutPlane Normal > > filters AMRCutPlane UseNativeCutter > > filters AMRDualClip Input > > filters AMRDualClip InternalDecimation > > filters AMRDualClip MergePoints > > filters AMRDualClip MultiprocessCommunication > > filters AMRDualClip SelectMaterialArrays > > filters AMRDualClip VolumeFractionSurfaceValue > > filters AMRDualContour Capping > > filters AMRDualContour DegenerateCells > > filters AMRDualContour Input > > filters AMRDualContour MergePoints > > filters AMRDualContour MultiprocessCommunication > > filters AMRDualContour SelectMaterialArrays > > filters AMRDualContour SkipGhostCopy > > filters AMRDualContour Triangulate > > filters AMRDualContour VolumeFractionSurfaceValue > > filters AMRFragmentIntegration Input > > filters AMRFragmentIntegration SelectMassArrays > > filters AMRFragmentIntegration SelectMassWeightedArrays > > filters AMRFragmentIntegration SelectMaterialArrays > > filters AMRFragmentIntegration SelectVolumeWeightedArrays > > filters AMRFragmentsFilter Extract Surface > > filters AMRFragmentsFilter Input > > filters AMRFragmentsFilter Integrate Fragments > > filters AMRFragmentsFilter SelectMassArrays > > filters AMRFragmentsFilter SelectMassWeightedArrays > > filters AMRFragmentsFilter SelectMaterialArrays > > filters AMRFragmentsFilter SelectVolumeWeightedArrays > > filters AMRFragmentsFilter Use Watertight Surface > > filters AMRFragmentsFilter VolumeFractionSurfaceValue > > filters AMRResampleFilter Demand-Driven Mode > > filters AMRResampleFilter Input > > filters AMRResampleFilter Max > > filters AMRResampleFilter Min > > filters AMRResampleFilter Number of Samples > > filters AMRResampleFilter NumberOfPartitions > > filters AMRResampleFilter TransferToNodes > > filters AMRSlice EnablePrefetching > > filters AMRSlice ForwardUpstream > > filters AMRSlice Input > > filters AMRSlice Level > > filters AMRSlice Normal > > filters AMRSlice OffSet > > filters AMRToMultiBlock Input > > filters AnnotateAttributeData ArrayAssociation > > filters AnnotateAttributeData ArrayName > > filters AnnotateAttributeData ElementId > > filters AnnotateAttributeData Input > > filters AnnotateAttributeData Prefix > > filters AnnotateAttributeData ProcessId > > filters AnnotateGlobalData Input > > filters AnnotateGlobalData Prefix > > filters AnnotateGlobalData SelectArrays > > filters Append Input > > filters AppendAttributes Input > > filters AppendPolyData Input > > filters ArbitrarySourceStreamTracer ComputeVorticity > > filters ArbitrarySourceStreamTracer InitialIntegrationStep > > filters ArbitrarySourceStreamTracer Input > > filters ArbitrarySourceStreamTracer IntegrationDirection > > filters ArbitrarySourceStreamTracer IntegrationStepUnit > > filters ArbitrarySourceStreamTracer IntegratorType > > filters ArbitrarySourceStreamTracer MaximumError > > filters ArbitrarySourceStreamTracer MaximumIntegrationStep > > filters ArbitrarySourceStreamTracer MaximumNumberOfSteps > > filters ArbitrarySourceStreamTracer MaximumPropagation > > filters ArbitrarySourceStreamTracer MinimumIntegrationStep > > filters ArbitrarySourceStreamTracer SelectInputVectors > > filters ArbitrarySourceStreamTracer Source > > filters ArbitrarySourceStreamTracer TerminalSpeed > > filters AttributeDataToTableFilter AddMetaData > > filters AttributeDataToTableFilter FieldAssociation > > filters AttributeDataToTableFilter Input > > filters BlockIdScalars Input > > filters BrownianPoints Input > > filters BrownianPoints MaximumSpeed > > filters BrownianPoints MinimumSpeed > > filters CTHPart CapSurfaces > > filters CTHPart ClipPlane > > filters CTHPart GenerateTriangles > > filters CTHPart Input > > filters CTHPart RemoveGhostCells > > filters CTHPart VolumeArrays > > filters CTHPart VolumeFractionSurfaceValue > > filters CTHSurface Input > > filters CacheKeeper CacheTime > > filters CacheKeeper CachingEnabled > > filters CacheKeeper Input > > filters CacheKeeper RemoveAllCaches > > filters Calculator AttributeMode > > filters Calculator CoordinateResults > > filters Calculator Function > > filters Calculator Input > > filters Calculator ReplaceInvalidValues > > filters Calculator ReplacementValue > > filters Calculator ResultArrayName > > filters Calculator ResultNormals > > filters Calculator ResultTCoords > > filters CellCenters Input > > filters CellCenters VertexCells > > filters CellDataToPointData Input > > filters CellDataToPointData PassCellData > > filters CellDataToPointData PieceInvariant > > filters CellDerivatives Input > > filters CellDerivatives OutputTensorType > > filters CellDerivatives OutputVectorType > > filters CellDerivatives SelectInputScalars > > filters CellDerivatives SelectInputVectors > > filters CleanPolyData AbsoluteTolerance > > filters CleanPolyData ConvertLinesToPoints > > filters CleanPolyData ConvertPolysToLines > > filters CleanPolyData ConvertStripsToPolys > > filters CleanPolyData Input > > filters CleanPolyData PieceInvariant > > filters CleanPolyData PointMerging > > filters CleanPolyData Tolerance > > filters CleanPolyData ToleranceIsAbsolute > > filters CleanUnstructuredGrid Input > > filters CleanUnstructuredGridCells Input > > filters ClientServerMoveData Input > > filters ClientServerMoveData OutputDataType > > filters ClientServerMoveData WholeExtent > > filters Clip ClipFunction > > filters Clip Input > > filters Clip InputBounds > > filters Clip InsideOut > > filters Clip PreserveInputCells > > filters Clip SelectInputScalars > > filters Clip UseValueAsOffset > > filters Clip Value > > filters ClipClosedSurface BaseColor > > filters ClipClosedSurface ClipColor > > filters ClipClosedSurface ClippingPlane > > filters ClipClosedSurface GenerateFaces > > filters ClipClosedSurface GenerateOutline > > filters ClipClosedSurface Input > > filters ClipClosedSurface InsideOut > > filters ClipClosedSurface ScalarMode > > filters ClipClosedSurface Tolerance > > filters ColorByArray Input > > filters ColorByArray LookupTable > > filters ColorByArray NaNColor > > filters ColorByArray OutputFormat > > filters ColorByArray SelectInputScalars > > filters ComputeQuartiles Input > > filters ContingencyStatistics AttributeMode > > filters ContingencyStatistics Input > > filters ContingencyStatistics ModelInput > > filters ContingencyStatistics SelectArrays > > filters ContingencyStatistics Task > > filters ContingencyStatistics TrainingFraction > > filters Contour ComputeGradients > > filters Contour ComputeNormals > > filters Contour ComputeScalars > > filters Contour ContourValues > > filters Contour GenerateTriangles > > filters Contour Input > > filters Contour Locator > > filters Contour SelectInputScalars > > filters ConvertSelection ArrayNames > > filters ConvertSelection DataInput > > filters ConvertSelection Input > > filters ConvertSelection MatchAnyValues > > filters ConvertSelection OutputType > > filters Curvatures CurvatureType > > filters Curvatures Input > > filters Curvatures InvertMeanCurvature > > filters Cut ContourValues > > filters Cut CutFunction > > filters Cut Input > > filters Cut InputBounds > > filters Cut PreserveInputCells > > filters Cut Triangulate the slice > > filters CutEverything ContourValues > > filters CutEverything CutFunction > > filters CutEverything Input > > filters CutEverything InputBounds > > filters DataSetSurfaceFilter Input > > filters DataSetSurfaceFilter NonlinearSubdivisionLevel > > filters DataSetSurfaceFilter PieceInvariant > > filters DataSetTriangleFilter Input > > filters DecimatePro BoundaryVertexDeletion > > filters DecimatePro FeatureAngle > > filters DecimatePro Input > > filters DecimatePro PreserveTopology > > filters DecimatePro TargetReduction > > filters Delaunay2D Alpha > > filters Delaunay2D BoundingTriangulation > > filters Delaunay2D Input > > filters Delaunay2D Offset > > filters Delaunay2D ProjectionPlaneMode > > filters Delaunay2D Tolerance > > filters Delaunay3D Alpha > > filters Delaunay3D AlphaLines > > filters Delaunay3D AlphaTets > > filters Delaunay3D AlphaTris > > filters Delaunay3D AlphaVerts > > filters Delaunay3D BoundingTriangulation > > filters Delaunay3D Input > > filters Delaunay3D Offset > > filters Delaunay3D Tolerance > > filters DescriptiveStatistics AttributeMode > > filters DescriptiveStatistics Input > > filters DescriptiveStatistics ModelInput > > filters DescriptiveStatistics SelectArrays > > filters DescriptiveStatistics SignedDeviations > > filters DescriptiveStatistics Task > > filters DescriptiveStatistics TrainingFraction > > filters ElevationFilter HighPoint > > filters ElevationFilter Input > > filters ElevationFilter LowPoint > > filters ElevationFilter ScalarRange > > filters ExtractBagPlots Input > > filters ExtractBagPlots RobustPCA > > filters ExtractBagPlots SelectArrays > > filters ExtractBagPlots Sigma > > filters ExtractBagPlots TransposeTable > > filters ExtractBlock BlockIndices > > filters ExtractBlock Input > > filters ExtractBlock MaintainStructure > > filters ExtractBlock PruneOutput > > filters ExtractEdges Input > > filters ExtractFieldDataOverTime Input > > filters ExtractGeometry Extract intersected > > filters ExtractGeometry Extract only intersected > > filters ExtractGeometry ExtractInside > > filters ExtractGeometry ImplicitFunction > > filters ExtractGeometry Input > > filters ExtractGeometry InputBounds > > filters ExtractGrid IncludeBoundary > > filters ExtractGrid Input > > filters ExtractGrid SampleRateI > > filters ExtractGrid SampleRateJ > > filters ExtractGrid SampleRateK > > filters ExtractGrid VOI > > filters ExtractHierarchicalDataSets Input > > filters ExtractHierarchicalDataSets SelectedDataSets > > filters ExtractHierarchicalLevel Input > > filters ExtractHierarchicalLevel Levels > > filters ExtractHistogram BinCount > > filters ExtractHistogram CalculateAverages > > filters ExtractHistogram Component > > filters ExtractHistogram CustomBinRanges > > filters ExtractHistogram Input > > filters ExtractHistogram SelectInputArray > > filters ExtractHistogram UseCustomBinRanges > > filters ExtractLocation Input > > filters ExtractLocation Location > > filters ExtractLocation Mode > > filters ExtractSelection Input > > filters ExtractSelection PreserveTopology > > filters ExtractSelection Selection > > filters ExtractSelection ShowBounds > > filters ExtractSelectionOverTime Input > > filters ExtractSelectionOverTime Only Report Selection Statistics > > filters ExtractSelectionOverTime Selection > > filters FFTSelectionOverTime Input > > filters FFTSelectionOverTime Selection > > filters FeatureEdges BoundaryEdges > > filters FeatureEdges Coloring > > filters FeatureEdges FeatureAngle > > filters FeatureEdges FeatureEdges > > filters FeatureEdges Input > > filters FeatureEdges ManifoldEdges > > filters FeatureEdges NonManifoldEdges > > filters FlattenFilter Input > > filters GaussianSplatter Accumulation Mode > > filters GaussianSplatter CapValue > > filters GaussianSplatter Capping > > filters GaussianSplatter Eccentricity > > filters GaussianSplatter ExponentFactor > > filters GaussianSplatter Input > > filters GaussianSplatter ModelBounds > > filters GaussianSplatter NormalWarping > > filters GaussianSplatter NullValue > > filters GaussianSplatter Radius > > filters GaussianSplatter SampleDimensions > > filters GaussianSplatter ScalarWarping > > filters GaussianSplatter ScaleFactor > > filters GaussianSplatter SelectInputScalars > > filters GenerateIdScalars ArrayName > > filters GenerateIdScalars Input > > filters GenericClip ClipFunction > > filters GenericClip Input > > filters GenericClip InputBounds > > filters GenericClip InsideOut > > filters GenericClip SelectInputScalars > > filters GenericClip Value > > filters GenericContour ComputeGradients > > filters GenericContour ComputeNormals > > filters GenericContour ComputeScalars > > filters GenericContour ContourValues > > filters GenericContour Input > > filters GenericContour Locator > > filters GenericContour SelectInputScalars > > filters GenericCut ContourValues > > filters GenericCut CutFunction > > filters GenericCut Input > > filters GenericCut InputBounds > > filters GenericGeometryFilter Input > > filters GenericGeometryFilter PassThroughCellIds > > filters GenericOutlineFilter Input > > filters GenericStreamTracer InitialIntegrationStep > > filters GenericStreamTracer Input > > filters GenericStreamTracer IntegrationDirection > > filters GenericStreamTracer IntegrationStepUnit > > filters GenericStreamTracer IntegratorType > > filters GenericStreamTracer MaximumError > > filters GenericStreamTracer MaximumIntegrationStep > > filters GenericStreamTracer MaximumNumberOfSteps > > filters GenericStreamTracer MaximumPropagation > > filters GenericStreamTracer MinimumIntegrationStep > > filters GenericStreamTracer SelectInputVectors > > filters GenericStreamTracer Source > > filters GenericStreamTracer TerminalSpeed > > filters GenericTessellator Input > > filters GeometryFilter ForceStrips > > filters GeometryFilter Input > > filters GeometryFilter NonlinearSubdivisionLevel > > filters GeometryFilter PassThroughIds > > filters GeometryFilter PassThroughPointIds > > filters GeometryFilter UseOutline > > filters GeometryFilter UseStrips > > filters Glyph GlyphMode > > filters Glyph GlyphTransform > > filters Glyph Input > > filters Glyph MaximumNumberOfSamplePoints > > filters Glyph Orient > > filters Glyph Scalars > > filters Glyph ScaleFactor > > filters Glyph ScaleMode > > filters Glyph Seed > > filters Glyph Source > > filters Glyph Stride > > filters Glyph Vectors > > filters GlyphWithCustomSource GlyphMode > > filters GlyphWithCustomSource GlyphTransform > > filters GlyphWithCustomSource Input > > filters GlyphWithCustomSource MaximumNumberOfSamplePoints > > filters GlyphWithCustomSource Orient > > filters GlyphWithCustomSource Scalars > > filters GlyphWithCustomSource ScaleFactor > > filters GlyphWithCustomSource ScaleMode > > filters GlyphWithCustomSource Seed > > filters GlyphWithCustomSource Source > > filters GlyphWithCustomSource Stride > > filters GlyphWithCustomSource Vectors > > filters Gradient Dimensionality > > filters Gradient Input > > filters Gradient SelectInputScalars > > filters GradientMagnitude Dimensionality > > filters GradientMagnitude Input > > filters GridConnectivity Input > > filters GroupDataSets Input > > filters ImageClip Input > > filters ImageClip OutputWholeExtent > > filters ImageDataToAMR Input > > filters ImageDataToAMR MaximumNumberOfLevels > > filters ImageDataToAMR NumberOfLevels > > filters ImageDataToAMR RefinementRatio > > filters ImageDataToPointSet Input > > filters ImageDataToUniformGrid Input > > filters ImageDataToUniformGrid Reverse > > filters ImageDataToUniformGrid SelectInputScalars > > filters ImageResampling CustomSamplingBounds > > filters ImageResampling Input > > filters ImageResampling SamplingDimension > > filters ImageResampling UseInputBounds > > filters ImageShrink Averaging > > filters ImageShrink Input > > filters ImageShrink ShrinkFactors > > filters IntegrateAttributes Input > > filters IntegrateFlowThroughSurface Input > > filters IntegrateFlowThroughSurface SelectInputVectors > > filters IntersectFragments CutFunction > > filters IntersectFragments Input > > filters IntersectFragments Source > > filters IsoVolume Input > > filters IsoVolume SelectInputScalars > > filters IsoVolume ThresholdBetween > > filters KMeans AttributeMode > > filters KMeans Input > > filters KMeans K > > filters KMeans MaxNumIterations > > filters KMeans ModelInput > > filters KMeans SelectArrays > > filters KMeans Task > > filters KMeans Tolerance > > filters KMeans TrainingFraction > > filters LegacyArbitrarySourceGlyph Input > > filters LegacyArbitrarySourceGlyph KeepRandomPoints > > filters LegacyArbitrarySourceGlyph MaximumNumberOfPoints > > filters LegacyArbitrarySourceGlyph RandomMode > > filters LegacyArbitrarySourceGlyph SelectInputScalars > > filters LegacyArbitrarySourceGlyph SelectInputVectors > > filters LegacyArbitrarySourceGlyph SetOrient > > filters LegacyArbitrarySourceGlyph SetScaleFactor > > filters LegacyArbitrarySourceGlyph SetScaleMode > > filters LegacyArbitrarySourceGlyph Source > > filters LegacyArbitrarySourceGlyph UseMaskPoints > > filters LegacyGlyph GlyphTransform > > filters LegacyGlyph Input > > filters LegacyGlyph KeepRandomPoints > > filters LegacyGlyph MaximumNumberOfPoints > > filters LegacyGlyph RandomMode > > filters LegacyGlyph SelectInputScalars > > filters LegacyGlyph SelectInputVectors > > filters LegacyGlyph SetOrient > > filters LegacyGlyph SetScaleFactor > > filters LegacyGlyph SetScaleMode > > filters LegacyGlyph Source > > filters LegacyGlyph UseMaskPoints > > filters LinearExtrusionFilter Capping > > filters LinearExtrusionFilter Input > > filters LinearExtrusionFilter PieceInvariant > > filters LinearExtrusionFilter ScaleFactor > > filters LinearExtrusionFilter Vector > > filters LoopSubdivisionFilter Input > > filters LoopSubdivisionFilter NumberOfSubdivisions > > filters MPIMoveData Input > > filters MPIMoveData MoveMode > > filters MPIMoveData OutputDataType > > filters MaskPoints GenerateVertices > > filters MaskPoints Input > > filters MaskPoints MaximumNumberOfPoints > > filters MaskPoints Offset > > filters MaskPoints OnRatio > > filters MaskPoints ProportionalMaximumNumberOfPoints > > filters MaskPoints RandomMode > > filters MaskPoints RandomModeType > > filters MaskPoints SingleVertexPerCell > > filters MaterialInterfaceFilter ClipFunction > > filters MaterialInterfaceFilter ComputeOBB > > filters MaterialInterfaceFilter Input > > filters MaterialInterfaceFilter InvertVolumeFraction > > filters MaterialInterfaceFilter MaterialFractionThreshold > > filters MaterialInterfaceFilter OutputBaseName > > filters MaterialInterfaceFilter SelectMassArray > > filters MaterialInterfaceFilter SelectMassWtdAvgArray > > filters MaterialInterfaceFilter SelectMaterialArray > > filters MaterialInterfaceFilter SelectVolumeWtdAvgArray > > filters MaterialInterfaceFilter WriteGeometryOutput > > filters MaterialInterfaceFilter WriteStatisticsOutput > > filters Median Input > > filters Median KernelSize > > filters Median SelectInputScalars > > filters MergeBlocks Input > > filters MergeBlocks MergePoints > > filters MergeBlocks SubTreeCompositeIndex > > filters MeshQuality HexQualityMeasure > > filters MeshQuality Input > > filters MeshQuality QuadQualityMeasure > > filters MeshQuality TetQualityMeasure > > filters MeshQuality TriangleQualityMeasure > > filters MinMax Input > > filters MinMax Operation > > filters MulticorrelativeStatistics AttributeMode > > filters MulticorrelativeStatistics Input > > filters MulticorrelativeStatistics ModelInput > > filters MulticorrelativeStatistics SelectArrays > > filters MulticorrelativeStatistics Task > > filters MulticorrelativeStatistics TrainingFraction > > filters NonOverlappingLevelIdScalars Input > > filters NormalGlyphs Consistency > > filters NormalGlyphs Glyph Max. Points > > filters NormalGlyphs Glyph Scale Factor > > filters NormalGlyphs Input > > filters NormalGlyphs InvertArrow > > filters OctreeDepthLimit Input > > filters OctreeDepthLimit MaximumLevel > > filters OctreeDepthScalars Input > > filters OrderedCompositeDistributor Input > > filters OrderedCompositeDistributor OutputType > > filters OrderedCompositeDistributor PKdTree > > filters OrderedCompositeDistributor PassThrough > > filters OutlineCornerFilter CornerFactor > > filters OutlineCornerFilter Input > > filters OutlineFilter Input > > filters OverlappingLevelIdScalars Input > > filters PCAStatistics AttributeMode > > filters PCAStatistics BasisEnergy > > filters PCAStatistics BasisScheme > > filters PCAStatistics BasisSize > > filters PCAStatistics Input > > filters PCAStatistics ModelInput > > filters PCAStatistics NormalizationScheme > > filters PCAStatistics RobustPCA > > filters PCAStatistics SelectArrays > > filters PCAStatistics Task > > filters PCAStatistics TrainingFraction > > filters PVConnectivityFilter ColorRegions > > filters PVConnectivityFilter ExtractionMode > > filters PVConnectivityFilter Input > > filters PVExtractSelection Input > > filters PVExtractSelection Selection > > filters ParticlePath ComputeVorticity > > filters ParticlePath DisableResetCache > > filters ParticlePath ForceReinjectionEveryNSteps > > filters ParticlePath Input > > filters ParticlePath SelectInputVectors > > filters ParticlePath Source > > filters ParticlePath StaticMesh > > filters ParticlePath StaticSeeds > > filters ParticlePath TerminationTime > > filters ParticlePath TimestepValues > > filters ParticlePathLines IdChannelArray > > filters ParticlePathLines Input > > filters ParticlePathLines MaskPoints > > filters ParticlePathLines MaxStepDistance > > filters ParticlePathLines MaxTrackLength > > filters ParticlePathLines Selection > > filters ParticleTracer ComputeVorticity > > filters ParticleTracer ForceReinjectionEveryNSteps > > filters ParticleTracer Input > > filters ParticleTracer SelectInputVectors > > filters ParticleTracer Source > > filters ParticleTracer StaticMesh > > filters ParticleTracer StaticSeeds > > filters ParticleTracer TimestepValues > > filters PassArrays CellDataArrays > > filters PassArrays FieldDataArrays > > filters PassArrays Input > > filters PassArrays PointDataArrays > > filters PassArrays SelectedFieldTypes > > filters PassArrays UseFieldTypes > > filters PassThrough Input > > filters PlotAttributes Input > > filters PlotOnIntersectionCurves Input > > filters PlotOnIntersectionCurves Slice Type > > filters PlotOnSortedLines Input > > filters PointDataToCellData Input > > filters PointDataToCellData PassPointData > > filters PolyDataNormals ComputeCellNormals > > filters PolyDataNormals Consistency > > filters PolyDataNormals FeatureAngle > > filters PolyDataNormals FlipNormals > > filters PolyDataNormals Input > > filters PolyDataNormals NonManifoldTraversal > > filters PolyDataNormals PieceInvariant > > filters PolyDataNormals Splitting > > filters PolyLineToRectilinearGrid Input > > filters Probe ComputeTolerance > > filters Probe Input > > filters Probe PassCellArrays > > filters Probe PassFieldArrays > > filters Probe PassPointArrays > > filters Probe Source > > filters Probe Tolerance > > filters ProbeLine ComputeTolerance > > filters ProbeLine Input > > filters ProbeLine PassPartialArrays > > filters ProbeLine Source > > filters ProbeLine Tolerance > > filters ProbePoint ComputeTolerance > > filters ProbePoint Input > > filters ProbePoint PassFieldArrays > > filters ProbePoint Source > > filters ProbePoint Tolerance > > filters ProcessIdScalars Input > > filters ProcessIdScalars RandomMode > > filters ProgrammableFilter CopyArrays > > filters ProgrammableFilter InformationScript > > filters ProgrammableFilter Input > > filters ProgrammableFilter OutputDataSetType > > filters ProgrammableFilter Parameters > > filters ProgrammableFilter PythonPath > > filters ProgrammableFilter Script > > filters ProgrammableFilter UpdateExtentScript > > filters PythonAnnotation AnnotationValue > > filters PythonAnnotation ArrayAssociation > > filters PythonAnnotation Expression > > filters PythonAnnotation Input > > filters PythonCalculator ArrayAssociation > > filters PythonCalculator ArrayName > > filters PythonCalculator CopyArrays > > filters PythonCalculator Expression > > filters PythonCalculator Input > > filters QuadraturePointInterpolator Input > > filters QuadraturePointInterpolator QuadratureSchemeDefinition > > filters QuadraturePointsGenerator Input > > filters QuadraturePointsGenerator QuadratureSchemeDefinition > > filters QuadratureSchemeDictionaryGenerator Input > > filters QuadricClustering CopyCellData > > filters QuadricClustering Input > > filters QuadricClustering NumberOfDivisions > > filters QuadricClustering UseFeatureEdges > > filters QuadricClustering UseFeaturePoints > > filters QuadricClustering UseInputPoints > > filters QuadricClustering UseInternalTriangles > > filters RandomAttributeGenerator AttributesConstantPerBlock > > filters RandomAttributeGenerator ComponentRange > > filters RandomAttributeGenerator DataType > > filters RandomAttributeGenerator GenerateCellScalars > > filters RandomAttributeGenerator GenerateCellVectors > > filters RandomAttributeGenerator GeneratePointScalars > > filters RandomAttributeGenerator GeneratePointVectors > > filters RandomAttributeGenerator Input > > filters RectilinearGridConnectivity AddDoubleVolumeArrayName > > filters RectilinearGridConnectivity AddFloatVolumeArrayName > > filters RectilinearGridConnectivity AddUnsignedCharVolumeArrayName > > filters RectilinearGridConnectivity Input > > filters RectilinearGridConnectivity VolumeFractionSurfaceValue > > filters RectilinearGridGeometryFilter Input > > filters RectilinearGridToPointSet Input > > filters ReductionFilter GenerateProcessIds > > filters ReductionFilter Input > > filters ReductionFilter PassThrough > > filters ReductionFilter PostGatherHelper > > filters ReductionFilter PostGatherHelperName > > filters ReductionFilter PreGatherHelper > > filters ReductionFilter PreGatherHelperName > > filters ReflectionFilter Center > > filters ReflectionFilter CopyInput > > filters ReflectionFilter Input > > filters ReflectionFilter Plane > > filters RibbonFilter Angle > > filters RibbonFilter DefaultNormal > > filters RibbonFilter Input > > filters RibbonFilter SelectInputScalars > > filters RibbonFilter SelectInputVectors > > filters RibbonFilter UseDefaultNormal > > filters RibbonFilter VaryWidth > > filters RibbonFilter Width > > filters RotationalExtrusionFilter Angle > > filters RotationalExtrusionFilter Capping > > filters RotationalExtrusionFilter DeltaRadius > > filters RotationalExtrusionFilter Input > > filters RotationalExtrusionFilter Resolution > > filters RotationalExtrusionFilter Translation > > filters ScatterPlot Input > > filters ShrinkFilter Input > > filters ShrinkFilter ShrinkFactor > > filters SliceAlongPolyLine Dataset > > filters SliceAlongPolyLine PolyLine > > filters SliceAlongPolyLine Tolerance > > filters SmoothPolyDataFilter Convergence > > filters SmoothPolyDataFilter Input > > filters SmoothPolyDataFilter NumberOfIterations > > filters StreakLine ComputeVorticity > > filters StreakLine DisableResetCache > > filters StreakLine ForceReinjectionEveryNSteps > > filters StreakLine Input > > filters StreakLine SelectInputVectors > > filters StreakLine Source > > filters StreakLine StaticMesh > > filters StreakLine StaticSeeds > > filters StreakLine TerminationTime > > filters StreakLine TimestepValues > > filters StreamTracer ComputeVorticity > > filters StreamTracer InitialIntegrationStep > > filters StreamTracer Input > > filters StreamTracer IntegrationDirection > > filters StreamTracer IntegrationStepUnit > > filters StreamTracer IntegratorType > > filters StreamTracer InterpolatorType > > filters StreamTracer MaximumError > > filters StreamTracer MaximumIntegrationStep > > filters StreamTracer MaximumNumberOfSteps > > filters StreamTracer MaximumPropagation > > filters StreamTracer MinimumIntegrationStep > > filters StreamTracer SelectInputVectors > > filters StreamTracer Source > > filters StreamTracer TerminalSpeed > > filters Stripper Input > > filters Stripper MaximumLength > > filters StructuredGridOutlineFilter Input > > filters Subdivide Input > > filters Subdivide NumberOfSubdivisions > > filters SurfaceVectors ConstraintMode > > filters SurfaceVectors Input > > filters SurfaceVectors SelectInputVectors > > filters TableFFT Input > > filters TableToPolyData Create2DPoints > > filters TableToPolyData Input > > filters TableToPolyData KeepAllDataArrays > > filters TableToPolyData XColumn > > filters TableToPolyData YColumn > > filters TableToPolyData ZColumn > > filters TableToStructuredGrid Input > > filters TableToStructuredGrid WholeExtent > > filters TableToStructuredGrid XColumn > > filters TableToStructuredGrid YColumn > > filters TableToStructuredGrid ZColumn > > filters TemporalCache CacheSize > > filters TemporalCache Input > > filters TemporalCache TimestepValues > > filters TemporalInterpolator DiscreteTimeStepInterval > > filters TemporalInterpolator Input > > filters TemporalInterpolator TimeRange > > filters TemporalInterpolator TimestepValues > > filters TemporalShiftScale Input > > filters TemporalShiftScale MaximumNumberOfPeriods > > filters TemporalShiftScale Periodic > > filters TemporalShiftScale PeriodicEndCorrection > > filters TemporalShiftScale PostShift > > filters TemporalShiftScale PreShift > > filters TemporalShiftScale Scale > > filters TemporalShiftScale TimestepValues > > filters TemporalSnapToTimeStep Input > > filters TemporalSnapToTimeStep SnapMode > > filters TemporalSnapToTimeStep TimestepValues > > filters TemporalStatistics ComputeAverage > > filters TemporalStatistics ComputeMaximum > > filters TemporalStatistics ComputeMinimum > > filters TemporalStatistics ComputeStandardDeviation > > filters TemporalStatistics Input > > filters TensorGlyph ColorGlyphs > > filters TensorGlyph ColorMode > > filters TensorGlyph ExtractEigenvalues > > filters TensorGlyph Input > > filters TensorGlyph LimitScalingByEigenvalues > > filters TensorGlyph MaxScaleFactor > > filters TensorGlyph ScaleFactor > > filters TensorGlyph SelectInputScalars > > filters TensorGlyph SelectInputTensors > > filters TensorGlyph Source > > filters TensorGlyph Symmetric > > filters TensorGlyph ThreeGlyphs > > filters TessellatorFilter ChordError > > filters TessellatorFilter FieldError2 > > filters TessellatorFilter Input > > filters TessellatorFilter MaximumNumberOfSubdivisions > > filters TessellatorFilter MergePoints > > filters TessellatorFilter OutputDimension > > filters TessellatorFilter ResetFieldCriteria > > filters TextureMapToCylinder Input > > filters TextureMapToCylinder PreventSeam > > filters TextureMapToPlane Input > > filters TextureMapToSphere Input > > filters TextureMapToSphere PreventSeam > > filters Threshold AllScalars > > filters Threshold Input > > filters Threshold SelectInputScalars > > filters Threshold ThresholdBetween > > filters Threshold UseContinuousCellRange > > filters TimeToTextConvertor Format > > filters TimeToTextConvertor Input > > filters TimeToTextConvertor Scale > > filters TimeToTextConvertor Shift > > filters TransformFilter Input > > filters TransformFilter Transform > > filters TransposeTable AddIdColumn > > filters TransposeTable DoNotTranspose > > filters TransposeTable Input > > filters TransposeTable SelectArrays > > filters TransposeTable UseIdColumn > > filters TriangleFilter Input > > filters TubeFilter Capping > > filters TubeFilter DefaultNormal > > filters TubeFilter Input > > filters TubeFilter NumberOfSides > > filters TubeFilter Radius > > filters TubeFilter RadiusFactor > > filters TubeFilter SelectInputScalars > > filters TubeFilter SelectInputVectors > > filters TubeFilter UseDefaultNormal > > filters TubeFilter VaryRadius > > filters UnstructuredGradient ComputeQCriterion > > filters UnstructuredGradient ComputeVorticity > > filters UnstructuredGradient FasterApproximation > > filters UnstructuredGradient Input > > filters UnstructuredGradient QCriterionArrayName > > filters UnstructuredGradient ResultArrayName > > filters UnstructuredGradient SelectInputScalars > > filters UnstructuredGradient VorticityArrayName > > filters UpdateSuppressor2 Enabled > > filters UpdateSuppressor2 ForceUpdate > > filters UpdateSuppressor2 Input > > filters UpdateSuppressor2 UpdateTime > > filters WarpScalar Input > > filters WarpScalar Normal > > filters WarpScalar ScaleFactor > > filters WarpScalar SelectInputScalars > > filters WarpScalar UseNormal > > filters WarpScalar XYPlane > > filters WarpVector Input > > filters WarpVector ScaleFactor > > filters WarpVector SelectInputVectors > > filters YoungsMaterialInterface AxisSymetric > > filters YoungsMaterialInterface FillMaterial > > filters YoungsMaterialInterface Input > > filters YoungsMaterialInterface InverseNormal > > filters YoungsMaterialInterface NormalArrays > > filters YoungsMaterialInterface NumberOfDomainsInformation > > filters YoungsMaterialInterface OnionPeel > > filters YoungsMaterialInterface OrderingArrays > > filters YoungsMaterialInterface ReverseMaterialOrder > > filters YoungsMaterialInterface UseFractionAsDistance > > filters YoungsMaterialInterface VolumeFractionArrays > > filters YoungsMaterialInterface VolumeFractionRange > > filters GlyphSpeed Input > > filters GlyphSpeed Scalars > > Traceback (most recent call last): > > File "", line 1, in > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/simple.py", > line 39, in > > import servermanager > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > line 3185, in > > __initialize() > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > line 3176, in __initialize > > c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > line 1932, in __init__ > > _createModules(self.Modules) > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > line 2564, in _createModules > > m.filters = createModule('filters') > > File > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > line 2627, in createModule > > if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ > > AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' > >>>> > > > On Thu, Feb 26, 2015 at 3:06 PM, Utkarsh Ayachit > wrote: >> >> It is believable, let me see if I can find a 10.10 here to reproduce >> the problem. >> >> Another thing to try: >> >> 1. edit >> "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py" >> 2. before line 2626, add the following: >> print groupName, proxyName, propName >> >> Let's see which proxy this is failing for. >> >> Utkarsh >> >> >> >> >> On Thu, Feb 26, 2015 at 3:53 PM, Matei Stroila >> wrote: >> > I do not have any plugin auto-loaded. Also I just tried now with the OS >> > X >> > default Python and I get the same errors. >> > Could be a 10.10 issue? I built ParaView on a 10.9 machine yesterday >> > with no >> > issues (ParaView from git, the release branch, 4.3.1). >> > >> > Matei >> > >> > On Thu, Feb 26, 2015 at 2:10 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> How was ParaView built? I am not sure if Homebrew Python is different >> >> from the one packaged in OsX, but binaries on paraview.org are built >> >> using OsX default Python. >> >> >> >> Also, do you have any plugins that are being auto-loaded? If you're >> >> running pvpython, try running with "-dr" argument. That will avoid >> >> loading any auto-load plugins. Does that help? >> >> >> >> Utkarsh >> >> >> >> On Thu, Feb 26, 2015 at 3:03 PM, Matei Stroila >> >> >> >> wrote: >> >> > Not sure if other people have seen this. Using Python from Homebrew >> >> > on >> >> > Mac >> >> > OS X 10.10, got the same error on two different Macs. >> >> > >> >> > Python 2.7.9 (default, Dec 19 2014, 06:00:59) >> >> > >> >> > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin >> >> > >> >> >>>> from paraview.simple import * >> >> > >> >> > Traceback (most recent call last): >> >> > >> >> > File "", line 1, in >> >> > >> >> > File >> >> > >> >> > >> >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/simple.py", >> >> > line 39, in >> >> > >> >> > import servermanager >> >> > >> >> > File >> >> > >> >> > >> >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", >> >> > line 3184, in >> >> > >> >> > __initialize() >> >> > >> >> > File >> >> > >> >> > >> >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", >> >> > line 3175, in __initialize >> >> > >> >> > c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) >> >> > >> >> > File >> >> > >> >> > >> >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", >> >> > line 1932, in __init__ >> >> > >> >> > _createModules(self.Modules) >> >> > >> >> > File >> >> > >> >> > >> >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", >> >> > line 2564, in _createModules >> >> > >> >> > m.filters = createModule('filters') >> >> > >> >> > File >> >> > >> >> > >> >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", >> >> > line 2626, in createModule >> >> > >> >> > if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ >> >> > >> >> > AttributeError: 'NoneType' object has no attribute >> >> > 'GetInformationOnly' >> >> > >> >> >>>> >> >> > >> >> > Thanks for any suggestion. >> >> > >> >> > >> >> > Matei >> >> > >> >> > >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> > http://paraview.org/Wiki/ParaView >> >> > >> >> > 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 26 16:57:10 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 26 Feb 2015 16:57:10 -0500 Subject: [Paraview] pvserver running out of memory In-Reply-To: <54EF538B.2000501@nasa.gov> References: <54EE1C01.3020303@nasa.gov> <54EE430B.6010101@nasa.gov> <54EE5B88.3090000@nasa.gov> <54EF538B.2000501@nasa.gov> Message-ID: Odd...can you share the data? I'll see if I can reproduce the issue. Utkarsh On Thu, Feb 26, 2015 at 12:10 PM, Jeff Becker wrote: > On 02/26/2015 06:04 AM, Utkarsh Ayachit wrote: >>> >>> The threshold is zero. I was able to remote render the disk_out_ref.ex2 >>> tutorial example just fine. Perhaps there's some issue with the SILO >>> reader >>> used in pvserver? Thanks. >> >> Possible, but you said it works fine when you load locally on the >> client and not in client-server mode. But given that this is just a >> single MPI rank for pvserver, I wonder what's different. Try not >> using "--use-offscreen-rendering" argument. Does that make any >> difference? > > > Still runs out of memory. > > -jeff >> >> >> Utkarsh > > From matei.stroila at gmail.com Thu Feb 26 17:22:45 2015 From: matei.stroila at gmail.com (Matei Stroila) Date: Thu, 26 Feb 2015 16:22:45 -0600 Subject: [Paraview] problem wirh python shell in Paraview 4.3.1 and Python 2.7.9 on Mac OS X 10.10 In-Reply-To: References: Message-ID: This helped, thanks! The culprit was the .ini file in the .config directory. I deleted that and everything works. I think that file stored information about old custom Python filters that were no longer available. Matei On Thu, Feb 26, 2015 at 3:55 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > The "GlyphSpeed" filter seems to be the culprit. It's not a standard > ParaView filter. Any ideas where it's coming from? I suspect it has a > property named "Scalars" that is exposed, but doesn't really exist or > something to that effect. > > Utkarsh > > On Thu, Feb 26, 2015 at 4:44 PM, Matei Stroila > wrote: > > Here is the output: > > > > > > Python 2.7.6 (default, Sep 9 2014, 15:04:36) > > > > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.39)] on darwin > > > >>>> from paraview.simple import * > > > > sources AMRGaussianPulseSource Dimension > > > > sources AMRGaussianPulseSource PulseAmplitude > > > > sources AMRGaussianPulseSource RefinementRatio > > > > sources AMRGaussianPulseSource Root Spacing > > > > sources AMRGaussianPulseSource XPulseOrigin > > > > sources AMRGaussianPulseSource XPulseWidth > > > > sources AMRGaussianPulseSource YPulseOrigin > > > > sources AMRGaussianPulseSource YPulseWidth > > > > sources AMRGaussianPulseSource ZPulseOrigin > > > > sources AMRGaussianPulseSource ZPulseWidth > > > > sources AVSucdSeriesReader FileNameInfo > > > > sources AVSucdSeriesReader FileNames > > > > sources AVSucdSeriesReader TimestepValues > > > > sources AVSucdSeriesReader CellArrayInfo > > > > sources AVSucdSeriesReader CellArrayStatus > > > > sources AVSucdSeriesReader PointArrayInfo > > > > sources AVSucdSeriesReader PointArrayStatus > > > > sources ArrowSource Invert > > > > sources ArrowSource ShaftRadius > > > > sources ArrowSource ShaftResolution > > > > sources ArrowSource TipLength > > > > sources ArrowSource TipRadius > > > > sources ArrowSource TipResolution > > > > sources Axes Origin > > > > sources Axes ScaleFactor > > > > sources Axes Symmetric > > > > sources BlockSelectionSource Blocks > > > > sources BlockSelectionSource ContainingCells > > > > sources BlockSelectionSource FieldType > > > > sources BlockSelectionSource InsideOut > > > > sources CMLMoleculeReader FileName > > > > sources CSVReader FileName > > > > sources CSVReader FileNameInfo > > > > sources CSVReader TimestepValues > > > > sources CSVReader DetectNumericColumns > > > > sources CSVReader FieldDelimiterCharacters > > > > sources CSVReader HaveHeaders > > > > sources CSVReader MergeConsecutiveDelimiters > > > > sources CSVReader UseStringDelimiter > > > > sources CompositeDataIDSelectionSource ContainingCells > > > > sources CompositeDataIDSelectionSource FieldType > > > > sources CompositeDataIDSelectionSource IDs > > > > sources CompositeDataIDSelectionSource InsideOut > > > > sources ConeSource Capping > > > > sources ConeSource Center > > > > sources ConeSource Direction > > > > sources ConeSource Height > > > > sources ConeSource Radius > > > > sources ConeSource Resolution > > > > sources CubeSource Center > > > > sources CubeSource XLength > > > > sources CubeSource YLength > > > > sources CubeSource ZLength > > > > sources CylinderSource Capping > > > > sources CylinderSource Center > > > > sources CylinderSource Height > > > > sources CylinderSource Radius > > > > sources CylinderSource Resolution > > > > sources DEMReader FileName > > > > sources DICOMReader FileName > > > > sources DICOMReaderSingle FileName > > > > sources DataObjectGenerator Program > > > > sources DiskSource CircumferentialResolution > > > > sources DiskSource InnerRadius > > > > sources DiskSource OuterRadius > > > > sources DiskSource RadialResolution > > > > sources DistributedTrivialProducer UpdateDataset > > > > sources DistributedTrivialProducer WholeExtent > > > > sources EnzoParticlesReader FileNameInfo > > > > sources EnzoParticlesReader FileNames > > > > sources EnzoParticlesReader TimestepValues > > > > sources EnzoParticlesReader FilterLocation > > > > sources EnzoParticlesReader Frequency > > > > sources EnzoParticlesReader MaxLocation > > > > sources EnzoParticlesReader MinLocation > > > > sources EnzoParticlesReader NumParticles > > > > sources EnzoParticlesReader ParticleArrayStatus > > > > sources EnzoParticlesReader ParticleType > > > > sources EnzoReader FileNameInfo > > > > sources EnzoReader FileNames > > > > sources EnzoReader TimestepValues > > > > sources EnzoReader CellArrayStatus > > > > sources EnzoReader ConvertToCGS > > > > sources EnzoReader EnableCaching > > > > sources EnzoReader Level > > > > sources EnzoReader NumBlocks > > > > sources EnzoReader NumLevels > > > > sources EnzoReader PointArrayStatus > > > > sources ExodusIIReader FileName > > > > sources ExodusIIReader FileNameInfo > > > > sources ExodusIIReader TimestepValues > > > > sources ExodusIIReader UseMetaFile > > > > sources ExodusIIReader AnimateVibrations > > > > sources ExodusIIReader ApplyDisplacements > > > > sources ExodusIIReader DisplacementMagnitude > > > > sources ExodusIIReader EdgeBlocks > > > > sources ExodusIIReader EdgeBlocksInfo > > > > sources ExodusIIReader EdgeMapArrayStatus > > > > sources ExodusIIReader EdgeMapInfo > > > > sources ExodusIIReader EdgeSetArrayStatus > > > > sources ExodusIIReader EdgeSetInfo > > > > sources ExodusIIReader EdgeSetResultArrayInfo > > > > sources ExodusIIReader EdgeSetResultArrayStatus > > > > sources ExodusIIReader EdgeVariables > > > > sources ExodusIIReader EdgeVariablesInfo > > > > sources ExodusIIReader ElementBlocks > > > > sources ExodusIIReader ElementMapArrayStatus > > > > sources ExodusIIReader ElementMapInfo > > > > sources ExodusIIReader ElementSetArrayStatus > > > > sources ExodusIIReader ElementSetInfo > > > > sources ExodusIIReader ElementSetResultArrayInfo > > > > sources ExodusIIReader ElementSetResultArrayStatus > > > > sources ExodusIIReader ElementVariables > > > > sources ExodusIIReader ElementVariablesInfo > > > > sources ExodusIIReader FaceBlocks > > > > sources ExodusIIReader FaceBlocksInfo > > > > sources ExodusIIReader FaceMapArrayStatus > > > > sources ExodusIIReader FaceMapInfo > > > > sources ExodusIIReader FaceSetArrayStatus > > > > sources ExodusIIReader FaceSetInfo > > > > sources ExodusIIReader FaceSetResultArrayInfo > > > > sources ExodusIIReader FaceSetResultArrayStatus > > > > sources ExodusIIReader FaceVariables > > > > sources ExodusIIReader FaceVariablesInfo > > > > sources ExodusIIReader FilePattern > > > > sources ExodusIIReader FilePatternInfo > > > > sources ExodusIIReader FilePrefix > > > > sources ExodusIIReader FilePrefixInfo > > > > sources ExodusIIReader FileRange > > > > sources ExodusIIReader FileRangeInfo > > > > sources ExodusIIReader GenerateGlobalElementIdArray > > > > sources ExodusIIReader GenerateGlobalNodeIdArray > > > > sources ExodusIIReader GenerateObjectIdCellArray > > > > sources ExodusIIReader GlobalVariables > > > > sources ExodusIIReader GlobalVariablesInfo > > > > sources ExodusIIReader HasModeShapes > > > > sources ExodusIIReader ModeShape > > > > sources ExodusIIReader ModeShapesRangeInfo > > > > sources ExodusIIReader NodeMapArrayStatus > > > > sources ExodusIIReader NodeMapInfo > > > > sources ExodusIIReader NodeSetArrayStatus > > > > sources ExodusIIReader NodeSetInfo > > > > sources ExodusIIReader NodeSetResultArrayInfo > > > > sources ExodusIIReader NodeSetResultArrayStatus > > > > sources ExodusIIReader PointVariables > > > > sources ExodusIIReader PointVariablesInfo > > > > sources ExodusIIReader Refresh > > > > sources ExodusIIReader SILUpdateStamp > > > > sources ExodusIIReader SideSetArrayStatus > > > > sources ExodusIIReader SideSetInfo > > > > sources ExodusIIReader SideSetResultArrayInfo > > > > sources ExodusIIReader SideSetResultArrayStatus > > > > sources ExodusIIReader XMLFileName > > > > sources ExodusIIReader XMLFileNameInfo > > > > sources ExodusRestartReader FileName > > > > sources ExodusRestartReader FileNameInfo > > > > sources ExodusRestartReader TimestepValues > > > > sources ExodusRestartReader UseMetaFile > > > > sources ExodusRestartReader AnimateVibrations > > > > sources ExodusRestartReader ApplyDisplacements > > > > sources ExodusRestartReader DisplacementMagnitude > > > > sources ExodusRestartReader EdgeBlocks > > > > sources ExodusRestartReader EdgeBlocksInfo > > > > sources ExodusRestartReader EdgeMapArrayStatus > > > > sources ExodusRestartReader EdgeMapInfo > > > > sources ExodusRestartReader EdgeSetArrayStatus > > > > sources ExodusRestartReader EdgeSetInfo > > > > sources ExodusRestartReader EdgeSetResultArrayInfo > > > > sources ExodusRestartReader EdgeSetResultArrayStatus > > > > sources ExodusRestartReader EdgeVariables > > > > sources ExodusRestartReader EdgeVariablesInfo > > > > sources ExodusRestartReader ElementBlocks > > > > sources ExodusRestartReader ElementMapArrayStatus > > > > sources ExodusRestartReader ElementMapInfo > > > > sources ExodusRestartReader ElementSetArrayStatus > > > > sources ExodusRestartReader ElementSetInfo > > > > sources ExodusRestartReader ElementSetResultArrayInfo > > > > sources ExodusRestartReader ElementSetResultArrayStatus > > > > sources ExodusRestartReader ElementVariables > > > > sources ExodusRestartReader ElementVariablesInfo > > > > sources ExodusRestartReader FaceBlocks > > > > sources ExodusRestartReader FaceBlocksInfo > > > > sources ExodusRestartReader FaceMapArrayStatus > > > > sources ExodusRestartReader FaceMapInfo > > > > sources ExodusRestartReader FaceSetArrayStatus > > > > sources ExodusRestartReader FaceSetInfo > > > > sources ExodusRestartReader FaceSetResultArrayInfo > > > > sources ExodusRestartReader FaceSetResultArrayStatus > > > > sources ExodusRestartReader FaceVariables > > > > sources ExodusRestartReader FaceVariablesInfo > > > > sources ExodusRestartReader FilePattern > > > > sources ExodusRestartReader FilePatternInfo > > > > sources ExodusRestartReader FilePrefix > > > > sources ExodusRestartReader FilePrefixInfo > > > > sources ExodusRestartReader FileRange > > > > sources ExodusRestartReader FileRangeInfo > > > > sources ExodusRestartReader GenerateGlobalElementIdArray > > > > sources ExodusRestartReader GenerateGlobalNodeIdArray > > > > sources ExodusRestartReader GenerateObjectIdCellArray > > > > sources ExodusRestartReader GlobalVariables > > > > sources ExodusRestartReader GlobalVariablesInfo > > > > sources ExodusRestartReader HasModeShapes > > > > sources ExodusRestartReader ModeShape > > > > sources ExodusRestartReader ModeShapesRangeInfo > > > > sources ExodusRestartReader NodeMapArrayStatus > > > > sources ExodusRestartReader NodeMapInfo > > > > sources ExodusRestartReader NodeSetArrayStatus > > > > sources ExodusRestartReader NodeSetInfo > > > > sources ExodusRestartReader NodeSetResultArrayInfo > > > > sources ExodusRestartReader NodeSetResultArrayStatus > > > > sources ExodusRestartReader PointVariables > > > > sources ExodusRestartReader PointVariablesInfo > > > > sources ExodusRestartReader Refresh > > > > sources ExodusRestartReader SILUpdateStamp > > > > sources ExodusRestartReader SideSetArrayStatus > > > > sources ExodusRestartReader SideSetInfo > > > > sources ExodusRestartReader SideSetResultArrayInfo > > > > sources ExodusRestartReader SideSetResultArrayStatus > > > > sources ExodusRestartReader XMLFileName > > > > sources ExodusRestartReader XMLFileNameInfo > > > > sources FLUENTReader FileName > > > > sources FLUENTReader CellArrayInfo > > > > sources FLUENTReader CellArrayStatus > > > > sources FacetReader FileName > > > > sources FlashParticlesReader FileNameInfo > > > > sources FlashParticlesReader FileNames > > > > sources FlashParticlesReader TimestepValues > > > > sources FlashParticlesReader FilterLocation > > > > sources FlashParticlesReader Frequency > > > > sources FlashParticlesReader MaxLocation > > > > sources FlashParticlesReader MinLocation > > > > sources FlashParticlesReader NumParticles > > > > sources FlashParticlesReader ParticleArrayStatus > > > > sources FlashReader FileNameInfo > > > > sources FlashReader FileNames > > > > sources FlashReader TimestepValues > > > > sources FlashReader CellArrayStatus > > > > sources FlashReader EnableCaching > > > > sources FlashReader Level > > > > sources FlashReader NumBlocks > > > > sources FlashReader NumLevels > > > > sources FlashReader PointArrayStatus > > > > sources FrustumSelectionSource ContainingCells > > > > sources FrustumSelectionSource FieldType > > > > sources FrustumSelectionSource Frustum > > > > sources FrustumSelectionSource InsideOut > > > > sources GlobalIDSelectionSource ContainingCells > > > > sources GlobalIDSelectionSource FieldType > > > > sources GlobalIDSelectionSource IDs > > > > sources GlobalIDSelectionSource InsideOut > > > > sources GlyphSource2D Center > > > > sources GlyphSource2D Filled > > > > sources GlyphSource2D GlyphType > > > > sources HierarchicalDataIDSelectionSource ContainingCells > > > > sources HierarchicalDataIDSelectionSource FieldType > > > > sources HierarchicalDataIDSelectionSource IDs > > > > sources HierarchicalDataIDSelectionSource InsideOut > > > > sources HierarchicalFractal Asymetric > > > > sources HierarchicalFractal Dimensions > > > > sources HierarchicalFractal FractalValue > > > > sources HierarchicalFractal GhostLevels > > > > sources HierarchicalFractal MaximumLevel > > > > sources HierarchicalFractal RectilinearGrids > > > > sources HierarchicalFractal TimeStep > > > > sources HierarchicalFractal TimeStepRangeInfo > > > > sources HierarchicalFractal TwoDimensional > > > > sources HyperTreeGridSource BranchFactor > > > > sources HyperTreeGridSource Descriptor > > > > sources HyperTreeGridSource Dimension > > > > sources HyperTreeGridSource GridScale > > > > sources HyperTreeGridSource GridSize > > > > sources HyperTreeGridSource MaximumLevel > > > > sources IDSelectionSource ContainingCells > > > > sources IDSelectionSource FieldType > > > > sources IDSelectionSource IDs > > > > sources IDSelectionSource InsideOut > > > > sources ImageMandelbrotSource MaximumNumberOfIterations > > > > sources ImageMandelbrotSource OriginCX > > > > sources ImageMandelbrotSource ProjectionAxes > > > > sources ImageMandelbrotSource SizeCX > > > > sources ImageMandelbrotSource SubsampleRate > > > > sources ImageMandelbrotSource WholeExtent > > > > sources ImageReader DataByteOrder > > > > sources ImageReader DataExtent > > > > sources ImageReader DataOrigin > > > > sources ImageReader DataScalarType > > > > sources ImageReader DataSpacing > > > > sources ImageReader FileDimensionality > > > > sources ImageReader FileLowerLeft > > > > sources ImageReader FilePattern > > > > sources ImageReader FilePrefix > > > > sources ImageReader NumberOfScalarComponents > > > > sources ImageReader ScalarArrayName > > > > sources JPEGSeriesReader FileNames > > > > sources JPEGSeriesReader TimestepValues > > > > sources LSDynaReader BeamArrayInfo > > > > sources LSDynaReader BeamArrayStatus > > > > sources LSDynaReader DeformedMesh > > > > sources LSDynaReader FileName > > > > sources LSDynaReader PartArrayInfo > > > > sources LSDynaReader PartArrayStatus > > > > sources LSDynaReader ParticleArrayInfo > > > > sources LSDynaReader ParticleArrayStatus > > > > sources LSDynaReader PointArrayInfo > > > > sources LSDynaReader PointArrayStatus > > > > sources LSDynaReader RemoveDeletedCells > > > > sources LSDynaReader RigidBodyArrayInfo > > > > sources LSDynaReader RigidBodyArrayStatus > > > > sources LSDynaReader RoadSurfaceArrayInfo > > > > sources LSDynaReader RoadSurfaceArrayStatus > > > > sources LSDynaReader ShellArrayInfo > > > > sources LSDynaReader ShellArrayStatus > > > > sources LSDynaReader SolidArrayInfo > > > > sources LSDynaReader SolidArrayStatus > > > > sources LSDynaReader ThickShellArrayInfo > > > > sources LSDynaReader ThickShellArrayStatus > > > > sources LSDynaReader TimestepValues > > > > sources LegacyVTKFileReader FileNameInfo > > > > sources LegacyVTKFileReader FileNames > > > > sources LegacyVTKFileReader TimestepValues > > > > sources LineSource Point1 > > > > sources LineSource Point2 > > > > sources LineSource Resolution > > > > sources LocationSelectionSource ContainingCells > > > > sources LocationSelectionSource FieldType > > > > sources LocationSelectionSource InsideOut > > > > sources LocationSelectionSource Locations > > > > sources MFIXReader CellArrayInfo > > > > sources MFIXReader CellArrayStatus > > > > sources MFIXReader FileName > > > > sources MFIXReader TimestepValues > > > > sources MPASReader CellArrayInfo > > > > sources MPASReader CellArrayStatus > > > > sources MPASReader CenterLon > > > > sources MPASReader CenterLonRangeInfo > > > > sources MPASReader FileName > > > > sources MPASReader IsAtmosphere > > > > sources MPASReader LayerThickness > > > > sources MPASReader LayerThicknessRangeInfo > > > > sources MPASReader PointArrayInfo > > > > sources MPASReader PointArrayStatus > > > > sources MPASReader ProjectLatLon > > > > sources MPASReader ShowMultilayerView > > > > sources MPASReader TimestepValues > > > > sources MPASReader VerticalLevel > > > > sources MPASReader VerticalLevelRangeInfo > > > > sources MetaImageReader FileNameInfo > > > > sources MetaImageReader FileNames > > > > sources MetaImageReader TimestepValues > > > > sources MultiServerProxy DependencyLink > > > > sources NetCDFCAMReader FileName > > > > sources NetCDFCAMReader FileNameInfo > > > > sources NetCDFCAMReader TimestepValues > > > > sources NetCDFCAMReader CellLayerRight > > > > sources NetCDFCAMReader ConnectivityFileName > > > > sources NetCDFCAMReader SingleLevel > > > > sources NetCDFPOPReader FileName > > > > sources NetCDFPOPReader FileNameInfo > > > > sources NetCDFPOPReader TimestepValues > > > > sources NetCDFPOPReader Stride > > > > sources NetCDFPOPReader VariableArrayInfo > > > > sources NetCDFPOPReader VariableArrayStatus > > > > sources NetworkImageSource FileName > > > > sources NrrdReader DataVOI > > > > sources NrrdReader FileName > > > > sources OctreeFractal Dimension > > > > sources OctreeFractal MaximumLevel > > > > sources OctreeFractal MaximumNumberOfIterations > > > > sources OctreeFractal MinimumLevel > > > > sources OctreeFractal OriginCX > > > > sources OctreeFractal ProjectionAxes > > > > sources OctreeFractal SizeCX > > > > sources OctreeFractal Threshold > > > > sources OpenFOAMReader AddDimensionsToArrayNames > > > > sources OpenFOAMReader CacheMesh > > > > sources OpenFOAMReader CaseType > > > > sources OpenFOAMReader CellArrayInfo > > > > sources OpenFOAMReader CellArrays > > > > sources OpenFOAMReader CreateCellToPoint > > > > sources OpenFOAMReader DecomposePolyhedra > > > > sources OpenFOAMReader FileName > > > > sources OpenFOAMReader LagrangianArrayInfo > > > > sources OpenFOAMReader LagrangianArrays > > > > sources OpenFOAMReader ListTimeStepsByControlDict > > > > sources OpenFOAMReader MeshRegions > > > > sources OpenFOAMReader PatchArrayInfo > > > > sources OpenFOAMReader PointArrayInfo > > > > sources OpenFOAMReader PointArrays > > > > sources OpenFOAMReader PositionsIsIn13Format > > > > sources OpenFOAMReader ReadZones > > > > sources OpenFOAMReader Refresh > > > > sources OpenFOAMReader TimestepValues > > > > sources OutlineSource Bounds > > > > sources P3DReader FileNameInfo > > > > sources P3DReader QFileName > > > > sources P3DReader TimestepValues > > > > sources P3DReader AutoDetectFormat > > > > sources P3DReader BinaryFile > > > > sources P3DReader ByteOrder > > > > sources P3DReader DoublePrecision > > > > sources P3DReader FileName > > > > sources P3DReader ForceRead > > > > sources P3DReader FunctionFileName > > > > sources P3DReader Functions > > > > sources P3DReader HasByteCount > > > > sources P3DReader IBlanking > > > > sources P3DReader MultiGrid > > > > sources P3DReader TwoDimensionalGeometry > > > > sources PNGSeriesReader FileNames > > > > sources PNGSeriesReader TimestepValues > > > > sources PVDReader FileName > > > > sources PVDReader TimestepValues > > > > sources PVTrivialProducer WholeExtent > > > > sources ParticleReader FileName > > > > sources ParticleReader FileNameInfo > > > > sources ParticleReader TimestepValues > > > > sources ParticleReader ByteOrder > > > > sources ParticleReader DataType > > > > sources ParticleReader FileType > > > > sources ParticleReader HasScalar > > > > sources PedigreeIDSelectionSource ContainingCells > > > > sources PedigreeIDSelectionSource FieldType > > > > sources PedigreeIDSelectionSource IDs > > > > sources PedigreeIDSelectionSource InsideOut > > > > sources PedigreeIDSelectionSource StringIDs > > > > sources PhastaReader FileName > > > > sources PhastaReader TimestepValues > > > > sources PlaneSource Origin > > > > sources PlaneSource Point1 > > > > sources PlaneSource Point2 > > > > sources PlaneSource XResolution > > > > sources PlaneSource YResolution > > > > sources Plot3DMetaReader FileName > > > > sources Plot3DMetaReader TimestepValues > > > > sources PointSource Center > > > > sources PointSource NumberOfPoints > > > > sources PointSource Radius > > > > sources ProStarReader FileName > > > > sources ProStarReader ScaleFactor > > > > sources ProgrammableSource InformationScript > > > > sources ProgrammableSource OutputDataSetType > > > > sources ProgrammableSource Parameters > > > > sources ProgrammableSource PythonPath > > > > sources ProgrammableSource Script > > > > sources RTAnalyticSource Center > > > > sources RTAnalyticSource Maximum > > > > sources RTAnalyticSource StandardDeviation > > > > sources RTAnalyticSource SubsampleRate > > > > sources RTAnalyticSource WholeExtent > > > > sources RTAnalyticSource XFreq > > > > sources RTAnalyticSource XMag > > > > sources RTAnalyticSource YFreq > > > > sources RTAnalyticSource YMag > > > > sources RTAnalyticSource ZFreq > > > > sources RTAnalyticSource ZMag > > > > sources RTXMLPolyDataReader FileName > > > > sources RTXMLPolyDataReader Location > > > > sources RTXMLPolyDataReader NewDataAvailable > > > > sources RTXMLPolyDataReader NextFileName > > > > sources RTXMLPolyDataReader ResetReader > > > > sources RTXMLPolyDataReader UpdateToNextFile > > > > sources Ruler Point1 > > > > sources Ruler Point2 > > > > sources SLACParticleReader FileName > > > > sources SLACParticleReader TimestepValues > > > > sources SLACReader FrequencyScale > > > > sources SLACReader FrequencyScaleInfo > > > > sources SLACReader MeshFileName > > > > sources SLACReader ModeFileName > > > > sources SLACReader PhaseShift > > > > sources SLACReader PhaseShiftInfo > > > > sources SLACReader ReadExternalSurface > > > > sources SLACReader ReadInternalVolume > > > > sources SLACReader ReadMidpoints > > > > sources SLACReader TimeRange > > > > sources SLACReader TimestepValues > > > > sources SPCTHRestartReader FileName > > > > sources SPCTHRestartReader TimestepValues > > > > sources SPCTHRestartReader UseMetaFile > > > > sources SPCTHRestartReader CellArrayInfo > > > > sources SPCTHRestartReader CellArrayStatus > > > > sources SPCTHRestartReader DistributeFiles > > > > sources SPCTHRestartReader DownConvertVolumeFraction > > > > sources SPCTHRestartReader GenerateActiveBlockArray > > > > sources SPCTHRestartReader GenerateBlockIdArray > > > > sources SPCTHRestartReader GenerateLevelArray > > > > sources SPCTHRestartReader GenerateMarkers > > > > sources SPCTHRestartReader GenerateTracers > > > > sources SelectionQuerySource CompositeIndex > > > > sources SelectionQuerySource FieldType > > > > sources SelectionQuerySource HierarchicalIndex > > > > sources SelectionQuerySource HierarchicalLevel > > > > sources SelectionQuerySource InsideOut > > > > sources SelectionQuerySource ProcessID > > > > sources SelectionQuerySource QueryString > > > > sources SelectionQuerySource UserFriendlyText > > > > sources SelectionSourceBase ContainingCells > > > > sources SelectionSourceBase FieldType > > > > sources SelectionSourceBase InsideOut > > > > sources SphereSource Center > > > > sources SphereSource EndPhi > > > > sources SphereSource EndTheta > > > > sources SphereSource PhiResolution > > > > sources SphereSource Radius > > > > sources SphereSource StartPhi > > > > sources SphereSource StartTheta > > > > sources SphereSource ThetaResolution > > > > sources SplineSource ParametricFunction > > > > sources SuperquadricSource Center > > > > sources SuperquadricSource PhiResolution > > > > sources SuperquadricSource PhiRoundness > > > > sources SuperquadricSource Scale > > > > sources SuperquadricSource Size > > > > sources SuperquadricSource ThetaResolution > > > > sources SuperquadricSource ThetaRoundness > > > > sources SuperquadricSource Thickness > > > > sources SuperquadricSource Toroidal > > > > sources TIFFReader FileName > > > > sources TIFFSeriesReader FileNames > > > > sources TIFFSeriesReader TimestepValues > > > > sources TecplotReader FileNameInfo > > > > sources TecplotReader FileNames > > > > sources TecplotReader TimestepValues > > > > sources TecplotReader DataArrayInfo > > > > sources TecplotReader DataArrayStatus > > > > sources Test3DWidget Resolution > > > > sources TextSource Text > > > > sources ThresholdSelectionSource ArrayName > > > > sources ThresholdSelectionSource ContainingCells > > > > sources ThresholdSelectionSource FieldType > > > > sources ThresholdSelectionSource InsideOut > > > > sources ThresholdSelectionSource Thresholds > > > > sources TimeSource Analytic > > > > sources TimeSource Growing > > > > sources TimeSource TimestepValues > > > > sources TimeSource X Amplitude > > > > sources TimeSource Y Amplitude > > > > sources TimeToTextConvertorSource Format > > > > sources UnstructuredPOPReader FileName > > > > sources UnstructuredPOPReader FileNameInfo > > > > sources UnstructuredPOPReader TimestepValues > > > > sources UnstructuredPOPReader Stride > > > > sources UnstructuredPOPReader VOI > > > > sources UnstructuredPOPReader VerticalVelocity > > > > sources VPICReader DefaultXExtent > > > > sources VPICReader DefaultYExtent > > > > sources VPICReader DefaultZExtent > > > > sources VPICReader FileName > > > > sources VPICReader PointArrayInfo > > > > sources VPICReader PointArrayStatus > > > > sources VPICReader SetStride > > > > sources VPICReader TimestepValues > > > > sources VPICReader XExtent > > > > sources VPICReader YExtent > > > > sources VPICReader ZExtent > > > > sources VectorText Text > > > > sources WindBladeReader Filename > > > > sources WindBladeReader PointArrayInfo > > > > sources WindBladeReader PointArrayStatus > > > > sources WindBladeReader TimestepValues > > > > sources XMLHierarchicalBoxDataReader FileName > > > > sources XMLHierarchicalBoxDataReader FileNameInfo > > > > sources XMLHierarchicalBoxDataReader TimestepValues > > > > sources XMLImageDataReader FileName > > > > sources XMLImageDataReader FileNameInfo > > > > sources XMLImageDataReader TimestepValues > > > > sources XMLImageDataReader CellArrayInfo > > > > sources XMLImageDataReader CellArrayStatus > > > > sources XMLImageDataReader PointArrayInfo > > > > sources XMLImageDataReader PointArrayStatus > > > > sources XMLMultiBlockDataReader FileName > > > > sources XMLMultiBlockDataReader FileNameInfo > > > > sources XMLMultiBlockDataReader TimestepValues > > > > sources XMLPImageDataReader FileName > > > > sources XMLPImageDataReader FileNameInfo > > > > sources XMLPImageDataReader TimestepValues > > > > sources XMLPImageDataReader CellArrayInfo > > > > sources XMLPImageDataReader CellArrayStatus > > > > sources XMLPImageDataReader PointArrayInfo > > > > sources XMLPImageDataReader PointArrayStatus > > > > sources XMLPPolyDataReader FileName > > > > sources XMLPPolyDataReader FileNameInfo > > > > sources XMLPPolyDataReader TimestepValues > > > > sources XMLPPolyDataReader CellArrayInfo > > > > sources XMLPPolyDataReader CellArrayStatus > > > > sources XMLPPolyDataReader PointArrayInfo > > > > sources XMLPPolyDataReader PointArrayStatus > > > > sources XMLPRectilinearGridReader FileName > > > > sources XMLPRectilinearGridReader FileNameInfo > > > > sources XMLPRectilinearGridReader TimestepValues > > > > sources XMLPRectilinearGridReader CellArrayInfo > > > > sources XMLPRectilinearGridReader CellArrayStatus > > > > sources XMLPRectilinearGridReader PointArrayInfo > > > > sources XMLPRectilinearGridReader PointArrayStatus > > > > sources XMLPStructuredGridReader FileName > > > > sources XMLPStructuredGridReader FileNameInfo > > > > sources XMLPStructuredGridReader TimestepValues > > > > sources XMLPStructuredGridReader CellArrayInfo > > > > sources XMLPStructuredGridReader CellArrayStatus > > > > sources XMLPStructuredGridReader PointArrayInfo > > > > sources XMLPStructuredGridReader PointArrayStatus > > > > sources XMLPUnstructuredGridReader FileName > > > > sources XMLPUnstructuredGridReader FileNameInfo > > > > sources XMLPUnstructuredGridReader TimestepValues > > > > sources XMLPUnstructuredGridReader CellArrayInfo > > > > sources XMLPUnstructuredGridReader CellArrayStatus > > > > sources XMLPUnstructuredGridReader PointArrayInfo > > > > sources XMLPUnstructuredGridReader PointArrayStatus > > > > sources XMLPolyDataEnsembleReader FileIndex > > > > sources XMLPolyDataEnsembleReader FileIndexRange > > > > sources XMLPolyDataEnsembleReader MetaFileName > > > > sources XMLPolyDataEnsembleReader TimestepValues > > > > sources XMLPolyDataEnsembleReader CellArrayInfo > > > > sources XMLPolyDataEnsembleReader CellArrayStatus > > > > sources XMLPolyDataEnsembleReader PointArrayInfo > > > > sources XMLPolyDataEnsembleReader PointArrayStatus > > > > sources XMLPolyDataEnsembleReader UseMetaFile > > > > sources XMLPolyDataReader FileName > > > > sources XMLPolyDataReader FileNameInfo > > > > sources XMLPolyDataReader TimestepValues > > > > sources XMLPolyDataReader CellArrayInfo > > > > sources XMLPolyDataReader CellArrayStatus > > > > sources XMLPolyDataReader PointArrayInfo > > > > sources XMLPolyDataReader PointArrayStatus > > > > sources XMLRectilinearGridReader FileName > > > > sources XMLRectilinearGridReader FileNameInfo > > > > sources XMLRectilinearGridReader TimestepValues > > > > sources XMLRectilinearGridReader CellArrayInfo > > > > sources XMLRectilinearGridReader CellArrayStatus > > > > sources XMLRectilinearGridReader PointArrayInfo > > > > sources XMLRectilinearGridReader PointArrayStatus > > > > sources XMLStructuredGridReader FileName > > > > sources XMLStructuredGridReader FileNameInfo > > > > sources XMLStructuredGridReader TimestepValues > > > > sources XMLStructuredGridReader CellArrayInfo > > > > sources XMLStructuredGridReader CellArrayStatus > > > > sources XMLStructuredGridReader PointArrayInfo > > > > sources XMLStructuredGridReader PointArrayStatus > > > > sources XMLUniformGridAMRReader FileName > > > > sources XMLUniformGridAMRReader FileNameInfo > > > > sources XMLUniformGridAMRReader TimestepValues > > > > sources XMLUniformGridAMRReader DefaultNumberOfLevels > > > > sources XMLUnstructuredGridReader FileName > > > > sources XMLUnstructuredGridReader FileNameInfo > > > > sources XMLUnstructuredGridReader TimestepValues > > > > sources XMLUnstructuredGridReader CellArrayInfo > > > > sources XMLUnstructuredGridReader CellArrayStatus > > > > sources XMLUnstructuredGridReader PointArrayInfo > > > > sources XMLUnstructuredGridReader PointArrayStatus > > > > sources XdmfReader FileNameInfo > > > > sources XdmfReader FileNames > > > > sources XdmfReader TimestepValues > > > > sources XdmfReader CellArrayInfo > > > > sources XdmfReader CellArrayStatus > > > > sources XdmfReader GridInfo > > > > sources XdmfReader GridStatus > > > > sources XdmfReader PointArrayInfo > > > > sources XdmfReader PointArrayStatus > > > > sources XdmfReader SILTimeStamp > > > > sources XdmfReader SetInfo > > > > sources XdmfReader SetStatus > > > > sources XdmfReader Stride > > > > sources byureader FileName > > > > sources ensight CaseFileName > > > > sources ensight CellArrayInfo > > > > sources ensight CellArrayStatus > > > > sources ensight PointArrayInfo > > > > sources ensight PointArrayStatus > > > > sources ensight TimestepValues > > > > sources ensightMS ByteOrder > > > > sources ensightMS CaseFileName > > > > sources ensightMS CellArrayInfo > > > > sources ensightMS CellArrayStatus > > > > sources ensightMS PointArrayInfo > > > > sources ensightMS PointArrayStatus > > > > sources ensightMS SetTimeValue > > > > sources ensightMS TimestepValues > > > > sources gaussiancubereader BScale > > > > sources gaussiancubereader FileName > > > > sources gaussiancubereader HBScale > > > > sources netCDFReader FileName > > > > sources netCDFReader TimestepValues > > > > sources netCDFReader DimensionInfo > > > > sources netCDFReader Dimensions > > > > sources netCDFReader OutputType > > > > sources netCDFReader ReplaceFillValueWithNan > > > > sources netCDFReader SphericalCoordinates > > > > sources netCDFReader VariableArrayInfo > > > > sources netCDFReader VariableDimensionInfo > > > > sources netCDFReader VerticalBias > > > > sources netCDFReader VerticalScale > > > > sources objreader FileName > > > > sources pdbreader FileName > > > > sources plyreader FileName > > > > sources pvtkfile FileName > > > > sources spcthhistoryreader CommentCharacter > > > > sources spcthhistoryreader Delimeter > > > > sources spcthhistoryreader FileName > > > > sources spcthhistoryreader TimestepValues > > > > sources spcthreader CellArrayInfo > > > > sources spcthreader CellArrayStatus > > > > sources spcthreader ComputeDerivedVariables > > > > sources spcthreader DistributeFiles > > > > sources spcthreader DownConvertVolumeFraction > > > > sources spcthreader FileName > > > > sources spcthreader GenerateActiveBlockArray > > > > sources spcthreader GenerateBlockIdArray > > > > sources spcthreader GenerateLevelArray > > > > sources spcthreader GenerateMarkers > > > > sources spcthreader GenerateTracers > > > > sources spcthreader MergeXYZComponents > > > > sources spcthreader TimestepValues > > > > sources stlreader FileNameInfo > > > > sources stlreader FileNames > > > > sources stlreader TimestepValues > > > > sources vrmlreader FileName > > > > sources xyzreader FileName > > > > sources xyzreader TimeStep > > > > filters AMRConnectivity Input > > > > filters AMRConnectivity Propagate Ghosts > > > > filters AMRConnectivity Resolve Blocks > > > > filters AMRConnectivity SelectMaterialArrays > > > > filters AMRConnectivity VolumeFractionSurfaceValue > > > > filters AMRCutPlane Center > > > > filters AMRCutPlane Input > > > > filters AMRCutPlane LevelOfResolution > > > > filters AMRCutPlane Normal > > > > filters AMRCutPlane UseNativeCutter > > > > filters AMRDualClip Input > > > > filters AMRDualClip InternalDecimation > > > > filters AMRDualClip MergePoints > > > > filters AMRDualClip MultiprocessCommunication > > > > filters AMRDualClip SelectMaterialArrays > > > > filters AMRDualClip VolumeFractionSurfaceValue > > > > filters AMRDualContour Capping > > > > filters AMRDualContour DegenerateCells > > > > filters AMRDualContour Input > > > > filters AMRDualContour MergePoints > > > > filters AMRDualContour MultiprocessCommunication > > > > filters AMRDualContour SelectMaterialArrays > > > > filters AMRDualContour SkipGhostCopy > > > > filters AMRDualContour Triangulate > > > > filters AMRDualContour VolumeFractionSurfaceValue > > > > filters AMRFragmentIntegration Input > > > > filters AMRFragmentIntegration SelectMassArrays > > > > filters AMRFragmentIntegration SelectMassWeightedArrays > > > > filters AMRFragmentIntegration SelectMaterialArrays > > > > filters AMRFragmentIntegration SelectVolumeWeightedArrays > > > > filters AMRFragmentsFilter Extract Surface > > > > filters AMRFragmentsFilter Input > > > > filters AMRFragmentsFilter Integrate Fragments > > > > filters AMRFragmentsFilter SelectMassArrays > > > > filters AMRFragmentsFilter SelectMassWeightedArrays > > > > filters AMRFragmentsFilter SelectMaterialArrays > > > > filters AMRFragmentsFilter SelectVolumeWeightedArrays > > > > filters AMRFragmentsFilter Use Watertight Surface > > > > filters AMRFragmentsFilter VolumeFractionSurfaceValue > > > > filters AMRResampleFilter Demand-Driven Mode > > > > filters AMRResampleFilter Input > > > > filters AMRResampleFilter Max > > > > filters AMRResampleFilter Min > > > > filters AMRResampleFilter Number of Samples > > > > filters AMRResampleFilter NumberOfPartitions > > > > filters AMRResampleFilter TransferToNodes > > > > filters AMRSlice EnablePrefetching > > > > filters AMRSlice ForwardUpstream > > > > filters AMRSlice Input > > > > filters AMRSlice Level > > > > filters AMRSlice Normal > > > > filters AMRSlice OffSet > > > > filters AMRToMultiBlock Input > > > > filters AnnotateAttributeData ArrayAssociation > > > > filters AnnotateAttributeData ArrayName > > > > filters AnnotateAttributeData ElementId > > > > filters AnnotateAttributeData Input > > > > filters AnnotateAttributeData Prefix > > > > filters AnnotateAttributeData ProcessId > > > > filters AnnotateGlobalData Input > > > > filters AnnotateGlobalData Prefix > > > > filters AnnotateGlobalData SelectArrays > > > > filters Append Input > > > > filters AppendAttributes Input > > > > filters AppendPolyData Input > > > > filters ArbitrarySourceStreamTracer ComputeVorticity > > > > filters ArbitrarySourceStreamTracer InitialIntegrationStep > > > > filters ArbitrarySourceStreamTracer Input > > > > filters ArbitrarySourceStreamTracer IntegrationDirection > > > > filters ArbitrarySourceStreamTracer IntegrationStepUnit > > > > filters ArbitrarySourceStreamTracer IntegratorType > > > > filters ArbitrarySourceStreamTracer MaximumError > > > > filters ArbitrarySourceStreamTracer MaximumIntegrationStep > > > > filters ArbitrarySourceStreamTracer MaximumNumberOfSteps > > > > filters ArbitrarySourceStreamTracer MaximumPropagation > > > > filters ArbitrarySourceStreamTracer MinimumIntegrationStep > > > > filters ArbitrarySourceStreamTracer SelectInputVectors > > > > filters ArbitrarySourceStreamTracer Source > > > > filters ArbitrarySourceStreamTracer TerminalSpeed > > > > filters AttributeDataToTableFilter AddMetaData > > > > filters AttributeDataToTableFilter FieldAssociation > > > > filters AttributeDataToTableFilter Input > > > > filters BlockIdScalars Input > > > > filters BrownianPoints Input > > > > filters BrownianPoints MaximumSpeed > > > > filters BrownianPoints MinimumSpeed > > > > filters CTHPart CapSurfaces > > > > filters CTHPart ClipPlane > > > > filters CTHPart GenerateTriangles > > > > filters CTHPart Input > > > > filters CTHPart RemoveGhostCells > > > > filters CTHPart VolumeArrays > > > > filters CTHPart VolumeFractionSurfaceValue > > > > filters CTHSurface Input > > > > filters CacheKeeper CacheTime > > > > filters CacheKeeper CachingEnabled > > > > filters CacheKeeper Input > > > > filters CacheKeeper RemoveAllCaches > > > > filters Calculator AttributeMode > > > > filters Calculator CoordinateResults > > > > filters Calculator Function > > > > filters Calculator Input > > > > filters Calculator ReplaceInvalidValues > > > > filters Calculator ReplacementValue > > > > filters Calculator ResultArrayName > > > > filters Calculator ResultNormals > > > > filters Calculator ResultTCoords > > > > filters CellCenters Input > > > > filters CellCenters VertexCells > > > > filters CellDataToPointData Input > > > > filters CellDataToPointData PassCellData > > > > filters CellDataToPointData PieceInvariant > > > > filters CellDerivatives Input > > > > filters CellDerivatives OutputTensorType > > > > filters CellDerivatives OutputVectorType > > > > filters CellDerivatives SelectInputScalars > > > > filters CellDerivatives SelectInputVectors > > > > filters CleanPolyData AbsoluteTolerance > > > > filters CleanPolyData ConvertLinesToPoints > > > > filters CleanPolyData ConvertPolysToLines > > > > filters CleanPolyData ConvertStripsToPolys > > > > filters CleanPolyData Input > > > > filters CleanPolyData PieceInvariant > > > > filters CleanPolyData PointMerging > > > > filters CleanPolyData Tolerance > > > > filters CleanPolyData ToleranceIsAbsolute > > > > filters CleanUnstructuredGrid Input > > > > filters CleanUnstructuredGridCells Input > > > > filters ClientServerMoveData Input > > > > filters ClientServerMoveData OutputDataType > > > > filters ClientServerMoveData WholeExtent > > > > filters Clip ClipFunction > > > > filters Clip Input > > > > filters Clip InputBounds > > > > filters Clip InsideOut > > > > filters Clip PreserveInputCells > > > > filters Clip SelectInputScalars > > > > filters Clip UseValueAsOffset > > > > filters Clip Value > > > > filters ClipClosedSurface BaseColor > > > > filters ClipClosedSurface ClipColor > > > > filters ClipClosedSurface ClippingPlane > > > > filters ClipClosedSurface GenerateFaces > > > > filters ClipClosedSurface GenerateOutline > > > > filters ClipClosedSurface Input > > > > filters ClipClosedSurface InsideOut > > > > filters ClipClosedSurface ScalarMode > > > > filters ClipClosedSurface Tolerance > > > > filters ColorByArray Input > > > > filters ColorByArray LookupTable > > > > filters ColorByArray NaNColor > > > > filters ColorByArray OutputFormat > > > > filters ColorByArray SelectInputScalars > > > > filters ComputeQuartiles Input > > > > filters ContingencyStatistics AttributeMode > > > > filters ContingencyStatistics Input > > > > filters ContingencyStatistics ModelInput > > > > filters ContingencyStatistics SelectArrays > > > > filters ContingencyStatistics Task > > > > filters ContingencyStatistics TrainingFraction > > > > filters Contour ComputeGradients > > > > filters Contour ComputeNormals > > > > filters Contour ComputeScalars > > > > filters Contour ContourValues > > > > filters Contour GenerateTriangles > > > > filters Contour Input > > > > filters Contour Locator > > > > filters Contour SelectInputScalars > > > > filters ConvertSelection ArrayNames > > > > filters ConvertSelection DataInput > > > > filters ConvertSelection Input > > > > filters ConvertSelection MatchAnyValues > > > > filters ConvertSelection OutputType > > > > filters Curvatures CurvatureType > > > > filters Curvatures Input > > > > filters Curvatures InvertMeanCurvature > > > > filters Cut ContourValues > > > > filters Cut CutFunction > > > > filters Cut Input > > > > filters Cut InputBounds > > > > filters Cut PreserveInputCells > > > > filters Cut Triangulate the slice > > > > filters CutEverything ContourValues > > > > filters CutEverything CutFunction > > > > filters CutEverything Input > > > > filters CutEverything InputBounds > > > > filters DataSetSurfaceFilter Input > > > > filters DataSetSurfaceFilter NonlinearSubdivisionLevel > > > > filters DataSetSurfaceFilter PieceInvariant > > > > filters DataSetTriangleFilter Input > > > > filters DecimatePro BoundaryVertexDeletion > > > > filters DecimatePro FeatureAngle > > > > filters DecimatePro Input > > > > filters DecimatePro PreserveTopology > > > > filters DecimatePro TargetReduction > > > > filters Delaunay2D Alpha > > > > filters Delaunay2D BoundingTriangulation > > > > filters Delaunay2D Input > > > > filters Delaunay2D Offset > > > > filters Delaunay2D ProjectionPlaneMode > > > > filters Delaunay2D Tolerance > > > > filters Delaunay3D Alpha > > > > filters Delaunay3D AlphaLines > > > > filters Delaunay3D AlphaTets > > > > filters Delaunay3D AlphaTris > > > > filters Delaunay3D AlphaVerts > > > > filters Delaunay3D BoundingTriangulation > > > > filters Delaunay3D Input > > > > filters Delaunay3D Offset > > > > filters Delaunay3D Tolerance > > > > filters DescriptiveStatistics AttributeMode > > > > filters DescriptiveStatistics Input > > > > filters DescriptiveStatistics ModelInput > > > > filters DescriptiveStatistics SelectArrays > > > > filters DescriptiveStatistics SignedDeviations > > > > filters DescriptiveStatistics Task > > > > filters DescriptiveStatistics TrainingFraction > > > > filters ElevationFilter HighPoint > > > > filters ElevationFilter Input > > > > filters ElevationFilter LowPoint > > > > filters ElevationFilter ScalarRange > > > > filters ExtractBagPlots Input > > > > filters ExtractBagPlots RobustPCA > > > > filters ExtractBagPlots SelectArrays > > > > filters ExtractBagPlots Sigma > > > > filters ExtractBagPlots TransposeTable > > > > filters ExtractBlock BlockIndices > > > > filters ExtractBlock Input > > > > filters ExtractBlock MaintainStructure > > > > filters ExtractBlock PruneOutput > > > > filters ExtractEdges Input > > > > filters ExtractFieldDataOverTime Input > > > > filters ExtractGeometry Extract intersected > > > > filters ExtractGeometry Extract only intersected > > > > filters ExtractGeometry ExtractInside > > > > filters ExtractGeometry ImplicitFunction > > > > filters ExtractGeometry Input > > > > filters ExtractGeometry InputBounds > > > > filters ExtractGrid IncludeBoundary > > > > filters ExtractGrid Input > > > > filters ExtractGrid SampleRateI > > > > filters ExtractGrid SampleRateJ > > > > filters ExtractGrid SampleRateK > > > > filters ExtractGrid VOI > > > > filters ExtractHierarchicalDataSets Input > > > > filters ExtractHierarchicalDataSets SelectedDataSets > > > > filters ExtractHierarchicalLevel Input > > > > filters ExtractHierarchicalLevel Levels > > > > filters ExtractHistogram BinCount > > > > filters ExtractHistogram CalculateAverages > > > > filters ExtractHistogram Component > > > > filters ExtractHistogram CustomBinRanges > > > > filters ExtractHistogram Input > > > > filters ExtractHistogram SelectInputArray > > > > filters ExtractHistogram UseCustomBinRanges > > > > filters ExtractLocation Input > > > > filters ExtractLocation Location > > > > filters ExtractLocation Mode > > > > filters ExtractSelection Input > > > > filters ExtractSelection PreserveTopology > > > > filters ExtractSelection Selection > > > > filters ExtractSelection ShowBounds > > > > filters ExtractSelectionOverTime Input > > > > filters ExtractSelectionOverTime Only Report Selection Statistics > > > > filters ExtractSelectionOverTime Selection > > > > filters FFTSelectionOverTime Input > > > > filters FFTSelectionOverTime Selection > > > > filters FeatureEdges BoundaryEdges > > > > filters FeatureEdges Coloring > > > > filters FeatureEdges FeatureAngle > > > > filters FeatureEdges FeatureEdges > > > > filters FeatureEdges Input > > > > filters FeatureEdges ManifoldEdges > > > > filters FeatureEdges NonManifoldEdges > > > > filters FlattenFilter Input > > > > filters GaussianSplatter Accumulation Mode > > > > filters GaussianSplatter CapValue > > > > filters GaussianSplatter Capping > > > > filters GaussianSplatter Eccentricity > > > > filters GaussianSplatter ExponentFactor > > > > filters GaussianSplatter Input > > > > filters GaussianSplatter ModelBounds > > > > filters GaussianSplatter NormalWarping > > > > filters GaussianSplatter NullValue > > > > filters GaussianSplatter Radius > > > > filters GaussianSplatter SampleDimensions > > > > filters GaussianSplatter ScalarWarping > > > > filters GaussianSplatter ScaleFactor > > > > filters GaussianSplatter SelectInputScalars > > > > filters GenerateIdScalars ArrayName > > > > filters GenerateIdScalars Input > > > > filters GenericClip ClipFunction > > > > filters GenericClip Input > > > > filters GenericClip InputBounds > > > > filters GenericClip InsideOut > > > > filters GenericClip SelectInputScalars > > > > filters GenericClip Value > > > > filters GenericContour ComputeGradients > > > > filters GenericContour ComputeNormals > > > > filters GenericContour ComputeScalars > > > > filters GenericContour ContourValues > > > > filters GenericContour Input > > > > filters GenericContour Locator > > > > filters GenericContour SelectInputScalars > > > > filters GenericCut ContourValues > > > > filters GenericCut CutFunction > > > > filters GenericCut Input > > > > filters GenericCut InputBounds > > > > filters GenericGeometryFilter Input > > > > filters GenericGeometryFilter PassThroughCellIds > > > > filters GenericOutlineFilter Input > > > > filters GenericStreamTracer InitialIntegrationStep > > > > filters GenericStreamTracer Input > > > > filters GenericStreamTracer IntegrationDirection > > > > filters GenericStreamTracer IntegrationStepUnit > > > > filters GenericStreamTracer IntegratorType > > > > filters GenericStreamTracer MaximumError > > > > filters GenericStreamTracer MaximumIntegrationStep > > > > filters GenericStreamTracer MaximumNumberOfSteps > > > > filters GenericStreamTracer MaximumPropagation > > > > filters GenericStreamTracer MinimumIntegrationStep > > > > filters GenericStreamTracer SelectInputVectors > > > > filters GenericStreamTracer Source > > > > filters GenericStreamTracer TerminalSpeed > > > > filters GenericTessellator Input > > > > filters GeometryFilter ForceStrips > > > > filters GeometryFilter Input > > > > filters GeometryFilter NonlinearSubdivisionLevel > > > > filters GeometryFilter PassThroughIds > > > > filters GeometryFilter PassThroughPointIds > > > > filters GeometryFilter UseOutline > > > > filters GeometryFilter UseStrips > > > > filters Glyph GlyphMode > > > > filters Glyph GlyphTransform > > > > filters Glyph Input > > > > filters Glyph MaximumNumberOfSamplePoints > > > > filters Glyph Orient > > > > filters Glyph Scalars > > > > filters Glyph ScaleFactor > > > > filters Glyph ScaleMode > > > > filters Glyph Seed > > > > filters Glyph Source > > > > filters Glyph Stride > > > > filters Glyph Vectors > > > > filters GlyphWithCustomSource GlyphMode > > > > filters GlyphWithCustomSource GlyphTransform > > > > filters GlyphWithCustomSource Input > > > > filters GlyphWithCustomSource MaximumNumberOfSamplePoints > > > > filters GlyphWithCustomSource Orient > > > > filters GlyphWithCustomSource Scalars > > > > filters GlyphWithCustomSource ScaleFactor > > > > filters GlyphWithCustomSource ScaleMode > > > > filters GlyphWithCustomSource Seed > > > > filters GlyphWithCustomSource Source > > > > filters GlyphWithCustomSource Stride > > > > filters GlyphWithCustomSource Vectors > > > > filters Gradient Dimensionality > > > > filters Gradient Input > > > > filters Gradient SelectInputScalars > > > > filters GradientMagnitude Dimensionality > > > > filters GradientMagnitude Input > > > > filters GridConnectivity Input > > > > filters GroupDataSets Input > > > > filters ImageClip Input > > > > filters ImageClip OutputWholeExtent > > > > filters ImageDataToAMR Input > > > > filters ImageDataToAMR MaximumNumberOfLevels > > > > filters ImageDataToAMR NumberOfLevels > > > > filters ImageDataToAMR RefinementRatio > > > > filters ImageDataToPointSet Input > > > > filters ImageDataToUniformGrid Input > > > > filters ImageDataToUniformGrid Reverse > > > > filters ImageDataToUniformGrid SelectInputScalars > > > > filters ImageResampling CustomSamplingBounds > > > > filters ImageResampling Input > > > > filters ImageResampling SamplingDimension > > > > filters ImageResampling UseInputBounds > > > > filters ImageShrink Averaging > > > > filters ImageShrink Input > > > > filters ImageShrink ShrinkFactors > > > > filters IntegrateAttributes Input > > > > filters IntegrateFlowThroughSurface Input > > > > filters IntegrateFlowThroughSurface SelectInputVectors > > > > filters IntersectFragments CutFunction > > > > filters IntersectFragments Input > > > > filters IntersectFragments Source > > > > filters IsoVolume Input > > > > filters IsoVolume SelectInputScalars > > > > filters IsoVolume ThresholdBetween > > > > filters KMeans AttributeMode > > > > filters KMeans Input > > > > filters KMeans K > > > > filters KMeans MaxNumIterations > > > > filters KMeans ModelInput > > > > filters KMeans SelectArrays > > > > filters KMeans Task > > > > filters KMeans Tolerance > > > > filters KMeans TrainingFraction > > > > filters LegacyArbitrarySourceGlyph Input > > > > filters LegacyArbitrarySourceGlyph KeepRandomPoints > > > > filters LegacyArbitrarySourceGlyph MaximumNumberOfPoints > > > > filters LegacyArbitrarySourceGlyph RandomMode > > > > filters LegacyArbitrarySourceGlyph SelectInputScalars > > > > filters LegacyArbitrarySourceGlyph SelectInputVectors > > > > filters LegacyArbitrarySourceGlyph SetOrient > > > > filters LegacyArbitrarySourceGlyph SetScaleFactor > > > > filters LegacyArbitrarySourceGlyph SetScaleMode > > > > filters LegacyArbitrarySourceGlyph Source > > > > filters LegacyArbitrarySourceGlyph UseMaskPoints > > > > filters LegacyGlyph GlyphTransform > > > > filters LegacyGlyph Input > > > > filters LegacyGlyph KeepRandomPoints > > > > filters LegacyGlyph MaximumNumberOfPoints > > > > filters LegacyGlyph RandomMode > > > > filters LegacyGlyph SelectInputScalars > > > > filters LegacyGlyph SelectInputVectors > > > > filters LegacyGlyph SetOrient > > > > filters LegacyGlyph SetScaleFactor > > > > filters LegacyGlyph SetScaleMode > > > > filters LegacyGlyph Source > > > > filters LegacyGlyph UseMaskPoints > > > > filters LinearExtrusionFilter Capping > > > > filters LinearExtrusionFilter Input > > > > filters LinearExtrusionFilter PieceInvariant > > > > filters LinearExtrusionFilter ScaleFactor > > > > filters LinearExtrusionFilter Vector > > > > filters LoopSubdivisionFilter Input > > > > filters LoopSubdivisionFilter NumberOfSubdivisions > > > > filters MPIMoveData Input > > > > filters MPIMoveData MoveMode > > > > filters MPIMoveData OutputDataType > > > > filters MaskPoints GenerateVertices > > > > filters MaskPoints Input > > > > filters MaskPoints MaximumNumberOfPoints > > > > filters MaskPoints Offset > > > > filters MaskPoints OnRatio > > > > filters MaskPoints ProportionalMaximumNumberOfPoints > > > > filters MaskPoints RandomMode > > > > filters MaskPoints RandomModeType > > > > filters MaskPoints SingleVertexPerCell > > > > filters MaterialInterfaceFilter ClipFunction > > > > filters MaterialInterfaceFilter ComputeOBB > > > > filters MaterialInterfaceFilter Input > > > > filters MaterialInterfaceFilter InvertVolumeFraction > > > > filters MaterialInterfaceFilter MaterialFractionThreshold > > > > filters MaterialInterfaceFilter OutputBaseName > > > > filters MaterialInterfaceFilter SelectMassArray > > > > filters MaterialInterfaceFilter SelectMassWtdAvgArray > > > > filters MaterialInterfaceFilter SelectMaterialArray > > > > filters MaterialInterfaceFilter SelectVolumeWtdAvgArray > > > > filters MaterialInterfaceFilter WriteGeometryOutput > > > > filters MaterialInterfaceFilter WriteStatisticsOutput > > > > filters Median Input > > > > filters Median KernelSize > > > > filters Median SelectInputScalars > > > > filters MergeBlocks Input > > > > filters MergeBlocks MergePoints > > > > filters MergeBlocks SubTreeCompositeIndex > > > > filters MeshQuality HexQualityMeasure > > > > filters MeshQuality Input > > > > filters MeshQuality QuadQualityMeasure > > > > filters MeshQuality TetQualityMeasure > > > > filters MeshQuality TriangleQualityMeasure > > > > filters MinMax Input > > > > filters MinMax Operation > > > > filters MulticorrelativeStatistics AttributeMode > > > > filters MulticorrelativeStatistics Input > > > > filters MulticorrelativeStatistics ModelInput > > > > filters MulticorrelativeStatistics SelectArrays > > > > filters MulticorrelativeStatistics Task > > > > filters MulticorrelativeStatistics TrainingFraction > > > > filters NonOverlappingLevelIdScalars Input > > > > filters NormalGlyphs Consistency > > > > filters NormalGlyphs Glyph Max. Points > > > > filters NormalGlyphs Glyph Scale Factor > > > > filters NormalGlyphs Input > > > > filters NormalGlyphs InvertArrow > > > > filters OctreeDepthLimit Input > > > > filters OctreeDepthLimit MaximumLevel > > > > filters OctreeDepthScalars Input > > > > filters OrderedCompositeDistributor Input > > > > filters OrderedCompositeDistributor OutputType > > > > filters OrderedCompositeDistributor PKdTree > > > > filters OrderedCompositeDistributor PassThrough > > > > filters OutlineCornerFilter CornerFactor > > > > filters OutlineCornerFilter Input > > > > filters OutlineFilter Input > > > > filters OverlappingLevelIdScalars Input > > > > filters PCAStatistics AttributeMode > > > > filters PCAStatistics BasisEnergy > > > > filters PCAStatistics BasisScheme > > > > filters PCAStatistics BasisSize > > > > filters PCAStatistics Input > > > > filters PCAStatistics ModelInput > > > > filters PCAStatistics NormalizationScheme > > > > filters PCAStatistics RobustPCA > > > > filters PCAStatistics SelectArrays > > > > filters PCAStatistics Task > > > > filters PCAStatistics TrainingFraction > > > > filters PVConnectivityFilter ColorRegions > > > > filters PVConnectivityFilter ExtractionMode > > > > filters PVConnectivityFilter Input > > > > filters PVExtractSelection Input > > > > filters PVExtractSelection Selection > > > > filters ParticlePath ComputeVorticity > > > > filters ParticlePath DisableResetCache > > > > filters ParticlePath ForceReinjectionEveryNSteps > > > > filters ParticlePath Input > > > > filters ParticlePath SelectInputVectors > > > > filters ParticlePath Source > > > > filters ParticlePath StaticMesh > > > > filters ParticlePath StaticSeeds > > > > filters ParticlePath TerminationTime > > > > filters ParticlePath TimestepValues > > > > filters ParticlePathLines IdChannelArray > > > > filters ParticlePathLines Input > > > > filters ParticlePathLines MaskPoints > > > > filters ParticlePathLines MaxStepDistance > > > > filters ParticlePathLines MaxTrackLength > > > > filters ParticlePathLines Selection > > > > filters ParticleTracer ComputeVorticity > > > > filters ParticleTracer ForceReinjectionEveryNSteps > > > > filters ParticleTracer Input > > > > filters ParticleTracer SelectInputVectors > > > > filters ParticleTracer Source > > > > filters ParticleTracer StaticMesh > > > > filters ParticleTracer StaticSeeds > > > > filters ParticleTracer TimestepValues > > > > filters PassArrays CellDataArrays > > > > filters PassArrays FieldDataArrays > > > > filters PassArrays Input > > > > filters PassArrays PointDataArrays > > > > filters PassArrays SelectedFieldTypes > > > > filters PassArrays UseFieldTypes > > > > filters PassThrough Input > > > > filters PlotAttributes Input > > > > filters PlotOnIntersectionCurves Input > > > > filters PlotOnIntersectionCurves Slice Type > > > > filters PlotOnSortedLines Input > > > > filters PointDataToCellData Input > > > > filters PointDataToCellData PassPointData > > > > filters PolyDataNormals ComputeCellNormals > > > > filters PolyDataNormals Consistency > > > > filters PolyDataNormals FeatureAngle > > > > filters PolyDataNormals FlipNormals > > > > filters PolyDataNormals Input > > > > filters PolyDataNormals NonManifoldTraversal > > > > filters PolyDataNormals PieceInvariant > > > > filters PolyDataNormals Splitting > > > > filters PolyLineToRectilinearGrid Input > > > > filters Probe ComputeTolerance > > > > filters Probe Input > > > > filters Probe PassCellArrays > > > > filters Probe PassFieldArrays > > > > filters Probe PassPointArrays > > > > filters Probe Source > > > > filters Probe Tolerance > > > > filters ProbeLine ComputeTolerance > > > > filters ProbeLine Input > > > > filters ProbeLine PassPartialArrays > > > > filters ProbeLine Source > > > > filters ProbeLine Tolerance > > > > filters ProbePoint ComputeTolerance > > > > filters ProbePoint Input > > > > filters ProbePoint PassFieldArrays > > > > filters ProbePoint Source > > > > filters ProbePoint Tolerance > > > > filters ProcessIdScalars Input > > > > filters ProcessIdScalars RandomMode > > > > filters ProgrammableFilter CopyArrays > > > > filters ProgrammableFilter InformationScript > > > > filters ProgrammableFilter Input > > > > filters ProgrammableFilter OutputDataSetType > > > > filters ProgrammableFilter Parameters > > > > filters ProgrammableFilter PythonPath > > > > filters ProgrammableFilter Script > > > > filters ProgrammableFilter UpdateExtentScript > > > > filters PythonAnnotation AnnotationValue > > > > filters PythonAnnotation ArrayAssociation > > > > filters PythonAnnotation Expression > > > > filters PythonAnnotation Input > > > > filters PythonCalculator ArrayAssociation > > > > filters PythonCalculator ArrayName > > > > filters PythonCalculator CopyArrays > > > > filters PythonCalculator Expression > > > > filters PythonCalculator Input > > > > filters QuadraturePointInterpolator Input > > > > filters QuadraturePointInterpolator QuadratureSchemeDefinition > > > > filters QuadraturePointsGenerator Input > > > > filters QuadraturePointsGenerator QuadratureSchemeDefinition > > > > filters QuadratureSchemeDictionaryGenerator Input > > > > filters QuadricClustering CopyCellData > > > > filters QuadricClustering Input > > > > filters QuadricClustering NumberOfDivisions > > > > filters QuadricClustering UseFeatureEdges > > > > filters QuadricClustering UseFeaturePoints > > > > filters QuadricClustering UseInputPoints > > > > filters QuadricClustering UseInternalTriangles > > > > filters RandomAttributeGenerator AttributesConstantPerBlock > > > > filters RandomAttributeGenerator ComponentRange > > > > filters RandomAttributeGenerator DataType > > > > filters RandomAttributeGenerator GenerateCellScalars > > > > filters RandomAttributeGenerator GenerateCellVectors > > > > filters RandomAttributeGenerator GeneratePointScalars > > > > filters RandomAttributeGenerator GeneratePointVectors > > > > filters RandomAttributeGenerator Input > > > > filters RectilinearGridConnectivity AddDoubleVolumeArrayName > > > > filters RectilinearGridConnectivity AddFloatVolumeArrayName > > > > filters RectilinearGridConnectivity AddUnsignedCharVolumeArrayName > > > > filters RectilinearGridConnectivity Input > > > > filters RectilinearGridConnectivity VolumeFractionSurfaceValue > > > > filters RectilinearGridGeometryFilter Input > > > > filters RectilinearGridToPointSet Input > > > > filters ReductionFilter GenerateProcessIds > > > > filters ReductionFilter Input > > > > filters ReductionFilter PassThrough > > > > filters ReductionFilter PostGatherHelper > > > > filters ReductionFilter PostGatherHelperName > > > > filters ReductionFilter PreGatherHelper > > > > filters ReductionFilter PreGatherHelperName > > > > filters ReflectionFilter Center > > > > filters ReflectionFilter CopyInput > > > > filters ReflectionFilter Input > > > > filters ReflectionFilter Plane > > > > filters RibbonFilter Angle > > > > filters RibbonFilter DefaultNormal > > > > filters RibbonFilter Input > > > > filters RibbonFilter SelectInputScalars > > > > filters RibbonFilter SelectInputVectors > > > > filters RibbonFilter UseDefaultNormal > > > > filters RibbonFilter VaryWidth > > > > filters RibbonFilter Width > > > > filters RotationalExtrusionFilter Angle > > > > filters RotationalExtrusionFilter Capping > > > > filters RotationalExtrusionFilter DeltaRadius > > > > filters RotationalExtrusionFilter Input > > > > filters RotationalExtrusionFilter Resolution > > > > filters RotationalExtrusionFilter Translation > > > > filters ScatterPlot Input > > > > filters ShrinkFilter Input > > > > filters ShrinkFilter ShrinkFactor > > > > filters SliceAlongPolyLine Dataset > > > > filters SliceAlongPolyLine PolyLine > > > > filters SliceAlongPolyLine Tolerance > > > > filters SmoothPolyDataFilter Convergence > > > > filters SmoothPolyDataFilter Input > > > > filters SmoothPolyDataFilter NumberOfIterations > > > > filters StreakLine ComputeVorticity > > > > filters StreakLine DisableResetCache > > > > filters StreakLine ForceReinjectionEveryNSteps > > > > filters StreakLine Input > > > > filters StreakLine SelectInputVectors > > > > filters StreakLine Source > > > > filters StreakLine StaticMesh > > > > filters StreakLine StaticSeeds > > > > filters StreakLine TerminationTime > > > > filters StreakLine TimestepValues > > > > filters StreamTracer ComputeVorticity > > > > filters StreamTracer InitialIntegrationStep > > > > filters StreamTracer Input > > > > filters StreamTracer IntegrationDirection > > > > filters StreamTracer IntegrationStepUnit > > > > filters StreamTracer IntegratorType > > > > filters StreamTracer InterpolatorType > > > > filters StreamTracer MaximumError > > > > filters StreamTracer MaximumIntegrationStep > > > > filters StreamTracer MaximumNumberOfSteps > > > > filters StreamTracer MaximumPropagation > > > > filters StreamTracer MinimumIntegrationStep > > > > filters StreamTracer SelectInputVectors > > > > filters StreamTracer Source > > > > filters StreamTracer TerminalSpeed > > > > filters Stripper Input > > > > filters Stripper MaximumLength > > > > filters StructuredGridOutlineFilter Input > > > > filters Subdivide Input > > > > filters Subdivide NumberOfSubdivisions > > > > filters SurfaceVectors ConstraintMode > > > > filters SurfaceVectors Input > > > > filters SurfaceVectors SelectInputVectors > > > > filters TableFFT Input > > > > filters TableToPolyData Create2DPoints > > > > filters TableToPolyData Input > > > > filters TableToPolyData KeepAllDataArrays > > > > filters TableToPolyData XColumn > > > > filters TableToPolyData YColumn > > > > filters TableToPolyData ZColumn > > > > filters TableToStructuredGrid Input > > > > filters TableToStructuredGrid WholeExtent > > > > filters TableToStructuredGrid XColumn > > > > filters TableToStructuredGrid YColumn > > > > filters TableToStructuredGrid ZColumn > > > > filters TemporalCache CacheSize > > > > filters TemporalCache Input > > > > filters TemporalCache TimestepValues > > > > filters TemporalInterpolator DiscreteTimeStepInterval > > > > filters TemporalInterpolator Input > > > > filters TemporalInterpolator TimeRange > > > > filters TemporalInterpolator TimestepValues > > > > filters TemporalShiftScale Input > > > > filters TemporalShiftScale MaximumNumberOfPeriods > > > > filters TemporalShiftScale Periodic > > > > filters TemporalShiftScale PeriodicEndCorrection > > > > filters TemporalShiftScale PostShift > > > > filters TemporalShiftScale PreShift > > > > filters TemporalShiftScale Scale > > > > filters TemporalShiftScale TimestepValues > > > > filters TemporalSnapToTimeStep Input > > > > filters TemporalSnapToTimeStep SnapMode > > > > filters TemporalSnapToTimeStep TimestepValues > > > > filters TemporalStatistics ComputeAverage > > > > filters TemporalStatistics ComputeMaximum > > > > filters TemporalStatistics ComputeMinimum > > > > filters TemporalStatistics ComputeStandardDeviation > > > > filters TemporalStatistics Input > > > > filters TensorGlyph ColorGlyphs > > > > filters TensorGlyph ColorMode > > > > filters TensorGlyph ExtractEigenvalues > > > > filters TensorGlyph Input > > > > filters TensorGlyph LimitScalingByEigenvalues > > > > filters TensorGlyph MaxScaleFactor > > > > filters TensorGlyph ScaleFactor > > > > filters TensorGlyph SelectInputScalars > > > > filters TensorGlyph SelectInputTensors > > > > filters TensorGlyph Source > > > > filters TensorGlyph Symmetric > > > > filters TensorGlyph ThreeGlyphs > > > > filters TessellatorFilter ChordError > > > > filters TessellatorFilter FieldError2 > > > > filters TessellatorFilter Input > > > > filters TessellatorFilter MaximumNumberOfSubdivisions > > > > filters TessellatorFilter MergePoints > > > > filters TessellatorFilter OutputDimension > > > > filters TessellatorFilter ResetFieldCriteria > > > > filters TextureMapToCylinder Input > > > > filters TextureMapToCylinder PreventSeam > > > > filters TextureMapToPlane Input > > > > filters TextureMapToSphere Input > > > > filters TextureMapToSphere PreventSeam > > > > filters Threshold AllScalars > > > > filters Threshold Input > > > > filters Threshold SelectInputScalars > > > > filters Threshold ThresholdBetween > > > > filters Threshold UseContinuousCellRange > > > > filters TimeToTextConvertor Format > > > > filters TimeToTextConvertor Input > > > > filters TimeToTextConvertor Scale > > > > filters TimeToTextConvertor Shift > > > > filters TransformFilter Input > > > > filters TransformFilter Transform > > > > filters TransposeTable AddIdColumn > > > > filters TransposeTable DoNotTranspose > > > > filters TransposeTable Input > > > > filters TransposeTable SelectArrays > > > > filters TransposeTable UseIdColumn > > > > filters TriangleFilter Input > > > > filters TubeFilter Capping > > > > filters TubeFilter DefaultNormal > > > > filters TubeFilter Input > > > > filters TubeFilter NumberOfSides > > > > filters TubeFilter Radius > > > > filters TubeFilter RadiusFactor > > > > filters TubeFilter SelectInputScalars > > > > filters TubeFilter SelectInputVectors > > > > filters TubeFilter UseDefaultNormal > > > > filters TubeFilter VaryRadius > > > > filters UnstructuredGradient ComputeQCriterion > > > > filters UnstructuredGradient ComputeVorticity > > > > filters UnstructuredGradient FasterApproximation > > > > filters UnstructuredGradient Input > > > > filters UnstructuredGradient QCriterionArrayName > > > > filters UnstructuredGradient ResultArrayName > > > > filters UnstructuredGradient SelectInputScalars > > > > filters UnstructuredGradient VorticityArrayName > > > > filters UpdateSuppressor2 Enabled > > > > filters UpdateSuppressor2 ForceUpdate > > > > filters UpdateSuppressor2 Input > > > > filters UpdateSuppressor2 UpdateTime > > > > filters WarpScalar Input > > > > filters WarpScalar Normal > > > > filters WarpScalar ScaleFactor > > > > filters WarpScalar SelectInputScalars > > > > filters WarpScalar UseNormal > > > > filters WarpScalar XYPlane > > > > filters WarpVector Input > > > > filters WarpVector ScaleFactor > > > > filters WarpVector SelectInputVectors > > > > filters YoungsMaterialInterface AxisSymetric > > > > filters YoungsMaterialInterface FillMaterial > > > > filters YoungsMaterialInterface Input > > > > filters YoungsMaterialInterface InverseNormal > > > > filters YoungsMaterialInterface NormalArrays > > > > filters YoungsMaterialInterface NumberOfDomainsInformation > > > > filters YoungsMaterialInterface OnionPeel > > > > filters YoungsMaterialInterface OrderingArrays > > > > filters YoungsMaterialInterface ReverseMaterialOrder > > > > filters YoungsMaterialInterface UseFractionAsDistance > > > > filters YoungsMaterialInterface VolumeFractionArrays > > > > filters YoungsMaterialInterface VolumeFractionRange > > > > filters GlyphSpeed Input > > > > filters GlyphSpeed Scalars > > > > Traceback (most recent call last): > > > > File "", line 1, in > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/simple.py", > > line 39, in > > > > import servermanager > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > > line 3185, in > > > > __initialize() > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > > line 3176, in __initialize > > > > c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > > line 1932, in __init__ > > > > _createModules(self.Modules) > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > > line 2564, in _createModules > > > > m.filters = createModule('filters') > > > > File > > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > > line 2627, in createModule > > > > if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ > > > > AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' > > > >>>> > > > > > > On Thu, Feb 26, 2015 at 3:06 PM, Utkarsh Ayachit > > wrote: > >> > >> It is believable, let me see if I can find a 10.10 here to reproduce > >> the problem. > >> > >> Another thing to try: > >> > >> 1. edit > >> > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py" > >> 2. before line 2626, add the following: > >> print groupName, proxyName, propName > >> > >> Let's see which proxy this is failing for. > >> > >> Utkarsh > >> > >> > >> > >> > >> On Thu, Feb 26, 2015 at 3:53 PM, Matei Stroila > > >> wrote: > >> > I do not have any plugin auto-loaded. Also I just tried now with the > OS > >> > X > >> > default Python and I get the same errors. > >> > Could be a 10.10 issue? I built ParaView on a 10.9 machine yesterday > >> > with no > >> > issues (ParaView from git, the release branch, 4.3.1). > >> > > >> > Matei > >> > > >> > On Thu, Feb 26, 2015 at 2:10 PM, Utkarsh Ayachit > >> > wrote: > >> >> > >> >> How was ParaView built? I am not sure if Homebrew Python is different > >> >> from the one packaged in OsX, but binaries on paraview.org are built > >> >> using OsX default Python. > >> >> > >> >> Also, do you have any plugins that are being auto-loaded? If you're > >> >> running pvpython, try running with "-dr" argument. That will avoid > >> >> loading any auto-load plugins. Does that help? > >> >> > >> >> Utkarsh > >> >> > >> >> On Thu, Feb 26, 2015 at 3:03 PM, Matei Stroila > >> >> > >> >> wrote: > >> >> > Not sure if other people have seen this. Using Python from Homebrew > >> >> > on > >> >> > Mac > >> >> > OS X 10.10, got the same error on two different Macs. > >> >> > > >> >> > Python 2.7.9 (default, Dec 19 2014, 06:00:59) > >> >> > > >> >> > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin > >> >> > > >> >> >>>> from paraview.simple import * > >> >> > > >> >> > Traceback (most recent call last): > >> >> > > >> >> > File "", line 1, in > >> >> > > >> >> > File > >> >> > > >> >> > > >> >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/simple.py", > >> >> > line 39, in > >> >> > > >> >> > import servermanager > >> >> > > >> >> > File > >> >> > > >> >> > > >> >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > >> >> > line 3184, in > >> >> > > >> >> > __initialize() > >> >> > > >> >> > File > >> >> > > >> >> > > >> >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > >> >> > line 3175, in __initialize > >> >> > > >> >> > c = Connection(iter.GetCurrentSessionId(), > iter.GetCurrentSession()) > >> >> > > >> >> > File > >> >> > > >> >> > > >> >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > >> >> > line 1932, in __init__ > >> >> > > >> >> > _createModules(self.Modules) > >> >> > > >> >> > File > >> >> > > >> >> > > >> >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > >> >> > line 2564, in _createModules > >> >> > > >> >> > m.filters = createModule('filters') > >> >> > > >> >> > File > >> >> > > >> >> > > >> >> > > "/Users/mstroila/dev/build/ParaView/lib/site-packages/paraview/servermanager.py", > >> >> > line 2626, in createModule > >> >> > > >> >> > if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ > >> >> > > >> >> > AttributeError: 'NoneType' object has no attribute > >> >> > 'GetInformationOnly' > >> >> > > >> >> >>>> > >> >> > > >> >> > Thanks for any suggestion. > >> >> > > >> >> > > >> >> > Matei > >> >> > > >> >> > > >> >> > > >> >> > _______________________________________________ > >> >> > Powered by www.kitware.com > >> >> > > >> >> > Visit other Kitware open-source projects at > >> >> > http://www.kitware.com/opensource/opensource.html > >> >> > > >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> > http://paraview.org/Wiki/ParaView > >> >> > > >> >> > 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 26 17:27:26 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 26 Feb 2015 17:27:26 -0500 Subject: [Paraview] pvserver running out of memory In-Reply-To: References: <54EE1C01.3020303@nasa.gov> <54EE430B.6010101@nasa.gov> <54EE5B88.3090000@nasa.gov> <54EF538B.2000501@nasa.gov> Message-ID: I, alas, have no issues opening this file with [1]. I even loaded all the variables/meshes :/. It is possible that the SILO library used to build the pvserver is causing the issue. Can you try one morething? Download the ParaView 4.3.1 binaries from [1] and run pvserver (without MPI) on the target machine instead of your pvserver. Does that work? [1] http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=binary&os=linux64&downloadFile=ParaView-4.3.1-Linux-64bit-glibc-2.3.6.tar.gz On Thu, Feb 26, 2015 at 4:57 PM, Utkarsh Ayachit wrote: > Odd...can you share the data? I'll see if I can reproduce the issue. > > Utkarsh > > On Thu, Feb 26, 2015 at 12:10 PM, Jeff Becker wrote: >> On 02/26/2015 06:04 AM, Utkarsh Ayachit wrote: >>>> >>>> The threshold is zero. I was able to remote render the disk_out_ref.ex2 >>>> tutorial example just fine. Perhaps there's some issue with the SILO >>>> reader >>>> used in pvserver? Thanks. >>> >>> Possible, but you said it works fine when you load locally on the >>> client and not in client-server mode. But given that this is just a >>> single MPI rank for pvserver, I wonder what's different. Try not >>> using "--use-offscreen-rendering" argument. Does that make any >>> difference? >> >> >> Still runs out of memory. >> >> -jeff >>> >>> >>> Utkarsh >> >> From kevin.d.lau at gmail.com Thu Feb 26 17:41:59 2015 From: kevin.d.lau at gmail.com (Kevin Lau) Date: Thu, 26 Feb 2015 17:41:59 -0500 Subject: [Paraview] Hardware suggestions for volume rendering Message-ID: Hi, I'm looking to putting together a workstation to perform realtime volume rendering of our simulation data. Are there any particular GPU features I should look for? If there are multiple GPUs will Paraview be able to take advantage of each GPU for volume rendering? Many thanks Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Thu Feb 26 18:02:58 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Thu, 26 Feb 2015 15:02:58 -0800 Subject: [Paraview] pvserver running out of memory In-Reply-To: References: <54EE1C01.3020303@nasa.gov> <54EE430B.6010101@nasa.gov> <54EE5B88.3090000@nasa.gov> <54EF538B.2000501@nasa.gov> Message-ID: <54EFA622.8060405@nasa.gov> On 02/26/2015 02:27 PM, Utkarsh Ayachit wrote: > I, alas, have no issues opening this file with [1]. I even loaded all > the variables/meshes :/. It is possible that the SILO library used to > build the pvserver is causing the issue. Can you try one morething? > Download the ParaView 4.3.1 binaries from [1] and run pvserver > (without MPI) on the target machine instead of your pvserver. Does > that work? Yes it does! After selecting the file to open, my version runs out of memory before it gets to the dialog box for selecting the file type (since it doesn't know what kind of file I asked for- wrong extension), so it's probably not SILO, but something else. I'm happy to try rebuilding if you have suggestions. Thanks. -jeff > > [1] http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=binary&os=linux64&downloadFile=ParaView-4.3.1-Linux-64bit-glibc-2.3.6.tar.gz > > On Thu, Feb 26, 2015 at 4:57 PM, Utkarsh Ayachit > wrote: >> Odd...can you share the data? I'll see if I can reproduce the issue. >> >> Utkarsh >> >> On Thu, Feb 26, 2015 at 12:10 PM, Jeff Becker wrote: >>> On 02/26/2015 06:04 AM, Utkarsh Ayachit wrote: >>>>> The threshold is zero. I was able to remote render the disk_out_ref.ex2 >>>>> tutorial example just fine. Perhaps there's some issue with the SILO >>>>> reader >>>>> used in pvserver? Thanks. >>>> Possible, but you said it works fine when you load locally on the >>>> client and not in client-server mode. But given that this is just a >>>> single MPI rank for pvserver, I wonder what's different. Try not >>>> using "--use-offscreen-rendering" argument. Does that make any >>>> difference? >>> >>> Still runs out of memory. >>> >>> -jeff >>>> >>>> Utkarsh >>> From jeffrey.c.becker at nasa.gov Thu Feb 26 18:32:14 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Thu, 26 Feb 2015 15:32:14 -0800 Subject: [Paraview] pvserver running out of memory In-Reply-To: <54EFA622.8060405@nasa.gov> References: <54EE1C01.3020303@nasa.gov> <54EE430B.6010101@nasa.gov> <54EE5B88.3090000@nasa.gov> <54EF538B.2000501@nasa.gov> <54EFA622.8060405@nasa.gov> Message-ID: <54EFACFE.8020504@nasa.gov> On 02/26/2015 03:02 PM, Jeff Becker wrote: > On 02/26/2015 02:27 PM, Utkarsh Ayachit wrote: >> I, alas, have no issues opening this file with [1]. I even loaded all >> the variables/meshes :/. It is possible that the SILO library used to >> build the pvserver is causing the issue. Can you try one morething? >> Download the ParaView 4.3.1 binaries from [1] and run pvserver >> (without MPI) on the target machine instead of your pvserver. Does >> that work? > > Yes it does! After selecting the file to open, my version runs out of > memory before it gets to the dialog box for selecting the file type > (since it doesn't know what kind of file I asked for- wrong > extension), so it's probably not SILO, but something else. I'm happy > to try rebuilding if you have suggestions. Thanks. I may have found the problem. If I run your pvserver with SGI MPI, I get an error. However it runs fine with Intel MPI. I'll try rebuilding with Intel MPI. -jeff > > -jeff >> >> [1] >> http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=binary&os=linux64&downloadFile=ParaView-4.3.1-Linux-64bit-glibc-2.3.6.tar.gz >> >> On Thu, Feb 26, 2015 at 4:57 PM, Utkarsh Ayachit >> wrote: >>> Odd...can you share the data? I'll see if I can reproduce the issue. >>> >>> Utkarsh >>> >>> On Thu, Feb 26, 2015 at 12:10 PM, Jeff Becker >>> wrote: >>>> On 02/26/2015 06:04 AM, Utkarsh Ayachit wrote: >>>>>> The threshold is zero. I was able to remote render the >>>>>> disk_out_ref.ex2 >>>>>> tutorial example just fine. Perhaps there's some issue with the SILO >>>>>> reader >>>>>> used in pvserver? Thanks. >>>>> Possible, but you said it works fine when you load locally on the >>>>> client and not in client-server mode. But given that this is just a >>>>> single MPI rank for pvserver, I wonder what's different. Try not >>>>> using "--use-offscreen-rendering" argument. Does that make any >>>>> difference? >>>> >>>> Still runs out of memory. >>>> >>>> -jeff >>>>> >>>>> Utkarsh >>>> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From f.veronesi at scsitaly.com Fri Feb 27 03:21:35 2015 From: f.veronesi at scsitaly.com (Federico Veronesi) Date: Fri, 27 Feb 2015 09:21:35 +0100 Subject: [Paraview] Bug in redo camera/property link Message-ID: Dear all, I found this bug on redo camera link (but it occours anytime I try to redo a link) Add source to renderview split layout add source to renderview2 link camera between the two views UNDO the link REDO the link CRASH (on PV 4.2 debug) , view destroyed on PV 4.3.1 (release) I reported it on Mantis : http://www.paraview.org/Bug/view.php?id=15347 I found out that the problem rises because in vtkSMSessionProxyManager when trying to load the state of the link the corresponding classname is not stored in the message. If somebody can point me out where to look I'll be happy to help with the fix. Regards -------------------------------- Federico Veronesi, PhD SCS s.r.l. - Via Parini 1, Casalecchio di Reno (BO) Italy CINECA - Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy Phone: +39 051 6171624 E-mail: f.veronesi at scsitaly.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Fri Feb 27 05:07:04 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Fri, 27 Feb 2015 10:07:04 +0000 Subject: [Paraview] read data in nc file and colocate as text in each frame In-Reply-To: References: , Message-ID: I have a scrip that read a nc file and plot the sediments cloud from a clarifier . The script already save each image from each instant of my nc file. Now i want to include in each slide the data. So, i want that the scrip associate and write the correc data as text in each slide. How can include these feature in my script? Can you help me? Kind regards Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Fri Feb 27 05:31:01 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Fri, 27 Feb 2015 10:31:01 +0000 Subject: [Paraview] Animate a solid with a specific time serie In-Reply-To: References: , , , Message-ID: Deal all,I want to animate a solid that moves acording to specific time serie (time, position). By recording the code via python shell i see that appears two simple keywords that moves the solid by proving specific values. example: # get animation trackbox1CenterTrack = GetAnimationTrack('Center', index=0, proxy=box1) # create keyframes for animation trackkeyFrame0 = CompositeKeyFrame()keyFrame0.KeyTime = 0.0keyFrame0.KeyValues = 60.0 keyFrame1 = CompositeKeyFrame()keyFrame1.KeyTime = 1.0keyFrame1.KeyValues = 0.0 # initialize the animation trackbox1CenterTrack.KeyFrames = [keyFrame0, keyFrame1] My doubt is the place where is possible to provide my time serie of time and position. And what is the time units of KeyTime? The KeyValues is position if i understand the sample that i run. Instead a specific time serie it is possible to provide each line of time serie as KeyTime and Kay Value, and then for the animation track call them all. Example:time (minuts) position (m)1 7.2 Converted in script: keyFrame1.KeyTime = 1.0; keyFrame1.KeyValues = 7.2 2 9.374 Converted in script: keyFrame2.KeyTime = 2.0; keyFrame2.KeyValues = 9.374 3 11.548 Converted in script: keyFrame1.KeyTime = 3.0; keyFrame1.KeyValues = 11.548 box1CenterTrack.KeyFrames = [keyFrame0, keyFrame1, KeyFrame 3 etc..] Is possible to do sometinh like that? Convert my time serie of time and position to each keytime and keyvalues in script? Kind regardsMadalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From louie.cardone-noott at linacre.ox.ac.uk Fri Feb 27 06:32:58 2015 From: louie.cardone-noott at linacre.ox.ac.uk (Louie Cardone-Noott) Date: Fri, 27 Feb 2015 11:32:58 +0000 Subject: [Paraview] VTK parallel unstructured grid and halo elements In-Reply-To: <7d78668e-79eb-4364-8e2d-08fb061dfb1f@HUB04.ad.oak.ox.ac.uk> References: <1a180a02-4f10-4dff-91fe-a7a9ce1918ed@HUB06.ad.oak.ox.ac.uk> <7d78668e-79eb-4364-8e2d-08fb061dfb1f@HUB04.ad.oak.ox.ac.uk> Message-ID: Hi Berk, Thanks for your reply. Yes that does sound like what I need to do. Shouldn't the nodes of elements with vtkGhostLevels>0 already be ignored in the range calculation though? Is there no way to do this currently then? I tried marking them with vtkGhostPoints but it didn't help last time I tried. Cheers, Louie On 25 February 2015 at 18:31, Berk Geveci wrote: > Hi Louie, > > Ghost/halo nodes are considered valid (but duplicated) so they are taken > into account when calculating ranges, statistics etc. What you need is to > mark them as invalid, it sounds like? We are making slow progress towards > having an infrastructure that supports this but currently it is only > partially support for structured grids and AMR meshes and a subset of > filters. > > Best, > -berk > > On Wed, Feb 25, 2015 at 11:06 AM, Louie Cardone-Noott < > louie.cardone-noott at linacre.ox.ac.uk> wrote: > >> Hi again list, >> >> Inspired by David Ortley's recent success (see "Smooth seams in SILO >> files") I wonder if perhaps the way I'm doing it is correct, but Paraview >> is incorrectly considering the values at hidden nodes when calculating data >> ranges. >> >> Essentially my "option 3" (writing a vtkGhostLevels array) appears to >> work as it should, and the "seams" are hidden in my parallel data. But, if >> I then Extract Surface and look at the Data Arrays -> Data Ranges I see >> values which can only be from non-surface nodes. I suspect they are >> probably from nodes on the (hidden) interior surfaces. This is obviously a >> bug. >> >> I could probably provide a minimal example if useful. >> >> Best wishes, >> Louie >> >> >> On 17 January 2015 at 16:26, Louie Cardone-Noott < >> louie.cardone-noott at linacre.ox.ac.uk> wrote: >> >>> Hi Paraview list, >>> >>> I use a finite element code that generates VTK output, but I'm having >>> trouble dealing with halo (ghost) nodes/elements correctly. >>> >>> We currently partition meshes node-wise, and each process writes all its >>> owned nodes and one level of halo nodes to a chunk. Once all the chunks are >>> loaded there is a "double layer" of internal boundaries between processes. >>> I'd really like to be able to use the Extract Surface filter correctly but >>> as you would expect it also finds all the internal surfaces. From searching >>> I've tried: >>> >>> * Clean To Grid, but this removes both sides of the double layer leaving >>> unsightly gaps. >>> * Writing a vtkGhostPoints array (on nodes) but this seems not to be >>> used by this filter (or Paraview at all?) >>> * Writing a vtkGhostLevels array (on elements). This correctly hides all >>> the ghost elements at the internal boundaries (great!) but still doesn't >>> let me do everything I want to. For example, the extracted surface looks >>> right, but the array limits still seem to be based on the max/min of the >>> external AND internal surfaces, so I suspect the internal ones are just >>> "hidden from view". >>> >>> What's the right way to deal with this? >>> >>> Thanks in advance. >>> >>> Louie >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Feb 27 07:41:56 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 27 Feb 2015 07:41:56 -0500 Subject: [Paraview] [Paraview-developers] How to force an update of the time information? In-Reply-To: <593AFCE559F11049B8F268BE84170A0DC13151@EXCHMBX03.fed.cclrc.ac.uk> References: <593AFCE559F11049B8F268BE84170A0DC13151@EXCHMBX03.fed.cclrc.ac.uk> Message-ID: ParaVIew has a global "time" and it will request the same time from all sources in the application when updating. When you create the first source, ParaView internal clock realizes that there are a set of timesteps available, say A and will change the global time to the first timestep in A and also update the animation to iterate through timesteps in A sequentially. When you add another source with another set of timesteps, say B, ParaView updates the internal clock to be a union of timesteps provided by all the sources by both the sources thus (A U B). The current clock time isn't updated since it's in this set of timesteps available. If you're only interested in the second source, try removing the first source before adding the second, rather than the other way. If you want to simply set a specific timestep, get access to the animation scene and then directly change its animation time. Utkarsh On Wed, Feb 25, 2015 at 11:17 AM, wrote: > Hi, > > I am currently working on a customization of ParaView (PV 3.98.1) which uses its animation capabilities. Hence I need to set TIME_STEPS in the requestInformation method of my source plugin. It works quite nicely in fact. > > An issue occurs, when I create a second instance of the same type of source. The second source has different time information compared to the original source. I would like to use this second time information. But it seems that the time information is not updated when the requestInformation method is called for the new source. In the requestData method I retrieve the time information via > > time =outInfo->Get(vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()); > > This returns the old time information. How can I enforce an update in ParaView? I believe something similar was discussed in: http://public.kitware.com/pipermail/paraview/2010-November/019492.html. But unfortunately the answer seems to be cut off. > > Any ideas or help is very much appreciated. > > Many thanks and best regards, > > Anton > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers From aashish.chaudhary at kitware.com Fri Feb 27 08:15:36 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Fri, 27 Feb 2015 08:15:36 -0500 Subject: [Paraview] Hardware suggestions for volume rendering In-Reply-To: References: Message-ID: Dear Kevin, First, I would like to mention that we have been working hard to improve rendering in VTK that includes volume rendering as well. You may want to read this source article: http://www.kitware.com/source/home/post/154. Most of the changes related to this work is now available in VTK github repository in master branch. If you are targetting current VTK, I would suggest that any card that can support OpenGL2.1 or higher would be great. The higher the GPU memory the better. While these newer card will work with the previous version of volume rendering, it may not scale very well (in our testing that's what we have observed). Current the default in ParaView is OpenGL Volume Rendering but that is going to change sometime soon and once that happens you will have OpenGL2 backend for everything. Hope this helps. - Aashish On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau wrote: > Hi, > > I'm looking to putting together a workstation to perform realtime volume > rendering of our simulation data. > > Are there any particular GPU features I should look for? > > If there are multiple GPUs will Paraview be able to take advantage of each > GPU for volume rendering? > > Many thanks > > Kevin > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nenasantos at hotmail.com Fri Feb 27 08:50:03 2015 From: nenasantos at hotmail.com (Madalena S. Malhadas) Date: Fri, 27 Feb 2015 13:50:03 +0000 Subject: [Paraview] Annotate time filter - regard real time In-Reply-To: References: , Message-ID: Dear paraview users,I have a question over the use of Annotate time filter in Paraview. I have a paraview script that read netcdf data which has time axis given as "days since 1970-01-0100:00" (Epoch Time). This gives problem if I want to show the real time of the data in the animation window. What I would like to have shown are the date as4-8-2003, 00:00 etc. and it shows big number like 19521, 19522. Does anyone have some idea how to solve the problem?Thanks a lot! Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From oshima at eng.niigata-u.ac.jp Fri Feb 27 08:45:46 2015 From: oshima at eng.niigata-u.ac.jp (Takuya OSHIMA) Date: Fri, 27 Feb 2015 22:45:46 +0900 (JST) Subject: [Paraview] Problem loading a .pvd file in parallel into PV 4.3.1 Message-ID: <20150227.224546.76329235.oshima@eng.niigata-u.ac.jp> Hi, I have a problem trying to load a .pvd file (containing a link to a time-series of .pvtp datasets) into a parallel configuration of PV 4.3.1. The steps to reproduce my problem are: Start multiple (say 4) pvservers in parallel Start the ParaView GUI, connect to the server Source - Sphere, Apply File - Save Data... Choose ParaView Data Files(*.pvd) as Files of type Name the file as sphere.pvd, OK, OK Delete Sphere1 File - Open... Choose sphere.pvd, OK, Apply With the above steps a sphere source is created, saved, loaded back and what I see should be a whole sphere. However, I only see a fragment of the sphere which has been saved as piece 0 of sphere.pvd (sphere/sphere_0_0.vtp). Moreover, when I load the underlying .pvtp file (sphere/sphere_0.pvtp), I can see the whole sphere as expected. I have the same problem with PV 4.2 as well, but not with 4.1. My problem looks similar to http://markmail.org/message/33hr6k45fgfd4w63 which reports a problem with .pvti files, but I am not sure if it is identical. Is this a bug or am I missing something? Thanks, Takuya OSHIMA, Ph.D. Faculty of Engineering, Niigata University 8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN From kmorel at sandia.gov Fri Feb 27 10:43:15 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 27 Feb 2015 15:43:15 +0000 Subject: [Paraview] Animate a solid with a specific time serie Message-ID: Madalena, The time units in ParaView can be anything you want them to be: minutes, seconds, epochs, jiffies, whatever. ParaView does not manage the units for time; it is an exercise for the user to ensure that all time values refer to the same scale (and bias). You can control the time range (the time values where the animation starts and stops) through the animation scene object returned from GetAnimationScene(). The StartTime and EndTime fields can be set to the start and end times you want your animation to be. The following code sets the animation range to be compatible with the keyframe times you describe below. # get animation scene animationScene1 = GetAnimationScene() # Properties modified on animationScene1 animationScene1.StartTime = 1.0 animationScene1.EndTime = 3.0 If you want to control the playback of the animation in terms of frames or speed, you can do so with the PlayMode and other parameters. For example, in the email below you mentioned the time value in terms of minutes. If you wanted you keyframes to play over the course of 2 minutes (the time between T = 1min and T = 3min is 2 minutes), you can set the PlayMode to 'Real Time' and set the Duration field to 120. (The duration is measured in seconds, so 2 minutes converts to 120 seconds.) You can do that as follows: animationScene1.PlayMode = 'Real Time' animationScene1.Duration = 120 Alternately, you can request a certain number of frames in the animation. You cannot specify arbitrary time values for every frame, ParaView evenly spaces them between the start and end time. But if your keyframes are evenly spaced it is easy to align them. So if you want a frame at every keyframe in the example below, you can use the following code. animationScene1.PlayMode = 'Sequence' animationScene1.NumberOfFrames = 3 In the GUI, all of these controls are in the Animation View widget. You can learn more about the animation view in the ParaView tutorial (http://www.paraview.org/Wiki/The_ParaView_Tutorial), specifically in Exercise 2.18. These tools are also documented in the ParaView User's Guide (http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=data&os=all&downloadFile=TheParaViewGuide-v4.3-CC-Edition.pdf), specifically in Section 7.2. Once you know how to set these controls in the GUI, you can use ParaView script trace to learn the appropriate Python commands. -Ken From: "Madalena S. Malhadas" > Date: Friday, February 27, 2015 at 3:31 AM To: Kenneth Moreland >, Jeff Becker >, Utkarsh Ayachit > Cc: ParaView > Subject: [EXTERNAL] Animate a solid with a specific time serie Deal all, I want to animate a solid that moves acording to specific time serie (time, position). By recording the code via python shell i see that appears two simple keywords that moves the solid by proving specific values. example: # get animation track box1CenterTrack = GetAnimationTrack('Center', index=0, proxy=box1) # create keyframes for animation track keyFrame0 = CompositeKeyFrame() keyFrame0.KeyTime = 0.0 keyFrame0.KeyValues = 60.0 keyFrame1 = CompositeKeyFrame() keyFrame1.KeyTime = 1.0 keyFrame1.KeyValues = 0.0 # initialize the animation track box1CenterTrack.KeyFrames = [keyFrame0, keyFrame1] My doubt is the place where is possible to provide my time serie of time and position. And what is the time units of KeyTime? The KeyValues is position if i understand the sample that i run. Instead a specific time serie it is possible to provide each line of time serie as KeyTime and Kay Value, and then for the animation track call them all. Example: time (minuts) position (m) 1 7.2 Converted in script: keyFrame1.KeyTime = 1.0; keyFrame1.KeyValues = 7.2 2 9.374 Converted in script: keyFrame2.KeyTime = 2.0; keyFrame2.KeyValues = 9.374 3 11.548 Converted in script: keyFrame1.KeyTime = 3.0; keyFrame1.KeyValues = 11.548 box1CenterTrack.KeyFrames = [keyFrame0, keyFrame1, KeyFrame 3 etc..] Is possible to do sometinh like that? Convert my time serie of time and position to each keytime and keyvalues in script? Kind regards Madalena -------------- next part -------------- An HTML attachment was scrubbed... URL: From anton.piccardo-selg at stfc.ac.uk Fri Feb 27 12:05:09 2015 From: anton.piccardo-selg at stfc.ac.uk (anton.piccardo-selg at stfc.ac.uk) Date: Fri, 27 Feb 2015 17:05:09 +0000 Subject: [Paraview] [Paraview-developers] How to force an update of the time information? In-Reply-To: References: <593AFCE559F11049B8F268BE84170A0DC13151@EXCHMBX03.fed.cclrc.ac.uk>, Message-ID: <593AFCE559F11049B8F268BE84170A0DC1A1F3@EXCHMBX03.fed.cclrc.ac.uk> Hi Utkarsh, Thanks a lot for that explanation. Knowing that the time steps are a union of both sources helped me to resolve our issue. Many thanks and best regards, Anton ________________________________________ From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] Sent: 27 February 2015 12:41 To: Piccardo-Selg, Anton (-,RAL,ISIS) Cc: ParaView Developers; paraview at paraview.org Subject: Re: [Paraview-developers] How to force an update of the time information? ParaVIew has a global "time" and it will request the same time from all sources in the application when updating. When you create the first source, ParaView internal clock realizes that there are a set of timesteps available, say A and will change the global time to the first timestep in A and also update the animation to iterate through timesteps in A sequentially. When you add another source with another set of timesteps, say B, ParaView updates the internal clock to be a union of timesteps provided by all the sources by both the sources thus (A U B). The current clock time isn't updated since it's in this set of timesteps available. If you're only interested in the second source, try removing the first source before adding the second, rather than the other way. If you want to simply set a specific timestep, get access to the animation scene and then directly change its animation time. Utkarsh On Wed, Feb 25, 2015 at 11:17 AM, wrote: > Hi, > > I am currently working on a customization of ParaView (PV 3.98.1) which uses its animation capabilities. Hence I need to set TIME_STEPS in the requestInformation method of my source plugin. It works quite nicely in fact. > > An issue occurs, when I create a second instance of the same type of source. The second source has different time information compared to the original source. I would like to use this second time information. But it seems that the time information is not updated when the requestInformation method is called for the new source. In the requestData method I retrieve the time information via > > time =outInfo->Get(vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()); > > This returns the old time information. How can I enforce an update in ParaView? I believe something similar was discussed in: http://public.kitware.com/pipermail/paraview/2010-November/019492.html. But unfortunately the answer seems to be cut off. > > Any ideas or help is very much appreciated. > > Many thanks and best regards, > > Anton > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers From chrisneal at ufl.edu Fri Feb 27 14:51:53 2015 From: chrisneal at ufl.edu (Neal,Christopher R) Date: Fri, 27 Feb 2015 19:51:53 +0000 Subject: [Paraview] Numerical Schlieren In Paraview Message-ID: Hi, I would like to compute a numerical schlieren field from a density field in Paraview. The schlieren variable would just be the magnitude of the density gradient computed at each cell center in the data set. I have been able to compute a basic schlieren dataset by using the Paraview filter "Gradient of Unstructured DataSet". However I would like to do something like the following. 1.) Compute density gradients. 2.) Compute the magnitude of the gradients. 3.) Normalize the gradient magnitudes by the maximum value in the domain( so that the new variable goes from 0 to 1 ) 4.) Store this new data as a new variable called 'Schlieren' 5.) Take the new schlieren variable and perform a second point-by-point operation on the data. NewSchlieren = exp( -k*oldSchlieren) where k is a constant that I set. This 5th operation just serves to sharpen the lines that are present in the oldSchlieren data set. I'm thinking that I need to write some sort of programmable filter. I'm just not sure how I would actually perform point-by-point operations on the data sets. Any guidance on how to read/operate on variables in the data set would be greatly appreciated. Thanks, Christopher R. Neal Graduate Student Center for Compressible Multiphase Turbulence Mechanical and Aerospace Engineering Department University of Florida Cell: (863)-697-1958 E-mail: chrisneal at ufl.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisneal at ufl.edu Fri Feb 27 14:53:27 2015 From: chrisneal at ufl.edu (Neal,Christopher R) Date: Fri, 27 Feb 2015 19:53:27 +0000 Subject: [Paraview] Smoothing color map of data set Message-ID: <1425066806864.77826@ufl.edu> Hello, I have data on an unstructured tetrahedral grid. It is numerical schlieren data i.e. it is a scalar field of the magnitude of the density gradients at each cell center. When I open the dataset in Paraview and view the schlieren data set I see a jagged color map. I've attached an image that shows the jagged shape. I have used Tecplot before on this data set and it had the capability to have a continuous flooding color map that smooths out the colors on the color map. It makes the colors seems a little fuzzy, but it looks good. Does Paraview have this capability? Thank you, Christopher R. Neal Graduate Student Center for Compressible Multiphase Turbulence Mechanical and Aerospace Engineering Department University of Florida Cell: (863)-697-1958 E-mail: chrisneal at ufl.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image1.png Type: image/png Size: 195360 bytes Desc: image1.png URL: From dave.demarle at kitware.com Fri Feb 27 14:57:26 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 27 Feb 2015 14:57:26 -0500 Subject: [Paraview] Smoothing color map of data set In-Reply-To: <1425066806864.77826@ufl.edu> References: <1425066806864.77826@ufl.edu> Message-ID: Try the cell to point filter and then choose the point aligned array to color by. C2P will average neighboring cell values onto the vertices. Then rendering can linearly interpolate across the surface of each cell. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Feb 27, 2015 at 2:53 PM, Neal,Christopher R wrote: > Hello, > > > I have data on an unstructured tetrahedral grid. It is numerical > schlieren data i.e. it is a scalar field of the magnitude of the density > gradients at each cell center. When I open the dataset in Paraview and > view the schlieren data set I see a jagged color map. I've attached an > image that shows the jagged shape. I have used Tecplot before on this data > set and it had the capability to have a continuous flooding color map that > smooths out the colors on the color map. It makes the colors seems a little > fuzzy, but it looks good. Does Paraview have this capability? > > Thank you, > > > > Christopher R. Neal > Graduate Student > Center for Compressible Multiphase Turbulence > Mechanical and Aerospace Engineering Department > University of Florida > Cell: (863)-697-1958 > E-mail: chrisneal at ufl.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 burlen.loring at gmail.com Fri Feb 27 17:06:18 2015 From: burlen.loring at gmail.com (Burlen Loring) Date: Fri, 27 Feb 2015 14:06:18 -0800 Subject: [Paraview] wiki issue Message-ID: <54F0EA5A.7090106@gmail.com> Hi All, I just noticed that math ml equations are no longer type set on the wiki. instead tags and contents are displayed ... . was this an accidental change? Burlen From dave.demarle at kitware.com Fri Feb 27 17:16:45 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 27 Feb 2015 17:16:45 -0500 Subject: [Paraview] wiki issue In-Reply-To: <54F0EA5A.7090106@gmail.com> References: <54F0EA5A.7090106@gmail.com> Message-ID: Looking?. can you point me at a specific page Burlen? ty On Fri, Feb 27, 2015 at 5:06 PM, Burlen Loring wrote: > Hi All, > > I just noticed that math ml equations are no longer type set on the wiki. > instead tags and contents are displayed ... . was this an > accidental change? > > Burlen > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 bloring at lbl.gov Fri Feb 27 17:50:28 2015 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 27 Feb 2015 14:50:28 -0800 Subject: [Paraview] wiki issue In-Reply-To: References: <54F0EA5A.7090106@gmail.com> Message-ID: <54F0F4B4.7050203@lbl.gov> http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution On 02/27/2015 02:16 PM, David E DeMarle wrote: > Looking?. can you point me at a specific page Burlen? > > ty > > On Fri, Feb 27, 2015 at 5:06 PM, Burlen Loring > > wrote: > > Hi All, > > I just noticed that math ml equations are no longer type set on > the wiki. instead tags and contents are displayed ... > . was this an accidental change? > > Burlen > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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 dave.demarle at kitware.com Fri Feb 27 18:31:26 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 27 Feb 2015 18:31:26 -0500 Subject: [Paraview] wiki issue In-Reply-To: <54F0F4B4.7050203@lbl.gov> References: <54F0EA5A.7090106@gmail.com> <54F0F4B4.7050203@lbl.gov> Message-ID: Should be all set now. Thanks to Jake, who found that newer mediawiki needs an extension to format math text. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Feb 27, 2015 at 5:50 PM, Burlen Loring wrote: > http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution > > > On 02/27/2015 02:16 PM, David E DeMarle wrote: > > Looking?. can you point me at a specific page Burlen? > > ty > > On Fri, Feb 27, 2015 at 5:06 PM, Burlen Loring > wrote: > >> Hi All, >> >> I just noticed that math ml equations are no longer type set on the wiki. >> instead tags and contents are displayed ... . was this an >> accidental change? >> >> Burlen >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> 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 benjamin.lee.hinchliffe at gmail.com Sat Feb 28 04:54:24 2015 From: benjamin.lee.hinchliffe at gmail.com (Ben Hinchliffe) Date: Sat, 28 Feb 2015 09:54:24 +0000 Subject: [Paraview] Crash when loading plt file Message-ID: When I load a 'large' plt file paraview gives me a segmentation fault. I can load smaller cases with no problem. The file size is around 1Gb. I'm not sure what else to do as there is no more information on the crash. Thanks in advance From andy.bauer at kitware.com Sat Feb 28 15:49:40 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Sat, 28 Feb 2015 15:49:40 -0500 Subject: [Paraview] Numerical Schlieren In Paraview In-Reply-To: References: Message-ID: I tried this out with the Wavelet source and it's RTData as the input. You can see what I did by loading the attached state file shlieren.pvsm). I inlined information below on the steps. Note that you can use the Point Data to Cell Data Filter to change to cell data output. Let me know how it goes. If you could share a result, I'd like to see how it comes out! On Fri, Feb 27, 2015 at 2:51 PM, Neal,Christopher R wrote: > Hi, > > > I would like to compute a numerical schlieren field from a density field > in Paraview. The schlieren variable would just be the magnitude of the > density gradient computed at each cell center in the data set. I have been > able to compute a basic schlieren dataset by using the Paraview filter > "Gradient of Unstructured DataSet". However I would like to do something > like the following. > > > 1.) Compute density gradients. > > 2.) Compute the magnitude of the gradients. > I used the Python calculator with the expression "mag(Gradients)" here. The output array was called gradientmagnitude. > 3.) Normalize the gradient magnitudes by the maximum value in the domain( > so that the new variable goes from 0 to 1 ) > I created another Python Calculator with the expression "gradientmagnitude/max(gradientmagnitude)" and called the output array oldSchlieren. > 4.) Store this new data as a new variable called 'Schlieren' > > 5.) Take the new schlieren variable and perform a second point-by-point > operation on the data. > > NewSchlieren = exp( -k*oldSchlieren) > I used the Calculator filter with the input of "exp(-.5*oldSchlieren)" and named the output newSchlieren. I just used a value of k of 0.5. > > where k is a constant that I set. This 5th operation just serves to > sharpen the lines that are present in the oldSchlieren data set. > > > I'm thinking that I need to write some sort of programmable filter. I'm > just not sure how I would actually perform point-by-point operations on the > data sets. > > > Any guidance on how to read/operate on variables in the data set would > be greatly appreciated. > > > Thanks, > > > > > Christopher R. Neal > Graduate Student > Center for Compressible Multiphase Turbulence > Mechanical and Aerospace Engineering Department > University of Florida > Cell: (863)-697-1958 > E-mail: chrisneal at ufl.edu > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: schlieren.pvsm Type: application/octet-stream Size: 202748 bytes Desc: not available URL: