From utkarsh.ayachit at kitware.com Tue Nov 4 10:48:28 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 4 Nov 2014 10:48:28 -0500 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: Topics merged into master: (VTK) update-vtk-20141030 15032_fix_settings_dialog ? ? 15076_fix_opacity_mapping_reset ? ? ? 15078_fix_point_sprite ? ? ? 15090_fix_state_loading_issues ? ? ? 15093_fix_stereo_issues ? ? ? fix-xml-crash-on-close ? ? ? python_syntax_highlighting_bugs From biddisco at cscs.ch Tue Nov 4 14:54:14 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Tue, 4 Nov 2014 19:54:14 +0000 Subject: [Paraview-developers] Multiple lookup tables Message-ID: I?m Rendering particles from astrophysics simulations and would like to have a single mapper with access to two lookup tables (ideally up to 4 or 5), one for gas particles, one for dark matter, then potentially more for other particle types. Currently the lookuptable manager manages tables based on the name of the field array ? is there a precedent for having multiple lookuptables used anywhere in a single representation? I could probably query the lookuptable manager and get handles of luts and set them manually on my representation, but I?d quite like to have the ability to edit the ranges and colours by hand in my panel (by providing a LUT button for each particle type and popping up the editor for each one) If there anything in the code anywhere which does something like this already that I can have a play with ? alternatively, any advice on what to do to save myself some time with experimentation? Many thanks JB -------------- next part -------------- An HTML attachment was scrubbed... URL: From ndfabia at sandia.gov Tue Nov 4 16:03:28 2014 From: ndfabia at sandia.gov (Fabian, Nathan) Date: Tue, 4 Nov 2014 21:03:28 +0000 Subject: [Paraview-developers] Tracking down this error message in my new filter Message-ID: I'm creating a filter which works with datasets and the input data is multiblock unstructured grid. I can't make heads or tails of this error message: ERROR: In /Users/ndfabia/paraview/ParaView/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 810 vtkPVPostFilterExecutive (0x127d520c0): Input for connection index 0 on input port index 0 for algorithm vtkPVPostFilter(0x127d5ef70) is of type vtkDataObject, but a vtkPolyData is required Any help would be appreciated. Thanks, Nathan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Nov 4 16:19:00 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 4 Nov 2014 16:19:00 -0500 Subject: [Paraview-developers] Tracking down this error message in my new filter In-Reply-To: References: Message-ID: Maybe your filter needs to override RequestDataObject() to provide a proper output dataobject? On Tue, Nov 4, 2014 at 4:03 PM, Fabian, Nathan wrote: > I?m creating a filter which works with datasets and the input data is > multiblock unstructured grid. > > I can?t make heads or tails of this error message: > > > ERROR: In > /Users/ndfabia/paraview/ParaView/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 810 > > vtkPVPostFilterExecutive (0x127d520c0): Input for connection index 0 on > input port index 0 for algorithm vtkPVPostFilter(0x127d5ef70) is of type > vtkDataObject, but a vtkPolyData is required > > > Any help would be appreciated. > > > Thanks, > > Nathan. > > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > From ndfabia at sandia.gov Tue Nov 4 16:27:14 2014 From: ndfabia at sandia.gov (Fabian, Nathan) Date: Tue, 4 Nov 2014 21:27:14 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Tracking down this error message in my new filter In-Reply-To: References: Message-ID: Yes indeed. It would be right after I write that I realize I made it a vtkDataObjectAlgorithm not a vtkDataSetAlgorithm. Thanks, On 11/4/14, 2:19 PM, "Utkarsh Ayachit" wrote: >Maybe your filter needs to override RequestDataObject() to provide a >proper output dataobject? > >On Tue, Nov 4, 2014 at 4:03 PM, Fabian, Nathan wrote: >> I?m creating a filter which works with datasets and the input data is >> multiblock unstructured grid. >> >> I can?t make heads or tails of this error message: >> >> >> ERROR: In >> >>/Users/ndfabia/paraview/ParaView/VTK/Common/ExecutionModel/vtkDemandDrive >>nPipeline.cxx, >> line 810 >> >> vtkPVPostFilterExecutive (0x127d520c0): Input for connection index 0 on >> input port index 0 for algorithm vtkPVPostFilter(0x127d5ef70) is of type >> vtkDataObject, but a vtkPolyData is required >> >> >> Any help would be appreciated. >> >> >> Thanks, >> >> Nathan. >> >> >> _______________________________________________ >> Paraview-developers mailing list >> Paraview-developers at paraview.org >> http://public.kitware.com/mailman/listinfo/paraview-developers >> From utkarsh.ayachit at kitware.com Tue Nov 4 16:37:40 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 4 Nov 2014 16:37:40 -0500 Subject: [Paraview-developers] Multiple lookup tables In-Reply-To: References: Message-ID: John, Nothing does this currently, but I suspect should be doable. You're correct, go down the path of using the lookuptable manager to get separate LUts and setting those up using custom property widgets, where needed. Feel free to holler if you have specific questions. Utkarsh On Tue, Nov 4, 2014 at 2:54 PM, Biddiscombe, John A. wrote: > I?m Rendering particles from astrophysics simulations and would like to have > a single mapper with access to two lookup tables (ideally up to 4 or 5), one > for gas particles, one for dark matter, then potentially more for other > particle types. > > Currently the lookuptable manager manages tables based on the name of the > field array ? is there a precedent for having multiple lookuptables used > anywhere in a single representation? I could probably query the lookuptable > manager and get handles of luts and set them manually on my representation, > but I?d quite like to have the ability to edit the ranges and colours by > hand in my panel (by providing a LUT button for each particle type and > popping up the editor for each one) > > If there anything in the code anywhere which does something like this > already that I can have a play with ? alternatively, any advice on what to > do to save myself some time with experimentation? > > Many thanks > > JB > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Wed Nov 5 08:12:29 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 5 Nov 2014 08:12:29 -0500 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: SUMMARY --------------------------------------------- Topics merged into master: 0015060_fix_temporalshift_issue 15059_fix_time_comments 15100_fix_color_map_editor_size python_syntax_highlighting_bugs test_max (VTK) vtk_master_20141104 From utkarsh.ayachit at kitware.com Thu Nov 6 08:18:54 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 6 Nov 2014 08:18:54 -0500 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: SUMMARY --------------------------------------------- Topics merged into master: 14845_reset_color_map 15053_fix_coloring_with_missing_arrays 15085_fix_install_rules_for_catalyst 15107_catalyst_rendering_edition opengl2-backend (VTK) vtk_master_20141105 From marcus.hanwell at kitware.com Thu Nov 6 09:08:38 2014 From: marcus.hanwell at kitware.com (Marcus D. Hanwell) Date: Thu, 6 Nov 2014 09:08:38 -0500 Subject: [Paraview-developers] OpenGL2 backend and ParaView Message-ID: Hi, There was some interest in this on the list, and so I would like to point out a topic was merged to master this morning adding limited support for using the OpenGL2 backend. I would like to stress that it is far from ready for production use, several features are disabled, and it needs more work to be able to replace the existing backend. I have tested it by turning off all plugins, testing, and if you want Python support you need to disable ParaViewWeb. So far I have only had chance to try building it on Linux and Mac. You can select OpenGL2 from the list of VTK_RENDERING_BACKENDS and then keep your fingers crossed. I will write a fuller post some time soon, the polygonal rendering has some big speed ups. There are warnings being output from the rendering code, and they should be cleaned up soon. It would be great to get feedback from the brave few who want to try it out. Thanks, Marcus From Orlando.RIVERA at mtu.de Mon Nov 10 03:55:10 2014 From: Orlando.RIVERA at mtu.de (RIVERA, Orlando) Date: Mon, 10 Nov 2014 08:55:10 +0000 Subject: [Paraview-developers] Paraview save state wrong implemetation for GUI Message-ID: Hello I need again your help I been working on a Plugin base on vtkMultiBlockDataSetAlgorithm. It does pretty much what I do , but I am missing something ! When I read my data and select the blocks, it works fine , When I save the state (File->SaveState) the corresponding *.psvm is written and when I tried to load the state, from the previous generated file , the Data is loaded as expected. My problem is in the GUI . I have a GUI with a QTreeWidget, and the state of the previous state is not loaded (the leaves in the tree are not checked), I assume I have to tell the GUI what was its previous state . I also assume that the best place to do it is a the end of RequestData (server) : i.e Server tells GUI which of its elements have to be checked,marked ,displayed ,etc . - How the GUI can read the state on a pvsm? - Which function is responsible for recovering the state on the GUI/client side? - How can I drive events on the GUI from Server ? ( Influence the CLIENT from the server , is that possible) Any Help would be greatly appreciated Cheers !! Orlando -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schrey?gg, Dr. Stefan Weingartner Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. From f.veronesi at scsitaly.com Mon Nov 10 08:46:30 2014 From: f.veronesi at scsitaly.com (Federico Veronesi) Date: Mon, 10 Nov 2014 14:46:30 +0100 Subject: [Paraview-developers] Problem with all in one/separated panels Message-ID: Dear Paraview-developers, I found an unexpected behavior in Paraview 4.2. When I set separated panel or other options except the combined one, I don't get what it is expected and 6 grayed button (restore, update) appears. I think I fixed it by adding the following lines to pqPropertiesPanel.cxx in the setPanelMode method: // added to avoid unwanted update restore buttons this->Internals->Ui.PropertiesSaveAsDefaults->setVisible(has_source); this->Internals->Ui.PropertiesRestoreDefaults->setVisible(has_source); this->Internals->Ui.DisplaySaveAsDefaults->setVisible(has_display); this->Internals->Ui.DisplayRestoreDefaults->setVisible(has_display); this->Internals->Ui.ViewSaveAsDefaults->setVisible(has_view); this->Internals->Ui.ViewRestoreDefaults->setVisible(has_view); Moreover I modified the paraview main window to setup the panels. i.e. for ALL_SEPARATE: case vtkPVGeneralSettings::ALL_SEPARATE: this->Internals->propertiesPanel->setPanelMode( pqPropertiesPanel::SOURCE_PROPERTIES); // added this->Internals->viewPropertiesPanel->setPanelMode( pqPropertiesPanel::VIEW_PROPERTIES); this->Internals->displayPropertiesPanel->setPanelMode(pqPropertiesPanel::DISPLAY_PROPERTIES); It works at start up, but when I use more than one source the display panel doesn't show any property when switching from one source to another. Do you know what can cause this behavior and how to possibly solve it? Thank you Federico -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Mon Nov 10 16:22:32 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 10 Nov 2014 16:22:32 -0500 Subject: [Paraview-developers] See what our closest collaborators have been cooking up for IEEE SC 2014 Message-ID: Greetings again lists, If you are planning out what to see and do at this year's Supercomputing conference, please don't forget about the presentations we've got lined up at the Kitware booth. http://www.kitware.com/blog/home/post/773 thanks! 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 biddisco at cscs.ch Tue Nov 11 06:27:52 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Tue, 11 Nov 2014 11:27:52 +0000 Subject: [Paraview-developers] How to compute difference of data arrays between two time steps for filter. In-Reply-To: References: <50320452A334BD42A5EC72BAD21450991905F471@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD21450991906048E@MBX210.d.ethz.ch> Message-ID: <50320452A334BD42A5EC72BAD214509919DF4263@MBX110.d.ethz.ch> Apologies Maxim I completely forgot about this I?ve just used git filter-branch on another repository and taken two classes out and put them into a repo on github https://github.com/biddisco/pv-temporal there?s no cmakelists in there , but it?ll only take you a minute to make one. I?ll get around to that myself when I get a moment. At some point, I?ll gather some other time based filters I have lying around and add them to that repo. JB From: ?????? ?????? [mailto:maxim.glibin at gmail.com] Sent: 30 October 2014 14:55 To: Biddiscombe, John A. Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] How to compute difference of data arrays between two time steps for filter. Thank you, I look forward to receiving your reply. BR 2014-10-30 15:29 GMT+03:00 Biddiscombe, John A. >: I beg your pardon, it?s not in a public repository. I?ll create a new plugin and put it on github with the classes you need (probably not before the end of the weekend though) JB From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Biddiscombe, John A. Sent: 30 October 2014 13:28 To: ?????? ??????; paraview-developers at paraview.org Subject: Re: [Paraview-developers] How to compute difference of data arrays between two time steps for filter. Maxim vtkTemporalDifferenceFilter is what you want. If you google that, you should find the code. JB From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of ?????? ?????? Sent: 29 October 2014 13:27 To: paraview-developers at paraview.org Subject: [Paraview-developers] How to compute difference of data arrays between two time steps for filter. Hello all, It is necessary to extract only data array, compute difference between two time steps and save obtained difference into output. Who have any ideas how to implement it? BR Maxim -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank.tt at einseinself.org Tue Nov 11 07:00:59 2014 From: frank.tt at einseinself.org (Frank TT) Date: Tue, 11 Nov 2014 13:00:59 +0100 Subject: [Paraview-developers] Using vtkImageMarchingCubes as multithread process gives wrong output In-Reply-To: References: <1413985211.1700.18.camel@imedv21.ime.kfa-juelich.de> Message-ID: <1415707259.17406.1.camel@Judika> Hi Utkarsh, thanks for your hint and sorry for the late answer. I've got some other problem after some updates with remote rendering, which I had have to fix first. I avoid the *.mhd file reader issue using *.xdmf (with binary *.raw) files. This reader works fine and it is consistent with the expectations. So I didn't work on the RequestData(?) function. I'm still using ITK or imagej to create the *.mhd (and *.raw) files. But I have to create an extra *.xdmf header file. Does anybody know a well working *.xdmf converter? Greetings Frank On Sun, 2014-10-26 at 12:07 -0400, Utkarsh Ayachit wrote: > The problem seems to be that the vtkImageMarchingCubes filter is not > designed to be used in cases where data is also partitioned among > ranks. It's RequestData(..) implementation directly uses WHOLE_EXTENT > to determine chunking for threaded executing, it should have been > using UPDATE_EXTENT. > > Utkarsh > > On Thu, Oct 23, 2014 at 8:45 AM, Frank TT wrote: > > On 2014-10-22 20:58, Utkarsh Ayachit wrote: > >> > >> Frank, > >> > >> Did you forget to attach the attachments. > > > > > > Oh, yes. Sorry. > > > > > > > > > > > >> > >> Utkarsh > >> > >> On Wed, Oct 22, 2014 at 6:40 AM, Frank tt > >> wrote: > >>> > >>> Hi, > >>> > >>> I wrote a PV plugin based on vtkImageMarchingCubes.h. At my local > >>> machine it's working fine. But at the server, when running with mpiexec > >>> I get some wrong output of the createt surface. (See attachments) > >>> > >>> Now I'm not sure if this depends on the vtkImageMarchingCubes.h or at > >>> mpiexec. > >>> > >>> I'm using at server: > >>> * cuda-5.5 > >>> * gcc-4.7.1 > >>> * mesa-7.11.2 (selfbuild, like the superbuild) > >>> * openmpi-1.8.1 (selfbuild) > >>> * paraview-4.1.0 (selfbuild) > >>> > >>> Has anybody any idea what I did wrong or what I can do? > >>> > >>> I have the option to use the servers mpi installation > >>> (parastation/gcc-mt-5.0.29). This is what I'm actually doing (I'm > >>> waiting for the next proc slot a the server). > >>> > >>> Greetings > >>> > >>> Frank > >>> > >>> _______________________________________________ > >>> Paraview-developers mailing list > >>> Paraview-developers at paraview.org > >>> http://public.kitware.com/mailman/listinfo/paraview-developers From sankhesh.jhaveri at kitware.com Tue Nov 11 12:31:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Tue, 11 Nov 2014 09:31:05 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Monday, November 10 2014 Message-ID: <20141111173103.793597FF62@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Win7x64-vs10-static-release 1 [2]Mac10.7.5-gcc-nightlymaster-release 4 [3]Mac10.7.5-clang-nightlymaster-release 2 [4]Win7x64-vs10-shared-release 1 -------------------- REPORT -------------------- 7 FAILURES [5]pvcs-collab.ZLibXDMF , 1 , ['Win7x64-vs10-static-release'] [6]pv.ServerConnectDialog , 1 , ['Win7x64-vs10-shared-release'] [7]pvcrs.MemoryInspectorPanel , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [8]pvcrs.TensorGlyph , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [9]pvcrs.TestIsoVolume , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [10]pvcs-tile-display-2x1.TileDisplayScatterPlot-2x1 , 1 , ['Mac10.7.5-clang-nightlymaster-release'] [11]pvcrs.UndoRedo1 , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [12]ubuntu-x64-nightlynext 1 -------------------- REPORT -------------------- 1 FAILURES [13]pvcs-collab.CreateDelete , 1 , ['ubuntu-x64-nightlynext'] Issues with submitters The following expected submitters did not submit: Blight.kitware , ubuntu-x64-nightlymaster Blight.kitware , ubuntu-x64-nightlymaster-static Blight.kitware , ubuntu-x64-coverage Blight.kitware , ubuntu-x64-nightlynext Blight.kitware , ubuntu-x64-nightlynext-static Blight.kitware , ubuntu-x64-nightlynext-nogui amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-11&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-11-11&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release 3. http://open.cdash.org/index.php?project=ParaView&date=2014-11-11&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release 4. http://open.cdash.org/index.php?project=ParaView&date=2014-11-11&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-shared-release 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-11&name=pvcs-collab.ZLibXDMF 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-11&name=pv.ServerConnectDialog 7. http://open.cdash.org/testSummary.php?project=9&date=2014-11-11&name=pvcrs.MemoryInspectorPanel 8. http://open.cdash.org/testSummary.php?project=9&date=2014-11-11&name=pvcrs.TensorGlyph 9. http://open.cdash.org/testSummary.php?project=9&date=2014-11-11&name=pvcrs.TestIsoVolume 10. http://open.cdash.org/testSummary.php?project=9&date=2014-11-11&name=pvcs-tile-display-2x1.TileDisplayScatterPlot-2x1 11. http://open.cdash.org/testSummary.php?project=9&date=2014-11-11&name=pvcrs.UndoRedo1 12. http://open.cdash.org/index.php?project=ParaView&date=2014-11-11&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 13. http://open.cdash.org/testSummary.php?project=9&date=2014-11-11&name=pvcs-collab.CreateDelete -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Nov 12 08:19:13 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 12 Nov 2014 08:19:13 -0500 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: Topics merged into master: 0015111-enable-cinema-dynamic-rendering (VTK) 14809_fix_title_placement 15109_improve_vtkCompleteArrays cgns-plugin From sankhesh.jhaveri at kitware.com Wed Nov 12 12:31:06 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Wed, 12 Nov 2014 09:31:06 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Tuesday, November 11 2014 Message-ID: <20141112173104.87B62804D2@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-clang-nightlymaster-release 4 [2]Win7x64-vs10-static-release 1 [3]Mac10.7.5-gcc-nightlymaster-release 4 [4]Win7x64-ninja-nightlymaster-static-release 1 -------------------- REPORT -------------------- 10 FAILURES [5]pvcrs.ExTimeseries2 , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [6]pvcs-collab.ZLibXDMF , 1 , ['Win7x64-vs10-static-release'] [7]pvcs-collab.PropertyConversion1 , 1 , ['Mac10.7.5-clang-nightlymaster-release'] [8]pvcrs.TemporalShiftScale , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [9]pvcrs.UndoRedo1 , 1 , ['Mac10.7.5-clang-nightlymaster-release'] [10]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [11]pvcs.MultiSliceMultiBlock , 1 , ['Mac10.7.5-clang-nightlymaster-release'] [12]pv.UndoRedo1 , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [13]pvcrs.TensorGlyph , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [14]pvcs.UndoRedo1 , 1 , ['Mac10.7.5-clang-nightlymaster-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [15]Win64-vs9-static-release 2 -------------------- REPORT -------------------- 2 FAILURES [16]pvcs-collab.SpreadSheet1 , 1 , ['Win64-vs9-static-release'] [17]pvcs-collab.CreateDelete , 1 , ['Win64-vs9-static-release'] Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-12&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-11-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 3. http://open.cdash.org/index.php?project=ParaView&date=2014-11-12&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release 4. http://open.cdash.org/index.php?project=ParaView&date=2014-11-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pvcrs.ExTimeseries2 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pvcs-collab.ZLibXDMF 7. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pvcs-collab.PropertyConversion1 8. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pvcrs.TemporalShiftScale 9. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pvcrs.UndoRedo1 10. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter 11. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pvcs.MultiSliceMultiBlock 12. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pv.UndoRedo1 13. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pvcrs.TensorGlyph 14. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pvcs.UndoRedo1 15. http://open.cdash.org/index.php?project=ParaView&date=2014-11-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release 16. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pvcs-collab.SpreadSheet1 17. http://open.cdash.org/testSummary.php?project=9&date=2014-11-12&name=pvcs-collab.CreateDelete -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Thu Nov 13 12:31:08 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Thu, 13 Nov 2014 09:31:08 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Wednesday, November 12 2014 Message-ID: <20141113173103.E2F2880EE8@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-gcc-nightlymaster-release 4 [2]ubuntu-x64-nightlymaster-static 1 -------------------- REPORT -------------------- 5 FAILURES [3]pvcrs.TensorGlyph , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [4]pvcrs.TemporalShiftScale , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [5]pv.ServerConnectDialog , 1 , ['ubuntu-x64-nightlymaster-static'] [6]pvcrs.TemporalInterpolator , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [7]pvcrs.MemoryInspectorPanel , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] Dashboard status for Nightly (next) Cdash returned nothing useful as of this report. Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-13&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-11-13&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-13&name=pvcrs.TensorGlyph 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-13&name=pvcrs.TemporalShiftScale 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-13&name=pv.ServerConnectDialog 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-13&name=pvcrs.TemporalInterpolator 7. http://open.cdash.org/testSummary.php?project=9&date=2014-11-13&name=pvcrs.MemoryInspectorPanel -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank.tt at einseinself.org Fri Nov 14 04:18:56 2014 From: frank.tt at einseinself.org (Frank tt) Date: Fri, 14 Nov 2014 10:18:56 +0100 Subject: [Paraview-developers] Get coordinates of selectetd cells in data set Message-ID: <1415956736.2462.5.camel@einseinself.org> Hi, I want to mark one or more cells at a surface data set. Now I'm interestet in its coordines to use them for further analytics in my plugin. I'm trying to get something like: int infoStream::RequestData( vtkInformation *vtkNotUsed(request), vtkInformationVector **inputVector, vtkInformationVector *outputVector ) { inputInfo = inputVector[0]->GetInformationObject(0); outputInfo = outputVector->GetInformationObject(0); inputData = vtkImageData::SafeDownCast( inputInfo->Get(vtkDataObject::DATA_OBJECT()) ); // TODO: vtkIdList cellPtIds = inputInfo->GetCellSelection(); vtkCell3D cell = cellPtIds->getMiddle(); std::vector coords = cell->getCoords(); return 1; } I know about the 'Selection Inspector' (PV 3.3.0). In my version (4.1.0), it does not exist. I've found a 'Selection Display Inspector' with some different functions. I don't know how to get the selection from the user to the plugin and work with it. I'm using locally: ParaView 4.1.0 Qt 4.8.6 server side: ParaView 4.1.0 OSMesa 7.11.2 OpenMPI 1.8.1 Greetings, Frank From maxim.glibin at gmail.com Fri Nov 14 11:23:23 2014 From: maxim.glibin at gmail.com (=?UTF-8?B?0JzQsNC60YHQuNC8INCT0LvQuNCx0LjQvQ==?=) Date: Fri, 14 Nov 2014 19:23:23 +0300 Subject: [Paraview-developers] Server Manager XML Message-ID: Hello everybody, It is necessary for the information helper to retrieve information from the server about names of attribute arrays indicating cell data and point data arrays simultaneously. As I know ArrayCollectionInformationHelper allows to implement the similar situation, but only for one of data arrays(Point or Cell attribute_name). Who have any ideas how to implement it? Maxim. -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Nov 14 11:28:44 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 14 Nov 2014 11:28:44 -0500 Subject: [Paraview-developers] Server Manager XML In-Reply-To: References: Message-ID: If you don't care the application to distinguishing between point/cell when you can still use ArraySelectionInformationHelper on a single property. Pick any attribute_name="..". The helper will look for Get* methods using the suffix you specify. If you do case about the application knowing the different between the two, you'd need two properties, separate for point and cell, I am afraid. Utkarsh On Fri, Nov 14, 2014 at 11:23 AM, ?????? ?????? wrote: > Hello everybody, > > It is necessary for the information helper to retrieve information from the > server about names of attribute arrays indicating cell data and point data > arrays simultaneously. > As I know ArrayCollectionInformationHelper allows to implement the similar > situation, but only for one of data arrays(Point or Cell attribute_name). > Who have any ideas how to implement it? > > Maxim. > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > From sankhesh.jhaveri at kitware.com Fri Nov 14 12:31:11 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Fri, 14 Nov 2014 09:31:11 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Thursday, November 13 2014 Message-ID: <20141114173104.050F77FF5E@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-gcc-nightlymaster-release 4 [2]Mac10.7.5-clang-nightlymaster-release 2 -------------------- REPORT -------------------- 6 FAILURES [3]pvcrs.UndoRedo1 , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [4]pvcs.TraceExportAndSaveData , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [5]pvcrs.ChartAxisRangeAndLabels , 1 , ['Mac10.7.5-clang-nightlymaster-release'] [6]pvcrs.TensorGlyph , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [7]pvcs.Threshold , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [8]pvcrs.TestIsoVolume , 1 , ['Mac10.7.5-clang-nightlymaster-release'] Dashboard status for Nightly (next) Cdash returned nothing useful as of this report. Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-14&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-11-14&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-14&name=pvcrs.UndoRedo1 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-14&name=pvcs.TraceExportAndSaveData 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-14&name=pvcrs.ChartAxisRangeAndLabels 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-14&name=pvcrs.TensorGlyph 7. http://open.cdash.org/testSummary.php?project=9&date=2014-11-14&name=pvcs.Threshold 8. http://open.cdash.org/testSummary.php?project=9&date=2014-11-14&name=pvcrs.TestIsoVolume -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Nov 14 23:05:57 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 14 Nov 2014 23:05:57 -0500 Subject: [Paraview-developers] Paraview save state wrong implemetation for GUI In-Reply-To: References: Message-ID: A pvsm file should store the entire state of the pipeline. Things like "server tells GUI which elements are checked" after a state file is loaded are generally not necessary and strongly dissuaded. The corresponding property should have the entire state. If you can post your XML for the filter, and the state xml, I can try to provide a more useful reply. Utkarsh On Mon, Nov 10, 2014 at 3:55 AM, RIVERA, Orlando wrote: > Hello > > I need again your help > > I been working on a Plugin base on vtkMultiBlockDataSetAlgorithm. It does pretty much what I do , but I am missing something ! > > When I read my data and select the blocks, it works fine , When I save the state (File->SaveState) the corresponding *.psvm is written and when I tried to load the state, from the previous generated file , the Data is loaded as expected. > > My problem is in the GUI . I have a GUI with a QTreeWidget, and the state of the previous state is not loaded (the leaves in the tree are not checked), > I assume I have to tell the GUI what was its previous state . I also assume that the best place to do it is a the end of RequestData (server) : i.e Server tells GUI which of its elements have to be checked,marked ,displayed ,etc . > > - How the GUI can read the state on a pvsm? > - Which function is responsible for recovering the state on the GUI/client side? > - How can I drive events on the GUI from Server ? ( Influence the CLIENT from the server , is that possible) > > Any Help would be greatly appreciated > > Cheers !! > > Orlando > > > > > -- > MTU Aero Engines AG > Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schrey?gg, Dr. Stefan Weingartner > Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt > Sitz der Gesellschaft/Registered Office: Muenchen > Handelsregister/Commercial Register: Muenchen HRB 157206 > > Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. > Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese > E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. > > This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. > If you are not the intended recipient, please advise the sender and delete this message and its attachments. > Any unauthorised storing, copying or distribution is prohibited. > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers From utkarsh.ayachit at kitware.com Sat Nov 15 09:57:54 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 15 Nov 2014 09:57:54 -0500 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: Topics merged into master (v4.2.0-133-g7e996c8) 0015121_fix_ambient_diffuse 14835_fix_log_scale_for_coloring (VTK) 15101_fix_particlepath 15126_fix_properties_panel 15128_fix_output_window_on_Windows (VTK) adios-buffer-resizing cmake-warnings-20140922 fix-COPYONLY-usage osx-deprecation-warnings remove-else-and-endfoo-cmake-args (VTK) update-vtk-20141114 From frank.tt at einseinself.org Mon Nov 17 02:29:18 2014 From: frank.tt at einseinself.org (Frank tt) Date: Mon, 17 Nov 2014 08:29:18 +0100 Subject: [Paraview-developers] Get coordinates of selectetd cells in data set In-Reply-To: <1415956736.2462.5.camel@einseinself.org> References: <1415956736.2462.5.camel@einseinself.org> Message-ID: <1416209358.1549.4.camel@einseinself.org> Hi. I found an interesting filter 'Extract Selection'. It creates an new data set only including the selection of the current data set. In the Properties dock is a function 'Copy Active Selection'. Now I'm trying to analyse the code to get an idea, what I should do for my plugin. Are source/ParaViewCore/ClientServerCore/Core/vtkPVExtractSelection.h and its *.cxx the correct files I found an surface selection example in? Where is the *.ui or server manger *.xml file? Greetings Frank On Fri, 2014-11-14 at 10:18 +0100, Frank tt wrote: > Hi, > > > I want to mark one or more cells at a surface data set. Now I'm > interestet in its coordines to use them for further analytics in my > plugin. > > I'm trying to get something like: > > int infoStream::RequestData( vtkInformation *vtkNotUsed(request), > vtkInformationVector **inputVector, > vtkInformationVector *outputVector ) > { > inputInfo = inputVector[0]->GetInformationObject(0); > outputInfo = outputVector->GetInformationObject(0); > > inputData = vtkImageData::SafeDownCast( inputInfo->Get(vtkDataObject::DATA_OBJECT()) ); > > > // TODO: > vtkIdList cellPtIds = inputInfo->GetCellSelection(); > vtkCell3D cell = cellPtIds->getMiddle(); > std::vector coords = cell->getCoords(); > > > return 1; > } > > I know about the 'Selection Inspector' (PV 3.3.0). In my version (4.1.0), it > does not exist. I've found a 'Selection Display Inspector' with some > different functions. > > I don't know how to get the selection from the user to the plugin and work with it. > > I'm using locally: > ParaView 4.1.0 > Qt 4.8.6 > > server side: > ParaView 4.1.0 > OSMesa 7.11.2 > OpenMPI 1.8.1 > > > > Greetings, > Frank > > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers From sankhesh.jhaveri at kitware.com Mon Nov 17 12:31:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Mon, 17 Nov 2014 09:31:05 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Sunday, November 16 2014 Message-ID: <20141117173103.C5AA980E7A@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]fedora-x64-icc-nightlymaster-debug 2 [2]ubuntu-x64-nightlymaster-unified 3 -------------------- REPORT -------------------- 5 FAILURES [3]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [4]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [5]pv.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlymaster-unified'] [6]pvcs.ChartAxisRangeAndLabels , 1 , ['ubuntu-x64-nightlymaster-unified'] [7]pvcs.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlymaster-unified'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [8]fedora-x64-icc-nightlynext-release 2 -------------------- REPORT -------------------- 2 FAILURES [9]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] [10]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-17&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 2. http://open.cdash.org/index.php?project=ParaView&date=2014-11-17&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-17&name=pvcs.PropertyLink 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-17&name=pvcrs.PropertyLink 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-17&name=pv.ColorOpacityTableEditing 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-17&name=pvcs.ChartAxisRangeAndLabels 7. http://open.cdash.org/testSummary.php?project=9&date=2014-11-17&name=pvcs.ColorOpacityTableEditing 8. http://open.cdash.org/index.php?project=ParaView&date=2014-11-17&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 9. http://open.cdash.org/testSummary.php?project=9&date=2014-11-17&name=pvcs.PropertyLink 10. http://open.cdash.org/testSummary.php?project=9&date=2014-11-17&name=pvcrs.PropertyLink -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Tue Nov 18 12:31:08 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Tue, 18 Nov 2014 09:31:08 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Monday, November 17 2014 Message-ID: <20141118173103.A061A7FF37@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Win7x64-vs10-static-release 1 [2]fedora-x64-icc-nightlymaster-debug 2 -------------------- REPORT -------------------- 3 FAILURES [3]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [4]pv.ServerConnectDialog , 1 , ['Win7x64-vs10-static-release'] [5]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [6]fedora-x64-icc-nightlynext-release 1 -------------------- REPORT -------------------- 1 FAILURES [7]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-18&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-11-18&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-18&name=pvcs.PropertyLink 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-18&name=pv.ServerConnectDialog 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-18&name=pvcrs.PropertyLink 6. http://open.cdash.org/index.php?project=ParaView&date=2014-11-18&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 7. http://open.cdash.org/testSummary.php?project=9&date=2014-11-18&name=pvcrs.PropertyLink -------------- next part -------------- An HTML attachment was scrubbed... URL: From joshiga at gmail.com Wed Nov 19 03:36:07 2014 From: joshiga at gmail.com (Girish Joshi) Date: Wed, 19 Nov 2014 14:06:07 +0530 Subject: [Paraview-developers] Point Sprite Compilation Problem Message-ID: Hi, I'm trying to build custom VTK having point sprite from paraview source (Paraview-4.0.1) in VTK. I got error while compiling that the vtkPointSpriteGraphicsModule.h file is missing. I searched the source folder for the file but couldn't get it. Where could I get this file and all the relevant files to build VTK with point sprite support? Best Regards, Girish -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Wed Nov 19 07:15:26 2014 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Wed, 19 Nov 2014 17:45:26 +0530 Subject: [Paraview-developers] Building Examples - Message-ID: Hi All, I am trying to build a full tree of paraview(v4.2.0) locally with Examples with the intention of developing my own plugin. I started afresh with downloading the paraview source and building from scratch. I followed the following steps : 1. Extracted the source and create a build directory under the source. Then I run cmake to build the Makefile with the following option : cmake -DCMAKE_SKIP_BUILD_RPATH:BOOL=OFF -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=OFF -DCMAKE_INSTALL_RPATH:STRING="" -DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=OFF -DBUILD_EXAMPLE:BOOL=ON -DBUILD_EXAMPLES:BOOL=ON -DBUILD_TESTING:BOOL=OFF -DPARAVIEW_QT_VERSION:STRING=5 -DCMAKE_PREFIX_PATH:PATH=$QTDIR -DPARAVIEW_USE_MPI:BOOL=ON -DQT_DISABLE_WEBKIT:BOOL=OFF -DBUILD_SHARED_LIBS:BOOL=ON -DPARAVIEW_ENABLE_PYTHON:BOOL=ON -DPARAVIEW_ENABLE_FFMPEG:BOOL=OFF -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR $SRC_DIR where I declare INSTALLDIR and SRC_DIR myself. 2. Then I run "make" to build the tree and the process terminates without any error. 3. Once I build the main paraview tree, I found that "Examples" directory is created with CMakeLists.txt file inside that. I run the following from the build location : cmake After completion of this level "Examples/All" is created under the build location which contains the file "CMakeCache.txt and " and the direcotry "CMakeFiles" but none of the plugins are getting generated. Am I doing something wrong or there are some alternative methods to build the examples for Paraview ? I was looking for the other threads for an answer but could not found one that solves my problem. If anyone can give me some pointers about how to build Paraview + Examples which can work as a basic platform for my plugin development, I will be very thankful. Thanks for your time and the help. Chiranjib From alexandre.ancel at cemosis.fr Wed Nov 19 09:55:47 2014 From: alexandre.ancel at cemosis.fr (Alexandre Ancel) Date: Wed, 19 Nov 2014 15:55:47 +0100 Subject: [Paraview-developers] Building Examples - In-Reply-To: References: Message-ID: Hello Chiranjib, First I am not a Paraview developer, just a simple user that also uses a self-compiled version of ParaView. Regarding to your problem, I tested building the examples by adding the -DBUILD_EXAMPLES:BOOL=ON to my locally built ParaView. I think that Step 3 in your build process is wrong. You do not have to reexecute the cmake command in the Examples/All subdirectory. The examples are built as a subproject, so all you need to do normally is to enable them in cmake and then go to the Examples/All directory and type make. That did the trick for me and I was able to build the examples provided with Paraview (being generated in the bin and lib directories of the base build dir). Hope it helps in your developments, Best regards, Alexandre Ancel On Wed, Nov 19, 2014 at 1:15 PM, Chiranjib Sur wrote: > Hi All, > I am trying to build a full tree of paraview(v4.2.0) locally with > Examples with the intention of developing my own plugin. I started > afresh with downloading the paraview source and building from scratch. > > I followed the following steps : > > 1. Extracted the source and create a build directory under the source. > Then I run cmake to build the Makefile with the following option : > > cmake -DCMAKE_SKIP_BUILD_RPATH:BOOL=OFF > -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=OFF > -DCMAKE_INSTALL_RPATH:STRING="" > -DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=OFF -DBUILD_EXAMPLE:BOOL=ON > -DBUILD_EXAMPLES:BOOL=ON -DBUILD_TESTING:BOOL=OFF > -DPARAVIEW_QT_VERSION:STRING=5 -DCMAKE_PREFIX_PATH:PATH=$QTDIR > -DPARAVIEW_USE_MPI:BOOL=ON -DQT_DISABLE_WEBKIT:BOOL=OFF > -DBUILD_SHARED_LIBS:BOOL=ON -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > -DPARAVIEW_ENABLE_FFMPEG:BOOL=OFF > -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR $SRC_DIR > > where I declare INSTALLDIR and SRC_DIR myself. > > 2. Then I run "make" to build the tree and the process terminates > without any error. > > 3. Once I build the main paraview tree, I found that "Examples" > directory is created with CMakeLists.txt file inside that. I run the > following from the build location : > > cmake > > After completion of this level "Examples/All" is created under the > build location which contains the file "CMakeCache.txt and " and the > direcotry "CMakeFiles" but none of the plugins are getting generated. > > Am I doing something wrong or there are some alternative methods to > build the examples for Paraview ? > > I was looking for the other threads for an answer but could not found > one that solves my problem. > > If anyone can give me some pointers about how to build Paraview + > Examples which can work as a basic platform for my plugin development, > I will be very thankful. > > Thanks for your time and the help. > > Chiranjib > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Alexandre Ancel Docteur, Ing?nieur de recherche / Phd, Research Engineer Cemosis - alexandre.ancel at cemosis.fr Tel: +33 (0)3 68 8*5 02 06* IRMA - 7, rue Ren? Descartes 67 000 Strasbourg, France -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Wed Nov 19 12:31:10 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Wed, 19 Nov 2014 09:31:10 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Tuesday, November 18 2014 Message-ID: <20141119173103.B54807FF52@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]fedora-x64-icc-nightlymaster-debug 2 [2]Master-Win64-vs9-shared-release 1 -------------------- REPORT -------------------- 3 FAILURES [3]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [4]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [5]pv.ServerConnectDialog , 1 , ['Master-Win64-vs9-shared-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [6]fedora-x64-icc-nightlynext-release 2 -------------------- REPORT -------------------- 2 FAILURES [7]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] [8]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] Issues with submitters The following expected submitters did not submit: KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-19&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 2. http://open.cdash.org/index.php?project=ParaView&date=2014-11-19&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-shared-release 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-19&name=pvcs.PropertyLink 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-19&name=pvcrs.PropertyLink 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-19&name=pv.ServerConnectDialog 6. http://open.cdash.org/index.php?project=ParaView&date=2014-11-19&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 7. http://open.cdash.org/testSummary.php?project=9&date=2014-11-19&name=pvcs.PropertyLink 8. http://open.cdash.org/testSummary.php?project=9&date=2014-11-19&name=pvcrs.PropertyLink -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Thu Nov 20 00:44:05 2014 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Thu, 20 Nov 2014 11:14:05 +0530 Subject: [Paraview-developers] Building Examples - In-Reply-To: References: Message-ID: Hi Ancel, Thanks for your reply. I followed your steps. I can get Examples/All after the first set of build but to run "make" at that directory, I need to have a "Makefile" there, which doesn't exist for this case. My build/Examples/All contain the file "CMakeCache.txt" and the folder "CMakeFiles" Threfore, in a nutshell, I am back to square one with no example libraries built. Any more pointers ? Thanks again for your suggestions. Chiranjib On Wed, Nov 19, 2014 at 8:25 PM, Alexandre Ancel wrote: > Hello Chiranjib, > > First I am not a Paraview developer, just a simple user that also uses a > self-compiled version of ParaView. > > Regarding to your problem, I tested building the examples by adding the > -DBUILD_EXAMPLES:BOOL=ON to my locally built ParaView. > > I think that Step 3 in your build process is wrong. You do not have to > reexecute the cmake command in the Examples/All subdirectory. The examples > are built as a subproject, so all you need to do normally is to enable them > in cmake and then go to the Examples/All directory and type make. That did > the trick for me and I was able to build the examples provided with Paraview > (being generated in the bin and lib directories of the base build dir). > > Hope it helps in your developments, > > Best regards, > > Alexandre Ancel > > On Wed, Nov 19, 2014 at 1:15 PM, Chiranjib Sur > wrote: >> >> Hi All, >> I am trying to build a full tree of paraview(v4.2.0) locally with >> Examples with the intention of developing my own plugin. I started >> afresh with downloading the paraview source and building from scratch. >> >> I followed the following steps : >> >> 1. Extracted the source and create a build directory under the source. >> Then I run cmake to build the Makefile with the following option : >> >> cmake -DCMAKE_SKIP_BUILD_RPATH:BOOL=OFF >> -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=OFF >> -DCMAKE_INSTALL_RPATH:STRING="" >> -DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=OFF -DBUILD_EXAMPLE:BOOL=ON >> -DBUILD_EXAMPLES:BOOL=ON -DBUILD_TESTING:BOOL=OFF >> -DPARAVIEW_QT_VERSION:STRING=5 -DCMAKE_PREFIX_PATH:PATH=$QTDIR >> -DPARAVIEW_USE_MPI:BOOL=ON -DQT_DISABLE_WEBKIT:BOOL=OFF >> -DBUILD_SHARED_LIBS:BOOL=ON -DPARAVIEW_ENABLE_PYTHON:BOOL=ON >> -DPARAVIEW_ENABLE_FFMPEG:BOOL=OFF >> -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR $SRC_DIR >> >> where I declare INSTALLDIR and SRC_DIR myself. >> >> 2. Then I run "make" to build the tree and the process terminates >> without any error. >> >> 3. Once I build the main paraview tree, I found that "Examples" >> directory is created with CMakeLists.txt file inside that. I run the >> following from the build location : >> >> cmake >> >> After completion of this level "Examples/All" is created under the >> build location which contains the file "CMakeCache.txt and " and the >> direcotry "CMakeFiles" but none of the plugins are getting generated. >> >> Am I doing something wrong or there are some alternative methods to >> build the examples for Paraview ? >> >> I was looking for the other threads for an answer but could not found >> one that solves my problem. >> >> If anyone can give me some pointers about how to build Paraview + >> Examples which can work as a basic platform for my plugin development, >> I will be very thankful. >> >> Thanks for your time and the help. >> >> Chiranjib >> _______________________________________________ >> Paraview-developers mailing list >> Paraview-developers at paraview.org >> http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > -- > Alexandre Ancel > Docteur, Ing?nieur de recherche / Phd, Research Engineer > Cemosis - alexandre.ancel at cemosis.fr > Tel: +33 (0)3 68 85 02 06 > IRMA - 7, rue Ren? Descartes > 67 000 Strasbourg, France From alexandre.ancel at cemosis.fr Thu Nov 20 03:18:38 2014 From: alexandre.ancel at cemosis.fr (Alexandre Ancel) Date: Thu, 20 Nov 2014 09:18:38 +0100 Subject: [Paraview-developers] Building Examples - In-Reply-To: References: Message-ID: Hello Chiranjib, The CMakeCache.txt is a remaining file from your previous cmake comamnd you issued in Examples/All. I think the best to do is to delete the Examples directory to clean up what you previously did, then make sure you activated the examples (-DBUILD_EXAMPLE:BOOL=ON) in the base build dir, then relaunch the make command. It should recreate the examples dir, and eventually you can run the make command in the Examples/All directory. Best regards, Alexandre On Thu, Nov 20, 2014 at 6:44 AM, Chiranjib Sur wrote: > Hi Ancel, > Thanks for your reply. > I followed your steps. I can get Examples/All after the first set of > build but to run "make" at that directory, > > I need to have a "Makefile" there, which doesn't exist for this case. > My build/Examples/All contain the file "CMakeCache.txt" and the folder > "CMakeFiles" > > Threfore, in a nutshell, I am back to square one with no example > libraries built. > > Any more pointers ? > Thanks again for your suggestions. > > Chiranjib > > On Wed, Nov 19, 2014 at 8:25 PM, Alexandre Ancel > wrote: > > Hello Chiranjib, > > > > First I am not a Paraview developer, just a simple user that also uses a > > self-compiled version of ParaView. > > > > Regarding to your problem, I tested building the examples by adding the > > -DBUILD_EXAMPLES:BOOL=ON to my locally built ParaView. > > > > I think that Step 3 in your build process is wrong. You do not have to > > reexecute the cmake command in the Examples/All subdirectory. The > examples > > are built as a subproject, so all you need to do normally is to enable > them > > in cmake and then go to the Examples/All directory and type make. That > did > > the trick for me and I was able to build the examples provided with > Paraview > > (being generated in the bin and lib directories of the base build dir). > > > > Hope it helps in your developments, > > > > Best regards, > > > > Alexandre Ancel > > > > On Wed, Nov 19, 2014 at 1:15 PM, Chiranjib Sur > > wrote: > >> > >> Hi All, > >> I am trying to build a full tree of paraview(v4.2.0) locally with > >> Examples with the intention of developing my own plugin. I started > >> afresh with downloading the paraview source and building from scratch. > >> > >> I followed the following steps : > >> > >> 1. Extracted the source and create a build directory under the source. > >> Then I run cmake to build the Makefile with the following option : > >> > >> cmake -DCMAKE_SKIP_BUILD_RPATH:BOOL=OFF > >> -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=OFF > >> -DCMAKE_INSTALL_RPATH:STRING="" > >> -DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=OFF -DBUILD_EXAMPLE:BOOL=ON > >> -DBUILD_EXAMPLES:BOOL=ON -DBUILD_TESTING:BOOL=OFF > >> -DPARAVIEW_QT_VERSION:STRING=5 -DCMAKE_PREFIX_PATH:PATH=$QTDIR > >> -DPARAVIEW_USE_MPI:BOOL=ON -DQT_DISABLE_WEBKIT:BOOL=OFF > >> -DBUILD_SHARED_LIBS:BOOL=ON -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > >> -DPARAVIEW_ENABLE_FFMPEG:BOOL=OFF > >> -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR $SRC_DIR > >> > >> where I declare INSTALLDIR and SRC_DIR myself. > >> > >> 2. Then I run "make" to build the tree and the process terminates > >> without any error. > >> > >> 3. Once I build the main paraview tree, I found that "Examples" > >> directory is created with CMakeLists.txt file inside that. I run the > >> following from the build location : > >> > >> cmake > >> > >> After completion of this level "Examples/All" is created under the > >> build location which contains the file "CMakeCache.txt and " and the > >> direcotry "CMakeFiles" but none of the plugins are getting generated. > >> > >> Am I doing something wrong or there are some alternative methods to > >> build the examples for Paraview ? > >> > >> I was looking for the other threads for an answer but could not found > >> one that solves my problem. > >> > >> If anyone can give me some pointers about how to build Paraview + > >> Examples which can work as a basic platform for my plugin development, > >> I will be very thankful. > >> > >> Thanks for your time and the help. > >> > >> Chiranjib > >> _______________________________________________ > >> Paraview-developers mailing list > >> Paraview-developers at paraview.org > >> http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > > > > > -- > > Alexandre Ancel > > Docteur, Ing?nieur de recherche / Phd, Research Engineer > > Cemosis - alexandre.ancel at cemosis.fr > > Tel: +33 (0)3 68 85 02 06 > > IRMA - 7, rue Ren? Descartes > > 67 000 Strasbourg, France > -- Alexandre Ancel Docteur, Ing?nieur de recherche / Phd, Research Engineer Cemosis - alexandre.ancel at cemosis.fr Tel: +33 (0)3 68 8*5 02 06* IRMA - 7, rue Ren? Descartes 67 000 Strasbourg, France -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Thu Nov 20 05:47:00 2014 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Thu, 20 Nov 2014 16:17:00 +0530 Subject: [Paraview-developers] Building Examples - In-Reply-To: References: Message-ID: Hi Alexandre, Thanks much for your email. I tried this but still I am hitting the same error. Here are the steps : 1. Created a new build location and I ran cmake with the option (-DBUILD_EXAMPLES:BOOL=ON). This creates the Makefile at the source location. 2. When I run 'make' at the source, Examples/All is created at the build location but it contains the CMakeCache.txt and the CMakefiles directory. Nothing else. Therefore I am not able to launch 'make' at build_location/Examples/All FYI, I am using the following bundle : qt.5.2.1 + cmake 3.0.2 + Paraview 4.2.0 (downloaded as tar.gz from the website - not through git clone) Any more suggestions ? Thanks and regards, Chiranjib On Thu, Nov 20, 2014 at 1:48 PM, Alexandre Ancel wrote: > Hello Chiranjib, > > The CMakeCache.txt is a remaining file from your previous cmake comamnd you > issued in Examples/All. > I think the best to do is to delete the Examples directory to clean up what > you previously did, then make sure you activated the examples > (-DBUILD_EXAMPLE:BOOL=ON) in the base build dir, then relaunch the make > command. It should recreate the examples dir, and eventually you can run the > make command in the Examples/All directory. > > Best regards, > Alexandre > > On Thu, Nov 20, 2014 at 6:44 AM, Chiranjib Sur > wrote: >> >> Hi Ancel, >> Thanks for your reply. >> I followed your steps. I can get Examples/All after the first set of >> build but to run "make" at that directory, >> >> I need to have a "Makefile" there, which doesn't exist for this case. >> My build/Examples/All contain the file "CMakeCache.txt" and the folder >> "CMakeFiles" >> >> Threfore, in a nutshell, I am back to square one with no example >> libraries built. >> >> Any more pointers ? >> Thanks again for your suggestions. >> >> Chiranjib >> >> On Wed, Nov 19, 2014 at 8:25 PM, Alexandre Ancel >> wrote: >> > Hello Chiranjib, >> > >> > First I am not a Paraview developer, just a simple user that also uses a >> > self-compiled version of ParaView. >> > >> > Regarding to your problem, I tested building the examples by adding the >> > -DBUILD_EXAMPLES:BOOL=ON to my locally built ParaView. >> > >> > I think that Step 3 in your build process is wrong. You do not have to >> > reexecute the cmake command in the Examples/All subdirectory. The >> > examples >> > are built as a subproject, so all you need to do normally is to enable >> > them >> > in cmake and then go to the Examples/All directory and type make. That >> > did >> > the trick for me and I was able to build the examples provided with >> > Paraview >> > (being generated in the bin and lib directories of the base build dir). >> > >> > Hope it helps in your developments, >> > >> > Best regards, >> > >> > Alexandre Ancel >> > >> > On Wed, Nov 19, 2014 at 1:15 PM, Chiranjib Sur >> > wrote: >> >> >> >> Hi All, >> >> I am trying to build a full tree of paraview(v4.2.0) locally with >> >> Examples with the intention of developing my own plugin. I started >> >> afresh with downloading the paraview source and building from scratch. >> >> >> >> I followed the following steps : >> >> >> >> 1. Extracted the source and create a build directory under the source. >> >> Then I run cmake to build the Makefile with the following option : >> >> >> >> cmake -DCMAKE_SKIP_BUILD_RPATH:BOOL=OFF >> >> -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=OFF >> >> -DCMAKE_INSTALL_RPATH:STRING="" >> >> -DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=OFF -DBUILD_EXAMPLE:BOOL=ON >> >> -DBUILD_EXAMPLES:BOOL=ON -DBUILD_TESTING:BOOL=OFF >> >> -DPARAVIEW_QT_VERSION:STRING=5 -DCMAKE_PREFIX_PATH:PATH=$QTDIR >> >> -DPARAVIEW_USE_MPI:BOOL=ON -DQT_DISABLE_WEBKIT:BOOL=OFF >> >> -DBUILD_SHARED_LIBS:BOOL=ON -DPARAVIEW_ENABLE_PYTHON:BOOL=ON >> >> -DPARAVIEW_ENABLE_FFMPEG:BOOL=OFF >> >> -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR $SRC_DIR >> >> >> >> where I declare INSTALLDIR and SRC_DIR myself. >> >> >> >> 2. Then I run "make" to build the tree and the process terminates >> >> without any error. >> >> >> >> 3. Once I build the main paraview tree, I found that "Examples" >> >> directory is created with CMakeLists.txt file inside that. I run the >> >> following from the build location : >> >> >> >> cmake >> >> >> >> After completion of this level "Examples/All" is created under the >> >> build location which contains the file "CMakeCache.txt and " and the >> >> direcotry "CMakeFiles" but none of the plugins are getting generated. >> >> >> >> Am I doing something wrong or there are some alternative methods to >> >> build the examples for Paraview ? >> >> >> >> I was looking for the other threads for an answer but could not found >> >> one that solves my problem. >> >> >> >> If anyone can give me some pointers about how to build Paraview + >> >> Examples which can work as a basic platform for my plugin development, >> >> I will be very thankful. >> >> >> >> Thanks for your time and the help. >> >> >> >> Chiranjib >> >> _______________________________________________ >> >> Paraview-developers mailing list >> >> Paraview-developers at paraview.org >> >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > >> > >> > >> > >> > -- >> > Alexandre Ancel >> > Docteur, Ing?nieur de recherche / Phd, Research Engineer >> > Cemosis - alexandre.ancel at cemosis.fr >> > Tel: +33 (0)3 68 85 02 06 >> > IRMA - 7, rue Ren? Descartes >> > 67 000 Strasbourg, France > > > > > -- > Alexandre Ancel > Docteur, Ing?nieur de recherche / Phd, Research Engineer > Cemosis - alexandre.ancel at cemosis.fr > Tel: +33 (0)3 68 85 02 06 > IRMA - 7, rue Ren? Descartes > 67 000 Strasbourg, France From sankhesh.jhaveri at kitware.com Thu Nov 20 12:31:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Thu, 20 Nov 2014 09:31:05 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Wednesday, November 19 2014 Message-ID: <20141120173104.331BF7FF5F@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Master-Win64-vs9-shared-release 1 [2]fedora-x64-icc-nightlymaster-debug 3 -------------------- REPORT -------------------- 4 FAILURES [3]pv.TestPopOutWidget , 1 , ['fedora-x64-icc-nightlymaster-debug'] [4]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [5]pv.XdmfGridAttributes , 1 , ['Master-Win64-vs9-shared-release'] [6]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [7]fedora-x64-icc-nightlynext-release 2 [8]ubuntu-x64-nightlynext 1 -------------------- REPORT -------------------- 3 FAILURES [9]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] [10]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] [11]pvcs-collab.CreateDelete , 1 , ['ubuntu-x64-nightlynext'] Issues with submitters The following expected submitters did not submit: KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-20&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-shared-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-11-20&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-20&name=pv.TestPopOutWidget 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-20&name=pvcs.PropertyLink 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-20&name=pv.XdmfGridAttributes 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-20&name=pvcrs.PropertyLink 7. http://open.cdash.org/index.php?project=ParaView&date=2014-11-20&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 8. http://open.cdash.org/index.php?project=ParaView&date=2014-11-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 9. http://open.cdash.org/testSummary.php?project=9&date=2014-11-20&name=pvcs.PropertyLink 10. http://open.cdash.org/testSummary.php?project=9&date=2014-11-20&name=pvcrs.PropertyLink 11. http://open.cdash.org/testSummary.php?project=9&date=2014-11-20&name=pvcs-collab.CreateDelete -------------- next part -------------- An HTML attachment was scrubbed... URL: From yumin.yuan at kitware.com Thu Nov 20 12:34:48 2014 From: yumin.yuan at kitware.com (Yumin Yuan) Date: Thu, 20 Nov 2014 12:34:48 -0500 Subject: [Paraview-developers] Dashboard Status: Wednesday, November 19 2014 In-Reply-To: <20141120173104.331BF7FF5F@sanganak-ubuntu> References: <20141120173104.331BF7FF5F@sanganak-ubuntu> Message-ID: Hi folks, Anybody knows an easy way to run ONLY all Paraview UI tests. I am trying out some changes in QtTesting repo. Thanks, Yumin On Thu, Nov 20, 2014 at 12:31 PM, Sankhesh Jhaveri < sankhesh.jhaveri at kitware.com> wrote: > Dashboard for *Wednesday, November 19 2014 * > > *Dashboard status for Nightly (master) * > > -------------------- ANALYZING -------------------- > Master-Win64-vs9-shared-release > > 1 > fedora-x64-icc-nightlymaster-debug > > 3 > > -------------------- REPORT -------------------- > 4 FAILURES > pv.TestPopOutWidget > > , 1 , ['fedora-x64-icc-nightlymaster-debug'] > pvcs.PropertyLink > > , 1 , ['fedora-x64-icc-nightlymaster-debug'] > pv.XdmfGridAttributes > > , 1 , ['Master-Win64-vs9-shared-release'] > pvcrs.PropertyLink > > , 1 , ['fedora-x64-icc-nightlymaster-debug'] > > *Dashboard status for Nightly (next) * > > -------------------- ANALYZING -------------------- > fedora-x64-icc-nightlynext-release > > 2 > ubuntu-x64-nightlynext > > 1 > > -------------------- REPORT -------------------- > 3 FAILURES > pvcs.PropertyLink > > , 1 , ['fedora-x64-icc-nightlynext-release'] > pvcrs.PropertyLink > > , 1 , ['fedora-x64-icc-nightlynext-release'] > pvcs-collab.CreateDelete > > , 1 , ['ubuntu-x64-nightlynext'] > > * Issues with submitters * > The following expected submitters did not submit: > * KargadMac.kitware * , * Lion-gcc-pvVTK * > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Thu Nov 20 14:40:20 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 20 Nov 2014 14:40:20 -0500 Subject: [Paraview-developers] Dashboard Status: Wednesday, November 19 2014 In-Reply-To: References: <20141120173104.331BF7FF5F@sanganak-ubuntu> Message-ID: <20141120194020.GA14872@megas.kitwarein.com> On Thu, Nov 20, 2014 at 12:34:48 -0500, Yumin Yuan wrote: > Anybody knows an easy way to run ONLY all Paraview UI tests. I am trying out > some changes in QtTesting repo. I assume you mean without VTK's tests? You should be able to run ctest with "-L PARAVIEW" to only run the tests labelled as such (and all of ParaView's tests should be marked with the label). --Ben From yumin.yuan at kitware.com Thu Nov 20 14:45:08 2014 From: yumin.yuan at kitware.com (Yumin Yuan) Date: Thu, 20 Nov 2014 14:45:08 -0500 Subject: [Paraview-developers] Dashboard Status: Wednesday, November 19 2014 In-Reply-To: <20141120194020.GA14872@megas.kitwarein.com> References: <20141120173104.331BF7FF5F@sanganak-ubuntu> <20141120194020.GA14872@megas.kitwarein.com> Message-ID: Thanks, Ben. On Thu, Nov 20, 2014 at 2:40 PM, Ben Boeckel wrote: > On Thu, Nov 20, 2014 at 12:34:48 -0500, Yumin Yuan wrote: > > Anybody knows an easy way to run ONLY all Paraview UI tests. I am trying > out > > some changes in QtTesting repo. > > I assume you mean without VTK's tests? Actually, I meant ParaView's UI tests. Tests that involve Qt UI components. > You should be able to run ctest > with "-L PARAVIEW" to only run the tests labelled as such (and all of > ParaView's tests should be marked with the label). This tip will certainly help. Thanks. Yumin -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Fri Nov 21 12:31:08 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Fri, 21 Nov 2014 09:31:08 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Thursday, November 20 2014 Message-ID: <20141121173104.00F927FF02@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]fedora-x64-icc-nightlymaster-debug 1 [2]ubuntu-x64-nightlymaster-static 1 -------------------- REPORT -------------------- 2 FAILURES [3]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [4]pvcs-collab.SpreadSheet1 , 1 , ['ubuntu-x64-nightlymaster-static'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [5]fedora-x64-icc-nightlynext-release 1 -------------------- REPORT -------------------- 1 FAILURES [6]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] Issues with submitters The following expected submitters did not submit: KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-21&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 2. http://open.cdash.org/index.php?project=ParaView&date=2014-11-21&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-static 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-21&name=pvcs.PropertyLink 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-21&name=pvcs-collab.SpreadSheet1 5. http://open.cdash.org/index.php?project=ParaView&date=2014-11-21&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-21&name=pvcrs.PropertyLink -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Sat Nov 22 12:31:16 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Sat, 22 Nov 2014 09:31:16 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Friday, November 21 2014 Message-ID: <20141122173104.95CD17FF5F@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]ubuntu-x64-nightlymaster-unified 2 [2]fedora-x64-icc-nightlymaster-debug 3 -------------------- REPORT -------------------- 5 FAILURES [3]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [4]pvcs.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlymaster-unified'] [5]pvcs.Contour , 1 , ['ubuntu-x64-nightlymaster-unified'] [6]pvcs-collab.CreateDelete , 1 , ['fedora-x64-icc-nightlymaster-debug'] [7]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [8]ubuntu-x64-nightlynext 1 [9]Win7x64-ninja-nightlynext-shared-release 5 [10]fedora-x64-icc-nightlynext-release 4 -------------------- REPORT -------------------- 8 FAILURES [11]CoProcessingProgrammableFilter , 1 , ['Win7x64-ninja-nightlynext-shared-release'] [12]CoProcessingFullWorkflow , 1 , ['Win7x64-ninja-nightlynext-shared-release'] [13]pvcs-collab.CreateDelete , 1 , ['ubuntu-x64-nightlynext'] [14]CoProcessingImport , 1 , ['Win7x64-ninja-nightlynext-shared-release'] [15]CoProcessingTestPythonScript , 1 , ['Win7x64-ninja-nightlynext-shared-release'] [16]SavePythonState , 1 , ['Win7x64-ninja-nightlynext-shared-release'] [17]pvcrs.PropertyLink , 2 , ['fedora-x64-icc-nightlynext-release', 'fedora-x64-icc-nightlynext-release'] [18]pvcs.PropertyLink , 2 , ['fedora-x64-icc-nightlynext-release', 'fedora-x64-icc-nightlynext-release'] Issues with submitters The following expected submitters did not submit: KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-22&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified 2. http://open.cdash.org/index.php?project=ParaView&date=2014-11-22&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=pvcs.PropertyLink 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=pvcs.ColorOpacityTableEditing 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=pvcs.Contour 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=pvcs-collab.CreateDelete 7. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=pvcrs.PropertyLink 8. http://open.cdash.org/index.php?project=ParaView&date=2014-11-22&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 9. http://open.cdash.org/index.php?project=ParaView&date=2014-11-22&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release 10. http://open.cdash.org/index.php?project=ParaView&date=2014-11-22&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 11. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=CoProcessingProgrammableFilter 12. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=CoProcessingFullWorkflow 13. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=pvcs-collab.CreateDelete 14. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=CoProcessingImport 15. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=CoProcessingTestPythonScript 16. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=SavePythonState 17. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=pvcrs.PropertyLink 18. http://open.cdash.org/testSummary.php?project=9&date=2014-11-22&name=pvcs.PropertyLink -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Sun Nov 23 10:06:30 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 23 Nov 2014 10:06:30 -0500 Subject: [Paraview-developers] How to read time data in custom reader plugin In-Reply-To: <4A9B0002-F0B9-4B28-B578-F7D20C2370C1@aia.rwth-aachen.de> References: <08F52AD6-6DE6-4BC2-80AC-470AA37CB32E@aia.rwth-aachen.de> <4A9B0002-F0B9-4B28-B578-F7D20C2370C1@aia.rwth-aachen.de> Message-ID: Michael, Hard to say. If you could share the code with a sample dataset to reproduce the problem, that'd make it easier to detect the issue. Utkarsh On Thu, Nov 13, 2014 at 11:26 AM, Schlottke, Michael wrote: > Hi Utkarsh, > > Thanks again for your answer. It seems to me that this method only works when using the file series reader. I?ve implemented the time step values property as per your suggestions, and also added a > > outInfo->Set(vtkStreamingDemandDrivenPipeline::TIME_STEPS(), &time, 1); > > line to our RequestInformation method. When opening multiple files using the internal FileSeriesReader, the time value is properly shown. However, when reading only a single file results in always showing ?0? in the simulation time field, although I added the XML code also to the normal (i.e. non-fileseries) reader plugin. > > Any ideas what I might be doing wrong? Or is it possible that showing the simulation time only works through the file series reader? > > Regards, > > Michael > >> On 02 Oct 2014, at 22:10 , Utkarsh Ayachit wrote: >> >> Michael, >> >> I think you may just need a "TimestepValues" property like follows: >> >> > name="TimestepValues" >> repeatable="1"> >> >> Available timestep values. >> >> >> Refer to readers.xml[1] for examples of other readers that do the same. >> >> Utkarsh >> >> [1] https://github.com/Kitware/ParaView/blob/master/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml >> >> On Thu, Oct 2, 2014 at 11:30 AM, Schlottke, Michael >> wrote: >>> Dear Utkarsh, >>> >>> OK, this seems to work! Is there any way I can make this work (display of time) when I read a single file, i.e. bypassing the vtkFileSeriesReader? >>> >>> Michael >>> >>> On 28 Aug 2014, at 17:05 , Utkarsh Ayachit wrote: >>> >>>> What you can do is make your internal reader which is used to read a >>>> timestep put out a correct value for >>>> vtkStreamingDemandDrivenPipeline::TIME_STEPS()/TIME_RANGE() keys in >>>> the outInfo in its RequestInformation(). The vtkFileSeriesReader >>>> iterates over all files in the series to gather that information is >>>> possible ( see vtkFileSeriesReader::RequestInformation). >>>> >>>> Utkarsh >>>> >>>> On Thu, Jul 31, 2014 at 5:45 AM, Schlottke, Michael >>>> wrote: >>>>> Hi folks, >>>>> >>>>> How can I make my custom plugin reader be aware of the simulation time, >>>>> which is stored in the solution files I want to read? Thanks to the >>>>> vtkFileSeriesReader (?) plugin I can already read in a series of files (i.e. >>>>> solution_000*) and traverse through them in the correct order. However, in >>>>> the ?time? field only the time step number is displayed, but not the actual >>>>> simulation time. How can I make ParaView use the correct time? I guess it's >>>>> something I have to add to the ?RequestInformation(..)? method in my reader. >>>>> Is anyone there who has already solved this problem for her/himself? >>>>> >>>>> Thank you very much in advance >>>>> >>>>> Michael >>>>> >>>>> P.S.: I?m sure that this must have been asked here before, but I wasn?t able >>>>> to find anything in the archives. If I missed something I?d greatly >>>>> appreciate a link to the correct thread. >>>>> >>>>> >>>>> -- >>>>> Michael Schlottke >>>>> >>>>> SimLab Highly Scalable Fluids & Solids Engineering >>>>> J?lich Aachen Research Alliance (JARA-HPC) >>>>> RWTH Aachen University >>>>> W?llnerstra?e 5a >>>>> 52062 Aachen >>>>> Germany >>>>> >>>>> Phone: +49 (241) 80 95188 >>>>> Fax: +49 (241) 80 92257 >>>>> Mail: m.schlottke at aia.rwth-aachen.de >>>>> Web: http://www.jara.org/jara-hpc >>>>> >>>>> >>>>> _______________________________________________ >>>>> Paraview-developers mailing list >>>>> Paraview-developers at paraview.org >>>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>>> >>> > From sankhesh.jhaveri at kitware.com Sun Nov 23 12:31:13 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Sun, 23 Nov 2014 09:31:13 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Saturday, November 22 2014 Message-ID: <20141123173103.C3C4380023@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]fedora-x64-icc-nightlymaster-debug 2 -------------------- REPORT -------------------- 2 FAILURES [2]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [3]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [4]fedora-x64-icc-nightlynext-release 2 -------------------- REPORT -------------------- 2 FAILURES [5]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] [6]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK miranda.kitware , Win7x64-ninja-nightlymaster-static-release miranda.kitware , Win7x64-vs9-nightlymaster-shared-release References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-23&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 2. http://open.cdash.org/testSummary.php?project=9&date=2014-11-23&name=pvcs.PropertyLink 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-23&name=pvcrs.PropertyLink 4. http://open.cdash.org/index.php?project=ParaView&date=2014-11-23&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-23&name=pvcs.PropertyLink 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-23&name=pvcrs.PropertyLink -------------- next part -------------- An HTML attachment was scrubbed... URL: From breton at cynicmansion.ru Mon Nov 24 06:17:03 2014 From: breton at cynicmansion.ru (Boris Bobrov) Date: Mon, 24 Nov 2014 14:17:03 +0300 Subject: [Paraview-developers] Paraview architecture Message-ID: <10475F00-9C0E-42CE-821E-FF00389FE2B1@cynicmansion.ru> Hello, I am trying to understand the architecture of paraview and it's dataflow. 1. What kind of rendering happens on client side? What rendering does default paraview client perform? Does it use OpenGL or something? What happens when I drag an image in the client? 2. What kind of data flows between a client, a data server and a rendering server? What's the format? I tried to search the wiki but either I am a bad lurker or it's not there. I am also not sure which mailing list to use, so I'll send this email to both. -- WBR, Boris -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Mon Nov 24 09:10:07 2014 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Mon, 24 Nov 2014 15:10:07 +0100 Subject: [Paraview-developers] Paraview architecture In-Reply-To: <10475F00-9C0E-42CE-821E-FF00389FE2B1@cynicmansion.ru> References: <10475F00-9C0E-42CE-821E-FF00389FE2B1@cynicmansion.ru> Message-ID: Boris, In the 3D View, and depending on the Render View settings, the client may render the geometry (that is the external surface) of the datasets that it receives from the server using OpenGL, or it can receive and display the images (remote rendering) generated by the server. With the first mode, the interaction is performed locally with some VTK graphical pipelines (camera, interactors, rendere, etc.); when the rendering is performed remotely, the client sends the local camera properties to the server so it can generate images from the correct viewpoint. So depending the mode, the raw surface geometry can be transfered or some compressed images (different compression techniques are available, see Settings / Render View panel). Some other views (eg. 2D plots) may have different behaviour and might require the full dataset to be transfered from the server to the client for display/analysis (in this case, this will not scale of course : eg. if you plot a huge UnstructuredGrid within a Line Plot view after applying the Plot Data filter)... Hope it helps, Joachim *Joachim Pouderoux* *PhD, Technical Expert* *Kitware SAS * 2014-11-24 12:17 GMT+01:00 Boris Bobrov : > Hello, > > I am trying to understand the architecture of paraview and it's dataflow. > > 1. What kind of rendering happens on client side? What rendering does > default paraview client perform? Does it use OpenGL or something? What > happens when I drag an image in the client? > > 2. What kind of data flows between a client, a data server and a rendering > server? What's the format? > > I tried to search the wiki but either I am a bad lurker or it's not there. > I am also not sure which mailing list to use, so I'll send this email to > both. > -- > WBR, > Boris > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Mon Nov 24 09:54:32 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 24 Nov 2014 09:54:32 -0500 Subject: [Paraview-developers] [Paraview] Paraview architecture In-Reply-To: References: <10475F00-9C0E-42CE-821E-FF00389FE2B1@cynicmansion.ru> Message-ID: Also see, http://www.paraview.org/Wiki/Representations_and_Views. It is out of date ever since since 3.14's redesign of the rendering architecture so the names of the classes are different but the overall flow is the same. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Nov 24, 2014 at 9:10 AM, Joachim Pouderoux < joachim.pouderoux at kitware.com> wrote: > Boris, > > In the 3D View, and depending on the Render View settings, the client may > render the geometry (that is the external surface) of the datasets that it > receives from the server using OpenGL, or it can receive and display the > images (remote rendering) generated by the server. With the first mode, the > interaction is performed locally with some VTK graphical pipelines (camera, > interactors, rendere, etc.); when the rendering is performed remotely, the > client sends the local camera properties to the server so it can generate > images from the correct viewpoint. > > So depending the mode, the raw surface geometry can be transfered or some > compressed images (different compression techniques are available, see > Settings / Render View panel). > > Some other views (eg. 2D plots) may have different behaviour and might > require the full dataset to be transfered from the server to the client for > display/analysis (in this case, this will not scale of course : eg. if you > plot a huge UnstructuredGrid within a Line Plot view after applying the > Plot Data filter)... > > Hope it helps, > > Joachim > > *Joachim Pouderoux* > > *PhD, Technical Expert* > *Kitware SAS * > > > 2014-11-24 12:17 GMT+01:00 Boris Bobrov : > >> Hello, >> >> I am trying to understand the architecture of paraview and it's dataflow. >> >> 1. What kind of rendering happens on client side? What rendering does >> default paraview client perform? Does it use OpenGL or something? What >> happens when I drag an image in the client? >> >> 2. What kind of data flows between a client, a data server and a >> rendering server? What's the format? >> >> I tried to search the wiki but either I am a bad lurker or it's not >> there. I am also not sure which mailing list to use, so I'll send this >> email to both. >> -- >> WBR, >> Boris >> _______________________________________________ >> Paraview-developers mailing list >> Paraview-developers at paraview.org >> 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Mon Nov 24 12:31:16 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Mon, 24 Nov 2014 09:31:16 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Sunday, November 23 2014 Message-ID: <20141124173103.8A4BB7FF5F@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]fedora-x64-icc-nightlymaster-debug 2 -------------------- REPORT -------------------- 2 FAILURES [2]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [3]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [4]fedora-x64-icc-nightlynext-release 2 -------------------- REPORT -------------------- 2 FAILURES [5]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] [6]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-24&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 2. http://open.cdash.org/testSummary.php?project=9&date=2014-11-24&name=pvcs.PropertyLink 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-24&name=pvcrs.PropertyLink 4. http://open.cdash.org/index.php?project=ParaView&date=2014-11-24&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-24&name=pvcs.PropertyLink 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-24&name=pvcrs.PropertyLink -------------- next part -------------- An HTML attachment was scrubbed... URL: From maxim.glibin at gmail.com Tue Nov 25 06:46:08 2014 From: maxim.glibin at gmail.com (Maxim Glibin) Date: Tue, 25 Nov 2014 14:46:08 +0300 Subject: [Paraview-developers] Modified scalar bar in representation Message-ID: Hello everybody, I need just modify the scalar bar. Is it necessary to create a new representation and add in 3D View or there is another way in order to get or update the scalar bar of representation? I need anyway create my own scalar bar and add to new representation, needn't I? Who have any ideas how to do it? I will be grateful for any help that you can provide. Sincerely, Maxim -------------- next part -------------- An HTML attachment was scrubbed... URL: From maxim.glibin at gmail.com Wed Nov 26 02:38:28 2014 From: maxim.glibin at gmail.com (Maxim Glibin) Date: Wed, 26 Nov 2014 10:38:28 +0300 Subject: [Paraview-developers] Modified scalar bar in representation In-Reply-To: References: Message-ID: I am sorry, this issue is not relevant. It is not necessary for me to create new representation. I need only provide an opportunity to modify scalar bar by using input information of reader. For example, I can add button to section of settings values for display which will be responsible for updating the scalar bar. 2014-11-25 14:46 GMT+03:00 Maxim Glibin : > Hello everybody, > > I need just modify the scalar bar. > Is it necessary to create a new representation and add in 3D View or there > is another way in order to get or update the scalar bar of representation? > I need anyway create my own scalar bar and add to new representation, > needn't I? > Who have any ideas how to do it? > > I will be grateful for any help that you can provide. > > Sincerely, > Maxim > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Wed Nov 26 12:31:07 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Wed, 26 Nov 2014 09:31:07 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Tuesday, November 25 2014 Message-ID: <20141126173104.16EB07FF00@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]ubuntu-x64-nightlymaster-unified 5 -------------------- REPORT -------------------- 5 FAILURES [2]pv.FindWidget , 1 , ['ubuntu-x64-nightlymaster-unified'] [3]pv.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlymaster-unified'] [4]pv.Contour , 1 , ['ubuntu-x64-nightlymaster-unified'] [5]pvcs.ChartAxisRangeAndLabels , 1 , ['ubuntu-x64-nightlymaster-unified'] [6]pvcs.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlymaster-unified'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- -------------------- REPORT -------------------- 0 FAILURES Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified 2. http://open.cdash.org/testSummary.php?project=9&date=2014-11-26&name=pv.FindWidget 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-26&name=pv.ColorOpacityTableEditing 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-26&name=pv.Contour 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-26&name=pvcs.ChartAxisRangeAndLabels 6. http://open.cdash.org/testSummary.php?project=9&date=2014-11-26&name=pvcs.ColorOpacityTableEditing -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Nov 27 11:40:09 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 27 Nov 2014 11:40:09 -0500 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: Topics merged into master (v4.2.0-153-g044be9b): 0015141_add_rotation_factor 0015144_subticks_marks_deactivation 0015146_add_SelectPoints_function_in_pvsimple 15137_fix_label_format 15148_ADIOS_require_MPI (VTK) kdtree-repr qtEvent_player_fix (VTK) update-hdf5 (VTK) vtk_20141122 From sankhesh.jhaveri at kitware.com Thu Nov 27 12:31:07 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Thu, 27 Nov 2014 09:31:07 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Wednesday, November 26 2014 Message-ID: <20141127173103.EFB6780002@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]ubuntu-x64-nightlymaster-unified 3 -------------------- REPORT -------------------- 3 FAILURES [2]pv.FindWidget , 1 , ['ubuntu-x64-nightlymaster-unified'] [3]pv.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlymaster-unified'] [4]pvcs.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlymaster-unified'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [5]Win7x64-vs10-static-release 12 [6]ubuntu-x64-nightlynext 14 [7]ubuntu-x64-nightlynext-static 14 [8]ubuntu-x64-coverage 14 [9]ubuntu-x64-nightlynext 14 [10]Win7x64-vs9-nightlynext-static-release 14 [11]Win7x64-vs10-shared-release 12 [12]Win7x64-ninja-nightlynext-shared-release 14 -------------------- REPORT -------------------- 14 FAILURES [13]pv.CatalystLiveSetBreakpoint , 6 , ['ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-ninja-nightlynext-shared-release'] [14]pvcs.CatalystLiveSetBreakpoint , 6 , ['ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-ninja-nightlynext-shared-release'] [15]pv.SaveColorMap , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [16]pv.ColorOpacityTableEditing , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [17]pvcs.CategoricalColors , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [18]pvcrs.Contour , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [19]pvcs.SaveColorMap , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [20]pv.CategoricalColors , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [21]pvcs.ColorOpacityTableEditing , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [22]pv.Contour , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [23]pvcrs.SaveColorMap , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [24]pvcs.Contour , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [25]pvcrs.CategoricalColors , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] [26]pvcrs.ColorOpacityTableEditing , 8 , ['Win7x64-vs10-static-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster-unified 2. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pv.FindWidget 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pv.ColorOpacityTableEditing 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pvcs.ColorOpacityTableEditing 5. http://open.cdash.org/index.php?project=ParaView&date=2014-11-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 6. http://open.cdash.org/index.php?project=ParaView&date=2014-11-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 7. http://open.cdash.org/index.php?project=ParaView&date=2014-11-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static 8. http://open.cdash.org/index.php?project=ParaView&date=2014-11-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage 9. http://open.cdash.org/index.php?project=ParaView&date=2014-11-27&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 10. http://open.cdash.org/index.php?project=ParaView&date=2014-11-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 11. http://open.cdash.org/index.php?project=ParaView&date=2014-11-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-shared-release 12. http://open.cdash.org/index.php?project=ParaView&date=2014-11-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release 13. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pv.CatalystLiveSetBreakpoint 14. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pvcs.CatalystLiveSetBreakpoint 15. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pv.SaveColorMap 16. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pv.ColorOpacityTableEditing 17. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pvcs.CategoricalColors 18. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pvcrs.Contour 19. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pvcs.SaveColorMap 20. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pv.CategoricalColors 21. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pvcs.ColorOpacityTableEditing 22. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pv.Contour 23. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pvcrs.SaveColorMap 24. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pvcs.Contour 25. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pvcrs.CategoricalColors 26. http://open.cdash.org/testSummary.php?project=9&date=2014-11-27&name=pvcrs.ColorOpacityTableEditing -------------- next part -------------- An HTML attachment was scrubbed... URL: From maxim.glibin at gmail.com Fri Nov 28 04:09:54 2014 From: maxim.glibin at gmail.com (Maxim Glibin) Date: Fri, 28 Nov 2014 12:09:54 +0300 Subject: [Paraview-developers] Example PropertyWidgets Message-ID: Hello everybody, I tried to use plugin from Examples\Plugins\PropertyWidgets. Could anybody explain to me how it works? In fact I need add a custom widget into display setting for certain filter. Is it possible? Best regards, Maxim -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Fri Nov 28 12:31:06 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Fri, 28 Nov 2014 09:31:06 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Thursday, November 27 2014 Message-ID: <20141128173104.834D18084A@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Win7x64-vs10-shared-release 1 -------------------- REPORT -------------------- 1 FAILURES [2]pv.ServerConnectDialog , 1 , ['Win7x64-vs10-shared-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- -------------------- REPORT -------------------- 0 FAILURES Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-28&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-shared-release 2. http://open.cdash.org/testSummary.php?project=9&date=2014-11-28&name=pv.ServerConnectDialog -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Sat Nov 29 12:31:07 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Sat, 29 Nov 2014 09:31:07 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Friday, November 28 2014 Message-ID: <20141129173103.682DB80002@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]fedora-x64-icc-nightlymaster-debug 2 -------------------- REPORT -------------------- 2 FAILURES [2]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [3]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [4]fedora-x64-icc-nightlynext-release 2 -------------------- REPORT -------------------- 1 FAILURES [5]pvcrs.PropertyLink , 2 , ['fedora-x64-icc-nightlynext-release', 'fedora-x64-icc-nightlynext-release'] Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-29&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 2. http://open.cdash.org/testSummary.php?project=9&date=2014-11-29&name=pvcs.PropertyLink 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-29&name=pvcrs.PropertyLink 4. http://open.cdash.org/index.php?project=ParaView&date=2014-11-29&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 5. http://open.cdash.org/testSummary.php?project=9&date=2014-11-29&name=pvcrs.PropertyLink -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Sun Nov 30 12:31:14 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Sun, 30 Nov 2014 09:31:14 -0800 (PST) Subject: [Paraview-developers] Dashboard Status: Saturday, November 29 2014 Message-ID: <20141130173106.1739B7FEE6@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]fedora-x64-icc-nightlymaster-debug 3 -------------------- REPORT -------------------- 3 FAILURES [2]pv.TestPopOutWidget , 1 , ['fedora-x64-icc-nightlymaster-debug'] [3]pvcs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] [4]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlymaster-debug'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [5]ubuntu-x64-nightlynext 1 [6]Win64-vs9-static-release 1 [7]fedora-x64-icc-nightlynext-release 1 -------------------- REPORT -------------------- 3 FAILURES [8]pv.LogColorMap , 1 , ['Win64-vs9-static-release'] [9]pvcrs.PropertyLink , 1 , ['fedora-x64-icc-nightlynext-release'] [10]pvcs-collab.CreateDelete , 1 , ['ubuntu-x64-nightlynext'] Issues with submitters The following expected submitters did not submit: amber12.kitware , Master-Win64-vs9-static-release KargadMac.kitware , Lion-gcc-pvVTK References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-11-30&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 2. http://open.cdash.org/testSummary.php?project=9&date=2014-11-30&name=pv.TestPopOutWidget 3. http://open.cdash.org/testSummary.php?project=9&date=2014-11-30&name=pvcs.PropertyLink 4. http://open.cdash.org/testSummary.php?project=9&date=2014-11-30&name=pvcrs.PropertyLink 5. http://open.cdash.org/index.php?project=ParaView&date=2014-11-30&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 6. http://open.cdash.org/index.php?project=ParaView&date=2014-11-30&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release 7. http://open.cdash.org/index.php?project=ParaView&date=2014-11-30&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 8. http://open.cdash.org/testSummary.php?project=9&date=2014-11-30&name=pv.LogColorMap 9. http://open.cdash.org/testSummary.php?project=9&date=2014-11-30&name=pvcrs.PropertyLink 10. http://open.cdash.org/testSummary.php?project=9&date=2014-11-30&name=pvcs-collab.CreateDelete -------------- next part -------------- An HTML attachment was scrubbed... URL: