From sankhesh.jhaveri at kitware.com Fri Aug 1 12:31:04 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Fri, 1 Aug 2014 12:31:04 -0400 (EDT) Subject: [Paraview-developers] Dashboard Status: Thursday, July 31 2014 Message-ID: <20140801163104.9B5867FF8C@sanganak-ubuntu> An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Sat Aug 2 09:27:01 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 2 Aug 2014 09:27:01 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: SUMMARY --------------------------------------------- Topics merged into master: 14599_fix_double_range_issues 14899_ensure_good_axes_ranges fix_matplot_lib fix_proxy_widget_dialog_apply pvweb-fixes --------------------------------------------- Topics reverted from next: 14813_fix_mode_shapes_range From biddisco at cscs.ch Mon Aug 4 09:05:02 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Mon, 4 Aug 2014 13:05:02 +0000 Subject: [Paraview-developers] IceT compositing in paraview In-Reply-To: Message-ID: Thanks Utkarsh. I got my code running using the modified blend function trick, but now I?ve discovered that it isn?t actually correct as my (their) normalisation uses a nonlinear function, so actually I have to collect all images and then normalise. This means I?m going to either need your suggested tweaks to the synchronised renderers or find a way of adjusting the normalisation to make it commutative Thanks for the information. Very useful as always. JB On 30/07/14 20:45, "Utkarsh Ayachit" wrote: >vtkSynchronizedRenderers From utkarsh.ayachit at kitware.com Mon Aug 4 10:12:53 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 4 Aug 2014 10:12:53 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: SUMMARY --------------------------------------------- Topics merged into master: (VTK) 14279_glyph_filter (VTK) fix_invalid_socket_check From sankhesh.jhaveri at kitware.com Mon Aug 4 16:26:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Mon, 04 Aug 2014 13:26:05 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Sunday, August 03 2014 Message-ID: <20140804202603.2236E7FEE9@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-clang-nightlymaster-release 3 [2]Mac10.7.5-gcc-nightlymaster-release 4 [3]Master-Win64-vs9-static-release 1 [4]Win7x64-ninja-nightlymaster-static-release 3 -------------------- REPORT -------------------- 8 FAILURES [5]pv.OpenHelp , 1 , ['Master-Win64-vs9-static-release'] [6]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [7]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [8]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [9]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [10]pqWidgetspqTextEditTest , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [11]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [12]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [13]Lion-gcc-pvVTK 2 [14]Win7x64-vs9-nightlynext-static-release 4 [15]Win64-vs9-static-release 1 -------------------- REPORT -------------------- 6 FAILURES [16]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [17]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [18]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [19]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 1 , ['Lion-gcc-pvVTK'] [20]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [21]pv.OpenHelp , 2 , ['Win7x64-vs9-nightlynext-static-release', 'Win64-vs9-static-release'] References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-04&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-08-04&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-08-04&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-static-release 4. http://open.cdash.org/index.php?project=ParaView&date=2014-08-04&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 5. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=pv.OpenHelp 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=SurfaceLIC-ShuttleZoom2-Batch 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=SurfaceLIC-ShuttleZoom1-Batch 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=SurfaceLIC-ShuttleAll-Batch 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=pqWidgetspqTextEditTest 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 13. http://open.cdash.org/index.php?project=ParaView&date=2014-08-04&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 14. http://open.cdash.org/index.php?project=ParaView&date=2014-08-04&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 15. http://open.cdash.org/index.php?project=ParaView&date=2014-08-04&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=SurfaceLIC-ShuttleZoom2-Batch 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=SurfaceLIC-ShuttleZoom1-Batch 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=SurfaceLIC-ShuttleAll-Batch 19. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 20. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 21. http://open.cdash.org/testSummary.php?project=9&date=2014-08-04&name=pv.OpenHelp -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Aug 5 08:35:36 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 5 Aug 2014 08:35:36 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: SUMMARY --------------------------------------------- Topics merged into master: remove_obsolete_panels rms-plots --------------------------------------------- Topics reverted from next: live-breakpoint static-numpy From sankhesh.jhaveri at kitware.com Tue Aug 5 14:04:18 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Tue, 05 Aug 2014 11:04:18 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Monday, August 04 2014 Message-ID: <20140805180416.CAF3E7FFB8@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-clang-nightlymaster-release 3 [2]Win7x64-ninja-nightlymaster-static-release 3 [3]Mac10.7.5-gcc-nightlymaster-release 3 [4]Master-Win64-vs9-shared-release 1 -------------------- REPORT -------------------- 7 FAILURES [5]pv.OpenHelp , 1 , ['Master-Win64-vs9-shared-release'] [6]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [7]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [8]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [9]pqWidgetspqTextEditTest , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [10]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [11]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [12]Lion-gcc-pvVTK 4 [13]Win64-vs9-shared-debug-nocollab 2 [14]Win32-vs9-shared-release 2 -------------------- REPORT -------------------- 4 FAILURES [15]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 1 , ['Lion-gcc-pvVTK'] [16]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [17]pv.CatalystLiveSetBreakpoint , 3 , ['Lion-gcc-pvVTK', 'Win64-vs9-shared-debug-nocollab', 'Win32-vs9-shared-release'] [18]pvcs.CatalystLiveSetBreakpoint , 3 , ['Lion-gcc-pvVTK', 'Win64-vs9-shared-debug-nocollab', 'Win32-vs9-shared-release'] References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-05&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-08-05&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 3. http://open.cdash.org/index.php?project=ParaView&date=2014-08-05&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-08-05&filtercount=1&field1=buildname/string&compare1=61&value1=Master-Win64-vs9-shared-release 5. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=pv.OpenHelp 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=SurfaceLIC-ShuttleZoom2-Batch 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=SurfaceLIC-ShuttleZoom1-Batch 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=SurfaceLIC-ShuttleAll-Batch 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=pqWidgetspqTextEditTest 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 12. http://open.cdash.org/index.php?project=ParaView&date=2014-08-05&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 13. http://open.cdash.org/index.php?project=ParaView&date=2014-08-05&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab 14. http://open.cdash.org/index.php?project=ParaView&date=2014-08-05&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=pv.CatalystLiveSetBreakpoint 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-05&name=pvcs.CatalystLiveSetBreakpoint -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Thu Aug 7 12:31:08 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Thu, 07 Aug 2014 09:31:08 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Wednesday, August 06 2014 Message-ID: <20140807163104.054E47FF1F@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-clang-nightlymaster-release 4 [2]Win7x64-ninja-nightlymaster-static-release 3 [3]Win7x64-vs10-static-release 1 [4]Win7x64-vs10-shared-release 1 [5]Mac10.7.5-gcc-nightlymaster-release 4 [6]fedora-x64-icc-nightlymaster-debug 9 -------------------- REPORT -------------------- 17 FAILURES [7]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [9]pvcs-collab.VariableSelector , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [10]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [11]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [12]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [13]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [14]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [15]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [16]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [17]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [18]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [19]pvcrs.ExportX3dPOVVRML , 1 , ['Mac10.7.5-clang-nightlymaster-release'] [20]pv.OpenHelp , 2 , ['Win7x64-vs10-static-release', 'Win7x64-vs10-shared-release'] [21]pqWidgetspqTextEditTest , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [22]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [23]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 3 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'fedora-x64-icc-nightlymaster-debug'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [24]Win64-vs9-shared-debug-nocollab 2 [25]fedora-x64-icc-nightlynext-release 13 [26]Lion-gcc-pvVTK 4 [27]Win7x64-ninja-nightlynext-shared-release 2 [28]ubuntu-x64-nightlynext 2 [29]ubuntu-x64-nightlynext-nogui 2 [30]Win32-vs9-shared-release 3 [31]Win7x64-vs10-static-release 1 [32]ubuntu-x64-nightlynext-static 3 [33]ubuntu-x64-nightlynext 3 [34]ubuntu-x64-coverage 4 [35]Win7x64-vs9-nightlynext-static-release 5 -------------------- REPORT -------------------- 23 FAILURES [36]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [37]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [38]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [39]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [40]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [41]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [42]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [43]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [44]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [45]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [46]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [47]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [48]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [49]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [50]pvcs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [51]pvcs.CatalystLiveSetBreakpoint , 2 , ['ubuntu-x64-nightlynext', 'ubuntu-x64-coverage'] [52]pv.CatalystGUI-static , 2 , ['ubuntu-x64-nightlynext-static', 'Win7x64-vs9-nightlynext-static-release'] [53]pv.OpenHelp , 2 , ['Win32-vs9-shared-release', 'Win7x64-vs10-static-release'] [54]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['fedora-x64-icc-nightlynext-release', 'Lion-gcc-pvVTK'] [55]pvweb-chrome.TestApp-all , 4 , ['ubuntu-x64-nightlynext-nogui', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-nightlynext', 'ubuntu-x64-coverage'] [56]pvweb-firefox.TestApp-all , 4 , ['ubuntu-x64-nightlynext-nogui', 'ubuntu-x64-nightlynext-static', 'ubuntu-x64-nightlynext', 'ubuntu-x64-coverage'] [57]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 5 , ['Win64-vs9-shared-debug-nocollab', 'Lion-gcc-pvVTK', 'Win7x64-ninja-nightlynext-shared-release', 'Win32-vs9-shared-release', 'Win7x64-vs9-nightlynext-static-release'] [58]CoProcessingFullWorkflow , 8 , ['Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'Lion-gcc-pvVTK', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win32-vs9-shared-release', 'ubuntu-x64-nightlynext', 'ubuntu-x64-coverage'] References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&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-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 3. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 4. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-shared-release 5. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release 6. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs.ProbePicking 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcrs.LoadStateMultiView 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs-collab.VariableSelector 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pv.LoadStateMultiView 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs.TestPythonView 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=SurfaceLIC-ShuttleZoom2-Batch 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pv.TestPythonView 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=SurfaceLIC-ShuttleZoom1-Batch 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcrs.TestPythonView 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=SurfaceLIC-ShuttleAll-Batch 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pv.ProbePicking 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs.LoadStateMultiView 19. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcrs.ExportX3dPOVVRML 20. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pv.OpenHelp 21. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pqWidgetspqTextEditTest 22. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 23. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 24. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab 25. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 26. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 27. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release 28. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 29. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui 30. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 31. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 32. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static 33. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 34. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage 35. http://open.cdash.org/index.php?project=ParaView&date=2014-08-07&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 36. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcrs.UndoRedo1 37. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pv.ProbePicking 38. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 39. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs.LoadStateMultiView 40. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pv.LoadStateMultiView 41. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=SurfaceLIC-ShuttleZoom2-Batch 42. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs.ProbePicking 43. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcrs.LoadStateMultiView 44. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pv.UndoRedo1 45. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcrs.TestPythonView 46. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pv.TestPythonView 47. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=SurfaceLIC-ShuttleZoom1-Batch 48. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs.TestPythonView 49. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=SurfaceLIC-ShuttleAll-Batch 50. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs.UndoRedo1 51. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs.CatalystLiveSetBreakpoint 52. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pv.CatalystGUI-static 53. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pv.OpenHelp 54. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 55. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvweb-chrome.TestApp-all 56. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=pvweb-firefox.TestApp-all 57. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks 58. http://open.cdash.org/testSummary.php?project=9&date=2014-08-07&name=CoProcessingFullWorkflow -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Fri Aug 8 12:31:06 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Fri, 08 Aug 2014 09:31:06 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Thursday, August 07 2014 Message-ID: <20140808163104.4E8087FEC7@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Win7x64-ninja-nightlymaster-static-release 3 [2]Mac10.7.5-gcc-nightlymaster-release 3 [3]fedora-x64-icc-nightlymaster-debug 9 [4]Mac10.7.5-clang-nightlymaster-release 3 [5]Win7x64-vs10-static-release 1 -------------------- REPORT -------------------- 15 FAILURES [6]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [7]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [9]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [10]pv.ServerConnectDialog , 1 , ['Win7x64-vs10-static-release'] [11]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [12]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [13]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [14]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [15]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [16]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [17]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [18]pqWidgetspqTextEditTest , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [19]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [20]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 3 , ['Mac10.7.5-gcc-nightlymaster-release', 'fedora-x64-icc-nightlymaster-debug', 'Mac10.7.5-clang-nightlymaster-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [21]ubuntu-x64-nightlynext 1 [22]ubuntu-x64-nightlynext-static 1 [23]ubuntu-x64-nightlynext 1 [24]Win64-vs9-static-release 1 [25]Win32-vs9-shared-release 2 [26]Win64-vs9-shared-debug-nocollab 5 [27]Win7x64-vs9-nightlynext-static-release 7 [28]ubuntu-x64-coverage 3 [29]Lion-gcc-pvVTK 4 [30]fedora-x64-icc-nightlynext-release 13 [31]Win7x64-ninja-nightlynext-shared-release 4 -------------------- REPORT -------------------- 23 FAILURES [32]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [33]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [34]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [35]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [36]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [37]pqWidgetspqTextEditTest , 1 , ['Win64-vs9-static-release'] [38]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [39]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [40]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [41]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [42]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [43]pv.OpenHelp , 1 , ['Win64-vs9-shared-debug-nocollab'] [44]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [45]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [46]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [47]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [48]pvcs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [49]pv.CatalystGUI-static , 2 , ['ubuntu-x64-nightlynext-static', 'Win7x64-vs9-nightlynext-static-release'] [50]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['Lion-gcc-pvVTK', 'fedora-x64-icc-nightlynext-release'] [51]pvcs.CatalystLiveSetBreakpoint , 4 , ['Win64-vs9-shared-debug-nocollab', 'Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'Win7x64-ninja-nightlynext-shared-release'] [52]pv.CatalystLiveSetBreakpoint , 4 , ['Win64-vs9-shared-debug-nocollab', 'Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'Win7x64-ninja-nightlynext-shared-release'] [53]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 5 , ['Win32-vs9-shared-release', 'Win64-vs9-shared-debug-nocollab', 'Win7x64-vs9-nightlynext-static-release', 'Lion-gcc-pvVTK', 'Win7x64-ninja-nightlynext-shared-release'] [54]CoProcessingFullWorkflow , 8 , ['ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext', 'Win32-vs9-shared-release', 'Win64-vs9-shared-debug-nocollab', 'ubuntu-x64-coverage', 'Lion-gcc-pvVTK', 'fedora-x64-icc-nightlynext-release', 'Win7x64-ninja-nightlynext-shared-release'] References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&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-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 4. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release 5. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs.ProbePicking 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcrs.TestPythonView 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.LoadStateMultiView 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs.TestPythonView 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.ServerConnectDialog 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=SurfaceLIC-ShuttleZoom2-Batch 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.TestPythonView 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=SurfaceLIC-ShuttleZoom1-Batch 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcrs.LoadStateMultiView 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=SurfaceLIC-ShuttleAll-Batch 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.ProbePicking 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs.LoadStateMultiView 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pqWidgetspqTextEditTest 19. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 20. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 21. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 22. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static 23. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 24. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release 25. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 26. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab 27. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 28. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage 29. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 30. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 31. http://open.cdash.org/index.php?project=ParaView&date=2014-08-08&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release 32. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcrs.UndoRedo1 33. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=SurfaceLIC-ShuttleAll-Batch 34. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 35. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs.LoadStateMultiView 36. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.LoadStateMultiView 37. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pqWidgetspqTextEditTest 38. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=SurfaceLIC-ShuttleZoom2-Batch 39. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs.ProbePicking 40. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcrs.LoadStateMultiView 41. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.UndoRedo1 42. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcrs.TestPythonView 43. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.OpenHelp 44. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.TestPythonView 45. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=SurfaceLIC-ShuttleZoom1-Batch 46. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs.TestPythonView 47. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.ProbePicking 48. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs.UndoRedo1 49. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.CatalystGUI-static 50. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 51. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pvcs.CatalystLiveSetBreakpoint 52. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=pv.CatalystLiveSetBreakpoint 53. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks 54. http://open.cdash.org/testSummary.php?project=9&date=2014-08-08&name=CoProcessingFullWorkflow -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Tue Aug 12 12:31:07 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Tue, 12 Aug 2014 09:31:07 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Monday, August 11 2014 Message-ID: <20140812163103.C6DFB80247@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 3 [4]Win7x64-ninja-nightlymaster-static-release 3 [5]fedora-x64-icc-nightlymaster-debug 9 -------------------- REPORT -------------------- 16 FAILURES [6]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [7]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [9]pv.OpenHelp , 1 , ['Win7x64-vs10-static-release'] [10]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [11]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [12]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [13]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [14]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [15]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [16]pvcrs.TensorGlyph , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [17]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [18]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [19]pqWidgetspqTextEditTest , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [20]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [21]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 3 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release', 'fedora-x64-icc-nightlymaster-debug'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [22]Win64-vs9-static-release 1 [23]ubuntu-x64-nightlynext-nogui 8 [24]Win7x64-vs9-nightlynext-static-release 18 [25]ubuntu-x64-coverage 21 [26]ubuntu-x64-nightlynext 21 [27]Win7x64-ninja-nightlynext-shared-release 17 [28]ubuntu-x64-nightlynext 20 [29]Win64-vs9-shared-debug-nocollab 18 [30]fedora-x64-icc-nightlynext-release 31 [31]ubuntu-x64-nightlynext-static 19 [32]Lion-gcc-pvVTK 22 [33]Win32-vs9-shared-release 18 -------------------- REPORT -------------------- 40 FAILURES [34]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [35]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [36]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [37]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [38]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [39]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [40]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [41]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [42]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [43]pv.CameraLink , 1 , ['ubuntu-x64-nightlynext'] [44]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [45]pv.OpenHelp , 1 , ['Win64-vs9-static-release'] [46]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [47]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [48]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [49]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [50]pvcs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [51]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['fedora-x64-icc-nightlynext-release', 'Lion-gcc-pvVTK'] [52]pvweb-chrome.TestApp-all , 4 , ['ubuntu-x64-nightlynext-nogui', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static'] [53]pvweb-firefox.TestApp-all , 4 , ['ubuntu-x64-nightlynext-nogui', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext-static'] [54]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 5 , ['Win7x64-vs9-nightlynext-static-release', 'Win7x64-ninja-nightlynext-shared-release', 'Win64-vs9-shared-debug-nocollab', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [55]pvcs.CatalystLiveSetBreakpoint , 6 , ['ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK'] [56]pv.CatalystLiveSetBreakpoint , 6 , ['ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK'] [57]CoProcessingFullWorkflow , 8 , ['ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [58]SavePythonState , 8 , ['ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [59]PCoProcessingTestPythonScript , 9 , ['ubuntu-x64-nightlynext-nogui', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [60]pvcrs.TraceSaveGeometry , 10 , ['Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [61]pv.TraceExodus , 10 , ['Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [62]pvcs.TraceSaveGeometry , 10 , ['Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [63]pvcs.TraceExodus , 10 , ['Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [64]pv.TraceMultiViews , 10 , ['Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [65]pv.TraceSaveGeometry , 10 , ['Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [66]pvcrs.TraceMultiViews , 10 , ['Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [67]pvcrs.TraceExodus , 10 , ['Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [68]pvcs.TraceMultiViews , 10 , ['Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [69]vtkPVServerManagerDefaultPython-PythonPVLookupTables , 11 , ['ubuntu-x64-nightlynext-nogui', 'Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [70]CoProcessingTestPythonScript , 11 , ['ubuntu-x64-nightlynext-nogui', 'Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [71]vtkPVServerManagerDefaultPython-ValidateSources , 11 , ['ubuntu-x64-nightlynext-nogui', 'Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [72]vtkPVServerManagerDefaultPython-PythonSMTraceTest1 , 11 , ['ubuntu-x64-nightlynext-nogui', 'Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-release'] [73]vtkPVServerManagerDefaultPython-PythonSMTraceTest2 , 11 , ['ubuntu-x64-nightlynext-nogui', 'Win7x64-vs9-nightlynext-static-release', 'ubuntu-x64-coverage', 'ubuntu-x64-nightlynext', 'Win7x64-ninja-nightlynext-shared-release', 'ubuntu-x64-nightlynext', 'Win64-vs9-shared-debug-nocollab', 'fedora-x64-icc-nightlynext-release', 'ubuntu-x64-nightlynext-static', 'Lion-gcc-pvVTK', 'Win32-vs9-shared-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-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&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-08-12&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-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 5. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.ProbePicking 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcrs.TestPythonView 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.LoadStateMultiView 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.OpenHelp 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.TestPythonView 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=SurfaceLIC-ShuttleZoom2-Batch 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.TestPythonView 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=SurfaceLIC-ShuttleZoom1-Batch 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcrs.LoadStateMultiView 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=SurfaceLIC-ShuttleAll-Batch 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcrs.TensorGlyph 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.ProbePicking 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.LoadStateMultiView 19. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pqWidgetspqTextEditTest 20. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 21. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 22. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release 23. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui 24. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 25. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage 26. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 27. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release 28. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 29. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab 30. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 31. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-static 32. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 33. http://open.cdash.org/index.php?project=ParaView&date=2014-08-12&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 34. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcrs.UndoRedo1 35. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=SurfaceLIC-ShuttleAll-Batch 36. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 37. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.LoadStateMultiView 38. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.LoadStateMultiView 39. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=SurfaceLIC-ShuttleZoom2-Batch 40. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.ProbePicking 41. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcrs.LoadStateMultiView 42. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.UndoRedo1 43. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.CameraLink 44. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcrs.TestPythonView 45. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.OpenHelp 46. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.TestPythonView 47. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=SurfaceLIC-ShuttleZoom1-Batch 48. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.TestPythonView 49. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.ProbePicking 50. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.UndoRedo1 51. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 52. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvweb-chrome.TestApp-all 53. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvweb-firefox.TestApp-all 54. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks 55. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.CatalystLiveSetBreakpoint 56. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.CatalystLiveSetBreakpoint 57. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=CoProcessingFullWorkflow 58. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=SavePythonState 59. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=PCoProcessingTestPythonScript 60. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcrs.TraceSaveGeometry 61. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.TraceExodus 62. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.TraceSaveGeometry 63. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.TraceExodus 64. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.TraceMultiViews 65. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pv.TraceSaveGeometry 66. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcrs.TraceMultiViews 67. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcrs.TraceExodus 68. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=pvcs.TraceMultiViews 69. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=vtkPVServerManagerDefaultPython-PythonPVLookupTables 70. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=CoProcessingTestPythonScript 71. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=vtkPVServerManagerDefaultPython-ValidateSources 72. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=vtkPVServerManagerDefaultPython-PythonSMTraceTest1 73. http://open.cdash.org/testSummary.php?project=9&date=2014-08-12&name=vtkPVServerManagerDefaultPython-PythonSMTraceTest2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 13 10:23:04 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Aug 2014 10:23:04 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: Topics merged into master: 14894-fix-vgl-renderer (VTK) 14913_fix_widget_enabled_state 14918_fix_color_palette_restore (VTK) autobahn-update-http-endpoints fix-extras-catalyst-patch lazy_update_enabled_filters mpas-changes (VTK) newest-xdmf pvweb-update-to-generic-decorators pvweb-visualizer-busy-until-connected quieter-cuda-discovery remove_analyze rename-coproc-script-gen scalar-reset-button static-numpy transparent-png-views ui_fixes From sankhesh.jhaveri at kitware.com Wed Aug 13 12:31:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Wed, 13 Aug 2014 09:31:05 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Tuesday, August 12 2014 Message-ID: <20140813163103.7447080118@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-clang-nightlymaster-release 4 [2]Win7x64-ninja-nightlymaster-static-release 3 [3]fedora-x64-icc-nightlymaster-debug 10 [4]Mac10.7.5-gcc-nightlymaster-release 3 -------------------- REPORT -------------------- 16 FAILURES [5]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [6]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [7]pv.ServerConnectDialog , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [9]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [10]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [11]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [12]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [13]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter , 1 , ['Mac10.7.5-clang-nightlymaster-release'] [14]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [15]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [16]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [17]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [18]pqWidgetspqTextEditTest , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [19]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [20]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 3 , ['Mac10.7.5-clang-nightlymaster-release', 'fedora-x64-icc-nightlymaster-debug', 'Mac10.7.5-gcc-nightlymaster-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [21]Win7x64-ninja-nightlynext-shared-release 1 [22]Win7x64-vs10-static-release 1 [23]Win64-vs9-static-release 1 [24]Lion-gcc-pvVTK 4 [25]fedora-x64-icc-nightlynext-release 12 [26]Win7x64-vs9-nightlynext-static-release 5 [27]Win32-vs9-shared-release 1 [28]Win64-vs9-shared-debug-nocollab 1 -------------------- REPORT -------------------- 19 FAILURES [29]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [30]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [31]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [32]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [33]pv.ServerConnectDialog , 1 , ['Lion-gcc-pvVTK'] [34]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [35]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [36]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [37]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [38]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [39]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [40]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [41]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [42]pvcs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [43]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [44]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [45]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['Lion-gcc-pvVTK', 'fedora-x64-icc-nightlynext-release'] [46]pv.OpenHelp , 3 , ['Win7x64-vs10-static-release', 'Win64-vs9-static-release', 'Win7x64-vs9-nightlynext-static-release'] [47]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 5 , ['Win7x64-ninja-nightlynext-shared-release', 'Lion-gcc-pvVTK', 'Win7x64-vs9-nightlynext-static-release', 'Win32-vs9-shared-release', 'Win64-vs9-shared-debug-nocollab'] References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&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-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 3. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 4. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-gcc-nightlymaster-release 5. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs.ProbePicking 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcrs.LoadStateMultiView 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pv.ServerConnectDialog 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pv.LoadStateMultiView 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs.TestPythonView 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=SurfaceLIC-ShuttleZoom2-Batch 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pv.TestPythonView 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=SurfaceLIC-ShuttleZoom1-Batch 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcrs.TestPythonView 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=SurfaceLIC-ShuttleAll-Batch 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pv.ProbePicking 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs.LoadStateMultiView 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pqWidgetspqTextEditTest 19. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 20. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 21. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release 22. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 23. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release 24. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 25. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 26. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 27. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 28. http://open.cdash.org/index.php?project=ParaView&date=2014-08-13&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab 29. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs.ProbePicking 30. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcrs.TestPythonView 31. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pv.LoadStateMultiView 32. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=SurfaceLIC-ShuttleZoom2-Batch 33. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pv.ServerConnectDialog 34. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcrs.UndoRedo1 35. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pv.TestPythonView 36. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=SurfaceLIC-ShuttleZoom1-Batch 37. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcrs.LoadStateMultiView 38. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pv.ProbePicking 39. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 40. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pv.UndoRedo1 41. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs.TestPythonView 42. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs.UndoRedo1 43. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs.LoadStateMultiView 44. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=SurfaceLIC-ShuttleAll-Batch 45. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 46. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=pv.OpenHelp 47. http://open.cdash.org/testSummary.php?project=9&date=2014-08-13&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Thu Aug 14 12:31:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Thu, 14 Aug 2014 09:31:05 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Wednesday, August 13 2014 Message-ID: <20140814163104.2765B7FECA@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-gcc-nightlymaster-release 6 [2]Win7x64-ninja-nightlymaster-static-release 5 [3]fedora-x64-icc-nightlymaster-debug 9 [4]Win7x64-vs9-nightlymaster-shared-release 1 [5]Win7x64-vs10-static-release 1 [6]Mac10.7.5-clang-nightlymaster-release 4 -------------------- REPORT -------------------- 18 FAILURES [7]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [9]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [10]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [11]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [12]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [13]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [14]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [15]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [16]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [17]pvcrs.TensorGlyph , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [18]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [19]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [20]pv.OpenHelp , 2 , ['Win7x64-ninja-nightlymaster-static-release', 'Win7x64-vs10-static-release'] [21]pqWidgetspqTextEditTest , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [22]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [23]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 3 , ['Mac10.7.5-gcc-nightlymaster-release', 'fedora-x64-icc-nightlymaster-debug', 'Mac10.7.5-clang-nightlymaster-release'] [24]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 4 , ['Mac10.7.5-gcc-nightlymaster-release', 'Win7x64-ninja-nightlymaster-static-release', 'Win7x64-vs9-nightlymaster-shared-release', 'Mac10.7.5-clang-nightlymaster-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [25]ubuntu-x64-coverage 1 [26]Win7x64-vs9-nightlynext-static-release 8 [27]Win7x64-vs10-shared-release 3 [28]Win32-vs9-shared-release 4 [29]fedora-x64-icc-nightlynext-release 12 [30]ubuntu-x64-nightlynext 2 [31]Win7x64-ninja-nightlynext-shared-release 5 [32]Win7x64-vs10-static-release 3 [33]Win64-vs9-static-release 4 [34]Win64-vs9-shared-debug-nocollab 4 [35]Lion-gcc-pvVTK 3 -------------------- REPORT -------------------- 23 FAILURES [36]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [37]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [38]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [39]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [40]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [41]pvcs-collab.CreateDelete , 1 , ['ubuntu-x64-nightlynext'] [42]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [43]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [44]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [45]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [46]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [47]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [48]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [49]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [50]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [51]pvcs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [52]pvcs.CatalystLiveSetBreakpoint , 2 , ['ubuntu-x64-coverage', 'ubuntu-x64-nightlynext'] [53]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['fedora-x64-icc-nightlynext-release', 'Lion-gcc-pvVTK'] [54]pv.OpenHelp , 3 , ['Win7x64-vs9-nightlynext-static-release', 'Win7x64-ninja-nightlynext-shared-release', 'Win64-vs9-static-release'] [55]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 5 , ['Win7x64-vs9-nightlynext-static-release', 'Win32-vs9-shared-release', 'Win7x64-ninja-nightlynext-shared-release', 'Win64-vs9-shared-debug-nocollab', 'Lion-gcc-pvVTK'] [56]pv.SaveColorMap , 7 , ['Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win32-vs9-shared-release', 'Win7x64-ninja-nightlynext-shared-release', 'Win7x64-vs10-static-release', 'Win64-vs9-static-release', 'Win64-vs9-shared-debug-nocollab'] [57]pvcrs.SaveColorMap , 7 , ['Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win32-vs9-shared-release', 'Win7x64-ninja-nightlynext-shared-release', 'Win7x64-vs10-static-release', 'Win64-vs9-static-release', 'Win64-vs9-shared-debug-nocollab'] [58]pvcs.SaveColorMap , 7 , ['Win7x64-vs9-nightlynext-static-release', 'Win7x64-vs10-shared-release', 'Win32-vs9-shared-release', 'Win7x64-ninja-nightlynext-shared-release', 'Win7x64-vs10-static-release', 'Win64-vs9-static-release', 'Win64-vs9-shared-debug-nocollab'] References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-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-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 3. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 4. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release 5. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 6. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs.ProbePicking 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcrs.TestPythonView 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pv.LoadStateMultiView 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs.TestPythonView 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=SurfaceLIC-ShuttleZoom2-Batch 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pv.TestPythonView 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=SurfaceLIC-ShuttleZoom1-Batch 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcrs.LoadStateMultiView 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=SurfaceLIC-ShuttleAll-Batch 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcrs.TensorGlyph 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pv.ProbePicking 19. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs.LoadStateMultiView 20. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pv.OpenHelp 21. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pqWidgetspqTextEditTest 22. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 23. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 24. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks 25. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage 26. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 27. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-shared-release 28. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 29. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 30. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 31. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release 32. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 33. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release 34. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab 35. http://open.cdash.org/index.php?project=ParaView&date=2014-08-14&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 36. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcrs.UndoRedo1 37. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=SurfaceLIC-ShuttleAll-Batch 38. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 39. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs.LoadStateMultiView 40. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pv.LoadStateMultiView 41. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs-collab.CreateDelete 42. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=SurfaceLIC-ShuttleZoom2-Batch 43. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs.ProbePicking 44. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcrs.LoadStateMultiView 45. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pv.UndoRedo1 46. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcrs.TestPythonView 47. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pv.TestPythonView 48. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=SurfaceLIC-ShuttleZoom1-Batch 49. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs.TestPythonView 50. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pv.ProbePicking 51. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs.UndoRedo1 52. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs.CatalystLiveSetBreakpoint 53. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 54. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pv.OpenHelp 55. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks 56. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pv.SaveColorMap 57. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcrs.SaveColorMap 58. http://open.cdash.org/testSummary.php?project=9&date=2014-08-14&name=pvcs.SaveColorMap -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Aug 15 10:49:19 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 15 Aug 2014 10:49:19 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: --------------------------------------------- Topics merged into master: 14901_fix_transfer_function_settings_labels 14922_fix_python_from_install 14928_add_catalyst_label_to_test fix_parallel_tests live-breakpoint pvweb-dev-doc start_counting_from_1 From sankhesh.jhaveri at kitware.com Fri Aug 15 12:31:08 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Fri, 15 Aug 2014 09:31:08 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Thursday, August 14 2014 Message-ID: <20140815163104.0F1E07FF00@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-clang-nightlymaster-release 4 [2]Win7x64-ninja-nightlymaster-static-release 5 [3]Mac10.7.5-gcc-nightlymaster-release 5 [4]fedora-x64-icc-nightlymaster-debug 9 [5]Win7x64-vs9-nightlymaster-shared-release 1 -------------------- REPORT -------------------- 17 FAILURES [6]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [7]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]pvcrs.SaveLargeScreenshot , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [9]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [10]pv.OpenHelp , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [11]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [12]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [13]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [14]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [15]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [16]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [17]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [18]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [19]pqWidgetspqTextEditTest , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [20]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [21]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 3 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'fedora-x64-icc-nightlymaster-debug'] [22]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 4 , ['Mac10.7.5-clang-nightlymaster-release', 'Win7x64-ninja-nightlymaster-static-release', 'Mac10.7.5-gcc-nightlymaster-release', 'Win7x64-vs9-nightlymaster-shared-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [23]Win7x64-vs9-nightlynext-static-release 4 [24]Win32-vs9-shared-release 2 [25]Win64-vs9-shared-debug-nocollab 1 [26]Lion-gcc-pvVTK 5 [27]fedora-x64-icc-nightlynext-release 12 [28]Win7x64-ninja-nightlynext-shared-release 1 -------------------- REPORT -------------------- 20 FAILURES [29]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [30]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [31]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [32]pv.OpenHelp , 1 , ['Win32-vs9-shared-release'] [33]pvcs.CatalystLiveSetBreakpoint , 1 , ['Lion-gcc-pvVTK'] [34]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [35]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [36]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [37]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [38]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [39]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [40]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [41]pv.CatalystLiveSetBreakpoint , 1 , ['Lion-gcc-pvVTK'] [42]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [43]pvcs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [44]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [45]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [46]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [47]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['Lion-gcc-pvVTK', 'fedora-x64-icc-nightlynext-release'] [48]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 5 , ['Win7x64-vs9-nightlynext-static-release', 'Win32-vs9-shared-release', 'Win64-vs9-shared-debug-nocollab', 'Lion-gcc-pvVTK', 'Win7x64-ninja-nightlynext-shared-release'] References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-15&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-08-15&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 3. http://open.cdash.org/index.php?project=ParaView&date=2014-08-15&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-08-15&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 5. http://open.cdash.org/index.php?project=ParaView&date=2014-08-15&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs.ProbePicking 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcrs.LoadStateMultiView 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcrs.SaveLargeScreenshot 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pv.LoadStateMultiView 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pv.OpenHelp 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs.TestPythonView 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=SurfaceLIC-ShuttleZoom2-Batch 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pv.TestPythonView 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=SurfaceLIC-ShuttleZoom1-Batch 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcrs.TestPythonView 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=SurfaceLIC-ShuttleAll-Batch 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pv.ProbePicking 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs.LoadStateMultiView 19. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pqWidgetspqTextEditTest 20. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 21. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 22. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks 23. http://open.cdash.org/index.php?project=ParaView&date=2014-08-15&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 24. http://open.cdash.org/index.php?project=ParaView&date=2014-08-15&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 25. http://open.cdash.org/index.php?project=ParaView&date=2014-08-15&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab 26. http://open.cdash.org/index.php?project=ParaView&date=2014-08-15&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 27. http://open.cdash.org/index.php?project=ParaView&date=2014-08-15&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 28. http://open.cdash.org/index.php?project=ParaView&date=2014-08-15&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release 29. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs.ProbePicking 30. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcrs.TestPythonView 31. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pv.LoadStateMultiView 32. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pv.OpenHelp 33. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs.CatalystLiveSetBreakpoint 34. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs.TestPythonView 35. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=SurfaceLIC-ShuttleZoom2-Batch 36. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pv.TestPythonView 37. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=SurfaceLIC-ShuttleZoom1-Batch 38. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcrs.LoadStateMultiView 39. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=SurfaceLIC-ShuttleAll-Batch 40. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pv.UndoRedo1 41. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pv.CatalystLiveSetBreakpoint 42. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pv.ProbePicking 43. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs.UndoRedo1 44. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs.LoadStateMultiView 45. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcrs.UndoRedo1 46. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 47. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 48. http://open.cdash.org/testSummary.php?project=9&date=2014-08-15&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Sat Aug 16 12:31:11 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Sat, 16 Aug 2014 09:31:11 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Friday, August 15 2014 Message-ID: <20140816163104.1753F7FEE6@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-clang-nightlymaster-release 6 [2]Mac10.7.5-gcc-nightlymaster-release 8 [3]fedora-x64-icc-nightlymaster-debug 9 [4]Win7x64-ninja-nightlymaster-static-release 4 [5]Win7x64-vs10-static-release 1 [6]Win7x64-vs9-nightlymaster-shared-release 1 -------------------- REPORT -------------------- 20 FAILURES [7]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [9]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [10]pv.OpenHelp , 1 , ['Win7x64-vs10-static-release'] [11]pvcrs.TraceMultiViews , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [12]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [13]pvcrs.MemoryInspectorPanel , 1 , ['Mac10.7.5-gcc-nightlymaster-release'] [14]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [15]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [16]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [17]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [18]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [19]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [20]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [21]pvcs.CatalystLiveSetBreakpoint , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [22]pqWidgetspqTextEditTest , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [23]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [24]pv.CatalystLiveSetBreakpoint , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [25]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 3 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'fedora-x64-icc-nightlymaster-debug'] [26]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 4 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'Win7x64-ninja-nightlymaster-static-release', 'Win7x64-vs9-nightlymaster-shared-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [27]Lion-gcc-pvVTK 5 [28]fedora-x64-icc-nightlynext-release 12 [29]Win32-vs9-shared-release 1 [30]Win64-vs9-shared-debug-nocollab 1 [31]Win64-vs9-static-release 1 [32]Win7x64-ninja-nightlynext-shared-release 1 [33]Win7x64-vs9-nightlynext-static-release 4 -------------------- REPORT -------------------- 20 FAILURES [34]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [35]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [36]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [37]pv.OpenHelp , 1 , ['Win64-vs9-static-release'] [38]pvcs.CatalystLiveSetBreakpoint , 1 , ['Lion-gcc-pvVTK'] [39]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [40]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [41]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [42]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [43]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [44]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [45]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [46]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [47]pv.CatalystLiveSetBreakpoint , 1 , ['Lion-gcc-pvVTK'] [48]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [49]pvcs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [50]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [51]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [52]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['Lion-gcc-pvVTK', 'fedora-x64-icc-nightlynext-release'] [53]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 5 , ['Lion-gcc-pvVTK', 'Win32-vs9-shared-release', 'Win64-vs9-shared-debug-nocollab', 'Win7x64-ninja-nightlynext-shared-release', 'Win7x64-vs9-nightlynext-static-release'] References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&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-08-16&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-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 4. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 5. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 6. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs.ProbePicking 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcrs.TestPythonView 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.LoadStateMultiView 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.OpenHelp 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcrs.TraceMultiViews 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=SurfaceLIC-ShuttleZoom2-Batch 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcrs.MemoryInspectorPanel 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.TestPythonView 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=SurfaceLIC-ShuttleZoom1-Batch 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcrs.LoadStateMultiView 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.ProbePicking 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs.TestPythonView 19. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs.LoadStateMultiView 20. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=SurfaceLIC-ShuttleAll-Batch 21. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs.CatalystLiveSetBreakpoint 22. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pqWidgetspqTextEditTest 23. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 24. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.CatalystLiveSetBreakpoint 25. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 26. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks 27. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 28. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 29. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 30. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab 31. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release 32. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release 33. http://open.cdash.org/index.php?project=ParaView&date=2014-08-16&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 34. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs.ProbePicking 35. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcrs.TestPythonView 36. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.LoadStateMultiView 37. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.OpenHelp 38. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs.CatalystLiveSetBreakpoint 39. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=SurfaceLIC-ShuttleZoom2-Batch 40. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcrs.UndoRedo1 41. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.TestPythonView 42. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=SurfaceLIC-ShuttleZoom1-Batch 43. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcrs.LoadStateMultiView 44. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.ProbePicking 45. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 46. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.UndoRedo1 47. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pv.CatalystLiveSetBreakpoint 48. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs.TestPythonView 49. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs.UndoRedo1 50. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs.LoadStateMultiView 51. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=SurfaceLIC-ShuttleAll-Batch 52. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 53. http://open.cdash.org/testSummary.php?project=9&date=2014-08-16&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Sun Aug 17 12:31:13 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Sun, 17 Aug 2014 09:31:13 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Saturday, August 16 2014 Message-ID: <20140817163103.F069E806A2@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Win7x64-vs9-nightlymaster-shared-release 1 [2]Win7x64-ninja-nightlymaster-static-release 4 [3]fedora-x64-icc-nightlymaster-debug 10 -------------------- REPORT -------------------- 14 FAILURES [4]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [5]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [6]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [7]pvcs-collab.CreateDelete , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [9]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [10]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [11]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [12]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [13]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [14]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [15]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [16]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 1 , ['fedora-x64-icc-nightlymaster-debug'] [17]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 2 , ['Win7x64-vs9-nightlymaster-shared-release', 'Win7x64-ninja-nightlymaster-static-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [18]Win64-vs9-shared-debug-nocollab 1 [19]Lion-gcc-pvVTK 5 [20]Win7x64-vs9-nightlynext-static-release 4 [21]fedora-x64-icc-nightlynext-release 12 [22]Win32-vs9-shared-release 1 [23]Win7x64-ninja-nightlynext-shared-release 2 -------------------- REPORT -------------------- 20 FAILURES [24]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [25]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [26]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [27]pv.OpenHelp , 1 , ['Win7x64-ninja-nightlynext-shared-release'] [28]pvcs.CatalystLiveSetBreakpoint , 1 , ['Lion-gcc-pvVTK'] [29]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [30]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [31]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [32]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [33]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [34]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [35]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [36]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [37]pv.CatalystLiveSetBreakpoint , 1 , ['Lion-gcc-pvVTK'] [38]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [39]pvcs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [40]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [41]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [42]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['Lion-gcc-pvVTK', 'fedora-x64-icc-nightlynext-release'] [43]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 5 , ['Win64-vs9-shared-debug-nocollab', 'Lion-gcc-pvVTK', 'Win7x64-vs9-nightlynext-static-release', 'Win32-vs9-shared-release', 'Win7x64-ninja-nightlynext-shared-release'] Issues with submitters The following expected submitters did not submit: kamino.kitware , Mac10.7.5-clang-nightlymaster-release References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-08-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 3. http://open.cdash.org/index.php?project=ParaView&date=2014-08-17&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 4. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs.ProbePicking 5. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcrs.TestPythonView 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pv.LoadStateMultiView 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs-collab.CreateDelete 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=SurfaceLIC-ShuttleZoom2-Batch 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pv.TestPythonView 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=SurfaceLIC-ShuttleZoom1-Batch 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcrs.LoadStateMultiView 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pv.ProbePicking 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs.TestPythonView 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=SurfaceLIC-ShuttleAll-Batch 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs.LoadStateMultiView 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks 18. http://open.cdash.org/index.php?project=ParaView&date=2014-08-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-shared-debug-nocollab 19. http://open.cdash.org/index.php?project=ParaView&date=2014-08-17&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 20. http://open.cdash.org/index.php?project=ParaView&date=2014-08-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 21. http://open.cdash.org/index.php?project=ParaView&date=2014-08-17&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 22. http://open.cdash.org/index.php?project=ParaView&date=2014-08-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 23. http://open.cdash.org/index.php?project=ParaView&date=2014-08-17&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlynext-shared-release 24. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs.ProbePicking 25. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcrs.TestPythonView 26. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pv.LoadStateMultiView 27. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pv.OpenHelp 28. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs.CatalystLiveSetBreakpoint 29. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs.TestPythonView 30. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=SurfaceLIC-ShuttleZoom2-Batch 31. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pv.TestPythonView 32. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=SurfaceLIC-ShuttleZoom1-Batch 33. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcrs.LoadStateMultiView 34. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=SurfaceLIC-ShuttleAll-Batch 35. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 36. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pv.UndoRedo1 37. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pv.CatalystLiveSetBreakpoint 38. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pv.ProbePicking 39. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs.UndoRedo1 40. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs.LoadStateMultiView 41. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcrs.UndoRedo1 42. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 43. http://open.cdash.org/testSummary.php?project=9&date=2014-08-17&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgirish28 at gmail.com Mon Aug 18 05:46:49 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Mon, 18 Aug 2014 11:46:49 +0200 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection Message-ID: Hi, I have been breaking my head over this problem for a while now as there are no servermanager xml explanations anywhere. So, what I want to accomplish is populate a GUI list with a vtkStringArray and be able to select strings within the list in order to fill a variable . Can someone please help me or point me in the right direction in this task? I am writing my own plugin reader as you may have understood, but I'm stuck at this point for a while. Thanks. Regards, Girish -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Aug 18 09:16:00 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 18 Aug 2014 09:16:00 -0400 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: Girish, Is the list of strings fixed, or can it vary depending on the file? There are three things you can do depending on what you need: 1). If you have a fixed set of strings, you can use an IntVectorProperty, and set its domain as a list of strings with an associated integer, i.e., an enumeration. This generates a combo box in the UI, and only one element can be selected at a time. It will expect your reader to have methods with the signature virtual void SetVariableType(int i); virtual int GetVariableType(); Within your reader, you can use this enumeration value to do whatever you'd like. 2). If you just have a list of strings generated in your reader and want to enable the selection of one, you can use a StringVectorProperty with a StringListDomain, e.g. The first property here is an "information-only" property. ParaView will invoke the method "GetAllDimensions" in your reader which should return a vtkStringArray. The second property is responsible for displaying the string array as a combobox, and invokes the method "SetDimensions" with the value selected in the combobox. You need the StringListDomain in the second property to connect the information-only property to the second property. 3). If you need to populate the list depending on what is in the file and be able to select/deselect list entries (e.g., to pick which variables are loaded from the file), then see the XML file ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml and search for the SourceProxy named "FlashReaderCore". You'll find this XML property definition: This property lists which cell-centered arrays to read. This XML is responsible for showing in the GUI the list of cell-associated arrays. In the vtkAMRFlashReader, there are a number of methods that are defined to make this work. (These are actually defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) // Description: // Get the data array selection tables used to configure which data // arrays are loaded by the reader. vtkGetObjectMacro(CellDataArraySelection, vtkDataArraySelection); // Description: // Get the number of point or cell arrays available in the input. int GetNumberOfCellArrays(); // Description: // Get the name of the point or cell array with the given index in // the input. const char* GetCellArrayName(int index); // Description: // Get/Set whether the point or cell array with the given name is to // be read. int GetCellArrayStatus(const char* name); void SetCellArrayStatus(const char* name, int status); The first method listed above might not be necessary in your reader; I'm not sure. The rest are necessary. Note in this XML and method definitions that "Cell" is the name of the given to the association of array the reader can load. You can replace all occurrences of "Cell" with whatever name is more appropriate for your needs. I hope that helps, Cory On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh wrote: > Hi, > > I have been breaking my head over this problem for a while now as there are > no servermanager xml explanations anywhere. So, what I want to accomplish is > populate a GUI list with a vtkStringArray and be able to select strings > within the list in order to fill a variable . Can someone please help me or > point me in the right direction in this task? I am writing my own plugin > reader as you may have understood, but I'm stuck at this point for a while. > Thanks. > > Regards, > Girish > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > From rgirish28 at gmail.com Mon Aug 18 09:25:40 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Mon, 18 Aug 2014 15:25:40 +0200 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: Dear Cory, Thank you very much. Your hints were very helpful. Option 2 was what I was looking for, but I didn't use the StringListDomain in the second property to connect the information. So my plugin was seg faulting repeatedly even though I thought my logic was correct. Also, is there any resource to find more about servermanager xmls and how to connect the different classes together or is the only option to look at examples. Sorry for the trouble :)Thanks again! Regards, Girish On 18 August 2014 15:16, Cory Quammen wrote: > Girish, > > Is the list of strings fixed, or can it vary depending on the file? > There are three things you can do depending on what you need: > > 1). If you have a fixed set of strings, you can use an > IntVectorProperty, and set its domain as a list of strings with an > associated integer, i.e., an enumeration. > > default_values="0" > name="VariableType" > number_of_elements="1"> > > value="0" /> > value="1" /> > value="2" /> > > > > This generates a combo box in the UI, and only one element can be > selected at a time. It will expect your reader to have methods with > the signature > > virtual void SetVariableType(int i); > virtual int GetVariableType(); > > Within your reader, you can use this enumeration value to do whatever > you'd like. > > 2). If you just have a list of strings generated in your reader and > want to enable the selection of one, you can use a > StringVectorProperty with a StringListDomain, e.g. > > information_only="1" > name="DimensionInfo"> > > > command="SetDimensions" > name="Dimensions" > number_of_elements="1" > panel_visibility="default"> > > > name="DimensionInfo" /> > > > > > The first property here is an "information-only" property. ParaView > will invoke the method "GetAllDimensions" in your reader which should > return a vtkStringArray. The second property is responsible for > displaying the string array as a combobox, and invokes the method > "SetDimensions" with the value selected in the combobox. You need the > StringListDomain in the second property to connect the > information-only property to the second property. > > 3). If you need to populate the list depending on what is in the file > and be able to select/deselect list entries (e.g., to pick which > variables are loaded from the file), then see the XML file > > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml > > and search for the SourceProxy named "FlashReaderCore". You'll find > this XML property definition: > > > name="CellArrayInfo"> > > > element_types="2 0" > information_property="CellArrayInfo" > label="Cell Arrays" > name="CellArrayStatus" > number_of_elements="0" > number_of_elements_per_command="2" > repeat_command="1"> > > > name="CellArrayInfo" /> > > > This property lists which cell-centered arrays to > read. > > name="PointArrayInfo"> > > > > This XML is responsible for showing in the GUI the list of > cell-associated arrays. In the vtkAMRFlashReader, there are a number > of > methods that are defined to make this work. (These are actually > defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) > > // Description: > // Get the data array selection tables used to configure which data > // arrays are loaded by the reader. > vtkGetObjectMacro(CellDataArraySelection, vtkDataArraySelection); > > // Description: > // Get the number of point or cell arrays available in the input. > int GetNumberOfCellArrays(); > > // Description: > // Get the name of the point or cell array with the given index in > // the input. > const char* GetCellArrayName(int index); > > // Description: > // Get/Set whether the point or cell array with the given name is to > // be read. > int GetCellArrayStatus(const char* name); > void SetCellArrayStatus(const char* name, int status); > > The first method listed above might not be necessary in your reader; > I'm not sure. The rest are necessary. > > Note in this XML and method definitions that "Cell" is the name of the > given to the association of array the reader can load. You can replace > all occurrences of "Cell" with whatever name is more appropriate for > your needs. > > I hope that helps, > Cory > > On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh > wrote: > > Hi, > > > > I have been breaking my head over this problem for a while now as there > are > > no servermanager xml explanations anywhere. So, what I want to > accomplish is > > populate a GUI list with a vtkStringArray and be able to select strings > > within the list in order to fill a variable . Can someone please help me > or > > point me in the right direction in this task? I am writing my own plugin > > reader as you may have understood, but I'm stuck at this point for a > while. > > Thanks. > > > > Regards, > > Girish > > > > _______________________________________________ > > 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 cory.quammen at kitware.com Mon Aug 18 09:29:21 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 18 Aug 2014 09:29:21 -0400 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: Girish, Unfortunately, there isn't much documentation about the server manager XMLs. Finding something that looks like what you are trying to do in the UI and then tracking it down in the XML is currently the best way. Thanks, Cory On Mon, Aug 18, 2014 at 9:25 AM, Girish Ramesh wrote: > Dear Cory, > > Thank you very much. Your hints were very helpful. Option 2 was what I was > looking for, but I didn't use the StringListDomain in the second property to > connect the information. So my plugin was seg faulting repeatedly even > though I thought my logic was correct. Also, is there any resource to find > more about servermanager xmls and how to connect the different classes > together or is the only option to look at examples. Sorry for the trouble > :)Thanks again! > > Regards, > Girish > > > > > On 18 August 2014 15:16, Cory Quammen wrote: >> >> Girish, >> >> Is the list of strings fixed, or can it vary depending on the file? >> There are three things you can do depending on what you need: >> >> 1). If you have a fixed set of strings, you can use an >> IntVectorProperty, and set its domain as a list of strings with an >> associated integer, i.e., an enumeration. >> >> > default_values="0" >> name="VariableType" >> number_of_elements="1"> >> >> > value="0" /> >> > value="1" /> >> > value="2" /> >> >> >> >> This generates a combo box in the UI, and only one element can be >> selected at a time. It will expect your reader to have methods with >> the signature >> >> virtual void SetVariableType(int i); >> virtual int GetVariableType(); >> >> Within your reader, you can use this enumeration value to do whatever >> you'd like. >> >> 2). If you just have a list of strings generated in your reader and >> want to enable the selection of one, you can use a >> StringVectorProperty with a StringListDomain, e.g. >> >> > information_only="1" >> name="DimensionInfo"> >> >> >> > command="SetDimensions" >> name="Dimensions" >> number_of_elements="1" >> panel_visibility="default"> >> >> >> > name="DimensionInfo" /> >> >> >> >> >> The first property here is an "information-only" property. ParaView >> will invoke the method "GetAllDimensions" in your reader which should >> return a vtkStringArray. The second property is responsible for >> displaying the string array as a combobox, and invokes the method >> "SetDimensions" with the value selected in the combobox. You need the >> StringListDomain in the second property to connect the >> information-only property to the second property. >> >> 3). If you need to populate the list depending on what is in the file >> and be able to select/deselect list entries (e.g., to pick which >> variables are loaded from the file), then see the XML file >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml >> >> and search for the SourceProxy named "FlashReaderCore". You'll find >> this XML property definition: >> >> >> > name="CellArrayInfo"> >> >> >> > element_types="2 0" >> information_property="CellArrayInfo" >> label="Cell Arrays" >> name="CellArrayStatus" >> number_of_elements="0" >> number_of_elements_per_command="2" >> repeat_command="1"> >> >> >> > name="CellArrayInfo" /> >> >> >> This property lists which cell-centered arrays to >> read. >> >> > name="PointArrayInfo"> >> >> >> >> This XML is responsible for showing in the GUI the list of >> cell-associated arrays. In the vtkAMRFlashReader, there are a number >> of >> methods that are defined to make this work. (These are actually >> defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) >> >> // Description: >> // Get the data array selection tables used to configure which data >> // arrays are loaded by the reader. >> vtkGetObjectMacro(CellDataArraySelection, vtkDataArraySelection); >> >> // Description: >> // Get the number of point or cell arrays available in the input. >> int GetNumberOfCellArrays(); >> >> // Description: >> // Get the name of the point or cell array with the given index in >> // the input. >> const char* GetCellArrayName(int index); >> >> // Description: >> // Get/Set whether the point or cell array with the given name is to >> // be read. >> int GetCellArrayStatus(const char* name); >> void SetCellArrayStatus(const char* name, int status); >> >> The first method listed above might not be necessary in your reader; >> I'm not sure. The rest are necessary. >> >> Note in this XML and method definitions that "Cell" is the name of the >> given to the association of array the reader can load. You can replace >> all occurrences of "Cell" with whatever name is more appropriate for >> your needs. >> >> I hope that helps, >> Cory >> >> On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh >> wrote: >> > Hi, >> > >> > I have been breaking my head over this problem for a while now as there >> > are >> > no servermanager xml explanations anywhere. So, what I want to >> > accomplish is >> > populate a GUI list with a vtkStringArray and be able to select strings >> > within the list in order to fill a variable . Can someone please help me >> > or >> > point me in the right direction in this task? I am writing my own plugin >> > reader as you may have understood, but I'm stuck at this point for a >> > while. >> > Thanks. >> > >> > Regards, >> > Girish >> > >> > _______________________________________________ >> > Paraview-developers mailing list >> > Paraview-developers at paraview.org >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > From rgirish28 at gmail.com Mon Aug 18 09:31:28 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Mon, 18 Aug 2014 15:31:28 +0200 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: Thank you very much Cory for your help. I guess the forum shall be peppered with any more problems I have! Regards, Girish On 18 August 2014 15:29, Cory Quammen wrote: > Girish, > > Unfortunately, there isn't much documentation about the server manager > XMLs. Finding something that looks like what you are trying to do in > the UI and then tracking it down in the XML is currently the best way. > > Thanks, > Cory > > On Mon, Aug 18, 2014 at 9:25 AM, Girish Ramesh > wrote: > > Dear Cory, > > > > Thank you very much. Your hints were very helpful. Option 2 was what I > was > > looking for, but I didn't use the StringListDomain in the second > property to > > connect the information. So my plugin was seg faulting repeatedly even > > though I thought my logic was correct. Also, is there any resource to > find > > more about servermanager xmls and how to connect the different classes > > together or is the only option to look at examples. Sorry for the trouble > > :)Thanks again! > > > > Regards, > > Girish > > > > > > > > > > On 18 August 2014 15:16, Cory Quammen wrote: > >> > >> Girish, > >> > >> Is the list of strings fixed, or can it vary depending on the file? > >> There are three things you can do depending on what you need: > >> > >> 1). If you have a fixed set of strings, you can use an > >> IntVectorProperty, and set its domain as a list of strings with an > >> associated integer, i.e., an enumeration. > >> > >> >> default_values="0" > >> name="VariableType" > >> number_of_elements="1"> > >> > >> >> value="0" /> > >> >> value="1" /> > >> >> value="2" /> > >> > >> > >> > >> This generates a combo box in the UI, and only one element can be > >> selected at a time. It will expect your reader to have methods with > >> the signature > >> > >> virtual void SetVariableType(int i); > >> virtual int GetVariableType(); > >> > >> Within your reader, you can use this enumeration value to do whatever > >> you'd like. > >> > >> 2). If you just have a list of strings generated in your reader and > >> want to enable the selection of one, you can use a > >> StringVectorProperty with a StringListDomain, e.g. > >> > >> >> information_only="1" > >> name="DimensionInfo"> > >> > >> > >> >> command="SetDimensions" > >> name="Dimensions" > >> number_of_elements="1" > >> panel_visibility="default"> > >> > >> > >> >> name="DimensionInfo" /> > >> > >> > >> > >> > >> The first property here is an "information-only" property. ParaView > >> will invoke the method "GetAllDimensions" in your reader which should > >> return a vtkStringArray. The second property is responsible for > >> displaying the string array as a combobox, and invokes the method > >> "SetDimensions" with the value selected in the combobox. You need the > >> StringListDomain in the second property to connect the > >> information-only property to the second property. > >> > >> 3). If you need to populate the list depending on what is in the file > >> and be able to select/deselect list entries (e.g., to pick which > >> variables are loaded from the file), then see the XML file > >> > >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml > >> > >> and search for the SourceProxy named "FlashReaderCore". You'll find > >> this XML property definition: > >> > >> > >> >> name="CellArrayInfo"> > >> > >> > >> >> element_types="2 0" > >> information_property="CellArrayInfo" > >> label="Cell Arrays" > >> name="CellArrayStatus" > >> number_of_elements="0" > >> number_of_elements_per_command="2" > >> repeat_command="1"> > >> > >> > >> >> name="CellArrayInfo" /> > >> > >> > >> This property lists which cell-centered arrays to > >> read. > >> > >> >> name="PointArrayInfo"> > >> > >> > >> > >> This XML is responsible for showing in the GUI the list of > >> cell-associated arrays. In the vtkAMRFlashReader, there are a number > >> of > >> methods that are defined to make this work. (These are actually > >> defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) > >> > >> // Description: > >> // Get the data array selection tables used to configure which data > >> // arrays are loaded by the reader. > >> vtkGetObjectMacro(CellDataArraySelection, vtkDataArraySelection); > >> > >> // Description: > >> // Get the number of point or cell arrays available in the input. > >> int GetNumberOfCellArrays(); > >> > >> // Description: > >> // Get the name of the point or cell array with the given index in > >> // the input. > >> const char* GetCellArrayName(int index); > >> > >> // Description: > >> // Get/Set whether the point or cell array with the given name is to > >> // be read. > >> int GetCellArrayStatus(const char* name); > >> void SetCellArrayStatus(const char* name, int status); > >> > >> The first method listed above might not be necessary in your reader; > >> I'm not sure. The rest are necessary. > >> > >> Note in this XML and method definitions that "Cell" is the name of the > >> given to the association of array the reader can load. You can replace > >> all occurrences of "Cell" with whatever name is more appropriate for > >> your needs. > >> > >> I hope that helps, > >> Cory > >> > >> On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh > >> wrote: > >> > Hi, > >> > > >> > I have been breaking my head over this problem for a while now as > there > >> > are > >> > no servermanager xml explanations anywhere. So, what I want to > >> > accomplish is > >> > populate a GUI list with a vtkStringArray and be able to select > strings > >> > within the list in order to fill a variable . Can someone please help > me > >> > or > >> > point me in the right direction in this task? I am writing my own > plugin > >> > reader as you may have understood, but I'm stuck at this point for a > >> > while. > >> > Thanks. > >> > > >> > Regards, > >> > Girish > >> > > >> > _______________________________________________ > >> > 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 rgirish28 at gmail.com Mon Aug 18 09:42:27 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Mon, 18 Aug 2014 15:42:27 +0200 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: Sorry but I'm still getting a seg fault and I'm not sure why. This is the relevant code within the plugin. Thanks. XML: This property helps select the CPO. C++: vtkStringArray* ReadUALGrid::GetCPOList(){ vtkNew labels; labels->InsertNextValue("hello"); labels->InsertNextValue("world"); return labels.GetPointer(); } void ReadUALGrid::SetCPOList(int index) { } I'm just using a random vtkStringArray for testing, but it still segfaults. Thank you for the help. Regards, Girish On 18 August 2014 15:31, Girish Ramesh wrote: > Thank you very much Cory for your help. I guess the forum shall be > peppered with any more problems I have! > > Regards, > Girish > > > On 18 August 2014 15:29, Cory Quammen wrote: > >> Girish, >> >> Unfortunately, there isn't much documentation about the server manager >> XMLs. Finding something that looks like what you are trying to do in >> the UI and then tracking it down in the XML is currently the best way. >> >> Thanks, >> Cory >> >> On Mon, Aug 18, 2014 at 9:25 AM, Girish Ramesh >> wrote: >> > Dear Cory, >> > >> > Thank you very much. Your hints were very helpful. Option 2 was what I >> was >> > looking for, but I didn't use the StringListDomain in the second >> property to >> > connect the information. So my plugin was seg faulting repeatedly even >> > though I thought my logic was correct. Also, is there any resource to >> find >> > more about servermanager xmls and how to connect the different classes >> > together or is the only option to look at examples. Sorry for the >> trouble >> > :)Thanks again! >> > >> > Regards, >> > Girish >> > >> > >> > >> > >> > On 18 August 2014 15:16, Cory Quammen wrote: >> >> >> >> Girish, >> >> >> >> Is the list of strings fixed, or can it vary depending on the file? >> >> There are three things you can do depending on what you need: >> >> >> >> 1). If you have a fixed set of strings, you can use an >> >> IntVectorProperty, and set its domain as a list of strings with an >> >> associated integer, i.e., an enumeration. >> >> >> >> > >> default_values="0" >> >> name="VariableType" >> >> number_of_elements="1"> >> >> >> >> > >> value="0" /> >> >> > >> value="1" /> >> >> > >> value="2" /> >> >> >> >> >> >> >> >> This generates a combo box in the UI, and only one element can be >> >> selected at a time. It will expect your reader to have methods with >> >> the signature >> >> >> >> virtual void SetVariableType(int i); >> >> virtual int GetVariableType(); >> >> >> >> Within your reader, you can use this enumeration value to do whatever >> >> you'd like. >> >> >> >> 2). If you just have a list of strings generated in your reader and >> >> want to enable the selection of one, you can use a >> >> StringVectorProperty with a StringListDomain, e.g. >> >> >> >> > >> information_only="1" >> >> name="DimensionInfo"> >> >> >> >> >> >> > >> command="SetDimensions" >> >> name="Dimensions" >> >> number_of_elements="1" >> >> panel_visibility="default"> >> >> >> >> >> >> > >> name="DimensionInfo" /> >> >> >> >> >> >> >> >> >> >> The first property here is an "information-only" property. ParaView >> >> will invoke the method "GetAllDimensions" in your reader which should >> >> return a vtkStringArray. The second property is responsible for >> >> displaying the string array as a combobox, and invokes the method >> >> "SetDimensions" with the value selected in the combobox. You need the >> >> StringListDomain in the second property to connect the >> >> information-only property to the second property. >> >> >> >> 3). If you need to populate the list depending on what is in the file >> >> and be able to select/deselect list entries (e.g., to pick which >> >> variables are loaded from the file), then see the XML file >> >> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml >> >> >> >> and search for the SourceProxy named "FlashReaderCore". You'll find >> >> this XML property definition: >> >> >> >> >> >> > >> name="CellArrayInfo"> >> >> >> >> >> >> > >> element_types="2 0" >> >> information_property="CellArrayInfo" >> >> label="Cell Arrays" >> >> name="CellArrayStatus" >> >> number_of_elements="0" >> >> number_of_elements_per_command="2" >> >> repeat_command="1"> >> >> >> >> >> >> > >> name="CellArrayInfo" /> >> >> >> >> >> >> This property lists which cell-centered arrays >> to >> >> read. >> >> >> >> > >> name="PointArrayInfo"> >> >> >> >> >> >> >> >> This XML is responsible for showing in the GUI the list of >> >> cell-associated arrays. In the vtkAMRFlashReader, there are a number >> >> of >> >> methods that are defined to make this work. (These are actually >> >> defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) >> >> >> >> // Description: >> >> // Get the data array selection tables used to configure which data >> >> // arrays are loaded by the reader. >> >> vtkGetObjectMacro(CellDataArraySelection, vtkDataArraySelection); >> >> >> >> // Description: >> >> // Get the number of point or cell arrays available in the input. >> >> int GetNumberOfCellArrays(); >> >> >> >> // Description: >> >> // Get the name of the point or cell array with the given index in >> >> // the input. >> >> const char* GetCellArrayName(int index); >> >> >> >> // Description: >> >> // Get/Set whether the point or cell array with the given name is to >> >> // be read. >> >> int GetCellArrayStatus(const char* name); >> >> void SetCellArrayStatus(const char* name, int status); >> >> >> >> The first method listed above might not be necessary in your reader; >> >> I'm not sure. The rest are necessary. >> >> >> >> Note in this XML and method definitions that "Cell" is the name of the >> >> given to the association of array the reader can load. You can replace >> >> all occurrences of "Cell" with whatever name is more appropriate for >> >> your needs. >> >> >> >> I hope that helps, >> >> Cory >> >> >> >> On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh >> >> wrote: >> >> > Hi, >> >> > >> >> > I have been breaking my head over this problem for a while now as >> there >> >> > are >> >> > no servermanager xml explanations anywhere. So, what I want to >> >> > accomplish is >> >> > populate a GUI list with a vtkStringArray and be able to select >> strings >> >> > within the list in order to fill a variable . Can someone please >> help me >> >> > or >> >> > point me in the right direction in this task? I am writing my own >> plugin >> >> > reader as you may have understood, but I'm stuck at this point for a >> >> > while. >> >> > Thanks. >> >> > >> >> > Regards, >> >> > Girish >> >> > >> >> > _______________________________________________ >> >> > 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 cory.quammen at kitware.com Mon Aug 18 09:44:46 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 18 Aug 2014 09:44:46 -0400 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: By the way, I should mention that the ParaView plugin howto page has the most information about how to define the XML: http://www.paraview.org/Wiki/ParaView/Plugin_HowTo You are doing some advanced things, though, so this page may not help. It would be super cool if you could add documentation on using StringVectorProperty with a StringListDomain, though :-) Cory On Mon, Aug 18, 2014 at 9:31 AM, Girish Ramesh wrote: > Thank you very much Cory for your help. I guess the forum shall be peppered > with any more problems I have! > > Regards, > Girish > > > On 18 August 2014 15:29, Cory Quammen wrote: >> >> Girish, >> >> Unfortunately, there isn't much documentation about the server manager >> XMLs. Finding something that looks like what you are trying to do in >> the UI and then tracking it down in the XML is currently the best way. >> >> Thanks, >> Cory >> >> On Mon, Aug 18, 2014 at 9:25 AM, Girish Ramesh >> wrote: >> > Dear Cory, >> > >> > Thank you very much. Your hints were very helpful. Option 2 was what I >> > was >> > looking for, but I didn't use the StringListDomain in the second >> > property to >> > connect the information. So my plugin was seg faulting repeatedly even >> > though I thought my logic was correct. Also, is there any resource to >> > find >> > more about servermanager xmls and how to connect the different classes >> > together or is the only option to look at examples. Sorry for the >> > trouble >> > :)Thanks again! >> > >> > Regards, >> > Girish >> > >> > >> > >> > >> > On 18 August 2014 15:16, Cory Quammen wrote: >> >> >> >> Girish, >> >> >> >> Is the list of strings fixed, or can it vary depending on the file? >> >> There are three things you can do depending on what you need: >> >> >> >> 1). If you have a fixed set of strings, you can use an >> >> IntVectorProperty, and set its domain as a list of strings with an >> >> associated integer, i.e., an enumeration. >> >> >> >> > >> default_values="0" >> >> name="VariableType" >> >> number_of_elements="1"> >> >> >> >> > >> value="0" /> >> >> > >> value="1" /> >> >> > >> value="2" /> >> >> >> >> >> >> >> >> This generates a combo box in the UI, and only one element can be >> >> selected at a time. It will expect your reader to have methods with >> >> the signature >> >> >> >> virtual void SetVariableType(int i); >> >> virtual int GetVariableType(); >> >> >> >> Within your reader, you can use this enumeration value to do whatever >> >> you'd like. >> >> >> >> 2). If you just have a list of strings generated in your reader and >> >> want to enable the selection of one, you can use a >> >> StringVectorProperty with a StringListDomain, e.g. >> >> >> >> > >> information_only="1" >> >> name="DimensionInfo"> >> >> >> >> >> >> > >> command="SetDimensions" >> >> name="Dimensions" >> >> number_of_elements="1" >> >> panel_visibility="default"> >> >> >> >> >> >> > >> name="DimensionInfo" /> >> >> >> >> >> >> >> >> >> >> The first property here is an "information-only" property. ParaView >> >> will invoke the method "GetAllDimensions" in your reader which should >> >> return a vtkStringArray. The second property is responsible for >> >> displaying the string array as a combobox, and invokes the method >> >> "SetDimensions" with the value selected in the combobox. You need the >> >> StringListDomain in the second property to connect the >> >> information-only property to the second property. >> >> >> >> 3). If you need to populate the list depending on what is in the file >> >> and be able to select/deselect list entries (e.g., to pick which >> >> variables are loaded from the file), then see the XML file >> >> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml >> >> >> >> and search for the SourceProxy named "FlashReaderCore". You'll find >> >> this XML property definition: >> >> >> >> >> >> > >> name="CellArrayInfo"> >> >> >> >> >> >> > >> element_types="2 0" >> >> information_property="CellArrayInfo" >> >> label="Cell Arrays" >> >> name="CellArrayStatus" >> >> number_of_elements="0" >> >> number_of_elements_per_command="2" >> >> repeat_command="1"> >> >> >> >> >> >> > >> name="CellArrayInfo" /> >> >> >> >> >> >> This property lists which cell-centered arrays >> >> to >> >> read. >> >> >> >> > >> name="PointArrayInfo"> >> >> >> >> >> >> >> >> This XML is responsible for showing in the GUI the list of >> >> cell-associated arrays. In the vtkAMRFlashReader, there are a number >> >> of >> >> methods that are defined to make this work. (These are actually >> >> defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) >> >> >> >> // Description: >> >> // Get the data array selection tables used to configure which data >> >> // arrays are loaded by the reader. >> >> vtkGetObjectMacro(CellDataArraySelection, vtkDataArraySelection); >> >> >> >> // Description: >> >> // Get the number of point or cell arrays available in the input. >> >> int GetNumberOfCellArrays(); >> >> >> >> // Description: >> >> // Get the name of the point or cell array with the given index in >> >> // the input. >> >> const char* GetCellArrayName(int index); >> >> >> >> // Description: >> >> // Get/Set whether the point or cell array with the given name is to >> >> // be read. >> >> int GetCellArrayStatus(const char* name); >> >> void SetCellArrayStatus(const char* name, int status); >> >> >> >> The first method listed above might not be necessary in your reader; >> >> I'm not sure. The rest are necessary. >> >> >> >> Note in this XML and method definitions that "Cell" is the name of the >> >> given to the association of array the reader can load. You can replace >> >> all occurrences of "Cell" with whatever name is more appropriate for >> >> your needs. >> >> >> >> I hope that helps, >> >> Cory >> >> >> >> On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh >> >> wrote: >> >> > Hi, >> >> > >> >> > I have been breaking my head over this problem for a while now as >> >> > there >> >> > are >> >> > no servermanager xml explanations anywhere. So, what I want to >> >> > accomplish is >> >> > populate a GUI list with a vtkStringArray and be able to select >> >> > strings >> >> > within the list in order to fill a variable . Can someone please help >> >> > me >> >> > or >> >> > point me in the right direction in this task? I am writing my own >> >> > plugin >> >> > reader as you may have understood, but I'm stuck at this point for a >> >> > while. >> >> > Thanks. >> >> > >> >> > Regards, >> >> > Girish >> >> > >> >> > _______________________________________________ >> >> > Paraview-developers mailing list >> >> > Paraview-developers at paraview.org >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > >> > >> > > > From cory.quammen at kitware.com Mon Aug 18 09:49:37 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 18 Aug 2014 09:49:37 -0400 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: The biggest problem is that vtkNew will decrement the reference count when you go out of scope in GetCPOList(), so it will be garbage collected and anything using the return value may cause a crash. For your quick proof-of-concept work, use a vtkSmartPointer instead, or even just a raw pointer. Also, SetCPOList takes an int, but shouldn't it take a char* or const char*? Cory On Mon, Aug 18, 2014 at 9:42 AM, Girish Ramesh wrote: > Sorry but I'm still getting a seg fault and I'm not sure why. This is the > relevant code within the plugin. Thanks. > > XML: > > name="CPOList" > label="CPOList" > command="SetCPOList" > number_of_elements_per_command="1" > information_property="CPOListInfo" > > panel_visibility="default"> > > > name="CPOListInfo"/> > > > > > This property helps select the CPO. > > > > name="CPOListInfo" > label="CPOListInfo" > command="GetCPOList" > information_only="1" > > > > > C++: > > vtkStringArray* ReadUALGrid::GetCPOList(){ > > > vtkNew labels; > > > labels->InsertNextValue("hello"); > labels->InsertNextValue("world"); > > > return labels.GetPointer(); > > } > > void ReadUALGrid::SetCPOList(int index) > > { > > } > > > I'm just using a random vtkStringArray for testing, but it still segfaults. > Thank you for the help. > > Regards, > Girish > > > > > On 18 August 2014 15:31, Girish Ramesh wrote: >> >> Thank you very much Cory for your help. I guess the forum shall be >> peppered with any more problems I have! >> >> Regards, >> Girish >> >> >> On 18 August 2014 15:29, Cory Quammen wrote: >>> >>> Girish, >>> >>> Unfortunately, there isn't much documentation about the server manager >>> XMLs. Finding something that looks like what you are trying to do in >>> the UI and then tracking it down in the XML is currently the best way. >>> >>> Thanks, >>> Cory >>> >>> On Mon, Aug 18, 2014 at 9:25 AM, Girish Ramesh >>> wrote: >>> > Dear Cory, >>> > >>> > Thank you very much. Your hints were very helpful. Option 2 was what I >>> > was >>> > looking for, but I didn't use the StringListDomain in the second >>> > property to >>> > connect the information. So my plugin was seg faulting repeatedly even >>> > though I thought my logic was correct. Also, is there any resource to >>> > find >>> > more about servermanager xmls and how to connect the different classes >>> > together or is the only option to look at examples. Sorry for the >>> > trouble >>> > :)Thanks again! >>> > >>> > Regards, >>> > Girish >>> > >>> > >>> > >>> > >>> > On 18 August 2014 15:16, Cory Quammen wrote: >>> >> >>> >> Girish, >>> >> >>> >> Is the list of strings fixed, or can it vary depending on the file? >>> >> There are three things you can do depending on what you need: >>> >> >>> >> 1). If you have a fixed set of strings, you can use an >>> >> IntVectorProperty, and set its domain as a list of strings with an >>> >> associated integer, i.e., an enumeration. >>> >> >>> >> >> >> default_values="0" >>> >> name="VariableType" >>> >> number_of_elements="1"> >>> >> >>> >> >> >> value="0" /> >>> >> >> >> value="1" /> >>> >> >> >> value="2" /> >>> >> >>> >> >>> >> >>> >> This generates a combo box in the UI, and only one element can be >>> >> selected at a time. It will expect your reader to have methods with >>> >> the signature >>> >> >>> >> virtual void SetVariableType(int i); >>> >> virtual int GetVariableType(); >>> >> >>> >> Within your reader, you can use this enumeration value to do whatever >>> >> you'd like. >>> >> >>> >> 2). If you just have a list of strings generated in your reader and >>> >> want to enable the selection of one, you can use a >>> >> StringVectorProperty with a StringListDomain, e.g. >>> >> >>> >> >> >> information_only="1" >>> >> name="DimensionInfo"> >>> >> >>> >> >>> >> >> >> command="SetDimensions" >>> >> name="Dimensions" >>> >> number_of_elements="1" >>> >> panel_visibility="default"> >>> >> >>> >> >>> >> >> >> name="DimensionInfo" /> >>> >> >>> >> >>> >> >>> >> >>> >> The first property here is an "information-only" property. ParaView >>> >> will invoke the method "GetAllDimensions" in your reader which should >>> >> return a vtkStringArray. The second property is responsible for >>> >> displaying the string array as a combobox, and invokes the method >>> >> "SetDimensions" with the value selected in the combobox. You need the >>> >> StringListDomain in the second property to connect the >>> >> information-only property to the second property. >>> >> >>> >> 3). If you need to populate the list depending on what is in the file >>> >> and be able to select/deselect list entries (e.g., to pick which >>> >> variables are loaded from the file), then see the XML file >>> >> >>> >> >>> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml >>> >> >>> >> and search for the SourceProxy named "FlashReaderCore". You'll find >>> >> this XML property definition: >>> >> >>> >> >>> >> >> >> name="CellArrayInfo"> >>> >> >>> >> >>> >> >> >> element_types="2 0" >>> >> information_property="CellArrayInfo" >>> >> label="Cell Arrays" >>> >> name="CellArrayStatus" >>> >> number_of_elements="0" >>> >> number_of_elements_per_command="2" >>> >> repeat_command="1"> >>> >> >>> >> >>> >> >> >> name="CellArrayInfo" /> >>> >> >>> >> >>> >> This property lists which cell-centered arrays >>> >> to >>> >> read. >>> >> >>> >> >> >> name="PointArrayInfo"> >>> >> >>> >> >>> >> >>> >> This XML is responsible for showing in the GUI the list of >>> >> cell-associated arrays. In the vtkAMRFlashReader, there are a number >>> >> of >>> >> methods that are defined to make this work. (These are actually >>> >> defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) >>> >> >>> >> // Description: >>> >> // Get the data array selection tables used to configure which data >>> >> // arrays are loaded by the reader. >>> >> vtkGetObjectMacro(CellDataArraySelection, vtkDataArraySelection); >>> >> >>> >> // Description: >>> >> // Get the number of point or cell arrays available in the input. >>> >> int GetNumberOfCellArrays(); >>> >> >>> >> // Description: >>> >> // Get the name of the point or cell array with the given index in >>> >> // the input. >>> >> const char* GetCellArrayName(int index); >>> >> >>> >> // Description: >>> >> // Get/Set whether the point or cell array with the given name is to >>> >> // be read. >>> >> int GetCellArrayStatus(const char* name); >>> >> void SetCellArrayStatus(const char* name, int status); >>> >> >>> >> The first method listed above might not be necessary in your reader; >>> >> I'm not sure. The rest are necessary. >>> >> >>> >> Note in this XML and method definitions that "Cell" is the name of the >>> >> given to the association of array the reader can load. You can replace >>> >> all occurrences of "Cell" with whatever name is more appropriate for >>> >> your needs. >>> >> >>> >> I hope that helps, >>> >> Cory >>> >> >>> >> On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh >>> >> wrote: >>> >> > Hi, >>> >> > >>> >> > I have been breaking my head over this problem for a while now as >>> >> > there >>> >> > are >>> >> > no servermanager xml explanations anywhere. So, what I want to >>> >> > accomplish is >>> >> > populate a GUI list with a vtkStringArray and be able to select >>> >> > strings >>> >> > within the list in order to fill a variable . Can someone please >>> >> > help me >>> >> > or >>> >> > point me in the right direction in this task? I am writing my own >>> >> > plugin >>> >> > reader as you may have understood, but I'm stuck at this point for a >>> >> > while. >>> >> > Thanks. >>> >> > >>> >> > Regards, >>> >> > Girish >>> >> > >>> >> > _______________________________________________ >>> >> > Paraview-developers mailing list >>> >> > Paraview-developers at paraview.org >>> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >>> >> > >>> > >>> > >> >> > From rgirish28 at gmail.com Mon Aug 18 10:19:12 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Mon, 18 Aug 2014 16:19:12 +0200 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: Well, I did try with a vtkSmartPointer but it didn't work either. Still segfaulting. This is the code state at the moment and I can't figure out why! It is definitely the problem of this bit as the rest of the plugin is compiling and running without segfaulting. So, I hope you can help me. Thanks. XML: This property helps select the CPO. C++: vtkStringArray* ReadUALGrid::GetCPOList(){ vtkSmartPointer labels; labels->InsertNextValue("hello"); labels->InsertNextValue("world"); return labels; } void ReadUALGrid::SetCPOList(const char* name) { } On 18 August 2014 15:49, Cory Quammen wrote: > The biggest problem is that vtkNew will decrement the reference count > when you go out of scope in GetCPOList(), so it will be garbage > collected and anything using the return value may cause a crash. For > your quick proof-of-concept work, use a vtkSmartPointer instead, or > even just a raw pointer. > > Also, SetCPOList takes an int, but shouldn't it take a char* or const > char*? > > Cory > > On Mon, Aug 18, 2014 at 9:42 AM, Girish Ramesh > wrote: > > Sorry but I'm still getting a seg fault and I'm not sure why. This is the > > relevant code within the plugin. Thanks. > > > > XML: > > > > > name="CPOList" > > label="CPOList" > > command="SetCPOList" > > number_of_elements_per_command="1" > > information_property="CPOListInfo" > > > > panel_visibility="default"> > > > > > > > name="CPOListInfo"/> > > > > > > > > > > This property helps select the CPO. > > > > > > > > > name="CPOListInfo" > > label="CPOListInfo" > > command="GetCPOList" > > information_only="1" > > > > > > > > > C++: > > > > vtkStringArray* ReadUALGrid::GetCPOList(){ > > > > > > vtkNew labels; > > > > > > labels->InsertNextValue("hello"); > > labels->InsertNextValue("world"); > > > > > > return labels.GetPointer(); > > > > } > > > > void ReadUALGrid::SetCPOList(int index) > > > > { > > > > } > > > > > > I'm just using a random vtkStringArray for testing, but it still > segfaults. > > Thank you for the help. > > > > Regards, > > Girish > > > > > > > > > > On 18 August 2014 15:31, Girish Ramesh wrote: > >> > >> Thank you very much Cory for your help. I guess the forum shall be > >> peppered with any more problems I have! > >> > >> Regards, > >> Girish > >> > >> > >> On 18 August 2014 15:29, Cory Quammen wrote: > >>> > >>> Girish, > >>> > >>> Unfortunately, there isn't much documentation about the server manager > >>> XMLs. Finding something that looks like what you are trying to do in > >>> the UI and then tracking it down in the XML is currently the best way. > >>> > >>> Thanks, > >>> Cory > >>> > >>> On Mon, Aug 18, 2014 at 9:25 AM, Girish Ramesh > >>> wrote: > >>> > Dear Cory, > >>> > > >>> > Thank you very much. Your hints were very helpful. Option 2 was what > I > >>> > was > >>> > looking for, but I didn't use the StringListDomain in the second > >>> > property to > >>> > connect the information. So my plugin was seg faulting repeatedly > even > >>> > though I thought my logic was correct. Also, is there any resource to > >>> > find > >>> > more about servermanager xmls and how to connect the different > classes > >>> > together or is the only option to look at examples. Sorry for the > >>> > trouble > >>> > :)Thanks again! > >>> > > >>> > Regards, > >>> > Girish > >>> > > >>> > > >>> > > >>> > > >>> > On 18 August 2014 15:16, Cory Quammen > wrote: > >>> >> > >>> >> Girish, > >>> >> > >>> >> Is the list of strings fixed, or can it vary depending on the file? > >>> >> There are three things you can do depending on what you need: > >>> >> > >>> >> 1). If you have a fixed set of strings, you can use an > >>> >> IntVectorProperty, and set its domain as a list of strings with an > >>> >> associated integer, i.e., an enumeration. > >>> >> > >>> >> >>> >> default_values="0" > >>> >> name="VariableType" > >>> >> number_of_elements="1"> > >>> >> > >>> >> >>> >> value="0" /> > >>> >> >>> >> value="1" /> > >>> >> >>> >> value="2" /> > >>> >> > >>> >> > >>> >> > >>> >> This generates a combo box in the UI, and only one element can be > >>> >> selected at a time. It will expect your reader to have methods with > >>> >> the signature > >>> >> > >>> >> virtual void SetVariableType(int i); > >>> >> virtual int GetVariableType(); > >>> >> > >>> >> Within your reader, you can use this enumeration value to do > whatever > >>> >> you'd like. > >>> >> > >>> >> 2). If you just have a list of strings generated in your reader and > >>> >> want to enable the selection of one, you can use a > >>> >> StringVectorProperty with a StringListDomain, e.g. > >>> >> > >>> >> >>> >> information_only="1" > >>> >> name="DimensionInfo"> > >>> >> > >>> >> > >>> >> >>> >> command="SetDimensions" > >>> >> name="Dimensions" > >>> >> number_of_elements="1" > >>> >> panel_visibility="default"> > >>> >> > >>> >> > >>> >> >>> >> name="DimensionInfo" /> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> The first property here is an "information-only" property. ParaView > >>> >> will invoke the method "GetAllDimensions" in your reader which > should > >>> >> return a vtkStringArray. The second property is responsible for > >>> >> displaying the string array as a combobox, and invokes the method > >>> >> "SetDimensions" with the value selected in the combobox. You need > the > >>> >> StringListDomain in the second property to connect the > >>> >> information-only property to the second property. > >>> >> > >>> >> 3). If you need to populate the list depending on what is in the > file > >>> >> and be able to select/deselect list entries (e.g., to pick which > >>> >> variables are loaded from the file), then see the XML file > >>> >> > >>> >> > >>> >> > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml > >>> >> > >>> >> and search for the SourceProxy named "FlashReaderCore". You'll find > >>> >> this XML property definition: > >>> >> > >>> >> > >>> >> >>> >> name="CellArrayInfo"> > >>> >> > >>> >> > >>> >> >>> >> element_types="2 0" > >>> >> information_property="CellArrayInfo" > >>> >> label="Cell Arrays" > >>> >> name="CellArrayStatus" > >>> >> number_of_elements="0" > >>> >> number_of_elements_per_command="2" > >>> >> repeat_command="1"> > >>> >> > >>> >> > >>> >> >>> >> name="CellArrayInfo" /> > >>> >> > >>> >> > >>> >> This property lists which cell-centered > arrays > >>> >> to > >>> >> read. > >>> >> > >>> >> >>> >> name="PointArrayInfo"> > >>> >> > >>> >> > >>> >> > >>> >> This XML is responsible for showing in the GUI the list of > >>> >> cell-associated arrays. In the vtkAMRFlashReader, there are a number > >>> >> of > >>> >> methods that are defined to make this work. (These are actually > >>> >> defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) > >>> >> > >>> >> // Description: > >>> >> // Get the data array selection tables used to configure which > data > >>> >> // arrays are loaded by the reader. > >>> >> vtkGetObjectMacro(CellDataArraySelection, vtkDataArraySelection); > >>> >> > >>> >> // Description: > >>> >> // Get the number of point or cell arrays available in the input. > >>> >> int GetNumberOfCellArrays(); > >>> >> > >>> >> // Description: > >>> >> // Get the name of the point or cell array with the given index in > >>> >> // the input. > >>> >> const char* GetCellArrayName(int index); > >>> >> > >>> >> // Description: > >>> >> // Get/Set whether the point or cell array with the given name is > to > >>> >> // be read. > >>> >> int GetCellArrayStatus(const char* name); > >>> >> void SetCellArrayStatus(const char* name, int status); > >>> >> > >>> >> The first method listed above might not be necessary in your reader; > >>> >> I'm not sure. The rest are necessary. > >>> >> > >>> >> Note in this XML and method definitions that "Cell" is the name of > the > >>> >> given to the association of array the reader can load. You can > replace > >>> >> all occurrences of "Cell" with whatever name is more appropriate for > >>> >> your needs. > >>> >> > >>> >> I hope that helps, > >>> >> Cory > >>> >> > >>> >> On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh > > >>> >> wrote: > >>> >> > Hi, > >>> >> > > >>> >> > I have been breaking my head over this problem for a while now as > >>> >> > there > >>> >> > are > >>> >> > no servermanager xml explanations anywhere. So, what I want to > >>> >> > accomplish is > >>> >> > populate a GUI list with a vtkStringArray and be able to select > >>> >> > strings > >>> >> > within the list in order to fill a variable . Can someone please > >>> >> > help me > >>> >> > or > >>> >> > point me in the right direction in this task? I am writing my own > >>> >> > plugin > >>> >> > reader as you may have understood, but I'm stuck at this point > for a > >>> >> > while. > >>> >> > Thanks. > >>> >> > > >>> >> > Regards, > >>> >> > Girish > >>> >> > > >>> >> > _______________________________________________ > >>> >> > 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 utkarsh.ayachit at kitware.com Mon Aug 18 10:26:37 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 18 Aug 2014 10:26:37 -0400 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: Girish, GetCPOList() is incorrect. You cannot return references to variables that go out of scope at the end of the method. Just as a hack, mark the labels variable as static and it will work. You should change the code to make Labels an member variable of the class and return that. Utkarsh On Mon, Aug 18, 2014 at 10:19 AM, Girish Ramesh wrote: > Well, I did try with a vtkSmartPointer but it didn't work either. Still > segfaulting. This is the code state at the moment and I can't figure out > why! It is definitely the problem of this bit as the rest of the plugin is > compiling and running without segfaulting. So, I hope you can help me. > Thanks. > > XML: > > name="CPOList" > label="CPOList" > command="SetCPOList" > number_of_elements_per_ > command="1" > information_property="CPOListInfo" > > panel_visibility="default"> > > > name="CPOListInfo"/> > > > > > This property helps select the CPO. > > > > name="CPOListInfo" > label="CPOListInfo" > command="GetCPOList" > information_only="1" > > > > > > C++: > > > vtkStringArray* ReadUALGrid::GetCPOList(){ > > > vtkSmartPointer labels; > > > > labels->InsertNextValue("hello"); > labels->InsertNextValue("world"); > > > return labels; > > } > > void ReadUALGrid::SetCPOList(const char* name) > > { > > } > > > > > On 18 August 2014 15:49, Cory Quammen wrote: >> >> The biggest problem is that vtkNew will decrement the reference count >> when you go out of scope in GetCPOList(), so it will be garbage >> collected and anything using the return value may cause a crash. For >> your quick proof-of-concept work, use a vtkSmartPointer instead, or >> even just a raw pointer. >> >> Also, SetCPOList takes an int, but shouldn't it take a char* or const >> char*? >> >> Cory >> >> On Mon, Aug 18, 2014 at 9:42 AM, Girish Ramesh >> wrote: >> > Sorry but I'm still getting a seg fault and I'm not sure why. This is >> > the >> > relevant code within the plugin. Thanks. >> > >> > XML: >> > >> > > > name="CPOList" >> > label="CPOList" >> > command="SetCPOList" >> > number_of_elements_per_command="1" >> > information_property="CPOListInfo" >> > >> > panel_visibility="default"> >> > >> > >> > > > name="CPOListInfo"/> >> > >> > >> > >> > >> > This property helps select the CPO. >> > >> > >> > >> > > > name="CPOListInfo" >> > label="CPOListInfo" >> > command="GetCPOList" >> > information_only="1" > >> > >> > >> > >> > C++: >> > >> > vtkStringArray* ReadUALGrid::GetCPOList(){ >> > >> > >> > vtkNew labels; >> > >> > >> > labels->InsertNextValue("hello"); >> > labels->InsertNextValue("world"); >> > >> > >> > return labels.GetPointer(); >> > >> > } >> > >> > void ReadUALGrid::SetCPOList(int index) >> > >> > { >> > >> > } >> > >> > >> > I'm just using a random vtkStringArray for testing, but it still >> > segfaults. >> > Thank you for the help. >> > >> > Regards, >> > Girish >> > >> > >> > >> > >> > On 18 August 2014 15:31, Girish Ramesh wrote: >> >> >> >> Thank you very much Cory for your help. I guess the forum shall be >> >> peppered with any more problems I have! >> >> >> >> Regards, >> >> Girish >> >> >> >> >> >> On 18 August 2014 15:29, Cory Quammen wrote: >> >>> >> >>> Girish, >> >>> >> >>> Unfortunately, there isn't much documentation about the server manager >> >>> XMLs. Finding something that looks like what you are trying to do in >> >>> the UI and then tracking it down in the XML is currently the best way. >> >>> >> >>> Thanks, >> >>> Cory >> >>> >> >>> On Mon, Aug 18, 2014 at 9:25 AM, Girish Ramesh >> >>> wrote: >> >>> > Dear Cory, >> >>> > >> >>> > Thank you very much. Your hints were very helpful. Option 2 was what >> >>> > I >> >>> > was >> >>> > looking for, but I didn't use the StringListDomain in the second >> >>> > property to >> >>> > connect the information. So my plugin was seg faulting repeatedly >> >>> > even >> >>> > though I thought my logic was correct. Also, is there any resource >> >>> > to >> >>> > find >> >>> > more about servermanager xmls and how to connect the different >> >>> > classes >> >>> > together or is the only option to look at examples. Sorry for the >> >>> > trouble >> >>> > :)Thanks again! >> >>> > >> >>> > Regards, >> >>> > Girish >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > On 18 August 2014 15:16, Cory Quammen >> >>> > wrote: >> >>> >> >> >>> >> Girish, >> >>> >> >> >>> >> Is the list of strings fixed, or can it vary depending on the file? >> >>> >> There are three things you can do depending on what you need: >> >>> >> >> >>> >> 1). If you have a fixed set of strings, you can use an >> >>> >> IntVectorProperty, and set its domain as a list of strings with an >> >>> >> associated integer, i.e., an enumeration. >> >>> >> >> >>> >> > >>> >> default_values="0" >> >>> >> name="VariableType" >> >>> >> number_of_elements="1"> >> >>> >> >> >>> >> > >>> >> value="0" /> >> >>> >> > >>> >> value="1" /> >> >>> >> > >>> >> value="2" /> >> >>> >> >> >>> >> >> >>> >> >> >>> >> This generates a combo box in the UI, and only one element can be >> >>> >> selected at a time. It will expect your reader to have methods with >> >>> >> the signature >> >>> >> >> >>> >> virtual void SetVariableType(int i); >> >>> >> virtual int GetVariableType(); >> >>> >> >> >>> >> Within your reader, you can use this enumeration value to do >> >>> >> whatever >> >>> >> you'd like. >> >>> >> >> >>> >> 2). If you just have a list of strings generated in your reader and >> >>> >> want to enable the selection of one, you can use a >> >>> >> StringVectorProperty with a StringListDomain, e.g. >> >>> >> >> >>> >> > >>> >> information_only="1" >> >>> >> name="DimensionInfo"> >> >>> >> >> >>> >> >> >>> >> > >>> >> command="SetDimensions" >> >>> >> name="Dimensions" >> >>> >> number_of_elements="1" >> >>> >> panel_visibility="default"> >> >>> >> >> >>> >> >> >>> >> > >>> >> name="DimensionInfo" /> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> The first property here is an "information-only" property. ParaView >> >>> >> will invoke the method "GetAllDimensions" in your reader which >> >>> >> should >> >>> >> return a vtkStringArray. The second property is responsible for >> >>> >> displaying the string array as a combobox, and invokes the method >> >>> >> "SetDimensions" with the value selected in the combobox. You need >> >>> >> the >> >>> >> StringListDomain in the second property to connect the >> >>> >> information-only property to the second property. >> >>> >> >> >>> >> 3). If you need to populate the list depending on what is in the >> >>> >> file >> >>> >> and be able to select/deselect list entries (e.g., to pick which >> >>> >> variables are loaded from the file), then see the XML file >> >>> >> >> >>> >> >> >>> >> >> >>> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml >> >>> >> >> >>> >> and search for the SourceProxy named "FlashReaderCore". You'll find >> >>> >> this XML property definition: >> >>> >> >> >>> >> >> >>> >> > >>> >> name="CellArrayInfo"> >> >>> >> >> >>> >> >> >>> >> > >>> >> element_types="2 0" >> >>> >> information_property="CellArrayInfo" >> >>> >> label="Cell Arrays" >> >>> >> name="CellArrayStatus" >> >>> >> number_of_elements="0" >> >>> >> number_of_elements_per_command="2" >> >>> >> repeat_command="1"> >> >>> >> >> >>> >> >> >>> >> > >>> >> name="CellArrayInfo" /> >> >>> >> >> >>> >> >> >>> >> This property lists which cell-centered >> >>> >> arrays >> >>> >> to >> >>> >> read. >> >>> >> >> >>> >> > >>> >> name="PointArrayInfo"> >> >>> >> >> >>> >> >> >>> >> >> >>> >> This XML is responsible for showing in the GUI the list of >> >>> >> cell-associated arrays. In the vtkAMRFlashReader, there are a >> >>> >> number >> >>> >> of >> >>> >> methods that are defined to make this work. (These are actually >> >>> >> defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) >> >>> >> >> >>> >> // Description: >> >>> >> // Get the data array selection tables used to configure which >> >>> >> data >> >>> >> // arrays are loaded by the reader. >> >>> >> vtkGetObjectMacro(CellDataArraySelection, vtkDataArraySelection); >> >>> >> >> >>> >> // Description: >> >>> >> // Get the number of point or cell arrays available in the input. >> >>> >> int GetNumberOfCellArrays(); >> >>> >> >> >>> >> // Description: >> >>> >> // Get the name of the point or cell array with the given index >> >>> >> in >> >>> >> // the input. >> >>> >> const char* GetCellArrayName(int index); >> >>> >> >> >>> >> // Description: >> >>> >> // Get/Set whether the point or cell array with the given name is >> >>> >> to >> >>> >> // be read. >> >>> >> int GetCellArrayStatus(const char* name); >> >>> >> void SetCellArrayStatus(const char* name, int status); >> >>> >> >> >>> >> The first method listed above might not be necessary in your >> >>> >> reader; >> >>> >> I'm not sure. The rest are necessary. >> >>> >> >> >>> >> Note in this XML and method definitions that "Cell" is the name of >> >>> >> the >> >>> >> given to the association of array the reader can load. You can >> >>> >> replace >> >>> >> all occurrences of "Cell" with whatever name is more appropriate >> >>> >> for >> >>> >> your needs. >> >>> >> >> >>> >> I hope that helps, >> >>> >> Cory >> >>> >> >> >>> >> On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh >> >>> >> >> >>> >> wrote: >> >>> >> > Hi, >> >>> >> > >> >>> >> > I have been breaking my head over this problem for a while now as >> >>> >> > there >> >>> >> > are >> >>> >> > no servermanager xml explanations anywhere. So, what I want to >> >>> >> > accomplish is >> >>> >> > populate a GUI list with a vtkStringArray and be able to select >> >>> >> > strings >> >>> >> > within the list in order to fill a variable . Can someone please >> >>> >> > help me >> >>> >> > or >> >>> >> > point me in the right direction in this task? I am writing my own >> >>> >> > plugin >> >>> >> > reader as you may have understood, but I'm stuck at this point >> >>> >> > for a >> >>> >> > while. >> >>> >> > Thanks. >> >>> >> > >> >>> >> > Regards, >> >>> >> > Girish >> >>> >> > >> >>> >> > _______________________________________________ >> >>> >> > Paraview-developers mailing list >> >>> >> > Paraview-developers at paraview.org >> >>> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >>> >> > >> >>> > >> >>> > >> >> >> >> >> > > > > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > From rgirish28 at gmail.com Mon Aug 18 10:44:22 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Mon, 18 Aug 2014 16:44:22 +0200 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: Thanks Utkarsh. I was also making the mistake of not allocating the memory for a SmartPointer as I was changing the code from vtkNew and forgot to adapt it. I've changed it now and it works finally! Thanks a lot guys. I'll probably add some documentation for this as there is nothing mentioned in the Wiki that is close to this at all. Regards, Girish On 18 August 2014 16:26, Utkarsh Ayachit wrote: > Girish, > > GetCPOList() is incorrect. You cannot return references to variables > that go out of scope at the end of the method. Just as a hack, mark > the labels variable as static and it will work. You should change the > code to make Labels an > member variable of the class and return that. > > Utkarsh > > On Mon, Aug 18, 2014 at 10:19 AM, Girish Ramesh > wrote: > > Well, I did try with a vtkSmartPointer but it didn't work either. Still > > segfaulting. This is the code state at the moment and I can't figure out > > why! It is definitely the problem of this bit as the rest of the plugin > is > > compiling and running without segfaulting. So, I hope you can help me. > > Thanks. > > > > XML: > > > > > name="CPOList" > > label="CPOList" > > command="SetCPOList" > > number_of_elements_per_ > > command="1" > > information_property="CPOListInfo" > > > > panel_visibility="default"> > > > > > > > name="CPOListInfo"/> > > > > > > > > > > This property helps select the CPO. > > > > > > > > > name="CPOListInfo" > > label="CPOListInfo" > > command="GetCPOList" > > information_only="1" > > > > > > > > > > > C++: > > > > > > vtkStringArray* ReadUALGrid::GetCPOList(){ > > > > > > vtkSmartPointer labels; > > > > > > > > labels->InsertNextValue("hello"); > > labels->InsertNextValue("world"); > > > > > > return labels; > > > > } > > > > void ReadUALGrid::SetCPOList(const char* name) > > > > { > > > > } > > > > > > > > > > On 18 August 2014 15:49, Cory Quammen wrote: > >> > >> The biggest problem is that vtkNew will decrement the reference count > >> when you go out of scope in GetCPOList(), so it will be garbage > >> collected and anything using the return value may cause a crash. For > >> your quick proof-of-concept work, use a vtkSmartPointer instead, or > >> even just a raw pointer. > >> > >> Also, SetCPOList takes an int, but shouldn't it take a char* or const > >> char*? > >> > >> Cory > >> > >> On Mon, Aug 18, 2014 at 9:42 AM, Girish Ramesh > >> wrote: > >> > Sorry but I'm still getting a seg fault and I'm not sure why. This is > >> > the > >> > relevant code within the plugin. Thanks. > >> > > >> > XML: > >> > > >> > >> > name="CPOList" > >> > label="CPOList" > >> > command="SetCPOList" > >> > number_of_elements_per_command="1" > >> > information_property="CPOListInfo" > >> > > >> > panel_visibility="default"> > >> > > >> > > >> > >> > name="CPOListInfo"/> > >> > > >> > > >> > > >> > > >> > This property helps select the CPO. > >> > > >> > > >> > > >> > >> > name="CPOListInfo" > >> > label="CPOListInfo" > >> > command="GetCPOList" > >> > information_only="1" > > >> > > >> > > >> > > >> > C++: > >> > > >> > vtkStringArray* ReadUALGrid::GetCPOList(){ > >> > > >> > > >> > vtkNew labels; > >> > > >> > > >> > labels->InsertNextValue("hello"); > >> > labels->InsertNextValue("world"); > >> > > >> > > >> > return labels.GetPointer(); > >> > > >> > } > >> > > >> > void ReadUALGrid::SetCPOList(int index) > >> > > >> > { > >> > > >> > } > >> > > >> > > >> > I'm just using a random vtkStringArray for testing, but it still > >> > segfaults. > >> > Thank you for the help. > >> > > >> > Regards, > >> > Girish > >> > > >> > > >> > > >> > > >> > On 18 August 2014 15:31, Girish Ramesh wrote: > >> >> > >> >> Thank you very much Cory for your help. I guess the forum shall be > >> >> peppered with any more problems I have! > >> >> > >> >> Regards, > >> >> Girish > >> >> > >> >> > >> >> On 18 August 2014 15:29, Cory Quammen > wrote: > >> >>> > >> >>> Girish, > >> >>> > >> >>> Unfortunately, there isn't much documentation about the server > manager > >> >>> XMLs. Finding something that looks like what you are trying to do in > >> >>> the UI and then tracking it down in the XML is currently the best > way. > >> >>> > >> >>> Thanks, > >> >>> Cory > >> >>> > >> >>> On Mon, Aug 18, 2014 at 9:25 AM, Girish Ramesh > > >> >>> wrote: > >> >>> > Dear Cory, > >> >>> > > >> >>> > Thank you very much. Your hints were very helpful. Option 2 was > what > >> >>> > I > >> >>> > was > >> >>> > looking for, but I didn't use the StringListDomain in the second > >> >>> > property to > >> >>> > connect the information. So my plugin was seg faulting repeatedly > >> >>> > even > >> >>> > though I thought my logic was correct. Also, is there any resource > >> >>> > to > >> >>> > find > >> >>> > more about servermanager xmls and how to connect the different > >> >>> > classes > >> >>> > together or is the only option to look at examples. Sorry for the > >> >>> > trouble > >> >>> > :)Thanks again! > >> >>> > > >> >>> > Regards, > >> >>> > Girish > >> >>> > > >> >>> > > >> >>> > > >> >>> > > >> >>> > On 18 August 2014 15:16, Cory Quammen > >> >>> > wrote: > >> >>> >> > >> >>> >> Girish, > >> >>> >> > >> >>> >> Is the list of strings fixed, or can it vary depending on the > file? > >> >>> >> There are three things you can do depending on what you need: > >> >>> >> > >> >>> >> 1). If you have a fixed set of strings, you can use an > >> >>> >> IntVectorProperty, and set its domain as a list of strings with > an > >> >>> >> associated integer, i.e., an enumeration. > >> >>> >> > >> >>> >> >> >>> >> default_values="0" > >> >>> >> name="VariableType" > >> >>> >> number_of_elements="1"> > >> >>> >> > >> >>> >> >> >>> >> value="0" /> > >> >>> >> >> >>> >> value="1" /> > >> >>> >> >> >>> >> value="2" /> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> This generates a combo box in the UI, and only one element can be > >> >>> >> selected at a time. It will expect your reader to have methods > with > >> >>> >> the signature > >> >>> >> > >> >>> >> virtual void SetVariableType(int i); > >> >>> >> virtual int GetVariableType(); > >> >>> >> > >> >>> >> Within your reader, you can use this enumeration value to do > >> >>> >> whatever > >> >>> >> you'd like. > >> >>> >> > >> >>> >> 2). If you just have a list of strings generated in your reader > and > >> >>> >> want to enable the selection of one, you can use a > >> >>> >> StringVectorProperty with a StringListDomain, e.g. > >> >>> >> > >> >>> >> >> >>> >> information_only="1" > >> >>> >> name="DimensionInfo"> > >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> command="SetDimensions" > >> >>> >> name="Dimensions" > >> >>> >> number_of_elements="1" > >> >>> >> panel_visibility="default"> > >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> name="DimensionInfo" /> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> The first property here is an "information-only" property. > ParaView > >> >>> >> will invoke the method "GetAllDimensions" in your reader which > >> >>> >> should > >> >>> >> return a vtkStringArray. The second property is responsible for > >> >>> >> displaying the string array as a combobox, and invokes the method > >> >>> >> "SetDimensions" with the value selected in the combobox. You need > >> >>> >> the > >> >>> >> StringListDomain in the second property to connect the > >> >>> >> information-only property to the second property. > >> >>> >> > >> >>> >> 3). If you need to populate the list depending on what is in the > >> >>> >> file > >> >>> >> and be able to select/deselect list entries (e.g., to pick which > >> >>> >> variables are loaded from the file), then see the XML file > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml > >> >>> >> > >> >>> >> and search for the SourceProxy named "FlashReaderCore". You'll > find > >> >>> >> this XML property definition: > >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> name="CellArrayInfo"> > >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> element_types="2 0" > >> >>> >> information_property="CellArrayInfo" > >> >>> >> label="Cell Arrays" > >> >>> >> name="CellArrayStatus" > >> >>> >> number_of_elements="0" > >> >>> >> number_of_elements_per_command="2" > >> >>> >> repeat_command="1"> > >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> name="CellArrayInfo" /> > >> >>> >> > >> >>> >> > >> >>> >> This property lists which cell-centered > >> >>> >> arrays > >> >>> >> to > >> >>> >> read. > >> >>> >> > >> >>> >> >> >>> >> name="PointArrayInfo"> > >> >>> >> /> > >> >>> >> > >> >>> >> > >> >>> >> This XML is responsible for showing in the GUI the list of > >> >>> >> cell-associated arrays. In the vtkAMRFlashReader, there are a > >> >>> >> number > >> >>> >> of > >> >>> >> methods that are defined to make this work. (These are actually > >> >>> >> defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) > >> >>> >> > >> >>> >> // Description: > >> >>> >> // Get the data array selection tables used to configure which > >> >>> >> data > >> >>> >> // arrays are loaded by the reader. > >> >>> >> vtkGetObjectMacro(CellDataArraySelection, > vtkDataArraySelection); > >> >>> >> > >> >>> >> // Description: > >> >>> >> // Get the number of point or cell arrays available in the > input. > >> >>> >> int GetNumberOfCellArrays(); > >> >>> >> > >> >>> >> // Description: > >> >>> >> // Get the name of the point or cell array with the given index > >> >>> >> in > >> >>> >> // the input. > >> >>> >> const char* GetCellArrayName(int index); > >> >>> >> > >> >>> >> // Description: > >> >>> >> // Get/Set whether the point or cell array with the given name > is > >> >>> >> to > >> >>> >> // be read. > >> >>> >> int GetCellArrayStatus(const char* name); > >> >>> >> void SetCellArrayStatus(const char* name, int status); > >> >>> >> > >> >>> >> The first method listed above might not be necessary in your > >> >>> >> reader; > >> >>> >> I'm not sure. The rest are necessary. > >> >>> >> > >> >>> >> Note in this XML and method definitions that "Cell" is the name > of > >> >>> >> the > >> >>> >> given to the association of array the reader can load. You can > >> >>> >> replace > >> >>> >> all occurrences of "Cell" with whatever name is more appropriate > >> >>> >> for > >> >>> >> your needs. > >> >>> >> > >> >>> >> I hope that helps, > >> >>> >> Cory > >> >>> >> > >> >>> >> On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh > >> >>> >> > >> >>> >> wrote: > >> >>> >> > Hi, > >> >>> >> > > >> >>> >> > I have been breaking my head over this problem for a while now > as > >> >>> >> > there > >> >>> >> > are > >> >>> >> > no servermanager xml explanations anywhere. So, what I want to > >> >>> >> > accomplish is > >> >>> >> > populate a GUI list with a vtkStringArray and be able to select > >> >>> >> > strings > >> >>> >> > within the list in order to fill a variable . Can someone > please > >> >>> >> > help me > >> >>> >> > or > >> >>> >> > point me in the right direction in this task? I am writing my > own > >> >>> >> > plugin > >> >>> >> > reader as you may have understood, but I'm stuck at this point > >> >>> >> > for a > >> >>> >> > while. > >> >>> >> > Thanks. > >> >>> >> > > >> >>> >> > Regards, > >> >>> >> > Girish > >> >>> >> > > >> >>> >> > _______________________________________________ > >> >>> >> > Paraview-developers mailing list > >> >>> >> > Paraview-developers at paraview.org > >> >>> >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >> >>> >> > > >> >>> > > >> >>> > > >> >> > >> >> > >> > > > > > > > > > _______________________________________________ > > 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 rgirish28 at gmail.com Mon Aug 18 11:13:33 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Mon, 18 Aug 2014 17:13:33 +0200 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: There is an additional feature I am interested in, which is using the panel_widget="list" option for listing the strings. It again causes a segfault when change it within the XML. Thanks for the help. Regards, Girish On 18 August 2014 16:44, Girish Ramesh wrote: > Thanks Utkarsh. I was also making the mistake of not allocating the memory > for a SmartPointer as I was changing the code from vtkNew and forgot to > adapt it. I've changed it now and it works finally! Thanks a lot guys. I'll > probably add some documentation for this as there is nothing mentioned in > the Wiki that is close to this at all. > > Regards, > Girish > > > On 18 August 2014 16:26, Utkarsh Ayachit > wrote: > >> Girish, >> >> GetCPOList() is incorrect. You cannot return references to variables >> that go out of scope at the end of the method. Just as a hack, mark >> the labels variable as static and it will work. You should change the >> code to make Labels an >> member variable of the class and return that. >> >> Utkarsh >> >> On Mon, Aug 18, 2014 at 10:19 AM, Girish Ramesh >> wrote: >> > Well, I did try with a vtkSmartPointer but it didn't work either. Still >> > segfaulting. This is the code state at the moment and I can't figure out >> > why! It is definitely the problem of this bit as the rest of the plugin >> is >> > compiling and running without segfaulting. So, I hope you can help me. >> > Thanks. >> > >> > XML: >> > >> > > > name="CPOList" >> > label="CPOList" >> > command="SetCPOList" >> > number_of_elements_per_ >> > command="1" >> > information_property="CPOListInfo" >> > >> > panel_visibility="default"> >> > >> > >> > > > name="CPOListInfo"/> >> > >> > >> > >> > >> > This property helps select the CPO. >> > >> > >> > >> > > > name="CPOListInfo" >> > label="CPOListInfo" >> > command="GetCPOList" >> > information_only="1" > >> > >> > >> > >> > >> > C++: >> > >> > >> > vtkStringArray* ReadUALGrid::GetCPOList(){ >> > >> > >> > vtkSmartPointer labels; >> > >> > >> > >> > labels->InsertNextValue("hello"); >> > labels->InsertNextValue("world"); >> > >> > >> > return labels; >> > >> > } >> > >> > void ReadUALGrid::SetCPOList(const char* name) >> > >> > { >> > >> > } >> > >> > >> > >> > >> > On 18 August 2014 15:49, Cory Quammen wrote: >> >> >> >> The biggest problem is that vtkNew will decrement the reference count >> >> when you go out of scope in GetCPOList(), so it will be garbage >> >> collected and anything using the return value may cause a crash. For >> >> your quick proof-of-concept work, use a vtkSmartPointer instead, or >> >> even just a raw pointer. >> >> >> >> Also, SetCPOList takes an int, but shouldn't it take a char* or const >> >> char*? >> >> >> >> Cory >> >> >> >> On Mon, Aug 18, 2014 at 9:42 AM, Girish Ramesh >> >> wrote: >> >> > Sorry but I'm still getting a seg fault and I'm not sure why. This is >> >> > the >> >> > relevant code within the plugin. Thanks. >> >> > >> >> > XML: >> >> > >> >> > > >> > name="CPOList" >> >> > label="CPOList" >> >> > command="SetCPOList" >> >> > number_of_elements_per_command="1" >> >> > information_property="CPOListInfo" >> >> > >> >> > panel_visibility="default"> >> >> > >> >> > >> >> > > >> > name="CPOListInfo"/> >> >> > >> >> > >> >> > >> >> > >> >> > This property helps select the CPO. >> >> > >> >> > >> >> > >> >> > > >> > name="CPOListInfo" >> >> > label="CPOListInfo" >> >> > command="GetCPOList" >> >> > information_only="1" > >> >> > >> >> > >> >> > >> >> > C++: >> >> > >> >> > vtkStringArray* ReadUALGrid::GetCPOList(){ >> >> > >> >> > >> >> > vtkNew labels; >> >> > >> >> > >> >> > labels->InsertNextValue("hello"); >> >> > labels->InsertNextValue("world"); >> >> > >> >> > >> >> > return labels.GetPointer(); >> >> > >> >> > } >> >> > >> >> > void ReadUALGrid::SetCPOList(int index) >> >> > >> >> > { >> >> > >> >> > } >> >> > >> >> > >> >> > I'm just using a random vtkStringArray for testing, but it still >> >> > segfaults. >> >> > Thank you for the help. >> >> > >> >> > Regards, >> >> > Girish >> >> > >> >> > >> >> > >> >> > >> >> > On 18 August 2014 15:31, Girish Ramesh wrote: >> >> >> >> >> >> Thank you very much Cory for your help. I guess the forum shall be >> >> >> peppered with any more problems I have! >> >> >> >> >> >> Regards, >> >> >> Girish >> >> >> >> >> >> >> >> >> On 18 August 2014 15:29, Cory Quammen >> wrote: >> >> >>> >> >> >>> Girish, >> >> >>> >> >> >>> Unfortunately, there isn't much documentation about the server >> manager >> >> >>> XMLs. Finding something that looks like what you are trying to do >> in >> >> >>> the UI and then tracking it down in the XML is currently the best >> way. >> >> >>> >> >> >>> Thanks, >> >> >>> Cory >> >> >>> >> >> >>> On Mon, Aug 18, 2014 at 9:25 AM, Girish Ramesh < >> rgirish28 at gmail.com> >> >> >>> wrote: >> >> >>> > Dear Cory, >> >> >>> > >> >> >>> > Thank you very much. Your hints were very helpful. Option 2 was >> what >> >> >>> > I >> >> >>> > was >> >> >>> > looking for, but I didn't use the StringListDomain in the second >> >> >>> > property to >> >> >>> > connect the information. So my plugin was seg faulting repeatedly >> >> >>> > even >> >> >>> > though I thought my logic was correct. Also, is there any >> resource >> >> >>> > to >> >> >>> > find >> >> >>> > more about servermanager xmls and how to connect the different >> >> >>> > classes >> >> >>> > together or is the only option to look at examples. Sorry for the >> >> >>> > trouble >> >> >>> > :)Thanks again! >> >> >>> > >> >> >>> > Regards, >> >> >>> > Girish >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > On 18 August 2014 15:16, Cory Quammen >> >> >>> > wrote: >> >> >>> >> >> >> >>> >> Girish, >> >> >>> >> >> >> >>> >> Is the list of strings fixed, or can it vary depending on the >> file? >> >> >>> >> There are three things you can do depending on what you need: >> >> >>> >> >> >> >>> >> 1). If you have a fixed set of strings, you can use an >> >> >>> >> IntVectorProperty, and set its domain as a list of strings with >> an >> >> >>> >> associated integer, i.e., an enumeration. >> >> >>> >> >> >> >>> >> > >> >>> >> default_values="0" >> >> >>> >> name="VariableType" >> >> >>> >> number_of_elements="1"> >> >> >>> >> >> >> >>> >> > >> >>> >> value="0" /> >> >> >>> >> > >> >>> >> value="1" /> >> >> >>> >> > >> >>> >> value="2" /> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> This generates a combo box in the UI, and only one element can >> be >> >> >>> >> selected at a time. It will expect your reader to have methods >> with >> >> >>> >> the signature >> >> >>> >> >> >> >>> >> virtual void SetVariableType(int i); >> >> >>> >> virtual int GetVariableType(); >> >> >>> >> >> >> >>> >> Within your reader, you can use this enumeration value to do >> >> >>> >> whatever >> >> >>> >> you'd like. >> >> >>> >> >> >> >>> >> 2). If you just have a list of strings generated in your reader >> and >> >> >>> >> want to enable the selection of one, you can use a >> >> >>> >> StringVectorProperty with a StringListDomain, e.g. >> >> >>> >> >> >> >>> >> > >> >>> >> information_only="1" >> >> >>> >> name="DimensionInfo"> >> >> >>> >> >> >> >>> >> >> >> >>> >> > >> >>> >> command="SetDimensions" >> >> >>> >> name="Dimensions" >> >> >>> >> number_of_elements="1" >> >> >>> >> panel_visibility="default"> >> >> >>> >> >> >> >>> >> >> >> >>> >> > >> >>> >> name="DimensionInfo" /> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> The first property here is an "information-only" property. >> ParaView >> >> >>> >> will invoke the method "GetAllDimensions" in your reader which >> >> >>> >> should >> >> >>> >> return a vtkStringArray. The second property is responsible for >> >> >>> >> displaying the string array as a combobox, and invokes the >> method >> >> >>> >> "SetDimensions" with the value selected in the combobox. You >> need >> >> >>> >> the >> >> >>> >> StringListDomain in the second property to connect the >> >> >>> >> information-only property to the second property. >> >> >>> >> >> >> >>> >> 3). If you need to populate the list depending on what is in the >> >> >>> >> file >> >> >>> >> and be able to select/deselect list entries (e.g., to pick which >> >> >>> >> variables are loaded from the file), then see the XML file >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml >> >> >>> >> >> >> >>> >> and search for the SourceProxy named "FlashReaderCore". You'll >> find >> >> >>> >> this XML property definition: >> >> >>> >> >> >> >>> >> >> >> >>> >> > >> >>> >> name="CellArrayInfo"> >> >> >>> >> > /> >> >> >>> >> >> >> >>> >> > >> >>> >> element_types="2 0" >> >> >>> >> information_property="CellArrayInfo" >> >> >>> >> label="Cell Arrays" >> >> >>> >> name="CellArrayStatus" >> >> >>> >> number_of_elements="0" >> >> >>> >> number_of_elements_per_command="2" >> >> >>> >> repeat_command="1"> >> >> >>> >> >> >> >>> >> >> >> >>> >> > >> >>> >> name="CellArrayInfo" /> >> >> >>> >> >> >> >>> >> >> >> >>> >> This property lists which cell-centered >> >> >>> >> arrays >> >> >>> >> to >> >> >>> >> read. >> >> >>> >> >> >> >>> >> > >> >>> >> name="PointArrayInfo"> >> >> >>> >> > /> >> >> >>> >> >> >> >>> >> >> >> >>> >> This XML is responsible for showing in the GUI the list of >> >> >>> >> cell-associated arrays. In the vtkAMRFlashReader, there are a >> >> >>> >> number >> >> >>> >> of >> >> >>> >> methods that are defined to make this work. (These are actually >> >> >>> >> defined in vtkAMRFlashReader's parent class, vtkAMRBaseReader.h) >> >> >>> >> >> >> >>> >> // Description: >> >> >>> >> // Get the data array selection tables used to configure which >> >> >>> >> data >> >> >>> >> // arrays are loaded by the reader. >> >> >>> >> vtkGetObjectMacro(CellDataArraySelection, >> vtkDataArraySelection); >> >> >>> >> >> >> >>> >> // Description: >> >> >>> >> // Get the number of point or cell arrays available in the >> input. >> >> >>> >> int GetNumberOfCellArrays(); >> >> >>> >> >> >> >>> >> // Description: >> >> >>> >> // Get the name of the point or cell array with the given >> index >> >> >>> >> in >> >> >>> >> // the input. >> >> >>> >> const char* GetCellArrayName(int index); >> >> >>> >> >> >> >>> >> // Description: >> >> >>> >> // Get/Set whether the point or cell array with the given >> name is >> >> >>> >> to >> >> >>> >> // be read. >> >> >>> >> int GetCellArrayStatus(const char* name); >> >> >>> >> void SetCellArrayStatus(const char* name, int status); >> >> >>> >> >> >> >>> >> The first method listed above might not be necessary in your >> >> >>> >> reader; >> >> >>> >> I'm not sure. The rest are necessary. >> >> >>> >> >> >> >>> >> Note in this XML and method definitions that "Cell" is the name >> of >> >> >>> >> the >> >> >>> >> given to the association of array the reader can load. You can >> >> >>> >> replace >> >> >>> >> all occurrences of "Cell" with whatever name is more appropriate >> >> >>> >> for >> >> >>> >> your needs. >> >> >>> >> >> >> >>> >> I hope that helps, >> >> >>> >> Cory >> >> >>> >> >> >> >>> >> On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh >> >> >>> >> >> >> >>> >> wrote: >> >> >>> >> > Hi, >> >> >>> >> > >> >> >>> >> > I have been breaking my head over this problem for a while >> now as >> >> >>> >> > there >> >> >>> >> > are >> >> >>> >> > no servermanager xml explanations anywhere. So, what I want to >> >> >>> >> > accomplish is >> >> >>> >> > populate a GUI list with a vtkStringArray and be able to >> select >> >> >>> >> > strings >> >> >>> >> > within the list in order to fill a variable . Can someone >> please >> >> >>> >> > help me >> >> >>> >> > or >> >> >>> >> > point me in the right direction in this task? I am writing my >> own >> >> >>> >> > plugin >> >> >>> >> > reader as you may have understood, but I'm stuck at this point >> >> >>> >> > for a >> >> >>> >> > while. >> >> >>> >> > Thanks. >> >> >>> >> > >> >> >>> >> > Regards, >> >> >>> >> > Girish >> >> >>> >> > >> >> >>> >> > _______________________________________________ >> >> >>> >> > Paraview-developers mailing list >> >> >>> >> > Paraview-developers at paraview.org >> >> >>> >> > >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> >>> >> > >> >> >>> > >> >> >>> > >> >> >> >> >> >> >> >> > >> > >> > >> > >> > _______________________________________________ >> > 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 sankhesh.jhaveri at kitware.com Mon Aug 18 12:31:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Mon, 18 Aug 2014 09:31:05 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Sunday, August 17 2014 Message-ID: <20140818163103.8CFCC815FA@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Win7x64-ninja-nightlymaster-static-release 4 [2]Win7x64-vs9-nightlymaster-shared-release 1 [3]fedora-x64-icc-nightlymaster-debug 10 -------------------- REPORT -------------------- 14 FAILURES [4]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [5]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [6]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [7]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [9]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [10]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [11]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [12]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [13]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [14]pv.LogColorMap , 1 , ['fedora-x64-icc-nightlymaster-debug'] [15]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [16]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 1 , ['fedora-x64-icc-nightlymaster-debug'] [17]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 2 , ['Win7x64-ninja-nightlymaster-static-release', 'Win7x64-vs9-nightlymaster-shared-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [18]Lion-gcc-pvVTK 7 [19]Win7x64-vs9-nightlynext-static-release 3 [20]fedora-x64-icc-nightlynext-release 12 [21]Win32-vs9-shared-release 1 -------------------- REPORT -------------------- 22 FAILURES [22]pvcs.CatalystLiveSetBreakpoint , 1 , ['Lion-gcc-pvVTK'] [23]pvcs.HistogramSelection , 1 , ['Lion-gcc-pvVTK'] [24]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [25]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [26]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 1 , ['Lion-gcc-pvVTK'] [27]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [28]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [29]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [30]pvcs.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [31]pv.CatalystLiveSetBreakpoint , 1 , ['Lion-gcc-pvVTK'] [32]pvcrs.HistogramSelection , 1 , ['Lion-gcc-pvVTK'] [33]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [34]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [35]pvcrs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [36]pv.OpenHelp , 1 , ['Win32-vs9-shared-release'] [37]pv.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [38]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [39]pvcs.TestPythonView , 1 , ['fedora-x64-icc-nightlynext-release'] [40]pv.ProbePicking , 1 , ['fedora-x64-icc-nightlynext-release'] [41]pv.HistogramSelection , 1 , ['Lion-gcc-pvVTK'] [42]pvcs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [43]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 2 , ['Lion-gcc-pvVTK', 'fedora-x64-icc-nightlynext-release'] Issues with submitters The following expected submitters did not submit: kamino.kitware , Mac10.7.5-gcc-nightlymaster-release kamino.kitware , Mac10.7.5-clang-nightlymaster-release References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-18&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-08-18&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release 3. http://open.cdash.org/index.php?project=ParaView&date=2014-08-18&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 4. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs.ProbePicking 5. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcrs.TestPythonView 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.LoadStateMultiView 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.ProbePicking 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=SurfaceLIC-ShuttleZoom2-Batch 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.TestPythonView 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=SurfaceLIC-ShuttleZoom1-Batch 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcrs.LoadStateMultiView 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=SurfaceLIC-ShuttleAll-Batch 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs.TestPythonView 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.LogColorMap 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs.LoadStateMultiView 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks 18. http://open.cdash.org/index.php?project=ParaView&date=2014-08-18&filtercount=1&field1=buildname/string&compare1=61&value1=Lion-gcc-pvVTK 19. http://open.cdash.org/index.php?project=ParaView&date=2014-08-18&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 20. http://open.cdash.org/index.php?project=ParaView&date=2014-08-18&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 21. http://open.cdash.org/index.php?project=ParaView&date=2014-08-18&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 22. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs.CatalystLiveSetBreakpoint 23. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs.HistogramSelection 24. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcrs.UndoRedo1 25. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=SurfaceLIC-ShuttleAll-Batch 26. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 27. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs.LoadStateMultiView 28. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.LoadStateMultiView 29. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=SurfaceLIC-ShuttleZoom2-Batch 30. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs.ProbePicking 31. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.CatalystLiveSetBreakpoint 32. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcrs.HistogramSelection 33. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcrs.LoadStateMultiView 34. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.UndoRedo1 35. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcrs.TestPythonView 36. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.OpenHelp 37. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.TestPythonView 38. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=SurfaceLIC-ShuttleZoom1-Batch 39. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs.TestPythonView 40. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.ProbePicking 41. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pv.HistogramSelection 42. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs.UndoRedo1 43. http://open.cdash.org/testSummary.php?project=9&date=2014-08-18&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From panos.asproulis at gmail.com Mon Aug 18 12:54:50 2014 From: panos.asproulis at gmail.com (Panos Asproulis) Date: Mon, 18 Aug 2014 18:54:50 +0200 Subject: [Paraview-developers] Trying to compile a GUI plugin Message-ID: <53F22FDA.1080209@gmail.com> Hi all, I am trying to create a GUI plugin and for that purpose I am looking at the SourceToolbar example in the Examples subdirectory. This compiles fine when using the CMake system with the Examples Build option enabled. I then copied the SourceToolbar folder to the Plugins folder of ParaView and added the following plugin.cmake file: pv_plugin(SourceToolbar DESCRIPTION "Testing plugin" DEFAULT_ENABLED) I did the CMake configuration step, which reported that it was also going to build the "SourceToolbar" plugin: Plugin: SourceToolbar - Testing plugin : Enabled I then generated the Makefiles and started the build. I get the following error message: /home/panos/Development/ParaView/ParaView-v4.1.0-bin/Plugins/SourceToolbar/SourceToolbarActionsImplementation.h:46: Error: Undefined interface make[2]: *** [Plugins/SourceToolbar/moc_SourceToolbarActionsImplementation.cxx] Error 1 Why would the same code compiles correctly when in the Examples directory and fails when in the Plugins directory? -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgirish28 at gmail.com Tue Aug 19 04:01:07 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Tue, 19 Aug 2014 10:01:07 +0200 Subject: [Paraview-developers] Populating a servermanager list widget with string array Message-ID: Hi, As an addition to a previous query on the developers forum (Servermanager XML: Displaying a list of strings along with selection), I would like to add another query. I would like to use the panel_widget option in the servermanager XML with a String Array, but whenever I try to do it, it doesn't display anything. So, I'm wondering how it can be done even though it works with a normal StringVectorProperty. Thank you. The XML and screenshot is given below. XML: This property specifies the CPO on the UAL Database. Screenshot of option working with default widget: https://imageshack.com/i/eyhM3mFKp Regards, Girish -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgirish28 at gmail.com Tue Aug 19 04:59:20 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Tue, 19 Aug 2014 10:59:20 +0200 Subject: [Paraview-developers] Servermanager XML: Displaying a list of strings along with selection In-Reply-To: References: Message-ID: Also, I would like to know whether it is possible to select multiple values within the stringlist property i.e multiple values out of the drop down box/list. Would I have to use an ArraySelectionDomain for that purpose? Thanks. On 18 August 2014 17:13, Girish Ramesh wrote: > There is an additional feature I am interested in, which is using the > panel_widget="list" option for listing the strings. It again causes a > segfault when change it within the XML. Thanks for the help. > > Regards, > Girish > > > On 18 August 2014 16:44, Girish Ramesh wrote: > >> Thanks Utkarsh. I was also making the mistake of not allocating the >> memory for a SmartPointer as I was changing the code from vtkNew and forgot >> to adapt it. I've changed it now and it works finally! Thanks a lot guys. >> I'll probably add some documentation for this as there is nothing mentioned >> in the Wiki that is close to this at all. >> >> Regards, >> Girish >> >> >> On 18 August 2014 16:26, Utkarsh Ayachit >> wrote: >> >>> Girish, >>> >>> GetCPOList() is incorrect. You cannot return references to variables >>> that go out of scope at the end of the method. Just as a hack, mark >>> the labels variable as static and it will work. You should change the >>> code to make Labels an >>> member variable of the class and return that. >>> >>> Utkarsh >>> >>> On Mon, Aug 18, 2014 at 10:19 AM, Girish Ramesh >>> wrote: >>> > Well, I did try with a vtkSmartPointer but it didn't work either. Still >>> > segfaulting. This is the code state at the moment and I can't figure >>> out >>> > why! It is definitely the problem of this bit as the rest of the >>> plugin is >>> > compiling and running without segfaulting. So, I hope you can help me. >>> > Thanks. >>> > >>> > XML: >>> > >>> > >> > name="CPOList" >>> > label="CPOList" >>> > command="SetCPOList" >>> > number_of_elements_per_ >>> > command="1" >>> > information_property="CPOListInfo" >>> > >>> > panel_visibility="default"> >>> > >>> > >>> > >> > name="CPOListInfo"/> >>> > >>> > >>> > >>> > >>> > This property helps select the CPO. >>> > >>> > >>> > >>> > >> > name="CPOListInfo" >>> > label="CPOListInfo" >>> > command="GetCPOList" >>> > information_only="1" > >>> > >>> > >>> > >>> > >>> > C++: >>> > >>> > >>> > vtkStringArray* ReadUALGrid::GetCPOList(){ >>> > >>> > >>> > vtkSmartPointer labels; >>> > >>> > >>> > >>> > labels->InsertNextValue("hello"); >>> > labels->InsertNextValue("world"); >>> > >>> > >>> > return labels; >>> > >>> > } >>> > >>> > void ReadUALGrid::SetCPOList(const char* name) >>> > >>> > { >>> > >>> > } >>> > >>> > >>> > >>> > >>> > On 18 August 2014 15:49, Cory Quammen >>> wrote: >>> >> >>> >> The biggest problem is that vtkNew will decrement the reference count >>> >> when you go out of scope in GetCPOList(), so it will be garbage >>> >> collected and anything using the return value may cause a crash. For >>> >> your quick proof-of-concept work, use a vtkSmartPointer instead, or >>> >> even just a raw pointer. >>> >> >>> >> Also, SetCPOList takes an int, but shouldn't it take a char* or const >>> >> char*? >>> >> >>> >> Cory >>> >> >>> >> On Mon, Aug 18, 2014 at 9:42 AM, Girish Ramesh >>> >> wrote: >>> >> > Sorry but I'm still getting a seg fault and I'm not sure why. This >>> is >>> >> > the >>> >> > relevant code within the plugin. Thanks. >>> >> > >>> >> > XML: >>> >> > >>> >> > >> >> > name="CPOList" >>> >> > label="CPOList" >>> >> > command="SetCPOList" >>> >> > number_of_elements_per_command="1" >>> >> > information_property="CPOListInfo" >>> >> > >>> >> > panel_visibility="default"> >>> >> > >>> >> > >>> >> > >> >> > name="CPOListInfo"/> >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > This property helps select the CPO. >>> >> > >>> >> > >>> >> > >>> >> > >> >> > name="CPOListInfo" >>> >> > label="CPOListInfo" >>> >> > command="GetCPOList" >>> >> > information_only="1" > >>> >> > >>> >> > >>> >> > >>> >> > C++: >>> >> > >>> >> > vtkStringArray* ReadUALGrid::GetCPOList(){ >>> >> > >>> >> > >>> >> > vtkNew labels; >>> >> > >>> >> > >>> >> > labels->InsertNextValue("hello"); >>> >> > labels->InsertNextValue("world"); >>> >> > >>> >> > >>> >> > return labels.GetPointer(); >>> >> > >>> >> > } >>> >> > >>> >> > void ReadUALGrid::SetCPOList(int index) >>> >> > >>> >> > { >>> >> > >>> >> > } >>> >> > >>> >> > >>> >> > I'm just using a random vtkStringArray for testing, but it still >>> >> > segfaults. >>> >> > Thank you for the help. >>> >> > >>> >> > Regards, >>> >> > Girish >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > On 18 August 2014 15:31, Girish Ramesh wrote: >>> >> >> >>> >> >> Thank you very much Cory for your help. I guess the forum shall be >>> >> >> peppered with any more problems I have! >>> >> >> >>> >> >> Regards, >>> >> >> Girish >>> >> >> >>> >> >> >>> >> >> On 18 August 2014 15:29, Cory Quammen >>> wrote: >>> >> >>> >>> >> >>> Girish, >>> >> >>> >>> >> >>> Unfortunately, there isn't much documentation about the server >>> manager >>> >> >>> XMLs. Finding something that looks like what you are trying to do >>> in >>> >> >>> the UI and then tracking it down in the XML is currently the best >>> way. >>> >> >>> >>> >> >>> Thanks, >>> >> >>> Cory >>> >> >>> >>> >> >>> On Mon, Aug 18, 2014 at 9:25 AM, Girish Ramesh < >>> rgirish28 at gmail.com> >>> >> >>> wrote: >>> >> >>> > Dear Cory, >>> >> >>> > >>> >> >>> > Thank you very much. Your hints were very helpful. Option 2 was >>> what >>> >> >>> > I >>> >> >>> > was >>> >> >>> > looking for, but I didn't use the StringListDomain in the second >>> >> >>> > property to >>> >> >>> > connect the information. So my plugin was seg faulting >>> repeatedly >>> >> >>> > even >>> >> >>> > though I thought my logic was correct. Also, is there any >>> resource >>> >> >>> > to >>> >> >>> > find >>> >> >>> > more about servermanager xmls and how to connect the different >>> >> >>> > classes >>> >> >>> > together or is the only option to look at examples. Sorry for >>> the >>> >> >>> > trouble >>> >> >>> > :)Thanks again! >>> >> >>> > >>> >> >>> > Regards, >>> >> >>> > Girish >>> >> >>> > >>> >> >>> > >>> >> >>> > >>> >> >>> > >>> >> >>> > On 18 August 2014 15:16, Cory Quammen >> > >>> >> >>> > wrote: >>> >> >>> >> >>> >> >>> >> Girish, >>> >> >>> >> >>> >> >>> >> Is the list of strings fixed, or can it vary depending on the >>> file? >>> >> >>> >> There are three things you can do depending on what you need: >>> >> >>> >> >>> >> >>> >> 1). If you have a fixed set of strings, you can use an >>> >> >>> >> IntVectorProperty, and set its domain as a list of strings >>> with an >>> >> >>> >> associated integer, i.e., an enumeration. >>> >> >>> >> >>> >> >>> >> >> >> >>> >> default_values="0" >>> >> >>> >> name="VariableType" >>> >> >>> >> number_of_elements="1"> >>> >> >>> >> >>> >> >>> >> >> >> >>> >> value="0" /> >>> >> >>> >> >> >> >>> >> value="1" /> >>> >> >>> >> >> >> >>> >> value="2" /> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> This generates a combo box in the UI, and only one element can >>> be >>> >> >>> >> selected at a time. It will expect your reader to have methods >>> with >>> >> >>> >> the signature >>> >> >>> >> >>> >> >>> >> virtual void SetVariableType(int i); >>> >> >>> >> virtual int GetVariableType(); >>> >> >>> >> >>> >> >>> >> Within your reader, you can use this enumeration value to do >>> >> >>> >> whatever >>> >> >>> >> you'd like. >>> >> >>> >> >>> >> >>> >> 2). If you just have a list of strings generated in your >>> reader and >>> >> >>> >> want to enable the selection of one, you can use a >>> >> >>> >> StringVectorProperty with a StringListDomain, e.g. >>> >> >>> >> >>> >> >>> >> >> >> >>> >> information_only="1" >>> >> >>> >> name="DimensionInfo"> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >> >> >>> >> command="SetDimensions" >>> >> >>> >> name="Dimensions" >>> >> >>> >> number_of_elements="1" >>> >> >>> >> panel_visibility="default"> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >> >> >>> >> name="DimensionInfo" /> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> The first property here is an "information-only" property. >>> ParaView >>> >> >>> >> will invoke the method "GetAllDimensions" in your reader which >>> >> >>> >> should >>> >> >>> >> return a vtkStringArray. The second property is responsible for >>> >> >>> >> displaying the string array as a combobox, and invokes the >>> method >>> >> >>> >> "SetDimensions" with the value selected in the combobox. You >>> need >>> >> >>> >> the >>> >> >>> >> StringListDomain in the second property to connect the >>> >> >>> >> information-only property to the second property. >>> >> >>> >> >>> >> >>> >> 3). If you need to populate the list depending on what is in >>> the >>> >> >>> >> file >>> >> >>> >> and be able to select/deselect list entries (e.g., to pick >>> which >>> >> >>> >> variables are loaded from the file), then see the XML file >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml >>> >> >>> >> >>> >> >>> >> and search for the SourceProxy named "FlashReaderCore". You'll >>> find >>> >> >>> >> this XML property definition: >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >> >> >>> >> name="CellArrayInfo"> >>> >> >>> >> >> /> >>> >> >>> >> >>> >> >>> >> >> >> >>> >> element_types="2 0" >>> >> >>> >> >>> information_property="CellArrayInfo" >>> >> >>> >> label="Cell Arrays" >>> >> >>> >> name="CellArrayStatus" >>> >> >>> >> number_of_elements="0" >>> >> >>> >> number_of_elements_per_command="2" >>> >> >>> >> repeat_command="1"> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >> >> >>> >> name="CellArrayInfo" /> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> This property lists which cell-centered >>> >> >>> >> arrays >>> >> >>> >> to >>> >> >>> >> read. >>> >> >>> >> >>> >> >>> >> >> >> >>> >> name="PointArrayInfo"> >>> >> >>> >> >> attribute_name="Point" /> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> This XML is responsible for showing in the GUI the list of >>> >> >>> >> cell-associated arrays. In the vtkAMRFlashReader, there are a >>> >> >>> >> number >>> >> >>> >> of >>> >> >>> >> methods that are defined to make this work. (These are actually >>> >> >>> >> defined in vtkAMRFlashReader's parent class, >>> vtkAMRBaseReader.h) >>> >> >>> >> >>> >> >>> >> // Description: >>> >> >>> >> // Get the data array selection tables used to configure >>> which >>> >> >>> >> data >>> >> >>> >> // arrays are loaded by the reader. >>> >> >>> >> vtkGetObjectMacro(CellDataArraySelection, >>> vtkDataArraySelection); >>> >> >>> >> >>> >> >>> >> // Description: >>> >> >>> >> // Get the number of point or cell arrays available in the >>> input. >>> >> >>> >> int GetNumberOfCellArrays(); >>> >> >>> >> >>> >> >>> >> // Description: >>> >> >>> >> // Get the name of the point or cell array with the given >>> index >>> >> >>> >> in >>> >> >>> >> // the input. >>> >> >>> >> const char* GetCellArrayName(int index); >>> >> >>> >> >>> >> >>> >> // Description: >>> >> >>> >> // Get/Set whether the point or cell array with the given >>> name is >>> >> >>> >> to >>> >> >>> >> // be read. >>> >> >>> >> int GetCellArrayStatus(const char* name); >>> >> >>> >> void SetCellArrayStatus(const char* name, int status); >>> >> >>> >> >>> >> >>> >> The first method listed above might not be necessary in your >>> >> >>> >> reader; >>> >> >>> >> I'm not sure. The rest are necessary. >>> >> >>> >> >>> >> >>> >> Note in this XML and method definitions that "Cell" is the >>> name of >>> >> >>> >> the >>> >> >>> >> given to the association of array the reader can load. You can >>> >> >>> >> replace >>> >> >>> >> all occurrences of "Cell" with whatever name is more >>> appropriate >>> >> >>> >> for >>> >> >>> >> your needs. >>> >> >>> >> >>> >> >>> >> I hope that helps, >>> >> >>> >> Cory >>> >> >>> >> >>> >> >>> >> On Mon, Aug 18, 2014 at 5:46 AM, Girish Ramesh >>> >> >>> >> >>> >> >>> >> wrote: >>> >> >>> >> > Hi, >>> >> >>> >> > >>> >> >>> >> > I have been breaking my head over this problem for a while >>> now as >>> >> >>> >> > there >>> >> >>> >> > are >>> >> >>> >> > no servermanager xml explanations anywhere. So, what I want >>> to >>> >> >>> >> > accomplish is >>> >> >>> >> > populate a GUI list with a vtkStringArray and be able to >>> select >>> >> >>> >> > strings >>> >> >>> >> > within the list in order to fill a variable . Can someone >>> please >>> >> >>> >> > help me >>> >> >>> >> > or >>> >> >>> >> > point me in the right direction in this task? I am writing >>> my own >>> >> >>> >> > plugin >>> >> >>> >> > reader as you may have understood, but I'm stuck at this >>> point >>> >> >>> >> > for a >>> >> >>> >> > while. >>> >> >>> >> > Thanks. >>> >> >>> >> > >>> >> >>> >> > Regards, >>> >> >>> >> > Girish >>> >> >>> >> > >>> >> >>> >> > _______________________________________________ >>> >> >>> >> > Paraview-developers mailing list >>> >> >>> >> > Paraview-developers at paraview.org >>> >> >>> >> > >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >> >>> >> > >>> >> >>> > >>> >> >>> > >>> >> >> >>> >> >> >>> >> > >>> > >>> > >>> > >>> > _______________________________________________ >>> > 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 redkite at virgin.net Tue Aug 19 04:51:24 2014 From: redkite at virgin.net (redkite) Date: Tue, 19 Aug 2014 09:51:24 +0100 Subject: [Paraview-developers] paraview plugin with VS 2010 Message-ID: <53F3100C.5010001@virgin.net> Hi, I've been developing a plugin for FE analysis a little like the SLAC tool but for our own purposes. This seems to work well on Ubuntu, but I have an issue under Windows 7/VS 2010. In particular, I made use several times of the call at:- pqFiltersMenuReaction::createFilter to allow the correct inputs/outputs to be set. This appears (to me) to be available through the "__declspec(dllimport)" -- etc -- qualifications but leaves me with the following error: VoxFETools had to comment line filter = pqFiltersMenuReaction::createFilter( QString("filters"), QString("OutputSolverScript") ); ~L590 pqVoxFEManager.cxx Linkage error: 2>pqVoxFEManager.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: static class pqPipelineSource * __cdecl pqFiltersMenuReaction::createFilter(class QString const &,class QString const &)" (__imp_?createFilter at pqFiltersMenuReaction@@SAPEAVpqPipelineSource@@AEBVQString@@0 at Z) 2>C:\Temp\build\VoxFETools_vs2010\Debug\VoxFETools.dll : fatal error LNK1120: 1 unresolved externals To make things worse, if I remove the pqFiltersMenuReaction call, Paraview and the plugin both seem to build ok -- but -- on attempting to load the plugin I get:- ERROR: In ..\..\..\..\..\src\ParaView-v4.1.0\ParaViewCore\ClientServerCore\Core\vtkPVPluginLoader.cxx, line 302 vtkPVPluginLoader (00000000068A7920): The specified module could not be found. The SLAC and other built in plugins seem to work fine. AFAICT the correct Qt/Paraview build flags have been set, but maybe I've missed something ....? regards, Richard From utkarsh.ayachit at kitware.com Tue Aug 19 09:46:02 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 19 Aug 2014 09:46:02 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: SUMMARY --------------------------------------------- Topics merged into master: 14926_fix_zoom_to_data_icon catalyst-edition-ordering catalyst-missing-proxy fragments_meta_filter (VTK) introduce_histogram_representation live-breakpoint From sankhesh.jhaveri at kitware.com Tue Aug 19 12:31:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Tue, 19 Aug 2014 09:31:05 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Monday, August 18 2014 Message-ID: <20140819163103.845FE811FB@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-clang-nightlymaster-release 14 [2]Mac10.7.5-gcc-nightlymaster-release 11 [3]Win7x64-vs9-nightlymaster-shared-release 1 [4]Win7x64-ninja-nightlymaster-static-release 4 [5]fedora-x64-icc-nightlymaster-debug 5 -------------------- REPORT -------------------- 14 FAILURES [6]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [7]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]pvcrs.RenderNan , 1 , ['fedora-x64-icc-nightlymaster-debug'] [9]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [10]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [11]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [12]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [13]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter , 2 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [14]pvcs.CatalystLiveSetBreakpoint , 4 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [15]pqWidgetspqTextEditTest , 4 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [16]pv.CatalystLiveSetBreakpoint , 4 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [17]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 4 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release'] [18]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 5 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'fedora-x64-icc-nightlymaster-debug'] [19]vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks , 5 , ['Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release', 'Mac10.7.5-gcc-nightlymaster-release', 'Win7x64-vs9-nightlymaster-shared-release', 'Win7x64-ninja-nightlymaster-static-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [20]Win64-vs9-static-release 1 [21]fedora-x64-icc-nightlynext-release 7 [22]Win7x64-vs9-nightlynext-static-release 3 -------------------- REPORT -------------------- 11 FAILURES [23]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [24]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [25]pv.OpenHelp , 1 , ['Win64-vs9-static-release'] [26]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [27]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [28]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [29]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [30]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 1 , ['fedora-x64-icc-nightlynext-release'] [31]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [32]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [33]pvcs.UndoRedo1 , 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-08-19&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-08-19&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-08-19&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release 4. http://open.cdash.org/index.php?project=ParaView&date=2014-08-19&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 5. http://open.cdash.org/index.php?project=ParaView&date=2014-08-19&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcrs.LoadStateMultiView 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pv.LoadStateMultiView 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcrs.RenderNan 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=SurfaceLIC-ShuttleZoom2-Batch 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=SurfaceLIC-ShuttleZoom1-Batch 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=SurfaceLIC-ShuttleAll-Batch 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcs.LoadStateMultiView 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcs.CatalystLiveSetBreakpoint 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pqWidgetspqTextEditTest 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pv.CatalystLiveSetBreakpoint 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 19. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=vtkPVServerManagerDefaultPython-GhostCellsInMergeBlocks 20. http://open.cdash.org/index.php?project=ParaView&date=2014-08-19&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release 21. http://open.cdash.org/index.php?project=ParaView&date=2014-08-19&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 22. http://open.cdash.org/index.php?project=ParaView&date=2014-08-19&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 23. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcrs.LoadStateMultiView 24. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pv.LoadStateMultiView 25. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pv.OpenHelp 26. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=SurfaceLIC-ShuttleZoom2-Batch 27. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcrs.UndoRedo1 28. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=SurfaceLIC-ShuttleZoom1-Batch 29. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=SurfaceLIC-ShuttleAll-Batch 30. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 31. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pv.UndoRedo1 32. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcs.LoadStateMultiView 33. http://open.cdash.org/testSummary.php?project=9&date=2014-08-19&name=pvcs.UndoRedo1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 20 08:46:08 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 20 Aug 2014 08:46:08 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: SUMMARY --------------------------------------------- Topics merged into master: 14279_fix_rand_on_windows_attempt_2 14813_fix_mode_shapes_range catalyst-updates --------------------------------------------- Topics reverted from next: catalyst-script-plugin-client From sankhesh.jhaveri at kitware.com Wed Aug 20 12:31:08 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Wed, 20 Aug 2014 09:31:08 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Tuesday, August 19 2014 Message-ID: <20140820163104.29C7580030@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Win7x64-ninja-nightlymaster-static-release 3 [2]Mac10.7.5-gcc-nightlymaster-release 6 [3]ubuntu-x64-nightlymaster 1 [4]fedora-x64-icc-nightlymaster-debug 4 [5]Mac10.7.5-clang-nightlymaster-release 7 -------------------- REPORT -------------------- 14 FAILURES [6]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [7]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [8]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [9]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [10]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [11]pvcs.Threshold , 1 , ['Mac10.7.5-clang-nightlymaster-release'] [12]pvcs-collab.SpreadSheet1 , 1 , ['ubuntu-x64-nightlymaster'] [13]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlymaster-debug'] [14]pqWidgetspqTextEditTest , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [15]pvcs.HistogramSelection , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [16]pvcrs.HistogramSelection , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [17]pv.HistogramSelection , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [18]pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 , 2 , ['Mac10.7.5-gcc-nightlymaster-release', 'Mac10.7.5-clang-nightlymaster-release'] [19]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 3 , ['Mac10.7.5-gcc-nightlymaster-release', 'fedora-x64-icc-nightlymaster-debug', 'Mac10.7.5-clang-nightlymaster-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [20]Win7x64-vs9-nightlynext-static-release 3 [21]Win64-vs9-static-release 1 [22]fedora-x64-icc-nightlynext-release 7 -------------------- REPORT -------------------- 11 FAILURES [23]pvcrs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [24]pv.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [25]pv.OpenHelp , 1 , ['Win64-vs9-static-release'] [26]pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 , 1 , ['fedora-x64-icc-nightlynext-release'] [27]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [28]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [29]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-vs9-nightlynext-static-release'] [30]pvcrs.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [31]pv.UndoRedo1 , 1 , ['fedora-x64-icc-nightlynext-release'] [32]pvcs.LoadStateMultiView , 1 , ['fedora-x64-icc-nightlynext-release'] [33]pvcs.UndoRedo1 , 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-08-20&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 2. http://open.cdash.org/index.php?project=ParaView&date=2014-08-20&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-08-20&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster 4. http://open.cdash.org/index.php?project=ParaView&date=2014-08-20&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 5. http://open.cdash.org/index.php?project=ParaView&date=2014-08-20&filtercount=1&field1=buildname/string&compare1=61&value1=Mac10.7.5-clang-nightlymaster-release 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcrs.LoadStateMultiView 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pv.LoadStateMultiView 8. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=SurfaceLIC-ShuttleZoom2-Batch 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=SurfaceLIC-ShuttleZoom1-Batch 10. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=SurfaceLIC-ShuttleAll-Batch 11. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcs.Threshold 12. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcs-collab.SpreadSheet1 13. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcs.LoadStateMultiView 14. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pqWidgetspqTextEditTest 15. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcs.HistogramSelection 16. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcrs.HistogramSelection 17. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pv.HistogramSelection 18. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcs-tile-display-2x1.TileDisplay3DTesting-2x1 19. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 20. http://open.cdash.org/index.php?project=ParaView&date=2014-08-20&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlynext-static-release 21. http://open.cdash.org/index.php?project=ParaView&date=2014-08-20&filtercount=1&field1=buildname/string&compare1=61&value1=Win64-vs9-static-release 22. http://open.cdash.org/index.php?project=ParaView&date=2014-08-20&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 23. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcrs.LoadStateMultiView 24. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pv.LoadStateMultiView 25. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pv.OpenHelp 26. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcs-tile-display-1x2.TileDisplay3DTesting-1x2 27. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=SurfaceLIC-ShuttleZoom2-Batch 28. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=SurfaceLIC-ShuttleZoom1-Batch 29. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=SurfaceLIC-ShuttleAll-Batch 30. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcrs.UndoRedo1 31. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pv.UndoRedo1 32. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcs.LoadStateMultiView 33. http://open.cdash.org/testSummary.php?project=9&date=2014-08-20&name=pvcs.UndoRedo1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 21 08:02:59 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 21 Aug 2014 08:02:59 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: --------------------------------------------- Topics merged into master: 14911_fix_ICC_build catalyst-script-plugin-client fix-qhp-warnings import-pygments pvw-fix-xdmf-reader-name update_baselines From utkarsh.ayachit at kitware.com Thu Aug 21 12:06:14 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 21 Aug 2014 12:06:14 -0400 Subject: [Paraview-developers] Trying to compile a GUI plugin In-Reply-To: <53F22FDA.1080209@gmail.com> References: <53F22FDA.1080209@gmail.com> Message-ID: I believe you need to add a INCLUDE_DIRECTORIES(${VTK_INCLUDE_DIRS}) in the CMakeLists.txt at the top when moving the plugin to under Plugins. On Mon, Aug 18, 2014 at 12:54 PM, Panos Asproulis wrote: > Hi all, > > I am trying to create a GUI plugin and for that purpose I am looking at the > SourceToolbar example in the Examples subdirectory. This compiles fine when > using the CMake system with the Examples Build option enabled. > > I then copied the SourceToolbar folder to the Plugins folder of ParaView and > added the following plugin.cmake file: > > pv_plugin(SourceToolbar > DESCRIPTION "Testing plugin" > DEFAULT_ENABLED) > > I did the CMake configuration step, which reported that it was also going to > build the "SourceToolbar" plugin: > > Plugin: SourceToolbar - Testing plugin : Enabled > > > I then generated the Makefiles and started the build. I get the following > error message: > > /home/panos/Development/ParaView/ParaView-v4.1.0-bin/Plugins/SourceToolbar/SourceToolbarActionsImplementation.h:46: > Error: Undefined interface > make[2]: *** > [Plugins/SourceToolbar/moc_SourceToolbarActionsImplementation.cxx] Error 1 > > Why would the same code compiles correctly when in the Examples directory > and fails when in the Plugins directory? > > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > From panos.asproulis at gmail.com Thu Aug 21 13:18:23 2014 From: panos.asproulis at gmail.com (Panos Asproulis) Date: Thu, 21 Aug 2014 19:18:23 +0200 Subject: [Paraview-developers] Trying to compile a GUI plugin In-Reply-To: References: <53F22FDA.1080209@gmail.com> Message-ID: <1918fe14-0e2f-4a86-84ed-b2443f4a8fe5@gmail.com> That is correct. Thank you! On 21 Aug 2014, Utkarsh Ayachit wrote: >I believe you need to add a > >INCLUDE_DIRECTORIES(${VTK_INCLUDE_DIRS}) > >in the CMakeLists.txt at the top when moving the plugin to under >Plugins. > >On Mon, Aug 18, 2014 at 12:54 PM, Panos Asproulis > wrote: >> Hi all, >> >> I am trying to create a GUI plugin and for that purpose I am looking >at the >> SourceToolbar example in the Examples subdirectory. This compiles >fine when >> using the CMake system with the Examples Build option enabled. >> >> I then copied the SourceToolbar folder to the Plugins folder of >ParaView and >> added the following plugin.cmake file: >> >> pv_plugin(SourceToolbar >> DESCRIPTION "Testing plugin" >> DEFAULT_ENABLED) >> >> I did the CMake configuration step, which reported that it was also >going to >> build the "SourceToolbar" plugin: >> >> Plugin: SourceToolbar - Testing plugin : Enabled >> >> >> I then generated the Makefiles and started the build. I get the >following >> error message: >> >> >/home/panos/Development/ParaView/ParaView-v4.1.0-bin/Plugins/SourceToolbar/SourceToolbarActionsImplementation.h:46: >> Error: Undefined interface >> make[2]: *** >> [Plugins/SourceToolbar/moc_SourceToolbarActionsImplementation.cxx] >Error 1 >> >> Why would the same code compiles correctly when in the Examples >directory >> and fails when in the Plugins directory? >> >> >> _______________________________________________ >> Paraview-developers mailing list >> Paraview-developers at paraview.org >> http://public.kitware.com/mailman/listinfo/paraview-developers >> -- Dr. Panos Asproulis, panos.asproulis at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Aug 22 08:26:05 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 22 Aug 2014 08:26:05 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: --------------------------------------------- Topics merged into master: 14962_fix_glyph_panel dashboard_fixes From panos.asproulis at gmail.com Fri Aug 22 08:45:22 2014 From: panos.asproulis at gmail.com (Panos Asproulis) Date: Fri, 22 Aug 2014 14:45:22 +0200 Subject: [Paraview-developers] Plugin: Add a submenu to a menu? Message-ID: <53F73B62.6080503@gmail.com> Hi all, In the section "Adding a Menu" of the ParaView Wiki regarding the development of plugins there is a note about adding a menu to the ParaView menu bar using the following: ADD_PARAVIEW_ACTION_GROUP(IFACES IFACE_SRCS CLASS_NAME SourceToolbarActions GROUP_NAME "MenuBar/MyActions") However, the added element SourceToolbarActions is a QActionGroup and therefore it can only have actions which are displayed as elements of a menu. What if one wants to add a submenu to this new menu which appears as "MyActions" in the ParaView menu bar? Thanks in advance, Panos -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Fri Aug 22 12:31:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Fri, 22 Aug 2014 09:31:05 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Thursday, August 21 2014 Message-ID: <20140822163103.A74218002A@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Win7x64-ninja-nightlymaster-static-release 3 -------------------- REPORT -------------------- 3 FAILURES [2]SurfaceLIC-ShuttleZoom1-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [3]SurfaceLIC-ShuttleAll-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] [4]SurfaceLIC-ShuttleZoom2-Batch , 1 , ['Win7x64-ninja-nightlymaster-static-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [5]fedora-x64-icc-nightlynext-release 1 -------------------- REPORT -------------------- 1 FAILURES [6]pv.LogColorMap , 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-08-22&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-ninja-nightlymaster-static-release 2. http://open.cdash.org/testSummary.php?project=9&date=2014-08-22&name=SurfaceLIC-ShuttleZoom1-Batch 3. http://open.cdash.org/testSummary.php?project=9&date=2014-08-22&name=SurfaceLIC-ShuttleAll-Batch 4. http://open.cdash.org/testSummary.php?project=9&date=2014-08-22&name=SurfaceLIC-ShuttleZoom2-Batch 5. http://open.cdash.org/index.php?project=ParaView&date=2014-08-22&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlynext-release 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-22&name=pv.LogColorMap -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Sat Aug 23 12:31:08 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Sat, 23 Aug 2014 09:31:08 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Friday, August 22 2014 Message-ID: <20140823163103.507FA7FFD1@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]fedora-x64-icc-nightlymaster-debug 1 -------------------- REPORT -------------------- 1 FAILURES [2]pqCoreBasicApp , 1 , ['fedora-x64-icc-nightlymaster-debug'] Dashboard status for Nightly (next) Cdash returned nothing useful as of this report. 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-08-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-08-23&name=pqCoreBasicApp -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Sun Aug 24 12:31:11 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Sun, 24 Aug 2014 09:31:11 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Saturday, August 23 2014 Message-ID: <20140824163103.D34267FFE5@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Mac10.7.5-clang-nightlymaster-release 2 [2]fedora-x64-icc-nightlymaster-debug 1 -------------------- REPORT -------------------- 3 FAILURES [3]pv.LogColorMap , 1 , ['fedora-x64-icc-nightlymaster-debug'] [4]vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter , 1 , ['Mac10.7.5-clang-nightlymaster-release'] [5]pv.UncertaintyRendering , 1 , ['Mac10.7.5-clang-nightlymaster-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [6]Win7x64-vs10-static-release 1 -------------------- REPORT -------------------- 1 FAILURES [7]pv.OpenHelp , 1 , ['Win7x64-vs10-static-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-08-24&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-08-24&filtercount=1&field1=buildname/string&compare1=61&value1=fedora-x64-icc-nightlymaster-debug 3. http://open.cdash.org/testSummary.php?project=9&date=2014-08-24&name=pv.LogColorMap 4. http://open.cdash.org/testSummary.php?project=9&date=2014-08-24&name=vtkPVServerManagerDefaultPython-MPI-SymmetricParallelImageWriter 5. http://open.cdash.org/testSummary.php?project=9&date=2014-08-24&name=pv.UncertaintyRendering 6. http://open.cdash.org/index.php?project=ParaView&date=2014-08-24&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-static-release 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-24&name=pv.OpenHelp -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Sun Aug 24 15:36:18 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 24 Aug 2014 15:36:18 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: Topics merged into master: catalyze_fixes clang_warnings dashboard_fixes dashboard-warnings-20140822 header-fixes nektar-flag-warning From jlih at masonlive.gmu.edu Mon Aug 25 05:22:16 2014 From: jlih at masonlive.gmu.edu (jlih) Date: Mon, 25 Aug 2014 09:22:16 +0000 Subject: [Paraview-developers] Parallel volume rendering for multiblock/AMR datasets? Message-ID: <1408958529427.67377@masonlive.gmu.edu> Hi folks, I am developing Python codes to visualize multiresolution data. I am wondering if parallel volume rendering for multiblock or AMR datasets is supported in the current version of paraview (4.1.0). Thanks in advance. Jing -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Mon Aug 25 12:31:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Mon, 25 Aug 2014 09:31:05 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Sunday, August 24 2014 Message-ID: <20140825163103.B194780814@sanganak-ubuntu> Dashboard status for Nightly (master) Cdash returned nothing useful as of this report. Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [1]ubuntu-x64-nightlynext 1 -------------------- REPORT -------------------- 1 FAILURES [2]pvcs.CatalystLiveSetBreakpoint , 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-08-25&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 2. http://open.cdash.org/testSummary.php?project=9&date=2014-08-25&name=pvcs.CatalystLiveSetBreakpoint -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgirish28 at gmail.com Tue Aug 26 09:41:28 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Tue, 26 Aug 2014 15:41:28 +0200 Subject: [Paraview-developers] Segmentation fault Message-ID: Hi, I am writing my own plugin but each time I try to add another check box, the plugin suddenly segfaults. I have no idea why. The XML and C++ code are attached. XML: The values of this property sets the run number. C++: public: vtkTypeMacro(ReadUALGrid, vtkUnstructuredGridAlgorithm); void PrintSelf(ostream& os, vtkIndent indent); static ReadUALGrid *New(); vtkGetMacro(Shot,int) vtkSetMacro(Shot,int); vtkGetMacro(Run,int); vtkSetMacro(Run,int); vtkGetMacro(RefRun,int); vtkSetMacro(RefRun,int); vtkGetMacro(CPOLoad,int); vtkSetMacro(CPOLoad,int); vtkGetMacro(FieldLoadStatus,int); vtkSetMacro(FieldLoadStatus,int); protected: ReadUALGrid(); ~ReadUALGrid(){} int Shot; int Run; int RefRun; int CPOLoad; int FieldLoadStatus; I have no idea why because it worked perfectly for other check boxes. Thank you. Regards, Girish -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Aug 26 09:49:00 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 26 Aug 2014 09:49:00 -0400 Subject: [Paraview-developers] Segmentation fault In-Reply-To: References: Message-ID: Girish, Can you run ParaView with your plugin through a debugger to find out where it is segfaulting? That will point out where the segfault occurs which is often a clue to why it is occurring. Thanks, Cory On Tue, Aug 26, 2014 at 9:41 AM, Girish Ramesh wrote: > Hi, > > I am writing my own plugin but each time I try to add another check box, the > plugin suddenly segfaults. I have no idea why. The XML and C++ code are > attached. > > XML: > > name="FieldLoadStatus" > command="SetFieldLoadStatus" > number_of_elements="1" > default_values="0" > panel_visibility="default" > > > > The values of this property sets the run number. > > > C++: > > public: > vtkTypeMacro(ReadUALGrid, vtkUnstructuredGridAlgorithm); > void PrintSelf(ostream& os, vtkIndent indent); > > static ReadUALGrid *New(); > > vtkGetMacro(Shot,int) > vtkSetMacro(Shot,int); > > vtkGetMacro(Run,int); > vtkSetMacro(Run,int); > > vtkGetMacro(RefRun,int); > vtkSetMacro(RefRun,int); > > vtkGetMacro(CPOLoad,int); > vtkSetMacro(CPOLoad,int); > > vtkGetMacro(FieldLoadStatus,int); > vtkSetMacro(FieldLoadStatus,int); > > protected: > ReadUALGrid(); > ~ReadUALGrid(){} > > int Shot; > int Run; > int RefRun; > int CPOLoad; > int FieldLoadStatus; > > I have no idea why because it worked perfectly for other check boxes. Thank > you. > > Regards, > Girish > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > From rgirish28 at gmail.com Tue Aug 26 09:59:51 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Tue, 26 Aug 2014 15:59:51 +0200 Subject: [Paraview-developers] Segmentation fault In-Reply-To: References: Message-ID: This is the backtrace i get when I run through gdb. Output: Program received signal SIGSEGV, Segmentation fault. 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 (gdb) bt full #0 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 No symbol table info available. #1 0x00002aaac9cb4ee9 in ReadUALGrid::SetUser (this=0x10e3c10, _arg=0x1b2ab39 "diy") at /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGrid.h:38 No locals. #2 0x00002aaac9cb6937 in ReadUALGridCommand (arlu=0xecf5b0, ob=0x10e3c10, method=0x1b2ab29 "SetUser", msg=..., resultStream=...) at /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGridClientServer.cxx:175 temp0 = 0x1b2ab39 "diy" op = 0x10e3c10 vtkmsg = #3 0x00002aaab1ee11c8 in vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 No symbol table info available. #4 0x00002aaab1ee5102 in vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 No symbol table info available. #5 0x00002aaab1ee4746 in vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 No symbol table info available. #6 0x00002aaab1ee480d in vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 No symbol table info available. #7 0x00002aaaae5011bb in vtkSIProperty::ProcessMessage(vtkClientServerStream&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #8 0x00002aaaae516ad7 in vtkSIStringVectorProperty::Push(vtkSIStringVectorProperty::vtkVectorOfStrings const&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #9 0x00002aaaae517431 in vtkSIStringVectorProperty::ReadXMLAttributes(vtkSIProxy*, vtkPVXMLElement*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #10 0x00002aaaae503832 in vtkSIProxy::ReadXMLProperty(vtkPVXMLElement*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #11 0x00002aaaae50249f in vtkSIProxy::ReadXMLAttributes(vtkPVXMLElement*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #12 0x00002aaaae513809 in vtkSISourceProxy::ReadXMLAttributes(vtkPVXMLElement*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #13 0x00002aaaae502e12 in vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) () ---Type to continue, or q to quit--- from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #14 0x00002aaaae515765 in vtkSISourceProxy::CreateVTKObjects(paraview_protobuf::Message*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #15 0x00002aaaae50209d in vtkSIProxy::Push(paraview_protobuf::Message*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #16 0x00002aaaae4e6e32 in vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #17 0x00002aaaae4e52e7 in vtkPVSessionCore::PushState(paraview_protobuf::Message*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #18 0x00002aaaae4e2b2d in vtkPVSessionBase::PushState(paraview_protobuf::Message*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 No symbol table info available. #19 0x00002aaaadfe7663 in vtkSMProxy::CreateVTKObjects() () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 No symbol table info available. #20 0x00002aaaae0277e5 in vtkSMSourceProxy::CreateVTKObjects() () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 No symbol table info available. #21 0x00002aaaae01c8f2 in vtkSMSessionProxyManager::RegisterProxy(char const*, char const*, vtkSMProxy*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 No symbol table info available. #22 0x00002aaaab7f051b in pqObjectBuilder::createProxyInternal(QString const&, QString const&, pqServer*, QString const&, QString const&, QMap const&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 No symbol table info available. #23 0x00002aaaab7ecd09 in pqObjectBuilder::createSource(QString const&, QString const&, pqServer*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 No symbol table info available. #24 0x00002aaaaad7838a in pqSourcesMenuReaction::createSource(QString const&, QString const&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 No symbol table info available. #25 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #26 0x00002aaaaad902a7 in pqProxyGroupMenuManager::triggered(QString const&, QString const&) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 No symbol table info available. #27 0x00002aaaaad679a7 in pqProxyGroupMenuManager::triggered() () ---Type to continue, or q to quit--- from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 No symbol table info available. #28 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #29 0x00002aaabd7f7da2 in QAction::triggered(bool) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #30 0x00002aaabd7f7f90 in QAction::activate(QAction::ActionEvent) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #31 0x00002aaabdc2e3b3 in ?? () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #32 0x00002aaabdc347c9 in ?? () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #33 0x00002aaabd84da99 in QWidget::event(QEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #34 0x00002aaabdc35b0b in QMenu::event(QEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #35 0x00002aaabd7fdfac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #36 0x00002aaabd8026db in QApplication::notify(QObject*, QEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #37 0x00002aaabe7b44de in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #38 0x00002aaabd7fedeb in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #39 0x00002aaabd87977c in ?? () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #40 0x00002aaabd878651 in QApplication::x11ProcessEvent(_XEvent*) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #41 0x00002aaabd89e322 in ?? () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 No symbol table info available. #42 0x00002aaac543960a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #43 0x00002aaac543ce88 in ?? () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #44 0x00002aaac543d03c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #45 0x00002aaabe7e2ac6 in QEventDispatcherGlib::processEvents(QFlags) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #46 0x00002aaabd89dfae in ?? () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 ---Type to continue, or q to quit--- No symbol table info available. #47 0x00002aaabe7b30df in QEventLoop::processEvents(QFlags) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #48 0x00002aaabe7b3368 in QEventLoop::exec(QFlags) () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #49 0x00002aaabe7b8248 in QCoreApplication::exec() () from /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 No symbol table info available. #50 0x0000000000407ac5 in main () No symbol table info available. No idea what's happening. Please help. Regards, Girish On 26 August 2014 15:49, Cory Quammen wrote: > Girish, > > Can you run ParaView with your plugin through a debugger to find out > where it is segfaulting? That will point out where the segfault occurs > which is often a clue to why it is occurring. > > Thanks, > Cory > > On Tue, Aug 26, 2014 at 9:41 AM, Girish Ramesh > wrote: > > Hi, > > > > I am writing my own plugin but each time I try to add another check box, > the > > plugin suddenly segfaults. I have no idea why. The XML and C++ code are > > attached. > > > > XML: > > > > > name="FieldLoadStatus" > > command="SetFieldLoadStatus" > > number_of_elements="1" > > default_values="0" > > panel_visibility="default" > > > > > > > The values of this property sets the run number. > > > > > > C++: > > > > public: > > vtkTypeMacro(ReadUALGrid, vtkUnstructuredGridAlgorithm); > > void PrintSelf(ostream& os, vtkIndent indent); > > > > static ReadUALGrid *New(); > > > > vtkGetMacro(Shot,int) > > vtkSetMacro(Shot,int); > > > > vtkGetMacro(Run,int); > > vtkSetMacro(Run,int); > > > > vtkGetMacro(RefRun,int); > > vtkSetMacro(RefRun,int); > > > > vtkGetMacro(CPOLoad,int); > > vtkSetMacro(CPOLoad,int); > > > > vtkGetMacro(FieldLoadStatus,int); > > vtkSetMacro(FieldLoadStatus,int); > > > > protected: > > ReadUALGrid(); > > ~ReadUALGrid(){} > > > > int Shot; > > int Run; > > int RefRun; > > int CPOLoad; > > int FieldLoadStatus; > > > > I have no idea why because it worked perfectly for other check boxes. > Thank > > you. > > > > Regards, > > Girish > > > > _______________________________________________ > > 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 berk.geveci at kitware.com Tue Aug 26 09:55:50 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Tue, 26 Aug 2014 09:55:50 -0400 Subject: [Paraview-developers] Parallel volume rendering for multiblock/AMR datasets? In-Reply-To: <1408958529427.67377@masonlive.gmu.edu> References: <1408958529427.67377@masonlive.gmu.edu> Message-ID: Hi Jing, Unfortunately not. The best way to go about it is to resample (possibly adaptively) to a uniform grid (vtkImageData). If you are interested in pursuing this, I can provide some pointers. Best, -berk On Mon, Aug 25, 2014 at 5:22 AM, jlih wrote: > Hi folks, > I am developing Python codes to visualize multiresolution data. I am > wondering if parallel volume rendering for multiblock or AMR datasets is > supported in the current version of paraview (4.1.0). > > Thanks in advance. > Jing > > _______________________________________________ > 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 utkarsh.ayachit at kitware.com Tue Aug 26 10:01:32 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 26 Aug 2014 10:01:32 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: --------------------------------------------- Topics merged into master: animation-dependency catalyst-cmake-warnings disable_unused_vars_warnings fix_eigen_warnings fix_id_selections_in_find_data (VTK) fix_python_packages_and_modules_in_vtk_modules pvweb-fix-failing-superbuild-test pvweb-support-reverse-connect silence-eigen-warnings sync-external-data --------------------------------------------- Topics still in next: live-breakpoint vr_plugin_fixes --------------------------------------------- Topics reverted from next: python_syntax_highlighting -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Aug 26 10:09:43 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 26 Aug 2014 10:09:43 -0400 Subject: [Paraview-developers] Segmentation fault In-Reply-To: References: Message-ID: My guess is that you have a member variable in RealUALGrid called "User" that is a char *, but you aren't initializing it to NULL in the constructor. When RealUALGrid::SetUser() is called, it checks whether the parameter string passed in is the same as the "User" member variable. Since "User" is initialized to an invalid pointer, you get the segmentation fault Cory On Tue, Aug 26, 2014 at 9:59 AM, Girish Ramesh wrote: > This is the backtrace i get when I run through gdb. > > Output: > > Program received signal SIGSEGV, Segmentation fault. > 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 > (gdb) bt full > #0 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 > No symbol table info available. > #1 0x00002aaac9cb4ee9 in ReadUALGrid::SetUser (this=0x10e3c10, > _arg=0x1b2ab39 "diy") > at > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGrid.h:38 > No locals. > #2 0x00002aaac9cb6937 in ReadUALGridCommand (arlu=0xecf5b0, ob=0x10e3c10, > method=0x1b2ab29 "SetUser", msg=..., resultStream=...) > at > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGridClientServer.cxx:175 > temp0 = 0x1b2ab39 "diy" > op = 0x10e3c10 > vtkmsg = > #3 0x00002aaab1ee11c8 in > vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, > char const*, vtkClientServerStream const&, vtkClientServerStream&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > No symbol table info available. > #4 0x00002aaab1ee5102 in > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > const&, int) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > No symbol table info available. > #5 0x00002aaab1ee4746 in > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, > int) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > No symbol table info available. > #6 0x00002aaab1ee480d in > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > No symbol table info available. > #7 0x00002aaaae5011bb in > vtkSIProperty::ProcessMessage(vtkClientServerStream&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #8 0x00002aaaae516ad7 in > vtkSIStringVectorProperty::Push(vtkSIStringVectorProperty::vtkVectorOfStrings > const&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #9 0x00002aaaae517431 in > vtkSIStringVectorProperty::ReadXMLAttributes(vtkSIProxy*, vtkPVXMLElement*) > () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #10 0x00002aaaae503832 in vtkSIProxy::ReadXMLProperty(vtkPVXMLElement*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #11 0x00002aaaae50249f in vtkSIProxy::ReadXMLAttributes(vtkPVXMLElement*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #12 0x00002aaaae513809 in > vtkSISourceProxy::ReadXMLAttributes(vtkPVXMLElement*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #13 0x00002aaaae502e12 in > vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) () > ---Type to continue, or q to quit--- > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #14 0x00002aaaae515765 in > vtkSISourceProxy::CreateVTKObjects(paraview_protobuf::Message*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #15 0x00002aaaae50209d in vtkSIProxy::Push(paraview_protobuf::Message*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #16 0x00002aaaae4e6e32 in > vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #17 0x00002aaaae4e52e7 in > vtkPVSessionCore::PushState(paraview_protobuf::Message*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #18 0x00002aaaae4e2b2d in > vtkPVSessionBase::PushState(paraview_protobuf::Message*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > No symbol table info available. > #19 0x00002aaaadfe7663 in vtkSMProxy::CreateVTKObjects() () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > No symbol table info available. > #20 0x00002aaaae0277e5 in vtkSMSourceProxy::CreateVTKObjects() () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > No symbol table info available. > #21 0x00002aaaae01c8f2 in vtkSMSessionProxyManager::RegisterProxy(char > const*, char const*, vtkSMProxy*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > No symbol table info available. > #22 0x00002aaaab7f051b in pqObjectBuilder::createProxyInternal(QString > const&, QString const&, pqServer*, QString const&, QString const&, > QMap const&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 > No symbol table info available. > #23 0x00002aaaab7ecd09 in pqObjectBuilder::createSource(QString const&, > QString const&, pqServer*) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 > No symbol table info available. > #24 0x00002aaaaad7838a in pqSourcesMenuReaction::createSource(QString > const&, QString const&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > No symbol table info available. > #25 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #26 0x00002aaaaad902a7 in pqProxyGroupMenuManager::triggered(QString const&, > QString const&) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > No symbol table info available. > #27 0x00002aaaaad679a7 in pqProxyGroupMenuManager::triggered() () > ---Type to continue, or q to quit--- > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > No symbol table info available. > #28 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #29 0x00002aaabd7f7da2 in QAction::triggered(bool) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #30 0x00002aaabd7f7f90 in QAction::activate(QAction::ActionEvent) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #31 0x00002aaabdc2e3b3 in ?? () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #32 0x00002aaabdc347c9 in ?? () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #33 0x00002aaabd84da99 in QWidget::event(QEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #34 0x00002aaabdc35b0b in QMenu::event(QEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #35 0x00002aaabd7fdfac in QApplicationPrivate::notify_helper(QObject*, > QEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #36 0x00002aaabd8026db in QApplication::notify(QObject*, QEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #37 0x00002aaabe7b44de in QCoreApplication::notifyInternal(QObject*, > QEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #38 0x00002aaabd7fedeb in QApplicationPrivate::sendMouseEvent(QWidget*, > QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #39 0x00002aaabd87977c in ?? () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #40 0x00002aaabd878651 in QApplication::x11ProcessEvent(_XEvent*) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #41 0x00002aaabd89e322 in ?? () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > No symbol table info available. > #42 0x00002aaac543960a in g_main_context_dispatch () from > /usr/lib64/libglib-2.0.so.0 > No symbol table info available. > #43 0x00002aaac543ce88 in ?? () from /usr/lib64/libglib-2.0.so.0 > No symbol table info available. > #44 0x00002aaac543d03c in g_main_context_iteration () from > /usr/lib64/libglib-2.0.so.0 > No symbol table info available. > #45 0x00002aaabe7e2ac6 in > QEventDispatcherGlib::processEvents(QFlags) > () > from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #46 0x00002aaabd89dfae in ?? () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > ---Type to continue, or q to quit--- > No symbol table info available. > #47 0x00002aaabe7b30df in > QEventLoop::processEvents(QFlags) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #48 0x00002aaabe7b3368 in > QEventLoop::exec(QFlags) () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #49 0x00002aaabe7b8248 in QCoreApplication::exec() () from > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > No symbol table info available. > #50 0x0000000000407ac5 in main () > No symbol table info available. > > > No idea what's happening. Please help. > > Regards, > Girish > > > On 26 August 2014 15:49, Cory Quammen wrote: >> >> Girish, >> >> Can you run ParaView with your plugin through a debugger to find out >> where it is segfaulting? That will point out where the segfault occurs >> which is often a clue to why it is occurring. >> >> Thanks, >> Cory >> >> On Tue, Aug 26, 2014 at 9:41 AM, Girish Ramesh >> wrote: >> > Hi, >> > >> > I am writing my own plugin but each time I try to add another check box, >> > the >> > plugin suddenly segfaults. I have no idea why. The XML and C++ code are >> > attached. >> > >> > XML: >> > >> > > > name="FieldLoadStatus" >> > command="SetFieldLoadStatus" >> > number_of_elements="1" >> > default_values="0" >> > panel_visibility="default" > >> > >> > >> > The values of this property sets the run number. >> > >> > >> > C++: >> > >> > public: >> > vtkTypeMacro(ReadUALGrid, vtkUnstructuredGridAlgorithm); >> > void PrintSelf(ostream& os, vtkIndent indent); >> > >> > static ReadUALGrid *New(); >> > >> > vtkGetMacro(Shot,int) >> > vtkSetMacro(Shot,int); >> > >> > vtkGetMacro(Run,int); >> > vtkSetMacro(Run,int); >> > >> > vtkGetMacro(RefRun,int); >> > vtkSetMacro(RefRun,int); >> > >> > vtkGetMacro(CPOLoad,int); >> > vtkSetMacro(CPOLoad,int); >> > >> > vtkGetMacro(FieldLoadStatus,int); >> > vtkSetMacro(FieldLoadStatus,int); >> > >> > protected: >> > ReadUALGrid(); >> > ~ReadUALGrid(){} >> > >> > int Shot; >> > int Run; >> > int RefRun; >> > int CPOLoad; >> > int FieldLoadStatus; >> > >> > I have no idea why because it worked perfectly for other check boxes. >> > Thank >> > you. >> > >> > Regards, >> > Girish >> > >> > _______________________________________________ >> > Paraview-developers mailing list >> > Paraview-developers at paraview.org >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > From rgirish28 at gmail.com Tue Aug 26 10:17:40 2014 From: rgirish28 at gmail.com (Girish Ramesh) Date: Tue, 26 Aug 2014 16:17:40 +0200 Subject: [Paraview-developers] Segmentation fault In-Reply-To: References: Message-ID: Oh thanks Cory. A very silly error! Sorry I missed that and thanks for pointing it out. Regards, Girish On 26 August 2014 16:09, Cory Quammen wrote: > My guess is that you have a member variable in RealUALGrid called > "User" that is a char *, but you aren't initializing it to NULL in the > constructor. When RealUALGrid::SetUser() is called, it checks whether > the parameter string passed in is the same as the "User" member > variable. Since "User" is initialized to an invalid pointer, you get > the segmentation fault > > Cory > > On Tue, Aug 26, 2014 at 9:59 AM, Girish Ramesh > wrote: > > This is the backtrace i get when I run through gdb. > > > > Output: > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 > > (gdb) bt full > > #0 0x00002aaabf3c21c4 in __strcmp_sse42 () from /lib64/libc.so.6 > > No symbol table info available. > > #1 0x00002aaac9cb4ee9 in ReadUALGrid::SetUser (this=0x10e3c10, > > _arg=0x1b2ab39 "diy") > > at > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGrid.h:38 > > No locals. > > #2 0x00002aaac9cb6937 in ReadUALGridCommand (arlu=0xecf5b0, > ob=0x10e3c10, > > method=0x1b2ab29 "SetUser", msg=..., resultStream=...) > > at > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/paraview/ParaView-v4.1.0/Plugins/ReadUALGrid/ReadUALGridClientServer.cxx:175 > > temp0 = 0x1b2ab39 "diy" > > op = 0x10e3c10 > > vtkmsg = > > #3 0x00002aaab1ee11c8 in > > vtkClientServerInterpreter::CallCommandFunction(char const*, > vtkObjectBase*, > > char const*, vtkClientServerStream const&, vtkClientServerStream&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > > No symbol table info available. > > #4 0x00002aaab1ee5102 in > > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > > const&, int) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > > No symbol table info available. > > #5 0x00002aaab1ee4746 in > > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream > const&, > > int) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > > No symbol table info available. > > #6 0x00002aaab1ee480d in > > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) > () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1 > > No symbol table info available. > > #7 0x00002aaaae5011bb in > > vtkSIProperty::ProcessMessage(vtkClientServerStream&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #8 0x00002aaaae516ad7 in > > > vtkSIStringVectorProperty::Push(vtkSIStringVectorProperty::vtkVectorOfStrings > > const&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #9 0x00002aaaae517431 in > > vtkSIStringVectorProperty::ReadXMLAttributes(vtkSIProxy*, > vtkPVXMLElement*) > > () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #10 0x00002aaaae503832 in vtkSIProxy::ReadXMLProperty(vtkPVXMLElement*) > () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #11 0x00002aaaae50249f in > vtkSIProxy::ReadXMLAttributes(vtkPVXMLElement*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #12 0x00002aaaae513809 in > > vtkSISourceProxy::ReadXMLAttributes(vtkPVXMLElement*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #13 0x00002aaaae502e12 in > > vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) () > > ---Type to continue, or q to quit--- > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #14 0x00002aaaae515765 in > > vtkSISourceProxy::CreateVTKObjects(paraview_protobuf::Message*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #15 0x00002aaaae50209d in vtkSIProxy::Push(paraview_protobuf::Message*) > () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #16 0x00002aaaae4e6e32 in > > vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #17 0x00002aaaae4e52e7 in > > vtkPVSessionCore::PushState(paraview_protobuf::Message*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #18 0x00002aaaae4e2b2d in > > vtkPVSessionBase::PushState(paraview_protobuf::Message*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1 > > No symbol table info available. > > #19 0x00002aaaadfe7663 in vtkSMProxy::CreateVTKObjects() () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > > No symbol table info available. > > #20 0x00002aaaae0277e5 in vtkSMSourceProxy::CreateVTKObjects() () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > > No symbol table info available. > > #21 0x00002aaaae01c8f2 in vtkSMSessionProxyManager::RegisterProxy(char > > const*, char const*, vtkSMProxy*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkPVServerManagerCore-pv4.1.so.1 > > No symbol table info available. > > #22 0x00002aaaab7f051b in pqObjectBuilder::createProxyInternal(QString > > const&, QString const&, pqServer*, QString const&, QString const&, > > QMap const&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 > > No symbol table info available. > > #23 0x00002aaaab7ecd09 in pqObjectBuilder::createSource(QString const&, > > QString const&, pqServer*) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqCore-pv4.1.so.1 > > No symbol table info available. > > #24 0x00002aaaaad7838a in pqSourcesMenuReaction::createSource(QString > > const&, QString const&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > > No symbol table info available. > > #25 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject > > const*, int, void**) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #26 0x00002aaaaad902a7 in pqProxyGroupMenuManager::triggered(QString > const&, > > QString const&) () > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > > No symbol table info available. > > #27 0x00002aaaaad679a7 in pqProxyGroupMenuManager::triggered() () > > ---Type to continue, or q to quit--- > > from > > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/paraview/4.1/lib/paraview-4.1/libvtkpqApplicationComponents-pv4.1.so.1 > > No symbol table info available. > > #28 0x00002aaabe7c99bf in QMetaObject::activate(QObject*, QMetaObject > > const*, int, void**) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #29 0x00002aaabd7f7da2 in QAction::triggered(bool) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #30 0x00002aaabd7f7f90 in QAction::activate(QAction::ActionEvent) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #31 0x00002aaabdc2e3b3 in ?? () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #32 0x00002aaabdc347c9 in ?? () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #33 0x00002aaabd84da99 in QWidget::event(QEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #34 0x00002aaabdc35b0b in QMenu::event(QEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #35 0x00002aaabd7fdfac in QApplicationPrivate::notify_helper(QObject*, > > QEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #36 0x00002aaabd8026db in QApplication::notify(QObject*, QEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #37 0x00002aaabe7b44de in QCoreApplication::notifyInternal(QObject*, > > QEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #38 0x00002aaabd7fedeb in QApplicationPrivate::sendMouseEvent(QWidget*, > > QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () > > from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #39 0x00002aaabd87977c in ?? () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #40 0x00002aaabd878651 in QApplication::x11ProcessEvent(_XEvent*) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #41 0x00002aaabd89e322 in ?? () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > No symbol table info available. > > #42 0x00002aaac543960a in g_main_context_dispatch () from > > /usr/lib64/libglib-2.0.so.0 > > No symbol table info available. > > #43 0x00002aaac543ce88 in ?? () from /usr/lib64/libglib-2.0.so.0 > > No symbol table info available. > > #44 0x00002aaac543d03c in g_main_context_iteration () from > > /usr/lib64/libglib-2.0.so.0 > > No symbol table info available. > > #45 0x00002aaabe7e2ac6 in > > > QEventDispatcherGlib::processEvents(QFlags) > > () > > from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #46 0x00002aaabd89dfae in ?? () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtGui.so.4 > > ---Type to continue, or q to quit--- > > No symbol table info available. > > #47 0x00002aaabe7b30df in > > QEventLoop::processEvents(QFlags) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #48 0x00002aaabe7b3368 in > > QEventLoop::exec(QFlags) () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #49 0x00002aaabe7b8248 in QCoreApplication::exec() () from > > /pfs/work/kosl/sohpc/girish/paraview_plugin/staging/qt/lib/libQtCore.so.4 > > No symbol table info available. > > #50 0x0000000000407ac5 in main () > > No symbol table info available. > > > > > > No idea what's happening. Please help. > > > > Regards, > > Girish > > > > > > On 26 August 2014 15:49, Cory Quammen wrote: > >> > >> Girish, > >> > >> Can you run ParaView with your plugin through a debugger to find out > >> where it is segfaulting? That will point out where the segfault occurs > >> which is often a clue to why it is occurring. > >> > >> Thanks, > >> Cory > >> > >> On Tue, Aug 26, 2014 at 9:41 AM, Girish Ramesh > >> wrote: > >> > Hi, > >> > > >> > I am writing my own plugin but each time I try to add another check > box, > >> > the > >> > plugin suddenly segfaults. I have no idea why. The XML and C++ code > are > >> > attached. > >> > > >> > XML: > >> > > >> > >> > name="FieldLoadStatus" > >> > command="SetFieldLoadStatus" > >> > number_of_elements="1" > >> > default_values="0" > >> > panel_visibility="default" > > >> > > >> > > >> > The values of this property sets the run number. > >> > > >> > > >> > C++: > >> > > >> > public: > >> > vtkTypeMacro(ReadUALGrid, vtkUnstructuredGridAlgorithm); > >> > void PrintSelf(ostream& os, vtkIndent indent); > >> > > >> > static ReadUALGrid *New(); > >> > > >> > vtkGetMacro(Shot,int) > >> > vtkSetMacro(Shot,int); > >> > > >> > vtkGetMacro(Run,int); > >> > vtkSetMacro(Run,int); > >> > > >> > vtkGetMacro(RefRun,int); > >> > vtkSetMacro(RefRun,int); > >> > > >> > vtkGetMacro(CPOLoad,int); > >> > vtkSetMacro(CPOLoad,int); > >> > > >> > vtkGetMacro(FieldLoadStatus,int); > >> > vtkSetMacro(FieldLoadStatus,int); > >> > > >> > protected: > >> > ReadUALGrid(); > >> > ~ReadUALGrid(){} > >> > > >> > int Shot; > >> > int Run; > >> > int RefRun; > >> > int CPOLoad; > >> > int FieldLoadStatus; > >> > > >> > I have no idea why because it worked perfectly for other check boxes. > >> > Thank > >> > you. > >> > > >> > Regards, > >> > Girish > >> > > >> > _______________________________________________ > >> > 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 sankhesh.jhaveri at kitware.com Tue Aug 26 12:31:05 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Tue, 26 Aug 2014 09:31:05 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Monday, August 25 2014 Message-ID: <20140826163103.A50A07FF4E@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]ubuntu-x64-nightlymaster 1 -------------------- REPORT -------------------- 1 FAILURES [2]pvcrs.ChartAxisRangeAndLabels , 1 , ['ubuntu-x64-nightlymaster'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [3]ubuntu-x64-nightlynext 4 -------------------- REPORT -------------------- 4 FAILURES [4]pvcs.CatalystLiveSetBreakpoint , 1 , ['ubuntu-x64-nightlynext'] [5]pv.ColorOpacityTableEditing , 1 , ['ubuntu-x64-nightlynext'] [6]pv.Contour , 1 , ['ubuntu-x64-nightlynext'] [7]pvcrs.Contour , 1 , ['ubuntu-x64-nightlynext'] Issues with submitters The following expected submitters did not submit: tarvalon.kitware , Win7x64-vs10-static-release tarvalon.kitware , Win7x64-vs10-static-release KargadMac.kitware , Lion-gcc-pvVTK kamino.kitware , Mac10.7.5-gcc-nightlymaster-release kamino.kitware , Mac10.7.5-clang-nightlymaster-release References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlymaster 2. http://open.cdash.org/testSummary.php?project=9&date=2014-08-26&name=pvcrs.ChartAxisRangeAndLabels 3. http://open.cdash.org/index.php?project=ParaView&date=2014-08-26&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 4. http://open.cdash.org/testSummary.php?project=9&date=2014-08-26&name=pvcs.CatalystLiveSetBreakpoint 5. http://open.cdash.org/testSummary.php?project=9&date=2014-08-26&name=pv.ColorOpacityTableEditing 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-26&name=pv.Contour 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-26&name=pvcrs.Contour -------------- next part -------------- An HTML attachment was scrubbed... URL: From biddisco at cscs.ch Wed Aug 27 03:16:43 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Wed, 27 Aug 2014 07:16:43 +0000 Subject: [Paraview-developers] vtkStreamingDemandDrivenPipeline::EXTENT_TRANSLATOR Message-ID: <50320452A334BD42A5EC72BAD214509916C0768B@MBX210.d.ethz.ch> Recompiling my Paraview plugins against the latest version, I find that many of the vtk::Keys I use frequently are gone. In order to handle my dynamic load balancing, I use the extent translators (particularly my own custom ones) continuously. Is there a replacement for this? thanks JB -- John Biddiscombe, email:biddisco @.at.@ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Wed Aug 27 07:36:05 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 27 Aug 2014 07:36:05 -0400 Subject: [Paraview-developers] vtkStreamingDemandDrivenPipeline::EXTENT_TRANSLATOR In-Reply-To: <50320452A334BD42A5EC72BAD214509916C0768B@MBX210.d.ethz.ch> References: <50320452A334BD42A5EC72BAD214509916C0768B@MBX210.d.ethz.ch> Message-ID: Hi John, Check out: http://www.vtk.org/Wiki/VTK/Parallel_Pipeline Overall, load balancing should be much easier now. The reader can make arbitrary partitioning decisions but can still get requests from downstream about partitioning. Two main strategies: - Downstream send extent + piece requests, reader does its own partitioning based on these two - Downstream send specific extent requests to each rank (and no piece) The first one is appropriate to ParaView. This is much more robust and works through extract vois with subsampling etc. Something that never worked well in parallel. -berk On Wed, Aug 27, 2014 at 3:16 AM, Biddiscombe, John A. wrote: > Recompiling my Paraview plugins against the latest version, I find that > many of the vtk::Keys I use frequently are gone. > > > > In order to handle my dynamic load balancing, I use the extent translators > (particularly my own custom ones) continuously. > > > > Is there a replacement for this? > > > > thanks > > > > JB > > > > -- > > John Biddiscombe, email:biddisco @.at.@ cscs.ch > > http://www.cscs.ch/ > > CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 > > Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 > > > > _______________________________________________ > 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 biddisco at cscs.ch Wed Aug 27 07:46:53 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Wed, 27 Aug 2014 11:46:53 +0000 Subject: [Paraview-developers] vtkStreamingDemandDrivenPipeline::EXTENT_TRANSLATOR In-Reply-To: References: <50320452A334BD42A5EC72BAD214509916C0768B@MBX210.d.ethz.ch> Message-ID: <50320452A334BD42A5EC72BAD214509916C0798E@MBX210.d.ethz.ch> Berk, OK. I see how the piece requests change, but I was using the extent translator to pass bounds information and (more importantly) a PKdTree (from Zoltan) downstream to the compositing engine to stop it from instantiating the D3 filter and performing a redundant and slow repartition when I enable transparency. My Zoltan partitioner used to add an extent translator (also containgin the KdTree) to the information in the pipeline, which the compositing code could detect and act appropriately (with some minor tweaks). Has the compositing code been enhanced in any way to make use of partitioning information that I can piggy-back for my needs? JB From: Berk Geveci [mailto:berk.geveci at kitware.com] Sent: 27 August 2014 13:36 To: Biddiscombe, John A. Cc: vtk-developers at vtk.org; paraview-developers at paraview.org Subject: Re: [Paraview-developers] vtkStreamingDemandDrivenPipeline::EXTENT_TRANSLATOR Hi John, Check out: http://www.vtk.org/Wiki/VTK/Parallel_Pipeline Overall, load balancing should be much easier now. The reader can make arbitrary partitioning decisions but can still get requests from downstream about partitioning. Two main strategies: - Downstream send extent + piece requests, reader does its own partitioning based on these two - Downstream send specific extent requests to each rank (and no piece) The first one is appropriate to ParaView. This is much more robust and works through extract vois with subsampling etc. Something that never worked well in parallel. -berk On Wed, Aug 27, 2014 at 3:16 AM, Biddiscombe, John A. > wrote: Recompiling my Paraview plugins against the latest version, I find that many of the vtk::Keys I use frequently are gone. In order to handle my dynamic load balancing, I use the extent translators (particularly my own custom ones) continuously. Is there a replacement for this? thanks JB -- John Biddiscombe, email:biddisco @.at.@ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 _______________________________________________ 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 utkarsh.ayachit at kitware.com Wed Aug 27 08:24:58 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 27 Aug 2014 08:24:58 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: Topics merged into master: (VTK) 14969_marshal_vtkStructuredGrid cleanups fix_file_open_slowdown live-breakpoint python_syntax_highlighting (VTK) slice_along_polyline vr_plugin_fixes -------------- next part -------------- An HTML attachment was scrubbed... URL: From felipe.bordeu at ec-nantes.fr Wed Aug 27 10:03:48 2014 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu) Date: Wed, 27 Aug 2014 16:03:48 +0200 Subject: [Paraview-developers] apply a filter to only a selected block Message-ID: <53FDE544.4070107@ec-nantes.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm writing a filter to apply a filter(for example a cut, or clip ) to only a selected block of a vtkMultiBlockData. So I start reading the implementation of the vtkExtractBlock and vtkPVGlyphFilter (because I what to select interactively the filter to apply in the same way we can choose the type of glyph). Now the problematic point. This is the part of the xml to select the filter to apply (in the same way as the glyph filter) : The interface is generated correctly in paraview. In the code a receive the algorithm with this function vtkfiltertest::vtkSetMacro(algoToApply, vtkAlgorithmOutput*); But I don't know how to set the input to the algorithm. I tried this (vtkDataSet* tmpinput is a pointer to some data, ) void vtkfiltertest::SetalgoToApply (vtkAlgorithmOutput* _arg) { if (this->algoToApply != _arg) { this->algoToApply = _arg; this->algoToApply->GetProducer()->SetInputDataObject(0,tmpinput); this->Modified(); } } and also in vtkfiltertest::RequestInformation(){ ... this->algoToApply->GetProducer()->SetInputDataObject(0,tmpinput); .. } but in paraview when I create the vtkfiltertest (click in the menu) I get this: ERROR: In /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 710 vtkPVCompositeDataPipeline (0x7845e80): Input port 0 of algorithm vtkPVMetaSliceDataSet(0x783d880) has 0 connections but is not optional. Is this possible of I'm asking to much??? Thanks. - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJT/eUzAAoJEE/fMfNgU9/DW1MH/2Fe2fW+7lgISDrO5o5DTnRV koyJmwSXu+Bx4JRmSLlwIZRUTQ1AfFNE/YGnPZi2db8jmoWrgEs4RS/xwS1873zj cDRD9NX44PRYS4p4IBYmDmmAucny8IaeB9sDBLhsC0SxJNHiaIzJxYlFvprxZh8h saRXjR0J3sUp3vGDCKrPui9JfOpZ/IT70hpKI4WPg71TiAftEiuc9wQtPZIbNawE nzR4ZudhdHG0LY3ipCy0/faTuPkdgqmuXKtsLxIhfQHyKHjhXluw7iKvsg02Wal+ bpA1XvaIJq9tlagXBEHhpN+KnO3yERG3Agi8o4b8j5ke+/pNoupEDzvjTYAQZYY= =TtDg -----END PGP SIGNATURE----- From sankhesh.jhaveri at kitware.com Wed Aug 27 12:31:08 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Wed, 27 Aug 2014 09:31:08 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Tuesday, August 26 2014 Message-ID: <20140827163103.CF0AC7FF94@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Win7x64-vs9-nightlymaster-shared-release 6 -------------------- REPORT -------------------- 6 FAILURES [2]pv.LoadStateMultiView , 1 , ['Win7x64-vs9-nightlymaster-shared-release'] [3]pv.Contour , 1 , ['Win7x64-vs9-nightlymaster-shared-release'] [4]pv.LineChartSelection , 1 , ['Win7x64-vs9-nightlymaster-shared-release'] [5]pv.FileSeries , 1 , ['Win7x64-vs9-nightlymaster-shared-release'] [6]pv.TestPythonConsole , 1 , ['Win7x64-vs9-nightlymaster-shared-release'] [7]pv.SearchBox , 1 , ['Win7x64-vs9-nightlymaster-shared-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [8]Win32-vs9-shared-release 1 -------------------- REPORT -------------------- 1 FAILURES [9]pvcs-collab.CreateDelete , 1 , ['Win32-vs9-shared-release'] Issues with submitters The following expected submitters did not submit: KargadMac.kitware , Lion-gcc-pvVTK kamino.kitware , Mac10.7.5-gcc-nightlymaster-release kamino.kitware , Mac10.7.5-clang-nightlymaster-release References 1. http://open.cdash.org/index.php?project=ParaView&date=2014-08-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs9-nightlymaster-shared-release 2. http://open.cdash.org/testSummary.php?project=9&date=2014-08-27&name=pv.LoadStateMultiView 3. http://open.cdash.org/testSummary.php?project=9&date=2014-08-27&name=pv.Contour 4. http://open.cdash.org/testSummary.php?project=9&date=2014-08-27&name=pv.LineChartSelection 5. http://open.cdash.org/testSummary.php?project=9&date=2014-08-27&name=pv.FileSeries 6. http://open.cdash.org/testSummary.php?project=9&date=2014-08-27&name=pv.TestPythonConsole 7. http://open.cdash.org/testSummary.php?project=9&date=2014-08-27&name=pv.SearchBox 8. http://open.cdash.org/index.php?project=ParaView&date=2014-08-27&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 9. http://open.cdash.org/testSummary.php?project=9&date=2014-08-27&name=pvcs-collab.CreateDelete -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Wed Aug 27 18:03:06 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 27 Aug 2014 18:03:06 -0400 Subject: [Paraview-developers] [vtk-developers] vtkStreamingDemandDrivenPipeline::EXTENT_TRANSLATOR In-Reply-To: <50320452A334BD42A5EC72BAD214509916C0798E@MBX210.d.ethz.ch> References: <50320452A334BD42A5EC72BAD214509916C0768B@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509916C0798E@MBX210.d.ethz.ch> Message-ID: Hi John, Good news. It is now much easier to propagate meta-data and requests in VTK now. (Don't give me a hard time about not communicating this. I am working on my issues). All you need is a subclass of a vtkInformationKey that overrides CopyDefaultInformation(), probably to copy itself. Look at vtkEnsembleSource and vtkInformationDataObjectMetaDataKey to see an example. In fact, if your kd tree is a vtkDataObject subclass, you can use that key class to define a custom key like vtkEnsembleSource. No more need for keys to copy silliness. There is also support for adding arbitrary request objects without changing executives. Look at vtkInformationIntegerRequestKey to see an example. You need a key subclass that overrides CopyDefaultInformation(), NeedToExecute(), StoreMetaData() for that. I will write a blog with details in the near future. Best, -berk On Wed, Aug 27, 2014 at 7:46 AM, Biddiscombe, John A. wrote: > Berk, > > > > OK. I see how the piece requests change, but I was using the extent > translator to pass bounds information and (more importantly) a PKdTree > (from Zoltan) downstream to the compositing engine to stop it from > instantiating the D3 filter and performing a redundant and slow repartition > when I enable transparency. My Zoltan partitioner used to add an extent > translator (also containgin the KdTree) to the information in the pipeline, > which the compositing code could detect and act appropriately (with some > minor tweaks). > > > > Has the compositing code been enhanced in any way to make use of > partitioning information that I can piggy-back for my needs? > > > > JB > > > > *From:* Berk Geveci [mailto:berk.geveci at kitware.com] > *Sent:* 27 August 2014 13:36 > *To:* Biddiscombe, John A. > *Cc:* vtk-developers at vtk.org; paraview-developers at paraview.org > *Subject:* Re: [Paraview-developers] > vtkStreamingDemandDrivenPipeline::EXTENT_TRANSLATOR > > > > Hi John, > > > > Check out: > > > > http://www.vtk.org/Wiki/VTK/Parallel_Pipeline > > > > Overall, load balancing should be much easier now. The reader can make > arbitrary partitioning decisions but can still get requests from downstream > about partitioning. Two main strategies: > > > > - Downstream send extent + piece requests, reader does its own > partitioning based on these two > > - Downstream send specific extent requests to each rank (and no piece) > > > > The first one is appropriate to ParaView. > > > > This is much more robust and works through extract vois with subsampling > etc. Something that never worked well in parallel. > > > > -berk > > > > On Wed, Aug 27, 2014 at 3:16 AM, Biddiscombe, John A. > wrote: > > Recompiling my Paraview plugins against the latest version, I find that > many of the vtk::Keys I use frequently are gone. > > > > In order to handle my dynamic load balancing, I use the extent translators > (particularly my own custom ones) continuously. > > > > Is there a replacement for this? > > > > thanks > > > > JB > > > > -- > > John Biddiscombe, email:biddisco @.at.@ cscs.ch > > http://www.cscs.ch/ > > CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 > > Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 > > > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 27 22:44:07 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 27 Aug 2014 22:44:07 -0400 Subject: [Paraview-developers] Plugin: Add a submenu to a menu? In-Reply-To: <53F73B62.6080503@gmail.com> References: <53F73B62.6080503@gmail.com> Message-ID: There's an easier way for this now: Just add the following for the filter/source proxy's XML. You can add multiple elements too. On Fri, Aug 22, 2014 at 8:45 AM, Panos Asproulis wrote: > Hi all, > > In the section "Adding a Menu" of the ParaView Wiki regarding the > development of plugins there is a note about adding a menu to the ParaView > menu bar using the following: > > ADD_PARAVIEW_ACTION_GROUP(IFACES IFACE_SRCS > CLASS_NAME SourceToolbarActions > GROUP_NAME "MenuBar/MyActions") > > > However, the added element SourceToolbarActions is a QActionGroup and > therefore it can only have actions which are displayed as elements of a > menu. What if one wants to add a submenu to this new menu which appears as > "MyActions" in the ParaView menu bar? > > Thanks in advance, > Panos > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Wed Aug 27 22:45:21 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 27 Aug 2014 22:45:21 -0400 Subject: [Paraview-developers] Plugin: Add a submenu to a menu? In-Reply-To: References: <53F73B62.6080503@gmail.com> Message-ID: ...and sub-sub menus, alas, are not supported. You can only go 1 level down the from the Filters or Sources menu currently. On Wed, Aug 27, 2014 at 10:44 PM, Utkarsh Ayachit wrote: > There's an easier way for this now: > > Just add the following for the filter/source proxy's XML. > > > > > > > > > You can add multiple elements too. > > > On Fri, Aug 22, 2014 at 8:45 AM, Panos Asproulis > wrote: >> Hi all, >> >> In the section "Adding a Menu" of the ParaView Wiki regarding the >> development of plugins there is a note about adding a menu to the ParaView >> menu bar using the following: >> >> ADD_PARAVIEW_ACTION_GROUP(IFACES IFACE_SRCS >> CLASS_NAME SourceToolbarActions >> GROUP_NAME "MenuBar/MyActions") >> >> >> However, the added element SourceToolbarActions is a QActionGroup and >> therefore it can only have actions which are displayed as elements of a >> menu. What if one wants to add a submenu to this new menu which appears as >> "MyActions" in the ParaView menu bar? >> >> Thanks in advance, >> Panos >> >> _______________________________________________ >> Paraview-developers mailing list >> Paraview-developers at paraview.org >> http://public.kitware.com/mailman/listinfo/paraview-developers >> From utkarsh.ayachit at kitware.com Thu Aug 28 09:26:07 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Aug 2014 09:26:07 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: SUMMARY --------------------------------------------- Topics merged into master: 14956_fix_extract_selection add-vtk-adios fix-catalyst-base (VTK) support-future-use-of-crossbar-io From biddisco at cscs.ch Thu Aug 28 10:10:42 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Thu, 28 Aug 2014 14:10:42 +0000 Subject: [Paraview-developers] [vtk-developers] vtkStreamingDemandDrivenPipeline::EXTENT_TRANSLATOR In-Reply-To: References: <50320452A334BD42A5EC72BAD214509916C0768B@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509916C0798E@MBX210.d.ethz.ch> Message-ID: <50320452A334BD42A5EC72BAD214509918DC428E@MBX110.d.ethz.ch> Berk Thanks once more for the info. Question : The class I want to pass downstream is a vtkObject and not a vtkDataObject, so .. There are informationDataObject and InformationDataObjectMetaData keys, but there are not informationObject and InformationObjectMetaData keys, but since DataObject is a type of Object, would anything be adversely affected if I were to change them to InformationObject->InformationObjectMetaData and provide a GetObject and GetDataObject interface to return the type contained? Adding two new classes seems wasteful when they actually do the same thing internally. Do the informationDataObject and metadata key classes need to specialized as different from Object and ObjectMetaData? (other than just for naming purposes) ta JB -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Thu Aug 28 10:16:49 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Thu, 28 Aug 2014 10:16:49 -0400 Subject: [Paraview-developers] [vtk-developers] vtkStreamingDemandDrivenPipeline::EXTENT_TRANSLATOR In-Reply-To: <50320452A334BD42A5EC72BAD214509918DC428E@MBX110.d.ethz.ch> References: <50320452A334BD42A5EC72BAD214509916C0768B@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509916C0798E@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509918DC428E@MBX110.d.ethz.ch> Message-ID: I have no objection whatsoever to changing it to be a subclass of vtkInformationObjectBaseKey and renaming it as such. It should work but please run the ensemble source test to make sure. -berk On Thu, Aug 28, 2014 at 10:10 AM, Biddiscombe, John A. wrote: > Berk > > > > Thanks once more for the info. > > > > Question : > > > > The class I want to pass downstream is a vtkObject and not a > vtkDataObject, so .. > > > > There are > > informationDataObject and InformationDataObjectMetaData keys, but there > are not > > informationObject and InformationObjectMetaData keys, > > > > but since DataObject is a type of Object, would anything be adversely > affected if I were to change them to > > InformationObject->InformationObjectMetaData > > > > and provide a GetObject and GetDataObject interface to return the type > contained? Adding two new classes seems wasteful when they actually do the > same thing internally. > > > > Do the informationDataObject and metadata key classes need to specialized > as different from Object and ObjectMetaData? (other than just for naming > purposes) > > > > ta > > > > JB > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 28 10:30:33 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Aug 2014 10:30:33 -0400 Subject: [Paraview-developers] apply a filter to only a selected block In-Reply-To: <53FDE544.4070107@ec-nantes.fr> References: <53FDE544.4070107@ec-nantes.fr> Message-ID: I am not sure I'd recommend anyone to do this :), but since you're experimenting .. here's something to try: Don't do the SetInputDataObject() in RequestInformation, try passing the output of ExtractBlock to the input in RequestData() instead. Utkarsh On Wed, Aug 27, 2014 at 10:03 AM, Felipe Bordeu wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I'm writing a filter to apply a filter(for example a cut, or clip ) to > only a selected block of a vtkMultiBlockData. > > So I start reading the implementation of the vtkExtractBlock and > vtkPVGlyphFilter (because I what to select interactively the filter to > apply in the same way we can choose the type of glyph). > > Now the problematic point. This is the part of the xml to select the > filter to apply (in the same way as the glyph filter) : > > > label="Filter To Apply" > name="Source"> > > > > > > > > > > > > > > > > The interface is generated correctly in paraview. > In the code a receive the algorithm with this function > > vtkfiltertest::vtkSetMacro(algoToApply, vtkAlgorithmOutput*); > > > But I don't know how to set the input to the algorithm. > > I tried this (vtkDataSet* tmpinput is a pointer to some data, ) > > void vtkfiltertest::SetalgoToApply (vtkAlgorithmOutput* _arg) { > if (this->algoToApply != _arg) { > this->algoToApply = _arg; > this->algoToApply->GetProducer()->SetInputDataObject(0,tmpinput); > this->Modified(); > } > } > > and also in > vtkfiltertest::RequestInformation(){ > ... > this->algoToApply->GetProducer()->SetInputDataObject(0,tmpinput); > .. > } > > but in paraview when I create the vtkfiltertest (click in the menu) I > get this: > > ERROR: In > /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 710 > vtkPVCompositeDataPipeline (0x7845e80): Input port 0 of algorithm > vtkPVMetaSliceDataSet(0x783d880) has 0 connections but is not optional. > > Is this possible of I'm asking to much??? > > Thanks. > - -- > Felipe Bordeu Weldt > Ing?nieur de Recherche > - ------------------------------------- > T?l. : 33 (0)2 40 37 16 57 > Fax. : 33 (0)2 40 74 74 06 > Felipe.Bordeu at ec-nantes.fr > Institut GeM - UMR CNRS 6183 > ?cole Centrale Nantes > 1 Rue de La No?, 44321 Nantes, FRANCE > - ------------------------------------- > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEcBAEBAgAGBQJT/eUzAAoJEE/fMfNgU9/DW1MH/2Fe2fW+7lgISDrO5o5DTnRV > koyJmwSXu+Bx4JRmSLlwIZRUTQ1AfFNE/YGnPZi2db8jmoWrgEs4RS/xwS1873zj > cDRD9NX44PRYS4p4IBYmDmmAucny8IaeB9sDBLhsC0SxJNHiaIzJxYlFvprxZh8h > saRXjR0J3sUp3vGDCKrPui9JfOpZ/IT70hpKI4WPg71TiAftEiuc9wQtPZIbNawE > nzR4ZudhdHG0LY3ipCy0/faTuPkdgqmuXKtsLxIhfQHyKHjhXluw7iKvsg02Wal+ > bpA1XvaIJq9tlagXBEHhpN+KnO3yERG3Agi8o4b8j5ke+/pNoupEDzvjTYAQZYY= > =TtDg > -----END PGP SIGNATURE----- > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers From utkarsh.ayachit at kitware.com Thu Aug 28 11:05:04 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Aug 2014 11:05:04 -0400 Subject: [Paraview-developers] How to read time data in custom reader plugin In-Reply-To: References: Message-ID: 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 felipe.bordeu at ec-nantes.fr Thu Aug 28 12:04:33 2014 From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu) Date: Thu, 28 Aug 2014 18:04:33 +0200 Subject: [Paraview-developers] apply a filter to only a selected block In-Reply-To: References: <53FDE544.4070107@ec-nantes.fr> Message-ID: <53FF5311.9090202@ec-nantes.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks, It works, but (I know there is always a but)... 1) Paraview (at the creation of my mainfilter) calls RequestInformation on all the internal filters available, and because they don't have connections, I get plenty of : ERROR: In /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 783 vtkPVCompositeDataPipeline (0x686f5b0): Algorithm vtkPVArrayCalculator(0x6875210) returned failure for request: vtkInformation (0x686dde0) ERROR: In /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 710 vtkPVCompositeDataPipeline (0x6940a30): Input port 0 of algorithm vtkPVMetaClipDataSet(0x6921660) has 0 connections but is not optional. ERROR: In /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 710 vtkPVCompositeDataPipeline (0x6969450): Input port 0 of algorithm vtkThreshold(0x696f170) has 0 connections but is not optional. ERROR: In /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 710 vtkPVCompositeDataPipeline (0x6977740): Input port 0 of algorithm vtkDataSetSurfaceFilter(0x697f540) has 0 connections but is not optional. 2) The panels of filters with custom widget are not generated correctly (the case of the calculator filter). 3) Because of the filters don't have information about the input, the 3D widget are not plot in the renderview ( the plane of the clip filter) I know I'm trying to do something tricky, but we do this kind of operation often (extract a block apply a filter, extract another block apply a filter, extract all the remaining block, and then do "append datasets" to recover a multi-block structure). And even with this we lost the original structure of the multi-block. the point 2 and tree are not that important (we can set the data from the panel, and for the calculator we still have the function field) Felipe ps: in the attachement there is an image of the filter Le 28/08/2014 16:30, Utkarsh Ayachit a ?crit : > I am not sure I'd recommend anyone to do this :), but since you're > experimenting .. here's something to try: > > Don't do the SetInputDataObject() in RequestInformation, try passing > the output of ExtractBlock to the input in RequestData() instead. > > Utkarsh > > On Wed, Aug 27, 2014 at 10:03 AM, Felipe Bordeu > wrote: > Hi, > > I'm writing a filter to apply a filter(for example a cut, or clip ) to > only a selected block of a vtkMultiBlockData. > > So I start reading the implementation of the vtkExtractBlock and > vtkPVGlyphFilter (because I what to select interactively the filter to > apply in the same way we can choose the type of glyph). > > Now the problematic point. This is the part of the xml to select the > filter to apply (in the same way as the glyph filter) : > > > label="Filter To Apply" > name="Source"> > > > > > > > > > > > > > > > > The interface is generated correctly in paraview. > In the code a receive the algorithm with this function > > vtkfiltertest::vtkSetMacro(algoToApply, vtkAlgorithmOutput*); > > > But I don't know how to set the input to the algorithm. > > I tried this (vtkDataSet* tmpinput is a pointer to some data, ) > > void vtkfiltertest::SetalgoToApply (vtkAlgorithmOutput* _arg) { > if (this->algoToApply != _arg) { > this->algoToApply = _arg; > this->algoToApply->GetProducer()->SetInputDataObject(0,tmpinput); > this->Modified(); > } > } > > and also in > vtkfiltertest::RequestInformation(){ > ... > this->algoToApply->GetProducer()->SetInputDataObject(0,tmpinput); > .. > } > > but in paraview when I create the vtkfiltertest (click in the menu) I > get this: > > ERROR: In > /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 710 > vtkPVCompositeDataPipeline (0x7845e80): Input port 0 of algorithm > vtkPVMetaSliceDataSet(0x783d880) has 0 connections but is not optional. > > Is this possible of I'm asking to much??? > > Thanks. >> _______________________________________________ >> Paraview-developers mailing list >> Paraview-developers at paraview.org >> http://public.kitware.com/mailman/listinfo/paraview-developers - -- Felipe Bordeu Weldt Ing?nieur de Recherche - ------------------------------------- T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes 1 Rue de La No?, 44321 Nantes, FRANCE - ------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJT/1MLAAoJEE/fMfNgU9/D4RIH/iWwW2KqkzTEnuFu7fTEMTNs yraqs/bTO8YLqsWkx5k2bnzT7zu1aCEzaWLFncZIrVVNJXdiY9o/XnO7g9Dqi/Rb pHgqkdwTaC9XTFSfbl0P55QsdlIcURE/5hue3WvoVE2PGjiWHf282zeTytuj++Vw jvSgpLLJVvW3b4BWssgtAb7o8BVdy5YoHf+gqdfi5pIgYsGtpBv60VcdCjTmIrSx RNii9eLHmBRYWqahyIuvvOej4H8Yb94n6PcK/Wd+pJS/JaFf872GDLHXaglj77zw EJYrT19WvFEW3rpLZLsi+ccLCXvk0Y67EEiHdpHNpDxQPu9fy4MmEie9I74gJ4o= =NYLZ -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: imageApplyOnBlocks.png Type: image/png Size: 45321 bytes Desc: not available URL: From sankhesh.jhaveri at kitware.com Thu Aug 28 12:31:10 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Thu, 28 Aug 2014 09:31:10 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Wednesday, August 27 2014 Message-ID: <20140828163103.608847FFE5@sanganak-ubuntu> Dashboard status for Nightly (master) -------------------- ANALYZING -------------------- [1]Win7x64-vs10-shared-release 1 -------------------- REPORT -------------------- 1 FAILURES [2]pv.OpenHelp , 1 , ['Win7x64-vs10-shared-release'] Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [3]ubuntu-x64-nightlynext-nogui 1 [4]ubuntu-x64-coverage 1 -------------------- REPORT -------------------- 1 FAILURES [5]pvweb-chrome.TestApp-all , 2 , ['ubuntu-x64-nightlynext-nogui', 'ubuntu-x64-coverage'] 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-08-28&filtercount=1&field1=buildname/string&compare1=61&value1=Win7x64-vs10-shared-release 2. http://open.cdash.org/testSummary.php?project=9&date=2014-08-28&name=pv.OpenHelp 3. http://open.cdash.org/index.php?project=ParaView&date=2014-08-28&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext-nogui 4. http://open.cdash.org/index.php?project=ParaView&date=2014-08-28&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage 5. http://open.cdash.org/testSummary.php?project=9&date=2014-08-28&name=pvweb-chrome.TestApp-all -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 28 12:49:18 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Aug 2014 12:49:18 -0400 Subject: [Paraview-developers] apply a filter to only a selected block In-Reply-To: <53FF5311.9090202@ec-nantes.fr> References: <53FDE544.4070107@ec-nantes.fr> <53FF5311.9090202@ec-nantes.fr> Message-ID: Maybe go the custom filter route instead. You cannot have a choice of filters to chose from a comb-box, in that case. But you can create a ExtractBlock+Filter version of every filter you're interested in. Something similar to how we deal with file-series readers, for example. On Thu, Aug 28, 2014 at 12:04 PM, Felipe Bordeu wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Thanks, > > It works, but (I know there is always a but)... > > 1) Paraview (at the creation of my mainfilter) calls RequestInformation > on all the internal filters available, and because they don't have > connections, I get plenty of : > > ERROR: In > /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkExecutive.cxx, > line 783 > vtkPVCompositeDataPipeline (0x686f5b0): Algorithm > vtkPVArrayCalculator(0x6875210) returned failure for request: > vtkInformation (0x686dde0) > > ERROR: In > /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 710 > vtkPVCompositeDataPipeline (0x6940a30): Input port 0 of algorithm > vtkPVMetaClipDataSet(0x6921660) has 0 connections but is not optional. > > > ERROR: In > /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 710 > vtkPVCompositeDataPipeline (0x6969450): Input port 0 of algorithm > vtkThreshold(0x696f170) has 0 connections but is not optional. > > > ERROR: In > /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, > line 710 > vtkPVCompositeDataPipeline (0x6977740): Input port 0 of algorithm > vtkDataSetSurfaceFilter(0x697f540) has 0 connections but is not optional. > > 2) The panels of filters with custom widget are not generated correctly > (the case of the calculator filter). > > 3) Because of the filters don't have information about the input, the 3D > widget are not plot in the renderview ( the plane of the clip filter) > > I know I'm trying to do something tricky, but we do this kind of > operation often (extract a block apply a filter, extract another block > apply a filter, extract all the remaining block, and then do "append > datasets" to recover a multi-block structure). And even with this we > lost the original structure of the multi-block. > > the point 2 and tree are not that important (we can set the data from > the panel, and for the calculator we still have the function field) > > Felipe > > ps: in the attachement there is an image of the filter > > Le 28/08/2014 16:30, Utkarsh Ayachit a ?crit : >> I am not sure I'd recommend anyone to do this :), but since you're >> experimenting .. here's something to try: >> >> Don't do the SetInputDataObject() in RequestInformation, try passing >> the output of ExtractBlock to the input in RequestData() instead. >> >> Utkarsh >> >> On Wed, Aug 27, 2014 at 10:03 AM, Felipe Bordeu >> wrote: >> Hi, >> >> I'm writing a filter to apply a filter(for example a cut, or clip ) to >> only a selected block of a vtkMultiBlockData. >> >> So I start reading the implementation of the vtkExtractBlock and >> vtkPVGlyphFilter (because I what to select interactively the filter to >> apply in the same way we can choose the type of glyph). >> >> Now the problematic point. This is the part of the xml to select the >> filter to apply (in the same way as the glyph filter) : >> >> >> > label="Filter To Apply" >> name="Source"> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> The interface is generated correctly in paraview. >> In the code a receive the algorithm with this function >> >> vtkfiltertest::vtkSetMacro(algoToApply, vtkAlgorithmOutput*); >> >> >> But I don't know how to set the input to the algorithm. >> >> I tried this (vtkDataSet* tmpinput is a pointer to some data, ) >> >> void vtkfiltertest::SetalgoToApply (vtkAlgorithmOutput* _arg) { >> if (this->algoToApply != _arg) { >> this->algoToApply = _arg; >> this->algoToApply->GetProducer()->SetInputDataObject(0,tmpinput); >> this->Modified(); >> } >> } >> >> and also in >> vtkfiltertest::RequestInformation(){ >> ... >> this->algoToApply->GetProducer()->SetInputDataObject(0,tmpinput); >> .. >> } >> >> but in paraview when I create the vtkfiltertest (click in the menu) I >> get this: >> >> ERROR: In >> /Big/fbordeu/sources/ParaView4/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, >> line 710 >> vtkPVCompositeDataPipeline (0x7845e80): Input port 0 of algorithm >> vtkPVMetaSliceDataSet(0x783d880) has 0 connections but is not optional. >> >> Is this possible of I'm asking to much??? >> >> Thanks. >>> _______________________________________________ >>> Paraview-developers mailing list >>> Paraview-developers at paraview.org >>> http://public.kitware.com/mailman/listinfo/paraview-developers > > - -- > Felipe Bordeu Weldt > Ing?nieur de Recherche > - ------------------------------------- > T?l. : 33 (0)2 40 37 16 57 > Fax. : 33 (0)2 40 74 74 06 > Felipe.Bordeu at ec-nantes.fr > Institut GeM - UMR CNRS 6183 > ?cole Centrale Nantes > 1 Rue de La No?, 44321 Nantes, FRANCE > - ------------------------------------- > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEcBAEBAgAGBQJT/1MLAAoJEE/fMfNgU9/D4RIH/iWwW2KqkzTEnuFu7fTEMTNs > yraqs/bTO8YLqsWkx5k2bnzT7zu1aCEzaWLFncZIrVVNJXdiY9o/XnO7g9Dqi/Rb > pHgqkdwTaC9XTFSfbl0P55QsdlIcURE/5hue3WvoVE2PGjiWHf282zeTytuj++Vw > jvSgpLLJVvW3b4BWssgtAb7o8BVdy5YoHf+gqdfi5pIgYsGtpBv60VcdCjTmIrSx > RNii9eLHmBRYWqahyIuvvOej4H8Yb94n6PcK/Wd+pJS/JaFf872GDLHXaglj77zw > EJYrT19WvFEW3rpLZLsi+ccLCXvk0Y67EEiHdpHNpDxQPu9fy4MmEie9I74gJ4o= > =NYLZ > -----END PGP SIGNATURE----- From utkarsh.ayachit at kitware.com Fri Aug 29 10:12:05 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 29 Aug 2014 10:12:05 -0400 Subject: [Paraview-developers] Gatekeeper Review Summary Message-ID: Topics merged into master: fix_warnings support_extract_location From utkarsh.ayachit at kitware.com Fri Aug 29 10:26:26 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 29 Aug 2014 10:26:26 -0400 Subject: [Paraview-developers] ANN: ParaView 4.2.0-RC1 Tagged! Message-ID: Good morning folks! ParaView 4.2.0-RC1 has been tagged! git tag name: v4.2.0-RC1 Binaries will be available for testing within the next few days. Utkarsh From sankhesh.jhaveri at kitware.com Fri Aug 29 12:31:18 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Fri, 29 Aug 2014 09:31:18 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Thursday, August 28 2014 Message-ID: <20140829163103.ADFB07FF8C@sanganak-ubuntu> Dashboard status for Nightly (master) Cdash returned nothing useful as of this report. Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [1]Win32-vs9-shared-release 1 -------------------- REPORT -------------------- 1 FAILURES [2]pvcrs.CalcParens , 1 , ['Win32-vs9-shared-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-08-29&filtercount=1&field1=buildname/string&compare1=61&value1=Win32-vs9-shared-release 2. http://open.cdash.org/testSummary.php?project=9&date=2014-08-29&name=pvcrs.CalcParens -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlih at masonlive.gmu.edu Fri Aug 29 12:50:56 2014 From: jlih at masonlive.gmu.edu (jlih) Date: Fri, 29 Aug 2014 16:50:56 +0000 Subject: [Paraview-developers] Paraviewweb: possbilities of integrating python scripts? Message-ID: <1409331056518.31974@masonlive.gmu.edu> Dear all, I have developed a few python scripts that calls pvserver to perform visualization functions for my datasets. I've noticed Paraviewweb has provided quite a few good functions to perform interactive manipulation within a browser. I have installed Paraviewweb on a server. I am wondering if I can use my python scripts as a basis to develop server side functions and use JSP functions provided by Paraviewweb as front-end to customize a website for my application. The purpose is to provide the visualization functions to users who do not have access to datasets and computing resources. Should I use "Python Launcher" to start? Thanks in advance. Jing -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Fri Aug 29 13:00:20 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Fri, 29 Aug 2014 11:00:20 -0600 Subject: [Paraview-developers] Paraviewweb: possbilities of integrating python scripts? In-Reply-To: <1409331056518.31974@masonlive.gmu.edu> References: <1409331056518.31974@masonlive.gmu.edu> Message-ID: Hi Jing, I'm glad to hear that you setup a ParaViewWeb instance on your end. And you are right, you can use your server side python scripts to extend existing ParaViewWeb application or even create your own one. We don't rely on JSP per say but on pure JavaScript which allow you to expose server side features on the client side. The Python launcher is made to allow several users to start their own visualization process automatically, but if you plan to develop your own app leveraging your scripts, you can start without it. Some useful resources can be found here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html Seb On Fri, Aug 29, 2014 at 10:50 AM, jlih wrote: > Dear all, > > I have developed a few python scripts that calls pvserver to perform > visualization functions for my datasets. I've noticed Paraviewweb has > provided quite a few good functions to perform interactive manipulation > within a browser. I have installed Paraviewweb on a server. > > > I am wondering if I can use my python scripts as a basis to develop > server side functions and use JSP functions provided by Paraviewweb as > front-end to customize a website for my application. The purpose is to > provide the visualization functions to users who do not have access to > datasets and computing resources. Should I use "Python Launcher" to start? > > > Thanks in advance. > > > Jing > > > > > > _______________________________________________ > 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 jlih at masonlive.gmu.edu Fri Aug 29 17:05:51 2014 From: jlih at masonlive.gmu.edu (jlih) Date: Fri, 29 Aug 2014 21:05:51 +0000 Subject: [Paraview-developers] Paraviewweb: possbilities of integrating python scripts? In-Reply-To: References: <1409331056518.31974@masonlive.gmu.edu>, Message-ID: <1409346343439.62598@masonlive.gmu.edu> Hi Seb, Thanks for your quick reply! Your answer help me understand the role of Javascript and the launcher in the framework. In terms of extending the application, could you provide me an example or point me to the related resources? Thanks again. Best, Jing ________________________________ From: Sebastien Jourdain Sent: Friday, August 29, 2014 1:00 PM To: jlih Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] Paraviewweb: possbilities of integrating python scripts? Hi Jing, I'm glad to hear that you setup a ParaViewWeb instance on your end. And you are right, you can use your server side python scripts to extend existing ParaViewWeb application or even create your own one. We don't rely on JSP per say but on pure JavaScript which allow you to expose server side features on the client side. The Python launcher is made to allow several users to start their own visualization process automatically, but if you plan to develop your own app leveraging your scripts, you can start without it. Some useful resources can be found here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html Seb On Fri, Aug 29, 2014 at 10:50 AM, jlih > wrote: Dear all, I have developed a few python scripts that calls pvserver to perform visualization functions for my datasets. I've noticed Paraviewweb has provided quite a few good functions to perform interactive manipulation within a browser. I have installed Paraviewweb on a server. I am wondering if I can use my python scripts as a basis to develop server side functions and use JSP functions provided by Paraviewweb as front-end to customize a website for my application. The purpose is to provide the visualization functions to users who do not have access to datasets and computing resources. Should I use "Python Launcher" to start? Thanks in advance. Jing _______________________________________________ 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 sebastien.jourdain at kitware.com Sat Aug 30 08:55:34 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Sat, 30 Aug 2014 06:55:34 -0600 Subject: [Paraview-developers] Paraviewweb: possbilities of integrating python scripts? In-Reply-To: <1409346343439.62598@masonlive.gmu.edu> References: <1409331056518.31974@masonlive.gmu.edu> <1409346343439.62598@masonlive.gmu.edu> Message-ID: Hi Jing, The web visualizer is an example by itself. You can look at the vtk web too. Specially the graph one. Seb > On Aug 29, 2014, at 15:05, jlih wrote: > > Hi Seb, > > Thanks for your quick reply! Your answer help me understand the role of Javascript and the launcher in the framework. > > In terms of extending the application, could you provide me an example or point me to the related resources? > > Thanks again. > > Best, > Jing > > From: Sebastien Jourdain > Sent: Friday, August 29, 2014 1:00 PM > To: jlih > Cc: paraview-developers at paraview.org > Subject: Re: [Paraview-developers] Paraviewweb: possbilities of integrating python scripts? > > Hi Jing, > > I'm glad to hear that you setup a ParaViewWeb instance on your end. And you are right, you can use your server side python scripts to extend existing ParaViewWeb application or even create your own one. > > We don't rely on JSP per say but on pure JavaScript which allow you to expose server side features on the client side. > > The Python launcher is made to allow several users to start their own visualization process automatically, but if you plan to develop your own app leveraging your scripts, you can start without it. > > Some useful resources can be found here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html > > Seb > > >> On Fri, Aug 29, 2014 at 10:50 AM, jlih wrote: >> Dear all, >> >> I have developed a few python scripts that calls pvserver to perform visualization functions for my datasets. I've noticed Paraviewweb has provided quite a few good functions to perform interactive manipulation within a browser. I have installed Paraviewweb on a server. >> >> >> I am wondering if I can use my python scripts as a basis to develop server side functions and use JSP functions provided by Paraviewweb as front-end to customize a website for my application. The purpose is to provide the visualization functions to users who do not have access to datasets and computing resources. Should I use "Python Launcher" to start? >> >> Thanks in advance. >> >> >> Jing >> >> >> >> >> >> _______________________________________________ >> 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 sankhesh.jhaveri at kitware.com Sun Aug 31 12:31:07 2014 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Sun, 31 Aug 2014 09:31:07 -0700 (PDT) Subject: [Paraview-developers] Dashboard Status: Saturday, August 30 2014 Message-ID: <20140831163103.DE4B27FFD4@sanganak-ubuntu> Dashboard status for Nightly (master) Cdash returned nothing useful as of this report. Dashboard status for Nightly (next) -------------------- ANALYZING -------------------- [1]ubuntu-x64-nightlynext 1 [2]ubuntu-x64-coverage 1 -------------------- REPORT -------------------- 2 FAILURES [3]pvcs-collab.CreateDelete , 1 , ['ubuntu-x64-nightlynext'] [4]pvweb-chrome.TestApp-all , 1 , ['ubuntu-x64-coverage'] 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-08-31&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-nightlynext 2. http://open.cdash.org/index.php?project=ParaView&date=2014-08-31&filtercount=1&field1=buildname/string&compare1=61&value1=ubuntu-x64-coverage 3. http://open.cdash.org/testSummary.php?project=9&date=2014-08-31&name=pvcs-collab.CreateDelete 4. http://open.cdash.org/testSummary.php?project=9&date=2014-08-31&name=pvweb-chrome.TestApp-all -------------- next part -------------- An HTML attachment was scrubbed... URL: