From utkarsh.ayachit at kitware.com Mon Sep 1 12:33:44 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 1 Sep 2014 12:33:44 -0400 Subject: [Paraview] ANN: ParaView 4.2.0-RC1 now available for download Message-ID: Folks, ParaView 4.2, RC 1 (release candidate) is now available for download [1] . The detailed summary of the changes will follow. In the mean time, check out the blog [2] for posts on several of the new features. An exhaustive list of features implemented and bugs fixed in this release can be found on the bug tracker [3]. The ParaView Team [1] http://www.paraview.org/download/ [2] http://www.kitware.com/blog/home/browse/topic/13 [3] http://paraview.org/Bug/changelog_page.php From guillaume.jacquenot at gmail.com Mon Sep 1 13:41:48 2014 From: guillaume.jacquenot at gmail.com (Guillaume Jacquenot) Date: Mon, 1 Sep 2014 19:41:48 +0200 Subject: [Paraview] Displaying wave elevation in time Message-ID: Dear Paraview users, I would like to display a wave elevation field in Paraview, that is a structured mesh with a scalar data (wave elevation). This mesh moves over time. I came up with a solution based on CSV point files and a delaunay 2d filter in Paraview to represent wave elevation. I ask myself some questions about the input file format, that could contain only points, or a mesh. Is there a dedicated format to do so? Ideally, this format would - be a single file containing all results over time - not repeat data (My CSV files contain repeatdly the same coordinates many many times) I have looked at VTK format, but I can't figure out which one would answer my needs. Can HDf5 file format help? (If it is possible to import hdf5 package in python interpreter) My data could be represented like this ti, y0, y1, y2, y3 x0,z00,z01,z02,z03 x1,z10,z11,z12,z13 x2,z20,z21,z22,z23 x3,z30,z31,z32,z33 x4,z40,z41,z42,z43 x5,z50,z51,z52,z53 where ti represents a timestep Guillaume Jacquenot Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From samuelkey at bresnan.net Mon Sep 1 16:46:04 2014 From: samuelkey at bresnan.net (Samuel Key) Date: Mon, 01 Sep 2014 14:46:04 -0600 Subject: [Paraview] Displaying wave elevation in time In-Reply-To: References: Message-ID: <5404DB0C.4060005@bresnan.net> An HTML attachment was scrubbed... URL: -------------- next part -------------- FORMAT type: ensight gold GEOMETRY model: 1 1 fmaego.data.geom change_coords_only VARIABLE vector per node: 1 1 Displacement fmaego.data.ndis vector per node: 1 1 Velocity fmaego.data.nvel vector per node: 1 1 Acceleration fmaego.data.nacc vector per node: 1 1 Max-Velocity fmaego.data.nvmx vector per node: 1 1 Min-Velocity fmaego.data.nvmn scalar per node: 1 1 Min-Velocity-Mag fmaego.data.nvnm scalar per node: 1 1 Max-Velocity-Mag fmaego.data.nvxm scalar per element: 1 1 Material fmaego.data.emat scalar per element: 1 1 Material-State fmaego.data.esta scalar per element: 1 1 Pressure fmaego.data.eprs scalar per element: 1 1 Bulk-Strain fmaego.data.elnv scalar per element: 1 1 Strain-Energy-Density fmaego.data.esed scalar per element: 1 1 Effective-Stress fmaego.data.edev vector per element: 1 1 Stress*Vel fmaego.data.estv tensor symm per element: 1 1 Stress fmaego.data.estr TIME time set: 1 number of steps: 51 time values: 7.583666201834E-05 4.550199721100E-04 9.100399442200E-04 1.365059916330E-03 1.802424622983E-03 2.230961696908E-03 2.659498770833E-03 3.088035844757E-03 3.587995764336E-03 4.016532838261E-03 4.445069912186E-03 4.873606986111E-03 5.302144060035E-03 5.730681133960E-03 6.230641053539E-03 6.659178127464E-03 7.087715201388E-03 7.516252275295E-03 7.944789349220E-03 8.373326423114E-03 8.801863497039E-03 9.301823416617E-03 9.730360490542E-03 1.015889756447E-02 1.058743463839E-02 1.101597171024E-02 1.144450878157E-02 1.194446870107E-02 1.237300577468E-02 1.280154284848E-02 1.323007992229E-02 1.365861699620E-02 1.408715407013E-02 1.458712292673E-02 1.501566000067E-02 1.544419707462E-02 1.587254185280E-02 1.630081112318E-02 1.672905989218E-02 1.722866851498E-02 1.765688637839E-02 1.808507855692E-02 1.851323771922E-02 1.894135782720E-02 1.936943388840E-02 1.986879521384E-02 2.029676314159E-02 2.072467588843E-02 2.115253073291E-02 2.158032510936E-02 2.200805654067E-02 FILE file set: 1 number of steps: 51 From komeil at infovalley.net.my Mon Sep 1 21:04:22 2014 From: komeil at infovalley.net.my (komeil) Date: Tue, 2 Sep 2014 09:04:22 +0800 Subject: [Paraview] Toggling between 2D & 3D view Issue Message-ID: <000a01cfc649$d58ccb00$80a66100$@net.my> Dear friends, here is my implementation for having 2D view along with 3D view: $("#view_3d").bind("mousedown", function(){ if ($(this).hasClass("session_started")) { pv.connection.session.call('vtk:load3DView', null); return false; }else{ $(this).addClass("session_started"); create3DView("#view_3d); pv.connection.session.call('vtk:save3DView', null); } $(UI_AXIAL).bind("mouseup", function(){ pv.connection.session.call('vtk:save3DView', null); }); I have the similar code for 2D. There are 2 viewports created to show loaded volume: pv.viewport_3D = vtkWeb.createViewport({ session: pv.connection.session }); pv.viewport_3D.bind("#view_3d"); and same code for 2D. By clicking on each view, RPC function 'vtk:save3DView' or 'vtk:save2DView' will be called. Each one changes the display properties & render view for representing appropriate view. For example for loading 3D: dp.Representation = 'Volume' view = simple.GetRenderView() view.InteractionMode = '3D' I can expect that it takes time to render the scene when the user clicks on the other view, especially changing from 2D to 3D. But, the issue is by clicking on the other view, the last view is shown before the completion of the rendering. For instance, if the current view is 2D, and user clicks on 3D, immediately, the last 2D scene is displayed in 3D view for a while, before having the rendered 3D view from the server. My question is how to prevent system to show the 2D view in 3D view, and just wait for the server to send rendered 3D scene. Best regards, cid:image007.jpg at 01CE563F.6F03C710 cid:image008.jpg at 01CE563F.6F03C710 cid:image009.jpg at 01CE563F.6F03C710 cid:image010.jpg at 01CE563F.6F03C710 cid:image011.jpg at 01CE563F.6F03C710 Komeil | Software Developer iGeneR Sdn. Bhd. INFOVALLEYR Group of Companies Unit 1.1, Level 1, Block B, MINES Waterfront Business Park No.3, JalanTasik, MINES Resort City 43300 Selangor, Malaysia Tel: +6 03 8941 5830| Fax: +6 03 8941 5970 "This mail (including any attachments) may contain confidential, proprietary or legally privileged information belonging to INFOVALLEY Group of Companies. In case you are not the original intended recipient of the message; you must not directly or indirectly, use, disclose, distribute, print, or copy any part of this message. You are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. We have taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus inadvertently transmitted by this email." -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 1314 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 904 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 1036 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 848 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 925 bytes Desc: not available URL: From komeil at infovalley.net.my Mon Sep 1 21:37:04 2014 From: komeil at infovalley.net.my (komeil) Date: Tue, 2 Sep 2014 09:37:04 +0800 Subject: [Paraview] Toggling between 2D & 3D view Issue Message-ID: <001901cfc64e$66b991e0$342cb5a0$@net.my> Dear friends, here is my implementation for having 2D view along with 3D view for Volume Rendeing: $("#view_3d").bind("mousedown", function(){ if ($(this).hasClass("session_started")) { pv.connection.session.call('vtk:load3DView', null); return false; }else{ $(this).addClass("session_started"); create3DView("#view_3d); pv.connection.session.call('vtk:save3DView', null); } $(UI_AXIAL).bind("mouseup", function(){ pv.connection.session.call('vtk:save3DView', null); }); I have the similar code for 2D. There are 2 viewports created to show loaded volume: pv.viewport_3D = vtkWeb.createViewport({ session: pv.connection.session }); pv.viewport_3D.bind("#view_3d"); and same code for 2D. By clicking on each view, RPC function 'vtk:save3DView' or 'vtk:save2DView' will be called. Each one changes the display properties & render view for representing appropriate view. For example for loading 3D: dp.Representation = 'Volume' view = simple.GetRenderView() view.InteractionMode = '3D' I can expect that it takes time to render the scene when the user clicks on the other view, especially changing from 2D to 3D. But, the issue is by clicking on the other view, the last view is shown before the completion of the rendering. For instance, if the current view is 2D, and user clicks on 3D, immediately, the last 2D scene is displayed in 3D view for a while, before having the rendered 3D view from the server. My question is how to prevent system to show the 2D view in 3D view, and just wait for the server to send rendered 3D scene. Best regards, cid:image007.jpg at 01CE563F.6F03C710 cid:image008.jpg at 01CE563F.6F03C710 cid:image009.jpg at 01CE563F.6F03C710 cid:image010.jpg at 01CE563F.6F03C710 cid:image011.jpg at 01CE563F.6F03C710 Komeil | Software Developer iGeneR Sdn. Bhd. INFOVALLEYR Group of Companies Unit 1.1, Level 1, Block B, MINES Waterfront Business Park No.3, JalanTasik, MINES Resort City 43300 Selangor, Malaysia Tel: +6 03 8941 5830| Fax: +6 03 8941 5970 "This mail (including any attachments) may contain confidential, proprietary or legally privileged information belonging to INFOVALLEY Group of Companies. In case you are not the original intended recipient of the message; you must not directly or indirectly, use, disclose, distribute, print, or copy any part of this message. You are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. We have taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus inadvertently transmitted by this email." -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 1314 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 904 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 1036 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 848 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 925 bytes Desc: not available URL: From sebastien.jourdain at kitware.com Tue Sep 2 10:54:25 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Tue, 2 Sep 2014 08:54:25 -0600 Subject: [Paraview] Toggling between 2D & 3D view Issue In-Reply-To: <001901cfc64e$66b991e0$342cb5a0$@net.my> References: <001901cfc64e$66b991e0$342cb5a0$@net.my> Message-ID: Why don't you use two truly separate view on the server side. That way you won't have any rendering artifact. And you can easily show/hide the local one in the web browser. Then on the client side, you just have to worry about which one is visible. Seb On Mon, Sep 1, 2014 at 7:37 PM, komeil wrote: > Dear friends, > > > > here is my implementation for having 2D view along with 3D view for Volume > Rendeing: > > > > $("#view_3d").bind("mousedown", function(){ > > if ($(this).hasClass("session_started")) > { > > > pv.connection.session.call('vtk:load3DView', null); > > return false; > > }else{ > > $(this).addClass("session_started"); > > > create3DView("#view_3d); > > > pv.connection.session.call('vtk:save3DView', null); > > } > > > > $(UI_AXIAL).bind("mouseup", function(){ > > > pv.connection.session.call('vtk:save3DView', null); > > }); > > > > I have the similar code for 2D. There are 2 viewports created to show > loaded volume: > > > > pv.viewport_3D = vtkWeb.createViewport({ > > session: > pv.connection.session > > }); > > > pv.viewport_3D.bind("#view_3d"); > > > > and same code for 2D. > > > > By clicking on each view, RPC function 'vtk:save3DView' or > 'vtk:save2DView' will be called. Each one changes the display properties & > render view for representing appropriate view. For example for loading 3D: > > > > dp.Representation = 'Volume' > > view = simple.GetRenderView() > > view.InteractionMode = '3D' > > > > I can expect that it takes time to render the scene when the user clicks > on the other view, especially changing from 2D to 3D. > > But, the issue is by clicking on the other view, the last view is shown > before the completion of the rendering. For instance, if the current view > is 2D, and user clicks on 3D, immediately, the last 2D scene is displayed > in 3D view for a while, before having the rendered 3D view from the server. > > > > My question is how to prevent system to show the 2D view in 3D view, and > just wait for the server to send rendered 3D scene. > > > > > > Best regards, > > [image: cid:image007.jpg at 01CE563F.6F03C710] > [image: > cid:image008.jpg at 01CE563F.6F03C710] [image: > cid:image009.jpg at 01CE563F.6F03C710] > [image: > cid:image010.jpg at 01CE563F.6F03C710] [image: > cid:image011.jpg at 01CE563F.6F03C710] > > > > *Komeil* | Software Developer > > iGene? Sdn. Bhd. > > INFOVALLEY? Group of Companies > > Unit 1.1, Level 1, Block B, MINES Waterfront Business Park > > No.3, JalanTasik, MINES Resort City > > 43300 Selangor, Malaysia > > *Tel: *+6 03 8941 5830*| Fax: *+6 03 8941 5970 > > > > ?This mail (including any attachments) may contain confidential, > proprietary or legally privileged information belonging to INFOVALLEY Group > of Companies. In case you are not the original intended recipient of the > message; you must not directly or indirectly, use, disclose, distribute, > print, or copy any part of this message. You are requested to delete it and > inform the sender. Any views expressed in this message are those of the > individual sender unless otherwise stated. We have taken enough precautions > to prevent the spread of viruses. However the company accepts no liability > for any damage caused by any virus inadvertently transmitted by this email." > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 904 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 1036 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 925 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 1314 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 848 bytes Desc: not available URL: From Matthias.Zenker at erbe-med.com Tue Sep 2 11:48:49 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Tue, 2 Sep 2014 15:48:49 +0000 Subject: [Paraview] Point label format in Find Data Message-ID: Hi, returning to ParaView after some time, I have learned that the Selection Inspector of the 3.x series is gone and has been replaced by the Find Data dialog. As before, I can display a label for each selected point showing, its ID, its temperature or whatever. It sometimes has been practical to tweak the format of those labels using C-like format strings in the "Label Format" field in the Selection Inspector. I did not find this field in the Find Data dialog - I would expect it to be in the "Advanced selection display properties" box. Is it somewhere else, or hasn't it been implemented in the new dialog? If so, is this planned, or do I need to post a feature request? Thanks, Matthias _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Sep 2 12:00:02 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 2 Sep 2014 12:00:02 -0400 Subject: [Paraview] Point label format in Find Data In-Reply-To: References: Message-ID: This has indeed been fixed in 4.2-RC1. The advanced properties should now show the label format strings. Utkarsh On Tue, Sep 2, 2014 at 11:48 AM, Zenker, Dr. Matthias wrote: > Hi, > > returning to ParaView after some time, I have learned that the Selection > Inspector of the 3.x series is gone and has been replaced by the Find Data > dialog. As before, I can display a label for each selected point showing, > its ID, its temperature or whatever. It sometimes has been practical to > tweak the format of those labels using C-like format strings in the ?Label > Format? field in the Selection Inspector. I did not find this field in the > Find Data dialog ? I would expect it to be in the ?Advanced selection > display properties? box. Is it somewhere else, or hasn?t it been implemented > in the new dialog? If so, is this planned, or do I need to post a feature > request? > > Thanks, > > Matthias > > > > _____________________________________________________________________ > ERBE Elektromedizin GmbH > Firmensitz: 72072 Tuebingen > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > Registergericht: Stuttgart HRB 380137 > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From furutaka.kazuyoshi at jaea.go.jp Tue Sep 2 22:50:11 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Wed, 03 Sep 2014 11:50:11 +0900 (JST) Subject: [Paraview] seg.fault when reading VRML files twice Message-ID: <20140903.115011.281070362.furutaka.kazuyoshi@jaea.go.jp> Dear ParaView experts... As the subject says, I'm suffering from the segmentation faluts when reading VRML files. It occurs: (i) File->Open a VRML file, display the content, (File->Disconnect) then File->Open a VRML file and display it, (ii) on linux (Fedora 20, binary package: paraview-4.1.0-1.fc20.i686) as well as on windows (Vista Business SP2, "4.1.0 32-bit", ParaView-4.1.0-Windows-32bit.exe, downloaded from http://www.paraview.org/download/ (iii) regardless of whether the second VRML file is the same as or different from the first one, (iV) even with a simple VRML file as the attached one... It DOES NOT occur when loading/displaying multiple VRML files in the same session (w/o disconnecting)... How can I avoid/fix this? I'll attach a trimmed backtrace obtained on linux with gdb... Thanks in advance. Kazuyoshi -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp -------------- next part -------------- A non-text attachment was scrubbed... Name: sample.wrl Type: model/vrml Size: 246 bytes Desc: sample.wrl URL: -------------- next part -------------- Program received signal SIGSEGV, Segmentation fault. yylex (self=self at entry=0x95fce80) at /usr/src/debug/ParaView-v4.1.0/VTK/IO/Import/vtkVRMLImporter.cxx:4696 4696 if ( yy_current_buffer->yy_buffer_status == YY_BUFFER_NEW ) (gdb) where #0 yylex (self=self at entry=0x95fce80) at /usr/src/debug/ParaView-v4.1.0/VTK/IO/Import/vtkVRMLImporter.cxx:4696 #1 0xb42e916a in yyparse (self=self at entry=0x95fce80) at /usr/src/debug/ParaView-v4.1.0/VTK/IO/Import/vtkVRMLImporter.cxx:1118 #2 0xb42e99a3 in vtkVRMLImporter::ImportBegin (this=0x95fce80) at /usr/src/debug/ParaView-v4.1.0/VTK/IO/Import/vtkVRMLImporter.cxx:5307 #3 0xb42e244c in vtkImporter::Read (this=0x95fce80) at /usr/src/debug/ParaView-v4.1.0/VTK/IO/Import/vtkImporter.cxx:79 #4 0xb45ee50d in vtkVRMLSource::InitializeImporter (this=this at entry=0x928c3d0) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/VTKExtensions/Default/vtkVRMLSource.cxx:111 #5 0xb45eeb98 in vtkVRMLSource::RequestData (this=0x928c3d0, outputVector= 0x957d040) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/VTKExtensions/Default/vtkVRMLSource.cxx:94 #6 0xb213caa8 in vtkMultiBlockDataSetAlgorithm::ProcessRequest ( this=0x928c3d0, request=0x9526260, inputVector=0x0, outputVector=0x957d040) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkMultiBlockDataSetAlgorithm.cxx:88 #7 0xb2130df7 in vtkExecutive::CallAlgorithm (this=0xa2b0868, request=0x9526260, direction=1, inInfo=0x0, outInfo=0x957d040) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx:745 #8 0xb212b2be in vtkDemandDrivenPipeline::ExecuteData ( this=this at entry=0xa2b0868, request=request at entry=0x9526260, inInfo=inInfo at entry=0x0, outInfo=outInfo at entry=0x957d040) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:497 #9 0xb2128340 in vtkCompositeDataPipeline::ExecuteData (this=0xa2b0868, request=0x9526260, inInfoVec=0x0, outInfoVec=0x957d040) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:175 #10 0xb212e1b3 in vtkDemandDrivenPipeline::ProcessRequest ( this=this at entry=0xa2b0868, request=request at entry=0x9526260, inInfoVec=inInfoVec at entry=0x0, outInfoVec=outInfoVec at entry=0x957d040) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:279 #11 0xb2143e79 in vtkStreamingDemandDrivenPipeline::ProcessRequest ( this=0xa2b0868, request=request at entry=0x9526260, inInfoVec=0x0, outInfoVec=outInfoVec at entry=0x957d040) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:346 #12 0xb212776e in vtkCompositeDataPipeline::ForwardUpstream (this=0xa401c28, request=0x9526260) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:712 #13 0xb212e144 in vtkDemandDrivenPipeline::ProcessRequest ( this=this at entry=0xa401c28, request=request at entry=0x9526260, inInfoVec=inInfoVec at entry=0x9515bc8, outInfoVec=outInfoVec at entry=0x8eab650) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:265 #14 0xb2143e79 in vtkStreamingDemandDrivenPipeline::ProcessRequest ( this=this at entry=0xa401c28, request=0x9526260, inInfoVec=0x9515bc8, outInfoVec=outInfoVec at entry=0x8eab650) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:346 #15 0xb212cacb in vtkDemandDrivenPipeline::UpdateData (this=0xa401c28, outputPort=0) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:448 #16 0xb2144b4b in vtkStreamingDemandDrivenPipeline::Update (this=0xa401c28, port=0) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:399 #17 0xb489c4a7 in vtkSISourceProxy::UpdatePipeline (this=0x95f1d00, port=0, time=0, doTime=true) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ServerImplementation/Core/vtkSISourceProxy.cxx:420 #18 0xb5078b9e in vtkSISourceProxyCommand (arlu=0x8772778, ob=0x95f1d00, method=, msg=..., resultStream=...) ---Type to continue, or q to quit--- at /usr/src/debug/ParaView-v4.1.0/fedora/Wrapping/ClientServer/vtkSISourceProxyClientServer.cxx:113 #19 0xb40a1fe6 in vtkClientServerInterpreter::CallCommandFunction ( this=this at entry=0x8772778, cname=0xb48b6dd9 "vtkSISourceProxy", ptr=ptr at entry=0x95f1d00, method=method at entry=0xa066675 "UpdatePipeline", msg=..., result=...) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:840 #20 0xb40a23aa in vtkClientServerInterpreter::ProcessCommandInvoke ( this=this at entry=0x8772778, css=..., midx=midx at entry=0) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:437 #21 0xb40a2de7 in vtkClientServerInterpreter::ProcessOneMessage ( this=this at entry=0x8772778, css=..., message=message at entry=0) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:269 #22 0xb40a3030 in vtkClientServerInterpreter::ProcessStream (this=0x8772778, css=...) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:238 #23 0xb486a06f in vtkPVSessionCore::ExecuteStreamInternal (this=0x8772738, stream=..., ignore_errors=false) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:668 #24 0xb4869e46 in vtkPVSessionCore::ExecuteStream (this=0x8772738, location=1, stream=..., ignore_errors=false) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:638 #25 0xb486876a in vtkPVSessionBase::ExecuteStream (this=0x87726f0, location=1, stream=..., ignore_errors=false) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:173 #26 0xb4983787 in vtkSMProxy::ExecuteStream (this=0xa065720, stream=..., ignore_errors=ignore_errors at entry=false, location=1, location at entry=0) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ServerManager/Core/vtkSMProxy.cxx:2262 #27 0xb4971665 in vtkSMOutputPort::UpdatePipelineInternal (this=0xa07fed0, time=0, doTime=true) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ServerManager/Core/vtkSMOutputPort.cxx:211 #28 0xb49718f3 in vtkSMOutputPort::UpdatePipeline (this=0xa07fed0, time=time at entry=0) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ServerManager/Core/vtkSMOutputPort.cxx:183 #29 0xb49c6f12 in vtkSMSourceProxy::UpdatePipeline (this=0xa065720, time=0) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ServerManager/Core/vtkSMSourceProxy.cxx:337 #30 0xb78e0698 in pqPipelineSource::updatePipeline (this=0x9578288) at /usr/src/debug/ParaView-v4.1.0/Qt/Core/pqPipelineSource.cxx:156 #31 0xb789d6ab in pqDisplayPolicy::getPreferredViewType (this=0x85f23a8, opPort=0x8eb4820, update_pipeline=true) at /usr/src/debug/ParaView-v4.1.0/Qt/Core/pqDisplayPolicy.cxx:84 #32 0xb789d0ae in pqDisplayPolicy::getPreferredView (this=0x85f23a8, opPort=0x8eb4820, currentView=0x8e0d3f0) at /usr/src/debug/ParaView-v4.1.0/Qt/Core/pqDisplayPolicy.cxx:165 #33 0xb789cc6c in pqDisplayPolicy::createPreferredRepresentation ( this=0x85f23a8, opPort=0x8eb4820, view=0x8e0d3f0, dont_create_view=dont_create_view at entry=false) at /usr/src/debug/ParaView-v4.1.0/Qt/Core/pqDisplayPolicy.cxx:229 #34 0xb7c6f38d in showData (this=, view=, source=0x9578288) at /usr/src/debug/ParaView-v4.1.0/Qt/Components/pqPropertiesPanel.cxx:188 #35 apply (view=, this=) at /usr/src/debug/ParaView-v4.1.0/Qt/Components/pqPropertiesPanel.cxx:148 #36 pqPropertiesPanel::apply (this=this at entry=0x87201a8) at /usr/src/debug/ParaView-v4.1.0/Qt/Components/pqPropertiesPanel.cxx:686 #37 0xb7d484d0 in pqPropertiesPanel::qt_static_metacall (_o=0x87201a8, _id=3, _a=0xa231c18, _c=) at /usr/src/debug/ParaView-v4.1.0/fedora/Qt/Components/moc_pqPropertiesPanel.cxx:82 ---Type to continue, or q to quit--- #38 0x4d1fe55b in QMetaCallEvent::placeMetaCall (this=0x962a8f0, object=0x87201a8) at kernel/qobject.cpp:524 #39 0x4d20689b in QObject::event (this=0x87201a8, e=0x962a8f0) at kernel/qobject.cpp:1222 #40 0x4d5108b8 in QWidget::event (this=0x87201a8, event=0x962a8f0) at kernel/qwidget.cpp:8859 #41 0x4d4b2b74 in QApplicationPrivate::notify_helper (this=0x8542898, receiver=0x87201a8, e=0x962a8f0) at kernel/qapplication.cpp:4565 #42 0x4d4b9aa9 in QApplication::notify (this=0xbfffe8a8, receiver=0x87201a8, e=0x962a8f0) at kernel/qapplication.cpp:4351 #43 0x4d1ec226 in QCoreApplication::notifyInternal (this=0xbfffe8a8, receiver=receiver at entry=0x87201a8, event=event at entry=0x962a8f0) at kernel/qcoreapplication.cpp:953 #44 0x4d1ef76a in sendEvent (event=0x962a8f0, receiver=0x87201a8) at kernel/qcoreapplication.h:231 #45 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver at entry=0x0, event_type=event_type at entry=0, data=0x8543050) at kernel/qcoreapplication.cpp:1577 #46 0x4d1efc6d in QCoreApplication::sendPostedEvents ( receiver=receiver at entry=0x0, event_type=event_type at entry=0) at kernel/qcoreapplication.cpp:1470 #47 0x4d21e70a in sendPostedEvents () at kernel/qcoreapplication.h:236 #48 postEventSourceDispatch (s=s at entry=0x8555798) at kernel/qeventdispatcher_glib.cpp:300 #49 0x4c4ab556 in g_main_dispatch (context=0x85556c8) at gmain.c:3066 #50 g_main_context_dispatch (context=context at entry=0x85556c8) at gmain.c:3642 #51 0x4c4ab920 in g_main_context_iterate (context=context at entry=0x85556c8, block=block at entry=1, dispatch=dispatch at entry=1, self=) at gmain.c:3713 #52 0x4c4ab9e9 in g_main_context_iteration (context=0x85556c8, may_block=1) at gmain.c:3774 #53 0x4d21dda4 in QEventDispatcherGlib::processEvents (this=this at entry= 0x85555f0, flags=...) at kernel/qeventdispatcher_glib.cpp:450 #54 0x4d56925c in QGuiEventDispatcherGlib::processEvents (this=0x85555f0, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #55 0x4d1eaac0 in QEventLoop::processEvents (this=this at entry=0xbfffe844, flags=...) at kernel/qeventloop.cpp:149 #56 0x4d1eae51 in QEventLoop::exec (this=this at entry=0xbfffe844, flags=...) at kernel/qeventloop.cpp:204 #57 0x4d1f0c7b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #58 0x4d4b0e95 in QApplication::exec () at kernel/qapplication.cpp:3823 #59 0x0804de91 in main (argc=1, argv=0xbfffe974) at /usr/src/debug/ParaView-v4.1.0/fedora/Applications/ParaView/paraview_main.cxx:98 From mail at alexander-stein.eu Wed Sep 3 01:17:13 2014 From: mail at alexander-stein.eu (Alexander Herzog) Date: Wed, 3 Sep 2014 07:17:13 +0200 (CEST) Subject: [Paraview] Problem with "no colormap" Message-ID: <192168710.115876.1409721433281.open-xchange@app10.ox.hosteurope.de> Dear all, i'm using Paraview v4.1 on a Windows 7 PC. When creating data with FEM Software ELMER my Paraview Installation is able to read in and process the data (e.g. "plot over line"). But showing a "Color map" is not possible. The geometry is always displayed in uniform blue and also rescaling (Auto and Manual) cannot make it work. The former Version worked (v3.8). And suprisiling the Input data can be displayed correctly (with rainbow Color map for example) on another Computer (Win7, Paraview v4.1). So: Did anyone had the same issue and could help me? Thanks in advance. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From livia.barazzetti at istb.unibe.ch Wed Sep 3 08:06:42 2014 From: livia.barazzetti at istb.unibe.ch (livia.barazzetti at istb.unibe.ch) Date: Wed, 3 Sep 2014 12:06:42 +0000 Subject: [Paraview] Calling a customized xml plugin from python Message-ID: Hi, I have saved a paraview state in python format. In the pipeline there are a couple of filters coming from an xml plugin (generated in this way http://www.kitware.com/blog/home/post/534 ). When I try to run the the script in the python shell (with the plugin already loaded from the gui menu), I get the error "'module' object has no attribute 'myfilter'" . I have tried also the following commands: >>LoadPlugin("path/to/myfilter.xml",globals()) >>servermanager.myfilter But still I am not able to access it. If it can help, when I load the pipeline from a pvsm file, the filter is correctly loaded. If I select it and call GetActiveSource, I get: What should be the correct command for calling it? Thank you Livia Barazzetti Ph.D. Student - Medical Image Analysis Institute for Surgical Technology and Biomechanics University of Bern Stauffacherstrasse 78 CH-3014 Bern Tel +41 31 631 59 48 http://www.istb.unibe.ch -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Sep 3 08:22:12 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Sep 2014 08:22:12 -0400 Subject: [Paraview] Calling a customized xml plugin from python In-Reply-To: References: Message-ID: I believe you should be accessing it as : >> myfilter() And not servermanager.myfilter. On Wed, Sep 3, 2014 at 8:06 AM, wrote: > Hi, > > > > I have saved a paraview state in python format. In the pipeline there are a > couple of filters coming from an xml plugin (generated in this way > http://www.kitware.com/blog/home/post/534 ). When I try to run the the > script in the python shell (with the plugin already loaded from the gui > menu), I get the error ?'module' object has no attribute 'myfilter'? . > > I have tried also the following commands: > > > >>>LoadPlugin(?path/to/myfilter.xml?,globals()) > >>>servermanager.myfilter > > But still I am not able to access it. > > If it can help, when I load the pipeline from a pvsm file, the filter is > correctly loaded. > > If I select it and call GetActiveSource, I get: myfilter object at 0x0000000015B40A20> > > > > What should be the correct command for calling it? > > Thank you > > > > Livia Barazzetti > Ph.D. Student - Medical Image Analysis > Institute for Surgical Technology and Biomechanics > University of Bern > Stauffacherstrasse 78 > CH-3014 Bern > Tel +41 31 631 59 48 > http://www.istb.unibe.ch > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Sep 3 08:24:37 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Sep 2014 08:24:37 -0400 Subject: [Paraview] Problem with "no colormap" In-Reply-To: <192168710.115876.1409721433281.open-xchange@app10.ox.hosteurope.de> References: <192168710.115876.1409721433281.open-xchange@app10.ox.hosteurope.de> Message-ID: Never heard of this before. But try toggling the "Interpolate scalar before mapping" checkbox on the Properties panel. Any difference? You may also want to try the latest 4.2-RC1 binaries, just in case. Utkarsh On Wed, Sep 3, 2014 at 1:17 AM, Alexander Herzog wrote: > Dear all, > i'm using Paraview v4.1 on a Windows 7 PC. > When creating data with FEM Software ELMER my Paraview Installation is able > to read in and process the data (e.g. "plot over line"). > But showing a "Color map" is not possible. The geometry is always displayed > in uniform blue and also rescaling (Auto and Manual) cannot make it work. > The former Version worked (v3.8). And suprisiling the Input data can be > displayed correctly (with rainbow Color map for example) on another Computer > (Win7, Paraview v4.1). > > So: Did anyone had the same issue and could help me? > > Thanks in advance. > > Alex > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From reuterma at ornl.gov Wed Sep 3 09:42:52 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Wed, 3 Sep 2014 13:42:52 +0000 Subject: [Paraview] Superbuild and OSX Message-ID: Hi, I?m having trouble getting the git-master version of the Superbuild running on OSX (10.9) with clang (5.1). Setting the CMAKE_OSX_SYSROOT variable causes the following error during CMake (2.8.12.2) generation for the ParaView subproject: -- The C compiler identification is unknown -- The CXX compiler identification is unknown -- Check for working C compiler using: Ninja -- Check for working C compiler using: Ninja -- broken CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): The C compiler "/usr/bin/cc" is not able to compile a simple test program. It fails with the following output: Change Dir: /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075 [1/2] Building C object CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o FAILED: /usr/bin/cc -fPIC -arch x86_64 -mmacosx-version-min=10.9 -sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk -o CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o -c testCCompiler.c clang: error: unknown argument: '-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' [-Wunused-command-line-argument-hard-error-in-future] clang: note: this will be a hard error (cannot be downgraded to a warning) in the future ninja: build stopped: subcommand failed. Even if I empty the CMAKE_OSX_SYSROOT variable, the system still tries to pass an empty -sysroot flag to clang causing it to choke. I removed the sysroot flag from the top-level CMakeLists.txt, but then the ParaView CMake setup fails for a reason I can?t seem to understand. I?m attaching the log showing the CMake output. The only obvious thing I see is the Fortran compiler. Is that required? Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov -------------- next part -------------- A non-text attachment was scrubbed... Name: PVSuperbuild-OSX-issue.rtf Type: text/rtf Size: 59197 bytes Desc: PVSuperbuild-OSX-issue.rtf URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From Matthias.Zenker at erbe-med.com Wed Sep 3 09:57:20 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Wed, 3 Sep 2014 13:57:20 +0000 Subject: [Paraview] Point label format in Find Data In-Reply-To: References: Message-ID: OK, thanks for the info. Matthias > -----Urspr?ngliche Nachricht----- > Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Gesendet: Dienstag, 2. September 2014 18:00 > An: Zenker, Dr. Matthias > Cc: paraview at paraview.org > Betreff: Re: [Paraview] Point label format in Find Data > > This has indeed been fixed in 4.2-RC1. The advanced properties should > now show the label format strings. > > Utkarsh > > On Tue, Sep 2, 2014 at 11:48 AM, Zenker, Dr. Matthias > wrote: > > Hi, > > > > returning to ParaView after some time, I have learned that the Selection > > Inspector of the 3.x series is gone and has been replaced by the Find Data > > dialog. As before, I can display a label for each selected point showing, > > its ID, its temperature or whatever. It sometimes has been practical to > > tweak the format of those labels using C-like format strings in the ?Label > > Format? field in the Selection Inspector. I did not find this field in the > > Find Data dialog ? I would expect it to be in the ?Advanced selection > > display properties? box. Is it somewhere else, or hasn?t it been > implemented > > in the new dialog? If so, is this planned, or do I need to post a feature > > request? > > > > Thanks, > > > > Matthias > > > > > > > > > __________________________________________________________ > ___________ > > ERBE Elektromedizin GmbH > > Firmensitz: 72072 Tuebingen > > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > > Registergericht: Stuttgart HRB 380137 > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 From reuterma at ornl.gov Wed Sep 3 10:07:48 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Wed, 3 Sep 2014 14:07:48 +0000 Subject: [Paraview] Superbuild and Windows Message-ID: Hi, I'm having an issue with the ParaView Superbuild on Windows (VS2012). I get this error during the build process: 322> Compiling Python package 'pygments' 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\filters ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\formatters ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\lexers ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\styles ... 322> ImportError: No module named site 9>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): error MSB6006: "cmd.exe" exited with code 1. [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] 322> 322>Build FAILED. However, the site module exists when I run python. I'm building from a script so I can control the environment. Everything else seems to build just fine. However, nothing appears in the install directory for cpack to find. I can't tell if this build error is disrupting the process or something else is going wrong. What controls the pygments build so I can shut it off for now? Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From livia.barazzetti at istb.unibe.ch Wed Sep 3 10:13:14 2014 From: livia.barazzetti at istb.unibe.ch (livia.barazzetti at istb.unibe.ch) Date: Wed, 3 Sep 2014 14:13:14 +0000 Subject: [Paraview] Calling a customized xml plugin from python In-Reply-To: References: Message-ID: Thank you for the quick response! I've tried with other plugins (very simple ones which expose vtkfilters), and it worked. I was able to make myfilter() work by restarting the python shell after loading it (and sometimes also loading it via the LoadPlugin() command). The strange thing is that if there is some error while running script (for example, reading empty arrays), then myfile() is not recognized anymore, unless I restart the python interpreter (not necessarily paraview), but I was not really able to isolate the issue (I am just restarting the shell to make it work) Thank you -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: 03 September 2014 14:22 To: Barazzetti, Livia (ISTB) Cc: ParaView Subject: Re: [Paraview] Calling a customized xml plugin from python I believe you should be accessing it as : >> myfilter() And not servermanager.myfilter. On Wed, Sep 3, 2014 at 8:06 AM, wrote: > Hi, > > > > I have saved a paraview state in python format. In the pipeline there > are a couple of filters coming from an xml plugin (generated in this > way > http://www.kitware.com/blog/home/post/534 ). When I try to run the the > script in the python shell (with the plugin already loaded from the > gui menu), I get the error ?'module' object has no attribute 'myfilter'? . > > I have tried also the following commands: > > > >>>LoadPlugin(?path/to/myfilter.xml?,globals()) > >>>servermanager.myfilter > > But still I am not able to access it. > > If it can help, when I load the pipeline from a pvsm file, the filter > is correctly loaded. > > If I select it and call GetActiveSource, I get: myfilter object at 0x0000000015B40A20> > > > > What should be the correct command for calling it? > > Thank you > > > > Livia Barazzetti > Ph.D. Student - Medical Image Analysis Institute for Surgical > Technology and Biomechanics University of Bern Stauffacherstrasse 78 > CH-3014 Bern > Tel +41 31 631 59 48 > http://www.istb.unibe.ch > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Sep 3 10:24:57 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Sep 2014 10:24:57 -0400 Subject: [Paraview] Superbuild and Windows In-Reply-To: References: Message-ID: Michael, Are you using VS generator? Can you switch to using Ninja? You can still use the MSVC compilers. The error is popping up when the build is trying to compiler the pygments *.py files. You'll get the same error later when it's trying to compile the ParaView *.py files. Also, another thing to note is that Windows has issues with long paths. So I'd suggest moving the superbuild source and build directories to something lower to avoid those e.g. C:/tmp/pvs-src and C:/tmp/pvs-build. Finally, if you're using VS2012, you'll need to use a system Python. Currently. the Python included in the superbuild is intended for VS2008. Also VS2012, is currently untested. As a first pass, if possible, I'd suggest using VS 2008. Once that's working, you can give VS2012 try. Hopefully, it should work (except the Python caveat), but I am always wary of VS version differences. Utkarsh On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. wrote: > Hi, > > > > I?m having an issue with the ParaView Superbuild on Windows > (VS2012). I get this error during the build process: > > > > 322> Compiling Python package 'pygments' > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\filters > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\formatters > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\lexers > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\styles > ... > > > > 322> ImportError: No module named site > > > > 9>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): > error MSB6006: "cmd.exe" exited with code 1. > [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] > > > > 322> > > 322>Build FAILED. > > > > However, the site module exists when I run python. I?m building from a > script so I can control the environment. Everything else seems to build just > fine. However, nothing appears in the install directory for cpack to find. I > can?t tell if this build error is disrupting the process or something else > is going wrong. What controls the pygments build so I can shut it off for > now? > > > > Thanks, > > M > > > > Dr. Michael Reuter > > Scientific Data Analysis Group > > Neutron Data Analysis and Visualization Division > > Oak Ridge National Laboratory > > > > Office: 1-865-241-7216 > > Fax: 1-865-574-6080 > > Email: reuterma at ornl.gov > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Sep 3 10:28:18 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Sep 2014 10:28:18 -0400 Subject: [Paraview] Superbuild and OSX In-Reply-To: References: Message-ID: Cherry-pick this fix for now : http://review.source.kitware.com/#/c/16665/ It'll go into master soon. Ben, anything this fix is waiting on? Utkarsh On Wed, Sep 3, 2014 at 9:42 AM, Reuter, Michael A. wrote: > Hi, > > I?m having trouble getting the git-master version of the Superbuild running on OSX (10.9) with clang (5.1). Setting the CMAKE_OSX_SYSROOT variable causes the following error during CMake (2.8.12.2) generation for the ParaView subproject: > > -- The C compiler identification is unknown > -- The CXX compiler identification is unknown > -- Check for working C compiler using: Ninja > -- Check for working C compiler using: Ninja -- broken > CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): > The C compiler "/usr/bin/cc" is not able to compile a simple test program. > > It fails with the following output: > > Change Dir: /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp > > Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075 > > [1/2] Building C object > CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o > > FAILED: /usr/bin/cc -fPIC -arch x86_64 -mmacosx-version-min=10.9 > -sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk > -o CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o -c > testCCompiler.c > > clang: error: unknown argument: > '-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' > [-Wunused-command-line-argument-hard-error-in-future] > > clang: note: this will be a hard error (cannot be downgraded to a warning) > in the future > > ninja: build stopped: subcommand failed. > > Even if I empty the CMAKE_OSX_SYSROOT variable, the system still tries to pass an empty -sysroot flag to clang causing it to choke. I removed the sysroot flag from the top-level CMakeLists.txt, but then the ParaView CMake setup fails for a reason I can?t seem to understand. I?m attaching the log showing the CMake output. The only obvious thing I see is the Fortran compiler. Is that required? > > Thanks, > M > > Dr. Michael Reuter > Scientific Data Analysis Group > Neutron Data Analysis and Visualization Division > Oak Ridge National Laboratory > > Office: 1-865-241-7216 > Fax: 1-865-574-6080 > Email: reuterma at ornl.gov > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From simon.m.su.ctr at mail.mil Wed Sep 3 10:41:54 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 3 Sep 2014 14:41:54 +0000 Subject: [Paraview] Superbuild and Windows (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Utkarsh, Is Ninja also preferred if I am using VS2008 to build the superbuild on Windows? Is this the Ninja - http://martine.github.io/ninja/manual.html ? Thanks -simon -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit Sent: Wednesday, September 03, 2014 10:25 AM To: Reuter, Michael A. Cc: paraview at paraview.org Subject: Re: [Paraview] Superbuild and Windows Michael, Are you using VS generator? Can you switch to using Ninja? You can still use the MSVC compilers. The error is popping up when the build is trying to compiler the pygments *.py files. You'll get the same error later when it's trying to compile the ParaView *.py files. Also, another thing to note is that Windows has issues with long paths. So I'd suggest moving the superbuild source and build directories to something lower to avoid those e.g. C:/tmp/pvs-src and C:/tmp/pvs-build. Finally, if you're using VS2012, you'll need to use a system Python. Currently. the Python included in the superbuild is intended for VS2008. Also VS2012, is currently untested. As a first pass, if possible, I'd suggest using VS 2008. Once that's working, you can give VS2012 try. Hopefully, it should work (except the Python caveat), but I am always wary of VS version differences. Utkarsh On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. wrote: > Hi, > > > > I?m having an issue with the ParaView Superbuild on > Windows (VS2012). I get this error during the build process: > > > > 322> Compiling Python package 'pygments' > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib > /site-packages/pygments > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib > /site-packages/pygments\filters > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib > /site-packages/pygments\formatters > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib > /site-packages/pygments\lexers > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib > /site-packages/pygments\styles > ... > > > > 322> ImportError: No module named site > > > > 9>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): > error MSB6006: "cmd.exe" exited with code 1. > [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] > > > > 322> > > 322>Build FAILED. > > > > However, the site module exists when I run python. I?m building from a > script so I can control the environment. Everything else seems to > build just fine. However, nothing appears in the install directory for > cpack to find. I can?t tell if this build error is disrupting the > process or something else is going wrong. What controls the pygments > build so I can shut it off for now? > > > > Thanks, > > M > > > > Dr. Michael Reuter > > Scientific Data Analysis Group > > Neutron Data Analysis and Visualization Division > > Oak Ridge National Laboratory > > > > Office: 1-865-241-7216 > > Fax: 1-865-574-6080 > > Email: reuterma at ornl.gov > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Wed Sep 3 10:48:15 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Sep 2014 10:48:15 -0400 Subject: [Paraview] Superbuild and Windows (UNCLASSIFIED) In-Reply-To: References: Message-ID: Yes, Ninja is indeed the preferred and the only tested generators for ParaView's Windows superbuild for all VS variants. Yes, that's indeed the Ninja. When using CMake, you just need to pick the Ninja generator. For all intents and purposes it;s like nmake. So you'll need to run CMake through the visual studio command prompt (also the builds need to be triggered throught the command prompt) otherwise you'll get compiler not working errors. Utkarsh On Wed, Sep 3, 2014 at 10:41 AM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Utkarsh, > > Is Ninja also preferred if I am using VS2008 to build the superbuild on Windows? > > Is this the Ninja - http://martine.github.io/ninja/manual.html ? > > Thanks > -simon > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit > Sent: Wednesday, September 03, 2014 10:25 AM > To: Reuter, Michael A. > Cc: paraview at paraview.org > Subject: Re: [Paraview] Superbuild and Windows > > Michael, > > Are you using VS generator? Can you switch to using Ninja? You can still use the MSVC compilers. The error is popping up when the build is trying to compiler the pygments *.py files. You'll get the same error later when it's trying to compile the ParaView *.py files. > > Also, another thing to note is that Windows has issues with long paths. So I'd suggest moving the superbuild source and build directories to something lower to avoid those e.g. C:/tmp/pvs-src and C:/tmp/pvs-build. > > Finally, if you're using VS2012, you'll need to use a system Python. > Currently. the Python included in the superbuild is intended for VS2008. Also VS2012, is currently untested. As a first pass, if possible, I'd suggest using VS 2008. Once that's working, you can give > VS2012 try. Hopefully, it should work (except the Python caveat), but I am always wary of VS version differences. > > Utkarsh > > > > On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. wrote: >> Hi, >> >> >> >> I?m having an issue with the ParaView Superbuild on >> Windows (VS2012). I get this error during the build process: >> >> >> >> 322> Compiling Python package 'pygments' >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib >> /site-packages/pygments >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib >> /site-packages/pygments\filters >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib >> /site-packages/pygments\formatters >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib >> /site-packages/pygments\lexers >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib >> /site-packages/pygments\styles >> ... >> >> >> >> 322> ImportError: No module named site >> >> >> >> 9>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): >> error MSB6006: "cmd.exe" exited with code 1. >> [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] >> >> >> >> 322> >> >> 322>Build FAILED. >> >> >> >> However, the site module exists when I run python. I?m building from a >> script so I can control the environment. Everything else seems to >> build just fine. However, nothing appears in the install directory for >> cpack to find. I can?t tell if this build error is disrupting the >> process or something else is going wrong. What controls the pygments >> build so I can shut it off for now? >> >> >> >> Thanks, >> >> M >> >> >> >> Dr. Michael Reuter >> >> Scientific Data Analysis Group >> >> Neutron Data Analysis and Visualization Division >> >> Oak Ridge National Laboratory >> >> >> >> Office: 1-865-241-7216 >> >> Fax: 1-865-574-6080 >> >> Email: reuterma at ornl.gov >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > Classification: UNCLASSIFIED > Caveats: NONE > > From brockp at umich.edu Wed Sep 3 10:50:52 2014 From: brockp at umich.edu (Brock Palen) Date: Wed, 3 Sep 2014 10:50:52 -0400 Subject: [Paraview] save cmake config Message-ID: <9390E29D-0392-4D5E-BEE6-C55EA03E45FB@umich.edu> If I wanted to save the Cmake config for a super build to rebuild it later (assume same version of paraview) what file[s] would I save and how would I tell ccmake to read them in? Thanks! Brock Palen www.umich.edu/~brockp CAEN Advanced Computing XSEDE Campus Champion brockp at umich.edu (734)936-1985 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: Message signed with OpenPGP using GPGMail URL: From simon.m.su.ctr at mail.mil Wed Sep 3 10:51:19 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 3 Sep 2014 14:51:19 +0000 Subject: [Paraview] Superbuild and Windows (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Thanks Utkarsh -simon -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Wednesday, September 03, 2014 10:48 AM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] Superbuild and Windows (UNCLASSIFIED) Yes, Ninja is indeed the preferred and the only tested generators for ParaView's Windows superbuild for all VS variants. Yes, that's indeed the Ninja. When using CMake, you just need to pick the Ninja generator. For all intents and purposes it;s like nmake. So you'll need to run CMake through the visual studio command prompt (also the builds need to be triggered throught the command prompt) otherwise you'll get compiler not working errors. Utkarsh On Wed, Sep 3, 2014 at 10:41 AM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Utkarsh, > > Is Ninja also preferred if I am using VS2008 to build the superbuild on Windows? > > Is this the Ninja - http://martine.github.io/ninja/manual.html ? > > Thanks > -simon > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of > Utkarsh Ayachit > Sent: Wednesday, September 03, 2014 10:25 AM > To: Reuter, Michael A. > Cc: paraview at paraview.org > Subject: Re: [Paraview] Superbuild and Windows > > Michael, > > Are you using VS generator? Can you switch to using Ninja? You can still use the MSVC compilers. The error is popping up when the build is trying to compiler the pygments *.py files. You'll get the same error later when it's trying to compile the ParaView *.py files. > > Also, another thing to note is that Windows has issues with long paths. So I'd suggest moving the superbuild source and build directories to something lower to avoid those e.g. C:/tmp/pvs-src and C:/tmp/pvs-build. > > Finally, if you're using VS2012, you'll need to use a system Python. > Currently. the Python included in the superbuild is intended for > VS2008. Also VS2012, is currently untested. As a first pass, if > possible, I'd suggest using VS 2008. Once that's working, you can give > VS2012 try. Hopefully, it should work (except the Python caveat), but I am always wary of VS version differences. > > Utkarsh > > > > On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. wrote: >> Hi, >> >> >> >> I?m having an issue with the ParaView Superbuild on >> Windows (VS2012). I get this error during the build process: >> >> >> >> 322> Compiling Python package 'pygments' >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/li >> b >> /site-packages/pygments >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/li >> b >> /site-packages/pygments\filters >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/li >> b >> /site-packages/pygments\formatters >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/li >> b >> /site-packages/pygments\lexers >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/li >> b >> /site-packages/pygments\styles >> ... >> >> >> >> 322> ImportError: No module named site >> >> >> >> 9>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): >> error MSB6006: "cmd.exe" exited with code 1. >> [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] >> >> >> >> 322> >> >> 322>Build FAILED. >> >> >> >> However, the site module exists when I run python. I?m building from >> a script so I can control the environment. Everything else seems to >> build just fine. However, nothing appears in the install directory >> for cpack to find. I can?t tell if this build error is disrupting the >> process or something else is going wrong. What controls the pygments >> build so I can shut it off for now? >> >> >> >> Thanks, >> >> M >> >> >> >> Dr. Michael Reuter >> >> Scientific Data Analysis Group >> >> Neutron Data Analysis and Visualization Division >> >> Oak Ridge National Laboratory >> >> >> >> Office: 1-865-241-7216 >> >> Fax: 1-865-574-6080 >> >> Email: reuterma at ornl.gov >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > Classification: UNCLASSIFIED > Caveats: NONE > > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Wed Sep 3 10:55:59 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Sep 2014 10:55:59 -0400 Subject: [Paraview] save cmake config In-Reply-To: <9390E29D-0392-4D5E-BEE6-C55EA03E45FB@umich.edu> References: <9390E29D-0392-4D5E-BEE6-C55EA03E45FB@umich.edu> Message-ID: CMakeCache.txt from the top-level build directory would be the thing to save. Next time, just copy this file into an empty build directory and the run cmake. On Wed, Sep 3, 2014 at 10:50 AM, Brock Palen wrote: > If I wanted to save the Cmake config for a super build to rebuild it later (assume same version of paraview) what file[s] would I save and how would I tell ccmake to read them in? > > Thanks! > > Brock Palen > www.umich.edu/~brockp > CAEN Advanced Computing > XSEDE Campus Champion > brockp at umich.edu > (734)936-1985 > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Sep 3 10:57:34 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Sep 2014 10:57:34 -0400 Subject: [Paraview] save cmake config In-Reply-To: References: <9390E29D-0392-4D5E-BEE6-C55EA03E45FB@umich.edu> Message-ID: The best option, however is to edit this file to only leave those options that you manually set to keep it easier to read and better handle changes in environment. On Wed, Sep 3, 2014 at 10:55 AM, Utkarsh Ayachit wrote: > CMakeCache.txt from the top-level build directory would be the thing > to save. Next time, just copy this file into an empty build directory > and the run cmake. > > On Wed, Sep 3, 2014 at 10:50 AM, Brock Palen wrote: >> If I wanted to save the Cmake config for a super build to rebuild it later (assume same version of paraview) what file[s] would I save and how would I tell ccmake to read them in? >> >> Thanks! >> >> Brock Palen >> www.umich.edu/~brockp >> CAEN Advanced Computing >> XSEDE Campus Champion >> brockp at umich.edu >> (734)936-1985 >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From utkarsh.ayachit at kitware.com Wed Sep 3 11:24:55 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Sep 2014 11:24:55 -0400 Subject: [Paraview] Calling a customized xml plugin from python In-Reply-To: References: Message-ID: Oh, I think I error is this: LoadPlugin(.., ns=globals()) The namespace is the 3rd argument for LoadPlugin[1], not second. So either use the proper location, or use the keyword argument. [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/paraview.simple.html#paraview.simple.LoadPlugin On Wed, Sep 3, 2014 at 10:13 AM, wrote: > Thank you for the quick response! > I've tried with other plugins (very simple ones which expose vtkfilters), and it worked. > I was able to make myfilter() work by restarting the python shell after loading it (and sometimes also loading it via the LoadPlugin() command). The strange thing is that if there is some error while running script (for example, reading empty arrays), then myfile() is not recognized anymore, unless I restart the python interpreter (not necessarily paraview), but I was not really able to isolate the issue (I am just restarting the shell to make it work) > Thank you > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: 03 September 2014 14:22 > To: Barazzetti, Livia (ISTB) > Cc: ParaView > Subject: Re: [Paraview] Calling a customized xml plugin from python > > I believe you should be accessing it as : > >> myfilter() > > And not servermanager.myfilter. > > On Wed, Sep 3, 2014 at 8:06 AM, wrote: >> Hi, >> >> >> >> I have saved a paraview state in python format. In the pipeline there >> are a couple of filters coming from an xml plugin (generated in this >> way >> http://www.kitware.com/blog/home/post/534 ). When I try to run the the >> script in the python shell (with the plugin already loaded from the >> gui menu), I get the error ?'module' object has no attribute 'myfilter'? . >> >> I have tried also the following commands: >> >> >> >>>>LoadPlugin(?path/to/myfilter.xml?,globals()) >> >>>>servermanager.myfilter >> >> But still I am not able to access it. >> >> If it can help, when I load the pipeline from a pvsm file, the filter >> is correctly loaded. >> >> If I select it and call GetActiveSource, I get: > myfilter object at 0x0000000015B40A20> >> >> >> >> What should be the correct command for calling it? >> >> Thank you >> >> >> >> Livia Barazzetti >> Ph.D. Student - Medical Image Analysis Institute for Surgical >> Technology and Biomechanics University of Bern Stauffacherstrasse 78 >> CH-3014 Bern >> Tel +41 31 631 59 48 >> http://www.istb.unibe.ch >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From reuterma at ornl.gov Wed Sep 3 14:40:45 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Wed, 3 Sep 2014 18:40:45 +0000 Subject: [Paraview] Superbuild and OSX In-Reply-To: References: Message-ID: This gets around the clang argument problem, but the ParaView CMake configuration step still fails for an unknown reason. M On Sep 3, 2014, at 10:28 AM, Utkarsh Ayachit > wrote: Cherry-pick this fix for now : http://review.source.kitware.com/#/c/16665/ It'll go into master soon. Ben, anything this fix is waiting on? Utkarsh On Wed, Sep 3, 2014 at 9:42 AM, Reuter, Michael A. > wrote: Hi, I?m having trouble getting the git-master version of the Superbuild running on OSX (10.9) with clang (5.1). Setting the CMAKE_OSX_SYSROOT variable causes the following error during CMake (2.8.12.2) generation for the ParaView subproject: -- The C compiler identification is unknown -- The CXX compiler identification is unknown -- Check for working C compiler using: Ninja -- Check for working C compiler using: Ninja -- broken CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): The C compiler "/usr/bin/cc" is not able to compile a simple test program. It fails with the following output: Change Dir: /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075 [1/2] Building C object CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o FAILED: /usr/bin/cc -fPIC -arch x86_64 -mmacosx-version-min=10.9 -sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk -o CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o -c testCCompiler.c clang: error: unknown argument: '-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' [-Wunused-command-line-argument-hard-error-in-future] clang: note: this will be a hard error (cannot be downgraded to a warning) in the future ninja: build stopped: subcommand failed. Even if I empty the CMAKE_OSX_SYSROOT variable, the system still tries to pass an empty -sysroot flag to clang causing it to choke. I removed the sysroot flag from the top-level CMakeLists.txt, but then the ParaView CMake setup fails for a reason I can?t seem to understand. I?m attaching the log showing the CMake output. The only obvious thing I see is the Fortran compiler. Is that required? Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Wed Sep 3 18:23:50 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Sep 2014 18:23:50 -0400 Subject: [Paraview] Superbuild and OSX In-Reply-To: References: Message-ID: Michael, Let me try this on a Moutain Lion myself and I'll let you know. What projects are you turning on in your build? Utkarsh On Wed, Sep 3, 2014 at 2:40 PM, Reuter, Michael A. wrote: > This gets around the clang argument problem, but the ParaView CMake configuration step still fails for an unknown reason. > > M > > On Sep 3, 2014, at 10:28 AM, Utkarsh Ayachit > wrote: > > Cherry-pick this fix for now : http://review.source.kitware.com/#/c/16665/ > It'll go into master soon. > > Ben, anything this fix is waiting on? > > Utkarsh > > On Wed, Sep 3, 2014 at 9:42 AM, Reuter, Michael A. > wrote: > Hi, > > I?m having trouble getting the git-master version of the Superbuild running on OSX (10.9) with clang (5.1). Setting the CMAKE_OSX_SYSROOT variable causes the following error during CMake (2.8.12.2) generation for the ParaView subproject: > > -- The C compiler identification is unknown > -- The CXX compiler identification is unknown > -- Check for working C compiler using: Ninja > -- Check for working C compiler using: Ninja -- broken > CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): > The C compiler "/usr/bin/cc" is not able to compile a simple test program. > > It fails with the following output: > > Change Dir: /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp > > Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075 > > [1/2] Building C object > CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o > > FAILED: /usr/bin/cc -fPIC -arch x86_64 -mmacosx-version-min=10.9 > -sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk > -o CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o -c > testCCompiler.c > > clang: error: unknown argument: > '-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' > [-Wunused-command-line-argument-hard-error-in-future] > > clang: note: this will be a hard error (cannot be downgraded to a warning) > in the future > > ninja: build stopped: subcommand failed. > > Even if I empty the CMAKE_OSX_SYSROOT variable, the system still tries to pass an empty -sysroot flag to clang causing it to choke. I removed the sysroot flag from the top-level CMakeLists.txt, but then the ParaView CMake setup fails for a reason I can?t seem to understand. I?m attaching the log showing the CMake output. The only obvious thing I see is the Fortran compiler. Is that required? > > Thanks, > M > > Dr. Michael Reuter > Scientific Data Analysis Group > Neutron Data Analysis and Visualization Division > Oak Ridge National Laboratory > > Office: 1-865-241-7216 > Fax: 1-865-574-6080 > Email: reuterma at ornl.gov > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From rcrocker at uvm.edu Wed Sep 3 19:10:45 2014 From: rcrocker at uvm.edu (Ryan Crocker) Date: Wed, 3 Sep 2014 16:10:45 -0700 Subject: [Paraview] number fields Message-ID: <4733FE02-28F3-4D93-B769-E53A3D9F68E4@uvm.edu> I'm using the Paraview 4 64 bit on os x 10.6. Every now and then i can not write in the number fields unless i re-load the state. This has always been a problem but it is more noticeable now that i'm doing a lot more post processing. Why does Paraview do that and is there a way to fix it? Ryan Crocker University of Vermont, School of Engineering Mechanical Engineering Department rcrocker at uvm.edu 315-212-7331 From utkarsh.ayachit at kitware.com Wed Sep 3 23:57:58 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Sep 2014 23:57:58 -0400 Subject: [Paraview] Superbuild and OSX In-Reply-To: References: Message-ID: Michael, Hold off on using the superbuild on MountainLion for now. I'll track the issues down and then let you know. Utkarsh On Wed, Sep 3, 2014 at 6:23 PM, Utkarsh Ayachit wrote: > Michael, > > Let me try this on a Moutain Lion myself and I'll let you know. What > projects are you turning on in your build? > > Utkarsh > > On Wed, Sep 3, 2014 at 2:40 PM, Reuter, Michael A. wrote: >> This gets around the clang argument problem, but the ParaView CMake configuration step still fails for an unknown reason. >> >> M >> >> On Sep 3, 2014, at 10:28 AM, Utkarsh Ayachit > wrote: >> >> Cherry-pick this fix for now : http://review.source.kitware.com/#/c/16665/ >> It'll go into master soon. >> >> Ben, anything this fix is waiting on? >> >> Utkarsh >> >> On Wed, Sep 3, 2014 at 9:42 AM, Reuter, Michael A. > wrote: >> Hi, >> >> I?m having trouble getting the git-master version of the Superbuild running on OSX (10.9) with clang (5.1). Setting the CMAKE_OSX_SYSROOT variable causes the following error during CMake (2.8.12.2) generation for the ParaView subproject: >> >> -- The C compiler identification is unknown >> -- The CXX compiler identification is unknown >> -- Check for working C compiler using: Ninja >> -- Check for working C compiler using: Ninja -- broken >> CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): >> The C compiler "/usr/bin/cc" is not able to compile a simple test program. >> >> It fails with the following output: >> >> Change Dir: /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp >> >> Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075 >> >> [1/2] Building C object >> CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o >> >> FAILED: /usr/bin/cc -fPIC -arch x86_64 -mmacosx-version-min=10.9 >> -sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk >> -o CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o -c >> testCCompiler.c >> >> clang: error: unknown argument: >> '-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' >> [-Wunused-command-line-argument-hard-error-in-future] >> >> clang: note: this will be a hard error (cannot be downgraded to a warning) >> in the future >> >> ninja: build stopped: subcommand failed. >> >> Even if I empty the CMAKE_OSX_SYSROOT variable, the system still tries to pass an empty -sysroot flag to clang causing it to choke. I removed the sysroot flag from the top-level CMakeLists.txt, but then the ParaView CMake setup fails for a reason I can?t seem to understand. I?m attaching the log showing the CMake output. The only obvious thing I see is the Fortran compiler. Is that required? >> >> Thanks, >> M >> >> Dr. Michael Reuter >> Scientific Data Analysis Group >> Neutron Data Analysis and Visualization Division >> Oak Ridge National Laboratory >> >> Office: 1-865-241-7216 >> Fax: 1-865-574-6080 >> Email: reuterma at ornl.gov >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From reuterma at ornl.gov Thu Sep 4 08:00:03 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Thu, 4 Sep 2014 12:00:03 +0000 Subject: [Paraview] Superbuild and OSX In-Reply-To: References: Message-ID: Thanks for the update. I?m actually building on Mavericks, but our project is still supporting Mountain Lion so it will be good to have it work there. M On Sep 3, 2014, at 11:57 PM, Utkarsh Ayachit > wrote: Michael, Hold off on using the superbuild on MountainLion for now. I'll track the issues down and then let you know. Utkarsh On Wed, Sep 3, 2014 at 6:23 PM, Utkarsh Ayachit > wrote: Michael, Let me try this on a Moutain Lion myself and I'll let you know. What projects are you turning on in your build? Utkarsh On Wed, Sep 3, 2014 at 2:40 PM, Reuter, Michael A. > wrote: This gets around the clang argument problem, but the ParaView CMake configuration step still fails for an unknown reason. M On Sep 3, 2014, at 10:28 AM, Utkarsh Ayachit > wrote: Cherry-pick this fix for now : http://review.source.kitware.com/#/c/16665/ It'll go into master soon. Ben, anything this fix is waiting on? Utkarsh On Wed, Sep 3, 2014 at 9:42 AM, Reuter, Michael A. > wrote: Hi, I?m having trouble getting the git-master version of the Superbuild running on OSX (10.9) with clang (5.1). Setting the CMAKE_OSX_SYSROOT variable causes the following error during CMake (2.8.12.2) generation for the ParaView subproject: -- The C compiler identification is unknown -- The CXX compiler identification is unknown -- Check for working C compiler using: Ninja -- Check for working C compiler using: Ninja -- broken CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): The C compiler "/usr/bin/cc" is not able to compile a simple test program. It fails with the following output: Change Dir: /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075 [1/2] Building C object CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o FAILED: /usr/bin/cc -fPIC -arch x86_64 -mmacosx-version-min=10.9 -sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk -o CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o -c testCCompiler.c clang: error: unknown argument: '-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' [-Wunused-command-line-argument-hard-error-in-future] clang: note: this will be a hard error (cannot be downgraded to a warning) in the future ninja: build stopped: subcommand failed. Even if I empty the CMAKE_OSX_SYSROOT variable, the system still tries to pass an empty -sysroot flag to clang causing it to choke. I removed the sysroot flag from the top-level CMakeLists.txt, but then the ParaView CMake setup fails for a reason I can?t seem to understand. I?m attaching the log showing the CMake output. The only obvious thing I see is the Fortran compiler. Is that required? Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From cory.quammen at kitware.com Thu Sep 4 08:39:08 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 4 Sep 2014 08:39:08 -0400 Subject: [Paraview] number fields In-Reply-To: <4733FE02-28F3-4D93-B769-E53A3D9F68E4@uvm.edu> References: <4733FE02-28F3-4D93-B769-E53A3D9F68E4@uvm.edu> Message-ID: Hi Ryan, This is a known bug on Mac OS: http://www.paraview.org/Bug/view.php?id=14311 We have not yet tracked down the problem that I know of. It has been a while since I have run ParaView on a Mac, but if I recall correctly, you could work around this by clicking in the render view and then clicking back in the field where editing wasn't working, and that would let you at least edit the number field you were changing. Hope that helps, Cory On Wed, Sep 3, 2014 at 7:10 PM, Ryan Crocker wrote: > I'm using the Paraview 4 64 bit on os x 10.6. Every now and then i can not write in the number fields unless i re-load the state. This has always been a problem but it is more noticeable now that i'm doing a lot more post processing. Why does Paraview do that and is there a way to fix it? > > Ryan Crocker > University of Vermont, School of Engineering > Mechanical Engineering Department > rcrocker at uvm.edu > 315-212-7331 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Thu Sep 4 09:22:03 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 4 Sep 2014 09:22:03 -0400 Subject: [Paraview] Superbuild and OSX In-Reply-To: References: Message-ID: Sorry, I did mean Mavericks :)..I can never keep the MacOS names straight. On Thu, Sep 4, 2014 at 8:00 AM, Reuter, Michael A. wrote: > Thanks for the update. I?m actually building on Mavericks, but our project is still supporting Mountain Lion so it will be good to have it work there. > > M > > > On Sep 3, 2014, at 11:57 PM, Utkarsh Ayachit > wrote: > > Michael, > > Hold off on using the superbuild on MountainLion for now. I'll track > the issues down and then let you know. > > > Utkarsh > > On Wed, Sep 3, 2014 at 6:23 PM, Utkarsh Ayachit > > wrote: > Michael, > > Let me try this on a Moutain Lion myself and I'll let you know. What > projects are you turning on in your build? > > Utkarsh > > On Wed, Sep 3, 2014 at 2:40 PM, Reuter, Michael A. > wrote: > This gets around the clang argument problem, but the ParaView CMake configuration step still fails for an unknown reason. > > M > > On Sep 3, 2014, at 10:28 AM, Utkarsh Ayachit > wrote: > > Cherry-pick this fix for now : http://review.source.kitware.com/#/c/16665/ > It'll go into master soon. > > Ben, anything this fix is waiting on? > > Utkarsh > > On Wed, Sep 3, 2014 at 9:42 AM, Reuter, Michael A. > wrote: > Hi, > > I?m having trouble getting the git-master version of the Superbuild running on OSX (10.9) with clang (5.1). Setting the CMAKE_OSX_SYSROOT variable causes the following error during CMake (2.8.12.2) generation for the ParaView subproject: > > -- The C compiler identification is unknown > -- The CXX compiler identification is unknown > -- Check for working C compiler using: Ninja > -- Check for working C compiler using: Ninja -- broken > CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): > The C compiler "/usr/bin/cc" is not able to compile a simple test program. > > It fails with the following output: > > Change Dir: /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp > > Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075 > > [1/2] Building C object > CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o > > FAILED: /usr/bin/cc -fPIC -arch x86_64 -mmacosx-version-min=10.9 > -sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk > -o CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o -c > testCCompiler.c > > clang: error: unknown argument: > '-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' > [-Wunused-command-line-argument-hard-error-in-future] > > clang: note: this will be a hard error (cannot be downgraded to a warning) > in the future > > ninja: build stopped: subcommand failed. > > Even if I empty the CMAKE_OSX_SYSROOT variable, the system still tries to pass an empty -sysroot flag to clang causing it to choke. I removed the sysroot flag from the top-level CMakeLists.txt, but then the ParaView CMake setup fails for a reason I can?t seem to understand. I?m attaching the log showing the CMake output. The only obvious thing I see is the Fortran compiler. Is that required? > > Thanks, > M > > Dr. Michael Reuter > Scientific Data Analysis Group > Neutron Data Analysis and Visualization Division > Oak Ridge National Laboratory > > Office: 1-865-241-7216 > Fax: 1-865-574-6080 > Email: reuterma at ornl.gov > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > From reuterma at ornl.gov Thu Sep 4 10:09:07 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Thu, 4 Sep 2014 14:09:07 +0000 Subject: [Paraview] QuadView option Message-ID: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Hi, I?m looking for the option that turns off the outline in the 3D panel in the Quad View in ParaView git-master. This used to be in the view settings dialog, but that no longer exists and the settings dialog doesn?t seem to have it unless I missed it. The Slice View has a similar option in the Properties panel under Background, but nothing appears there for the Quad View. Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov From Gerald.Lodron at joanneum.at Thu Sep 4 09:23:45 2014 From: Gerald.Lodron at joanneum.at (Lodron, Gerald) Date: Thu, 4 Sep 2014 13:23:45 +0000 Subject: [Paraview] Paraview and VS2013 compile errors Message-ID: <58fef09f89374bc3aa2e8db159886be3@RZJMBX2.jr1.local> Hi I am compiling PV with qt 5.2.1, internal VTK and boost 1.55 (for ReebGraph), under 64bit (without python) and get following errors: Min max unknown in protobuf, following patch works: https://code.google.com/p/protobuf/issues/detail?id=531 I also get many 2>C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\type_traits(1220): error C2065: 'max_align_t' : undeclared identifier Adding #include to common.h of protobuf solved that in porotobuf but I get it also in CommandLineArguments.cxx of vtksys where that solution does not worked... Additionally I get many linker errors: 6>QtTesting_automoc.obj : error LNK2005: "public: static struct QMetaObject const pqComboBoxEventTranslator::staticMetaObject" (?staticMetaObject at pqComboBoxEventTranslator@@2UQMetaObject@@B) already defined in moc_pqComboBoxEventTranslator.obj 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "public: virtual struct QMetaObject const * __cdecl QVTKPlugin::metaObject(void)const " (?metaObject at QVTKPlugin@@UEBAPEBUQMetaObject@@XZ) already defined in moc_Q4VTKWidgetPlugin.obj 6>QtTesting_automoc.obj : error LNK2005: "private: static void __cdecl pqComboBoxEventTranslator::qt_static_metacall(class QObject *,enum QMetaObject::Call,int,void * *)" (?qt_static_metacall at pqComboBoxEventTranslator@@CAXPEAVQObject@@W4Call at QMetaObject@@HPEAPEAX at Z) already defined in moc_pqComboBoxEventTranslator.obj 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "public: virtual void * __cdecl QVTKPlugin::qt_metacast(char const *)" (?qt_metacast at QVTKPlugin@@UEAAPEAXPEBD at Z) already defined in moc_Q4VTKWidgetPlugin.obj 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "public: virtual int __cdecl QVTKPlugin::qt_metacall(enum QMetaObject::Call,int,void * *)" (?qt_metacall at QVTKPlugin@@UEAAHW4Call at QMetaObject@@HPEAPEAX at Z) already defined in moc_Q4VTKWidgetPlugin.obj 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "private: static void __cdecl QVTKPlugin::qt_static_metacall(class QObject *,enum QMetaObject::Call,int,void * *)" (?qt_static_metacall at QVTKPlugin@@CAXPEAVQObject@@W4Call at QMetaObject@@HPEAPEAX at Z) already defined in moc_Q4VTKWidgetPlugin.obj 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "public: virtual struct QMetaObject const * __cdecl QVTKWidget::metaObject(void)const " (?metaObject at QVTKWidget@@UEBAPEBUQMetaObject@@XZ) already defined in moc_Q4VTKWidgetPlugin.obj 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "public: virtual void * __cdecl QVTKWidget::qt_metacast(char const *)" (?qt_metacast at QVTKWidget@@UEAAPEAXPEBD at Z) already defined in moc_Q4VTKWidgetPlugin.obj 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "public: virtual int __cdecl QVTKWidget::qt_metacall(enum QMetaObject::Call,int,void * *)" (?qt_metacall at QVTKWidget@@UEAAHW4Call at QMetaObject@@HPEAPEAX at Z) already defined in moc_Q4VTKWidgetPlugin.obj 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: "private: static void __cdecl QVTKWidget::qt_static_metacall(class QObject *,enum QMetaObject::Call,int,void * *)" (?qt_static_metacall at QVTKWidget@@CAXPEAVQObject@@W4Call at QMetaObject@@HPEAPEAX at Z) already defined in moc_Q4VTKWidgetPlugin.obj 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: qt_plugin_query_metadata already defined in moc_Q4VTKWidgetPlugin.obj 9>QVTKWidgetPlugin_automoc.obj : error LNK2005: qt_plugin_instance already defined in moc_Q4VTKWidgetPlugin.obj Any hints? -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Thu Sep 4 10:50:47 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 4 Sep 2014 08:50:47 -0600 Subject: [Paraview] QuadView option In-Reply-To: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: Hi Michael, I don't think there is such option. In fact, this must be due to the representation be set to "Outline" in the toolbar. If you change it to Surface of Wireframe you should not see anymore the outline. Seb On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. wrote: > Hi, > > I?m looking for the option that turns off the outline in the 3D panel in > the Quad View in ParaView git-master. This used to be in the view settings > dialog, but that no longer exists and the settings dialog doesn?t seem to > have it unless I missed it. The Slice View has a similar option in the > Properties panel under Background, but nothing appears there for the Quad > View. > > Thanks, > M > > Dr. Michael Reuter > Scientific Data Analysis Group > Neutron Data Analysis and Visualization Division > Oak Ridge National Laboratory > > Office: 1-865-241-7216 > Fax: 1-865-574-6080 > Email: reuterma at ornl.gov > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From reuterma at ornl.gov Thu Sep 4 11:20:16 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Thu, 4 Sep 2014 15:20:16 +0000 Subject: [Paraview] QuadView option In-Reply-To: References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: I?m providing a screenshot showing the option (Show Outline in 3D View) that appears in the View Settings dialog box in PV 3.98.1. The dialog was available from Edit/View Settings menu option. The 3D outline was effective when the Slice representation is used. This also brings up another issue. All the options that are in this dialog are not available either. I use the Quad View in a user distributed program and some of them use these options. They aren?t going to be happy when the upgrade removes them. M [cid:3662796F-3858-454F-9AF6-C956B97353FA at ornl.gov] On Sep 4, 2014, at 10:50 AM, Sebastien Jourdain > wrote: Hi Michael, I don't think there is such option. In fact, this must be due to the representation be set to "Outline" in the toolbar. If you change it to Surface of Wireframe you should not see anymore the outline. Seb On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. > wrote: Hi, I?m looking for the option that turns off the outline in the 3D panel in the Quad View in ParaView git-master. This used to be in the view settings dialog, but that no longer exists and the settings dialog doesn?t seem to have it unless I missed it. The Slice View has a similar option in the Properties panel under Background, but nothing appears there for the Quad View. Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov> _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- A non-text attachment was scrubbed... Name: QuadViewOption.png Type: image/png Size: 183665 bytes Desc: QuadViewOption.png URL: From utkarsh.ayachit at kitware.com Thu Sep 4 11:25:33 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 4 Sep 2014 11:25:33 -0400 Subject: [Paraview] QuadView option In-Reply-To: References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: I think the "Show Outline in 3D View" on the Properties panel is indeed the right option. The fact that it has no effect is a bug. Utkarsh On Thu, Sep 4, 2014 at 11:20 AM, Reuter, Michael A. wrote: > I?m providing a screenshot showing the option (Show Outline in 3D View) that appears in the View Settings dialog box in PV 3.98.1. The dialog was available from Edit/View Settings menu option. The 3D outline was effective when the Slice representation is used. This also brings up another issue. All the options that are in this dialog are not available either. I use the Quad View in a user distributed program and some of them use these options. They aren?t going to be happy when the upgrade removes them. > > M > > [cid:3662796F-3858-454F-9AF6-C956B97353FA at ornl.gov] > > > On Sep 4, 2014, at 10:50 AM, Sebastien Jourdain > wrote: > > Hi Michael, > > I don't think there is such option. > In fact, this must be due to the representation be set to "Outline" in the toolbar. > If you change it to Surface of Wireframe you should not see anymore the outline. > > Seb > > > On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. > wrote: > Hi, > > I?m looking for the option that turns off the outline in the 3D panel in the Quad View in ParaView git-master. This used to be in the view settings dialog, but that no longer exists and the settings dialog doesn?t seem to have it unless I missed it. The Slice View has a similar option in the Properties panel under Background, but nothing appears there for the Quad View. > > Thanks, > M > > Dr. Michael Reuter > Scientific Data Analysis Group > Neutron Data Analysis and Visualization Division > Oak Ridge National Laboratory > > Office: 1-865-241-7216 > Fax: 1-865-574-6080 > Email: reuterma at ornl.gov> > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Thu Sep 4 11:29:44 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 4 Sep 2014 11:29:44 -0400 Subject: [Paraview] QuadView option In-Reply-To: References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: I think I've spotted the issue in vtkQuadRepresentation. I'll have a fix soon. On Thu, Sep 4, 2014 at 11:25 AM, Utkarsh Ayachit wrote: > I think the "Show Outline in 3D View" on the Properties panel is > indeed the right option. The fact that it has no effect is a bug. > > Utkarsh > > On Thu, Sep 4, 2014 at 11:20 AM, Reuter, Michael A. wrote: >> I?m providing a screenshot showing the option (Show Outline in 3D View) that appears in the View Settings dialog box in PV 3.98.1. The dialog was available from Edit/View Settings menu option. The 3D outline was effective when the Slice representation is used. This also brings up another issue. All the options that are in this dialog are not available either. I use the Quad View in a user distributed program and some of them use these options. They aren?t going to be happy when the upgrade removes them. >> >> M >> >> [cid:3662796F-3858-454F-9AF6-C956B97353FA at ornl.gov] >> >> >> On Sep 4, 2014, at 10:50 AM, Sebastien Jourdain > wrote: >> >> Hi Michael, >> >> I don't think there is such option. >> In fact, this must be due to the representation be set to "Outline" in the toolbar. >> If you change it to Surface of Wireframe you should not see anymore the outline. >> >> Seb >> >> >> On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. > wrote: >> Hi, >> >> I?m looking for the option that turns off the outline in the 3D panel in the Quad View in ParaView git-master. This used to be in the view settings dialog, but that no longer exists and the settings dialog doesn?t seem to have it unless I missed it. The Slice View has a similar option in the Properties panel under Background, but nothing appears there for the Quad View. >> >> Thanks, >> M >> >> Dr. Michael Reuter >> Scientific Data Analysis Group >> Neutron Data Analysis and Visualization Division >> Oak Ridge National Laboratory >> >> Office: 1-865-241-7216 >> Fax: 1-865-574-6080 >> Email: reuterma at ornl.gov> >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From sebastien.jourdain at kitware.com Thu Sep 4 11:30:02 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 4 Sep 2014 09:30:02 -0600 Subject: [Paraview] QuadView option In-Reply-To: References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: On my Mac from yesterday's master, the option does allow me to toggle the outline. I just forgot about that Slices representation... On Thu, Sep 4, 2014 at 9:25 AM, Utkarsh Ayachit wrote: > I think the "Show Outline in 3D View" on the Properties panel is > indeed the right option. The fact that it has no effect is a bug. > > Utkarsh > > On Thu, Sep 4, 2014 at 11:20 AM, Reuter, Michael A. > wrote: > > I?m providing a screenshot showing the option (Show Outline in 3D View) > that appears in the View Settings dialog box in PV 3.98.1. The dialog was > available from Edit/View Settings menu option. The 3D outline was effective > when the Slice representation is used. This also brings up another issue. > All the options that are in this dialog are not available either. I use the > Quad View in a user distributed program and some of them use these options. > They aren?t going to be happy when the upgrade removes them. > > > > M > > > > [cid:3662796F-3858-454F-9AF6-C956B97353FA at ornl.gov] > > > > > > On Sep 4, 2014, at 10:50 AM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> > wrote: > > > > Hi Michael, > > > > I don't think there is such option. > > In fact, this must be due to the representation be set to "Outline" in > the toolbar. > > If you change it to Surface of Wireframe you should not see anymore the > outline. > > > > Seb > > > > > > On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. > wrote: > > Hi, > > > > I?m looking for the option that turns off the outline in the 3D panel in > the Quad View in ParaView git-master. This used to be in the view settings > dialog, but that no longer exists and the settings dialog doesn?t seem to > have it unless I missed it. The Slice View has a similar option in the > Properties panel under Background, but nothing appears there for the Quad > View. > > > > Thanks, > > M > > > > Dr. Michael Reuter > > Scientific Data Analysis Group > > Neutron Data Analysis and Visualization Division > > Oak Ridge National Laboratory > > > > Office: 1-865-241-7216 > > Fax: 1-865-574-6080 > > Email: reuterma at ornl.gov reuterma at ornl.gov> > > > > > > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Sep 4 11:38:33 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 4 Sep 2014 11:38:33 -0400 Subject: [Paraview] QuadView option In-Reply-To: References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: Can someone explain what this option is supposed to do? Even in 3.98.1 it has no effect for me, or at least I don't see anything change. On Thu, Sep 4, 2014 at 11:30 AM, Sebastien Jourdain wrote: > On my Mac from yesterday's master, the option does allow me to toggle the > outline. > I just forgot about that Slices representation... > > > On Thu, Sep 4, 2014 at 9:25 AM, Utkarsh Ayachit > wrote: >> >> I think the "Show Outline in 3D View" on the Properties panel is >> indeed the right option. The fact that it has no effect is a bug. >> >> Utkarsh >> >> On Thu, Sep 4, 2014 at 11:20 AM, Reuter, Michael A. >> wrote: >> > I?m providing a screenshot showing the option (Show Outline in 3D View) >> > that appears in the View Settings dialog box in PV 3.98.1. The dialog was >> > available from Edit/View Settings menu option. The 3D outline was effective >> > when the Slice representation is used. This also brings up another issue. >> > All the options that are in this dialog are not available either. I use the >> > Quad View in a user distributed program and some of them use these options. >> > They aren?t going to be happy when the upgrade removes them. >> > >> > M >> > >> > [cid:3662796F-3858-454F-9AF6-C956B97353FA at ornl.gov] >> > >> > >> > On Sep 4, 2014, at 10:50 AM, Sebastien Jourdain >> > > >> > wrote: >> > >> > Hi Michael, >> > >> > I don't think there is such option. >> > In fact, this must be due to the representation be set to "Outline" in >> > the toolbar. >> > If you change it to Surface of Wireframe you should not see anymore the >> > outline. >> > >> > Seb >> > >> > >> > On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. >> > > wrote: >> > Hi, >> > >> > I?m looking for the option that turns off the outline in the 3D panel in >> > the Quad View in ParaView git-master. This used to be in the view settings >> > dialog, but that no longer exists and the settings dialog doesn?t seem to >> > have it unless I missed it. The Slice View has a similar option in the >> > Properties panel under Background, but nothing appears there for the Quad >> > View. >> > >> > Thanks, >> > M >> > >> > Dr. Michael Reuter >> > Scientific Data Analysis Group >> > Neutron Data Analysis and Visualization Division >> > Oak Ridge National Laboratory >> > >> > Office: 1-865-241-7216 >> > Fax: 1-865-574-6080 >> > Email: >> > reuterma at ornl.gov> >> > >> > >> > >> > >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > > > From reuterma at ornl.gov Thu Sep 4 11:56:01 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Thu, 4 Sep 2014 15:56:01 +0000 Subject: [Paraview] QuadView option In-Reply-To: References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: <98A57BD8-AFA7-4DFD-8803-1DFA9660F2B6@ornl.gov> Hi Utkarsh, The outline only comes into effect when using the Slices representation in the Quad View. If you use the Surface rep, there is no outline. M On Sep 4, 2014, at 11:38 AM, Utkarsh Ayachit > wrote: Can someone explain what this option is supposed to do? Even in 3.98.1 it has no effect for me, or at least I don't see anything change. On Thu, Sep 4, 2014 at 11:30 AM, Sebastien Jourdain > wrote: On my Mac from yesterday's master, the option does allow me to toggle the outline. I just forgot about that Slices representation... On Thu, Sep 4, 2014 at 9:25 AM, Utkarsh Ayachit > wrote: I think the "Show Outline in 3D View" on the Properties panel is indeed the right option. The fact that it has no effect is a bug. Utkarsh On Thu, Sep 4, 2014 at 11:20 AM, Reuter, Michael A. > wrote: I?m providing a screenshot showing the option (Show Outline in 3D View) that appears in the View Settings dialog box in PV 3.98.1. The dialog was available from Edit/View Settings menu option. The 3D outline was effective when the Slice representation is used. This also brings up another issue. All the options that are in this dialog are not available either. I use the Quad View in a user distributed program and some of them use these options. They aren?t going to be happy when the upgrade removes them. M [cid:3662796F-3858-454F-9AF6-C956B97353FA at ornl.gov] On Sep 4, 2014, at 10:50 AM, Sebastien Jourdain > wrote: Hi Michael, I don't think there is such option. In fact, this must be due to the representation be set to "Outline" in the toolbar. If you change it to Surface of Wireframe you should not see anymore the outline. Seb On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. > wrote: Hi, I?m looking for the option that turns off the outline in the 3D panel in the Quad View in ParaView git-master. This used to be in the view settings dialog, but that no longer exists and the settings dialog doesn?t seem to have it unless I missed it. The Slice View has a similar option in the Properties panel under Background, but nothing appears there for the Quad View. Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov> _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Thu Sep 4 11:56:45 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 4 Sep 2014 11:56:45 -0400 Subject: [Paraview] QuadView option In-Reply-To: References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: Alright, here's the final diagnosis :): It's works as Seb was saying. What I was missing that I had not selected the Slices "representation". Once Slices representation is chosen, the "Show outline in 3D view" option starts working. This is indeed the way the view behaves in 3.98.1 as well. Utkarsh On Thu, Sep 4, 2014 at 11:38 AM, Utkarsh Ayachit wrote: > Can someone explain what this option is supposed to do? Even in 3.98.1 > it has no effect for me, or at least I don't see anything change. > > On Thu, Sep 4, 2014 at 11:30 AM, Sebastien Jourdain > wrote: >> On my Mac from yesterday's master, the option does allow me to toggle the >> outline. >> I just forgot about that Slices representation... >> >> >> On Thu, Sep 4, 2014 at 9:25 AM, Utkarsh Ayachit >> wrote: >>> >>> I think the "Show Outline in 3D View" on the Properties panel is >>> indeed the right option. The fact that it has no effect is a bug. >>> >>> Utkarsh >>> >>> On Thu, Sep 4, 2014 at 11:20 AM, Reuter, Michael A. >>> wrote: >>> > I?m providing a screenshot showing the option (Show Outline in 3D View) >>> > that appears in the View Settings dialog box in PV 3.98.1. The dialog was >>> > available from Edit/View Settings menu option. The 3D outline was effective >>> > when the Slice representation is used. This also brings up another issue. >>> > All the options that are in this dialog are not available either. I use the >>> > Quad View in a user distributed program and some of them use these options. >>> > They aren?t going to be happy when the upgrade removes them. >>> > >>> > M >>> > >>> > [cid:3662796F-3858-454F-9AF6-C956B97353FA at ornl.gov] >>> > >>> > >>> > On Sep 4, 2014, at 10:50 AM, Sebastien Jourdain >>> > > >>> > wrote: >>> > >>> > Hi Michael, >>> > >>> > I don't think there is such option. >>> > In fact, this must be due to the representation be set to "Outline" in >>> > the toolbar. >>> > If you change it to Surface of Wireframe you should not see anymore the >>> > outline. >>> > >>> > Seb >>> > >>> > >>> > On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. >>> > > wrote: >>> > Hi, >>> > >>> > I?m looking for the option that turns off the outline in the 3D panel in >>> > the Quad View in ParaView git-master. This used to be in the view settings >>> > dialog, but that no longer exists and the settings dialog doesn?t seem to >>> > have it unless I missed it. The Slice View has a similar option in the >>> > Properties panel under Background, but nothing appears there for the Quad >>> > View. >>> > >>> > Thanks, >>> > M >>> > >>> > Dr. Michael Reuter >>> > Scientific Data Analysis Group >>> > Neutron Data Analysis and Visualization Division >>> > Oak Ridge National Laboratory >>> > >>> > Office: 1-865-241-7216 >>> > Fax: 1-865-574-6080 >>> > Email: >>> > reuterma at ornl.gov> >>> > >>> > >>> > >>> > >>> > >>> > >>> > _______________________________________________ >>> > Powered by www.kitware.com >>> > >>> > Visit other Kitware open-source projects at >>> > http://www.kitware.com/opensource/opensource.html >>> > >>> > Please keep messages on-topic and check the ParaView Wiki at: >>> > http://paraview.org/Wiki/ParaView >>> > >>> > Follow this link to subscribe/unsubscribe: >>> > http://public.kitware.com/mailman/listinfo/paraview >>> > >>> > >>> > >>> > _______________________________________________ >>> > Powered by www.kitware.com >>> > >>> > Visit other Kitware open-source projects at >>> > http://www.kitware.com/opensource/opensource.html >>> > >>> > Please keep messages on-topic and check the ParaView Wiki at: >>> > http://paraview.org/Wiki/ParaView >>> > >>> > Follow this link to subscribe/unsubscribe: >>> > http://public.kitware.com/mailman/listinfo/paraview >>> > >> >> From utkarsh.ayachit at kitware.com Thu Sep 4 12:00:50 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 4 Sep 2014 12:00:50 -0400 Subject: [Paraview] QuadView option In-Reply-To: References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: BTW, I am pushing an update to the git repo to better organize the properties on the "Properties" panel for the Quad View. On Thu, Sep 4, 2014 at 11:56 AM, Utkarsh Ayachit wrote: > Alright, here's the final diagnosis :): > > It's works as Seb was saying. What I was missing that I had not > selected the Slices "representation". Once Slices representation is > chosen, the "Show outline in 3D view" option starts working. This is > indeed the way the view behaves in 3.98.1 as well. > > Utkarsh > > On Thu, Sep 4, 2014 at 11:38 AM, Utkarsh Ayachit > wrote: >> Can someone explain what this option is supposed to do? Even in 3.98.1 >> it has no effect for me, or at least I don't see anything change. >> >> On Thu, Sep 4, 2014 at 11:30 AM, Sebastien Jourdain >> wrote: >>> On my Mac from yesterday's master, the option does allow me to toggle the >>> outline. >>> I just forgot about that Slices representation... >>> >>> >>> On Thu, Sep 4, 2014 at 9:25 AM, Utkarsh Ayachit >>> wrote: >>>> >>>> I think the "Show Outline in 3D View" on the Properties panel is >>>> indeed the right option. The fact that it has no effect is a bug. >>>> >>>> Utkarsh >>>> >>>> On Thu, Sep 4, 2014 at 11:20 AM, Reuter, Michael A. >>>> wrote: >>>> > I?m providing a screenshot showing the option (Show Outline in 3D View) >>>> > that appears in the View Settings dialog box in PV 3.98.1. The dialog was >>>> > available from Edit/View Settings menu option. The 3D outline was effective >>>> > when the Slice representation is used. This also brings up another issue. >>>> > All the options that are in this dialog are not available either. I use the >>>> > Quad View in a user distributed program and some of them use these options. >>>> > They aren?t going to be happy when the upgrade removes them. >>>> > >>>> > M >>>> > >>>> > [cid:3662796F-3858-454F-9AF6-C956B97353FA at ornl.gov] >>>> > >>>> > >>>> > On Sep 4, 2014, at 10:50 AM, Sebastien Jourdain >>>> > > >>>> > wrote: >>>> > >>>> > Hi Michael, >>>> > >>>> > I don't think there is such option. >>>> > In fact, this must be due to the representation be set to "Outline" in >>>> > the toolbar. >>>> > If you change it to Surface of Wireframe you should not see anymore the >>>> > outline. >>>> > >>>> > Seb >>>> > >>>> > >>>> > On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. >>>> > > wrote: >>>> > Hi, >>>> > >>>> > I?m looking for the option that turns off the outline in the 3D panel in >>>> > the Quad View in ParaView git-master. This used to be in the view settings >>>> > dialog, but that no longer exists and the settings dialog doesn?t seem to >>>> > have it unless I missed it. The Slice View has a similar option in the >>>> > Properties panel under Background, but nothing appears there for the Quad >>>> > View. >>>> > >>>> > Thanks, >>>> > M >>>> > >>>> > Dr. Michael Reuter >>>> > Scientific Data Analysis Group >>>> > Neutron Data Analysis and Visualization Division >>>> > Oak Ridge National Laboratory >>>> > >>>> > Office: 1-865-241-7216 >>>> > Fax: 1-865-574-6080 >>>> > Email: >>>> > reuterma at ornl.gov> >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > _______________________________________________ >>>> > Powered by www.kitware.com >>>> > >>>> > Visit other Kitware open-source projects at >>>> > http://www.kitware.com/opensource/opensource.html >>>> > >>>> > Please keep messages on-topic and check the ParaView Wiki at: >>>> > http://paraview.org/Wiki/ParaView >>>> > >>>> > Follow this link to subscribe/unsubscribe: >>>> > http://public.kitware.com/mailman/listinfo/paraview >>>> > >>>> > >>>> > >>>> > _______________________________________________ >>>> > Powered by www.kitware.com >>>> > >>>> > Visit other Kitware open-source projects at >>>> > http://www.kitware.com/opensource/opensource.html >>>> > >>>> > Please keep messages on-topic and check the ParaView Wiki at: >>>> > http://paraview.org/Wiki/ParaView >>>> > >>>> > Follow this link to subscribe/unsubscribe: >>>> > http://public.kitware.com/mailman/listinfo/paraview >>>> > >>> >>> From simon.m.su.ctr at mail.mil Thu Sep 4 12:06:17 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 4 Sep 2014 16:06:17 +0000 Subject: [Paraview] implication of -DUSE_SYSTEM_python=OFF (UNCLASSIFIED) Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hello, What is the difference between -DUSE_SYSTEM_python=OFF and -DUSE_SYSTEM_python=ON superbuild PV compile? Are there things that I need to setup differently between the two type of compile to make sure that PV is picking up the right python version after I deploy the binary compiled? Thanks -simon Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Sep 4 12:09:23 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 4 Sep 2014 12:09:23 -0400 Subject: [Paraview] QuadView option In-Reply-To: References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: Attached is the patch (will be in git/master after next gatekeeper review). I made all the properties "default" to avoid confusion. Michael, feel free to suggest better default visibility options. Thanks Utkarsh On Thu, Sep 4, 2014 at 12:00 PM, Utkarsh Ayachit wrote: > BTW, I am pushing an update to the git repo to better organize the > properties on the "Properties" panel for the Quad View. > > On Thu, Sep 4, 2014 at 11:56 AM, Utkarsh Ayachit > wrote: >> Alright, here's the final diagnosis :): >> >> It's works as Seb was saying. What I was missing that I had not >> selected the Slices "representation". Once Slices representation is >> chosen, the "Show outline in 3D view" option starts working. This is >> indeed the way the view behaves in 3.98.1 as well. >> >> Utkarsh >> >> On Thu, Sep 4, 2014 at 11:38 AM, Utkarsh Ayachit >> wrote: >>> Can someone explain what this option is supposed to do? Even in 3.98.1 >>> it has no effect for me, or at least I don't see anything change. >>> >>> On Thu, Sep 4, 2014 at 11:30 AM, Sebastien Jourdain >>> wrote: >>>> On my Mac from yesterday's master, the option does allow me to toggle the >>>> outline. >>>> I just forgot about that Slices representation... >>>> >>>> >>>> On Thu, Sep 4, 2014 at 9:25 AM, Utkarsh Ayachit >>>> wrote: >>>>> >>>>> I think the "Show Outline in 3D View" on the Properties panel is >>>>> indeed the right option. The fact that it has no effect is a bug. >>>>> >>>>> Utkarsh >>>>> >>>>> On Thu, Sep 4, 2014 at 11:20 AM, Reuter, Michael A. >>>>> wrote: >>>>> > I?m providing a screenshot showing the option (Show Outline in 3D View) >>>>> > that appears in the View Settings dialog box in PV 3.98.1. The dialog was >>>>> > available from Edit/View Settings menu option. The 3D outline was effective >>>>> > when the Slice representation is used. This also brings up another issue. >>>>> > All the options that are in this dialog are not available either. I use the >>>>> > Quad View in a user distributed program and some of them use these options. >>>>> > They aren?t going to be happy when the upgrade removes them. >>>>> > >>>>> > M >>>>> > >>>>> > [cid:3662796F-3858-454F-9AF6-C956B97353FA at ornl.gov] >>>>> > >>>>> > >>>>> > On Sep 4, 2014, at 10:50 AM, Sebastien Jourdain >>>>> > > >>>>> > wrote: >>>>> > >>>>> > Hi Michael, >>>>> > >>>>> > I don't think there is such option. >>>>> > In fact, this must be due to the representation be set to "Outline" in >>>>> > the toolbar. >>>>> > If you change it to Surface of Wireframe you should not see anymore the >>>>> > outline. >>>>> > >>>>> > Seb >>>>> > >>>>> > >>>>> > On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. >>>>> > > wrote: >>>>> > Hi, >>>>> > >>>>> > I?m looking for the option that turns off the outline in the 3D panel in >>>>> > the Quad View in ParaView git-master. This used to be in the view settings >>>>> > dialog, but that no longer exists and the settings dialog doesn?t seem to >>>>> > have it unless I missed it. The Slice View has a similar option in the >>>>> > Properties panel under Background, but nothing appears there for the Quad >>>>> > View. >>>>> > >>>>> > Thanks, >>>>> > M >>>>> > >>>>> > Dr. Michael Reuter >>>>> > Scientific Data Analysis Group >>>>> > Neutron Data Analysis and Visualization Division >>>>> > Oak Ridge National Laboratory >>>>> > >>>>> > Office: 1-865-241-7216 >>>>> > Fax: 1-865-574-6080 >>>>> > Email: >>>>> > reuterma at ornl.gov> >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > _______________________________________________ >>>>> > Powered by www.kitware.com >>>>> > >>>>> > Visit other Kitware open-source projects at >>>>> > http://www.kitware.com/opensource/opensource.html >>>>> > >>>>> > Please keep messages on-topic and check the ParaView Wiki at: >>>>> > http://paraview.org/Wiki/ParaView >>>>> > >>>>> > Follow this link to subscribe/unsubscribe: >>>>> > http://public.kitware.com/mailman/listinfo/paraview >>>>> > >>>>> > >>>>> > >>>>> > _______________________________________________ >>>>> > Powered by www.kitware.com >>>>> > >>>>> > Visit other Kitware open-source projects at >>>>> > http://www.kitware.com/opensource/opensource.html >>>>> > >>>>> > Please keep messages on-topic and check the ParaView Wiki at: >>>>> > http://paraview.org/Wiki/ParaView >>>>> > >>>>> > Follow this link to subscribe/unsubscribe: >>>>> > http://public.kitware.com/mailman/listinfo/paraview >>>>> > >>>> >>>> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Update-default-property-visibility-and-grouping-for-.patch Type: text/x-patch Size: 6598 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Sep 4 12:12:36 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 4 Sep 2014 12:12:36 -0400 Subject: [Paraview] implication of -DUSE_SYSTEM_python=OFF (UNCLASSIFIED) In-Reply-To: References: Message-ID: USE_SYSTEM_python=OFF will result in ParaView compile and package it's Python version. USE_SYSTEM_python=ON will result in ParaView using a version installed on your system. Thus the bundle won't be work on any other systems where the Python you build against isn't available. With USE_SYSTEM_python=ON, advanced CMAke options will allow you to pick which Python libraries and executables to use for the build (similar to what one sets in a regular ParaView build). Utkarsh On Thu, Sep 4, 2014 at 12:06 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > What is the difference between -DUSE_SYSTEM_python=OFF and > -DUSE_SYSTEM_python=ON superbuild PV compile? Are there things that I need > to setup differently between the two type of compile to make sure that PV is > picking up the right python version after I deploy the binary compiled? > > Thanks > -simon > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From simon.m.su.ctr at mail.mil Thu Sep 4 12:21:03 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 4 Sep 2014 16:21:03 +0000 Subject: [Paraview] implication of -DUSE_SYSTEM_python=OFF (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Thanks Utkarsh. Then PV compiled with USE_SYSTEM_python=OFF, none of the system installed python related packages (numpy, scipy, etc, etc) will work in PV right? And only those python packages (numpy) included in the PV superbuild process are available for use. Right? Thanks -simon -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Thursday, September 04, 2014 12:13 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] implication of -DUSE_SYSTEM_python=OFF (UNCLASSIFIED) USE_SYSTEM_python=OFF will result in ParaView compile and package it's Python version. USE_SYSTEM_python=ON will result in ParaView using a version installed on your system. Thus the bundle won't be work on any other systems where the Python you build against isn't available. With USE_SYSTEM_python=ON, advanced CMAke options will allow you to pick which Python libraries and executables to use for the build (similar to what one sets in a regular ParaView build). Utkarsh On Thu, Sep 4, 2014 at 12:06 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > What is the difference between -DUSE_SYSTEM_python=OFF and > -DUSE_SYSTEM_python=ON superbuild PV compile? Are there things that I > need to setup differently between the two type of compile to make sure > that PV is picking up the right python version after I deploy the binary > compiled? > > Thanks > -simon > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Sep 4 12:47:17 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 4 Sep 2014 12:47:17 -0400 Subject: [Paraview] implication of -DUSE_SYSTEM_python=OFF (UNCLASSIFIED) In-Reply-To: References: Message-ID: You're absolutely right. In general, if you're building a package to deploy on the same machine you should use-system-*=ON for as many components are possible including Python, MPI, (and maybe even Qt). Utkarsh On Thu, Sep 4, 2014 at 12:21 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Thanks Utkarsh. Then PV compiled with USE_SYSTEM_python=OFF, none of the > system installed python related packages (numpy, scipy, etc, etc) will work in > PV right? And only those python packages (numpy) included in the PV superbuild > process are available for use. Right? > > Thanks > -simon > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Thursday, September 04, 2014 12:13 PM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] implication of -DUSE_SYSTEM_python=OFF (UNCLASSIFIED) > > USE_SYSTEM_python=OFF will result in ParaView compile and package it's Python > version. USE_SYSTEM_python=ON will result in ParaView using a version > installed on your system. Thus the bundle won't be work on any other systems > where the Python you build against isn't available. > > With USE_SYSTEM_python=ON, advanced CMAke options will allow you to pick which > Python libraries and executables to use for the build (similar to what one > sets in a regular ParaView build). > > Utkarsh > > On Thu, Sep 4, 2014 at 12:06 PM, Su, Simon M CTR USARMY ARL (US) > wrote: >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> Hello, >> >> What is the difference between -DUSE_SYSTEM_python=OFF and >> -DUSE_SYSTEM_python=ON superbuild PV compile? Are there things that I >> need to setup differently between the two type of compile to make sure >> that PV is picking up the right python version after I deploy the binary >> compiled? >> >> Thanks >> -simon >> >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > Classification: UNCLASSIFIED > Caveats: NONE > > From simon.m.su.ctr at mail.mil Thu Sep 4 14:01:40 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 4 Sep 2014 18:01:40 +0000 Subject: [Paraview] implication of -DUSE_SYSTEM_python=OFF (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Thanks Utkarsh -simon -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Thursday, September 04, 2014 12:47 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] implication of -DUSE_SYSTEM_python=OFF (UNCLASSIFIED) You're absolutely right. In general, if you're building a package to deploy on the same machine you should use-system-*=ON for as many components are possible including Python, MPI, (and maybe even Qt). Utkarsh On Thu, Sep 4, 2014 at 12:21 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Thanks Utkarsh. Then PV compiled with USE_SYSTEM_python=OFF, none of > the system installed python related packages (numpy, scipy, etc, etc) > will work in PV right? And only those python packages (numpy) included > in the PV superbuild process are available for use. Right? > > Thanks > -simon > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Thursday, September 04, 2014 12:13 PM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] implication of -DUSE_SYSTEM_python=OFF > (UNCLASSIFIED) > > USE_SYSTEM_python=OFF will result in ParaView compile and package it's > Python version. USE_SYSTEM_python=ON will result in ParaView using a > version installed on your system. Thus the bundle won't be work on any > other systems where the Python you build against isn't available. > > With USE_SYSTEM_python=ON, advanced CMAke options will allow you to > pick which Python libraries and executables to use for the build > (similar to what one sets in a regular ParaView build). > > Utkarsh > > On Thu, Sep 4, 2014 at 12:06 PM, Su, Simon M CTR USARMY ARL (US) > wrote: >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> Hello, >> >> What is the difference between -DUSE_SYSTEM_python=OFF and >> -DUSE_SYSTEM_python=ON superbuild PV compile? Are there things that >> I need to setup differently between the two type of compile to make >> sure that PV is picking up the right python version after I deploy >> the binary compiled? >> >> Thanks >> -simon >> >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > Classification: UNCLASSIFIED > Caveats: NONE > > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From reuterma at ornl.gov Thu Sep 4 14:52:17 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Thu, 4 Sep 2014 18:52:17 +0000 Subject: [Paraview] QuadView option In-Reply-To: References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> Message-ID: <53659747-2EB2-4C38-933D-E03831866C18@ornl.gov> >From what I gathered from my users, I think what?s in the Miscellaneous group should have default visibility and the rest can go to advanced. I think that?s where part of my confusion came from was that things have moved around and views have advanced panels. Error code 18, replace user and try again. Thanks for ?setting? me straight. Cheers, M On Sep 4, 2014, at 12:09 PM, Utkarsh Ayachit wrote: > Attached is the patch (will be in git/master after next gatekeeper > review). I made all the properties "default" to avoid confusion. > Michael, feel free to suggest better default visibility options. > > Thanks > Utkarsh > > On Thu, Sep 4, 2014 at 12:00 PM, Utkarsh Ayachit > wrote: >> BTW, I am pushing an update to the git repo to better organize the >> properties on the "Properties" panel for the Quad View. >> >> On Thu, Sep 4, 2014 at 11:56 AM, Utkarsh Ayachit >> wrote: >>> Alright, here's the final diagnosis :): >>> >>> It's works as Seb was saying. What I was missing that I had not >>> selected the Slices "representation". Once Slices representation is >>> chosen, the "Show outline in 3D view" option starts working. This is >>> indeed the way the view behaves in 3.98.1 as well. >>> >>> Utkarsh >>> >>> On Thu, Sep 4, 2014 at 11:38 AM, Utkarsh Ayachit >>> wrote: >>>> Can someone explain what this option is supposed to do? Even in 3.98.1 >>>> it has no effect for me, or at least I don't see anything change. >>>> >>>> On Thu, Sep 4, 2014 at 11:30 AM, Sebastien Jourdain >>>> wrote: >>>>> On my Mac from yesterday's master, the option does allow me to toggle the >>>>> outline. >>>>> I just forgot about that Slices representation... >>>>> >>>>> >>>>> On Thu, Sep 4, 2014 at 9:25 AM, Utkarsh Ayachit >>>>> wrote: >>>>>> >>>>>> I think the "Show Outline in 3D View" on the Properties panel is >>>>>> indeed the right option. The fact that it has no effect is a bug. >>>>>> >>>>>> Utkarsh >>>>>> >>>>>> On Thu, Sep 4, 2014 at 11:20 AM, Reuter, Michael A. >>>>>> wrote: >>>>>>> I?m providing a screenshot showing the option (Show Outline in 3D View) >>>>>>> that appears in the View Settings dialog box in PV 3.98.1. The dialog was >>>>>>> available from Edit/View Settings menu option. The 3D outline was effective >>>>>>> when the Slice representation is used. This also brings up another issue. >>>>>>> All the options that are in this dialog are not available either. I use the >>>>>>> Quad View in a user distributed program and some of them use these options. >>>>>>> They aren?t going to be happy when the upgrade removes them. >>>>>>> >>>>>>> M >>>>>>> >>>>>>> [cid:3662796F-3858-454F-9AF6-C956B97353FA at ornl.gov] >>>>>>> >>>>>>> >>>>>>> On Sep 4, 2014, at 10:50 AM, Sebastien Jourdain >>>>>>> > >>>>>>> wrote: >>>>>>> >>>>>>> Hi Michael, >>>>>>> >>>>>>> I don't think there is such option. >>>>>>> In fact, this must be due to the representation be set to "Outline" in >>>>>>> the toolbar. >>>>>>> If you change it to Surface of Wireframe you should not see anymore the >>>>>>> outline. >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> >>>>>>> On Thu, Sep 4, 2014 at 8:09 AM, Reuter, Michael A. >>>>>>> > wrote: >>>>>>> Hi, >>>>>>> >>>>>>> I?m looking for the option that turns off the outline in the 3D panel in >>>>>>> the Quad View in ParaView git-master. This used to be in the view settings >>>>>>> dialog, but that no longer exists and the settings dialog doesn?t seem to >>>>>>> have it unless I missed it. The Slice View has a similar option in the >>>>>>> Properties panel under Background, but nothing appears there for the Quad >>>>>>> View. >>>>>>> >>>>>>> Thanks, >>>>>>> M >>>>>>> >>>>>>> Dr. Michael Reuter >>>>>>> Scientific Data Analysis Group >>>>>>> Neutron Data Analysis and Visualization Division >>>>>>> Oak Ridge National Laboratory >>>>>>> >>>>>>> Office: 1-865-241-7216 >>>>>>> Fax: 1-865-574-6080 >>>>>>> Email: >>>>>>> reuterma at ornl.gov> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>> >>>>> > <0001-Update-default-property-visibility-and-grouping-for-.patch> From utkarsh.ayachit at kitware.com Thu Sep 4 15:09:49 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 4 Sep 2014 15:09:49 -0400 Subject: [Paraview] QuadView option In-Reply-To: <53659747-2EB2-4C38-933D-E03831866C18@ornl.gov> References: <7CABF401-AA8A-42F3-9CEE-C9EAF95F81FA@ornl.gov> <53659747-2EB2-4C38-933D-E03831866C18@ornl.gov> Message-ID: > I think what?s in the Miscellaneous group should have default visibility and the rest can go to advanced. Done. Should be fixed in git/master soon. From furutaka.kazuyoshi at jaea.go.jp Thu Sep 4 18:27:50 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Fri, 05 Sep 2014 07:27:50 +0900 (JST) Subject: [Paraview] seg.fault when reading VRML files twice In-Reply-To: <20140903.115011.281070362.furutaka.kazuyoshi@jaea.go.jp> References: <20140903.115011.281070362.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <20140905.072750.413866329.furutaka.kazuyoshi@jaea.go.jp> Updates: (v) also occurs w/ ParaView-4.2.0-RC1-Windows-32bit.exe as well as a 4.2.0-RC1 binary compiled on Fedora 20 (i386). Any suggestions? Thanks. Kazuyoshi From: Kazuyoshi Furutaka Subject: [Paraview] seg.fault when reading VRML files twice Date: Wed, 03 Sep 2014 11:50:11 +0900 (JST) > Dear ParaView experts... > > As the subject says, I'm suffering from the segmentation faluts > when reading VRML files. > > It occurs: > (i) File->Open a VRML file, display the content, > (File->Disconnect) then File->Open a VRML file and display it, > > (ii) on linux (Fedora 20, binary package: paraview-4.1.0-1.fc20.i686) > as well as on windows (Vista Business SP2, "4.1.0 32-bit", > ParaView-4.1.0-Windows-32bit.exe, downloaded from > http://www.paraview.org/download/ > > (iii) regardless of whether the second VRML file is the same as > or different from the first one, > > (iV) even with a simple VRML file as the attached one... > > It DOES NOT occur when loading/displaying multiple VRML files > in the same session (w/o disconnecting)... > > How can I avoid/fix this? > > I'll attach a trimmed backtrace obtained on linux with gdb... > > Thanks in advance. > > Kazuyoshi > -- > Kazuyoshi Furutaka > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From andy.john.parker at googlemail.com Fri Sep 5 02:33:16 2014 From: andy.john.parker at googlemail.com (Dr Andrew Parker) Date: Fri, 5 Sep 2014 07:33:16 +0100 Subject: [Paraview] Job Opportunities at Fluid Gravity Engineering Message-ID: <0F28BC61-1CCB-4125-909A-A4F3B3B32E0D@gmail.com> Dear All, I know this is not the purpose of these forums, but I wanted to take a moment to notify you of the current job opportunities available at Fluid Gravity Engineering. Please visit http://www.fluidgravity.co.uk for further details about our company and the roles that are currently available. You will also find contact details there should you wish to get in touch. Please feel free to forward this to others who may be interested. Many thanks, Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: From reuterma at ornl.gov Fri Sep 5 09:24:24 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Fri, 5 Sep 2014 13:24:24 +0000 Subject: [Paraview] Replacement for colorByArray Message-ID: Hi, I have an application that I?m trying to conform back to git-master in preparation for the version 4.2 release. In the application, I used the pqPipelineRepresentation::colorByArray function to preset the colormap array before the data is rendered. I see that this function has been removed. I did a bit of digging and tried to use the following as a replacement (signal is our default array name): pqDataRepresentation *drep = objectBuilder->createDataRepresentation(?); vtkSMPropertyHelper(drep->getProxy(), ?Representation?).Set(?Surface?); vtkSMPropertyHelper(drep->getProxy(), ?ColorArrayName?).Set(?signal?); drep->getProxy()->UpdateVTKObjects(); However, this doesn?t seem to set the correct array as the view shows Solid Color for the array when it renders. I?m either invoking things incorrectly or at the wrong time, but I don?t know what. What am I missing or is there a more appropriate alternative to this method? Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov From shawn.waldon at kitware.com Fri Sep 5 09:37:06 2014 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Fri, 5 Sep 2014 09:37:06 -0400 Subject: [Paraview] seg.fault when reading VRML files twice In-Reply-To: <20140905.072750.413866329.furutaka.kazuyoshi@jaea.go.jp> References: <20140903.115011.281070362.furutaka.kazuyoshi@jaea.go.jp> <20140905.072750.413866329.furutaka.kazuyoshi@jaea.go.jp> Message-ID: Hi Kazuyoshi, I've tracked down the segfault, which results from a bug in the VTK VRML importer class. You will get the same thing if you delete a VRML Reader and re-create it. It will affect any current build of ParaView. Fixing it is going to require restructuring that class somewhat and will take a day or two. For now, just try to avoid this particular use case if possible and I'll let you know as soon as it is fixed and merged into ParaView. -Shawn On Thu, Sep 4, 2014 at 6:27 PM, Kazuyoshi Furutaka < furutaka.kazuyoshi at jaea.go.jp> wrote: > Updates: > > (v) also occurs w/ ParaView-4.2.0-RC1-Windows-32bit.exe as well > as a 4.2.0-RC1 binary compiled on Fedora 20 (i386). > > Any suggestions? > > Thanks. > Kazuyoshi > > From: Kazuyoshi Furutaka > Subject: [Paraview] seg.fault when reading VRML files twice > Date: Wed, 03 Sep 2014 11:50:11 +0900 (JST) > > > Dear ParaView experts... > > > > As the subject says, I'm suffering from the segmentation faluts > > when reading VRML files. > > > > It occurs: > > (i) File->Open a VRML file, display the content, > > (File->Disconnect) then File->Open a VRML file and display it, > > > > (ii) on linux (Fedora 20, binary package: paraview-4.1.0-1.fc20.i686) > > as well as on windows (Vista Business SP2, "4.1.0 32-bit", > > ParaView-4.1.0-Windows-32bit.exe, downloaded from > > http://www.paraview.org/download/ > > > > (iii) regardless of whether the second VRML file is the same as > > or different from the first one, > > > > (iV) even with a simple VRML file as the attached one... > > > > It DOES NOT occur when loading/displaying multiple VRML files > > in the same session (w/o disconnecting)... > > > > How can I avoid/fix this? > > > > I'll attach a trimmed backtrace obtained on linux with gdb... > > > > Thanks in advance. > > > > Kazuyoshi > > -- > > Kazuyoshi Furutaka > > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp > -- > Kazuyoshi Furutaka > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yumin.yuan at kitware.com Fri Sep 5 09:40:34 2014 From: yumin.yuan at kitware.com (Yumin Yuan) Date: Fri, 5 Sep 2014 09:40:34 -0400 Subject: [Paraview] Replacement for colorByArray In-Reply-To: References: Message-ID: Hi Michael, Checkout out "vtkSMPVRepresentationProxy::SetScalarColoring(...)". I think that's what you are looking for. Yumin On Fri, Sep 5, 2014 at 9:24 AM, Reuter, Michael A. wrote: > Hi, > > I have an application that I?m trying to conform back to git-master in > preparation for the version 4.2 release. In the application, I used the > pqPipelineRepresentation::colorByArray function to preset the colormap > array before the data is rendered. I see that this function has been > removed. I did a bit of digging and tried to use the following as a > replacement (signal is our default array name): > > pqDataRepresentation *drep = objectBuilder->createDataRepresentation(?); > vtkSMPropertyHelper(drep->getProxy(), ?Representation?).Set(?Surface?); > vtkSMPropertyHelper(drep->getProxy(), ?ColorArrayName?).Set(?signal?); > drep->getProxy()->UpdateVTKObjects(); > > However, this doesn?t seem to set the correct array as the view shows > Solid Color for the array when it renders. I?m either invoking things > incorrectly or at the wrong time, but I don?t know what. What am I missing > or is there a more appropriate alternative to this method? > > Thanks, > M > > Dr. Michael Reuter > Scientific Data Analysis Group > Neutron Data Analysis and Visualization Division > Oak Ridge National Laboratory > > Office: 1-865-241-7216 > Fax: 1-865-574-6080 > Email: reuterma at ornl.gov > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From reuterma at ornl.gov Fri Sep 5 11:03:48 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Fri, 5 Sep 2014 15:03:48 +0000 Subject: [Paraview] Replacement for colorByArray In-Reply-To: References: Message-ID: <4ED638DE-D317-42C2-A0FC-01EB2687CAD6@ornl.gov> Hi Yumin, Thanks for the pointer as now the array is set. My next problem is that the transfer function range is (0, 1) and not the range of my array. I tried using vtkSMPVRepresentationProxy::RescaleTransferFunctionToDataRange, but ParaView gives a Could not determine array range warning. I wedged a UpdateVTKObjects() between the two calls but that didn?t help. What?s the right way to do this? As a larger issue, I?m seeing that my old (PV 3.98.1 based) application is not liking how PV 4.2 is handling things. Is there any documentation or good examples of how things should be done for 4.2? My focus is on how to programmatically do things like: source and filter creation, pipeline construction and manipulation, manage different views, color map/transfer function manipulation, camera resetting. Now is the perfect time for a bit of a rewrite, but I?d definitely like to align things to how 4.2 wants things done. Thanks, M On Sep 5, 2014, at 9:40 AM, Yumin Yuan > wrote: Hi Michael, Checkout out "vtkSMPVRepresentationProxy::SetScalarColoring(...)". I think that's what you are looking for. Yumin On Fri, Sep 5, 2014 at 9:24 AM, Reuter, Michael A. > wrote: Hi, I have an application that I?m trying to conform back to git-master in preparation for the version 4.2 release. In the application, I used the pqPipelineRepresentation::colorByArray function to preset the colormap array before the data is rendered. I see that this function has been removed. I did a bit of digging and tried to use the following as a replacement (signal is our default array name): pqDataRepresentation *drep = objectBuilder->createDataRepresentation(?); vtkSMPropertyHelper(drep->getProxy(), ?Representation?).Set(?Surface?); vtkSMPropertyHelper(drep->getProxy(), ?ColorArrayName?).Set(?signal?); drep->getProxy()->UpdateVTKObjects(); However, this doesn?t seem to set the correct array as the view shows Solid Color for the array when it renders. I?m either invoking things incorrectly or at the wrong time, but I don?t know what. What am I missing or is there a more appropriate alternative to this method? Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov> _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From jlih at masonlive.gmu.edu Fri Sep 5 10:04:39 2014 From: jlih at masonlive.gmu.edu (jlih) Date: Fri, 5 Sep 2014 14:04:39 +0000 Subject: [Paraview] Paraviewweb and Amazon EC2 instance: X display, GPU option, parallel visualization, launcher... Message-ID: <1409925879253.99854@masonlive.gmu.edu> Dear all, I have installed Paraviewweb on an Amazon EC2 GPU instance based on the installation guide at: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2. The webpages under "apps" can show up correctly. Now I am trying to install the parallel visualization. Here are a few questions I want to verify: 1. When I run pvpython on the GPU instance, I got the error message saying "bad X display..". I guess this occurs when the instance does not have a "real graphics" card and "off screen rendering" option should be used. My question is will this error affect the Paraviewweb application? 2. I have installed Paraview (not Paraviewweb) on two other instances (without GPU) which run MPI without any issues. I would like to use those two instances as a part of the parallel visualization framework. Should I install the Paraviewweb on those two instances as well? Or I just need to change the machine configuration file to include the two instances? 3. It seems GPU is needed for the instance when I configured the Paraviewweb on Amazon EC2. There is a option for NVIDIA.. But I read this document: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/os_mesa which says GPU may not be necessary. Is this applicable to Amazon EC2 instances? 4. Launcher ( http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/parallel_app). I'm not sure if I should modify the pw.session.public.fields if I am going to use the default Parallel example provided by Paraviewweb to start with. Sorry about throwing out so many questions but Paraviewweb is a very interesting application to explore. Thanks, Jing -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Fri Sep 5 12:05:39 2014 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Fri, 5 Sep 2014 10:05:39 -0600 Subject: [Paraview] Paraviewweb and Amazon EC2 instance: X display, GPU option, parallel visualization, launcher... In-Reply-To: <1409925879253.99854@masonlive.gmu.edu> References: <1409925879253.99854@masonlive.gmu.edu> Message-ID: Hi Jing, I'm responding to your questions inline. Thanks! On Fri, Sep 5, 2014 at 8:04 AM, jlih wrote: > Dear all, > > I have installed Paraviewweb on an Amazon EC2 GPU instance based on the > installation guide at: > > > http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2. > The webpages under "apps" can show up correctly. Now I am trying to install > the parallel visualization. Here are a few questions I want to verify: > > > Since the instructions you referenced describe installing a binary version, I assume that's what you did. However, those instructions assumed an instance with a graphics card, hence all the instructions specific to NVidia. If you have chosen an instance without a graphics card, you can't use the binary installation of ParaView, instead you'll need to compile ParaView yourself with support for OSMesa. > 1. When I run pvpython on the GPU instance, I got the error message > saying "bad X display..". I guess this occurs when the instance does not > have a "real graphics" card and "off screen rendering" option should be > used. My question is will this error affect the Paraviewweb application? > > > ParaViewWeb is just ParaView with Python turned on. If you get a binary version, this is already done for you. If you compile it yourself, make sure to enable Python during the configure stage. At any rate, yes, ParaViewWeb is affected the same as ParaView by not having a graphics card. > 2. I have installed Paraview (not Paraviewweb) on two other instances > (without GPU) which run MPI without any issues. I would like to use those > two instances as a part of the parallel visualization framework. Should I > install the Paraviewweb on those two instances as well? Or I just need to > change the machine configuration file to include the two instances? > > > If you installed ParaView on those two instances, and if those installations of ParaView include Python, then you're good to go. Unless they don't have graphics cards and you installed the binary version, as mentioned above. > 3. It seems GPU is needed for the instance when I configured the > Paraviewweb on Amazon EC2. There is a option for NVIDIA.. But I read this > document: > > > http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/os_mesa > which says GPU may not be necessary. Is this applicable to Amazon EC2 > instances? > > > Yep, it is. But again, you have to compile ParaView yourself. See the guide you referenced above for information on how to do that. Also there's a ParaView wiki page with information on that. > 4. Launcher ( > > > http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/parallel_app). > I'm not sure if I should modify the * pw.session.public.fields* if I am > going to use the default Parallel example provided by Paraviewweb to start > with. > > > The ParaViewWeb on EC2 documentation describes setting up the Jetty launcher, which is totally fine. In that case, you would set up a few key/vals to allow that launcher to start the server side application you're interested, the parallel visualization launcher in your case. That's all covered in the guide you linked. Then you would indeed need to make sure you add "file" to those session fields as the documentation states. On the other hand, you might want to consider using the Python launcher instead of the Jetty launcher. It comes within ParaView so you don't have another software stack to worry about, and it has all the same capabilities and more. For those reasons, we currently recommend the Python launcher over the Jetty one. You can find information about the Python launcher here . > Sorry about throwing out so many questions but Paraviewweb is a very > interesting application to explore. > > > No worries, thanks for your interest! Hopefully you now have what you need to get started. Cheers, Scott > Thanks, > > Jing > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Fri Sep 5 12:36:20 2014 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Fri, 5 Sep 2014 10:36:20 -0600 Subject: [Paraview] Paraviewweb and Amazon EC2 instance: X display, GPU option, parallel visualization, launcher... In-Reply-To: <1409934553881.91779@masonlive.gmu.edu> References: <1409925879253.99854@masonlive.gmu.edu> <1409934553881.91779@masonlive.gmu.edu> Message-ID: Hi Jing, Make sure to turn on OSMesa support too, see here or here for details. And the fastest offscreen rendering involves using Gallium llvmpipe. If you're interested in that, the first link has instructions on buidling a version of OSMesa that includes Gallium llvmpipe, as well as how to then compile ParaView to take advantage of it. Hope that helps. Cheers, Scott On Fri, Sep 5, 2014 at 10:29 AM, jlih wrote: > Hi Scott, > > Thanks for your answers and recommendations. > > > When I complied and installed Paraview on my two instances, I turned the > Python option ON but did not turn off VTK-USE-X. I will go ahead to > recompile Paraview again and check the Python launcher. > > > Thanks again. > > Jing > ------------------------------ > *From:* Scott Wittenburg > *Sent:* Friday, September 5, 2014 12:05 PM > *To:* jlih > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Paraviewweb and Amazon EC2 instance: X display, > GPU option, parallel visualization, launcher... > > Hi Jing, > > I'm responding to your questions inline. Thanks! > > > On Fri, Sep 5, 2014 at 8:04 AM, jlih wrote: > >> Dear all, >> >> I have installed Paraviewweb on an Amazon EC2 GPU instance based on the >> installation guide at: >> >> >> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2. >> The webpages under "apps" can show up correctly. Now I am trying to install >> the parallel visualization. Here are a few questions I want to verify: >> >> >> Since the instructions you referenced describe installing a binary > version, I assume that's what you did. However, those instructions assumed > an instance with a graphics card, hence all the instructions specific to > NVidia. If you have chosen an instance without a graphics card, you can't > use the binary installation of ParaView, instead you'll need to compile > ParaView yourself with support for OSMesa. > >> 1. When I run pvpython on the GPU instance, I got the error message >> saying "bad X display..". I guess this occurs when the instance does not >> have a "real graphics" card and "off screen rendering" option should be >> used. My question is will this error affect the Paraviewweb application? >> >> >> ParaViewWeb is just ParaView with Python turned on. If you get a > binary version, this is already done for you. If you compile it yourself, > make sure to enable Python during the configure stage. At any rate, yes, > ParaViewWeb is affected the same as ParaView by not having a graphics card. > >> 2. I have installed Paraview (not Paraviewweb) on two other instances >> (without GPU) which run MPI without any issues. I would like to use those >> two instances as a part of the parallel visualization framework. Should I >> install the Paraviewweb on those two instances as well? Or I just need to >> change the machine configuration file to include the two instances? >> >> >> If you installed ParaView on those two instances, and if those > installations of ParaView include Python, then you're good to go. Unless > they don't have graphics cards and you installed the binary version, as > mentioned above. > >> 3. It seems GPU is needed for the instance when I configured the >> Paraviewweb on Amazon EC2. There is a option for NVIDIA.. But I read this >> document: >> >> >> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/os_mesa >> which says GPU may not be necessary. Is this applicable to Amazon EC2 >> instances? >> >> >> Yep, it is. But again, you have to compile ParaView yourself. See > the guide you referenced above for information on how to do that. Also > there's a ParaView wiki page > with information on > that. > >> 4. Launcher ( >> >> >> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/parallel_app). >> I'm not sure if I should modify the * pw.session.public.fields* if I am >> going to use the default Parallel example provided by Paraviewweb to start >> with. >> >> >> The ParaViewWeb on EC2 documentation describes setting up the Jetty > launcher, which is totally fine. In that case, you would set up a few > key/vals to allow that launcher to start the server side application you're > interested, the parallel visualization launcher in your case. That's all > covered in the guide you linked. Then you would indeed need to make sure > you add "file" to those session fields as the documentation states. > > On the other hand, you might want to consider using the Python launcher > instead of the Jetty launcher. It comes within ParaView so you don't have > another software stack to worry about, and it has all the same capabilities > and more. For those reasons, we currently recommend the Python launcher > over the Jetty one. You can find information about the Python launcher > here > > . > >> Sorry about throwing out so many questions but Paraviewweb is a very >> interesting application to explore. >> >> >> No worries, thanks for your interest! Hopefully you now have what you > need to get started. > > Cheers, > Scott > >> Thanks, >> >> Jing >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlih at masonlive.gmu.edu Fri Sep 5 12:29:14 2014 From: jlih at masonlive.gmu.edu (jlih) Date: Fri, 5 Sep 2014 16:29:14 +0000 Subject: [Paraview] Paraviewweb and Amazon EC2 instance: X display, GPU option, parallel visualization, launcher... In-Reply-To: References: <1409925879253.99854@masonlive.gmu.edu>, Message-ID: <1409934553881.91779@masonlive.gmu.edu> Hi Scott, Thanks for your answers and recommendations. When I complied and installed Paraview on my two instances, I turned the Python option ON but did not turn off VTK-USE-X. I will go ahead to recompile Paraview again and check the Python launcher. Thanks again. Jing ________________________________ From: Scott Wittenburg Sent: Friday, September 5, 2014 12:05 PM To: jlih Cc: paraview at paraview.org Subject: Re: [Paraview] Paraviewweb and Amazon EC2 instance: X display, GPU option, parallel visualization, launcher... Hi Jing, I'm responding to your questions inline. Thanks! On Fri, Sep 5, 2014 at 8:04 AM, jlih > wrote: Dear all, I have installed Paraviewweb on an Amazon EC2 GPU instance based on the installation guide at: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2. The webpages under "apps" can show up correctly. Now I am trying to install the parallel visualization. Here are a few questions I want to verify: Since the instructions you referenced describe installing a binary version, I assume that's what you did. However, those instructions assumed an instance with a graphics card, hence all the instructions specific to NVidia. If you have chosen an instance without a graphics card, you can't use the binary installation of ParaView, instead you'll need to compile ParaView yourself with support for OSMesa. 1. When I run pvpython on the GPU instance, I got the error message saying "bad X display..". I guess this occurs when the instance does not have a "real graphics" card and "off screen rendering" option should be used. My question is will this error affect the Paraviewweb application? ParaViewWeb is just ParaView with Python turned on. If you get a binary version, this is already done for you. If you compile it yourself, make sure to enable Python during the configure stage. At any rate, yes, ParaViewWeb is affected the same as ParaView by not having a graphics card. 2. I have installed Paraview (not Paraviewweb) on two other instances (without GPU) which run MPI without any issues. I would like to use those two instances as a part of the parallel visualization framework. Should I install the Paraviewweb on those two instances as well? Or I just need to change the machine configuration file to include the two instances? If you installed ParaView on those two instances, and if those installations of ParaView include Python, then you're good to go. Unless they don't have graphics cards and you installed the binary version, as mentioned above. 3. It seems GPU is needed for the instance when I configured the Paraviewweb on Amazon EC2. There is a option for NVIDIA.. But I read this document: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/os_mesa which says GPU may not be necessary. Is this applicable to Amazon EC2 instances? Yep, it is. But again, you have to compile ParaView yourself. See the guide you referenced above for information on how to do that. Also there's a ParaView wiki page with information on that. 4. Launcher ( http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/parallel_app). I'm not sure if I should modify the pw.session.public.fields if I am going to use the default Parallel example provided by Paraviewweb to start with. The ParaViewWeb on EC2 documentation describes setting up the Jetty launcher, which is totally fine. In that case, you would set up a few key/vals to allow that launcher to start the server side application you're interested, the parallel visualization launcher in your case. That's all covered in the guide you linked. Then you would indeed need to make sure you add "file" to those session fields as the documentation states. On the other hand, you might want to consider using the Python launcher instead of the Jetty launcher. It comes within ParaView so you don't have another software stack to worry about, and it has all the same capabilities and more. For those reasons, we currently recommend the Python launcher over the Jetty one. You can find information about the Python launcher here. Sorry about throwing out so many questions but Paraviewweb is a very interesting application to explore. No worries, thanks for your interest! Hopefully you now have what you need to get started. Cheers, Scott Thanks, Jing _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From reuterma at ornl.gov Fri Sep 5 16:29:13 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Fri, 5 Sep 2014 20:29:13 +0000 Subject: [Paraview] Superbuild and Windows In-Reply-To: References: Message-ID: <6E8F6C07-4BA8-4575-B404-16ABCD63CE63@ornl.gov> I switched to Ninja and shortened up the paths, but what really got things working was passing the VTK_USE_SYSTEM_PYGMENTS down to the ParaView CMake config via the PV_EXTRA_CMAKE_ARGS. After that, the build went smoothly. I hit a snag on creating the package because I?m triggering the USE_SYSTEM_matplotlib option and the Projects/win32/paraview.bundle.cmake does not trap the copying of matplotlib related items when this flag is used. I see a similar issue in the Projects/apple/paraview.bundle.cmake file as well. I added a AND NOT USE_SYSTEM_matplotlib to the if (matplotlib_ENABLED) line and that fixed the generated cmake_install.cmake file and the package created fine. I?ve tested the resulting package and so far so good. M On Sep 3, 2014, at 10:24 AM, Utkarsh Ayachit > wrote: Michael, Are you using VS generator? Can you switch to using Ninja? You can still use the MSVC compilers. The error is popping up when the build is trying to compiler the pygments *.py files. You'll get the same error later when it's trying to compile the ParaView *.py files. Also, another thing to note is that Windows has issues with long paths. So I'd suggest moving the superbuild source and build directories to something lower to avoid those e.g. C:/tmp/pvs-src and C:/tmp/pvs-build. Finally, if you're using VS2012, you'll need to use a system Python. Currently. the Python included in the superbuild is intended for VS2008. Also VS2012, is currently untested. As a first pass, if possible, I'd suggest using VS 2008. Once that's working, you can give VS2012 try. Hopefully, it should work (except the Python caveat), but I am always wary of VS version differences. Utkarsh On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. > wrote: Hi, I?m having an issue with the ParaView Superbuild on Windows (VS2012). I get this error during the build process: 322> Compiling Python package 'pygments' 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\filters ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\formatters ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\lexers ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\styles ... 322> ImportError: No module named site 9>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): error MSB6006: "cmd.exe" exited with code 1. [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] 322> 322>Build FAILED. However, the site module exists when I run python. I?m building from a script so I can control the environment. Everything else seems to build just fine. However, nothing appears in the install directory for cpack to find. I can?t tell if this build error is disrupting the process or something else is going wrong. What controls the pygments build so I can shut it off for now? Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Fri Sep 5 16:32:25 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 5 Sep 2014 16:32:25 -0400 Subject: [Paraview] Superbuild and Windows In-Reply-To: <6E8F6C07-4BA8-4575-B404-16ABCD63CE63@ornl.gov> References: <6E8F6C07-4BA8-4575-B404-16ABCD63CE63@ornl.gov> Message-ID: Great! Which VS was this? The Pygments thing should be tracked down. I'll see what's happening there. BTW, I am making progress on Mavericks build. I think I have most things ironed out. I'll send an updated email once I have dashboard testing it. Utkarsh On Fri, Sep 5, 2014 at 4:29 PM, Reuter, Michael A. wrote: > I switched to Ninja and shortened up the paths, but what really got things working was passing the VTK_USE_SYSTEM_PYGMENTS down to the ParaView CMake config via the PV_EXTRA_CMAKE_ARGS. After that, the build went smoothly. I hit a snag on creating the package because I?m triggering the USE_SYSTEM_matplotlib option and the Projects/win32/paraview.bundle.cmake does not trap the copying of matplotlib related items when this flag is used. I see a similar issue in the Projects/apple/paraview.bundle.cmake file as well. I added a AND NOT USE_SYSTEM_matplotlib to the if (matplotlib_ENABLED) line and that fixed the generated cmake_install.cmake file and the package created fine. I?ve tested the resulting package and so far so good. > > M > > > On Sep 3, 2014, at 10:24 AM, Utkarsh Ayachit > wrote: > > Michael, > > Are you using VS generator? Can you switch to using Ninja? You can > still use the MSVC compilers. The error is popping up when the build > is trying to compiler the pygments *.py files. You'll get the same > error later when it's trying to compile the ParaView *.py files. > > Also, another thing to note is that Windows has issues with long > paths. So I'd suggest moving the superbuild source and build > directories to something lower to avoid those e.g. C:/tmp/pvs-src and > C:/tmp/pvs-build. > > Finally, if you're using VS2012, you'll need to use a system Python. > Currently. the Python included in the superbuild is intended for > VS2008. Also VS2012, is currently untested. As a first pass, if > possible, I'd suggest using VS 2008. Once that's working, you can give > VS2012 try. Hopefully, it should work (except the Python caveat), but > I am always wary of VS version differences. > > Utkarsh > > > > On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. > wrote: > Hi, > > > > I?m having an issue with the ParaView Superbuild on Windows > (VS2012). I get this error during the build process: > > > > 322> Compiling Python package 'pygments' > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\filters > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\formatters > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\lexers > ... > > > > 322> Listing > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\styles > ... > > > > 322> ImportError: No module named site > > > > 9>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): > error MSB6006: "cmd.exe" exited with code 1. > [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] > > > > 322> > > 322>Build FAILED. > > > > However, the site module exists when I run python. I?m building from a > script so I can control the environment. Everything else seems to build just > fine. However, nothing appears in the install directory for cpack to find. I > can?t tell if this build error is disrupting the process or something else > is going wrong. What controls the pygments build so I can shut it off for > now? > > > > Thanks, > > M > > > > Dr. Michael Reuter > > Scientific Data Analysis Group > > Neutron Data Analysis and Visualization Division > > Oak Ridge National Laboratory > > > > Office: 1-865-241-7216 > > Fax: 1-865-574-6080 > > Email: reuterma at ornl.gov > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > From yumin.yuan at kitware.com Fri Sep 5 16:44:31 2014 From: yumin.yuan at kitware.com (Yumin Yuan) Date: Fri, 5 Sep 2014 16:44:31 -0400 Subject: [Paraview] Replacement for colorByArray In-Reply-To: <4ED638DE-D317-42C2-A0FC-01EB2687CAD6@ornl.gov> References: <4ED638DE-D317-42C2-A0FC-01EB2687CAD6@ornl.gov> Message-ID: Hi Michael, Please see inline comments below, On Fri, Sep 5, 2014 at 11:03 AM, Reuter, Michael A. wrote: > Hi Yumin, > > Thanks for the pointer as now the array is set. My next problem is that > the transfer function range is (0, 1) and not the range of my array. I > tried using vtkSMPVRepresentationProxy::RescaleTransferFunctionToDataRange, > but ParaView gives a Could not determine array range warning. I wedged a > UpdateVTKObjects() between the two calls but that didn?t help. What?s the > right way to do this? > > Try adding UpdatePipeline() after UpdateVTKObjects() before calling RescaleTransferFunctionToDataRange(). The UpdatePipeline() will force the pipeline to update so that the array information is set up properly. > As a larger issue, I?m seeing that my old (PV 3.98.1 based) application is > not liking how PV 4.2 is handling things. Is there any documentation or > good examples of how things should be done for 4.2? My focus is on how to > programmatically do things like: source and filter creation, pipeline > construction and manipulation, manage different views, color map/transfer > function manipulation, camera resetting. Now is the perfect time for a bit > of a rewrite, but I?d definitely like to align things to how 4.2 wants > things done. > > AFAIK, there is no such document available (yet). However, we do have a primary list that could be useful to people trying to convert pv-3.98 based applications to pv-4.2. We (Utkarsh and I) are still working on this list, and will put it up on the wiki once it is formalized a bit more. Yumin -------------- next part -------------- An HTML attachment was scrubbed... URL: From reuterma at ornl.gov Fri Sep 5 16:58:32 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Fri, 5 Sep 2014 20:58:32 +0000 Subject: [Paraview] Superbuild and Windows In-Reply-To: References: <6E8F6C07-4BA8-4575-B404-16ABCD63CE63@ornl.gov> Message-ID: I?m working with VS2012. Thanks for the update on Mavericks. M On Sep 5, 2014, at 4:32 PM, Utkarsh Ayachit wrote: > Great! Which VS was this? The Pygments thing should be tracked down. > I'll see what's happening there. BTW, I am making progress on > Mavericks build. I think I have most things ironed out. I'll send an > updated email once I have dashboard testing it. > > Utkarsh > > On Fri, Sep 5, 2014 at 4:29 PM, Reuter, Michael A. wrote: >> I switched to Ninja and shortened up the paths, but what really got things working was passing the VTK_USE_SYSTEM_PYGMENTS down to the ParaView CMake config via the PV_EXTRA_CMAKE_ARGS. After that, the build went smoothly. I hit a snag on creating the package because I?m triggering the USE_SYSTEM_matplotlib option and the Projects/win32/paraview.bundle.cmake does not trap the copying of matplotlib related items when this flag is used. I see a similar issue in the Projects/apple/paraview.bundle.cmake file as well. I added a AND NOT USE_SYSTEM_matplotlib to the if (matplotlib_ENABLED) line and that fixed the generated cmake_install.cmake file and the package created fine. I?ve tested the resulting package and so far so good. >> >> M >> >> >> On Sep 3, 2014, at 10:24 AM, Utkarsh Ayachit > wrote: >> >> Michael, >> >> Are you using VS generator? Can you switch to using Ninja? You can >> still use the MSVC compilers. The error is popping up when the build >> is trying to compiler the pygments *.py files. You'll get the same >> error later when it's trying to compile the ParaView *.py files. >> >> Also, another thing to note is that Windows has issues with long >> paths. So I'd suggest moving the superbuild source and build >> directories to something lower to avoid those e.g. C:/tmp/pvs-src and >> C:/tmp/pvs-build. >> >> Finally, if you're using VS2012, you'll need to use a system Python. >> Currently. the Python included in the superbuild is intended for >> VS2008. Also VS2012, is currently untested. As a first pass, if >> possible, I'd suggest using VS 2008. Once that's working, you can give >> VS2012 try. Hopefully, it should work (except the Python caveat), but >> I am always wary of VS version differences. >> >> Utkarsh >> >> >> >> On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. > wrote: >> Hi, >> >> >> >> I?m having an issue with the ParaView Superbuild on Windows >> (VS2012). I get this error during the build process: >> >> >> >> 322> Compiling Python package 'pygments' >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\filters >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\formatters >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\lexers >> ... >> >> >> >> 322> Listing >> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\styles >> ... >> >> >> >> 322> ImportError: No module named site >> >> >> >> 9>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): >> error MSB6006: "cmd.exe" exited with code 1. >> [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] >> >> >> >> 322> >> >> 322>Build FAILED. >> >> >> >> However, the site module exists when I run python. I?m building from a >> script so I can control the environment. Everything else seems to build just >> fine. However, nothing appears in the install directory for cpack to find. I >> can?t tell if this build error is disrupting the process or something else >> is going wrong. What controls the pygments build so I can shut it off for >> now? >> >> >> >> Thanks, >> >> M >> >> >> >> Dr. Michael Reuter >> >> Scientific Data Analysis Group >> >> Neutron Data Analysis and Visualization Division >> >> Oak Ridge National Laboratory >> >> >> >> Office: 1-865-241-7216 >> >> Fax: 1-865-574-6080 >> >> Email: reuterma at ornl.gov >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> From scott.wittenburg at kitware.com Fri Sep 5 16:57:52 2014 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Fri, 5 Sep 2014 14:57:52 -0600 Subject: [Paraview] Paraviewweb and Amazon EC2 instance: X display, GPU option, parallel visualization, launcher... In-Reply-To: <1409949596825.31467@masonlive.gmu.edu> References: <1409925879253.99854@masonlive.gmu.edu> <1409934553881.91779@masonlive.gmu.edu> <1409949596825.31467@masonlive.gmu.edu> Message-ID: Hi Jing, I have copied the paraview list here so that everyone can benefit from the conversation. So don't worry, it's not a silly question. I don't think it's totally clear in the documentation, as there are several places where 'host' shows up as a key. There's one 'host' in the 'resources' section, and there's another in the 'configuration' section, and those should be fine left as localhost in your situation. The one you probably need to worry about is the one that is embedded in the 'sessionURL', as this is what clients will use to connect through to the visualization process. That hostname (in the 'sessionURL') should be changed to the public DNS of the Amazon instance (or the IP could work fine too I guess). However, you mentioned you have installed Apache, so I guess you're going to use that as a front end? Then you want to make sure you create your Apache VirtualHost and set the sessionURL as you find them in this guide , because Apache is going to intercept those session urls which contain the unique key from the launcher and re-write them so they get to the correct port where the visualization process is listening. I'm currently overhauling some of those ParaViewWeb guiedes, so I'll try to make sure that stuff is clearer. Cheers, Scott On Fri, Sep 5, 2014 at 2:39 PM, jlih wrote: > Hi Scott, > > Thanks for the additional info. I have complied Paraview with OSMesa > support and installed Apache. > > > Now I have one more silly question about the Python launcher. In the > "config.json", 'localhost' is used as an example for 'host'. If I'm going > to have a 'real deployment' with Apache, should I revise the host to use > the IP of the Amazon instance? > > > Thanks, > > Jing > > > ------------------------------ > *From:* Scott Wittenburg > *Sent:* Friday, September 5, 2014 12:36 PM > > *To:* jlih > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Paraviewweb and Amazon EC2 instance: X display, > GPU option, parallel visualization, launcher... > > Hi Jing, > > Make sure to turn on OSMesa support too, see here > > or here for details. > And the fastest offscreen rendering involves using Gallium llvmpipe. If > you're interested in that, the first link has instructions on buidling a > version of OSMesa that includes Gallium llvmpipe, as well as how to then > compile ParaView to take advantage of it. > > Hope that helps. > > Cheers, > Scott > > > > On Fri, Sep 5, 2014 at 10:29 AM, jlih wrote: > >> Hi Scott, >> >> Thanks for your answers and recommendations. >> >> >> When I complied and installed Paraview on my two instances, I turned >> the Python option ON but did not turn off VTK-USE-X. I will go ahead to >> recompile Paraview again and check the Python launcher. >> >> >> Thanks again. >> >> Jing >> ------------------------------ >> *From:* Scott Wittenburg >> *Sent:* Friday, September 5, 2014 12:05 PM >> *To:* jlih >> *Cc:* paraview at paraview.org >> *Subject:* Re: [Paraview] Paraviewweb and Amazon EC2 instance: X >> display, GPU option, parallel visualization, launcher... >> >> Hi Jing, >> >> I'm responding to your questions inline. Thanks! >> >> >> On Fri, Sep 5, 2014 at 8:04 AM, jlih wrote: >> >>> Dear all, >>> >>> I have installed Paraviewweb on an Amazon EC2 GPU instance based on the >>> installation guide at: >>> >>> >>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2. >>> The webpages under "apps" can show up correctly. Now I am trying to install >>> the parallel visualization. Here are a few questions I want to verify: >>> >>> >>> Since the instructions you referenced describe installing a binary >> version, I assume that's what you did. However, those instructions assumed >> an instance with a graphics card, hence all the instructions specific to >> NVidia. If you have chosen an instance without a graphics card, you can't >> use the binary installation of ParaView, instead you'll need to compile >> ParaView yourself with support for OSMesa. >> >>> 1. When I run pvpython on the GPU instance, I got the error message >>> saying "bad X display..". I guess this occurs when the instance does not >>> have a "real graphics" card and "off screen rendering" option should be >>> used. My question is will this error affect the Paraviewweb application? >>> >>> >>> ParaViewWeb is just ParaView with Python turned on. If you get a >> binary version, this is already done for you. If you compile it yourself, >> make sure to enable Python during the configure stage. At any rate, yes, >> ParaViewWeb is affected the same as ParaView by not having a graphics card. >> >>> 2. I have installed Paraview (not Paraviewweb) on two other instances >>> (without GPU) which run MPI without any issues. I would like to use those >>> two instances as a part of the parallel visualization framework. Should I >>> install the Paraviewweb on those two instances as well? Or I just need to >>> change the machine configuration file to include the two instances? >>> >>> >>> If you installed ParaView on those two instances, and if those >> installations of ParaView include Python, then you're good to go. Unless >> they don't have graphics cards and you installed the binary version, as >> mentioned above. >> >>> 3. It seems GPU is needed for the instance when I configured the >>> Paraviewweb on Amazon EC2. There is a option for NVIDIA.. But I read this >>> document: >>> >>> >>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/os_mesa >>> which says GPU may not be necessary. Is this applicable to Amazon EC2 >>> instances? >>> >>> >>> Yep, it is. But again, you have to compile ParaView yourself. See >> the guide you referenced above for information on how to do that. Also >> there's a ParaView wiki page >> with information on >> that. >> >>> 4. Launcher ( >>> >>> >>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/parallel_app). >>> I'm not sure if I should modify the * pw.session.public.fields* if I am >>> going to use the default Parallel example provided by Paraviewweb to start >>> with. >>> >>> >>> The ParaViewWeb on EC2 documentation describes setting up the Jetty >> launcher, which is totally fine. In that case, you would set up a few >> key/vals to allow that launcher to start the server side application you're >> interested, the parallel visualization launcher in your case. That's all >> covered in the guide you linked. Then you would indeed need to make sure >> you add "file" to those session fields as the documentation states. >> >> On the other hand, you might want to consider using the Python launcher >> instead of the Jetty launcher. It comes within ParaView so you don't have >> another software stack to worry about, and it has all the same capabilities >> and more. For those reasons, we currently recommend the Python launcher >> over the Jetty one. You can find information about the Python launcher >> here >> >> . >> >>> Sorry about throwing out so many questions but Paraviewweb is a very >>> interesting application to explore. >>> >>> >>> No worries, thanks for your interest! Hopefully you now have what >> you need to get started. >> >> Cheers, >> Scott >> >>> Thanks, >>> >>> Jing >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonardopessanha74 at gmail.com Fri Sep 5 17:47:19 2014 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Fri, 5 Sep 2014 18:47:19 -0300 Subject: [Paraview] Object following CSV file series points path Message-ID: Hi, I have a series of CSV files that describes a path I am able to see the path animated as points I want to put an object that i modelled following this path How can i do that? Att, Leonardo Pessanha -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlih at masonlive.gmu.edu Fri Sep 5 18:14:21 2014 From: jlih at masonlive.gmu.edu (jlih) Date: Fri, 5 Sep 2014 22:14:21 +0000 Subject: [Paraview] Paraviewweb and Amazon EC2 instance: X display, GPU option, parallel visualization, launcher... In-Reply-To: References: <1409925879253.99854@masonlive.gmu.edu> <1409934553881.91779@masonlive.gmu.edu> <1409949596825.31467@masonlive.gmu.edu>, Message-ID: <1409955260908.66203@masonlive.gmu.edu> Hi Scott, Thanks for your clarification. Yes. I am using Apache as the front end. The link you included is very helpful! Best, Jing ________________________________ From: Scott Wittenburg Sent: Friday, September 5, 2014 4:57 PM To: jlih; paraview at paraview.org Subject: Re: [Paraview] Paraviewweb and Amazon EC2 instance: X display, GPU option, parallel visualization, launcher... Hi Jing, I have copied the paraview list here so that everyone can benefit from the conversation. So don't worry, it's not a silly question. I don't think it's totally clear in the documentation, as there are several places where 'host' shows up as a key. There's one 'host' in the 'resources' section, and there's another in the 'configuration' section, and those should be fine left as localhost in your situation. The one you probably need to worry about is the one that is embedded in the 'sessionURL', as this is what clients will use to connect through to the visualization process. That hostname (in the 'sessionURL') should be changed to the public DNS of the Amazon instance (or the IP could work fine too I guess). However, you mentioned you have installed Apache, so I guess you're going to use that as a front end? Then you want to make sure you create your Apache VirtualHost and set the sessionURL as you find them in this guide, because Apache is going to intercept those session urls which contain the unique key from the launcher and re-write them so they get to the correct port where the visualization process is listening. I'm currently overhauling some of those ParaViewWeb guiedes, so I'll try to make sure that stuff is clearer. Cheers, Scott On Fri, Sep 5, 2014 at 2:39 PM, jlih > wrote: Hi Scott, Thanks for the additional info. I have complied Paraview with OSMesa support and installed Apache. Now I have one more silly question about the Python launcher. In the "config.json", 'localhost' is used as an example for 'host'. If I'm going to have a 'real deployment' with Apache, should I revise the host to use the IP of the Amazon instance? Thanks, Jing ________________________________ From: Scott Wittenburg > Sent: Friday, September 5, 2014 12:36 PM To: jlih Cc: paraview at paraview.org Subject: Re: [Paraview] Paraviewweb and Amazon EC2 instance: X display, GPU option, parallel visualization, launcher... Hi Jing, Make sure to turn on OSMesa support too, see here or here for details. And the fastest offscreen rendering involves using Gallium llvmpipe. If you're interested in that, the first link has instructions on buidling a version of OSMesa that includes Gallium llvmpipe, as well as how to then compile ParaView to take advantage of it. Hope that helps. Cheers, Scott On Fri, Sep 5, 2014 at 10:29 AM, jlih > wrote: Hi Scott, Thanks for your answers and recommendations. When I complied and installed Paraview on my two instances, I turned the Python option ON but did not turn off VTK-USE-X. I will go ahead to recompile Paraview again and check the Python launcher. Thanks again. Jing ________________________________ From: Scott Wittenburg > Sent: Friday, September 5, 2014 12:05 PM To: jlih Cc: paraview at paraview.org Subject: Re: [Paraview] Paraviewweb and Amazon EC2 instance: X display, GPU option, parallel visualization, launcher... Hi Jing, I'm responding to your questions inline. Thanks! On Fri, Sep 5, 2014 at 8:04 AM, jlih > wrote: Dear all, I have installed Paraviewweb on an Amazon EC2 GPU instance based on the installation guide at: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2. The webpages under "apps" can show up correctly. Now I am trying to install the parallel visualization. Here are a few questions I want to verify: Since the instructions you referenced describe installing a binary version, I assume that's what you did. However, those instructions assumed an instance with a graphics card, hence all the instructions specific to NVidia. If you have chosen an instance without a graphics card, you can't use the binary installation of ParaView, instead you'll need to compile ParaView yourself with support for OSMesa. 1. When I run pvpython on the GPU instance, I got the error message saying "bad X display..". I guess this occurs when the instance does not have a "real graphics" card and "off screen rendering" option should be used. My question is will this error affect the Paraviewweb application? ParaViewWeb is just ParaView with Python turned on. If you get a binary version, this is already done for you. If you compile it yourself, make sure to enable Python during the configure stage. At any rate, yes, ParaViewWeb is affected the same as ParaView by not having a graphics card. 2. I have installed Paraview (not Paraviewweb) on two other instances (without GPU) which run MPI without any issues. I would like to use those two instances as a part of the parallel visualization framework. Should I install the Paraviewweb on those two instances as well? Or I just need to change the machine configuration file to include the two instances? If you installed ParaView on those two instances, and if those installations of ParaView include Python, then you're good to go. Unless they don't have graphics cards and you installed the binary version, as mentioned above. 3. It seems GPU is needed for the instance when I configured the Paraviewweb on Amazon EC2. There is a option for NVIDIA.. But I read this document: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/os_mesa which says GPU may not be necessary. Is this applicable to Amazon EC2 instances? Yep, it is. But again, you have to compile ParaView yourself. See the guide you referenced above for information on how to do that. Also there's a ParaView wiki page with information on that. 4. Launcher ( http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/parallel_app). I'm not sure if I should modify the pw.session.public.fields if I am going to use the default Parallel example provided by Paraviewweb to start with. The ParaViewWeb on EC2 documentation describes setting up the Jetty launcher, which is totally fine. In that case, you would set up a few key/vals to allow that launcher to start the server side application you're interested, the parallel visualization launcher in your case. That's all covered in the guide you linked. Then you would indeed need to make sure you add "file" to those session fields as the documentation states. On the other hand, you might want to consider using the Python launcher instead of the Jetty launcher. It comes within ParaView so you don't have another software stack to worry about, and it has all the same capabilities and more. For those reasons, we currently recommend the Python launcher over the Jetty one. You can find information about the Python launcher here. Sorry about throwing out so many questions but Paraviewweb is a very interesting application to explore. No worries, thanks for your interest! Hopefully you now have what you need to get started. Cheers, Scott Thanks, Jing _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From f_magician at mac.com Sat Sep 6 06:25:17 2014 From: f_magician at mac.com (Magician) Date: Sat, 06 Sep 2014 19:25:17 +0900 Subject: [Paraview] Save Stereo Screenshots with Python Message-ID: Hi all, I want to export screenshots of stereo images with Python. The stereo mode is SplitViewportHorizontal (Side-by-Side). When I export images larger than active views, I get bad results as the attached image. How can I export large stereo screenshots correctly? Or I?m planning to export left and right-eye images separately, and composite them with other softwares. How can I export left or right-eye images with Python? Magician -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test_stereo.png Type: image/png Size: 176295 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Sun Sep 7 13:58:27 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 7 Sep 2014 13:58:27 -0400 Subject: [Paraview] Superbuild and OSX In-Reply-To: References: Message-ID: Alright, Superbuild + Mavericks is now working as expected. It's now tested on the dashboards too: http://open.cdash.org/buildSummary.php?buildid=3479885 If looking for options to turn on, here's a good start: http://open.cdash.org/viewNotes.php?buildid=3479885 Utkarsh On Thu, Sep 4, 2014 at 9:22 AM, Utkarsh Ayachit wrote: > Sorry, I did mean Mavericks :)..I can never keep the MacOS names straight. > > On Thu, Sep 4, 2014 at 8:00 AM, Reuter, Michael A. wrote: >> Thanks for the update. I?m actually building on Mavericks, but our project is still supporting Mountain Lion so it will be good to have it work there. >> >> M >> >> >> On Sep 3, 2014, at 11:57 PM, Utkarsh Ayachit > wrote: >> >> Michael, >> >> Hold off on using the superbuild on MountainLion for now. I'll track >> the issues down and then let you know. >> >> >> Utkarsh >> >> On Wed, Sep 3, 2014 at 6:23 PM, Utkarsh Ayachit >> > wrote: >> Michael, >> >> Let me try this on a Moutain Lion myself and I'll let you know. What >> projects are you turning on in your build? >> >> Utkarsh >> >> On Wed, Sep 3, 2014 at 2:40 PM, Reuter, Michael A. > wrote: >> This gets around the clang argument problem, but the ParaView CMake configuration step still fails for an unknown reason. >> >> M >> >> On Sep 3, 2014, at 10:28 AM, Utkarsh Ayachit > wrote: >> >> Cherry-pick this fix for now : http://review.source.kitware.com/#/c/16665/ >> It'll go into master soon. >> >> Ben, anything this fix is waiting on? >> >> Utkarsh >> >> On Wed, Sep 3, 2014 at 9:42 AM, Reuter, Michael A. > wrote: >> Hi, >> >> I?m having trouble getting the git-master version of the Superbuild running on OSX (10.9) with clang (5.1). Setting the CMAKE_OSX_SYSROOT variable causes the following error during CMake (2.8.12.2) generation for the ParaView subproject: >> >> -- The C compiler identification is unknown >> -- The CXX compiler identification is unknown >> -- Check for working C compiler using: Ninja >> -- Check for working C compiler using: Ninja -- broken >> CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): >> The C compiler "/usr/bin/cc" is not able to compile a simple test program. >> >> It fails with the following output: >> >> Change Dir: /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp >> >> Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075 >> >> [1/2] Building C object >> CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o >> >> FAILED: /usr/bin/cc -fPIC -arch x86_64 -mmacosx-version-min=10.9 >> -sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk >> -o CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o -c >> testCCompiler.c >> >> clang: error: unknown argument: >> '-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' >> [-Wunused-command-line-argument-hard-error-in-future] >> >> clang: note: this will be a hard error (cannot be downgraded to a warning) >> in the future >> >> ninja: build stopped: subcommand failed. >> >> Even if I empty the CMAKE_OSX_SYSROOT variable, the system still tries to pass an empty -sysroot flag to clang causing it to choke. I removed the sysroot flag from the top-level CMakeLists.txt, but then the ParaView CMake setup fails for a reason I can?t seem to understand. I?m attaching the log showing the CMake output. The only obvious thing I see is the Fortran compiler. Is that required? >> >> Thanks, >> M >> >> Dr. Michael Reuter >> Scientific Data Analysis Group >> Neutron Data Analysis and Visualization Division >> Oak Ridge National Laboratory >> >> Office: 1-865-241-7216 >> Fax: 1-865-574-6080 >> Email: reuterma at ornl.gov >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> From joachim.pouderoux at kitware.com Mon Sep 8 08:42:34 2014 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Mon, 8 Sep 2014 14:42:34 +0200 Subject: [Paraview] ANN: ParaView Training Course in Paris, France, October 14-15, 2014 Message-ID: Hello, Kitware will be holding a 2-day ParaView course on October 14 and 15th, 2014 at Universit? Pierre et Marie Curie, Paris, France. The specificity of this training is that it will take place in a virtual reality room fitted with a powerwall. Please visit our web site for more information and registration details at either: http://training.kitware.fr/browse/71 (in English) or http://formations.kitware.fr/browse/71 (in French) Note that the course might be taught in English. If you have any question, please contact us at formations at http://www.kitware.fr Thank you, *Joachim Pouderoux* *PhD, Technical Expert* *Kitware SAS * -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Mon Sep 8 10:30:47 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 8 Sep 2014 14:30:47 +0000 Subject: [Paraview] Object following CSV file series points path In-Reply-To: Message-ID: You can use the Glyph With Custom Source filter. This filter works like the standard Glyph filter but it allows you to input an arbitrary polydata to center on each point rather a predefined shape. -Ken From: L?o Pessanha > Date: Friday, September 5, 2014 3:47 PM To: ParaView list > Subject: [EXTERNAL] [Paraview] Object following CSV file series points path Hi, I have a series of CSV files that describes a path I am able to see the path animated as points I want to put an object that i modelled following this path How can i do that? Att, Leonardo Pessanha -------------- next part -------------- An HTML attachment was scrubbed... URL: From reuterma at ornl.gov Mon Sep 8 11:15:35 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Mon, 8 Sep 2014 15:15:35 +0000 Subject: [Paraview] Superbuild and OSX In-Reply-To: References: Message-ID: <8BF5A961-B485-4E06-B2A0-08CCE4CDF660@ornl.gov> After updating the Superbuild code and cleaning house, I was still seeing the ParaView CMake configure failure I reported before. I did a bit of digging and found that the generated pv-paraview-build.cmake was trying to execute the following command: step_command-NOTFOUND. It seems to be related to trying to use ninja instead of make files. I switched to make files and the build is in progress. Thanks, M On Sep 7, 2014, at 1:58 PM, Utkarsh Ayachit > wrote: Alright, Superbuild + Mavericks is now working as expected. It's now tested on the dashboards too: http://open.cdash.org/buildSummary.php?buildid=3479885 If looking for options to turn on, here's a good start: http://open.cdash.org/viewNotes.php?buildid=3479885 Utkarsh On Thu, Sep 4, 2014 at 9:22 AM, Utkarsh Ayachit wrote: Sorry, I did mean Mavericks :)..I can never keep the MacOS names straight. On Thu, Sep 4, 2014 at 8:00 AM, Reuter, Michael A. wrote: Thanks for the update. I?m actually building on Mavericks, but our project is still supporting Mountain Lion so it will be good to have it work there. M On Sep 3, 2014, at 11:57 PM, Utkarsh Ayachit > wrote: Michael, Hold off on using the superbuild on MountainLion for now. I'll track the issues down and then let you know. Utkarsh On Wed, Sep 3, 2014 at 6:23 PM, Utkarsh Ayachit > wrote: Michael, Let me try this on a Moutain Lion myself and I'll let you know. What projects are you turning on in your build? Utkarsh On Wed, Sep 3, 2014 at 2:40 PM, Reuter, Michael A. > wrote: This gets around the clang argument problem, but the ParaView CMake configuration step still fails for an unknown reason. M On Sep 3, 2014, at 10:28 AM, Utkarsh Ayachit > wrote: Cherry-pick this fix for now : http://review.source.kitware.com/#/c/16665/ It'll go into master soon. Ben, anything this fix is waiting on? Utkarsh On Wed, Sep 3, 2014 at 9:42 AM, Reuter, Michael A. > wrote: Hi, I?m having trouble getting the git-master version of the Superbuild running on OSX (10.9) with clang (5.1). Setting the CMAKE_OSX_SYSROOT variable causes the following error during CMake (2.8.12.2) generation for the ParaView subproject: -- The C compiler identification is unknown -- The CXX compiler identification is unknown -- Check for working C compiler using: Ninja -- Check for working C compiler using: Ninja -- broken CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): The C compiler "/usr/bin/cc" is not able to compile a simple test program. It fails with the following output: Change Dir: /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075 [1/2] Building C object CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o FAILED: /usr/bin/cc -fPIC -arch x86_64 -mmacosx-version-min=10.9 -sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk -o CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o -c testCCompiler.c clang: error: unknown argument: '-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' [-Wunused-command-line-argument-hard-error-in-future] clang: note: this will be a hard error (cannot be downgraded to a warning) in the future ninja: build stopped: subcommand failed. Even if I empty the CMAKE_OSX_SYSROOT variable, the system still tries to pass an empty -sysroot flag to clang causing it to choke. I removed the sysroot flag from the top-level CMakeLists.txt, but then the ParaView CMake setup fails for a reason I can?t seem to understand. I?m attaching the log showing the CMake output. The only obvious thing I see is the Fortran compiler. Is that required? Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Mon Sep 8 11:28:28 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 8 Sep 2014 11:28:28 -0400 Subject: [Paraview] Superbuild and OSX In-Reply-To: <8BF5A961-B485-4E06-B2A0-08CCE4CDF660@ornl.gov> References: <8BF5A961-B485-4E06-B2A0-08CCE4CDF660@ornl.gov> Message-ID: Don't use ninja..on OsX or Linux. Stick with make files for those for now. On Mon, Sep 8, 2014 at 11:15 AM, Reuter, Michael A. wrote: > After updating the Superbuild code and cleaning house, I was still seeing the ParaView CMake configure failure I reported before. I did a bit of digging and found that the generated pv-paraview-build.cmake was trying to execute the following command: step_command-NOTFOUND. It seems to be related to trying to use ninja instead of make files. I switched to make files and the build is in progress. > > Thanks, > M > > > > On Sep 7, 2014, at 1:58 PM, Utkarsh Ayachit > wrote: > > Alright, Superbuild + Mavericks is now working as expected. It's now > tested on the dashboards too: > > http://open.cdash.org/buildSummary.php?buildid=3479885 > > If looking for options to turn on, here's a good start: > http://open.cdash.org/viewNotes.php?buildid=3479885 > > Utkarsh > > On Thu, Sep 4, 2014 at 9:22 AM, Utkarsh Ayachit > wrote: > Sorry, I did mean Mavericks :)..I can never keep the MacOS names straight. > > On Thu, Sep 4, 2014 at 8:00 AM, Reuter, Michael A. wrote: > Thanks for the update. I?m actually building on Mavericks, but our project is still supporting Mountain Lion so it will be good to have it work there. > > M > > > On Sep 3, 2014, at 11:57 PM, Utkarsh Ayachit > wrote: > > Michael, > > Hold off on using the superbuild on MountainLion for now. I'll track > the issues down and then let you know. > > > Utkarsh > > On Wed, Sep 3, 2014 at 6:23 PM, Utkarsh Ayachit > > wrote: > Michael, > > Let me try this on a Moutain Lion myself and I'll let you know. What > projects are you turning on in your build? > > Utkarsh > > On Wed, Sep 3, 2014 at 2:40 PM, Reuter, Michael A. > wrote: > This gets around the clang argument problem, but the ParaView CMake configuration step still fails for an unknown reason. > > M > > On Sep 3, 2014, at 10:28 AM, Utkarsh Ayachit > wrote: > > Cherry-pick this fix for now : http://review.source.kitware.com/#/c/16665/ > It'll go into master soon. > > Ben, anything this fix is waiting on? > > Utkarsh > > On Wed, Sep 3, 2014 at 9:42 AM, Reuter, Michael A. > wrote: > Hi, > > I?m having trouble getting the git-master version of the Superbuild running on OSX (10.9) with clang (5.1). Setting the CMAKE_OSX_SYSROOT variable causes the following error during CMake (2.8.12.2) generation for the ParaView subproject: > > -- The C compiler identification is unknown > -- The CXX compiler identification is unknown > -- Check for working C compiler using: Ninja > -- Check for working C compiler using: Ninja -- broken > CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): > The C compiler "/usr/bin/cc" is not able to compile a simple test program. > > It fails with the following output: > > Change Dir: /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp > > Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075 > > [1/2] Building C object > CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o > > FAILED: /usr/bin/cc -fPIC -arch x86_64 -mmacosx-version-min=10.9 > -sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk > -o CMakeFiles/cmTryCompileExec4050157075.dir/testCCompiler.c.o -c > testCCompiler.c > > clang: error: unknown argument: > '-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' > [-Wunused-command-line-argument-hard-error-in-future] > > clang: note: this will be a hard error (cannot be downgraded to a warning) > in the future > > ninja: build stopped: subcommand failed. > > Even if I empty the CMAKE_OSX_SYSROOT variable, the system still tries to pass an empty -sysroot flag to clang causing it to choke. I removed the sysroot flag from the top-level CMakeLists.txt, but then the ParaView CMake setup fails for a reason I can?t seem to understand. I?m attaching the log showing the CMake output. The only obvious thing I see is the Fortran compiler. Is that required? > > Thanks, > M > > Dr. Michael Reuter > Scientific Data Analysis Group > Neutron Data Analysis and Visualization Division > Oak Ridge National Laboratory > > Office: 1-865-241-7216 > Fax: 1-865-574-6080 > Email: reuterma at ornl.gov > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > From wascott at sandia.gov Mon Sep 8 17:16:42 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 8 Sep 2014 21:16:42 +0000 Subject: [Paraview] Silo and CGNS readers Message-ID: <13f7183c73324fc8a29dded2d4500cc3@ES05AMSNLNT.srn.sandia.gov> What are the magic cmake switches used to compile and link Silo and CGNS into ParaView 4.2? Are these documented on the wiki anywhere? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlih at masonlive.gmu.edu Mon Sep 8 19:17:04 2014 From: jlih at masonlive.gmu.edu (jlih) Date: Mon, 8 Sep 2014 23:17:04 +0000 Subject: [Paraview] Usage of Octree, AMR In-Reply-To: References: <06634bcb906c4de2bf627b49a56ca25e@BN1PR01MB133.prod.exchangelabs.com> , Message-ID: <1410218224231.46003@masonlive.gmu.edu> Hi Berk, Do you have any suggestions regarding parallel volume rendering for multiresolution ? Thanks, Jing ________________________________ From: Berk Geveci Sent: Thursday, August 28, 2014 10:25 AM To: jlih Cc: paraview at paraview.org Subject: Re: [Paraview] Usage of Octree, AMR Hi Jing, I did not drop this. I will get back to you soon with some info. Best, -berk On Tue, Aug 26, 2014 at 10:24 AM, Jing Li > wrote: Hi Berk, Thanks for your reply. The original Netcdf file is a regular spaced 3D dataset with a lot of filled values. I plan to reorganize the data with AMR or some other more efficient structures for rendering. I am developing Python functions to resample Netcdf files but I am not sure if this is the right direction. Any suggestions are highly appreciated. Jing On Aug 26, 2014, at 9:57 PM, Berk Geveci > wrote: Hi Jing, So that I understand, does your NetCDF file already contain some sort of hierarchy or are you after adaptively rendering it by creating the hierarchy on the fly? Best, -berk On Sun, Aug 24, 2014 at 2:31 AM, jlih > wrote: Hi all, I have a question regarding the usage of the octree. Is it possible to create an octree structure for an array (e.g., an array from a NetCDF file)? >From the Source, I can select octree which creates a "template" octree structure. I'd like to use the octree structure to reorganize the 3D NetCDF data to make the rendering more efficient. If using octree is not possible, how about using AMR? Thanks in advance. Jing? _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Mon Sep 8 19:45:10 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Mon, 8 Sep 2014 23:45:10 +0000 Subject: [Paraview] writing block data in parallel for vtk readers Message-ID: Hi, I am wondering how to write out a set of VTK files for input into paraview. The code we are writing from is Miranda, an MPI code, and each processor writes out its subdomain individually. No ghost zones are written into the files. Perhaps they could be; I?m not sure about that part. Sometimes the data is curvilinear but usually rectilinear. Miranda is included in the VISIT_BRIDGE stuff but what?s in VISIT_BRIDGE for Miranda is old and the newer stuff doesn?t parse any more. Thanks! -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ganesh.iitm at gmail.com Mon Sep 8 19:46:53 2014 From: ganesh.iitm at gmail.com (Ganesh Vijayakumar) Date: Mon, 8 Sep 2014 19:46:53 -0400 Subject: [Paraview] writing block data in parallel for vtk readers In-Reply-To: References: Message-ID: Could you write your data into HDF5 files and try the xdmf format for visualization. On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: > Hi, > I am wondering how to write out a set of VTK files for input into > paraview. > The code we are writing from is Miranda, an MPI code, and each processor > writes out its subdomain individually. No ghost zones are written into the > files. Perhaps they could be; I?m not sure about that part. > Sometimes the data is curvilinear but usually rectilinear. > Miranda is included in the VISIT_BRIDGE stuff but what?s in VISIT_BRIDGE > for Miranda is old and the newer stuff doesn?t parse any more. > Thanks! > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From furutaka.kazuyoshi at jaea.go.jp Tue Sep 9 00:57:36 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Tue, 09 Sep 2014 13:57:36 +0900 (JST) Subject: [Paraview] how to know the type of a view? Message-ID: <20140909.135736.71465939.furutaka.kazuyoshi@jaea.go.jp> Dear ParaView experts... Is there any way to knwo what the type of a view is within a python macro (e.g. from the return value of GetRenderView())? I'd like to know whether an exisiting view is, say, a 'MultiSlice' or not (and create one if none exists). Thanks in advance. Kazuyoshi -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From cory.quammen at kitware.com Tue Sep 9 01:03:46 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 9 Sep 2014 01:03:46 -0400 Subject: [Paraview] how to know the type of a view? In-Reply-To: <20140909.135736.71465939.furutaka.kazuyoshi@jaea.go.jp> References: <20140909.135736.71465939.furutaka.kazuyoshi@jaea.go.jp> Message-ID: Kazuyoshi, You should be able to use type(GetRenderView()) or GetRenderView().GetClassName() to find out what type of view you have. Hope that helps, Cory On Tue, Sep 9, 2014 at 12:57 AM, Kazuyoshi Furutaka wrote: > Dear ParaView experts... > > Is there any way to knwo what the type of a view is > within a python macro (e.g. from the return value of > GetRenderView())? > I'd like to know whether an exisiting view is, say, a > 'MultiSlice' or not (and create one if none exists). > > Thanks in advance. > > Kazuyoshi > -- > Kazuyoshi Furutaka > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From furutaka.kazuyoshi at jaea.go.jp Tue Sep 9 01:11:30 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Tue, 09 Sep 2014 14:11:30 +0900 (JST) Subject: [Paraview] how to know the type of a view? In-Reply-To: References: <20140909.135736.71465939.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <20140909.141130.376373994.furutaka.kazuyoshi@jaea.go.jp> Dear Cory, Thanks for your immediate response! The latter (GetRenderView().GetClassName()) is what I want! Thanks again. Kazuyoshi From: Cory Quammen Subject: Re: [Paraview] how to know the type of a view? Date: Tue, 9 Sep 2014 01:03:46 -0400 > You should be able to use > > type(GetRenderView()) > > or > > GetRenderView().GetClassName() > > to find out what type of view you have. > > Hope that helps, > Cory -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From dave.demarle at kitware.com Tue Sep 9 09:35:08 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 9 Sep 2014 09:35:08 -0400 Subject: [Paraview] announce: nominees are decided, now vote in the 2014 HPCwire awards Message-ID: Thank you everyone who nominated VTK and ParaView! The nominees have been chosen and VTK and ParaView both made the Best HPC visualization product or technology list. Please vote for VTK and ParaView. For details see: http://tci.taborcommunications.com/webmail/21812/138268695/d27a89e0d341e5c4e5fe433bb0cb97f4 many thanks! David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Sep 9 12:54:51 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 9 Sep 2014 12:54:51 -0400 Subject: [Paraview] Building ParaView with QT 5.3 In-Reply-To: References: Message-ID: Andrew, Today's gatekeeper review brought in fixes to address the Qt 5.3 build issue. The CMake warnings still remain. I'll have them diagnosed soonish. Utkarsh On Tue, Jun 17, 2014 at 8:11 AM, Andrew Maclean wrote: > Has anyone been able to do this? > I am using Linux with Qt5.3 and CMake 3.0.0. > I have set PARAVIEW_QT_VERSION to 5 > QT 5.3 is found OK > It seems that there is an issue with double colons in target names as > evidenced by the CMake generation warnings raised: > -------------------------------------------- > CMake Warning (dev) at VTK/CMake/vtkModuleMacros.cmake:497 (add_library): > Policy CMP0028 is not set: Double colon in target name means ALIAS or > IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. > Use the cmake_policy command to set the policy and suppress this warning. > > Target "pqWidgets" links to target "Qt5::Test" but the target was not > found. Perhaps a find_package() call is missing for an IMPORTED target, > or > an ALIAS target is missing? > Call Stack (most recent call first): > VTK/CMake/vtkModuleMacros.cmake:581 (vtk_add_library) > Qt/Widgets/CMakeLists.txt:288 (vtk_module_library) > This warning is for project developers. Use -Wno-dev to suppress it. > > and so on until > > CMake Warning (dev) at VTK/CMake/vtkForwardingExecutable.cmake:91 > (add_executable): > Policy CMP0028 is not set: Double colon in target name means ALIAS or > IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. > Use the cmake_policy command to set the policy and suppress this warning. > > Target "paraview" links to target "Qt5::Xml" but the target was not found. > Perhaps a find_package() call is missing for an IMPORTED target, or an > ALIAS target is missing? > Call Stack (most recent call first): > CMake/ParaViewBranding.cmake:294 (vtk_add_executable_with_forwarding2) > Applications/ParaView/CMakeLists.txt:55 (build_paraview_client) > This warning is for project developers. Use -Wno-dev to suppress it. > > Generating done > -------------------------------------------- > > From what I understand CMake 3.0.0 is searching for targets, then files on > disk which is the OLD behaviour. So this may not be the problem as I have > been unable to build with earlier versions of CMake. > > The build then fails, after VTK is built, with (if testing is set): > -------------------------------------------- > [ 28%] Built target vtkPVServerManagerCore > Linking CXX shared library ../../../lib/libQtTesting.so > CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In function > `pqNativeFileDialogEventPlayer::start()': > /home/amaclean/Development/Kitware/src/ParaView/ThirdParty/QtTesting/vtkqttesting/pqNativeFileDialogEventPlayer.cxx:122: > undefined reference to `qt_filedialog_existing_directory_hook' > ... > /home/amaclean/Development/Kitware/src/ParaView/ThirdParty/QtTesting/vtkqttesting/pqNativeFileDialogEventTranslator.cxx:152: > undefined reference to `qt_filedialog_open_filenames_hook' > /home/amaclean/Development/Kitware/src/ParaView/ThirdParty/QtTesting/vtkqttesting/pqNativeFileDialogEventTranslator.cxx:153: > undefined reference to `qt_filedialog_save_filename_hook' > collect2: error: ld returned 1 exit status > make[2]: *** [lib/libQtTesting.so] Error 1 > make[1]: *** > [ThirdParty/QtTesting/vtkqttesting/CMakeFiles/QtTesting.dir/all] Error 2 > make: *** [all] Error 2 > -------------------------------------------- > If testing is not set the errors are similar: > -------------------------------------------- > Linking CXX shared library ../../../lib/libvtkPVServerManagerCore-pv4.1.so > [ 17%] Built target vtkPVServerManagerCore > Linking CXX shared library ../../../lib/libQtTesting.so > CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In function > `pqNativeFileDialogEventPlayer::start()': > /home/amaclean/Development/Kitware/src/ParaView/ThirdParty/QtTesting/vtkqttesting/pqNativeFileDialogEventPlayer.cxx:122: > undefined reference to `qt_filedialog_existing_directory_hook' > ... > /home/amaclean/Development/Kitware/src/ParaView/ThirdParty/QtTesting/vtkqttesting/pqNativeFileDialogEventTranslator.cxx:152: > undefined reference to `qt_filedialog_open_filenames_hook' > /home/amaclean/Development/Kitware/src/ParaView/ThirdParty/QtTesting/vtkqttesting/pqNativeFileDialogEventTranslator.cxx:153: > undefined reference to `qt_filedialog_save_filename_hook' > collect2: error: ld returned 1 exit status > make[2]: *** [lib/libQtTesting.so] Error 1 > make[1]: *** > [ThirdParty/QtTesting/vtkqttesting/CMakeFiles/QtTesting.dir/all] Error 2 > make: *** [all] Error 2 > > > Regards > Andrew > > -- > ___________________________________________ > Andrew J. P. Maclean > > ___________________________________________ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From robert.maynard at kitware.com Wed Sep 10 11:46:56 2014 From: robert.maynard at kitware.com (Robert Maynard) Date: Wed, 10 Sep 2014 11:46:56 -0400 Subject: [Paraview] Silo and CGNS readers In-Reply-To: <13f7183c73324fc8a29dded2d4500cc3@ES05AMSNLNT.srn.sandia.gov> References: <13f7183c73324fc8a29dded2d4500cc3@ES05AMSNLNT.srn.sandia.gov> Message-ID: You need to set the following paraview flags to enable Silo and CGNS. PARAVIEW_USE_VISITBRIDGE=ON VISIT_BUILD_READER_Silo=ON VISIT_BUILD_READER_CGNS=ON On Mon, Sep 8, 2014 at 5:16 PM, Scott, W Alan wrote: > What are the magic cmake switches used to compile and link Silo and CGNS > into ParaView 4.2? Are these documented on the wiki anywhere? > > Thanks, > > Alan > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From leonardopessanha74 at gmail.com Wed Sep 10 16:13:23 2014 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Wed, 10 Sep 2014 17:13:23 -0300 Subject: [Paraview] Object following CSV file series points path In-Reply-To: References: Message-ID: Thank you! That was exactly what i was looking for! Att, Leonardo Pessanha 2014-09-08 11:30 GMT-03:00 Moreland, Kenneth : > You can use the Glyph With Custom Source filter. This filter works like > the standard Glyph filter but it allows you to input an arbitrary polydata > to center on each point rather a predefined shape. > > -Ken > > From: L?o Pessanha > Date: Friday, September 5, 2014 3:47 PM > To: ParaView list > Subject: [EXTERNAL] [Paraview] Object following CSV file series points > path > > Hi, > > I have a series of CSV files that describes a path > > I am able to see the path animated as points > > I want to put an object that i modelled following this path > > How can i do that? > > Att, > Leonardo Pessanha > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkonesh at yahoo.com Wed Sep 10 16:56:31 2014 From: mkonesh at yahoo.com (Mohammad KONESHLOO) Date: Wed, 10 Sep 2014 13:56:31 -0700 Subject: [Paraview] vts file format Message-ID: <1410382591.84710.YahooMailNeo@web121202.mail.ne1.yahoo.com> Hi everybody, I'm trying to convert a big csv file to a simple structured grid (100x100x136). I imported it to Pra-view, but I could not convert it to grid using Filters-> "Table to Structured Grid". another attempt was creating a vts/vtk file from my csv file, but the structure of file is ambiguous. I couldn't find any example. In VTK pdf file regarding file formats, there is just an example for structured point (page.18), I copied and pasted this example in Notepad++ and saved with .vts and vtk extension, but I could not open in in Paraview (4.2.0 RC1 64-bit). Do you have any example file or comment on the file structure? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Wed Sep 10 19:55:56 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 10 Sep 2014 19:55:56 -0400 Subject: [Paraview] writing block data in parallel for vtk readers In-Reply-To: References: Message-ID: Hey Rich, Is this a matter of updating the VisIt bridge or the code in VisIt is old too? What are the larger runs these folks do? And what is the timeframe? We are working on ADIOS readers and that may be another option. This is where we currently plan on pushing for large scale IO needs. HDF5 is certainly another option. So is writing legacy VTK files from each node. I'd guess Silo is another option too. It depends on the needs and scale at which they will be running. Best, -berk On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: > Hi, > I am wondering how to write out a set of VTK files for input into > paraview. > The code we are writing from is Miranda, an MPI code, and each processor > writes out its subdomain individually. No ghost zones are written into the > files. Perhaps they could be; I?m not sure about that part. > Sometimes the data is curvilinear but usually rectilinear. > Miranda is included in the VISIT_BRIDGE stuff but what?s in VISIT_BRIDGE > for Miranda is old and the newer stuff doesn?t parse any more. > Thanks! > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Wed Sep 10 20:19:08 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 11 Sep 2014 00:19:08 +0000 Subject: [Paraview] writing block data in parallel for vtk readers In-Reply-To: References: Message-ID: The code in VisIt is up to date; it?s just Paraview that seems behind the times. I am not able to completely convince myself of why but I suspect that?s the problem. The actual error shows up as some sort of VTK error. ? Rich ERROR: In /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 754 vtkPVCompositeDataPipeline (0x252ff00): Algorithm vtkVisItMirandaReader(0x25342b0) returned failure for request: vtkInformation (0x2521130) Debug: Off Modified Time: 119319 Reference Count: 1 Registered Events: (none) Request: REQUEST_DATA_OBJECT ALGORITHM_AFTER_FORWARD: 1 FORWARD_DIRECTION: 0 ERROR: In /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 754 vtkPVCompositeDataPipeline (0x252ff00): Algorithm vtkVisItMirandaReader(0x25342b0) returned failure for request: vtkInformation (0x2521130) Debug: Off Modified Time: 119319 Reference Count: 1 Registered Events: (none) Request: REQUEST_DATA_OBJECT ALGORITHM_AFTER_FORWARD: 1 FORWARD_DIRECTION: 0 On Sep 10, 2014, at 4:55 PM, Berk Geveci > wrote: Hey Rich, Is this a matter of updating the VisIt bridge or the code in VisIt is old too? What are the larger runs these folks do? And what is the timeframe? We are working on ADIOS readers and that may be another option. This is where we currently plan on pushing for large scale IO needs. HDF5 is certainly another option. So is writing legacy VTK files from each node. I'd guess Silo is another option too. It depends on the needs and scale at which they will be running. Best, -berk On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich > wrote: Hi, I am wondering how to write out a set of VTK files for input into paraview. The code we are writing from is Miranda, an MPI code, and each processor writes out its subdomain individually. No ghost zones are written into the files. Perhaps they could be; I?m not sure about that part. Sometimes the data is curvilinear but usually rectilinear. Miranda is included in the VISIT_BRIDGE stuff but what?s in VISIT_BRIDGE for Miranda is old and the newer stuff doesn?t parse any more. Thanks! -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Sep 11 01:04:55 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 11 Sep 2014 01:04:55 -0400 Subject: [Paraview] writing block data in parallel for vtk readers In-Reply-To: References: Message-ID: Rich, FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You can try 4.2-RC1 to see if this was indeed a VisIt bridge being old issue. Utkarsh On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: > The code in VisIt is up to date; it?s just Paraview that seems behind the > times. I am not able to completely convince myself of why but I suspect > that?s the problem. The actual error shows up as some sort of VTK error. > ? Rich > > > ERROR: In > /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, > line 754 > vtkPVCompositeDataPipeline (0x252ff00): Algorithm > vtkVisItMirandaReader(0x25342b0) returned failure for request: > vtkInformation (0x2521130) > Debug: Off > Modified Time: 119319 > Reference Count: 1 > Registered Events: (none) > Request: REQUEST_DATA_OBJECT > ALGORITHM_AFTER_FORWARD: 1 > FORWARD_DIRECTION: 0 > > > > > ERROR: In > /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, > line 754 > vtkPVCompositeDataPipeline (0x252ff00): Algorithm > vtkVisItMirandaReader(0x25342b0) returned failure for request: > vtkInformation (0x2521130) > Debug: Off > Modified Time: 119319 > Reference Count: 1 > Registered Events: (none) > Request: REQUEST_DATA_OBJECT > ALGORITHM_AFTER_FORWARD: 1 > FORWARD_DIRECTION: 0 > > > > > On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: > > Hey Rich, > > Is this a matter of updating the VisIt bridge or the code in VisIt is old > too? > > What are the larger runs these folks do? And what is the timeframe? > > We are working on ADIOS readers and that may be another option. This is > where we currently plan on pushing for large scale IO needs. > > HDF5 is certainly another option. So is writing legacy VTK files from each > node. I'd guess Silo is another option too. > > It depends on the needs and scale at which they will be running. > > Best, > -berk > > On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >> >> Hi, >> I am wondering how to write out a set of VTK files for input into >> paraview. >> The code we are writing from is Miranda, an MPI code, and each processor >> writes out its subdomain individually. No ghost zones are written into the >> files. Perhaps they could be; I?m not sure about that part. >> Sometimes the data is curvilinear but usually rectilinear. >> Miranda is included in the VISIT_BRIDGE stuff but what?s in VISIT_BRIDGE >> for Miranda is old and the newer stuff doesn?t parse any more. >> Thanks! >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA >> ? (office) (925) 423-9605 >> ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., >> Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., > Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Thu Sep 11 01:21:44 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 11 Sep 2014 01:21:44 -0400 Subject: [Paraview] Superbuild and Windows In-Reply-To: References: <6E8F6C07-4BA8-4575-B404-16ABCD63CE63@ornl.gov> Message-ID: Michael, with VS2012, what was your selection for Python? Were you using system Python or did you let the superbuild build its own? Utkarsh On Fri, Sep 5, 2014 at 4:58 PM, Reuter, Michael A. wrote: > I?m working with VS2012. Thanks for the update on Mavericks. > > M > On Sep 5, 2014, at 4:32 PM, Utkarsh Ayachit wrote: > >> Great! Which VS was this? The Pygments thing should be tracked down. >> I'll see what's happening there. BTW, I am making progress on >> Mavericks build. I think I have most things ironed out. I'll send an >> updated email once I have dashboard testing it. >> >> Utkarsh >> >> On Fri, Sep 5, 2014 at 4:29 PM, Reuter, Michael A. wrote: >>> I switched to Ninja and shortened up the paths, but what really got things working was passing the VTK_USE_SYSTEM_PYGMENTS down to the ParaView CMake config via the PV_EXTRA_CMAKE_ARGS. After that, the build went smoothly. I hit a snag on creating the package because I?m triggering the USE_SYSTEM_matplotlib option and the Projects/win32/paraview.bundle.cmake does not trap the copying of matplotlib related items when this flag is used. I see a similar issue in the Projects/apple/paraview.bundle.cmake file as well. I added a AND NOT USE_SYSTEM_matplotlib to the if (matplotlib_ENABLED) line and that fixed the generated cmake_install.cmake file and the package created fine. I?ve tested the resulting package and so far so good. >>> >>> M >>> >>> >>> On Sep 3, 2014, at 10:24 AM, Utkarsh Ayachit > wrote: >>> >>> Michael, >>> >>> Are you using VS generator? Can you switch to using Ninja? You can >>> still use the MSVC compilers. The error is popping up when the build >>> is trying to compiler the pygments *.py files. You'll get the same >>> error later when it's trying to compile the ParaView *.py files. >>> >>> Also, another thing to note is that Windows has issues with long >>> paths. So I'd suggest moving the superbuild source and build >>> directories to something lower to avoid those e.g. C:/tmp/pvs-src and >>> C:/tmp/pvs-build. >>> >>> Finally, if you're using VS2012, you'll need to use a system Python. >>> Currently. the Python included in the superbuild is intended for >>> VS2008. Also VS2012, is currently untested. As a first pass, if >>> possible, I'd suggest using VS 2008. Once that's working, you can give >>> VS2012 try. Hopefully, it should work (except the Python caveat), but >>> I am always wary of VS version differences. >>> >>> Utkarsh >>> >>> >>> >>> On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. > wrote: >>> Hi, >>> >>> >>> >>> I?m having an issue with the ParaView Superbuild on Windows >>> (VS2012). I get this error during the build process: >>> >>> >>> >>> 322> Compiling Python package 'pygments' >>> >>> >>> >>> 322> Listing >>> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments >>> ... >>> >>> >>> >>> 322> Listing >>> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\filters >>> ... >>> >>> >>> >>> 322> Listing >>> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\formatters >>> ... >>> >>> >>> >>> 322> Listing >>> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\lexers >>> ... >>> >>> >>> >>> 322> Listing >>> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\styles >>> ... >>> >>> >>> >>> 322> ImportError: No module named site >>> >>> >>> >>> 9>C:\Program Files >>> (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): >>> error MSB6006: "cmd.exe" exited with code 1. >>> [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] >>> >>> >>> >>> 322> >>> >>> 322>Build FAILED. >>> >>> >>> >>> However, the site module exists when I run python. I?m building from a >>> script so I can control the environment. Everything else seems to build just >>> fine. However, nothing appears in the install directory for cpack to find. I >>> can?t tell if this build error is disrupting the process or something else >>> is going wrong. What controls the pygments build so I can shut it off for >>> now? >>> >>> >>> >>> Thanks, >>> >>> M >>> >>> >>> >>> Dr. Michael Reuter >>> >>> Scientific Data Analysis Group >>> >>> Neutron Data Analysis and Visualization Division >>> >>> Oak Ridge National Laboratory >>> >>> >>> >>> Office: 1-865-241-7216 >>> >>> Fax: 1-865-574-6080 >>> >>> Email: reuterma at ornl.gov >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> > From utkarsh.ayachit at kitware.com Thu Sep 11 01:49:01 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 11 Sep 2014 01:49:01 -0400 Subject: [Paraview] vts file format In-Reply-To: <1410382591.84710.YahooMailNeo@web121202.mail.ne1.yahoo.com> References: <1410382591.84710.YahooMailNeo@web121202.mail.ne1.yahoo.com> Message-ID: Are you sure it's a "structured grid" or is an "image data"? Refer to this for difference between the two: http://www.paraview.org/Wiki/ParaView/Users_Guide/VTK_Data_Model Programmable filer may be the easiest way to go. Attached is an extract from the ParaView User's Guide that's currently being updated. A combination of recipes shown in Sections 14.2.1 and 14.2.4 is what should help. Utkarsh ? ParaViewUsersGuideExtract.pdf ? On Wed, Sep 10, 2014 at 4:56 PM, Mohammad KONESHLOO via ParaView < paraview at paraview.org> wrote: > Hi everybody, > > I'm trying to convert a big csv file to a simple structured grid > (100x100x136). I imported it to Pra-view, but I could not convert it to > grid using Filters-> "Table to Structured Grid". another attempt was > creating a vts/vtk file from my csv file, but the structure of file is > ambiguous. I couldn't find any example. > In VTK pdf file regarding file formats, there is just an example for > structured point (page.18), I copied and pasted this example in Notepad++ > and saved with .vts and vtk extension, but I could not open in in Paraview > (4.2.0 RC1 64-bit). > > Do you have any example file or comment on the file structure? > > Thanks > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From reuterma at ornl.gov Thu Sep 11 08:34:45 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Thu, 11 Sep 2014 12:34:45 +0000 Subject: [Paraview] Superbuild and Windows In-Reply-To: References: <6E8F6C07-4BA8-4575-B404-16ABCD63CE63@ornl.gov> Message-ID: <8C642057-0905-44C4-AAB6-63D6DAEC8DF7@ornl.gov> I used a system Python which is pointed at a Python we distribute with Mantid on Windows. BTW, do you want me to pass along the patches I have for the USE_SYSTEM_matplotlib issues I run into, or should I just handle those in a Superbuild fork? Thanks, M On Sep 11, 2014, at 1:21 AM, Utkarsh Ayachit > wrote: Michael, with VS2012, what was your selection for Python? Were you using system Python or did you let the superbuild build its own? Utkarsh On Fri, Sep 5, 2014 at 4:58 PM, Reuter, Michael A. > wrote: I?m working with VS2012. Thanks for the update on Mavericks. M On Sep 5, 2014, at 4:32 PM, Utkarsh Ayachit > wrote: Great! Which VS was this? The Pygments thing should be tracked down. I'll see what's happening there. BTW, I am making progress on Mavericks build. I think I have most things ironed out. I'll send an updated email once I have dashboard testing it. Utkarsh On Fri, Sep 5, 2014 at 4:29 PM, Reuter, Michael A. > wrote: I switched to Ninja and shortened up the paths, but what really got things working was passing the VTK_USE_SYSTEM_PYGMENTS down to the ParaView CMake config via the PV_EXTRA_CMAKE_ARGS. After that, the build went smoothly. I hit a snag on creating the package because I?m triggering the USE_SYSTEM_matplotlib option and the Projects/win32/paraview.bundle.cmake does not trap the copying of matplotlib related items when this flag is used. I see a similar issue in the Projects/apple/paraview.bundle.cmake file as well. I added a AND NOT USE_SYSTEM_matplotlib to the if (matplotlib_ENABLED) line and that fixed the generated cmake_install.cmake file and the package created fine. I?ve tested the resulting package and so far so good. M On Sep 3, 2014, at 10:24 AM, Utkarsh Ayachit > wrote: Michael, Are you using VS generator? Can you switch to using Ninja? You can still use the MSVC compilers. The error is popping up when the build is trying to compiler the pygments *.py files. You'll get the same error later when it's trying to compile the ParaView *.py files. Also, another thing to note is that Windows has issues with long paths. So I'd suggest moving the superbuild source and build directories to something lower to avoid those e.g. C:/tmp/pvs-src and C:/tmp/pvs-build. Finally, if you're using VS2012, you'll need to use a system Python. Currently. the Python included in the superbuild is intended for VS2008. Also VS2012, is currently untested. As a first pass, if possible, I'd suggest using VS 2008. Once that's working, you can give VS2012 try. Hopefully, it should work (except the Python caveat), but I am always wary of VS version differences. Utkarsh On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. > wrote: Hi, I?m having an issue with the ParaView Superbuild on Windows (VS2012). I get this error during the build process: 322> Compiling Python package 'pygments' 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\filters ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\formatters ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\lexers ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\styles ... 322> ImportError: No module named site 9>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): error MSB6006: "cmd.exe" exited with code 1. [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] 322> 322>Build FAILED. However, the site module exists when I run python. I?m building from a script so I can control the environment. Everything else seems to build just fine. However, nothing appears in the install directory for cpack to find. I can?t tell if this build error is disrupting the process or something else is going wrong. What controls the pygments build so I can shut it off for now? Thanks, M Dr. Michael Reuter Scientific Data Analysis Group Neutron Data Analysis and Visualization Division Oak Ridge National Laboratory Office: 1-865-241-7216 Fax: 1-865-574-6080 Email: reuterma at ornl.gov _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Thu Sep 11 10:56:42 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 11 Sep 2014 10:56:42 -0400 Subject: [Paraview] Superbuild and Windows In-Reply-To: <8C642057-0905-44C4-AAB6-63D6DAEC8DF7@ornl.gov> References: <6E8F6C07-4BA8-4575-B404-16ABCD63CE63@ornl.gov> <8C642057-0905-44C4-AAB6-63D6DAEC8DF7@ornl.gov> Message-ID: Michael, The patches would be great! I don't think we tested with system Python on Windows. Utkarsh On Thu, Sep 11, 2014 at 8:34 AM, Reuter, Michael A. wrote: > I used a system Python which is pointed at a Python we distribute with > Mantid on Windows. BTW, do you want me to pass along the patches I have for > the USE_SYSTEM_matplotlib issues I run into, or should I just handle those > in a Superbuild fork? > > Thanks, > M > > > On Sep 11, 2014, at 1:21 AM, Utkarsh Ayachit > wrote: > > Michael, with VS2012, what was your selection for Python? Were you > using system Python or did you let the superbuild build its own? > > Utkarsh > > On Fri, Sep 5, 2014 at 4:58 PM, Reuter, Michael A. > wrote: > I?m working with VS2012. Thanks for the update on Mavericks. > > M > On Sep 5, 2014, at 4:32 PM, Utkarsh Ayachit > wrote: > > Great! Which VS was this? The Pygments thing should be tracked down. > I'll see what's happening there. BTW, I am making progress on > Mavericks build. I think I have most things ironed out. I'll send an > updated email once I have dashboard testing it. > > Utkarsh > > On Fri, Sep 5, 2014 at 4:29 PM, Reuter, Michael A. > wrote: > I switched to Ninja and shortened up the paths, but what really got things > working was passing the VTK_USE_SYSTEM_PYGMENTS down to the ParaView CMake > config via the PV_EXTRA_CMAKE_ARGS. After that, the build went smoothly. I > hit a snag on creating the package because I?m triggering the > USE_SYSTEM_matplotlib option and the Projects/win32/paraview.bundle.cmake > does not trap the copying of matplotlib related items when this flag is > used. I see a similar issue in the Projects/apple/paraview.bundle.cmake > file as well. I added a AND NOT USE_SYSTEM_matplotlib to the if > (matplotlib_ENABLED) line and that fixed the generated cmake_install.cmake > file and the package created fine. I?ve tested the resulting package and so > far so good. > > M > > > On Sep 3, 2014, at 10:24 AM, Utkarsh Ayachit > > wrote: > > Michael, > > Are you using VS generator? Can you switch to using Ninja? You can > still use the MSVC compilers. The error is popping up when the build > is trying to compiler the pygments *.py files. You'll get the same > error later when it's trying to compile the ParaView *.py files. > > Also, another thing to note is that Windows has issues with long > paths. So I'd suggest moving the superbuild source and build > directories to something lower to avoid those e.g. C:/tmp/pvs-src and > C:/tmp/pvs-build. > > Finally, if you're using VS2012, you'll need to use a system Python. > Currently. the Python included in the superbuild is intended for > VS2008. Also VS2012, is currently untested. As a first pass, if > possible, I'd suggest using VS 2008. Once that's working, you can give > VS2012 try. Hopefully, it should work (except the Python caveat), but > I am always wary of VS version differences. > > Utkarsh > > > > On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. > wrote: > Hi, > > > > I?m having an issue with the ParaView Superbuild on Windows > (VS2012). I get this error during the build process: > > > > 322> Compiling Python package 'pygments' > > > > 322> Listing > > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments > ... > > > > 322> Listing > > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\filters > ... > > > > 322> Listing > > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\formatters > ... > > > > 322> Listing > > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\lexers > ... > > > > 322> Listing > > C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\styles > ... > > > > 322> ImportError: No module named site > > > > 9>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): > error MSB6006: "cmd.exe" exited with code 1. > [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj] > > > > 322> > > 322>Build FAILED. > > > > However, the site module exists when I run python. I?m building from a > script so I can control the environment. Everything else seems to build > just > fine. However, nothing appears in the install directory for cpack to find. > I > can?t tell if this build error is disrupting the process or something else > is going wrong. What controls the pygments build so I can shut it off for > now? > > > > Thanks, > > M > > > > Dr. Michael Reuter > > Scientific Data Analysis Group > > Neutron Data Analysis and Visualization Division > > Oak Ridge National Laboratory > > > > Office: 1-865-241-7216 > > Fax: 1-865-574-6080 > > Email: reuterma at ornl.gov reuterma at ornl.gov> > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From reuterma at ornl.gov Thu Sep 11 14:02:14 2014 From: reuterma at ornl.gov (Reuter, Michael A.) Date: Thu, 11 Sep 2014 18:02:14 +0000 Subject: [Paraview] Superbuild and Windows In-Reply-To: References: <6E8F6C07-4BA8-4575-B404-16ABCD63CE63@ornl.gov> <8C642057-0905-44C4-AAB6-63D6DAEC8DF7@ornl.gov> Message-ID: The patches are attached. They aren?t much but they help get the package (on Windows and OSX) built without issues. The package I made against the system Python seems to work OK although I have not exhaustively tested it. The python interpreter interaction inside ParaView seems to work fine with the few tests and examples I ran on it. M -------------- next part -------------- A non-text attachment was scrubbed... Name: apple_system_matplotlib.patch Type: application/octet-stream Size: 563 bytes Desc: apple_system_matplotlib.patch URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: win32_system_matplotlib.patch Type: application/octet-stream Size: 530 bytes Desc: win32_system_matplotlib.patch URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From cook47 at llnl.gov Thu Sep 11 14:04:24 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 11 Sep 2014 18:04:24 +0000 Subject: [Paraview] writing block data in parallel for vtk readers In-Reply-To: References: Message-ID: Cannot build 4.2-RC1. I get this error. I?ve reported it before, but now it halts the build, so it needs to get fixed and I don?t know the answer: Compiling /usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py ... SyntaxError: ('invalid syntax', ('/usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in enumerate(test_module_browsers)})\n')) On Sep 10, 2014, at 10:04 PM, Utkarsh Ayachit wrote: > Rich, > > FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You > can try 4.2-RC1 to see if this was indeed a VisIt bridge being old > issue. > > Utkarsh > > On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: >> The code in VisIt is up to date; it?s just Paraview that seems behind the >> times. I am not able to completely convince myself of why but I suspect >> that?s the problem. The actual error shows up as some sort of VTK error. >> ? Rich >> >> >> ERROR: In >> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, >> line 754 >> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >> vtkVisItMirandaReader(0x25342b0) returned failure for request: >> vtkInformation (0x2521130) >> Debug: Off >> Modified Time: 119319 >> Reference Count: 1 >> Registered Events: (none) >> Request: REQUEST_DATA_OBJECT >> ALGORITHM_AFTER_FORWARD: 1 >> FORWARD_DIRECTION: 0 >> >> >> >> >> ERROR: In >> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, >> line 754 >> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >> vtkVisItMirandaReader(0x25342b0) returned failure for request: >> vtkInformation (0x2521130) >> Debug: Off >> Modified Time: 119319 >> Reference Count: 1 >> Registered Events: (none) >> Request: REQUEST_DATA_OBJECT >> ALGORITHM_AFTER_FORWARD: 1 >> FORWARD_DIRECTION: 0 >> >> >> >> >> On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: >> >> Hey Rich, >> >> Is this a matter of updating the VisIt bridge or the code in VisIt is old >> too? >> >> What are the larger runs these folks do? And what is the timeframe? >> >> We are working on ADIOS readers and that may be another option. This is >> where we currently plan on pushing for large scale IO needs. >> >> HDF5 is certainly another option. So is writing legacy VTK files from each >> node. I'd guess Silo is another option too. >> >> It depends on the needs and scale at which they will be running. >> >> Best, >> -berk >> >> On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >>> >>> Hi, >>> I am wondering how to write out a set of VTK files for input into >>> paraview. >>> The code we are writing from is Miranda, an MPI code, and each processor >>> writes out its subdomain individually. No ghost zones are written into the >>> files. Perhaps they could be; I?m not sure about that part. >>> Sometimes the data is curvilinear but usually rectilinear. >>> Miranda is included in the VISIT_BRIDGE stuff but what?s in VISIT_BRIDGE >>> for Miranda is old and the newer stuff doesn?t parse any more. >>> Thanks! >>> >>> -- >>> ?Richard Cook >>> ? Lawrence Livermore National Laboratory >>> Bldg-453 Rm-4024, Mail Stop L-557 >>> 7000 East Avenue, Livermore, CA, 94550, USA >>> ? (office) (925) 423-9605 >>> ? (fax) (925) 423-6961 >>> --- >>> Information Management & Graphics Grp., Services & Development Div., >>> Integrated Computing & Communications Dept. >>> (opinions expressed herein are mine and not those of LLNL) >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA >> ? (office) (925) 423-9605 >> ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., >> Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) From cook47 at llnl.gov Thu Sep 11 14:09:20 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 11 Sep 2014 18:09:20 +0000 Subject: [Paraview] writing block data in parallel for vtk readers In-Reply-To: References: Message-ID: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> What?s strange about that line is that in our python on our clusters, that line compiles just fine. So perhaps there is a bug in whatever is compiling testing.py? On Sep 11, 2014, at 11:04 AM, Cook, Rich wrote: > Cannot build 4.2-RC1. I get this error. I?ve reported it before, but now it halts the build, so it needs to get fixed and I don?t know the answer: > > Compiling /usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py ... > SyntaxError: ('invalid syntax', ('/usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in enumerate(test_module_browsers)})\n')) > > > > On Sep 10, 2014, at 10:04 PM, Utkarsh Ayachit wrote: > >> Rich, >> >> FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You >> can try 4.2-RC1 to see if this was indeed a VisIt bridge being old >> issue. >> >> Utkarsh >> >> On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: >>> The code in VisIt is up to date; it?s just Paraview that seems behind the >>> times. I am not able to completely convince myself of why but I suspect >>> that?s the problem. The actual error shows up as some sort of VTK error. >>> ? Rich >>> >>> >>> ERROR: In >>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, >>> line 754 >>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>> vtkInformation (0x2521130) >>> Debug: Off >>> Modified Time: 119319 >>> Reference Count: 1 >>> Registered Events: (none) >>> Request: REQUEST_DATA_OBJECT >>> ALGORITHM_AFTER_FORWARD: 1 >>> FORWARD_DIRECTION: 0 >>> >>> >>> >>> >>> ERROR: In >>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, >>> line 754 >>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>> vtkInformation (0x2521130) >>> Debug: Off >>> Modified Time: 119319 >>> Reference Count: 1 >>> Registered Events: (none) >>> Request: REQUEST_DATA_OBJECT >>> ALGORITHM_AFTER_FORWARD: 1 >>> FORWARD_DIRECTION: 0 >>> >>> >>> >>> >>> On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: >>> >>> Hey Rich, >>> >>> Is this a matter of updating the VisIt bridge or the code in VisIt is old >>> too? >>> >>> What are the larger runs these folks do? And what is the timeframe? >>> >>> We are working on ADIOS readers and that may be another option. This is >>> where we currently plan on pushing for large scale IO needs. >>> >>> HDF5 is certainly another option. So is writing legacy VTK files from each >>> node. I'd guess Silo is another option too. >>> >>> It depends on the needs and scale at which they will be running. >>> >>> Best, >>> -berk >>> >>> On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >>>> >>>> Hi, >>>> I am wondering how to write out a set of VTK files for input into >>>> paraview. >>>> The code we are writing from is Miranda, an MPI code, and each processor >>>> writes out its subdomain individually. No ghost zones are written into the >>>> files. Perhaps they could be; I?m not sure about that part. >>>> Sometimes the data is curvilinear but usually rectilinear. >>>> Miranda is included in the VISIT_BRIDGE stuff but what?s in VISIT_BRIDGE >>>> for Miranda is old and the newer stuff doesn?t parse any more. >>>> Thanks! >>>> >>>> -- >>>> ?Richard Cook >>>> ? Lawrence Livermore National Laboratory >>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>> 7000 East Avenue, Livermore, CA, 94550, USA >>>> ? (office) (925) 423-9605 >>>> ? (fax) (925) 423-6961 >>>> --- >>>> Information Management & Graphics Grp., Services & Development Div., >>>> Integrated Computing & Communications Dept. >>>> (opinions expressed herein are mine and not those of LLNL) >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> -- >>> ?Richard Cook >>> ? Lawrence Livermore National Laboratory >>> Bldg-453 Rm-4024, Mail Stop L-557 >>> 7000 East Avenue, Livermore, CA, 94550, USA >>> ? (office) (925) 423-9605 >>> ? (fax) (925) 423-6961 >>> --- >>> Information Management & Graphics Grp., Services & Development Div., >>> Integrated Computing & Communications Dept. >>> (opinions expressed herein are mine and not those of LLNL) >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) From cook47 at llnl.gov Thu Sep 11 14:14:23 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 11 Sep 2014 18:14:23 +0000 Subject: [Paraview] writing block data in parallel for vtk readers In-Reply-To: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> Message-ID: <341160D2-6741-4638-8BD4-A5174BF43179@llnl.gov> Aha, it?s a python 2.6 vs. 2.7 issue. On Sep 11, 2014, at 11:09 AM, Cook, Rich wrote: > What?s strange about that line is that in our python on our clusters, that line compiles just fine. So perhaps there is a bug in whatever is compiling testing.py? > > On Sep 11, 2014, at 11:04 AM, Cook, Rich wrote: > >> Cannot build 4.2-RC1. I get this error. I?ve reported it before, but now it halts the build, so it needs to get fixed and I don?t know the answer: >> >> Compiling /usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py ... >> SyntaxError: ('invalid syntax', ('/usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in enumerate(test_module_browsers)})\n')) >> >> >> >> On Sep 10, 2014, at 10:04 PM, Utkarsh Ayachit wrote: >> >>> Rich, >>> >>> FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You >>> can try 4.2-RC1 to see if this was indeed a VisIt bridge being old >>> issue. >>> >>> Utkarsh >>> >>> On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: >>>> The code in VisIt is up to date; it?s just Paraview that seems behind the >>>> times. I am not able to completely convince myself of why but I suspect >>>> that?s the problem. The actual error shows up as some sort of VTK error. >>>> ? Rich >>>> >>>> >>>> ERROR: In >>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, >>>> line 754 >>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>> vtkInformation (0x2521130) >>>> Debug: Off >>>> Modified Time: 119319 >>>> Reference Count: 1 >>>> Registered Events: (none) >>>> Request: REQUEST_DATA_OBJECT >>>> ALGORITHM_AFTER_FORWARD: 1 >>>> FORWARD_DIRECTION: 0 >>>> >>>> >>>> >>>> >>>> ERROR: In >>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, >>>> line 754 >>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>> vtkInformation (0x2521130) >>>> Debug: Off >>>> Modified Time: 119319 >>>> Reference Count: 1 >>>> Registered Events: (none) >>>> Request: REQUEST_DATA_OBJECT >>>> ALGORITHM_AFTER_FORWARD: 1 >>>> FORWARD_DIRECTION: 0 >>>> >>>> >>>> >>>> >>>> On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: >>>> >>>> Hey Rich, >>>> >>>> Is this a matter of updating the VisIt bridge or the code in VisIt is old >>>> too? >>>> >>>> What are the larger runs these folks do? And what is the timeframe? >>>> >>>> We are working on ADIOS readers and that may be another option. This is >>>> where we currently plan on pushing for large scale IO needs. >>>> >>>> HDF5 is certainly another option. So is writing legacy VTK files from each >>>> node. I'd guess Silo is another option too. >>>> >>>> It depends on the needs and scale at which they will be running. >>>> >>>> Best, >>>> -berk >>>> >>>> On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >>>>> >>>>> Hi, >>>>> I am wondering how to write out a set of VTK files for input into >>>>> paraview. >>>>> The code we are writing from is Miranda, an MPI code, and each processor >>>>> writes out its subdomain individually. No ghost zones are written into the >>>>> files. Perhaps they could be; I?m not sure about that part. >>>>> Sometimes the data is curvilinear but usually rectilinear. >>>>> Miranda is included in the VISIT_BRIDGE stuff but what?s in VISIT_BRIDGE >>>>> for Miranda is old and the newer stuff doesn?t parse any more. >>>>> Thanks! >>>>> >>>>> -- >>>>> ?Richard Cook >>>>> ? Lawrence Livermore National Laboratory >>>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>>> 7000 East Avenue, Livermore, CA, 94550, USA >>>>> ? (office) (925) 423-9605 >>>>> ? (fax) (925) 423-6961 >>>>> --- >>>>> Information Management & Graphics Grp., Services & Development Div., >>>>> Integrated Computing & Communications Dept. >>>>> (opinions expressed herein are mine and not those of LLNL) >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> >>>> -- >>>> ?Richard Cook >>>> ? Lawrence Livermore National Laboratory >>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>> 7000 East Avenue, Livermore, CA, 94550, USA >>>> ? (office) (925) 423-9605 >>>> ? (fax) (925) 423-6961 >>>> --- >>>> Information Management & Graphics Grp., Services & Development Div., >>>> Integrated Computing & Communications Dept. >>>> (opinions expressed herein are mine and not those of LLNL) >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA >> ? (office) (925) 423-9605 >> ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) From wascott at sandia.gov Thu Sep 11 14:15:28 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 11 Sep 2014 18:15:28 +0000 Subject: [Paraview] [EXTERNAL] Re: writing block data in parallel for vtk readers In-Reply-To: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> Message-ID: <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> What version of Python is in your path for the builds? Our cluster builds are so amazingly old that I build and hard code a newer version of Python. Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cook, Rich Sent: Thursday, September 11, 2014 12:09 PM To: Utkarsh Ayachit Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] writing block data in parallel for vtk readers What?s strange about that line is that in our python on our clusters, that line compiles just fine. So perhaps there is a bug in whatever is compiling testing.py? On Sep 11, 2014, at 11:04 AM, Cook, Rich wrote: > Cannot build 4.2-RC1. I get this error. I?ve reported it before, but now it halts the build, so it needs to get fixed and I don?t know the answer: > > Compiling /usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py ... > SyntaxError: ('invalid syntax', > ('/usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib > /site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = > type("Enum", (), {k: i for i, k in > enumerate(test_module_browsers)})\n')) > > > > On Sep 10, 2014, at 10:04 PM, Utkarsh Ayachit wrote: > >> Rich, >> >> FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You >> can try 4.2-RC1 to see if this was indeed a VisIt bridge being old >> issue. >> >> Utkarsh >> >> On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: >>> The code in VisIt is up to date; it?s just Paraview that seems >>> behind the times. I am not able to completely convince myself of >>> why but I suspect that?s the problem. The actual error shows up as some sort of VTK error. >>> ? Rich >>> >>> >>> ERROR: In >>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Commo >>> n/ExecutionModel/vtkExecutive.cxx, >>> line 754 >>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>> vtkInformation (0x2521130) >>> Debug: Off >>> Modified Time: 119319 >>> Reference Count: 1 >>> Registered Events: (none) >>> Request: REQUEST_DATA_OBJECT >>> ALGORITHM_AFTER_FORWARD: 1 >>> FORWARD_DIRECTION: 0 >>> >>> >>> >>> >>> ERROR: In >>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Commo >>> n/ExecutionModel/vtkExecutive.cxx, >>> line 754 >>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>> vtkInformation (0x2521130) >>> Debug: Off >>> Modified Time: 119319 >>> Reference Count: 1 >>> Registered Events: (none) >>> Request: REQUEST_DATA_OBJECT >>> ALGORITHM_AFTER_FORWARD: 1 >>> FORWARD_DIRECTION: 0 >>> >>> >>> >>> >>> On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: >>> >>> Hey Rich, >>> >>> Is this a matter of updating the VisIt bridge or the code in VisIt >>> is old too? >>> >>> What are the larger runs these folks do? And what is the timeframe? >>> >>> We are working on ADIOS readers and that may be another option. This >>> is where we currently plan on pushing for large scale IO needs. >>> >>> HDF5 is certainly another option. So is writing legacy VTK files >>> from each node. I'd guess Silo is another option too. >>> >>> It depends on the needs and scale at which they will be running. >>> >>> Best, >>> -berk >>> >>> On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >>>> >>>> Hi, >>>> I am wondering how to write out a set of VTK files for input into >>>> paraview. >>>> The code we are writing from is Miranda, an MPI code, and each >>>> processor writes out its subdomain individually. No ghost zones >>>> are written into the files. Perhaps they could be; I?m not sure about that part. >>>> Sometimes the data is curvilinear but usually rectilinear. >>>> Miranda is included in the VISIT_BRIDGE stuff but what?s in >>>> VISIT_BRIDGE for Miranda is old and the newer stuff doesn?t parse any more. >>>> Thanks! >>>> >>>> -- >>>> ?Richard Cook >>>> ? Lawrence Livermore National Laboratory >>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>> 423-9605 ? (fax) (925) 423-6961 >>>> --- >>>> Information Management & Graphics Grp., Services & Development >>>> Div., Integrated Computing & Communications Dept. >>>> (opinions expressed herein are mine and not those of LLNL) >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> -- >>> ?Richard Cook >>> ? Lawrence Livermore National Laboratory >>> Bldg-453 Rm-4024, Mail Stop L-557 >>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>> 423-9605 ? (fax) (925) 423-6961 >>> --- >>> Information Management & Graphics Grp., Services & Development Div., >>> Integrated Computing & Communications Dept. >>> (opinions expressed herein are mine and not those of LLNL) >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Thu Sep 11 14:15:47 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 11 Sep 2014 14:15:47 -0400 Subject: [Paraview] writing block data in parallel for vtk readers In-Reply-To: <341160D2-6741-4638-8BD4-A5174BF43179@llnl.gov> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <341160D2-6741-4638-8BD4-A5174BF43179@llnl.gov> Message-ID: Yes, it's a Python version thing. It's been fixed since RC1 was tagged. You can turn off PARAVIEW_ENABLE_WEB CMake flag for now. Utkarsh On Thu, Sep 11, 2014 at 2:14 PM, Cook, Rich wrote: > Aha, it?s a python 2.6 vs. 2.7 issue. > > On Sep 11, 2014, at 11:09 AM, Cook, Rich wrote: > >> What?s strange about that line is that in our python on our clusters, that line compiles just fine. So perhaps there is a bug in whatever is compiling testing.py? >> >> On Sep 11, 2014, at 11:04 AM, Cook, Rich wrote: >> >>> Cannot build 4.2-RC1. I get this error. I?ve reported it before, but now it halts the build, so it needs to get fixed and I don?t know the answer: >>> >>> Compiling /usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py ... >>> SyntaxError: ('invalid syntax', ('/usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in enumerate(test_module_browsers)})\n')) >>> >>> >>> >>> On Sep 10, 2014, at 10:04 PM, Utkarsh Ayachit wrote: >>> >>>> Rich, >>>> >>>> FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You >>>> can try 4.2-RC1 to see if this was indeed a VisIt bridge being old >>>> issue. >>>> >>>> Utkarsh >>>> >>>> On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: >>>>> The code in VisIt is up to date; it?s just Paraview that seems behind the >>>>> times. I am not able to completely convince myself of why but I suspect >>>>> that?s the problem. The actual error shows up as some sort of VTK error. >>>>> ? Rich >>>>> >>>>> >>>>> ERROR: In >>>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, >>>>> line 754 >>>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>>> vtkInformation (0x2521130) >>>>> Debug: Off >>>>> Modified Time: 119319 >>>>> Reference Count: 1 >>>>> Registered Events: (none) >>>>> Request: REQUEST_DATA_OBJECT >>>>> ALGORITHM_AFTER_FORWARD: 1 >>>>> FORWARD_DIRECTION: 0 >>>>> >>>>> >>>>> >>>>> >>>>> ERROR: In >>>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, >>>>> line 754 >>>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>>> vtkInformation (0x2521130) >>>>> Debug: Off >>>>> Modified Time: 119319 >>>>> Reference Count: 1 >>>>> Registered Events: (none) >>>>> Request: REQUEST_DATA_OBJECT >>>>> ALGORITHM_AFTER_FORWARD: 1 >>>>> FORWARD_DIRECTION: 0 >>>>> >>>>> >>>>> >>>>> >>>>> On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: >>>>> >>>>> Hey Rich, >>>>> >>>>> Is this a matter of updating the VisIt bridge or the code in VisIt is old >>>>> too? >>>>> >>>>> What are the larger runs these folks do? And what is the timeframe? >>>>> >>>>> We are working on ADIOS readers and that may be another option. This is >>>>> where we currently plan on pushing for large scale IO needs. >>>>> >>>>> HDF5 is certainly another option. So is writing legacy VTK files from each >>>>> node. I'd guess Silo is another option too. >>>>> >>>>> It depends on the needs and scale at which they will be running. >>>>> >>>>> Best, >>>>> -berk >>>>> >>>>> On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >>>>>> >>>>>> Hi, >>>>>> I am wondering how to write out a set of VTK files for input into >>>>>> paraview. >>>>>> The code we are writing from is Miranda, an MPI code, and each processor >>>>>> writes out its subdomain individually. No ghost zones are written into the >>>>>> files. Perhaps they could be; I?m not sure about that part. >>>>>> Sometimes the data is curvilinear but usually rectilinear. >>>>>> Miranda is included in the VISIT_BRIDGE stuff but what?s in VISIT_BRIDGE >>>>>> for Miranda is old and the newer stuff doesn?t parse any more. >>>>>> Thanks! >>>>>> >>>>>> -- >>>>>> ?Richard Cook >>>>>> ? Lawrence Livermore National Laboratory >>>>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>>>> 7000 East Avenue, Livermore, CA, 94550, USA >>>>>> ? (office) (925) 423-9605 >>>>>> ? (fax) (925) 423-6961 >>>>>> --- >>>>>> Information Management & Graphics Grp., Services & Development Div., >>>>>> Integrated Computing & Communications Dept. >>>>>> (opinions expressed herein are mine and not those of LLNL) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> >>>>> >>>>> -- >>>>> ?Richard Cook >>>>> ? Lawrence Livermore National Laboratory >>>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>>> 7000 East Avenue, Livermore, CA, 94550, USA >>>>> ? (office) (925) 423-9605 >>>>> ? (fax) (925) 423-6961 >>>>> --- >>>>> Information Management & Graphics Grp., Services & Development Div., >>>>> Integrated Computing & Communications Dept. >>>>> (opinions expressed herein are mine and not those of LLNL) >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>> >>> -- >>> ?Richard Cook >>> ? Lawrence Livermore National Laboratory >>> Bldg-453 Rm-4024, Mail Stop L-557 >>> 7000 East Avenue, Livermore, CA, 94550, USA >>> ? (office) (925) 423-9605 >>> ? (fax) (925) 423-6961 >>> --- >>> Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. >>> (opinions expressed herein are mine and not those of LLNL) >>> >>> >>> >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA >> ? (office) (925) 423-9605 >> ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > From cook47 at llnl.gov Thu Sep 11 14:34:29 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 11 Sep 2014 18:34:29 +0000 Subject: [Paraview] [EXTERNAL] Re: writing block data in parallel for vtk readers In-Reply-To: <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> Message-ID: <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> Alan, how do you hard code a newer version? I prefer not to turn off the web stuff On Sep 11, 2014, at 11:15 AM, Scott, W Alan wrote: > What version of Python is in your path for the builds? Our cluster builds are so amazingly old that I build and hard code a newer version of Python. > > Alan > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cook, Rich > Sent: Thursday, September 11, 2014 12:09 PM > To: Utkarsh Ayachit > Cc: paraview at paraview.org > Subject: [EXTERNAL] Re: [Paraview] writing block data in parallel for vtk readers > > What?s strange about that line is that in our python on our clusters, that line compiles just fine. So perhaps there is a bug in whatever is compiling testing.py? > > On Sep 11, 2014, at 11:04 AM, Cook, Rich wrote: > >> Cannot build 4.2-RC1. I get this error. I?ve reported it before, but now it halts the build, so it needs to get fixed and I don?t know the answer: >> >> Compiling /usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py ... >> SyntaxError: ('invalid syntax', >> ('/usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib >> /site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = >> type("Enum", (), {k: i for i, k in >> enumerate(test_module_browsers)})\n')) >> >> >> >> On Sep 10, 2014, at 10:04 PM, Utkarsh Ayachit wrote: >> >>> Rich, >>> >>> FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You >>> can try 4.2-RC1 to see if this was indeed a VisIt bridge being old >>> issue. >>> >>> Utkarsh >>> >>> On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: >>>> The code in VisIt is up to date; it?s just Paraview that seems >>>> behind the times. I am not able to completely convince myself of >>>> why but I suspect that?s the problem. The actual error shows up as some sort of VTK error. >>>> ? Rich >>>> >>>> >>>> ERROR: In >>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Commo >>>> n/ExecutionModel/vtkExecutive.cxx, >>>> line 754 >>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>> vtkInformation (0x2521130) >>>> Debug: Off >>>> Modified Time: 119319 >>>> Reference Count: 1 >>>> Registered Events: (none) >>>> Request: REQUEST_DATA_OBJECT >>>> ALGORITHM_AFTER_FORWARD: 1 >>>> FORWARD_DIRECTION: 0 >>>> >>>> >>>> >>>> >>>> ERROR: In >>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Commo >>>> n/ExecutionModel/vtkExecutive.cxx, >>>> line 754 >>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>> vtkInformation (0x2521130) >>>> Debug: Off >>>> Modified Time: 119319 >>>> Reference Count: 1 >>>> Registered Events: (none) >>>> Request: REQUEST_DATA_OBJECT >>>> ALGORITHM_AFTER_FORWARD: 1 >>>> FORWARD_DIRECTION: 0 >>>> >>>> >>>> >>>> >>>> On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: >>>> >>>> Hey Rich, >>>> >>>> Is this a matter of updating the VisIt bridge or the code in VisIt >>>> is old too? >>>> >>>> What are the larger runs these folks do? And what is the timeframe? >>>> >>>> We are working on ADIOS readers and that may be another option. This >>>> is where we currently plan on pushing for large scale IO needs. >>>> >>>> HDF5 is certainly another option. So is writing legacy VTK files >>>> from each node. I'd guess Silo is another option too. >>>> >>>> It depends on the needs and scale at which they will be running. >>>> >>>> Best, >>>> -berk >>>> >>>> On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >>>>> >>>>> Hi, >>>>> I am wondering how to write out a set of VTK files for input into >>>>> paraview. >>>>> The code we are writing from is Miranda, an MPI code, and each >>>>> processor writes out its subdomain individually. No ghost zones >>>>> are written into the files. Perhaps they could be; I?m not sure about that part. >>>>> Sometimes the data is curvilinear but usually rectilinear. >>>>> Miranda is included in the VISIT_BRIDGE stuff but what?s in >>>>> VISIT_BRIDGE for Miranda is old and the newer stuff doesn?t parse any more. >>>>> Thanks! >>>>> >>>>> -- >>>>> ?Richard Cook >>>>> ? Lawrence Livermore National Laboratory >>>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>>> 423-9605 ? (fax) (925) 423-6961 >>>>> --- >>>>> Information Management & Graphics Grp., Services & Development >>>>> Div., Integrated Computing & Communications Dept. >>>>> (opinions expressed herein are mine and not those of LLNL) >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> >>>> -- >>>> ?Richard Cook >>>> ? Lawrence Livermore National Laboratory >>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>> 423-9605 ? (fax) (925) 423-6961 >>>> --- >>>> Information Management & Graphics Grp., Services & Development Div., >>>> Integrated Computing & Communications Dept. >>>> (opinions expressed herein are mine and not those of LLNL) >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA >> ? (office) (925) 423-9605 >> ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) From cook47 at llnl.gov Thu Sep 11 14:42:47 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 11 Sep 2014 18:42:47 +0000 Subject: [Paraview] [EXTERNAL] Re: writing block data in parallel for vtk readers In-Reply-To: <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> Message-ID: <09E99FAA-FF57-4DB1-AA66-AE1E0BAFF5C5@llnl.gov> Found it, your genius continues to amaze me. On Sep 11, 2014, at 11:34 AM, Cook, Rich wrote: > Alan, how do you hard code a newer version? > I prefer not to turn off the web stuff > > On Sep 11, 2014, at 11:15 AM, Scott, W Alan wrote: > >> What version of Python is in your path for the builds? Our cluster builds are so amazingly old that I build and hard code a newer version of Python. >> >> Alan >> >> -----Original Message----- >> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cook, Rich >> Sent: Thursday, September 11, 2014 12:09 PM >> To: Utkarsh Ayachit >> Cc: paraview at paraview.org >> Subject: [EXTERNAL] Re: [Paraview] writing block data in parallel for vtk readers >> >> What?s strange about that line is that in our python on our clusters, that line compiles just fine. So perhaps there is a bug in whatever is compiling testing.py? >> >> On Sep 11, 2014, at 11:04 AM, Cook, Rich wrote: >> >>> Cannot build 4.2-RC1. I get this error. I?ve reported it before, but now it halts the build, so it needs to get fixed and I don?t know the answer: >>> >>> Compiling /usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py ... >>> SyntaxError: ('invalid syntax', >>> ('/usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib >>> /site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = >>> type("Enum", (), {k: i for i, k in >>> enumerate(test_module_browsers)})\n')) >>> >>> >>> >>> On Sep 10, 2014, at 10:04 PM, Utkarsh Ayachit wrote: >>> >>>> Rich, >>>> >>>> FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You >>>> can try 4.2-RC1 to see if this was indeed a VisIt bridge being old >>>> issue. >>>> >>>> Utkarsh >>>> >>>> On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: >>>>> The code in VisIt is up to date; it?s just Paraview that seems >>>>> behind the times. I am not able to completely convince myself of >>>>> why but I suspect that?s the problem. The actual error shows up as some sort of VTK error. >>>>> ? Rich >>>>> >>>>> >>>>> ERROR: In >>>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Commo >>>>> n/ExecutionModel/vtkExecutive.cxx, >>>>> line 754 >>>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>>> vtkInformation (0x2521130) >>>>> Debug: Off >>>>> Modified Time: 119319 >>>>> Reference Count: 1 >>>>> Registered Events: (none) >>>>> Request: REQUEST_DATA_OBJECT >>>>> ALGORITHM_AFTER_FORWARD: 1 >>>>> FORWARD_DIRECTION: 0 >>>>> >>>>> >>>>> >>>>> >>>>> ERROR: In >>>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Commo >>>>> n/ExecutionModel/vtkExecutive.cxx, >>>>> line 754 >>>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>>> vtkInformation (0x2521130) >>>>> Debug: Off >>>>> Modified Time: 119319 >>>>> Reference Count: 1 >>>>> Registered Events: (none) >>>>> Request: REQUEST_DATA_OBJECT >>>>> ALGORITHM_AFTER_FORWARD: 1 >>>>> FORWARD_DIRECTION: 0 >>>>> >>>>> >>>>> >>>>> >>>>> On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: >>>>> >>>>> Hey Rich, >>>>> >>>>> Is this a matter of updating the VisIt bridge or the code in VisIt >>>>> is old too? >>>>> >>>>> What are the larger runs these folks do? And what is the timeframe? >>>>> >>>>> We are working on ADIOS readers and that may be another option. This >>>>> is where we currently plan on pushing for large scale IO needs. >>>>> >>>>> HDF5 is certainly another option. So is writing legacy VTK files >>>>> from each node. I'd guess Silo is another option too. >>>>> >>>>> It depends on the needs and scale at which they will be running. >>>>> >>>>> Best, >>>>> -berk >>>>> >>>>> On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >>>>>> >>>>>> Hi, >>>>>> I am wondering how to write out a set of VTK files for input into >>>>>> paraview. >>>>>> The code we are writing from is Miranda, an MPI code, and each >>>>>> processor writes out its subdomain individually. No ghost zones >>>>>> are written into the files. Perhaps they could be; I?m not sure about that part. >>>>>> Sometimes the data is curvilinear but usually rectilinear. >>>>>> Miranda is included in the VISIT_BRIDGE stuff but what?s in >>>>>> VISIT_BRIDGE for Miranda is old and the newer stuff doesn?t parse any more. >>>>>> Thanks! >>>>>> >>>>>> -- >>>>>> ?Richard Cook >>>>>> ? Lawrence Livermore National Laboratory >>>>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>>>> 423-9605 ? (fax) (925) 423-6961 >>>>>> --- >>>>>> Information Management & Graphics Grp., Services & Development >>>>>> Div., Integrated Computing & Communications Dept. >>>>>> (opinions expressed herein are mine and not those of LLNL) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> >>>>> >>>>> -- >>>>> ?Richard Cook >>>>> ? Lawrence Livermore National Laboratory >>>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>>> 423-9605 ? (fax) (925) 423-6961 >>>>> --- >>>>> Information Management & Graphics Grp., Services & Development Div., >>>>> Integrated Computing & Communications Dept. >>>>> (opinions expressed herein are mine and not those of LLNL) >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>> >>> -- >>> ?Richard Cook >>> ? Lawrence Livermore National Laboratory >>> Bldg-453 Rm-4024, Mail Stop L-557 >>> 7000 East Avenue, Livermore, CA, 94550, USA >>> ? (office) (925) 423-9605 >>> ? (fax) (925) 423-6961 >>> --- >>> Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. >>> (opinions expressed herein are mine and not those of LLNL) >>> >>> >>> >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA >> ? (office) (925) 423-9605 >> ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) From wascott at sandia.gov Thu Sep 11 14:45:57 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 11 Sep 2014 18:45:57 +0000 Subject: [Paraview] [EXTERNAL] Re: writing block data in parallel for vtk readers In-Reply-To: <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> Message-ID: <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> What I do is as follows (probably overkill, but hey), in Python path = os.environ.get('PATH') os.environ['PATH']=pythonInstallDir+'/bin/:'+path path = os.environ.get('LD_LIBRARY_PATH') os.environ['LD_LIBRARY_PATH']=pythonInstallDir+'/lib/:'+path path = os.environ.get('PYTHONPATH') if path is None: os.environ['PYTHONPATH']=pythonInstallDir+'/lib/python2.7:' else: os.environ['PYTHONPATH']=pythonInstallDir+'/lib/python2.7:'+path if (buildPython == 'true') : cMakeVars = cMakeVars +\ '-DPARAVIEW_ENABLE_PYTHON:BOOL=ON ' else : cMakeVars = cMakeVars +\ '-DPARAVIEW_ENABLE_PYTHON:BOOL=OFF ' cMakeVars = cMakeVars +\ '-DPYTHON_EXECUTABLE:FILEPATH='+pythonInstallDir+'/bin/python '+\ '-DPYTHON_INCLUDE_PATH:PATH='+pythonInstallDir+'/include/python2.7/ '+\ '-DPYTHON_LIBRARY:FILEPATH='+pythonInstallDir+'/lib/libpython2.7.so ' Alan -----Original Message----- From: Cook, Rich [mailto:cook47 at llnl.gov] Sent: Thursday, September 11, 2014 12:34 PM To: Scott, W Alan Cc: Utkarsh Ayachit; paraview at paraview.org Subject: Re: [EXTERNAL] Re: [Paraview] writing block data in parallel for vtk readers Alan, how do you hard code a newer version? I prefer not to turn off the web stuff On Sep 11, 2014, at 11:15 AM, Scott, W Alan wrote: > What version of Python is in your path for the builds? Our cluster builds are so amazingly old that I build and hard code a newer version of Python. > > Alan > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of > Cook, Rich > Sent: Thursday, September 11, 2014 12:09 PM > To: Utkarsh Ayachit > Cc: paraview at paraview.org > Subject: [EXTERNAL] Re: [Paraview] writing block data in parallel for > vtk readers > > What?s strange about that line is that in our python on our clusters, that line compiles just fine. So perhaps there is a bug in whatever is compiling testing.py? > > On Sep 11, 2014, at 11:04 AM, Cook, Rich wrote: > >> Cannot build 4.2-RC1. I get this error. I?ve reported it before, but now it halts the build, so it needs to get fixed and I don?t know the answer: >> >> Compiling /usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py ... >> SyntaxError: ('invalid syntax', >> ('/usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/li >> b /site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = >> type("Enum", (), {k: i for i, k in >> enumerate(test_module_browsers)})\n')) >> >> >> >> On Sep 10, 2014, at 10:04 PM, Utkarsh Ayachit wrote: >> >>> Rich, >>> >>> FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You >>> can try 4.2-RC1 to see if this was indeed a VisIt bridge being old >>> issue. >>> >>> Utkarsh >>> >>> On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: >>>> The code in VisIt is up to date; it?s just Paraview that seems >>>> behind the times. I am not able to completely convince myself of >>>> why but I suspect that?s the problem. The actual error shows up as some sort of VTK error. >>>> ? Rich >>>> >>>> >>>> ERROR: In >>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Comm >>>> o >>>> n/ExecutionModel/vtkExecutive.cxx, >>>> line 754 >>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>> vtkInformation (0x2521130) >>>> Debug: Off >>>> Modified Time: 119319 >>>> Reference Count: 1 >>>> Registered Events: (none) >>>> Request: REQUEST_DATA_OBJECT >>>> ALGORITHM_AFTER_FORWARD: 1 >>>> FORWARD_DIRECTION: 0 >>>> >>>> >>>> >>>> >>>> ERROR: In >>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Comm >>>> o >>>> n/ExecutionModel/vtkExecutive.cxx, >>>> line 754 >>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>> vtkInformation (0x2521130) >>>> Debug: Off >>>> Modified Time: 119319 >>>> Reference Count: 1 >>>> Registered Events: (none) >>>> Request: REQUEST_DATA_OBJECT >>>> ALGORITHM_AFTER_FORWARD: 1 >>>> FORWARD_DIRECTION: 0 >>>> >>>> >>>> >>>> >>>> On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: >>>> >>>> Hey Rich, >>>> >>>> Is this a matter of updating the VisIt bridge or the code in VisIt >>>> is old too? >>>> >>>> What are the larger runs these folks do? And what is the timeframe? >>>> >>>> We are working on ADIOS readers and that may be another option. >>>> This is where we currently plan on pushing for large scale IO needs. >>>> >>>> HDF5 is certainly another option. So is writing legacy VTK files >>>> from each node. I'd guess Silo is another option too. >>>> >>>> It depends on the needs and scale at which they will be running. >>>> >>>> Best, >>>> -berk >>>> >>>> On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >>>>> >>>>> Hi, >>>>> I am wondering how to write out a set of VTK files for input into >>>>> paraview. >>>>> The code we are writing from is Miranda, an MPI code, and each >>>>> processor writes out its subdomain individually. No ghost zones >>>>> are written into the files. Perhaps they could be; I?m not sure about that part. >>>>> Sometimes the data is curvilinear but usually rectilinear. >>>>> Miranda is included in the VISIT_BRIDGE stuff but what?s in >>>>> VISIT_BRIDGE for Miranda is old and the newer stuff doesn?t parse any more. >>>>> Thanks! >>>>> >>>>> -- >>>>> ?Richard Cook >>>>> ? Lawrence Livermore National Laboratory >>>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>>> 423-9605 ? (fax) (925) 423-6961 >>>>> --- >>>>> Information Management & Graphics Grp., Services & Development >>>>> Div., Integrated Computing & Communications Dept. >>>>> (opinions expressed herein are mine and not those of LLNL) >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> >>>> -- >>>> ?Richard Cook >>>> ? Lawrence Livermore National Laboratory >>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>> 423-9605 ? (fax) (925) 423-6961 >>>> --- >>>> Information Management & Graphics Grp., Services & Development >>>> Div., Integrated Computing & Communications Dept. >>>> (opinions expressed herein are mine and not those of LLNL) >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >> 423-9605 ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) From wascott at sandia.gov Thu Sep 11 14:55:59 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 11 Sep 2014 18:55:59 +0000 Subject: [Paraview] [EXTERNAL] Re: writing block data in parallel for vtk readers In-Reply-To: <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> Message-ID: <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> Slight cut and paste error. I fixed it below. -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Thursday, September 11, 2014 12:46 PM To: Cook, Rich D (External Contacts) Cc: paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] Re: writing block data in parallel for vtk readers What I do is as follows (probably overkill, but hey), in Python path = os.environ.get('PATH') os.environ['PATH']=pythonInstallDir+'/bin/:'+path path = os.environ.get('LD_LIBRARY_PATH') os.environ['LD_LIBRARY_PATH']=pythonInstallDir+'/lib/:'+path path = os.environ.get('PYTHONPATH') if path is None: os.environ['PYTHONPATH']=pythonInstallDir+'/lib/python2.7:' else: os.environ['PYTHONPATH']=pythonInstallDir+'/lib/python2.7:'+path if (buildPython == 'true') : cMakeVars = cMakeVars +\ '-DPARAVIEW_ENABLE_PYTHON:BOOL=ON ' else : cMakeVars = cMakeVars +\ '-DPARAVIEW_ENABLE_PYTHON:BOOL=OFF ' cMakeVars = cMakeVars +\ '-DPYTHON_EXECUTABLE:FILEPATH='+pythonInstallDir+'/bin/python '+\ '-DPYTHON_INCLUDE_PATH:PATH='+pythonInstallDir+'/include/python2.7/ '+\ '-DPYTHON_LIBRARY:FILEPATH='+pythonInstallDir+'/lib/libpython2.7.so ' Alan -----Original Message----- From: Cook, Rich [mailto:cook47 at llnl.gov] Sent: Thursday, September 11, 2014 12:34 PM To: Scott, W Alan Cc: Utkarsh Ayachit; paraview at paraview.org Subject: Re: [EXTERNAL] Re: [Paraview] writing block data in parallel for vtk readers Alan, how do you hard code a newer version? I prefer not to turn off the web stuff On Sep 11, 2014, at 11:15 AM, Scott, W Alan wrote: > What version of Python is in your path for the builds? Our cluster builds are so amazingly old that I build and hard code a newer version of Python. > > Alan > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of > Cook, Rich > Sent: Thursday, September 11, 2014 12:09 PM > To: Utkarsh Ayachit > Cc: paraview at paraview.org > Subject: [EXTERNAL] Re: [Paraview] writing block data in parallel for > vtk readers > > What?s strange about that line is that in our python on our clusters, that line compiles just fine. So perhaps there is a bug in whatever is compiling testing.py? > > On Sep 11, 2014, at 11:04 AM, Cook, Rich wrote: > >> Cannot build 4.2-RC1. I get this error. I?ve reported it before, but now it halts the build, so it needs to get fixed and I don?t know the answer: >> >> Compiling /usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py ... >> SyntaxError: ('invalid syntax', >> ('/usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/li >> b /site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = >> type("Enum", (), {k: i for i, k in >> enumerate(test_module_browsers)})\n')) >> >> >> >> On Sep 10, 2014, at 10:04 PM, Utkarsh Ayachit wrote: >> >>> Rich, >>> >>> FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You >>> can try 4.2-RC1 to see if this was indeed a VisIt bridge being old >>> issue. >>> >>> Utkarsh >>> >>> On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: >>>> The code in VisIt is up to date; it?s just Paraview that seems >>>> behind the times. I am not able to completely convince myself of >>>> why but I suspect that?s the problem. The actual error shows up as some sort of VTK error. >>>> ? Rich >>>> >>>> >>>> ERROR: In >>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Comm >>>> o >>>> n/ExecutionModel/vtkExecutive.cxx, >>>> line 754 >>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>> vtkInformation (0x2521130) >>>> Debug: Off >>>> Modified Time: 119319 >>>> Reference Count: 1 >>>> Registered Events: (none) >>>> Request: REQUEST_DATA_OBJECT >>>> ALGORITHM_AFTER_FORWARD: 1 >>>> FORWARD_DIRECTION: 0 >>>> >>>> >>>> >>>> >>>> ERROR: In >>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Comm >>>> o >>>> n/ExecutionModel/vtkExecutive.cxx, >>>> line 754 >>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>> vtkInformation (0x2521130) >>>> Debug: Off >>>> Modified Time: 119319 >>>> Reference Count: 1 >>>> Registered Events: (none) >>>> Request: REQUEST_DATA_OBJECT >>>> ALGORITHM_AFTER_FORWARD: 1 >>>> FORWARD_DIRECTION: 0 >>>> >>>> >>>> >>>> >>>> On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: >>>> >>>> Hey Rich, >>>> >>>> Is this a matter of updating the VisIt bridge or the code in VisIt >>>> is old too? >>>> >>>> What are the larger runs these folks do? And what is the timeframe? >>>> >>>> We are working on ADIOS readers and that may be another option. >>>> This is where we currently plan on pushing for large scale IO needs. >>>> >>>> HDF5 is certainly another option. So is writing legacy VTK files >>>> from each node. I'd guess Silo is another option too. >>>> >>>> It depends on the needs and scale at which they will be running. >>>> >>>> Best, >>>> -berk >>>> >>>> On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >>>>> >>>>> Hi, >>>>> I am wondering how to write out a set of VTK files for input into >>>>> paraview. >>>>> The code we are writing from is Miranda, an MPI code, and each >>>>> processor writes out its subdomain individually. No ghost zones >>>>> are written into the files. Perhaps they could be; I?m not sure about that part. >>>>> Sometimes the data is curvilinear but usually rectilinear. >>>>> Miranda is included in the VISIT_BRIDGE stuff but what?s in >>>>> VISIT_BRIDGE for Miranda is old and the newer stuff doesn?t parse any more. >>>>> Thanks! >>>>> >>>>> -- >>>>> ?Richard Cook >>>>> ? Lawrence Livermore National Laboratory >>>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>>> 423-9605 ? (fax) (925) 423-6961 >>>>> --- >>>>> Information Management & Graphics Grp., Services & Development >>>>> Div., Integrated Computing & Communications Dept. >>>>> (opinions expressed herein are mine and not those of LLNL) >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> >>>> -- >>>> ?Richard Cook >>>> ? Lawrence Livermore National Laboratory >>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>> 423-9605 ? (fax) (925) 423-6961 >>>> --- >>>> Information Management & Graphics Grp., Services & Development >>>> Div., Integrated Computing & Communications Dept. >>>> (opinions expressed herein are mine and not those of LLNL) >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >> 423-9605 ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From cook47 at llnl.gov Thu Sep 11 18:12:27 2014 From: cook47 at llnl.gov (Cook, Rich) Date: Thu, 11 Sep 2014 22:12:27 +0000 Subject: [Paraview] [EXTERNAL] Re: writing block data in parallel for vtk readers In-Reply-To: <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> Message-ID: <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> It compiles with python2.7 for me now, thanks On Sep 11, 2014, at 11:55 AM, Scott, W Alan wrote: > Slight cut and paste error. I fixed it below. > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan > Sent: Thursday, September 11, 2014 12:46 PM > To: Cook, Rich D (External Contacts) > Cc: paraview at paraview.org > Subject: Re: [Paraview] [EXTERNAL] Re: writing block data in parallel for vtk readers > > What I do is as follows (probably overkill, but hey), in Python > > path = os.environ.get('PATH') > os.environ['PATH']=pythonInstallDir+'/bin/:'+path > > path = os.environ.get('LD_LIBRARY_PATH') > os.environ['LD_LIBRARY_PATH']=pythonInstallDir+'/lib/:'+path > > path = os.environ.get('PYTHONPATH') > if path is None: > os.environ['PYTHONPATH']=pythonInstallDir+'/lib/python2.7:' > else: > os.environ['PYTHONPATH']=pythonInstallDir+'/lib/python2.7:'+path > > > if (buildPython == 'true') : > cMakeVars = cMakeVars +\ > '-DPARAVIEW_ENABLE_PYTHON:BOOL=ON ' > else : > cMakeVars = cMakeVars +\ > '-DPARAVIEW_ENABLE_PYTHON:BOOL=OFF ' > > cMakeVars = cMakeVars +\ > '-DPYTHON_EXECUTABLE:FILEPATH='+pythonInstallDir+'/bin/python '+\ > '-DPYTHON_INCLUDE_PATH:PATH='+pythonInstallDir+'/include/python2.7/ '+\ > '-DPYTHON_LIBRARY:FILEPATH='+pythonInstallDir+'/lib/libpython2.7.so ' > > Alan > > > -----Original Message----- > From: Cook, Rich [mailto:cook47 at llnl.gov] > Sent: Thursday, September 11, 2014 12:34 PM > To: Scott, W Alan > Cc: Utkarsh Ayachit; paraview at paraview.org > Subject: Re: [EXTERNAL] Re: [Paraview] writing block data in parallel for vtk readers > > Alan, how do you hard code a newer version? > I prefer not to turn off the web stuff > > On Sep 11, 2014, at 11:15 AM, Scott, W Alan wrote: > >> What version of Python is in your path for the builds? Our cluster builds are so amazingly old that I build and hard code a newer version of Python. >> >> Alan >> >> -----Original Message----- >> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of >> Cook, Rich >> Sent: Thursday, September 11, 2014 12:09 PM >> To: Utkarsh Ayachit >> Cc: paraview at paraview.org >> Subject: [EXTERNAL] Re: [Paraview] writing block data in parallel for >> vtk readers >> >> What?s strange about that line is that in our python on our clusters, that line compiles just fine. So perhaps there is a bug in whatever is compiling testing.py? >> >> On Sep 11, 2014, at 11:04 AM, Cook, Rich wrote: >> >>> Cannot build 4.2-RC1. I get this error. I?ve reported it before, but now it halts the build, so it needs to get fixed and I don?t know the answer: >>> >>> Compiling /usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/lib/site-packages/vtk/web/testing.py ... >>> SyntaxError: ('invalid syntax', >>> ('/usr/local/tools/paraview-opengl-4.2.0/src/ParaView-v4.2.0-Build/li >>> b /site-packages/vtk/web/testing.py', 76, 47, 'TestModuleBrowsers = >>> type("Enum", (), {k: i for i, k in >>> enumerate(test_module_browsers)})\n')) >>> >>> >>> >>> On Sep 10, 2014, at 10:04 PM, Utkarsh Ayachit wrote: >>> >>>> Rich, >>>> >>>> FYI, the VisIt bridge was updated to VisIt 2.7.0 soon after 4.1. You >>>> can try 4.2-RC1 to see if this was indeed a VisIt bridge being old >>>> issue. >>>> >>>> Utkarsh >>>> >>>> On Wed, Sep 10, 2014 at 8:19 PM, Cook, Rich wrote: >>>>> The code in VisIt is up to date; it?s just Paraview that seems >>>>> behind the times. I am not able to completely convince myself of >>>>> why but I suspect that?s the problem. The actual error shows up as some sort of VTK error. >>>>> ? Rich >>>>> >>>>> >>>>> ERROR: In >>>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Comm >>>>> o >>>>> n/ExecutionModel/vtkExecutive.cxx, >>>>> line 754 >>>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>>> vtkInformation (0x2521130) >>>>> Debug: Off >>>>> Modified Time: 119319 >>>>> Reference Count: 1 >>>>> Registered Events: (none) >>>>> Request: REQUEST_DATA_OBJECT >>>>> ALGORITHM_AFTER_FORWARD: 1 >>>>> FORWARD_DIRECTION: 0 >>>>> >>>>> >>>>> >>>>> >>>>> ERROR: In >>>>> /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Comm >>>>> o >>>>> n/ExecutionModel/vtkExecutive.cxx, >>>>> line 754 >>>>> vtkPVCompositeDataPipeline (0x252ff00): Algorithm >>>>> vtkVisItMirandaReader(0x25342b0) returned failure for request: >>>>> vtkInformation (0x2521130) >>>>> Debug: Off >>>>> Modified Time: 119319 >>>>> Reference Count: 1 >>>>> Registered Events: (none) >>>>> Request: REQUEST_DATA_OBJECT >>>>> ALGORITHM_AFTER_FORWARD: 1 >>>>> FORWARD_DIRECTION: 0 >>>>> >>>>> >>>>> >>>>> >>>>> On Sep 10, 2014, at 4:55 PM, Berk Geveci wrote: >>>>> >>>>> Hey Rich, >>>>> >>>>> Is this a matter of updating the VisIt bridge or the code in VisIt >>>>> is old too? >>>>> >>>>> What are the larger runs these folks do? And what is the timeframe? >>>>> >>>>> We are working on ADIOS readers and that may be another option. >>>>> This is where we currently plan on pushing for large scale IO needs. >>>>> >>>>> HDF5 is certainly another option. So is writing legacy VTK files >>>>> from each node. I'd guess Silo is another option too. >>>>> >>>>> It depends on the needs and scale at which they will be running. >>>>> >>>>> Best, >>>>> -berk >>>>> >>>>> On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich wrote: >>>>>> >>>>>> Hi, >>>>>> I am wondering how to write out a set of VTK files for input into >>>>>> paraview. >>>>>> The code we are writing from is Miranda, an MPI code, and each >>>>>> processor writes out its subdomain individually. No ghost zones >>>>>> are written into the files. Perhaps they could be; I?m not sure about that part. >>>>>> Sometimes the data is curvilinear but usually rectilinear. >>>>>> Miranda is included in the VISIT_BRIDGE stuff but what?s in >>>>>> VISIT_BRIDGE for Miranda is old and the newer stuff doesn?t parse any more. >>>>>> Thanks! >>>>>> >>>>>> -- >>>>>> ?Richard Cook >>>>>> ? Lawrence Livermore National Laboratory >>>>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>>>> 423-9605 ? (fax) (925) 423-6961 >>>>>> --- >>>>>> Information Management & Graphics Grp., Services & Development >>>>>> Div., Integrated Computing & Communications Dept. >>>>>> (opinions expressed herein are mine and not those of LLNL) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> >>>>> >>>>> -- >>>>> ?Richard Cook >>>>> ? Lawrence Livermore National Laboratory >>>>> Bldg-453 Rm-4024, Mail Stop L-557 >>>>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>>>> 423-9605 ? (fax) (925) 423-6961 >>>>> --- >>>>> Information Management & Graphics Grp., Services & Development >>>>> Div., Integrated Computing & Communications Dept. >>>>> (opinions expressed herein are mine and not those of LLNL) >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>> >>> -- >>> ?Richard Cook >>> ? Lawrence Livermore National Laboratory >>> Bldg-453 Rm-4024, Mail Stop L-557 >>> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) >>> 423-9605 ? (fax) (925) 423-6961 >>> --- >>> Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. >>> (opinions expressed herein are mine and not those of LLNL) >>> >>> >>> >> >> -- >> ?Richard Cook >> ? Lawrence Livermore National Laboratory >> Bldg-453 Rm-4024, Mail Stop L-557 >> 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 >> ? (fax) (925) 423-6961 >> --- >> Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. >> (opinions expressed herein are mine and not those of LLNL) >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > -- > ?Richard Cook > ? Lawrence Livermore National Laboratory > Bldg-453 Rm-4024, Mail Stop L-557 > 7000 East Avenue, Livermore, CA, 94550, USA > ? (office) (925) 423-9605 > ? (fax) (925) 423-6961 > --- > Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. > (opinions expressed herein are mine and not those of LLNL) > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) From utkarsh.ayachit at kitware.com Fri Sep 12 14:09:10 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 12 Sep 2014 14:09:10 -0400 Subject: [Paraview] vts file format In-Reply-To: <1410532558.15566.YahooMailNeo@web121206.mail.ne1.yahoo.com> References: <1410382591.84710.YahooMailNeo@web121202.mail.ne1.yahoo.com> <1410532558.15566.YahooMailNeo@web121206.mail.ne1.yahoo.com> Message-ID: I don't think the file you attached is correct. Attached is an example of how a VTI file should look. On Fri, Sep 12, 2014 at 10:35 AM, Mohammad KONESHLOO wrote: > Thanks Utkrash, > > I read about the format used for image (vti), I tried to make a simple > example as follow: but it does not work, I've chose (loop o X then Y then Z > I mean (For X {For Y {For Z{}}}). > I think the Python code create a such file too, But I doesn't work > > > Origin=?1 1 1? Spacing=?1 1 1?> > > 1 1 1 > 1 1 2 > 1 2 1 > 1 2 2 > 1 3 1 > 1 3 2 > 1 4 1 > 1 4 2 > 2 1 1 > 2 1 2 > 2 2 1 > 2 2 2 > 2 3 1 > 2 3 2 > 2 4 1 > 2 4 2 > 3 1 1 > 3 1 2 > 3 2 1 > 3 2 2 > 3 3 1 > 3 3 2 > 3 4 1 > 3 4 2 > 4 1 1 > 4 1 2 > 4 2 1 > 4 2 2 > 4 3 1 > 4 3 2 > 4 4 1 > 4 4 2 > 5 1 1 > 5 1 2 > 5 2 1 > 5 2 2 > 5 3 1 > 5 3 2 > 5 4 1 > 5 4 2 > > 1 > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 > 10 > 11 > 12 > 13 > 14 > 15 > 16 > 17 > 18 > 19 > 20 > 21 > 22 > 23 > 24 > 25 > 26 > 27 > 28 > 29 > 30 > 31 > 32 > 33 > 34 > 35 > 36 > 37 > 38 > 39 > 40 > > > > > > Thanks in advance > > > > On Thursday, September 11, 2014 1:49 AM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > > > Are you sure it's a "structured grid" or is an "image data"? Refer to this > for difference between the two: > http://www.paraview.org/Wiki/ParaView/Users_Guide/VTK_Data_Model > > Programmable filer may be the easiest way to go. Attached is an extract > from the ParaView User's Guide that's currently being updated. A > combination of recipes shown in Sections 14.2.1 and 14.2.4 is what should > help. > > Utkarsh > ? > ParaViewUsersGuideExtract.pdf > > ? > > On Wed, Sep 10, 2014 at 4:56 PM, Mohammad KONESHLOO via ParaView < > paraview at paraview.org> wrote: > > Hi everybody, > > I'm trying to convert a big csv file to a simple structured grid > (100x100x136). I imported it to Pra-view, but I could not convert it to > grid using Filters-> "Table to Structured Grid". another attempt was > creating a vts/vtk file from my csv file, but the structure of file is > ambiguous. I couldn't find any example. > In VTK pdf file regarding file formats, there is just an example for > structured point (page.18), I copied and pasted this example in Notepad++ > and saved with .vts and vtk extension, but I could not open in in Paraview > (4.2.0 RC1 64-bit). > > Do you have any example file or comment on the file structure? > > Thanks > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sample.vti Type: application/octet-stream Size: 1541 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Fri Sep 12 14:47:45 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 12 Sep 2014 14:47:45 -0400 Subject: [Paraview] Superbuild and Windows In-Reply-To: References: <6E8F6C07-4BA8-4575-B404-16ABCD63CE63@ornl.gov> <8C642057-0905-44C4-AAB6-63D6DAEC8DF7@ornl.gov> Message-ID: Thanks Michael. Both these changes are now merged in. http://review.source.kitware.com/#/t/4658/ Utkarsh On Thu, Sep 11, 2014 at 2:02 PM, Reuter, Michael A. wrote: > The patches are attached. They aren?t much but they help get the package (on Windows and OSX) built without issues. The package I made against the system Python seems to work OK although I have not exhaustively tested it. The python interpreter interaction inside ParaView seems to work fine with the few tests and examples I ran on it. > > M > > From wascott at sandia.gov Fri Sep 12 20:52:24 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Sat, 13 Sep 2014 00:52:24 +0000 Subject: [Paraview] fft of selection over time filter Message-ID: <9aaec371d2464398be869e272feb22df@ES05AMSNLNT.srn.sandia.gov> I am trying to figure out the FFT of selection over time filter. My user is trying to use it on a velocity point vector field (in 2d, no less). So, a few questions: * This filter doesn't work on point data, but only cell data. Shouldn't it work on point data? * This filter doesn't create magnitudes of vectors. Shouldn't it if needed? * Since an FFT spans some array of data, shouldn't this span be changeable? For instance, 16 or 32 or 128? * Does this filter even work correctly? Has anyone ever used it? * Can anyone create a simple example using this filter? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matthias.Zenker at erbe-med.com Mon Sep 15 04:16:47 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Mon, 15 Sep 2014 08:16:47 +0000 Subject: [Paraview] How to simply "Reload" a data file Message-ID: Hi, I wanted to try the "Reload" button which presumably can be created by one of the methods outlined below. But I am maybe too naive or am missing something: I have a Windoze binary distribution of ParaView 4.0.1. I did not find the file indicated by Cory, and copying the xml code given by S?bastien into a file and loading that as plugin had no effect visible to me. What am I missing here? Thank you, Matthias > -----Urspr?ngliche Nachricht----- > Von: paraview-bounces at paraview.org [mailto:paraview- > bounces at paraview.org] Im Auftrag von paraview-request at paraview.org > Gesendet: Samstag, 15. Juni 2013 18:00 > An: paraview at paraview.org > Betreff: Reload a file > > Send ParaView mailing list submissions to > paraview at paraview.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.paraview.org/mailman/listinfo/paraview > or, via email, send a message with subject or body 'help' to > paraview-request at paraview.org > > You can reach the person managing the list at > paraview-owner at paraview.org > > When replying, please edit your Subject line so it is more specific than "Re: > Contents of ParaView digest..." > > > Today's Topics: > > 1. Re: How to simply "Reload" a data file (Cory Quammen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 14 Jun 2013 13:42:34 -0400 > From: Cory Quammen > Subject: Re: [Paraview] How to simply "Reload" a data file > To: Sebastien Jourdain > Cc: Michael Jackson , ParaView > > Message-ID: > OeRVRSrNbZUSQXg at mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > For what it's worth, I just experimented with adding the line > > panel_widget="command_button"/> > > to the CSV reader and XDMF reader in > > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers > .xml > > The Refresh button appears among the other property widgets and it indeed > reloads the data set. > > I would happily add this to all the readers and submit a patch to gerrit if it > would be received well by the core ParaView developers. > > Thanks, > Cory > > On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain > wrote: > > BTW that's the correct XML for you, just need to create a file with > > that in and load it as a plugin and you will have your "Refresh" button. > > > > > > > > > > > base_proxyname="XdmfReader" class="vtkXdmfReader"> > > > panel_widget="command_button"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain > > wrote: > >> > >> Another approach could be a python macro that invalidate the > >> "active/selected' proxy in the pipeline, but that one will require > >> the usage of ParaView in built-in mode. > >> > >> If interested I can try to write the corresponding python code... > >> > >> Seb > >> > >> > >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain > >> wrote: > >>> > >>> I forgot to state the obvious, the plugin is a XML one... No code > >>> involved... > >>> > >>> In fact, just having the XML that I wrote in a file extend the UI > >>> with a button to refresh the reader should be enough. > >>> Need to figure out why the reader factory did not catch up the hint. > >>> > >>> That should be the only thing that you would need. > >>> > >>> Seb > >>> > >>> > >>> > >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson > >>> wrote: > >>>> > >>>> I was hoping that ParaView just had something built in. I would > >>>> rather not have to create a plugin and distribute that along side > >>>> my own software and to keep up on builds for all the various OS's > >>>> and all of that. i tried that for a while and I just could not keep up. > >>>> > >>>> So either I am the only person who has asked for this or there is > >>>> some over riding reason in the design of ParView why this type of > >>>> functionality is not in ParaView. > >>>> > >>>> Thanks > >>>> > __________________________________________________________ > _ > >>>> Mike Jackson Principal Software Engineer > >>>> BlueQuartz Software Dayton, Ohio > >>>> mike.jackson at bluequartz.net www.bluequartz.net > >>>> > >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu > >>>> > >>>> wrote: > >>>> > >>>> > hi you can try the approach of S?bastien > >>>> > > >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html > >>>> > > >>>> > I haven't tested yet. > >>>> > > >>>> > You can save the code as a macro, so you will have a button. > >>>> > > >>>> > Felipe > >>>> > > >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : > >>>> >> Is there button where I can simply reload a data file that was > >>>> >> read in a pipeline? > >>>> >> > >>>> >> We have a workflow where we process data into a file and view it > >>>> >> in ParaView. it is becoming tedious to blow away the entire > >>>> >> pipeline just to reload the new data. > >>>> >> > >>>> >> I know about state files but this still requires the user to go > >>>> >> to the File->Load State... " menu and then select a state file. > >>>> >> I would like to just select the data file in the Pipeline > >>>> >> browser (XDMF File reader for us), and just click some button > >>>> >> that just reloads data from the file. > >>>> >> > >>>> >> Or am I just missing something? I am using ParaView 3.98.1. I > >>>> >> have to admit I have not tried any of the 4.0.RC* downloads. > >>>> >> > >>>> >> Thanks > >>>> >> > _________________________________________________________ > >>>> >> Mike Jackson mike.jackson at bluequartz.net > >>>> >> BlueQuartz Software www.bluequartz.net > >>>> >> Principal Software Engineer Dayton, Ohio > >>>> >> _______________________________________________ > >>>> >> Powered by www.kitware.com > >>>> >> > >>>> >> Visit other Kitware open-source projects at > >>>> >> http://www.kitware.com/opensource/opensource.html > >>>> >> > >>>> >> Please keep messages on-topic and check the ParaView Wiki at: > >>>> >> http://paraview.org/Wiki/ParaView > >>>> >> > >>>> >> Follow this link to subscribe/unsubscribe: > >>>> >> http://www.paraview.org/mailman/listinfo/paraview > >>>> > > >>>> > > >>>> > -- > >>>> > Felipe Bordeu Weldt > >>>> > Ing?nieur de Recherche > >>>> > ------------------------------------- > >>>> > T?l. : 33 (0)2 40 37 16 57 > >>>> > Fax. : 33 (0)2 40 74 74 06 > >>>> > Felipe.Bordeu at ec-nantes.fr > >>>> > Institut GeM - UMR CNRS 6183 > >>>> > ?cole Centrale Nantes > >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE > >>>> > ------------------------------------- > >>>> > > >>>> > _______________________________________________ > >>>> > Powered by www.kitware.com > >>>> > > >>>> > Visit other Kitware open-source projects at > >>>> > http://www.kitware.com/opensource/opensource.html > >>>> > > >>>> > Please keep messages on-topic and check the ParaView Wiki at: > >>>> > http://paraview.org/Wiki/ParaView > >>>> > > >>>> > Follow this link to subscribe/unsubscribe: > >>>> > http://www.paraview.org/mailman/listinfo/paraview > >>>> > >>>> _______________________________________________ > >>>> Powered by www.kitware.com > >>>> > >>>> Visit other Kitware open-source projects at > >>>> http://www.kitware.com/opensource/opensource.html > >>>> > >>>> Please keep messages on-topic and check the ParaView Wiki at: > >>>> http://paraview.org/Wiki/ParaView > >>>> > >>>> Follow this link to subscribe/unsubscribe: > >>>> http://www.paraview.org/mailman/listinfo/paraview > >>> > >>> > >> > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://www.paraview.org/mailman/listinfo/paraview > > > > > > -- > Cory Quammen > Research Associate > Department of Computer Science > The University of North Carolina at Chapel Hill > > > ------------------------------ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > > > End of ParaView Digest, Vol 110, Issue 42 > ***************************************** _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 From cory.quammen at kitware.com Mon Sep 15 09:04:43 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 15 Sep 2014 09:04:43 -0400 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Matthias, The method I suggested requires modifying ParaView's source code, so it won't work for a binary distribution. As for the XML method, did you try to load an Xdmf file through what should be the new "Xdmf Reader (Refresh button)" reader? If you are loading a different type of file, this plugin will have no effect because it provides a Refresh button only for the Xdmf reader. You could modify the XML for other reader types, though. Thanks, Cory On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias wrote: > Hi, > > I wanted to try the "Reload" button which presumably can be created by one of the methods outlined below. But I am maybe too naive or am missing something: I have a Windoze binary distribution of ParaView 4.0.1. I did not find the file indicated by Cory, and copying the xml code given by S?bastien into a file and loading that as plugin had no effect visible to me. > > What am I missing here? > > Thank you, > > Matthias > >> -----Urspr?ngliche Nachricht----- >> Von: paraview-bounces at paraview.org [mailto:paraview- >> bounces at paraview.org] Im Auftrag von paraview-request at paraview.org >> Gesendet: Samstag, 15. Juni 2013 18:00 >> An: paraview at paraview.org >> Betreff: Reload a file >> >> Send ParaView mailing list submissions to >> paraview at paraview.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://www.paraview.org/mailman/listinfo/paraview >> or, via email, send a message with subject or body 'help' to >> paraview-request at paraview.org >> >> You can reach the person managing the list at >> paraview-owner at paraview.org >> >> When replying, please edit your Subject line so it is more specific than "Re: >> Contents of ParaView digest..." >> >> >> Today's Topics: >> >> 1. Re: How to simply "Reload" a data file (Cory Quammen) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Fri, 14 Jun 2013 13:42:34 -0400 >> From: Cory Quammen >> Subject: Re: [Paraview] How to simply "Reload" a data file >> To: Sebastien Jourdain >> Cc: Michael Jackson , ParaView >> >> Message-ID: >> > OeRVRSrNbZUSQXg at mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> For what it's worth, I just experimented with adding the line >> >> > panel_widget="command_button"/> >> >> to the CSV reader and XDMF reader in >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers >> .xml >> >> The Refresh button appears among the other property widgets and it indeed >> reloads the data set. >> >> I would happily add this to all the readers and submit a patch to gerrit if it >> would be received well by the core ParaView developers. >> >> Thanks, >> Cory >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain >> wrote: >> > BTW that's the correct XML for you, just need to create a file with >> > that in and load it as a plugin and you will have your "Refresh" button. >> > >> > >> > >> > >> > > > base_proxyname="XdmfReader" class="vtkXdmfReader"> >> > > > panel_widget="command_button"/> >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain >> > wrote: >> >> >> >> Another approach could be a python macro that invalidate the >> >> "active/selected' proxy in the pipeline, but that one will require >> >> the usage of ParaView in built-in mode. >> >> >> >> If interested I can try to write the corresponding python code... >> >> >> >> Seb >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain >> >> wrote: >> >>> >> >>> I forgot to state the obvious, the plugin is a XML one... No code >> >>> involved... >> >>> >> >>> In fact, just having the XML that I wrote in a file extend the UI >> >>> with a button to refresh the reader should be enough. >> >>> Need to figure out why the reader factory did not catch up the hint. >> >>> >> >>> That should be the only thing that you would need. >> >>> >> >>> Seb >> >>> >> >>> >> >>> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson >> >>> wrote: >> >>>> >> >>>> I was hoping that ParaView just had something built in. I would >> >>>> rather not have to create a plugin and distribute that along side >> >>>> my own software and to keep up on builds for all the various OS's >> >>>> and all of that. i tried that for a while and I just could not keep up. >> >>>> >> >>>> So either I am the only person who has asked for this or there is >> >>>> some over riding reason in the design of ParView why this type of >> >>>> functionality is not in ParaView. >> >>>> >> >>>> Thanks >> >>>> >> __________________________________________________________ >> _ >> >>>> Mike Jackson Principal Software Engineer >> >>>> BlueQuartz Software Dayton, Ohio >> >>>> mike.jackson at bluequartz.net www.bluequartz.net >> >>>> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu >> >>>> >> >>>> wrote: >> >>>> >> >>>> > hi you can try the approach of S?bastien >> >>>> > >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html >> >>>> > >> >>>> > I haven't tested yet. >> >>>> > >> >>>> > You can save the code as a macro, so you will have a button. >> >>>> > >> >>>> > Felipe >> >>>> > >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : >> >>>> >> Is there button where I can simply reload a data file that was >> >>>> >> read in a pipeline? >> >>>> >> >> >>>> >> We have a workflow where we process data into a file and view it >> >>>> >> in ParaView. it is becoming tedious to blow away the entire >> >>>> >> pipeline just to reload the new data. >> >>>> >> >> >>>> >> I know about state files but this still requires the user to go >> >>>> >> to the File->Load State... " menu and then select a state file. >> >>>> >> I would like to just select the data file in the Pipeline >> >>>> >> browser (XDMF File reader for us), and just click some button >> >>>> >> that just reloads data from the file. >> >>>> >> >> >>>> >> Or am I just missing something? I am using ParaView 3.98.1. I >> >>>> >> have to admit I have not tried any of the 4.0.RC* downloads. >> >>>> >> >> >>>> >> Thanks >> >>>> >> >> _________________________________________________________ >> >>>> >> Mike Jackson mike.jackson at bluequartz.net >> >>>> >> BlueQuartz Software www.bluequartz.net >> >>>> >> Principal Software Engineer Dayton, Ohio >> >>>> >> _______________________________________________ >> >>>> >> Powered by www.kitware.com >> >>>> >> >> >>>> >> Visit other Kitware open-source projects at >> >>>> >> http://www.kitware.com/opensource/opensource.html >> >>>> >> >> >>>> >> Please keep messages on-topic and check the ParaView Wiki at: >> >>>> >> http://paraview.org/Wiki/ParaView >> >>>> >> >> >>>> >> Follow this link to subscribe/unsubscribe: >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview >> >>>> > >> >>>> > >> >>>> > -- >> >>>> > Felipe Bordeu Weldt >> >>>> > Ing?nieur de Recherche >> >>>> > ------------------------------------- >> >>>> > T?l. : 33 (0)2 40 37 16 57 >> >>>> > Fax. : 33 (0)2 40 74 74 06 >> >>>> > Felipe.Bordeu at ec-nantes.fr >> >>>> > Institut GeM - UMR CNRS 6183 >> >>>> > ?cole Centrale Nantes >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE >> >>>> > ------------------------------------- >> >>>> > >> >>>> > _______________________________________________ >> >>>> > Powered by www.kitware.com >> >>>> > >> >>>> > Visit other Kitware open-source projects at >> >>>> > http://www.kitware.com/opensource/opensource.html >> >>>> > >> >>>> > Please keep messages on-topic and check the ParaView Wiki at: >> >>>> > http://paraview.org/Wiki/ParaView >> >>>> > >> >>>> > Follow this link to subscribe/unsubscribe: >> >>>> > http://www.paraview.org/mailman/listinfo/paraview >> >>>> >> >>>> _______________________________________________ >> >>>> Powered by www.kitware.com >> >>>> >> >>>> Visit other Kitware open-source projects at >> >>>> http://www.kitware.com/opensource/opensource.html >> >>>> >> >>>> Please keep messages on-topic and check the ParaView Wiki at: >> >>>> http://paraview.org/Wiki/ParaView >> >>>> >> >>>> Follow this link to subscribe/unsubscribe: >> >>>> http://www.paraview.org/mailman/listinfo/paraview >> >>> >> >>> >> >> >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://www.paraview.org/mailman/listinfo/paraview >> > >> >> >> >> -- >> Cory Quammen >> Research Associate >> Department of Computer Science >> The University of North Carolina at Chapel Hill >> >> >> ------------------------------ >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> End of ParaView Digest, Vol 110, Issue 42 >> ***************************************** > > > _____________________________________________________________________ > ERBE Elektromedizin GmbH > Firmensitz: 72072 Tuebingen > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > Registergericht: Stuttgart HRB 380137 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From Matthias.Zenker at erbe-med.com Mon Sep 15 09:54:47 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Mon, 15 Sep 2014 13:54:47 +0000 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Hi Cory, I use the reader for vtu format and pvd (vtu time collection). I tried to modify the xml as follows: But I cannot even load it as plugin. Presumably there are special keyword to use for the name of the original reader. Is there a documentation where I can find more information on that topic? Thanks, Matthias > -----Urspr?ngliche Nachricht----- > Von: Cory Quammen [mailto:cory.quammen at kitware.com] > Gesendet: Montag, 15. September 2014 15:05 > An: Zenker, Dr. Matthias > Cc: paraview at paraview.org > Betreff: Re: [Paraview] How to simply "Reload" a data file > > Matthias, > > The method I suggested requires modifying ParaView's source code, so it > won't work for a binary distribution. > > As for the XML method, did you try to load an Xdmf file through what should > be the new "Xdmf Reader (Refresh button)" reader? If you are loading a > different type of file, this plugin will have no effect because it provides a > Refresh button only for the Xdmf reader. You could modify the XML for > other reader types, though. > > Thanks, > Cory > > On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias > wrote: > > Hi, > > > > I wanted to try the "Reload" button which presumably can be created by > one of the methods outlined below. But I am maybe too naive or am missing > something: I have a Windoze binary distribution of ParaView 4.0.1. I did not > find the file indicated by Cory, and copying the xml code given by S?bastien > into a file and loading that as plugin had no effect visible to me. > > > > What am I missing here? > > > > Thank you, > > > > Matthias > > > >> -----Urspr?ngliche Nachricht----- > >> Von: paraview-bounces at paraview.org [mailto:paraview- > >> bounces at paraview.org] Im Auftrag von paraview-request at paraview.org > >> Gesendet: Samstag, 15. Juni 2013 18:00 > >> An: paraview at paraview.org > >> Betreff: Reload a file > >> > >> Send ParaView mailing list submissions to > >> paraview at paraview.org > >> > >> To subscribe or unsubscribe via the World Wide Web, visit > >> http://www.paraview.org/mailman/listinfo/paraview > >> or, via email, send a message with subject or body 'help' to > >> paraview-request at paraview.org > >> > >> You can reach the person managing the list at > >> paraview-owner at paraview.org > >> > >> When replying, please edit your Subject line so it is more specific than > "Re: > >> Contents of ParaView digest..." > >> > >> > >> Today's Topics: > >> > >> 1. Re: How to simply "Reload" a data file (Cory Quammen) > >> > >> > >> --------------------------------------------------------------------- > >> - > >> > >> Message: 1 > >> Date: Fri, 14 Jun 2013 13:42:34 -0400 > >> From: Cory Quammen > >> Subject: Re: [Paraview] How to simply "Reload" a data file > >> To: Sebastien Jourdain > >> Cc: Michael Jackson , ParaView > >> > >> Message-ID: > >> >> OeRVRSrNbZUSQXg at mail.gmail.com> > >> Content-Type: text/plain; charset=ISO-8859-1 > >> > >> For what it's worth, I just experimented with adding the line > >> > >> >> panel_widget="command_button"/> > >> > >> to the CSV reader and XDMF reader in > >> > >> > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers > >> .xml > >> > >> The Refresh button appears among the other property widgets and it > >> indeed reloads the data set. > >> > >> I would happily add this to all the readers and submit a patch to > >> gerrit if it would be received well by the core ParaView developers. > >> > >> Thanks, > >> Cory > >> > >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain > >> wrote: > >> > BTW that's the correct XML for you, just need to create a file with > >> > that in and load it as a plugin and you will have your "Refresh" button. > >> > > >> > > >> > > >> > > >> > >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> > >> > >> > panel_widget="command_button"/> > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain > >> > wrote: > >> >> > >> >> Another approach could be a python macro that invalidate the > >> >> "active/selected' proxy in the pipeline, but that one will require > >> >> the usage of ParaView in built-in mode. > >> >> > >> >> If interested I can try to write the corresponding python code... > >> >> > >> >> Seb > >> >> > >> >> > >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain > >> >> wrote: > >> >>> > >> >>> I forgot to state the obvious, the plugin is a XML one... No code > >> >>> involved... > >> >>> > >> >>> In fact, just having the XML that I wrote in a file extend the UI > >> >>> with a button to refresh the reader should be enough. > >> >>> Need to figure out why the reader factory did not catch up the hint. > >> >>> > >> >>> That should be the only thing that you would need. > >> >>> > >> >>> Seb > >> >>> > >> >>> > >> >>> > >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson > >> >>> wrote: > >> >>>> > >> >>>> I was hoping that ParaView just had something built in. I would > >> >>>> rather not have to create a plugin and distribute that along > >> >>>> side my own software and to keep up on builds for all the > >> >>>> various OS's and all of that. i tried that for a while and I just could not > keep up. > >> >>>> > >> >>>> So either I am the only person who has asked for this or there > >> >>>> is some over riding reason in the design of ParView why this > >> >>>> type of functionality is not in ParaView. > >> >>>> > >> >>>> Thanks > >> >>>> > >> > __________________________________________________________ > >> _ > >> >>>> Mike Jackson Principal Software Engineer > >> >>>> BlueQuartz Software Dayton, Ohio > >> >>>> mike.jackson at bluequartz.net www.bluequartz.net > >> >>>> > >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu > >> >>>> > >> >>>> wrote: > >> >>>> > >> >>>> > hi you can try the approach of S?bastien > >> >>>> > > >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html > >> >>>> > > >> >>>> > I haven't tested yet. > >> >>>> > > >> >>>> > You can save the code as a macro, so you will have a button. > >> >>>> > > >> >>>> > Felipe > >> >>>> > > >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : > >> >>>> >> Is there button where I can simply reload a data file that > >> >>>> >> was read in a pipeline? > >> >>>> >> > >> >>>> >> We have a workflow where we process data into a file and view > >> >>>> >> it in ParaView. it is becoming tedious to blow away the > >> >>>> >> entire pipeline just to reload the new data. > >> >>>> >> > >> >>>> >> I know about state files but this still requires the user to > >> >>>> >> go to the File->Load State... " menu and then select a state file. > >> >>>> >> I would like to just select the data file in the Pipeline > >> >>>> >> browser (XDMF File reader for us), and just click some button > >> >>>> >> that just reloads data from the file. > >> >>>> >> > >> >>>> >> Or am I just missing something? I am using ParaView 3.98.1. I > >> >>>> >> have to admit I have not tried any of the 4.0.RC* downloads. > >> >>>> >> > >> >>>> >> Thanks > >> >>>> >> > >> > _________________________________________________________ > >> >>>> >> Mike Jackson mike.jackson at bluequartz.net > >> >>>> >> BlueQuartz Software www.bluequartz.net > >> >>>> >> Principal Software Engineer Dayton, Ohio > >> >>>> >> _______________________________________________ > >> >>>> >> Powered by www.kitware.com > >> >>>> >> > >> >>>> >> Visit other Kitware open-source projects at > >> >>>> >> http://www.kitware.com/opensource/opensource.html > >> >>>> >> > >> >>>> >> Please keep messages on-topic and check the ParaView Wiki at: > >> >>>> >> http://paraview.org/Wiki/ParaView > >> >>>> >> > >> >>>> >> Follow this link to subscribe/unsubscribe: > >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview > >> >>>> > > >> >>>> > > >> >>>> > -- > >> >>>> > Felipe Bordeu Weldt > >> >>>> > Ing?nieur de Recherche > >> >>>> > ------------------------------------- > >> >>>> > T?l. : 33 (0)2 40 37 16 57 > >> >>>> > Fax. : 33 (0)2 40 74 74 06 > >> >>>> > Felipe.Bordeu at ec-nantes.fr > >> >>>> > Institut GeM - UMR CNRS 6183 > >> >>>> > ?cole Centrale Nantes > >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE > >> >>>> > ------------------------------------- > >> >>>> > > >> >>>> > _______________________________________________ > >> >>>> > Powered by www.kitware.com > >> >>>> > > >> >>>> > Visit other Kitware open-source projects at > >> >>>> > http://www.kitware.com/opensource/opensource.html > >> >>>> > > >> >>>> > Please keep messages on-topic and check the ParaView Wiki at: > >> >>>> > http://paraview.org/Wiki/ParaView > >> >>>> > > >> >>>> > Follow this link to subscribe/unsubscribe: > >> >>>> > http://www.paraview.org/mailman/listinfo/paraview > >> >>>> > >> >>>> _______________________________________________ > >> >>>> Powered by www.kitware.com > >> >>>> > >> >>>> Visit other Kitware open-source projects at > >> >>>> http://www.kitware.com/opensource/opensource.html > >> >>>> > >> >>>> Please keep messages on-topic and check the ParaView Wiki at: > >> >>>> http://paraview.org/Wiki/ParaView > >> >>>> > >> >>>> Follow this link to subscribe/unsubscribe: > >> >>>> http://www.paraview.org/mailman/listinfo/paraview > >> >>> > >> >>> > >> >> > >> > > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://www.paraview.org/mailman/listinfo/paraview > >> > > >> > >> > >> > >> -- > >> Cory Quammen > >> Research Associate > >> Department of Computer Science > >> The University of North Carolina at Chapel Hill > >> > >> > >> ------------------------------ > >> > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: > >> http://paraview.org/Wiki/ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://www.paraview.org/mailman/listinfo/paraview > >> > >> > >> End of ParaView Digest, Vol 110, Issue 42 > >> ***************************************** > > > > > > > __________________________________________________________ > ___________ > > ERBE Elektromedizin GmbH > > Firmensitz: 72072 Tuebingen > > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > > Registergericht: Stuttgart HRB 380137 > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 From utkarsh.ayachit at kitware.com Mon Sep 15 10:28:23 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 15 Sep 2014 10:28:23 -0400 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: I suspect will not work with vtu. To understand this better, what is that which is changing that you need to reload the file? Are you loading a file series or a single file? Utkarsh On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias wrote: > Hi Cory, > > I use the reader for vtu format and pvd (vtu time collection). I tried to modify the xml as follows: > > > > > > > > > > > > > > > > > > But I cannot even load it as plugin. Presumably there are special keyword to use for the name of the original reader. Is there a documentation where I can find more information on that topic? > > Thanks, > > Matthias > >> -----Urspr?ngliche Nachricht----- >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] >> Gesendet: Montag, 15. September 2014 15:05 >> An: Zenker, Dr. Matthias >> Cc: paraview at paraview.org >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> Matthias, >> >> The method I suggested requires modifying ParaView's source code, so it >> won't work for a binary distribution. >> >> As for the XML method, did you try to load an Xdmf file through what should >> be the new "Xdmf Reader (Refresh button)" reader? If you are loading a >> different type of file, this plugin will have no effect because it provides a >> Refresh button only for the Xdmf reader. You could modify the XML for >> other reader types, though. >> >> Thanks, >> Cory >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias >> wrote: >> > Hi, >> > >> > I wanted to try the "Reload" button which presumably can be created by >> one of the methods outlined below. But I am maybe too naive or am missing >> something: I have a Windoze binary distribution of ParaView 4.0.1. I did not >> find the file indicated by Cory, and copying the xml code given by S?bastien >> into a file and loading that as plugin had no effect visible to me. >> > >> > What am I missing here? >> > >> > Thank you, >> > >> > Matthias >> > >> >> -----Urspr?ngliche Nachricht----- >> >> Von: paraview-bounces at paraview.org [mailto:paraview- >> >> bounces at paraview.org] Im Auftrag von paraview-request at paraview.org >> >> Gesendet: Samstag, 15. Juni 2013 18:00 >> >> An: paraview at paraview.org >> >> Betreff: Reload a file >> >> >> >> Send ParaView mailing list submissions to >> >> paraview at paraview.org >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> or, via email, send a message with subject or body 'help' to >> >> paraview-request at paraview.org >> >> >> >> You can reach the person managing the list at >> >> paraview-owner at paraview.org >> >> >> >> When replying, please edit your Subject line so it is more specific than >> "Re: >> >> Contents of ParaView digest..." >> >> >> >> >> >> Today's Topics: >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory Quammen) >> >> >> >> >> >> --------------------------------------------------------------------- >> >> - >> >> >> >> Message: 1 >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 >> >> From: Cory Quammen >> >> Subject: Re: [Paraview] How to simply "Reload" a data file >> >> To: Sebastien Jourdain >> >> Cc: Michael Jackson , ParaView >> >> >> >> Message-ID: >> >> > >> OeRVRSrNbZUSQXg at mail.gmail.com> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> For what it's worth, I just experimented with adding the line >> >> >> >> > >> panel_widget="command_button"/> >> >> >> >> to the CSV reader and XDMF reader in >> >> >> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers >> >> .xml >> >> >> >> The Refresh button appears among the other property widgets and it >> >> indeed reloads the data set. >> >> >> >> I would happily add this to all the readers and submit a patch to >> >> gerrit if it would be received well by the core ParaView developers. >> >> >> >> Thanks, >> >> Cory >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain >> >> wrote: >> >> > BTW that's the correct XML for you, just need to create a file with >> >> > that in and load it as a plugin and you will have your "Refresh" button. >> >> > >> >> > >> >> > >> >> > >> >> > > >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> >> >> > > >> > panel_widget="command_button"/> >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain >> >> > wrote: >> >> >> >> >> >> Another approach could be a python macro that invalidate the >> >> >> "active/selected' proxy in the pipeline, but that one will require >> >> >> the usage of ParaView in built-in mode. >> >> >> >> >> >> If interested I can try to write the corresponding python code... >> >> >> >> >> >> Seb >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain >> >> >> wrote: >> >> >>> >> >> >>> I forgot to state the obvious, the plugin is a XML one... No code >> >> >>> involved... >> >> >>> >> >> >>> In fact, just having the XML that I wrote in a file extend the UI >> >> >>> with a button to refresh the reader should be enough. >> >> >>> Need to figure out why the reader factory did not catch up the hint. >> >> >>> >> >> >>> That should be the only thing that you would need. >> >> >>> >> >> >>> Seb >> >> >>> >> >> >>> >> >> >>> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson >> >> >>> wrote: >> >> >>>> >> >> >>>> I was hoping that ParaView just had something built in. I would >> >> >>>> rather not have to create a plugin and distribute that along >> >> >>>> side my own software and to keep up on builds for all the >> >> >>>> various OS's and all of that. i tried that for a while and I just could not >> keep up. >> >> >>>> >> >> >>>> So either I am the only person who has asked for this or there >> >> >>>> is some over riding reason in the design of ParView why this >> >> >>>> type of functionality is not in ParaView. >> >> >>>> >> >> >>>> Thanks >> >> >>>> >> >> >> __________________________________________________________ >> >> _ >> >> >>>> Mike Jackson Principal Software Engineer >> >> >>>> BlueQuartz Software Dayton, Ohio >> >> >>>> mike.jackson at bluequartz.net www.bluequartz.net >> >> >>>> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu >> >> >>>> >> >> >>>> wrote: >> >> >>>> >> >> >>>> > hi you can try the approach of S?bastien >> >> >>>> > >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html >> >> >>>> > >> >> >>>> > I haven't tested yet. >> >> >>>> > >> >> >>>> > You can save the code as a macro, so you will have a button. >> >> >>>> > >> >> >>>> > Felipe >> >> >>>> > >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : >> >> >>>> >> Is there button where I can simply reload a data file that >> >> >>>> >> was read in a pipeline? >> >> >>>> >> >> >> >>>> >> We have a workflow where we process data into a file and view >> >> >>>> >> it in ParaView. it is becoming tedious to blow away the >> >> >>>> >> entire pipeline just to reload the new data. >> >> >>>> >> >> >> >>>> >> I know about state files but this still requires the user to >> >> >>>> >> go to the File->Load State... " menu and then select a state file. >> >> >>>> >> I would like to just select the data file in the Pipeline >> >> >>>> >> browser (XDMF File reader for us), and just click some button >> >> >>>> >> that just reloads data from the file. >> >> >>>> >> >> >> >>>> >> Or am I just missing something? I am using ParaView 3.98.1. I >> >> >>>> >> have to admit I have not tried any of the 4.0.RC* downloads. >> >> >>>> >> >> >> >>>> >> Thanks >> >> >>>> >> >> >> >> _________________________________________________________ >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net >> >> >>>> >> BlueQuartz Software www.bluequartz.net >> >> >>>> >> Principal Software Engineer Dayton, Ohio >> >> >>>> >> _______________________________________________ >> >> >>>> >> Powered by www.kitware.com >> >> >>>> >> >> >> >>>> >> Visit other Kitware open-source projects at >> >> >>>> >> http://www.kitware.com/opensource/opensource.html >> >> >>>> >> >> >> >>>> >> Please keep messages on-topic and check the ParaView Wiki at: >> >> >>>> >> http://paraview.org/Wiki/ParaView >> >> >>>> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: >> >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >>>> > >> >> >>>> > >> >> >>>> > -- >> >> >>>> > Felipe Bordeu Weldt >> >> >>>> > Ing?nieur de Recherche >> >> >>>> > ------------------------------------- >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 >> >> >>>> > Fax. : 33 (0)2 40 74 74 06 >> >> >>>> > Felipe.Bordeu at ec-nantes.fr >> >> >>>> > Institut GeM - UMR CNRS 6183 >> >> >>>> > ?cole Centrale Nantes >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE >> >> >>>> > ------------------------------------- >> >> >>>> > >> >> >>>> > _______________________________________________ >> >> >>>> > Powered by www.kitware.com >> >> >>>> > >> >> >>>> > Visit other Kitware open-source projects at >> >> >>>> > http://www.kitware.com/opensource/opensource.html >> >> >>>> > >> >> >>>> > Please keep messages on-topic and check the ParaView Wiki at: >> >> >>>> > http://paraview.org/Wiki/ParaView >> >> >>>> > >> >> >>>> > Follow this link to subscribe/unsubscribe: >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview >> >> >>>> >> >> >>>> _______________________________________________ >> >> >>>> Powered by www.kitware.com >> >> >>>> >> >> >>>> Visit other Kitware open-source projects at >> >> >>>> http://www.kitware.com/opensource/opensource.html >> >> >>>> >> >> >>>> Please keep messages on-topic and check the ParaView Wiki at: >> >> >>>> http://paraview.org/Wiki/ParaView >> >> >>>> >> >> >>>> Follow this link to subscribe/unsubscribe: >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview >> >> >>> >> >> >>> >> >> >> >> >> > >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> > http://paraview.org/Wiki/ParaView >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://www.paraview.org/mailman/listinfo/paraview >> >> > >> >> >> >> >> >> >> >> -- >> >> Cory Quammen >> >> Research Associate >> >> Department of Computer Science >> >> The University of North Carolina at Chapel Hill >> >> >> >> >> >> ------------------------------ >> >> >> >> _______________________________________________ >> >> Powered by www.kitware.com >> >> >> >> Visit other Kitware open-source projects at >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> >> http://paraview.org/Wiki/ParaView >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 >> >> ***************************************** >> > >> > >> > >> __________________________________________________________ >> ___________ >> > ERBE Elektromedizin GmbH >> > Firmensitz: 72072 Tuebingen >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> > Registergericht: Stuttgart HRB 380137 >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview > > > _____________________________________________________________________ > ERBE Elektromedizin GmbH > Firmensitz: 72072 Tuebingen > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > Registergericht: Stuttgart HRB 380137 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From florian.hoffmann at inutech.de Mon Sep 15 10:23:57 2014 From: florian.hoffmann at inutech.de (Florian Hoffmann) Date: Mon, 15 Sep 2014 16:23:57 +0200 Subject: [Paraview] PV4.1, Custom Dock Widget: How to automatically add a glyph3d filter after loading data ? In-Reply-To: <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> Message-ID: <5416F67D.4090602@inutech.de> I would like to automatically add a glyph filter and render the correctly scaled spheres after the user has opened a file in my custom dock widget. I created a DockWidget using the example in /examples/Plugins/DockWidget. When pressing a button a specific file is being opened for the user by the following calls: void on_button_clicked() { QStringxdmfFile="C:\\..\\unknown_case.xdmf"; QStringList visuFiles; visuFiles.append(xdmfFile); pqPipelineSource* pqPlinesource = pqLoadDataReaction::loadData(visuFiles); pqPlinesource->updatePipeline(); // TODO: // add spherical glyph for loaded polyData // scale spherical glyphs by a scalar attribute/property // render glyphs } I would like to include that the code automatically adds spherical glyphs and renders them for the data just loaded. I tried the following code but I am not sure if it works vtkSMProxy*myProxy=pqPlinesource->getProxy(); vtkObjectBase *myObject = myProxy->GetClientSideObject(); vtkAlgorithm *myvtkAlgo = vtkAlgorithm::SafeDownCast(myObject); vtkGlyph3D *myspheres = vtkGlyph3D::New(); myspheres->SetSourceConnection(myvtkAlgo->GetOutputPort()); In case this is supposed to work, how can I now update the pipeline and render the spheres using C++ PV core functionality ? (The user should also see the result in the pipeline browser dock of the GUI). In case my approach is totally wrong, what would be the right way of handling this situation ? Thank you. Best regards, Florian -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matthias.Zenker at erbe-med.com Mon Sep 15 10:31:50 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Mon, 15 Sep 2014 14:31:50 +0000 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Normally I load a time series, either a series of vtu files or a time collection (pvd file containing the vtu file names with asociated timestamps). During the simulation, new files are added to the series. So it would be nice to watch the simulation going on by reloading from time to time. Matthias > -----Urspr?ngliche Nachricht----- > Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Gesendet: Montag, 15. September 2014 16:28 > An: Zenker, Dr. Matthias > Cc: Cory Quammen; paraview at paraview.org > Betreff: Re: [Paraview] How to simply "Reload" a data file > > I suspect will not work with vtu. To understand this better, what is that which > is changing that you need to reload the file? Are you loading a file series or a > single file? > > Utkarsh > > On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias > wrote: > > Hi Cory, > > > > I use the reader for vtu format and pvd (vtu time collection). I tried to > modify the xml as follows: > > > > > > > > > > base_proxyname="VTUReader" class="vtuReader"> > > panel_widget="command_button"/> > > > > > > > > > > > > > > > > > > > > > > > > But I cannot even load it as plugin. Presumably there are special keyword to > use for the name of the original reader. Is there a documentation where I > can find more information on that topic? > > > > Thanks, > > > > Matthias > > > >> -----Urspr?ngliche Nachricht----- > >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] > >> Gesendet: Montag, 15. September 2014 15:05 > >> An: Zenker, Dr. Matthias > >> Cc: paraview at paraview.org > >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> > >> Matthias, > >> > >> The method I suggested requires modifying ParaView's source code, so > >> it won't work for a binary distribution. > >> > >> As for the XML method, did you try to load an Xdmf file through what > >> should be the new "Xdmf Reader (Refresh button)" reader? If you are > >> loading a different type of file, this plugin will have no effect > >> because it provides a Refresh button only for the Xdmf reader. You > >> could modify the XML for other reader types, though. > >> > >> Thanks, > >> Cory > >> > >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias > >> wrote: > >> > Hi, > >> > > >> > I wanted to try the "Reload" button which presumably can be created > >> > by > >> one of the methods outlined below. But I am maybe too naive or am > >> missing > >> something: I have a Windoze binary distribution of ParaView 4.0.1. I > >> did not find the file indicated by Cory, and copying the xml code > >> given by S?bastien into a file and loading that as plugin had no effect > visible to me. > >> > > >> > What am I missing here? > >> > > >> > Thank you, > >> > > >> > Matthias > >> > > >> >> -----Urspr?ngliche Nachricht----- > >> >> Von: paraview-bounces at paraview.org [mailto:paraview- > >> >> bounces at paraview.org] Im Auftrag von paraview- > request at paraview.org > >> >> Gesendet: Samstag, 15. Juni 2013 18:00 > >> >> An: paraview at paraview.org > >> >> Betreff: Reload a file > >> >> > >> >> Send ParaView mailing list submissions to > >> >> paraview at paraview.org > >> >> > >> >> To subscribe or unsubscribe via the World Wide Web, visit > >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> or, via email, send a message with subject or body 'help' to > >> >> paraview-request at paraview.org > >> >> > >> >> You can reach the person managing the list at > >> >> paraview-owner at paraview.org > >> >> > >> >> When replying, please edit your Subject line so it is more > >> >> specific than > >> "Re: > >> >> Contents of ParaView digest..." > >> >> > >> >> > >> >> Today's Topics: > >> >> > >> >> 1. Re: How to simply "Reload" a data file (Cory Quammen) > >> >> > >> >> > >> >> ------------------------------------------------------------------ > >> >> --- > >> >> - > >> >> > >> >> Message: 1 > >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 > >> >> From: Cory Quammen > >> >> Subject: Re: [Paraview] How to simply "Reload" a data file > >> >> To: Sebastien Jourdain > >> >> Cc: Michael Jackson , ParaView > >> >> > >> >> Message-ID: > >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> > >> >> Content-Type: text/plain; charset=ISO-8859-1 > >> >> > >> >> For what it's worth, I just experimented with adding the line > >> >> > >> >> >> >> panel_widget="command_button"/> > >> >> > >> >> to the CSV reader and XDMF reader in > >> >> > >> >> > >> > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers > >> >> .xml > >> >> > >> >> The Refresh button appears among the other property widgets and it > >> >> indeed reloads the data set. > >> >> > >> >> I would happily add this to all the readers and submit a patch to > >> >> gerrit if it would be received well by the core ParaView developers. > >> >> > >> >> Thanks, > >> >> Cory > >> >> > >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain > >> >> wrote: > >> >> > BTW that's the correct XML for you, just need to create a file > >> >> > with that in and load it as a plugin and you will have your "Refresh" > button. > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > >> >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> > >> >> > >> >> > panel_widget="command_button"/> > >> >> > > >> >> > >> >> > file_description="Xdmf Reader (Refresh button)" /> > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain > >> >> > wrote: > >> >> >> > >> >> >> Another approach could be a python macro that invalidate the > >> >> >> "active/selected' proxy in the pipeline, but that one will > >> >> >> require the usage of ParaView in built-in mode. > >> >> >> > >> >> >> If interested I can try to write the corresponding python code... > >> >> >> > >> >> >> Seb > >> >> >> > >> >> >> > >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain > >> >> >> wrote: > >> >> >>> > >> >> >>> I forgot to state the obvious, the plugin is a XML one... No > >> >> >>> code involved... > >> >> >>> > >> >> >>> In fact, just having the XML that I wrote in a file extend the > >> >> >>> UI with a button to refresh the reader should be enough. > >> >> >>> Need to figure out why the reader factory did not catch up the > hint. > >> >> >>> > >> >> >>> That should be the only thing that you would need. > >> >> >>> > >> >> >>> Seb > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson > >> >> >>> wrote: > >> >> >>>> > >> >> >>>> I was hoping that ParaView just had something built in. I > >> >> >>>> would rather not have to create a plugin and distribute that > >> >> >>>> along side my own software and to keep up on builds for all > >> >> >>>> the various OS's and all of that. i tried that for a while > >> >> >>>> and I just could not > >> keep up. > >> >> >>>> > >> >> >>>> So either I am the only person who has asked for this or > >> >> >>>> there is some over riding reason in the design of ParView why > >> >> >>>> this type of functionality is not in ParaView. > >> >> >>>> > >> >> >>>> Thanks > >> >> >>>> > >> >> > >> > __________________________________________________________ > >> >> _ > >> >> >>>> Mike Jackson Principal Software Engineer > >> >> >>>> BlueQuartz Software Dayton, Ohio > >> >> >>>> mike.jackson at bluequartz.net www.bluequartz.net > >> >> >>>> > >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu > >> >> >>>> > >> >> >>>> wrote: > >> >> >>>> > >> >> >>>> > hi you can try the approach of S?bastien > >> >> >>>> > > >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html > >> >> >>>> > > >> >> >>>> > I haven't tested yet. > >> >> >>>> > > >> >> >>>> > You can save the code as a macro, so you will have a button. > >> >> >>>> > > >> >> >>>> > Felipe > >> >> >>>> > > >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : > >> >> >>>> >> Is there button where I can simply reload a data file that > >> >> >>>> >> was read in a pipeline? > >> >> >>>> >> > >> >> >>>> >> We have a workflow where we process data into a file and > >> >> >>>> >> view it in ParaView. it is becoming tedious to blow away > >> >> >>>> >> the entire pipeline just to reload the new data. > >> >> >>>> >> > >> >> >>>> >> I know about state files but this still requires the user > >> >> >>>> >> to go to the File->Load State... " menu and then select a state > file. > >> >> >>>> >> I would like to just select the data file in the Pipeline > >> >> >>>> >> browser (XDMF File reader for us), and just click some > >> >> >>>> >> button that just reloads data from the file. > >> >> >>>> >> > >> >> >>>> >> Or am I just missing something? I am using ParaView > >> >> >>>> >> 3.98.1. I have to admit I have not tried any of the 4.0.RC* > downloads. > >> >> >>>> >> > >> >> >>>> >> Thanks > >> >> >>>> >> > >> >> > >> > _________________________________________________________ > >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net > >> >> >>>> >> BlueQuartz Software www.bluequartz.net > >> >> >>>> >> Principal Software Engineer Dayton, Ohio > >> >> >>>> >> _______________________________________________ > >> >> >>>> >> Powered by www.kitware.com > >> >> >>>> >> > >> >> >>>> >> Visit other Kitware open-source projects at > >> >> >>>> >> http://www.kitware.com/opensource/opensource.html > >> >> >>>> >> > >> >> >>>> >> Please keep messages on-topic and check the ParaView Wiki > at: > >> >> >>>> >> http://paraview.org/Wiki/ParaView > >> >> >>>> >> > >> >> >>>> >> Follow this link to subscribe/unsubscribe: > >> >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >>>> > > >> >> >>>> > > >> >> >>>> > -- > >> >> >>>> > Felipe Bordeu Weldt > >> >> >>>> > Ing?nieur de Recherche > >> >> >>>> > ------------------------------------- > >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 > >> >> >>>> > Fax. : 33 (0)2 40 74 74 06 > >> >> >>>> > Felipe.Bordeu at ec-nantes.fr > >> >> >>>> > Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes > >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE > >> >> >>>> > ------------------------------------- > >> >> >>>> > > >> >> >>>> > _______________________________________________ > >> >> >>>> > Powered by www.kitware.com > >> >> >>>> > > >> >> >>>> > Visit other Kitware open-source projects at > >> >> >>>> > http://www.kitware.com/opensource/opensource.html > >> >> >>>> > > >> >> >>>> > Please keep messages on-topic and check the ParaView Wiki > at: > >> >> >>>> > http://paraview.org/Wiki/ParaView > >> >> >>>> > > >> >> >>>> > Follow this link to subscribe/unsubscribe: > >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >>>> > >> >> >>>> _______________________________________________ > >> >> >>>> Powered by www.kitware.com > >> >> >>>> > >> >> >>>> Visit other Kitware open-source projects at > >> >> >>>> http://www.kitware.com/opensource/opensource.html > >> >> >>>> > >> >> >>>> Please keep messages on-topic and check the ParaView Wiki at: > >> >> >>>> http://paraview.org/Wiki/ParaView > >> >> >>>> > >> >> >>>> Follow this link to subscribe/unsubscribe: > >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview > >> >> >>> > >> >> >>> > >> >> >> > >> >> > > >> >> > > >> >> > _______________________________________________ > >> >> > Powered by www.kitware.com > >> >> > > >> >> > Visit other Kitware open-source projects at > >> >> > http://www.kitware.com/opensource/opensource.html > >> >> > > >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> > http://paraview.org/Wiki/ParaView > >> >> > > >> >> > Follow this link to subscribe/unsubscribe: > >> >> > http://www.paraview.org/mailman/listinfo/paraview > >> >> > > >> >> > >> >> > >> >> > >> >> -- > >> >> Cory Quammen > >> >> Research Associate > >> >> Department of Computer Science > >> >> The University of North Carolina at Chapel Hill > >> >> > >> >> > >> >> ------------------------------ > >> >> > >> >> _______________________________________________ > >> >> Powered by www.kitware.com > >> >> > >> >> Visit other Kitware open-source projects at > >> >> http://www.kitware.com/opensource/opensource.html > >> >> > >> >> Please keep messages on-topic and check the ParaView Wiki at: > >> >> http://paraview.org/Wiki/ParaView > >> >> > >> >> Follow this link to subscribe/unsubscribe: > >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> > >> >> > >> >> End of ParaView Digest, Vol 110, Issue 42 > >> >> ***************************************** > >> > > >> > > >> > > >> > __________________________________________________________ > >> ___________ > >> > ERBE Elektromedizin GmbH > >> > Firmensitz: 72072 Tuebingen > >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> > Registergericht: Stuttgart HRB 380137 > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > __________________________________________________________ > ___________ > > ERBE Elektromedizin GmbH > > Firmensitz: 72072 Tuebingen > > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > > Registergericht: Stuttgart HRB 380137 > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 From utkarsh.ayachit at kitware.com Mon Sep 15 10:49:41 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 15 Sep 2014 10:49:41 -0400 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Ah. since it's a file series, it would not work the way Cory is suggesting. I'll see if I can cook up a Python script that can make this possible for now. We're putting this on the roadmap for the next release (I know I've said that a few times in the past :) ). Utkarsh On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias wrote: > Normally I load a time series, either a series of vtu files or a time collection (pvd file containing the vtu file names with asociated timestamps). During the simulation, new files are added to the series. So it would be nice to watch the simulation going on by reloading from time to time. > > Matthias > >> -----Urspr?ngliche Nachricht----- >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Gesendet: Montag, 15. September 2014 16:28 >> An: Zenker, Dr. Matthias >> Cc: Cory Quammen; paraview at paraview.org >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> I suspect will not work with vtu. To understand this better, what is that which >> is changing that you need to reload the file? Are you loading a file series or a >> single file? >> >> Utkarsh >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias >> wrote: >> > Hi Cory, >> > >> > I use the reader for vtu format and pvd (vtu time collection). I tried to >> modify the xml as follows: >> > >> > >> > >> > >> > > base_proxyname="VTUReader" class="vtuReader"> >> > > panel_widget="command_button"/> >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > But I cannot even load it as plugin. Presumably there are special keyword to >> use for the name of the original reader. Is there a documentation where I >> can find more information on that topic? >> > >> > Thanks, >> > >> > Matthias >> > >> >> -----Urspr?ngliche Nachricht----- >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] >> >> Gesendet: Montag, 15. September 2014 15:05 >> >> An: Zenker, Dr. Matthias >> >> Cc: paraview at paraview.org >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> Matthias, >> >> >> >> The method I suggested requires modifying ParaView's source code, so >> >> it won't work for a binary distribution. >> >> >> >> As for the XML method, did you try to load an Xdmf file through what >> >> should be the new "Xdmf Reader (Refresh button)" reader? If you are >> >> loading a different type of file, this plugin will have no effect >> >> because it provides a Refresh button only for the Xdmf reader. You >> >> could modify the XML for other reader types, though. >> >> >> >> Thanks, >> >> Cory >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias >> >> wrote: >> >> > Hi, >> >> > >> >> > I wanted to try the "Reload" button which presumably can be created >> >> > by >> >> one of the methods outlined below. But I am maybe too naive or am >> >> missing >> >> something: I have a Windoze binary distribution of ParaView 4.0.1. I >> >> did not find the file indicated by Cory, and copying the xml code >> >> given by S?bastien into a file and loading that as plugin had no effect >> visible to me. >> >> > >> >> > What am I missing here? >> >> > >> >> > Thank you, >> >> > >> >> > Matthias >> >> > >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- >> >> >> bounces at paraview.org] Im Auftrag von paraview- >> request at paraview.org >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 >> >> >> An: paraview at paraview.org >> >> >> Betreff: Reload a file >> >> >> >> >> >> Send ParaView mailing list submissions to >> >> >> paraview at paraview.org >> >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> or, via email, send a message with subject or body 'help' to >> >> >> paraview-request at paraview.org >> >> >> >> >> >> You can reach the person managing the list at >> >> >> paraview-owner at paraview.org >> >> >> >> >> >> When replying, please edit your Subject line so it is more >> >> >> specific than >> >> "Re: >> >> >> Contents of ParaView digest..." >> >> >> >> >> >> >> >> >> Today's Topics: >> >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory Quammen) >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------ >> >> >> --- >> >> >> - >> >> >> >> >> >> Message: 1 >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 >> >> >> From: Cory Quammen >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data file >> >> >> To: Sebastien Jourdain >> >> >> Cc: Michael Jackson , ParaView >> >> >> >> >> >> Message-ID: >> >> >> > >> >> OeRVRSrNbZUSQXg at mail.gmail.com> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> >> >> For what it's worth, I just experimented with adding the line >> >> >> >> >> >> > >> >> panel_widget="command_button"/> >> >> >> >> >> >> to the CSV reader and XDMF reader in >> >> >> >> >> >> >> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers >> >> >> .xml >> >> >> >> >> >> The Refresh button appears among the other property widgets and it >> >> >> indeed reloads the data set. >> >> >> >> >> >> I would happily add this to all the readers and submit a patch to >> >> >> gerrit if it would be received well by the core ParaView developers. >> >> >> >> >> >> Thanks, >> >> >> Cory >> >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain >> >> >> wrote: >> >> >> > BTW that's the correct XML for you, just need to create a file >> >> >> > with that in and load it as a plugin and you will have your "Refresh" >> button. >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > > >> >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> >> >> >> > > >> >> > panel_widget="command_button"/> >> >> >> > >> >> >> > > >> >> > file_description="Xdmf Reader (Refresh button)" /> >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain >> >> >> > wrote: >> >> >> >> >> >> >> >> Another approach could be a python macro that invalidate the >> >> >> >> "active/selected' proxy in the pipeline, but that one will >> >> >> >> require the usage of ParaView in built-in mode. >> >> >> >> >> >> >> >> If interested I can try to write the corresponding python code... >> >> >> >> >> >> >> >> Seb >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain >> >> >> >> wrote: >> >> >> >>> >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... No >> >> >> >>> code involved... >> >> >> >>> >> >> >> >>> In fact, just having the XML that I wrote in a file extend the >> >> >> >>> UI with a button to refresh the reader should be enough. >> >> >> >>> Need to figure out why the reader factory did not catch up the >> hint. >> >> >> >>> >> >> >> >>> That should be the only thing that you would need. >> >> >> >>> >> >> >> >>> Seb >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson >> >> >> >>> wrote: >> >> >> >>>> >> >> >> >>>> I was hoping that ParaView just had something built in. I >> >> >> >>>> would rather not have to create a plugin and distribute that >> >> >> >>>> along side my own software and to keep up on builds for all >> >> >> >>>> the various OS's and all of that. i tried that for a while >> >> >> >>>> and I just could not >> >> keep up. >> >> >> >>>> >> >> >> >>>> So either I am the only person who has asked for this or >> >> >> >>>> there is some over riding reason in the design of ParView why >> >> >> >>>> this type of functionality is not in ParaView. >> >> >> >>>> >> >> >> >>>> Thanks >> >> >> >>>> >> >> >> >> >> >> __________________________________________________________ >> >> >> _ >> >> >> >>>> Mike Jackson Principal Software Engineer >> >> >> >>>> BlueQuartz Software Dayton, Ohio >> >> >> >>>> mike.jackson at bluequartz.net www.bluequartz.net >> >> >> >>>> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu >> >> >> >>>> >> >> >> >>>> wrote: >> >> >> >>>> >> >> >> >>>> > hi you can try the approach of S?bastien >> >> >> >>>> > >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html >> >> >> >>>> > >> >> >> >>>> > I haven't tested yet. >> >> >> >>>> > >> >> >> >>>> > You can save the code as a macro, so you will have a button. >> >> >> >>>> > >> >> >> >>>> > Felipe >> >> >> >>>> > >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : >> >> >> >>>> >> Is there button where I can simply reload a data file that >> >> >> >>>> >> was read in a pipeline? >> >> >> >>>> >> >> >> >> >>>> >> We have a workflow where we process data into a file and >> >> >> >>>> >> view it in ParaView. it is becoming tedious to blow away >> >> >> >>>> >> the entire pipeline just to reload the new data. >> >> >> >>>> >> >> >> >> >>>> >> I know about state files but this still requires the user >> >> >> >>>> >> to go to the File->Load State... " menu and then select a state >> file. >> >> >> >>>> >> I would like to just select the data file in the Pipeline >> >> >> >>>> >> browser (XDMF File reader for us), and just click some >> >> >> >>>> >> button that just reloads data from the file. >> >> >> >>>> >> >> >> >> >>>> >> Or am I just missing something? I am using ParaView >> >> >> >>>> >> 3.98.1. I have to admit I have not tried any of the 4.0.RC* >> downloads. >> >> >> >>>> >> >> >> >> >>>> >> Thanks >> >> >> >>>> >> >> >> >> >> >> >> _________________________________________________________ >> >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net >> >> >> >>>> >> BlueQuartz Software www.bluequartz.net >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio >> >> >> >>>> >> _______________________________________________ >> >> >> >>>> >> Powered by www.kitware.com >> >> >> >>>> >> >> >> >> >>>> >> Visit other Kitware open-source projects at >> >> >> >>>> >> http://www.kitware.com/opensource/opensource.html >> >> >> >>>> >> >> >> >> >>>> >> Please keep messages on-topic and check the ParaView Wiki >> at: >> >> >> >>>> >> http://paraview.org/Wiki/ParaView >> >> >> >>>> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: >> >> >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >>>> > >> >> >> >>>> > >> >> >> >>>> > -- >> >> >> >>>> > Felipe Bordeu Weldt >> >> >> >>>> > Ing?nieur de Recherche >> >> >> >>>> > ------------------------------------- >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 >> >> >> >>>> > Fax. : 33 (0)2 40 74 74 06 >> >> >> >>>> > Felipe.Bordeu at ec-nantes.fr >> >> >> >>>> > Institut GeM - UMR CNRS 6183 ?cole Centrale Nantes >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE >> >> >> >>>> > ------------------------------------- >> >> >> >>>> > >> >> >> >>>> > _______________________________________________ >> >> >> >>>> > Powered by www.kitware.com >> >> >> >>>> > >> >> >> >>>> > Visit other Kitware open-source projects at >> >> >> >>>> > http://www.kitware.com/opensource/opensource.html >> >> >> >>>> > >> >> >> >>>> > Please keep messages on-topic and check the ParaView Wiki >> at: >> >> >> >>>> > http://paraview.org/Wiki/ParaView >> >> >> >>>> > >> >> >> >>>> > Follow this link to subscribe/unsubscribe: >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >>>> >> >> >> >>>> _______________________________________________ >> >> >> >>>> Powered by www.kitware.com >> >> >> >>>> >> >> >> >>>> Visit other Kitware open-source projects at >> >> >> >>>> http://www.kitware.com/opensource/opensource.html >> >> >> >>>> >> >> >> >>>> Please keep messages on-topic and check the ParaView Wiki at: >> >> >> >>>> http://paraview.org/Wiki/ParaView >> >> >> >>>> >> >> >> >>>> Follow this link to subscribe/unsubscribe: >> >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >>> >> >> >> >>> >> >> >> >> >> >> >> > >> >> >> > >> >> >> > _______________________________________________ >> >> >> > Powered by www.kitware.com >> >> >> > >> >> >> > Visit other Kitware open-source projects at >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> > >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> > >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Cory Quammen >> >> >> Research Associate >> >> >> Department of Computer Science >> >> >> The University of North Carolina at Chapel Hill >> >> >> >> >> >> >> >> >> ------------------------------ >> >> >> >> >> >> _______________________________________________ >> >> >> Powered by www.kitware.com >> >> >> >> >> >> Visit other Kitware open-source projects at >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> >> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 >> >> >> ***************************************** >> >> > >> >> > >> >> > >> >> >> __________________________________________________________ >> >> ___________ >> >> > ERBE Elektromedizin GmbH >> >> > Firmensitz: 72072 Tuebingen >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> > Registergericht: Stuttgart HRB 380137 >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> > http://paraview.org/Wiki/ParaView >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> > >> > >> __________________________________________________________ >> ___________ >> > ERBE Elektromedizin GmbH >> > Firmensitz: 72072 Tuebingen >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> > Registergericht: Stuttgart HRB 380137 >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview > > > _____________________________________________________________________ > ERBE Elektromedizin GmbH > Firmensitz: 72072 Tuebingen > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > Registergericht: Stuttgart HRB 380137 > From utkarsh.ayachit at kitware.com Mon Sep 15 11:16:02 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 15 Sep 2014 11:16:02 -0400 Subject: [Paraview] PV4.1, Custom Dock Widget: How to automatically add a glyph3d filter after loading data ? In-Reply-To: <5416F67D.4090602@inutech.de> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> <5416F67D.4090602@inutech.de> Message-ID: Attached is an example based on ParaView 4.2-RC1. As it shows, you cannot directly use VTK objects to create visualization pipelines in ParaView. While this can surely be done with 4.1 or earlier, I'd suggest basing off 4.2, if possible since it simplified a lot of this initialization. Utkarsh On Mon, Sep 15, 2014 at 10:23 AM, Florian Hoffmann wrote: > I would like to automatically add a glyph filter and render the correctly > scaled spheres after the user has opened a file in my custom dock widget. > I created a DockWidget using the example in /examples/Plugins/DockWidget. > When pressing a button a specific file is being opened for the user by the > following calls: > > void on_button_clicked() > { > QString xdmfFile = "C:\\..\\unknown_case.xdmf"; > > QStringList visuFiles; > > visuFiles.append(xdmfFile); > > pqPipelineSource* pqPlinesource = > pqLoadDataReaction::loadData(visuFiles); > > pqPlinesource->updatePipeline(); > > // TODO: > // add spherical glyph for loaded polyData > // scale spherical glyphs by a scalar attribute/property > // render glyphs > > } > > I would like to include that the code automatically adds spherical glyphs > and renders them for the data just loaded. > > I tried the following code but I am not sure if it works > > vtkSMProxy *myProxy = pqPlinesource->getProxy(); > > vtkObjectBase *myObject = myProxy->GetClientSideObject(); > > vtkAlgorithm *myvtkAlgo = vtkAlgorithm::SafeDownCast(myObject); > > vtkGlyph3D *myspheres = vtkGlyph3D::New(); > > myspheres->SetSourceConnection(myvtkAlgo->GetOutputPort()); > > > > In case this is supposed to work, how can I now update the pipeline and > render the spheres using C++ PV core functionality ? (The user should also > see the result in the pipeline browser dock of the GUI). > > In case my approach is totally wrong, what would be the right way of > handling this situation ? > > Thank you. > > Best regards, > > Florian > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: DockWidget.tar.gz Type: application/x-gzip Size: 3222 bytes Desc: not available URL: From kmorel at sandia.gov Mon Sep 15 11:29:26 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 15 Sep 2014 15:29:26 +0000 Subject: [Paraview] [EXTERNAL] fft of selection over time filter In-Reply-To: <9aaec371d2464398be869e272feb22df@ES05AMSNLNT.srn.sandia.gov> References: <9aaec371d2464398be869e272feb22df@ES05AMSNLNT.srn.sandia.gov> Message-ID: Alan, I assume you are talking about the FFT of Selection Over Time filter. I'm not sure I understand all of your questions but I'll try to answer them. * I got the filter to work on point data. Two caveats though. First, I think the data needs to be of a scalar floating point type. It doesn't work on vectors and it doesn't seem to work on ids. You also need to make a point selection (vs. a cell selection). I also noticed some funniness with how the selection got populated in the filter. For some reason when I create the filter it does not seem to populate the active selection correctly. I have to hit the "Copy Active Selection" button for it to get my selection properly. * [Shrug] Most filter's don't automatically create magnitudes of vectors. I guess if auto convert feature is on maybe it should, but that could also be expensive since the filter takes the FFT of all fields, not just one selected field. * You mean pick some range of time to apply the FFT over? That should have more to do with clipping the data values than picking some number of values to apply the FFT to. Is there a use case for that feature? * I recall implementing the filter a while ago. It's a little flaky, but it seems to work on the can dataset. * Open can.ex2. Select a cell at the bottom of the can. Add the FFT of Selection Over Time filter. Click "Copy Active Selection". Apply. You get a plot that is in kind of a U shape. -Ken From: , Walter Scott > Date: Friday, September 12, 2014 6:52 PM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] fft of selection over time filter I am trying to figure out the FFT of selection over time filter. My user is trying to use it on a velocity point vector field (in 2d, no less). So, a few questions: * This filter doesn't work on point data, but only cell data. Shouldn't it work on point data? * This filter doesn't create magnitudes of vectors. Shouldn't it if needed? * Since an FFT spans some array of data, shouldn't this span be changeable? For instance, 16 or 32 or 128? * Does this filter even work correctly? Has anyone ever used it? * Can anyone create a simple example using this filter? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matthias.Zenker at erbe-med.com Mon Sep 15 12:12:56 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Mon, 15 Sep 2014 16:12:56 +0000 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: That would be great! Matthias > -----Urspr?ngliche Nachricht----- > Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Gesendet: Montag, 15. September 2014 16:50 > An: Zenker, Dr. Matthias > Cc: Cory Quammen; paraview at paraview.org > Betreff: Re: [Paraview] How to simply "Reload" a data file > > Ah. since it's a file series, it would not work the way Cory is suggesting. I'll see > if I can cook up a Python script that can make this possible for now. We're > putting this on the roadmap for the next release (I know I've said that a few > times in the past :) ). > > Utkarsh > > On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias > wrote: > > Normally I load a time series, either a series of vtu files or a time collection > (pvd file containing the vtu file names with asociated timestamps). During > the simulation, new files are added to the series. So it would be nice to watch > the simulation going on by reloading from time to time. > > > > Matthias > > > >> -----Urspr?ngliche Nachricht----- > >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> Gesendet: Montag, 15. September 2014 16:28 > >> An: Zenker, Dr. Matthias > >> Cc: Cory Quammen; paraview at paraview.org > >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> > >> I suspect will not work with vtu. To understand this better, what is > >> that which is changing that you need to reload the file? Are you > >> loading a file series or a single file? > >> > >> Utkarsh > >> > >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias > >> wrote: > >> > Hi Cory, > >> > > >> > I use the reader for vtu format and pvd (vtu time collection). I > >> > tried to > >> modify the xml as follows: > >> > > >> > > >> > > >> > > >> > >> base_proxyname="VTUReader" class="vtuReader"> > >> > >> panel_widget="command_button"/> > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > But I cannot even load it as plugin. Presumably there are special > >> > keyword to > >> use for the name of the original reader. Is there a documentation > >> where I can find more information on that topic? > >> > > >> > Thanks, > >> > > >> > Matthias > >> > > >> >> -----Urspr?ngliche Nachricht----- > >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] > >> >> Gesendet: Montag, 15. September 2014 15:05 > >> >> An: Zenker, Dr. Matthias > >> >> Cc: paraview at paraview.org > >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> > >> >> Matthias, > >> >> > >> >> The method I suggested requires modifying ParaView's source code, > >> >> so it won't work for a binary distribution. > >> >> > >> >> As for the XML method, did you try to load an Xdmf file through > >> >> what should be the new "Xdmf Reader (Refresh button)" reader? If > >> >> you are loading a different type of file, this plugin will have no > >> >> effect because it provides a Refresh button only for the Xdmf > >> >> reader. You could modify the XML for other reader types, though. > >> >> > >> >> Thanks, > >> >> Cory > >> >> > >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias > >> >> wrote: > >> >> > Hi, > >> >> > > >> >> > I wanted to try the "Reload" button which presumably can be > >> >> > created by > >> >> one of the methods outlined below. But I am maybe too naive or am > >> >> missing > >> >> something: I have a Windoze binary distribution of ParaView 4.0.1. > >> >> I did not find the file indicated by Cory, and copying the xml > >> >> code given by S?bastien into a file and loading that as plugin had > >> >> no effect > >> visible to me. > >> >> > > >> >> > What am I missing here? > >> >> > > >> >> > Thank you, > >> >> > > >> >> > Matthias > >> >> > > >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- > >> >> >> bounces at paraview.org] Im Auftrag von paraview- > >> request at paraview.org > >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 > >> >> >> An: paraview at paraview.org > >> >> >> Betreff: Reload a file > >> >> >> > >> >> >> Send ParaView mailing list submissions to > >> >> >> paraview at paraview.org > >> >> >> > >> >> >> To subscribe or unsubscribe via the World Wide Web, visit > >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> or, via email, send a message with subject or body 'help' to > >> >> >> paraview-request at paraview.org > >> >> >> > >> >> >> You can reach the person managing the list at > >> >> >> paraview-owner at paraview.org > >> >> >> > >> >> >> When replying, please edit your Subject line so it is more > >> >> >> specific than > >> >> "Re: > >> >> >> Contents of ParaView digest..." > >> >> >> > >> >> >> > >> >> >> Today's Topics: > >> >> >> > >> >> >> 1. Re: How to simply "Reload" a data file (Cory Quammen) > >> >> >> > >> >> >> > >> >> >> --------------------------------------------------------------- > >> >> >> --- > >> >> >> --- > >> >> >> - > >> >> >> > >> >> >> Message: 1 > >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 > >> >> >> From: Cory Quammen > >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data file > >> >> >> To: Sebastien Jourdain > >> >> >> Cc: Michael Jackson , ParaView > >> >> >> > >> >> >> Message-ID: > >> >> >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> > >> >> >> Content-Type: text/plain; charset=ISO-8859-1 > >> >> >> > >> >> >> For what it's worth, I just experimented with adding the line > >> >> >> > >> >> >> >> >> >> panel_widget="command_button"/> > >> >> >> > >> >> >> to the CSV reader and XDMF reader in > >> >> >> > >> >> >> > >> >> > >> > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers > >> >> >> .xml > >> >> >> > >> >> >> The Refresh button appears among the other property widgets and > >> >> >> it indeed reloads the data set. > >> >> >> > >> >> >> I would happily add this to all the readers and submit a patch > >> >> >> to gerrit if it would be received well by the core ParaView > developers. > >> >> >> > >> >> >> Thanks, > >> >> >> Cory > >> >> >> > >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain > >> >> >> wrote: > >> >> >> > BTW that's the correct XML for you, just need to create a > >> >> >> > file with that in and load it as a plugin and you will have your > "Refresh" > >> button. > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" > >> >> >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> > >> >> >> > >> >> >> > panel_widget="command_button"/> > >> >> >> > > >> >> >> > >> >> >> > file_description="Xdmf Reader (Refresh button)" /> > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain > >> >> >> > wrote: > >> >> >> >> > >> >> >> >> Another approach could be a python macro that invalidate the > >> >> >> >> "active/selected' proxy in the pipeline, but that one will > >> >> >> >> require the usage of ParaView in built-in mode. > >> >> >> >> > >> >> >> >> If interested I can try to write the corresponding python code... > >> >> >> >> > >> >> >> >> Seb > >> >> >> >> > >> >> >> >> > >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain > >> >> >> >> wrote: > >> >> >> >>> > >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... > >> >> >> >>> No code involved... > >> >> >> >>> > >> >> >> >>> In fact, just having the XML that I wrote in a file extend > >> >> >> >>> the UI with a button to refresh the reader should be enough. > >> >> >> >>> Need to figure out why the reader factory did not catch up > >> >> >> >>> the > >> hint. > >> >> >> >>> > >> >> >> >>> That should be the only thing that you would need. > >> >> >> >>> > >> >> >> >>> Seb > >> >> >> >>> > >> >> >> >>> > >> >> >> >>> > >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson > >> >> >> >>> wrote: > >> >> >> >>>> > >> >> >> >>>> I was hoping that ParaView just had something built in. I > >> >> >> >>>> would rather not have to create a plugin and distribute > >> >> >> >>>> that along side my own software and to keep up on builds > >> >> >> >>>> for all the various OS's and all of that. i tried that for > >> >> >> >>>> a while and I just could not > >> >> keep up. > >> >> >> >>>> > >> >> >> >>>> So either I am the only person who has asked for this or > >> >> >> >>>> there is some over riding reason in the design of ParView > >> >> >> >>>> why this type of functionality is not in ParaView. > >> >> >> >>>> > >> >> >> >>>> Thanks > >> >> >> >>>> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> _ > >> >> >> >>>> Mike Jackson Principal Software Engineer > >> >> >> >>>> BlueQuartz Software Dayton, Ohio > >> >> >> >>>> mike.jackson at bluequartz.net www.bluequartz.net > >> >> >> >>>> > >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu > >> >> >> >>>> > >> >> >> >>>> wrote: > >> >> >> >>>> > >> >> >> >>>> > hi you can try the approach of S?bastien > >> >> >> >>>> > > >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html > >> >> >> >>>> > > >> >> >> >>>> > I haven't tested yet. > >> >> >> >>>> > > >> >> >> >>>> > You can save the code as a macro, so you will have a button. > >> >> >> >>>> > > >> >> >> >>>> > Felipe > >> >> >> >>>> > > >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : > >> >> >> >>>> >> Is there button where I can simply reload a data file > >> >> >> >>>> >> that was read in a pipeline? > >> >> >> >>>> >> > >> >> >> >>>> >> We have a workflow where we process data into a file > >> >> >> >>>> >> and view it in ParaView. it is becoming tedious to blow > >> >> >> >>>> >> away the entire pipeline just to reload the new data. > >> >> >> >>>> >> > >> >> >> >>>> >> I know about state files but this still requires the > >> >> >> >>>> >> user to go to the File->Load State... " menu and then > >> >> >> >>>> >> select a state > >> file. > >> >> >> >>>> >> I would like to just select the data file in the > >> >> >> >>>> >> Pipeline browser (XDMF File reader for us), and just > >> >> >> >>>> >> click some button that just reloads data from the file. > >> >> >> >>>> >> > >> >> >> >>>> >> Or am I just missing something? I am using ParaView > >> >> >> >>>> >> 3.98.1. I have to admit I have not tried any of the > >> >> >> >>>> >> 4.0.RC* > >> downloads. > >> >> >> >>>> >> > >> >> >> >>>> >> Thanks > >> >> >> >>>> >> > >> >> >> > >> >> > >> > _________________________________________________________ > >> >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net > >> >> >> >>>> >> BlueQuartz Software www.bluequartz.net > >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio > >> >> >> >>>> >> > _______________________________________________ > >> >> >> >>>> >> Powered by www.kitware.com > >> >> >> >>>> >> > >> >> >> >>>> >> Visit other Kitware open-source projects at > >> >> >> >>>> >> http://www.kitware.com/opensource/opensource.html > >> >> >> >>>> >> > >> >> >> >>>> >> Please keep messages on-topic and check the ParaView > >> >> >> >>>> >> Wiki > >> at: > >> >> >> >>>> >> http://paraview.org/Wiki/ParaView > >> >> >> >>>> >> > >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: > >> >> >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >>>> > > >> >> >> >>>> > > >> >> >> >>>> > -- > >> >> >> >>>> > Felipe Bordeu Weldt > >> >> >> >>>> > Ing?nieur de Recherche > >> >> >> >>>> > ------------------------------------- > >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 > >> >> >> >>>> > Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 > >> >> >> >>>> > ?cole Centrale Nantes > >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE > >> >> >> >>>> > ------------------------------------- > >> >> >> >>>> > > >> >> >> >>>> > > _______________________________________________ > >> >> >> >>>> > Powered by www.kitware.com > >> >> >> >>>> > > >> >> >> >>>> > Visit other Kitware open-source projects at > >> >> >> >>>> > http://www.kitware.com/opensource/opensource.html > >> >> >> >>>> > > >> >> >> >>>> > Please keep messages on-topic and check the ParaView > >> >> >> >>>> > Wiki > >> at: > >> >> >> >>>> > http://paraview.org/Wiki/ParaView > >> >> >> >>>> > > >> >> >> >>>> > Follow this link to subscribe/unsubscribe: > >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >>>> > >> >> >> >>>> _______________________________________________ > >> >> >> >>>> Powered by www.kitware.com > >> >> >> >>>> > >> >> >> >>>> Visit other Kitware open-source projects at > >> >> >> >>>> http://www.kitware.com/opensource/opensource.html > >> >> >> >>>> > >> >> >> >>>> Please keep messages on-topic and check the ParaView Wiki > at: > >> >> >> >>>> http://paraview.org/Wiki/ParaView > >> >> >> >>>> > >> >> >> >>>> Follow this link to subscribe/unsubscribe: > >> >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >>> > >> >> >> >>> > >> >> >> >> > >> >> >> > > >> >> >> > > >> >> >> > _______________________________________________ > >> >> >> > Powered by www.kitware.com > >> >> >> > > >> >> >> > Visit other Kitware open-source projects at > >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> > > >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> > > >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> > > >> >> >> > >> >> >> > >> >> >> > >> >> >> -- > >> >> >> Cory Quammen > >> >> >> Research Associate > >> >> >> Department of Computer Science > >> >> >> The University of North Carolina at Chapel Hill > >> >> >> > >> >> >> > >> >> >> ------------------------------ > >> >> >> > >> >> >> _______________________________________________ > >> >> >> Powered by www.kitware.com > >> >> >> > >> >> >> Visit other Kitware open-source projects at > >> >> >> http://www.kitware.com/opensource/opensource.html > >> >> >> > >> >> >> Please keep messages on-topic and check the ParaView Wiki at: > >> >> >> http://paraview.org/Wiki/ParaView > >> >> >> > >> >> >> Follow this link to subscribe/unsubscribe: > >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> > >> >> >> > >> >> >> End of ParaView Digest, Vol 110, Issue 42 > >> >> >> ***************************************** > >> >> > > >> >> > > >> >> > > >> >> > >> > __________________________________________________________ > >> >> ___________ > >> >> > ERBE Elektromedizin GmbH > >> >> > Firmensitz: 72072 Tuebingen > >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> > Registergericht: Stuttgart HRB 380137 > >> >> > > >> >> > _______________________________________________ > >> >> > Powered by www.kitware.com > >> >> > > >> >> > Visit other Kitware open-source projects at > >> >> > http://www.kitware.com/opensource/opensource.html > >> >> > > >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> > http://paraview.org/Wiki/ParaView > >> >> > > >> >> > Follow this link to subscribe/unsubscribe: > >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > >> > > >> > > >> > __________________________________________________________ > >> ___________ > >> > ERBE Elektromedizin GmbH > >> > Firmensitz: 72072 Tuebingen > >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> > Registergericht: Stuttgart HRB 380137 > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > __________________________________________________________ > ___________ > > ERBE Elektromedizin GmbH > > Firmensitz: 72072 Tuebingen > > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > > Registergericht: Stuttgart HRB 380137 > > _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 From qifl2008 at gmail.com Mon Sep 15 13:19:43 2014 From: qifl2008 at gmail.com (fenglei qi) Date: Mon, 15 Sep 2014 12:19:43 -0500 Subject: [Paraview] Data structure for 'table to structured grid' filter Message-ID: Dear all, I met a problem when I converted table data to structured grid. The data is arranged as attached test.csv file. I set up Whole extent as ((0,2), (0,2), (0,1)). But the grid system does not look right. See below. I think the problem is the data ordering problem that are usually talked about in previous threads. Can anyone give a example of how to use this filter or give me some information on how to do it correctly. Thanks for all your considering. [image: ???? 1] Fenglei Qi -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Grid_wireframe.PNG Type: image/png Size: 38733 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test.csv Type: text/csv Size: 133 bytes Desc: not available URL: From andy.bauer at kitware.com Mon Sep 15 13:29:45 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 15 Sep 2014 13:29:45 -0400 Subject: [Paraview] Data structure for 'table to structured grid' filter In-Reply-To: References: Message-ID: Hi, I think the issue is that your ordering is wrong. VTK/ParaView assumes that you iterate over x the fastest, then y, and z is iterated over the slowest. For the table to structured grid filter, if you set the whole extent to [0, 2, 0, 1, 0, 2] and the X Column to y, Y Column to z and Z Column to x then at least the connectivity looks correct. If this output has the wrong orientation you can either change the ordering of the CXV file or use the transform filter to rotate it around. Andy On Mon, Sep 15, 2014 at 1:19 PM, fenglei qi wrote: > Dear all, > > I met a problem when I converted table data to structured grid. The data > is arranged as attached test.csv file. I set up Whole extent as ((0,2), > (0,2), (0,1)). But the grid system does not look right. See below. I think > the problem is the data ordering problem that are usually talked about in > previous threads. Can anyone give a example of how to use this filter or > give me some information on how to do it correctly. Thanks for all your > considering. > [image: ???? 1] > > Fenglei Qi > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Grid_wireframe.PNG Type: image/png Size: 38733 bytes Desc: not available URL: From rhodes at cs.olemiss.edu Mon Sep 15 14:00:04 2014 From: rhodes at cs.olemiss.edu (Philip J. Rhodes) Date: Mon, 15 Sep 2014 13:00:04 -0500 Subject: [Paraview] Open File Dialog Box Hang on OSX Message-ID: <90C865AD-8A61-4526-96CB-143CA90D709C@cs.olemiss.edu> Hello, I wanted to post a solution to a problem that I had with ParaView 4.1.0 on Mac OSX 10.9.4. The problem was a hang (not a crash) when selecting the ?Open? file menu item. The dialog box eventually appeared after a spinning beachball went away, but then complained that it could not find a certain AppleShare volume that was no longer in use on our local network. The dialog box also listed items that were taken from the Finder Sidebar, but were very out of date. This last point made me realize what was going on. Paraview was (perhaps indirectly) reading stale information out of ~/Library/Preferences/org.apple.sidebarlists.plist . Upon inspection, I found the stale info in this file. It seems that back in 2011 the finder was updated, and no longer uses some of this information, but Paraview still does. I removed this file and also set my finder sidebar preferences to not display shared volumes, or anything that I didn?t strictly need. You may find a restart is necessary in order for the change to take effect, but I?ve fixed the problem on three machines. I?m not sure how widespread this problem is, or if it?s even specifically a Paraview issue, but I thought I?d post the information in case it?s helpful to someone. -Phil ? Phil Rhodes Associate Professor Department of Computer and Information Science University of Mississippi -------------- next part -------------- An HTML attachment was scrubbed... URL: From qifl2008 at gmail.com Mon Sep 15 14:41:16 2014 From: qifl2008 at gmail.com (fenglei qi) Date: Mon, 15 Sep 2014 13:41:16 -0500 Subject: [Paraview] Data structure for 'table to structured grid' filter In-Reply-To: References: Message-ID: Hi Andy, It works in your way. Can you provide more information on how to make a correct ordering of points. I don't understand how the connectivity is built in Paraview. Any sources for me to refer to? Thank you. Fenglei 2014-09-15 12:29 GMT-05:00 Andy Bauer : > Hi, > > I think the issue is that your ordering is wrong. VTK/ParaView assumes > that you iterate over x the fastest, then y, and z is iterated over the > slowest. > > For the table to structured grid filter, if you set the whole extent to > [0, 2, 0, 1, 0, 2] and the X Column to y, Y Column to z and Z Column to x > then at least the connectivity looks correct. If this output has the wrong > orientation you can either change the ordering of the CXV file or use the > transform filter to rotate it around. > > Andy > > On Mon, Sep 15, 2014 at 1:19 PM, fenglei qi wrote: > >> Dear all, >> >> I met a problem when I converted table data to structured grid. The data >> is arranged as attached test.csv file. I set up Whole extent as ((0,2), >> (0,2), (0,1)). But the grid system does not look right. See below. I think >> the problem is the data ordering problem that are usually talked about in >> previous threads. Can anyone give a example of how to use this filter or >> give me some information on how to do it correctly. Thanks for all your >> considering. >> [image: ???? 1] >> >> Fenglei Qi >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Grid_wireframe.PNG Type: image/png Size: 38733 bytes Desc: not available URL: From Michael.M.Stephens at erdc.dren.mil Mon Sep 15 15:54:29 2014 From: Michael.M.Stephens at erdc.dren.mil (Stephens, Michael M ERDC-RDE-ITL-MS) Date: Mon, 15 Sep 2014 19:54:29 +0000 Subject: [Paraview] slightly puzzled by paraview extract block behavior (UNCLASSIFIED) Message-ID: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FB445@MS-EX1VKS.erdc.dren.mil> Classification: UNCLASSIFIED Caveats: FOUO had someone ask me for help with a problem they were having with paraview v4.1.0 in server/client mode. steps are: i) read in an ensight case file, ii) use Extract Block filter to yank out a particular block, iii) color extracted block with various variables. simple enough. let me say up front that the data is pretty small (order of 100k points, 450k cells). we ran this using a varying number of procs in a single node. when the number of procs got to be 14 or greater (16 cores in the server nodes) the extract block step lost the data variables. the geometry was correct still but none of the data variables survived the operation. I'll stipulate that it makes little sense to use more than one proc for data this small. but why does the extract block not still work? slightly puzzled. -m Classification: UNCLASSIFIED Caveats: FOUO -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Sep 15 16:22:32 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 15 Sep 2014 16:22:32 -0400 Subject: [Paraview] slightly puzzled by paraview extract block behavior (UNCLASSIFIED) In-Reply-To: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FB445@MS-EX1VKS.erdc.dren.mil> References: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FB445@MS-EX1VKS.erdc.dren.mil> Message-ID: Hey Mike, I'm getting something funky when reading an Ensight file with 14 processes as well that I don't see with 2 or 13 processes (I didn't bother trying with other amounts). The error I get is: ERROR: In /home/acbauer/CODE/ParaView/ParaView-v4.1.0/VTK/Common/DataModel/vtkDataSet.cxx, line 414 vtkStructuredGrid (0xa70560): Point array DENS with 1 components, only has -325 tuples but there are 0 points This is just for loading in the file though and not even using the extract block filter. Are you getting a similar error? I'm getting the error with the naca.bin.case at http://www.paraview.org/gitweb?p=ParaViewData.git;a=tree;f=Data/EnSight;h=fc6cbe6fc7851e2f3bae520f4cf4b933ab963c93;hb=HEAD. Best, Andy On Mon, Sep 15, 2014 at 3:54 PM, Stephens, Michael M ERDC-RDE-ITL-MS < Michael.M.Stephens at erdc.dren.mil> wrote: > Classification: UNCLASSIFIED > Caveats: FOUO > > had someone ask me for help with a problem they were having with > paraview v4.1.0 in server/client mode. > > > > steps are: i) read in an ensight case file, ii) use Extract Block filter > to yank out a particular block, iii) color extracted block with various > variables. > > simple enough. > > > > let me say up front that the data is pretty small (order of 100k points, > 450k cells). > > we ran this using a varying number of procs in a single node. > > > > when the number of procs got to be 14 or greater (16 cores in the server > nodes) the extract block step lost the data variables. > > the geometry was correct still but none of the data variables survived the > operation. > > > > I?ll stipulate that it makes little sense to use more than one proc for > data this small. > > > > but why does the extract block not still work? > > > > slightly puzzled. > > > > -m > > Classification: UNCLASSIFIED > Caveats: FOUO > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Michael.M.Stephens at erdc.dren.mil Mon Sep 15 16:53:50 2014 From: Michael.M.Stephens at erdc.dren.mil (Stephens, Michael M ERDC-RDE-ITL-MS) Date: Mon, 15 Sep 2014 20:53:50 +0000 Subject: [Paraview] slightly puzzled by paraview extract block behavior (UNCLASSIFIED) In-Reply-To: References: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FB445@MS-EX1VKS.erdc.dren.mil> Message-ID: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FC492@MS-EX1VKS.erdc.dren.mil> Classification: UNCLASSIFIED Caveats: FOUO in all cases for the ensight data we are working with, there is no READ error. there is no error reported at all either for reading or extract block operations. the extract block silently fails to pass the variable data for larger core counts on the data we are working on. geometry seems okay. btw, I am not very fluent in my understanding of the ensight formats (case files or otherwise) -m From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: Monday, September 15, 2014 3:23 PM To: Stephens, Michael M ERDC-RDE-ITL-MS Cc: paraview at paraview.org Subject: Re: [Paraview] slightly puzzled by paraview extract block behavior (UNCLASSIFIED) Hey Mike, I'm getting something funky when reading an Ensight file with 14 processes as well that I don't see with 2 or 13 processes (I didn't bother trying with other amounts). The error I get is: ERROR: In /home/acbauer/CODE/ParaView/ParaView-v4.1.0/VTK/Common/DataModel/vtkDataSet.cxx, line 414 vtkStructuredGrid (0xa70560): Point array DENS with 1 components, only has -325 tuples but there are 0 points This is just for loading in the file though and not even using the extract block filter. Are you getting a similar error? I'm getting the error with the naca.bin.case at http://www.paraview.org/gitweb?p=ParaViewData.git;a=tree;f=Data/EnSight;h=fc6cbe6fc7851e2f3bae520f4cf4b933ab963c93;hb=HEAD. Best, Andy On Mon, Sep 15, 2014 at 3:54 PM, Stephens, Michael M ERDC-RDE-ITL-MS > wrote: Classification: UNCLASSIFIED Caveats: FOUO had someone ask me for help with a problem they were having with paraview v4.1.0 in server/client mode. steps are: i) read in an ensight case file, ii) use Extract Block filter to yank out a particular block, iii) color extracted block with various variables. simple enough. let me say up front that the data is pretty small (order of 100k points, 450k cells). we ran this using a varying number of procs in a single node. when the number of procs got to be 14 or greater (16 cores in the server nodes) the extract block step lost the data variables. the geometry was correct still but none of the data variables survived the operation. I'll stipulate that it makes little sense to use more than one proc for data this small. but why does the extract block not still work? slightly puzzled. -m Classification: UNCLASSIFIED Caveats: FOUO _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: FOUO -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Sep 15 17:00:30 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 15 Sep 2014 17:00:30 -0400 Subject: [Paraview] slightly puzzled by paraview extract block behavior (UNCLASSIFIED) In-Reply-To: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FC492@MS-EX1VKS.erdc.dren.mil> References: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FB445@MS-EX1VKS.erdc.dren.mil> <4EBFE0C75EDFCB4EA50E6496FB1072C0622FC492@MS-EX1VKS.erdc.dren.mil> Message-ID: Hmm, well I have no idea if we're hitting the same bug or not but it seems like too much of a coincidence that this is happening for both of us at 14 procs but not 13. I created a mantis issue at http://www.paraview.org/Bug/view.php?id=14996. Feel free to add to it if you can share your Ensight file. Regards, Andy On Mon, Sep 15, 2014 at 4:53 PM, Stephens, Michael M ERDC-RDE-ITL-MS < Michael.M.Stephens at erdc.dren.mil> wrote: > Classification: UNCLASSIFIED > Caveats: FOUO > > in all cases for the ensight data we are working with, there is no READ > error. > > there is no error reported at all either for reading or extract block > operations. > > > > the extract block silently fails to pass the variable data for larger core > counts on the data we are working on. geometry seems okay. > > > > btw, I am not very fluent in my understanding of the ensight formats (case > files or otherwise) > > > > -m > > > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com] > *Sent:* Monday, September 15, 2014 3:23 PM > *To:* Stephens, Michael M ERDC-RDE-ITL-MS > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] slightly puzzled by paraview extract block > behavior (UNCLASSIFIED) > > > > Hey Mike, > > I'm getting something funky when reading an Ensight file with 14 processes > as well that I don't see with 2 or 13 processes (I didn't bother trying > with other amounts). The error I get is: > ERROR: In > /home/acbauer/CODE/ParaView/ParaView-v4.1.0/VTK/Common/DataModel/vtkDataSet.cxx, > line 414 > vtkStructuredGrid (0xa70560): Point array DENS with 1 components, only has > -325 tuples but there are 0 points > > This is just for loading in the file though and not even using the extract > block filter. Are you getting a similar error? > > I'm getting the error with the naca.bin.case at > http://www.paraview.org/gitweb?p=ParaViewData.git;a=tree;f=Data/EnSight;h=fc6cbe6fc7851e2f3bae520f4cf4b933ab963c93;hb=HEAD. > > > Best, > > Andy > > > > On Mon, Sep 15, 2014 at 3:54 PM, Stephens, Michael M ERDC-RDE-ITL-MS < > Michael.M.Stephens at erdc.dren.mil> wrote: > > Classification: UNCLASSIFIED > Caveats: FOUO > > had someone ask me for help with a problem they were having with paraview > v4.1.0 in server/client mode. > > > > steps are: i) read in an ensight case file, ii) use Extract Block filter > to yank out a particular block, iii) color extracted block with various > variables. > > simple enough. > > > > let me say up front that the data is pretty small (order of 100k points, > 450k cells). > > we ran this using a varying number of procs in a single node. > > > > when the number of procs got to be 14 or greater (16 cores in the server > nodes) the extract block step lost the data variables. > > the geometry was correct still but none of the data variables survived the > operation. > > > > I?ll stipulate that it makes little sense to use more than one proc for > data this small. > > > > but why does the extract block not still work? > > > > slightly puzzled. > > > > -m > > > Classification: UNCLASSIFIED > Caveats: FOUO > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > Classification: UNCLASSIFIED > Caveats: FOUO > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Michael.M.Stephens at erdc.dren.mil Mon Sep 15 17:06:52 2014 From: Michael.M.Stephens at erdc.dren.mil (Stephens, Michael M ERDC-RDE-ITL-MS) Date: Mon, 15 Sep 2014 21:06:52 +0000 Subject: [Paraview] slightly puzzled by paraview extract block behavior (UNCLASSIFIED) In-Reply-To: References: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FB445@MS-EX1VKS.erdc.dren.mil> <4EBFE0C75EDFCB4EA50E6496FB1072C0622FC492@MS-EX1VKS.erdc.dren.mil> Message-ID: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FC4B1@MS-EX1VKS.erdc.dren.mil> Classification: UNCLASSIFIED Caveats: FOUO this just in..... using the same data you are ( ParaViewdata: naca.bin.case, to eliminate one difference at least) when I tried 16 procs on the server side the server seems to be hung. didn't crash the server (not yet at least) but it might as well have because the client is frozen waiting on the server. the server is accumulating run time but nothing else. -m From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: Monday, September 15, 2014 4:01 PM To: Stephens, Michael M ERDC-RDE-ITL-MS Cc: paraview at paraview.org Subject: Re: [Paraview] slightly puzzled by paraview extract block behavior (UNCLASSIFIED) Hmm, well I have no idea if we're hitting the same bug or not but it seems like too much of a coincidence that this is happening for both of us at 14 procs but not 13. I created a mantis issue at http://www.paraview.org/Bug/view.php?id=14996. Feel free to add to it if you can share your Ensight file. Regards, Andy On Mon, Sep 15, 2014 at 4:53 PM, Stephens, Michael M ERDC-RDE-ITL-MS > wrote: Classification: UNCLASSIFIED Caveats: FOUO in all cases for the ensight data we are working with, there is no READ error. there is no error reported at all either for reading or extract block operations. the extract block silently fails to pass the variable data for larger core counts on the data we are working on. geometry seems okay. btw, I am not very fluent in my understanding of the ensight formats (case files or otherwise) -m From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: Monday, September 15, 2014 3:23 PM To: Stephens, Michael M ERDC-RDE-ITL-MS Cc: paraview at paraview.org Subject: Re: [Paraview] slightly puzzled by paraview extract block behavior (UNCLASSIFIED) Hey Mike, I'm getting something funky when reading an Ensight file with 14 processes as well that I don't see with 2 or 13 processes (I didn't bother trying with other amounts). The error I get is: ERROR: In /home/acbauer/CODE/ParaView/ParaView-v4.1.0/VTK/Common/DataModel/vtkDataSet.cxx, line 414 vtkStructuredGrid (0xa70560): Point array DENS with 1 components, only has -325 tuples but there are 0 points This is just for loading in the file though and not even using the extract block filter. Are you getting a similar error? I'm getting the error with the naca.bin.case at http://www.paraview.org/gitweb?p=ParaViewData.git;a=tree;f=Data/EnSight;h=fc6cbe6fc7851e2f3bae520f4cf4b933ab963c93;hb=HEAD. Best, Andy On Mon, Sep 15, 2014 at 3:54 PM, Stephens, Michael M ERDC-RDE-ITL-MS > wrote: Classification: UNCLASSIFIED Caveats: FOUO had someone ask me for help with a problem they were having with paraview v4.1.0 in server/client mode. steps are: i) read in an ensight case file, ii) use Extract Block filter to yank out a particular block, iii) color extracted block with various variables. simple enough. let me say up front that the data is pretty small (order of 100k points, 450k cells). we ran this using a varying number of procs in a single node. when the number of procs got to be 14 or greater (16 cores in the server nodes) the extract block step lost the data variables. the geometry was correct still but none of the data variables survived the operation. I'll stipulate that it makes little sense to use more than one proc for data this small. but why does the extract block not still work? slightly puzzled. -m Classification: UNCLASSIFIED Caveats: FOUO _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: FOUO Classification: UNCLASSIFIED Caveats: FOUO -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Sep 15 17:14:25 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 15 Sep 2014 17:14:25 -0400 Subject: [Paraview] slightly puzzled by paraview extract block behavior (UNCLASSIFIED) In-Reply-To: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FC4B1@MS-EX1VKS.erdc.dren.mil> References: <4EBFE0C75EDFCB4EA50E6496FB1072C0622FB445@MS-EX1VKS.erdc.dren.mil> <4EBFE0C75EDFCB4EA50E6496FB1072C0622FC492@MS-EX1VKS.erdc.dren.mil> <4EBFE0C75EDFCB4EA50E6496FB1072C0622FC4B1@MS-EX1VKS.erdc.dren.mil> Message-ID: If you check the output on the server you'll probably see the error I got. Since the client is waiting for the server to finish the error doesn't pop up on the client. If your file is shareable, maybe you could add that to the bug tracker since they might be different and I'd hate to assume we fixed your bug when we only verified that we fixed my bug. On Mon, Sep 15, 2014 at 5:06 PM, Stephens, Michael M ERDC-RDE-ITL-MS < Michael.M.Stephens at erdc.dren.mil> wrote: > Classification: UNCLASSIFIED > Caveats: FOUO > > this just in?.. > > > > using the same data you are ( ParaViewdata: naca.bin.case, to eliminate > one difference at least) > > > > when I tried 16 procs on the server side the server seems to be hung. > didn?t crash the server (not yet at least) > > but it might as well have because the client is frozen waiting on the > server. the server is accumulating run time but nothing else. > > > > -m > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com] > *Sent:* Monday, September 15, 2014 4:01 PM > > *To:* Stephens, Michael M ERDC-RDE-ITL-MS > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] slightly puzzled by paraview extract block > behavior (UNCLASSIFIED) > > > > Hmm, well I have no idea if we're hitting the same bug or not but it seems > like too much of a coincidence that this is happening for both of us at 14 > procs but not 13. I created a mantis issue at > http://www.paraview.org/Bug/view.php?id=14996. Feel free to add to it if > you can share your Ensight file. > > Regards, > Andy > > > > On Mon, Sep 15, 2014 at 4:53 PM, Stephens, Michael M ERDC-RDE-ITL-MS < > Michael.M.Stephens at erdc.dren.mil> wrote: > > Classification: UNCLASSIFIED > Caveats: FOUO > > in all cases for the ensight data we are working with, there is no READ > error. > > there is no error reported at all either for reading or extract block > operations. > > > > the extract block silently fails to pass the variable data for larger core > counts on the data we are working on. geometry seems okay. > > > > btw, I am not very fluent in my understanding of the ensight formats (case > files or otherwise) > > > > -m > > > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com] > *Sent:* Monday, September 15, 2014 3:23 PM > *To:* Stephens, Michael M ERDC-RDE-ITL-MS > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] slightly puzzled by paraview extract block > behavior (UNCLASSIFIED) > > > > Hey Mike, > > I'm getting something funky when reading an Ensight file with 14 processes > as well that I don't see with 2 or 13 processes (I didn't bother trying > with other amounts). The error I get is: > ERROR: In > /home/acbauer/CODE/ParaView/ParaView-v4.1.0/VTK/Common/DataModel/vtkDataSet.cxx, > line 414 > vtkStructuredGrid (0xa70560): Point array DENS with 1 components, only has > -325 tuples but there are 0 points > > This is just for loading in the file though and not even using the extract > block filter. Are you getting a similar error? > > I'm getting the error with the naca.bin.case at > http://www.paraview.org/gitweb?p=ParaViewData.git;a=tree;f=Data/EnSight;h=fc6cbe6fc7851e2f3bae520f4cf4b933ab963c93;hb=HEAD. > > > Best, > > Andy > > > > On Mon, Sep 15, 2014 at 3:54 PM, Stephens, Michael M ERDC-RDE-ITL-MS < > Michael.M.Stephens at erdc.dren.mil> wrote: > > Classification: UNCLASSIFIED > Caveats: FOUO > > had someone ask me for help with a problem they were having with paraview > v4.1.0 in server/client mode. > > > > steps are: i) read in an ensight case file, ii) use Extract Block filter > to yank out a particular block, iii) color extracted block with various > variables. > > simple enough. > > > > let me say up front that the data is pretty small (order of 100k points, > 450k cells). > > we ran this using a varying number of procs in a single node. > > > > when the number of procs got to be 14 or greater (16 cores in the server > nodes) the extract block step lost the data variables. > > the geometry was correct still but none of the data variables survived the > operation. > > > > I?ll stipulate that it makes little sense to use more than one proc for > data this small. > > > > but why does the extract block not still work? > > > > slightly puzzled. > > > > -m > > > Classification: UNCLASSIFIED > Caveats: FOUO > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > Classification: UNCLASSIFIED > Caveats: FOUO > > > > > Classification: UNCLASSIFIED > Caveats: FOUO > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Tue Sep 16 04:29:07 2014 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Tue, 16 Sep 2014 18:29:07 +1000 Subject: [Paraview] Parametric functions. Message-ID: A while back there was a request for something different from the usual sphere source. So I have created an xml file to access the parametric surface functions in ParaView along with a reverse sense programmable filter. It was an interesting exercise that revealed some deficiencies in the parametric function implementations that have been fixed in the VTK master. I am happy to contribute this if people feel it will be useful. Just let me know how. Regards Andrew -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From e0425375 at gmail.com Tue Sep 16 06:33:44 2014 From: e0425375 at gmail.com (Florian Bruckner) Date: Tue, 16 Sep 2014 12:33:44 +0200 Subject: [Paraview] howto move an object depending on actual time Message-ID: <54181208.3080906@gmail.com> hello, i would like to create an animation of moving objects using the animation view. unfortunately the positions of the objects stored within the data file are stationary, so i have to manually define the movement anyhow. is there a simple method to archive this using the animation inspector? (i am using paraview 4.1.0) alternatively i found a method to use the python calculator to translate the object. if i could access the actual time it would be possible to define the trajectory of the moving particle. is this possible? thanks FloB From florian.hoffmann at inutech.de Tue Sep 16 08:11:22 2014 From: florian.hoffmann at inutech.de (Florian Hoffmann) Date: Tue, 16 Sep 2014 14:11:22 +0200 Subject: [Paraview] PV4.1, Custom Dock Widget: How to automatically add a glyph3d filter after loading data ? In-Reply-To: References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> <5416F67D.4090602@inutech.de> Message-ID: <541828EA.3060509@inutech.de> Dear Utkarsh, thank you very much for your fast reply and the provided example. I compiled PV4.2RC2 from source and just tried to compile your example. Nevertheless I receive a compilation error complaining that the file vtkSMParaViewPipelineControllerWithRendering.h cannot be found. Where is this file supposed to be residing ? Thank you. Best regards, Florian Am 15.09.2014 um 17:16 schrieb Utkarsh Ayachit : > Attached is an example based on ParaView 4.2-RC1. As it shows, you > cannot directly use VTK objects to create visualization pipelines in > ParaView. While this can surely be done with 4.1 or earlier, I'd > suggest basing off 4.2, if possible since it simplified a lot of this > initialization. > > Utkarsh > > On Mon, Sep 15, 2014 at 10:23 AM, Florian Hoffmann > wrote: >> I would like to automatically add a glyph filter and render the correctly >> scaled spheres after the user has opened a file in my custom dock widget. >> I created a DockWidget using the example in /examples/Plugins/DockWidget. >> When pressing a button a specific file is being opened for the user >> by the >> following calls: >> >> void on_button_clicked() >> { >> QString xdmfFile = "C:\\..\\unknown_case.xdmf"; >> >> QStringList visuFiles; >> >> visuFiles.append(xdmfFile); >> >> pqPipelineSource* pqPlinesource = >> pqLoadDataReaction::loadData(visuFiles); >> >> pqPlinesource->updatePipeline(); >> >> // TODO: >> // add spherical glyph for loaded polyData >> // scale spherical glyphs by a scalar attribute/property >> // render glyphs >> >> } >> >> I would like to include that the code automatically adds spherical glyphs >> and renders them for the data just loaded. >> >> I tried the following code but I am not sure if it works >> >> vtkSMProxy *myProxy = pqPlinesource->getProxy(); >> >> vtkObjectBase *myObject = myProxy->GetClientSideObject(); >> >> vtkAlgorithm *myvtkAlgo = vtkAlgorithm::SafeDownCast(myObject); >> >> vtkGlyph3D *myspheres = vtkGlyph3D::New(); >> >> myspheres->SetSourceConnection(myvtkAlgo->GetOutputPort()); >> >> >> >> In case this is supposed to work, how can I now update the pipeline and >> render the spheres using C++ PV core functionality ? (The user should >> also >> see the result in the pipeline browser dock of the GUI). >> >> In case my approach is totally wrong, what would be the right way of >> handling this situation ? >> >> Thank you. >> >> Best regards, >> >> Florian >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From f_magician at mac.com Tue Sep 16 08:32:18 2014 From: f_magician at mac.com (Magician) Date: Tue, 16 Sep 2014 21:32:18 +0900 Subject: [Paraview] Save Stereo Screenshots with Python In-Reply-To: References: Message-ID: Hi all, I?d like to export left and right-eye images with Python. Any ideas? I?m using ParaView 4.1.0 and 4.2 RC1. Magician On Sep 6, 2014, at 19:25, Magician wrote: > Hi all, > > > I want to export screenshots of stereo images with Python. > The stereo mode is SplitViewportHorizontal (Side-by-Side). > > When I export images larger than active views, I get bad results as the attached image. > How can I export large stereo screenshots correctly? > Or I?m planning to export left and right-eye images separately, and composite them > with other softwares. > How can I export left or right-eye images with Python? > > > Magician From utkarsh.ayachit at kitware.com Tue Sep 16 08:41:10 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 16 Sep 2014 08:41:10 -0400 Subject: [Paraview] howto move an object depending on actual time In-Reply-To: <54181208.3080906@gmail.com> References: <54181208.3080906@gmail.com> Message-ID: I'd suggest using "Programmable Filter" instead of "Python Calculator". Refer to vtkTimeToTexConvertor::RequestData() [1] for how to access DATA_TIME_STEP value. You can write an equivalent script in "Script" part for the Programmable Filter to access the time value. Utkarsh [1] https://github.com/Kitware/ParaView/blob/ad70367102a1d9779435e9949d84a576e68a6ee8/ParaViewCore/VTKExtensions/Default/vtkTimeToTextConvertor.cxx On Tue, Sep 16, 2014 at 6:33 AM, Florian Bruckner wrote: > hello, > > i would like to create an animation of moving objects using the animation > view. unfortunately the positions of the objects stored within the data file > are stationary, so i have to manually define the movement anyhow. > > is there a simple method to archive this using the animation inspector? (i > am using paraview 4.1.0) > > alternatively i found a method to use the python calculator to translate the > object. if i could access the actual time it would be possible to define the > trajectory of the moving particle. is this possible? > > thanks > FloB > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Tue Sep 16 08:43:20 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 16 Sep 2014 08:43:20 -0400 Subject: [Paraview] PV4.1, Custom Dock Widget: How to automatically add a glyph3d filter after loading data ? In-Reply-To: <541828EA.3060509@inutech.de> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> <5416F67D.4090602@inutech.de> <541828EA.3060509@inutech.de> Message-ID: It's under "ParaVIewCore/ServerManager/Rendering/" in the ParaVIew source[1] Utkarsh [1] https://github.com/Kitware/ParaView/blob/master/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.h On Tue, Sep 16, 2014 at 8:11 AM, Florian Hoffmann wrote: > Dear Utkarsh, > > thank you very much for your fast reply and the provided example. > I compiled PV4.2RC2 from source and just tried to compile your example. > Nevertheless I receive a compilation error complaining that the file > > vtkSMParaViewPipelineControllerWithRendering.h > > cannot be found. > Where is this file supposed to be residing ? > > Thank you. > > Best regards, > > Florian > > > > Am 15.09.2014 um 17:16 schrieb Utkarsh Ayachit > : > > Attached is an example based on ParaView 4.2-RC1. As it shows, you > cannot directly use VTK objects to create visualization pipelines in > ParaView. While this can surely be done with 4.1 or earlier, I'd > suggest basing off 4.2, if possible since it simplified a lot of this > initialization. > > Utkarsh > > On Mon, Sep 15, 2014 at 10:23 AM, Florian Hoffmann > wrote: > > I would like to automatically add a glyph filter and render the correctly > scaled spheres after the user has opened a file in my custom dock widget. > I created a DockWidget using the example in /examples/Plugins/DockWidget. > When pressing a button a specific file is being opened for the user by the > following calls: > > void on_button_clicked() > { > QString xdmfFile = "C:\\..\\unknown_case.xdmf"; > > QStringList visuFiles; > > visuFiles.append(xdmfFile); > > pqPipelineSource* pqPlinesource = > pqLoadDataReaction::loadData(visuFiles); > > pqPlinesource->updatePipeline(); > > // TODO: > // add spherical glyph for loaded polyData > // scale spherical glyphs by a scalar attribute/property > // render glyphs > > } > > I would like to include that the code automatically adds spherical glyphs > and renders them for the data just loaded. > > I tried the following code but I am not sure if it works > > vtkSMProxy *myProxy = pqPlinesource->getProxy(); > > vtkObjectBase *myObject = myProxy->GetClientSideObject(); > > vtkAlgorithm *myvtkAlgo = vtkAlgorithm::SafeDownCast(myObject); > > vtkGlyph3D *myspheres = vtkGlyph3D::New(); > > myspheres->SetSourceConnection(myvtkAlgo->GetOutputPort()); > > > > In case this is supposed to work, how can I now update the pipeline and > render the spheres using C++ PV core functionality ? (The user should also > see the result in the pipeline browser dock of the GUI). > > In case my approach is totally wrong, what would be the right way of > handling this situation ? > > Thank you. > > Best regards, > > Florian > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > From e0425375 at gmail.com Tue Sep 16 09:24:28 2014 From: e0425375 at gmail.com (Florian Bruckner) Date: Tue, 16 Sep 2014 15:24:28 +0200 Subject: [Paraview] howto move an object depending on actual time In-Reply-To: References: <54181208.3080906@gmail.com> Message-ID: <54183A0C.1010901@gmail.com> hi, thanks alot for the fast reply. DATA_TIME_STEP was the variable that i was looking for. here is my "Programmable Filter Script" that is able to translate an object into a given direction depending on the actual timestep. ### paraview programmable filter script for translation of object depending on timestep from vtk import vtkDataObject from paraview.vtk import dataset_adapter as DA speed = [0.0004, 0.000, 0.000] # define input and output pdi = self.GetInputDataObject(0,0) pdo = self.GetOutputDataObject(0) pdo.CopyAttributes(pdi) # get current time-step step = pdi.GetInformation().Get(vtkDataObject.DATA_TIME_STEP()) # move object old_pts = inputs[0].Points new_pts = old_pts for i in range(3): new_pts[:,i] = old_pts[:,i] + step * speed[i] arr = DA.numpyTovtkDataArray(new_pts, 'newpts') pdo.GetPoints().SetData(arr) greetings FloB On 09/16/2014 02:41 PM, Utkarsh Ayachit wrote: > I'd suggest using "Programmable Filter" instead of "Python > Calculator". Refer to vtkTimeToTexConvertor::RequestData() [1] for how > to access DATA_TIME_STEP value. You can write an equivalent script in > "Script" part for the Programmable Filter to access the time value. > > Utkarsh > > [1] https://github.com/Kitware/ParaView/blob/ad70367102a1d9779435e9949d84a576e68a6ee8/ParaViewCore/VTKExtensions/Default/vtkTimeToTextConvertor.cxx > > > On Tue, Sep 16, 2014 at 6:33 AM, Florian Bruckner wrote: >> hello, >> >> i would like to create an animation of moving objects using the animation >> view. unfortunately the positions of the objects stored within the data file >> are stationary, so i have to manually define the movement anyhow. >> >> is there a simple method to archive this using the animation inspector? (i >> am using paraview 4.1.0) >> >> alternatively i found a method to use the python calculator to translate the >> object. if i could access the actual time it would be possible to define the >> trajectory of the moving particle. is this possible? >> >> thanks >> FloB >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From florian.hoffmann at inutech.de Tue Sep 16 11:26:48 2014 From: florian.hoffmann at inutech.de (Florian Hoffmann) Date: Tue, 16 Sep 2014 17:26:48 +0200 Subject: [Paraview] PV4.1, Custom Dock Widget: How to automatically add a glyph3d filter after loading data ? In-Reply-To: References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> <5416F67D.4090602@inutech.de> <541828EA.3060509@inutech.de> Message-ID: <3F35EDE7-3EF0-417E-8448-7F6CD3F634E9@inutech.de> I have the file there as well but nevertheless during compilation of the Plugin it cannot be found. Do you have any idea why this might be the case ? Thanks. Florian Mit freundlichen Gr??en -- Dr.-Ing. Florian Hoffmann inuTech GmbH Phone : +49-(0)911-323843-22 Fuerther Strasse 212 Fax : +49-(0)911-323843-43 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de Germany Internet : http://www.inutech.de inuTech GmbH Sitz / Registered Office: Nuernberg Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 Gesch?ftsf?hrer / Managing Director: Frank Vogel ***************************************************************** DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! Go to http://www.diffpack.com to read the details ***************************************************************** Am 16.09.2014 um 14:43 schrieb Utkarsh Ayachit : > It's under "ParaVIewCore/ServerManager/Rendering/" in the ParaVIew source[1] > > Utkarsh > > [1] https://github.com/Kitware/ParaView/blob/master/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.h > > On Tue, Sep 16, 2014 at 8:11 AM, Florian Hoffmann > wrote: >> Dear Utkarsh, >> >> thank you very much for your fast reply and the provided example. >> I compiled PV4.2RC2 from source and just tried to compile your example. >> Nevertheless I receive a compilation error complaining that the file >> >> vtkSMParaViewPipelineControllerWithRendering.h >> >> cannot be found. >> Where is this file supposed to be residing ? >> >> Thank you. >> >> Best regards, >> >> Florian >> >> >> >> Am 15.09.2014 um 17:16 schrieb Utkarsh Ayachit >> : >> >> Attached is an example based on ParaView 4.2-RC1. As it shows, you >> cannot directly use VTK objects to create visualization pipelines in >> ParaView. While this can surely be done with 4.1 or earlier, I'd >> suggest basing off 4.2, if possible since it simplified a lot of this >> initialization. >> >> Utkarsh >> >> On Mon, Sep 15, 2014 at 10:23 AM, Florian Hoffmann >> wrote: >> >> I would like to automatically add a glyph filter and render the correctly >> scaled spheres after the user has opened a file in my custom dock widget. >> I created a DockWidget using the example in /examples/Plugins/DockWidget. >> When pressing a button a specific file is being opened for the user by the >> following calls: >> >> void on_button_clicked() >> { >> QString xdmfFile = "C:\\..\\unknown_case.xdmf"; >> >> QStringList visuFiles; >> >> visuFiles.append(xdmfFile); >> >> pqPipelineSource* pqPlinesource = >> pqLoadDataReaction::loadData(visuFiles); >> >> pqPlinesource->updatePipeline(); >> >> // TODO: >> // add spherical glyph for loaded polyData >> // scale spherical glyphs by a scalar attribute/property >> // render glyphs >> >> } >> >> I would like to include that the code automatically adds spherical glyphs >> and renders them for the data just loaded. >> >> I tried the following code but I am not sure if it works >> >> vtkSMProxy *myProxy = pqPlinesource->getProxy(); >> >> vtkObjectBase *myObject = myProxy->GetClientSideObject(); >> >> vtkAlgorithm *myvtkAlgo = vtkAlgorithm::SafeDownCast(myObject); >> >> vtkGlyph3D *myspheres = vtkGlyph3D::New(); >> >> myspheres->SetSourceConnection(myvtkAlgo->GetOutputPort()); >> >> >> >> In case this is supposed to work, how can I now update the pipeline and >> render the spheres using C++ PV core functionality ? (The user should also >> see the result in the pipeline browser dock of the GUI). >> >> In case my approach is totally wrong, what would be the right way of >> handling this situation ? >> >> Thank you. >> >> Best regards, >> >> Florian >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Sep 16 11:55:26 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 16 Sep 2014 11:55:26 -0400 Subject: [Paraview] PV4.1, Custom Dock Widget: How to automatically add a glyph3d filter after loading data ? In-Reply-To: <3F35EDE7-3EF0-417E-8448-7F6CD3F634E9@inutech.de> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> <5416F67D.4090602@inutech.de> <541828EA.3060509@inutech.de> <3F35EDE7-3EF0-417E-8448-7F6CD3F634E9@inutech.de> Message-ID: Not entirely sure why. I just built that same with ParaVIew git/master and it built fine for me. What OS is this? Can you attach CMakeCache.txt from ParaView build as well as the plugin build? Utkarsh On Tue, Sep 16, 2014 at 11:26 AM, Florian Hoffmann wrote: > I have the file there as well but nevertheless during compilation of the > Plugin it cannot be found. > Do you have any idea why this might be the case ? > > > Thanks. > > Florian > > > Mit freundlichen Gr??en > -- > Dr.-Ing. Florian Hoffmann > inuTech GmbH Phone : +49-(0)911-323843-22 > Fuerther Strasse 212 Fax : +49-(0)911-323843-43 > 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de > Germany Internet : http://www.inutech.de > > inuTech GmbH > Sitz / Registered Office: Nuernberg > Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 > Gesch?ftsf?hrer / Managing Director: Frank Vogel > > ***************************************************************** > DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! > > Go to http://www.diffpack.com to read the details > ***************************************************************** > > Am 16.09.2014 um 14:43 schrieb Utkarsh Ayachit > : > > It's under "ParaVIewCore/ServerManager/Rendering/" in the ParaVIew source[1] > > Utkarsh > > [1] > https://github.com/Kitware/ParaView/blob/master/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.h > > On Tue, Sep 16, 2014 at 8:11 AM, Florian Hoffmann > wrote: > > Dear Utkarsh, > > thank you very much for your fast reply and the provided example. > I compiled PV4.2RC2 from source and just tried to compile your example. > Nevertheless I receive a compilation error complaining that the file > > vtkSMParaViewPipelineControllerWithRendering.h > > cannot be found. > Where is this file supposed to be residing ? > > Thank you. > > Best regards, > > Florian > > > > Am 15.09.2014 um 17:16 schrieb Utkarsh Ayachit > : > > Attached is an example based on ParaView 4.2-RC1. As it shows, you > cannot directly use VTK objects to create visualization pipelines in > ParaView. While this can surely be done with 4.1 or earlier, I'd > suggest basing off 4.2, if possible since it simplified a lot of this > initialization. > > Utkarsh > > On Mon, Sep 15, 2014 at 10:23 AM, Florian Hoffmann > wrote: > > I would like to automatically add a glyph filter and render the correctly > scaled spheres after the user has opened a file in my custom dock widget. > I created a DockWidget using the example in /examples/Plugins/DockWidget. > When pressing a button a specific file is being opened for the user by the > following calls: > > void on_button_clicked() > { > QString xdmfFile = "C:\\..\\unknown_case.xdmf"; > > QStringList visuFiles; > > visuFiles.append(xdmfFile); > > pqPipelineSource* pqPlinesource = > pqLoadDataReaction::loadData(visuFiles); > > pqPlinesource->updatePipeline(); > > // TODO: > // add spherical glyph for loaded polyData > // scale spherical glyphs by a scalar attribute/property > // render glyphs > > } > > I would like to include that the code automatically adds spherical glyphs > and renders them for the data just loaded. > > I tried the following code but I am not sure if it works > > vtkSMProxy *myProxy = pqPlinesource->getProxy(); > > vtkObjectBase *myObject = myProxy->GetClientSideObject(); > > vtkAlgorithm *myvtkAlgo = vtkAlgorithm::SafeDownCast(myObject); > > vtkGlyph3D *myspheres = vtkGlyph3D::New(); > > myspheres->SetSourceConnection(myvtkAlgo->GetOutputPort()); > > > > In case this is supposed to work, how can I now update the pipeline and > render the spheres using C++ PV core functionality ? (The user should also > see the result in the pipeline browser dock of the GUI). > > In case my approach is totally wrong, what would be the right way of > handling this situation ? > > Thank you. > > Best regards, > > Florian > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > From simon.m.su.ctr at mail.mil Tue Sep 16 12:22:38 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 16 Sep 2014 16:22:38 +0000 Subject: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON Message-ID: Hello, I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if the file size is still increase 10 fold when saving pvd file to xmf format. However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=/home/simonsm/tools/paraview/paraview-v4.2.0-RC1-75-gf64ee7a_mesa -DPARAVIEW_ENABLE_PYTHON:BOOL=ON -DPARAVIEW_USE_MPI:BOOL=ON -DPARAVIEW_ENABLE_WEB:BOOL=OFF -DModule_vtkIOXdmf3:BOOL=ON ../ParaView-v4.2.0-RC1-75-gf64ee7a I got whole bunch of boost related cmake error with cmake version 3.0.0 and cmake version 2.8.12.2. Some of the error messages are included at the end of this email. I am able to compile RC1-22-g9ca4e44 version ok but without Module_vtkIOXdmf3 set to ON. Is there anything on the boost side that I am not setting it right? I am compiling on RHEL 6.5 with boost-devel-1.41.0-18.el6.x86_64 installed. thanks -simon ================== some of the errors ============= Boost found. CMake Error at /usr/lib64/boost/Boost.cmake:16 (ADD_LIBRARY): add_library cannot create imported target "boost_date_time-static" because another target with the same name already exists. Call Stack (most recent call first): /usr/lib64/boost/BoostConfig.cmake:28 (include) /home/simonsm/tools/cmake/cmake-2.8.12.2/share/cmake-2.8/Modules/FindBoost.cmake:177 (find_package) VTK/ThirdParty/xdmf3/vtkxdmf3/core/CMakeLists.txt:38 (find_package) CMake Error at /usr/lib64/boost/Boost.cmake:19 (ADD_LIBRARY): add_library cannot create imported target "boost_date_time-mt-static" because another target with the same name already exists. Call Stack (most recent call first): /usr/lib64/boost/BoostConfig.cmake:28 (include) /home/simonsm/tools/cmake/cmake-2.8.12.2/share/cmake-2.8/Modules/FindBoost.cmake:177 (find_package) VTK/ThirdParty/xdmf3/vtkxdmf3/core/CMakeLists.txt:38 (find_package) CMake Error at /usr/lib64/boost/Boost.cmake:22 (ADD_LIBRARY): add_library cannot create imported target "boost_date_time-shared" because another target with the same name already exists. Call Stack (most recent call first): /usr/lib64/boost/BoostConfig.cmake:28 (include) /home/simonsm/tools/cmake/cmake-2.8.12.2/share/cmake-2.8/Modules/FindBoost.cmake:177 (find_package) VTK/ThirdParty/xdmf3/vtkxdmf3/core/CMakeLists.txt:38 (find_package) CMake Error at /usr/lib64/boost/Boost.cmake:25 (ADD_LIBRARY): add_library cannot create imported target "boost_date_time-mt-shared" because another target with the same name already exists. Call Stack (most recent call first): /usr/lib64/boost/BoostConfig.cmake:28 (include) /home/simonsm/tools/cmake/cmake-2.8.12.2/share/cmake-2.8/Modules/FindBoost.cmake:177 (find_package) VTK/ThirdParty/xdmf3/vtkxdmf3/core/CMakeLists.txt:38 (find_package) CMake Error at /usr/lib64/boost/Boost.cmake:28 (ADD_LIBRARY): add_library cannot create imported target "boost_date_time-static-debug" because another target with the same name already exists. Call Stack (most recent call first): /usr/lib64/boost/BoostConfig.cmake:28 (include) /home/simonsm/tools/cmake/cmake-2.8.12.2/share/cmake-2.8/Modules/FindBoost.cmake:177 (find_package) VTK/ThirdParty/xdmf3/vtkxdmf3/core/CMakeLists.txt:38 (find_package) CMake Error at /usr/lib64/boost/Boost.cmake:31 (ADD_LIBRARY): add_library cannot create imported target "boost_date_time-mt-static-debug" because another target with the same name already exists. Call Stack (most recent call first): /usr/lib64/boost/BoostConfig.cmake:28 (include) /home/simonsm/tools/cmake/cmake-2.8.12.2/share/cmake-2.8/Modules/FindBoost.cmake:177 (find_package) VTK/ThirdParty/xdmf3/vtkxdmf3/core/CMakeLists.txt:38 (find_package) CMake Error at /usr/lib64/boost/Boost.cmake:34 (ADD_LIBRARY): add_library cannot create imported target "boost_date_time-shared-debug" because another target with the same name already exists. Call Stack (most recent call first): /usr/lib64/boost/BoostConfig.cmake:28 (include) /home/simonsm/tools/cmake/cmake-2.8.12.2/share/cmake-2.8/Modules/FindBoost.cmake:177 (find_package) VTK/ThirdParty/xdmf3/vtkxdmf3/core/CMakeLists.txt:38 (find_package) -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Tue Sep 16 12:39:35 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Tue, 16 Sep 2014 12:39:35 -0400 Subject: [Paraview] Save Stereo Screenshots with Python In-Reply-To: References: Message-ID: I will look into it (or ping the right people for it). Thanks for reporting it. - Aashish On Tue, Sep 16, 2014 at 8:32 AM, Magician wrote: > Hi all, > > > I?d like to export left and right-eye images with Python. > Any ideas? > I?m using ParaView 4.1.0 and 4.2 RC1. > > > Magician > > > On Sep 6, 2014, at 19:25, Magician wrote: > > > Hi all, > > > > > > I want to export screenshots of stereo images with Python. > > The stereo mode is SplitViewportHorizontal (Side-by-Side). > > > > When I export images larger than active views, I get bad results as the > attached image. > > How can I export large stereo screenshots correctly? > > Or I?m planning to export left and right-eye images separately, and > composite them > > with other softwares. > > How can I export left or right-eye images with Python? > > > > > > Magician > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Sep 16 14:55:53 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 16 Sep 2014 14:55:53 -0400 Subject: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON In-Reply-To: References: Message-ID: <20140916185553.GA32690@megas.kitwarein.com> On Tue, Sep 16, 2014 at 16:22:38 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if the file > size is still increase 10 fold when saving pvd file to xmf format. > > However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with > -DModule_vtkIOXdmf3:BOOL=ON > > cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=/home/simonsm/tools/ > paraview/paraview-v4.2.0-RC1-75-gf64ee7a_mesa -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > -DPARAVIEW_USE_MPI:BOOL=ON -DPARAVIEW_ENABLE_WEB:BOOL=OFF > -DModule_vtkIOXdmf3:BOOL=ON ../ParaView-v4.2.0-RC1-75-gf64ee7a > > I got whole bunch of boost related cmake error with cmake version 3.0.0 and > cmake version 2.8.12.2. Some of the error messages are included at the end of > this email. > > I am able to compile RC1-22-g9ca4e44 version ok but without Module_vtkIOXdmf3 > set to ON. Is there anything on the boost side that I am not setting it right? > I am compiling on RHEL 6.5 with boost-devel-1.41.0-18.el6.x86_64 installed. Looks to be a CMake-ified boost. It worked here on Fedora with 1.54.0 (which I don't believe is built using CMake anymore). It seems that it doesn't support multiple find_package calls. Try setting Boost_NO_BOOST_CMAKE to ON to force the FindBoost.cmake logic to kick in. --Ben From kevin.d.lau at gmail.com Tue Sep 16 19:11:50 2014 From: kevin.d.lau at gmail.com (Kevin Lau) Date: Tue, 16 Sep 2014 19:11:50 -0400 Subject: [Paraview] Python Scripting - Slicing Data Message-ID: Dear all, I'm trying to use a Python script to slice a 3D model in multiple locations and interrogate the values at these slices. Is it possible to apply the slice with a plane? I.e. intersect the model with a pre-defined plane? I can load and view my data and a plane I've defined (see below), but I can't find how to slice/intersect them Many thanks for your help, Kevin PYTHON SCRIPT: from paraview.simple import * # read data data = PhastaReader(FileName="view.pht") Show(data) Render() # define plane plane1 = Plane() plane1.Origin = [0, 0, 0] plane1.Point1 = [1, 0, 0] plane1.Point2 = [0, 1, 0] Show(plane1) Render() # how to slice with the plane? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Wed Sep 17 03:12:05 2014 From: jfavre at cscs.ch (Favre Jean) Date: Wed, 17 Sep 2014 07:12:05 +0000 Subject: [Paraview] Python Scripting - Slicing Data In-Reply-To: References: Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6828139BC4@MBX11.d.ethz.ch> I'd recommend you use the Trace tools to see how to write the python code. Get your data, apply the slice filter, and see how its arguments are set. you'll end up with something like: data = PhastaReader(FileName="view.pht") Show(data) slice = Slice(Input=data) slice.SliceType = 'Plane' slice.SliceOffsetValues = [0.0] slice.SliceType.Origin = [0., 0., 0.] slice.SliceType.Normal = [0.0, 1.0, 0.0] Show() Jean/CSCS From jfavre at cscs.ch Wed Sep 17 05:17:15 2014 From: jfavre at cscs.ch (Favre Jean) Date: Wed, 17 Sep 2014 09:17:15 +0000 Subject: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON In-Reply-To: <20140916185553.GA32690@megas.kitwarein.com> References: , <20140916185553.GA32690@megas.kitwarein.com> Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6828139CCE@MBX11.d.ethz.ch> thanks for the tip. I got the new reader compiled, but I am disappointed to see that it crashes immediately on my existing data (which can be read in parallel, with the old xdmf2 reader). ERROR: In /apps/pilatus/ParaView/src/ParaView/VTK/Common/Core/vtkDataArrayTemplate.txx, line 148 vtkFloatArray (0x231e760): Unable to allocate 2790483579 elements of size 4 bytes. I am usually reading with 64 MPI tasks and the xdmf2 reader works really well in parallel. My grid size is 313x897x3313 and I am reading a single vector field. The error message above indicates that the partitioning of the grid is not happening and that each MPI tasks is asking for the whole grid. Determined Source Version : 4.2.0-RC1-75-gf64ee7a ----------------- Jean /CSCS From florian.hoffmann at inutech.de Wed Sep 17 05:22:01 2014 From: florian.hoffmann at inutech.de (Florian Hoffmann) Date: Wed, 17 Sep 2014 11:22:01 +0200 Subject: [Paraview] PV4.1, Custom Dock Widget: How to automatically add a glyph3d filter after loading data ? In-Reply-To: References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> <5416F67D.4090602@inutech.de> <541828EA.3060509@inutech.de> <3F35EDE7-3EF0-417E-8448-7F6CD3F634E9@inutech.de> Message-ID: <541952B9.4040505@inutech.de> Dear Utkarsh, thanks a lot. I made a small mistake during cmake configuration. It works fine. Question: Where can I find the "keywords" for vtkSMPropertyHelper(...) For example you used: vtkSMPropertyHelper(cylinder,"Resolution").Set(18); I would like to setup the glyph's settings in a similar fashion. For example: // your code ... //Createandinitializetheglyphfilter vtkSMSourceProxy* glyph = vtkSMSourceProxy::SafeDownCast(pxm->NewProxy("filters", "Glyph")); controller->PreInitializeProxy(glyph); vtkSMPropertyHelper(glyph,"Input").Set(cylinder); vtkSMPropertyHelper(glyph,"Source").Set(getSphereSource(glyph)); // what I would like to add to the glyph's settings vtkSMPropertyHelper(glyph,"Scale Factor").Set(1.0); vtkSMPropertyHelper(glyph,"Scale Mode").Set(scalar); vtkSMPropertyHelper(glyph,"Masking").Set(All_points); ... cylinder->UpdateVTKObjects(); ... For example I tried "ScaleFactor" and "Scale Factor" but they do not seem to work. what are the data types for the .Set() functions ? For example in the case of Masking ? Where can I find the C++ masking options and its data type to be used with vtkSMPropertyHelper ? Or do you suggest another way of accessing these properties ? Thank you very much. Florian Am 16.09.2014 um 17:55 schrieb Utkarsh Ayachit: > Not entirely sure why. I just built that same with ParaVIew git/master > and it built fine for me. What OS is this? Can you attach > CMakeCache.txt from ParaView build as well as the plugin build? > > Utkarsh > > On Tue, Sep 16, 2014 at 11:26 AM, Florian Hoffmann > wrote: >> I have the file there as well but nevertheless during compilation of the >> Plugin it cannot be found. >> Do you have any idea why this might be the case ? >> >> >> Thanks. >> >> Florian >> >> >> Mit freundlichen Gr??en >> -- >> Dr.-Ing. Florian Hoffmann >> inuTech GmbH Phone : +49-(0)911-323843-22 >> Fuerther Strasse 212 Fax : +49-(0)911-323843-43 >> 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de >> Germany Internet : http://www.inutech.de >> >> inuTech GmbH >> Sitz / Registered Office: Nuernberg >> Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 >> Gesch?ftsf?hrer / Managing Director: Frank Vogel >> >> ***************************************************************** >> DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! >> >> Go to http://www.diffpack.com to read the details >> ***************************************************************** >> >> Am 16.09.2014 um 14:43 schrieb Utkarsh Ayachit >> : >> >> It's under "ParaVIewCore/ServerManager/Rendering/" in the ParaVIew source[1] >> >> Utkarsh >> >> [1] >> https://github.com/Kitware/ParaView/blob/master/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.h >> >> On Tue, Sep 16, 2014 at 8:11 AM, Florian Hoffmann >> wrote: >> >> Dear Utkarsh, >> >> thank you very much for your fast reply and the provided example. >> I compiled PV4.2RC2 from source and just tried to compile your example. >> Nevertheless I receive a compilation error complaining that the file >> >> vtkSMParaViewPipelineControllerWithRendering.h >> >> cannot be found. >> Where is this file supposed to be residing ? >> >> Thank you. >> >> Best regards, >> >> Florian >> >> >> >> Am 15.09.2014 um 17:16 schrieb Utkarsh Ayachit >> : >> >> Attached is an example based on ParaView 4.2-RC1. As it shows, you >> cannot directly use VTK objects to create visualization pipelines in >> ParaView. While this can surely be done with 4.1 or earlier, I'd >> suggest basing off 4.2, if possible since it simplified a lot of this >> initialization. >> >> Utkarsh >> >> On Mon, Sep 15, 2014 at 10:23 AM, Florian Hoffmann >> wrote: >> >> I would like to automatically add a glyph filter and render the correctly >> scaled spheres after the user has opened a file in my custom dock widget. >> I created a DockWidget using the example in /examples/Plugins/DockWidget. >> When pressing a button a specific file is being opened for the user by the >> following calls: >> >> void on_button_clicked() >> { >> QString xdmfFile = "C:\\..\\unknown_case.xdmf"; >> >> QStringList visuFiles; >> >> visuFiles.append(xdmfFile); >> >> pqPipelineSource* pqPlinesource = >> pqLoadDataReaction::loadData(visuFiles); >> >> pqPlinesource->updatePipeline(); >> >> // TODO: >> // add spherical glyph for loaded polyData >> // scale spherical glyphs by a scalar attribute/property >> // render glyphs >> >> } >> >> I would like to include that the code automatically adds spherical glyphs >> and renders them for the data just loaded. >> >> I tried the following code but I am not sure if it works >> >> vtkSMProxy *myProxy = pqPlinesource->getProxy(); >> >> vtkObjectBase *myObject = myProxy->GetClientSideObject(); >> >> vtkAlgorithm *myvtkAlgo = vtkAlgorithm::SafeDownCast(myObject); >> >> vtkGlyph3D *myspheres = vtkGlyph3D::New(); >> >> myspheres->SetSourceConnection(myvtkAlgo->GetOutputPort()); >> >> >> >> In case this is supposed to work, how can I now update the pipeline and >> render the spheres using C++ PV core functionality ? (The user should also >> see the result in the pipeline browser dock of the GUI). >> >> In case my approach is totally wrong, what would be the right way of >> handling this situation ? >> >> Thank you. >> >> Best regards, >> >> Florian >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> >> -- Mit freundlichen Gr??en -- Dr.-Ing. Florian Hoffmann inuTech GmbH Phone : +49-(0)911-323843-22 Fuerther Strasse 212 Fax : +49-(0)911-323843-43 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de Germany Internet : http://www.inutech.de inuTech GmbH Sitz / Registered Office: Nuernberg Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 Gesch?ftsf?hrer / Managing Director: Frank Vogel ***************************************************************** DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! Go to http://www.diffpack.com to read the details ***************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From ronald.fowler at stfc.ac.uk Wed Sep 17 06:29:59 2014 From: ronald.fowler at stfc.ac.uk (ronald.fowler at stfc.ac.uk) Date: Wed, 17 Sep 2014 10:29:59 +0000 Subject: [Paraview] Client server volume rendering problem in 4.1 and 4.2RC1 Message-ID: <398242C76E3D3740BA94E23089B34E2C85F4B969@EXCHMBX03.fed.cclrc.ac.uk> Hi, A post by Robert Atwood in June mentioned a problem with client server volume visualisation in PV4.1, and I have also seen problems in this case both on Linux and Windows systems. Fixes (0014794 and 0014792) have been added to 4.2RC1 which allow correct rendering of the wavelet test case. I tried this on a Windows 7 system and works ok for 4.2RC1, but not for 4.1. However I think that the remote/local render problem for volume visualisation is really very confusing and needs to be improved. After spending more time then I should with it, I conclude that (again on windows 7 64 bit): (1) Volume rendering only works if done on the remote server, not the local on (as acknowledged in a tracker ticket, though I have not seen it documented elsewhere). (2) For 4.1 to do this correctly for just a volume image this seems to need settings of "remote render threshold" ticked and "0 Mbytes" selected. It will work for cases when >0 Mbytes is selected, if there is also another object displayed (e.g. an isosurface). This led me to think an additional surface was always needed to see the volume, which is not the case. (3) For 4.2RC1 the interface to settings has changed and there is no longer a tick box. Instead the slider for remote local render size has a much greater range. This should be set to zero to force remote render for volume views. It also works for non-zero values less than the size of the volume data, e.g. 4Mbytes for a 256^3 volume. This setting did not seem work for 4.1 to force a remote rendering of just volume data. I think it would be useful if at least the tool tips in the settings panel suggested how to make client server volume rendering work. It would also be useful if a warning message were displayed when trying (and failing) to do a local volume render in client server mode. Another problem that has been observed is that the "smart" option for volume rendering is not necessarily that smart when the server nodes have no GPUs and the client does. This was on a Linux 64 bit system with 4.1. Thanks, Ron fowler -- Scanned by iCritical. -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Sep 17 08:29:33 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 17 Sep 2014 08:29:33 -0400 Subject: [Paraview] PV4.1, Custom Dock Widget: How to automatically add a glyph3d filter after loading data ? In-Reply-To: <541952B9.4040505@inutech.de> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> <5416F67D.4090602@inutech.de> <541828EA.3060509@inutech.de> <3F35EDE7-3EF0-417E-8448-7F6CD3F634E9@inutech.de> <541952B9.4040505@inutech.de> Message-ID: Click on the "?" button on the ParaView UI with the filter active. That'll take you a page that will list all such "properties" available on the filter. Additionally, you can look at these xml files[1]. Locate the proxy using the group/name and then you'll have the details for properties on it. Utkarsh [1] https://github.com/Kitware/ParaView/tree/master/ParaViewCore/ServerManager/SMApplication/Resources On Wed, Sep 17, 2014 at 5:22 AM, Florian Hoffmann wrote: > Dear Utkarsh, > > thanks a lot. I made a small mistake during cmake configuration. It works > fine. > > Question: Where can I find the "keywords" for > > vtkSMPropertyHelper(...) > > For example you used: > > vtkSMPropertyHelper(cylinder, "Resolution").Set(18); > > > I would like to setup the glyph's settings in a similar fashion. For > example: > > // your code > ... > > // Create and initialize the glyph filter > > vtkSMSourceProxy* glyph = > vtkSMSourceProxy::SafeDownCast(pxm->NewProxy("filters", "Glyph")); > > controller->PreInitializeProxy(glyph); > vtkSMPropertyHelper(glyph, "Input").Set(cylinder); > vtkSMPropertyHelper(glyph, "Source").Set(getSphereSource(glyph)); > > > // what I would like to add to the glyph's settings > vtkSMPropertyHelper(glyph, "Scale Factor").Set(1.0); > vtkSMPropertyHelper(glyph, "Scale Mode").Set(scalar); > vtkSMPropertyHelper(glyph, "Masking").Set(All_points); > ... > > cylinder->UpdateVTKObjects(); > ... > > > For example I tried "ScaleFactor" and "Scale Factor" but they do not seem to > work. > > what are the data types for the .Set() functions ? For example in the case > of Masking ? Where can I find the C++ masking options and its data type to > be used with vtkSMPropertyHelper ? Or do you suggest another way of > accessing these properties ? > > Thank you very much. > > Florian > > > > Am 16.09.2014 um 17:55 schrieb Utkarsh Ayachit: > > Not entirely sure why. I just built that same with ParaVIew git/master > and it built fine for me. What OS is this? Can you attach > CMakeCache.txt from ParaView build as well as the plugin build? > > Utkarsh > > On Tue, Sep 16, 2014 at 11:26 AM, Florian Hoffmann > wrote: > > I have the file there as well but nevertheless during compilation of the > Plugin it cannot be found. > Do you have any idea why this might be the case ? > > > Thanks. > > Florian > > > Mit freundlichen Gr??en > -- > Dr.-Ing. Florian Hoffmann > inuTech GmbH Phone : +49-(0)911-323843-22 > Fuerther Strasse 212 Fax : +49-(0)911-323843-43 > 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de > Germany Internet : http://www.inutech.de > > inuTech GmbH > Sitz / Registered Office: Nuernberg > Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 > Gesch?ftsf?hrer / Managing Director: Frank Vogel > > ***************************************************************** > DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! > > Go to http://www.diffpack.com to read the details > ***************************************************************** > > Am 16.09.2014 um 14:43 schrieb Utkarsh Ayachit > : > > It's under "ParaVIewCore/ServerManager/Rendering/" in the ParaVIew source[1] > > Utkarsh > > [1] > https://github.com/Kitware/ParaView/blob/master/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.h > > On Tue, Sep 16, 2014 at 8:11 AM, Florian Hoffmann > wrote: > > Dear Utkarsh, > > thank you very much for your fast reply and the provided example. > I compiled PV4.2RC2 from source and just tried to compile your example. > Nevertheless I receive a compilation error complaining that the file > > vtkSMParaViewPipelineControllerWithRendering.h > > cannot be found. > Where is this file supposed to be residing ? > > Thank you. > > Best regards, > > Florian > > > > Am 15.09.2014 um 17:16 schrieb Utkarsh Ayachit > : > > Attached is an example based on ParaView 4.2-RC1. As it shows, you > cannot directly use VTK objects to create visualization pipelines in > ParaView. While this can surely be done with 4.1 or earlier, I'd > suggest basing off 4.2, if possible since it simplified a lot of this > initialization. > > Utkarsh > > On Mon, Sep 15, 2014 at 10:23 AM, Florian Hoffmann > wrote: > > I would like to automatically add a glyph filter and render the correctly > scaled spheres after the user has opened a file in my custom dock widget. > I created a DockWidget using the example in /examples/Plugins/DockWidget. > When pressing a button a specific file is being opened for the user by the > following calls: > > void on_button_clicked() > { > QString xdmfFile = "C:\\..\\unknown_case.xdmf"; > > QStringList visuFiles; > > visuFiles.append(xdmfFile); > > pqPipelineSource* pqPlinesource = > pqLoadDataReaction::loadData(visuFiles); > > pqPlinesource->updatePipeline(); > > // TODO: > // add spherical glyph for loaded polyData > // scale spherical glyphs by a scalar attribute/property > // render glyphs > > } > > I would like to include that the code automatically adds spherical glyphs > and renders them for the data just loaded. > > I tried the following code but I am not sure if it works > > vtkSMProxy *myProxy = pqPlinesource->getProxy(); > > vtkObjectBase *myObject = myProxy->GetClientSideObject(); > > vtkAlgorithm *myvtkAlgo = vtkAlgorithm::SafeDownCast(myObject); > > vtkGlyph3D *myspheres = vtkGlyph3D::New(); > > myspheres->SetSourceConnection(myvtkAlgo->GetOutputPort()); > > > > In case this is supposed to work, how can I now update the pipeline and > render the spheres using C++ PV core functionality ? (The user should also > see the result in the pipeline browser dock of the GUI). > > In case my approach is totally wrong, what would be the right way of > handling this situation ? > > Thank you. > > Best regards, > > Florian > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > -- > Mit freundlichen Gr??en > -- > Dr.-Ing. Florian Hoffmann > inuTech GmbH Phone : +49-(0)911-323843-22 > Fuerther Strasse 212 Fax : +49-(0)911-323843-43 > 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de > Germany Internet : http://www.inutech.de > > inuTech GmbH > Sitz / Registered Office: Nuernberg > Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 > Gesch?ftsf?hrer / Managing Director: Frank Vogel > > ***************************************************************** > DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! > > Go to http://www.diffpack.com to read the details > ***************************************************************** From florian.hoffmann at inutech.de Wed Sep 17 09:51:20 2014 From: florian.hoffmann at inutech.de (Florian Hoffmann) Date: Wed, 17 Sep 2014 15:51:20 +0200 Subject: [Paraview] PV4.1, Custom Dock Widget: How to automatically add a glyph3d filter after loading data ? In-Reply-To: References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> <5416F67D.4090602@inutech.de> <541828EA.3060509@inutech.de> <3F35EDE7-3EF0-417E-8448-7F6CD3F634E9@inutech.de> <541952B9.4040505@inutech.de> Message-ID: <541991D8.6020106@inutech.de> Dear Utkarsh, Thanks. That did help. So I am having now: ... vtkSMPropertyHelper(glyph, "Source").Set(getSphereSource(glyph)); // "scalar" = 0 // "vector" = 1 // "vector_comp" = 2 // "off" = 3 vtkSMPropertyHelper(glyph, "ScaleMode",true).Set(0); vtkSMPropertyHelper(glyph, "ScaleFactor",true).Set(1.0); // 0 or 1: 1=using vector property for orientation vtkSMPropertyHelper(glyph, "Orient",true).Set(0); // "All Points" = 0 vtkSMPropertyHelper(glyph, "GlyphMode",true).Set(0); All of the above work, except the ScaleFactor setter. The scale factor is odd anyway: in the GUI a value of 1.8 appears by default (even though according to the doc it should be 1.0) . Any clue ? Last question: How do I gain access to the GlyphSource(=SphereSource) object in order to use the .SetRadius(1.0) function on it ? It is not clear to me whether it needs to be accessed through a vtkSMPropertyHelper or through a proxy ? Thanks Florian Am 17.09.2014 um 14:29 schrieb Utkarsh Ayachit: > Click on the "?" button on the ParaView UI with the filter active. > That'll take you a page that will list all such "properties" available > on the filter. Additionally, you can look at these xml files[1]. > Locate the proxy using the group/name and then you'll have the details > for properties on it. > > Utkarsh > > [1] https://github.com/Kitware/ParaView/tree/master/ParaViewCore/ServerManager/SMApplication/Resources > > > On Wed, Sep 17, 2014 at 5:22 AM, Florian Hoffmann > wrote: >> Dear Utkarsh, >> >> thanks a lot. I made a small mistake during cmake configuration. It works >> fine. >> >> Question: Where can I find the "keywords" for >> >> vtkSMPropertyHelper(...) >> >> For example you used: >> >> vtkSMPropertyHelper(cylinder, "Resolution").Set(18); >> >> >> I would like to setup the glyph's settings in a similar fashion. For >> example: >> >> // your code >> ... >> >> // Create and initialize the glyph filter >> >> vtkSMSourceProxy* glyph = >> vtkSMSourceProxy::SafeDownCast(pxm->NewProxy("filters", "Glyph")); >> >> controller->PreInitializeProxy(glyph); >> vtkSMPropertyHelper(glyph, "Input").Set(cylinder); >> vtkSMPropertyHelper(glyph, "Source").Set(getSphereSource(glyph)); >> >> >> // what I would like to add to the glyph's settings >> vtkSMPropertyHelper(glyph, "Scale Factor").Set(1.0); >> vtkSMPropertyHelper(glyph, "Scale Mode").Set(scalar); >> vtkSMPropertyHelper(glyph, "Masking").Set(All_points); >> ... >> >> cylinder->UpdateVTKObjects(); >> ... >> >> >> For example I tried "ScaleFactor" and "Scale Factor" but they do not seem to >> work. >> >> what are the data types for the .Set() functions ? For example in the case >> of Masking ? Where can I find the C++ masking options and its data type to >> be used with vtkSMPropertyHelper ? Or do you suggest another way of >> accessing these properties ? >> >> Thank you very much. >> >> Florian >> >> >> >> Am 16.09.2014 um 17:55 schrieb Utkarsh Ayachit: >> >> Not entirely sure why. I just built that same with ParaVIew git/master >> and it built fine for me. What OS is this? Can you attach >> CMakeCache.txt from ParaView build as well as the plugin build? >> >> Utkarsh >> >> On Tue, Sep 16, 2014 at 11:26 AM, Florian Hoffmann >> wrote: >> >> I have the file there as well but nevertheless during compilation of the >> Plugin it cannot be found. >> Do you have any idea why this might be the case ? >> >> >> Thanks. >> >> Florian >> >> >> Mit freundlichen Gr??en >> -- >> Dr.-Ing. Florian Hoffmann >> inuTech GmbH Phone : +49-(0)911-323843-22 >> Fuerther Strasse 212 Fax : +49-(0)911-323843-43 >> 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de >> Germany Internet : http://www.inutech.de >> >> inuTech GmbH >> Sitz / Registered Office: Nuernberg >> Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 >> Gesch?ftsf?hrer / Managing Director: Frank Vogel >> >> ***************************************************************** >> DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! >> >> Go to http://www.diffpack.com to read the details >> ***************************************************************** >> >> Am 16.09.2014 um 14:43 schrieb Utkarsh Ayachit >> : >> >> It's under "ParaVIewCore/ServerManager/Rendering/" in the ParaVIew source[1] >> >> Utkarsh >> >> [1] >> https://github.com/Kitware/ParaView/blob/master/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.h >> >> On Tue, Sep 16, 2014 at 8:11 AM, Florian Hoffmann >> wrote: >> >> Dear Utkarsh, >> >> thank you very much for your fast reply and the provided example. >> I compiled PV4.2RC2 from source and just tried to compile your example. >> Nevertheless I receive a compilation error complaining that the file >> >> vtkSMParaViewPipelineControllerWithRendering.h >> >> cannot be found. >> Where is this file supposed to be residing ? >> >> Thank you. >> >> Best regards, >> >> Florian >> >> >> >> Am 15.09.2014 um 17:16 schrieb Utkarsh Ayachit >> : >> >> Attached is an example based on ParaView 4.2-RC1. As it shows, you >> cannot directly use VTK objects to create visualization pipelines in >> ParaView. While this can surely be done with 4.1 or earlier, I'd >> suggest basing off 4.2, if possible since it simplified a lot of this >> initialization. >> >> Utkarsh >> >> On Mon, Sep 15, 2014 at 10:23 AM, Florian Hoffmann >> wrote: >> >> I would like to automatically add a glyph filter and render the correctly >> scaled spheres after the user has opened a file in my custom dock widget. >> I created a DockWidget using the example in /examples/Plugins/DockWidget. >> When pressing a button a specific file is being opened for the user by the >> following calls: >> >> void on_button_clicked() >> { >> QString xdmfFile = "C:\\..\\unknown_case.xdmf"; >> >> QStringList visuFiles; >> >> visuFiles.append(xdmfFile); >> >> pqPipelineSource* pqPlinesource = >> pqLoadDataReaction::loadData(visuFiles); >> >> pqPlinesource->updatePipeline(); >> >> // TODO: >> // add spherical glyph for loaded polyData >> // scale spherical glyphs by a scalar attribute/property >> // render glyphs >> >> } >> >> I would like to include that the code automatically adds spherical glyphs >> and renders them for the data just loaded. >> >> I tried the following code but I am not sure if it works >> >> vtkSMProxy *myProxy = pqPlinesource->getProxy(); >> >> vtkObjectBase *myObject = myProxy->GetClientSideObject(); >> >> vtkAlgorithm *myvtkAlgo = vtkAlgorithm::SafeDownCast(myObject); >> >> vtkGlyph3D *myspheres = vtkGlyph3D::New(); >> >> myspheres->SetSourceConnection(myvtkAlgo->GetOutputPort()); >> >> >> >> In case this is supposed to work, how can I now update the pipeline and >> render the spheres using C++ PV core functionality ? (The user should also >> see the result in the pipeline browser dock of the GUI). >> >> In case my approach is totally wrong, what would be the right way of >> handling this situation ? >> >> Thank you. >> >> Best regards, >> >> Florian >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> >> >> >> -- >> Mit freundlichen Gr??en >> -- >> Dr.-Ing. Florian Hoffmann >> inuTech GmbH Phone : +49-(0)911-323843-22 >> Fuerther Strasse 212 Fax : +49-(0)911-323843-43 >> 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de >> Germany Internet : http://www.inutech.de >> >> inuTech GmbH >> Sitz / Registered Office: Nuernberg >> Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 >> Gesch?ftsf?hrer / Managing Director: Frank Vogel >> >> ***************************************************************** >> DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! >> >> Go to http://www.diffpack.com to read the details >> ***************************************************************** -- Mit freundlichen Gr??en -- Dr.-Ing. Florian Hoffmann inuTech GmbH Phone : +49-(0)911-323843-22 Fuerther Strasse 212 Fax : +49-(0)911-323843-43 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de Germany Internet : http://www.inutech.de inuTech GmbH Sitz / Registered Office: Nuernberg Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 Gesch?ftsf?hrer / Managing Director: Frank Vogel ***************************************************************** DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! Go to http://www.diffpack.com to read the details ***************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Sep 17 10:09:21 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 17 Sep 2014 10:09:21 -0400 Subject: [Paraview] Client server volume rendering problem in 4.1 and 4.2RC1 In-Reply-To: <398242C76E3D3740BA94E23089B34E2C85F4B969@EXCHMBX03.fed.cclrc.ac.uk> References: <398242C76E3D3740BA94E23089B34E2C85F4B969@EXCHMBX03.fed.cclrc.ac.uk> Message-ID: Ron, Those are good observations. I has been on my todo list to clean up the remote-local rendering issue. I want ParaView to automatically switch to remote rendering, if possible when volume rendering. I'll see what I can do for that. The volume rendering code is currently being revamped. I'd expect better "smart" rendering in near future. Utkarsh On Wed, Sep 17, 2014 at 6:29 AM, wrote: > Hi, > > A post by Robert Atwood in June mentioned a problem with client server > volume visualisation in PV4.1, and I have also seen problems in this case > both on Linux and Windows systems. > > > > Fixes (0014794 and 0014792) have been added to 4.2RC1 which allow correct > rendering of the wavelet test case. I tried this on a Windows 7 system and > works ok for 4.2RC1, but not for 4.1. > > > > However I think that the remote/local render problem for volume > visualisation is really very confusing and needs to be improved. After > spending more time then I should with it, I conclude that (again on windows > 7 64 bit): > > (1) Volume rendering only works if done on the remote server, not the > local on (as acknowledged in a tracker ticket, though I have not seen it > documented elsewhere). > > (2) For 4.1 to do this correctly for just a volume image this seems to > need settings of ?remote render threshold? ticked and ?0 Mbytes? selected. > It will work for cases when >0 Mbytes is selected, if there is also another > object displayed (e.g. an isosurface). This led me to think an additional > surface was always needed to see the volume, which is not the case. > > (3) For 4.2RC1 the interface to settings has changed and there is no > longer a tick box. Instead the slider for remote local render size has a > much greater range. This should be set to zero to force remote render for > volume views. It also works for non-zero values less than the size of the > volume data, e.g. 4Mbytes for a 256^3 volume. This setting did not seem work > for 4.1 to force a remote rendering of just volume data. > > > > I think it would be useful if at least the tool tips in the settings panel > suggested how to make client server volume rendering work. It would also be > useful if a warning message were displayed when trying (and failing) to do a > local volume render in client server mode. > > > > Another problem that has been observed is that the ?smart? option for volume > rendering is not necessarily that smart when the server nodes have no GPUs > and the client does. This was on a Linux 64 bit system with 4.1. > > > > Thanks, > > Ron fowler > > > > > > > > > > > > > > > > > -- > Scanned by iCritical. > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Sep 17 10:19:00 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 17 Sep 2014 10:19:00 -0400 Subject: [Paraview] PV4.1, Custom Dock Widget: How to automatically add a glyph3d filter after loading data ? In-Reply-To: <541991D8.6020106@inutech.de> References: <4B5B2149-0BE4-4F65-A1CD-E76C7C99E293@llnl.gov> <92654e5a023748898645f8a681933518@ES05AMSNLNT.srn.sandia.gov> <24DFC542-CF64-4395-9D5B-5866B5D4D158@llnl.gov> <63287f036d05457a8fe6ea5127f943fa@ES05AMSNLNT.srn.sandia.gov> <3a6f9fc4a71746eb87a6c247a8a81817@ES05AMSNLNT.srn.sandia.gov> <5885FA26-DDA6-4F4B-A0DF-1195627063D6@llnl.gov> <5416F67D.4090602@inutech.de> <541828EA.3060509@inutech.de> <3F35EDE7-3EF0-417E-8448-7F6CD3F634E9@inutech.de> <541952B9.4040505@inutech.de> <541991D8.6020106@inutech.de> Message-ID: > All of the above work, except the ScaleFactor setter. The scale factor is > odd anyway: in the GUI a value of 1.8 appears by default (even though > according to the doc it should be 1.0) . Any clue ? Certain properties update their default values based on runtime data values. This is done by what ParaView calls Domains. ScaleFactor is one such property. To force the ScaleFactor to 1, do the change after the "PostInialize" call. > Last question: How do I gain access to the GlyphSource(=SphereSource) object > in order to use the .SetRadius(1.0) function on it ? > It is not clear to me whether it needs to be accessed through a > vtkSMPropertyHelper or through a proxy ? vtkSMPropertyHelper(glyph, "Source").Set(getSphereSource(glyph)); vtkSMProxy* sphere = vtkSMPropertyHelper(glyph, "Source").GetAsProxy(); vtkSMPropertyHelper(sphere, "Radius").Set(1.0); sphere->UpdateVTKObjects(); Utkarsh From dave.demarle at kitware.com Wed Sep 17 11:56:50 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 17 Sep 2014 09:56:50 -0600 Subject: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON In-Reply-To: <20140916185553.GA32690@megas.kitwarein.com> References: <20140916185553.GA32690@megas.kitwarein.com> Message-ID: I had similar config problems in the DoD HPC machines I tested on. The root cause was that the system boost was CMakefied and find boost didn't like it but insisted on using it. To get around it I downloaded my own boost (no need to compile it) and made the my PV build use it by: In cmakecache.txt set Boost_NO_SYSTEM_PATHS:BOOL=ON set Boost_NO_BOOST_CMAKE:BOOL=ON Then it will ask for an respect your choice of boost headers to use. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Sep 16, 2014 at 12:55 PM, Ben Boeckel wrote: > On Tue, Sep 16, 2014 at 16:22:38 +0000, Su, Simon M CTR USARMY ARL (US) > wrote: > > I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if > the file > > size is still increase 10 fold when saving pvd file to xmf format. > > > > However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with > > -DModule_vtkIOXdmf3:BOOL=ON > > > > cmake -DCMAKE_BUILD_TYPE=release > -DCMAKE_INSTALL_PREFIX=/home/simonsm/tools/ > > paraview/paraview-v4.2.0-RC1-75-gf64ee7a_mesa > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > > -DPARAVIEW_USE_MPI:BOOL=ON -DPARAVIEW_ENABLE_WEB:BOOL=OFF > > -DModule_vtkIOXdmf3:BOOL=ON ../ParaView-v4.2.0-RC1-75-gf64ee7a > > > > I got whole bunch of boost related cmake error with cmake version 3.0.0 > and > > cmake version 2.8.12.2. Some of the error messages are included at the > end of > > this email. > > > > I am able to compile RC1-22-g9ca4e44 version ok but without > Module_vtkIOXdmf3 > > set to ON. Is there anything on the boost side that I am not setting it > right? > > I am compiling on RHEL 6.5 with boost-devel-1.41.0-18.el6.x86_64 > installed. > > Looks to be a CMake-ified boost. It worked here on Fedora with 1.54.0 > (which I don't believe is built using CMake anymore). It seems that it > doesn't support multiple find_package calls. Try setting > Boost_NO_BOOST_CMAKE to ON to force the FindBoost.cmake logic to kick > in. > > --Ben > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Sep 17 12:00:07 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 17 Sep 2014 10:00:07 -0600 Subject: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F6828139CCE@MBX11.d.ethz.ch> References: <20140916185553.GA32690@megas.kitwarein.com> <0EB9B6375711A04B820E6B6F5CCA9F6828139CCE@MBX11.d.ethz.ch> Message-ID: There are some annoying and minor differences in the XDMF xml format in the new and old versions. For example case sensitivity and changes in treatment of default values. My first intuition is that these are the cause. Jean if you can provide me with a minimal example that demonstrates the problem, I can take a deeper look. thanks, David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Sep 17, 2014 at 3:17 AM, Favre Jean wrote: > > thanks for the tip. I got the new reader compiled, but I am disappointed > to see that it crashes immediately on my existing data (which can be read > in parallel, with the old xdmf2 reader). > > ERROR: In > /apps/pilatus/ParaView/src/ParaView/VTK/Common/Core/vtkDataArrayTemplate.txx, > line 148 > vtkFloatArray (0x231e760): Unable to allocate 2790483579 elements of size > 4 bytes. > > I am usually reading with 64 MPI tasks and the xdmf2 reader works really > well in parallel. > My grid size is 313x897x3313 and I am reading a single vector field. The > error message above indicates that the partitioning of the grid is not > happening and that each MPI tasks is asking for the whole grid. > > Determined Source Version : 4.2.0-RC1-75-gf64ee7a > ----------------- > Jean /CSCS > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Wed Sep 17 12:16:30 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 17 Sep 2014 16:16:30 +0000 Subject: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON In-Reply-To: References: <20140916185553.GA32690@megas.kitwarein.com>, Message-ID: thanks Dave. We will remember that when we do the compile after 4.2 release... I tried xdmf3 writer using the File->Save Data option in PV v4.2.0-RC1-75-gf64ee7a and the 82M pvd file still turn into a 4.4G h5 file. Not sure if something that I am not doing right? Is there like a compression flag that I can turn on? thanks... thanks -simon ________________________________ From: David E DeMarle [dave.demarle at kitware.com] Sent: Wednesday, September 17, 2014 11:56 AM To: Ben Boeckel Cc: Su, Simon M CTR USARMY ARL (US); paraview at paraview.org Subject: Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON I had similar config problems in the DoD HPC machines I tested on. The root cause was that the system boost was CMakefied and find boost didn't like it but insisted on using it. To get around it I downloaded my own boost (no need to compile it) and made the my PV build use it by: In cmakecache.txt set Boost_NO_SYSTEM_PATHS:BOOL=ON set Boost_NO_BOOST_CMAKE:BOOL=ON Then it will ask for an respect your choice of boost headers to use. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Sep 16, 2014 at 12:55 PM, Ben Boeckel > wrote: On Tue, Sep 16, 2014 at 16:22:38 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if the file > size is still increase 10 fold when saving pvd file to xmf format. > > However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with > -DModule_vtkIOXdmf3:BOOL=ON > > cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=/home/simonsm/tools/ > paraview/paraview-v4.2.0-RC1-75-gf64ee7a_mesa -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > -DPARAVIEW_USE_MPI:BOOL=ON -DPARAVIEW_ENABLE_WEB:BOOL=OFF > -DModule_vtkIOXdmf3:BOOL=ON ../ParaView-v4.2.0-RC1-75-gf64ee7a > > I got whole bunch of boost related cmake error with cmake version 3.0.0 and > cmake version 2.8.12.2. Some of the error messages are included at the end of > this email. > > I am able to compile RC1-22-g9ca4e44 version ok but without Module_vtkIOXdmf3 > set to ON. Is there anything on the boost side that I am not setting it right? > I am compiling on RHEL 6.5 with boost-devel-1.41.0-18.el6.x86_64 installed. Looks to be a CMake-ified boost. It worked here on Fedora with 1.54.0 (which I don't believe is built using CMake anymore). It seems that it doesn't support multiple find_package calls. Try setting Boost_NO_BOOST_CMAKE to ON to force the FindBoost.cmake logic to kick in. --Ben _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Sep 17 12:24:58 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 17 Sep 2014 10:24:58 -0600 Subject: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON In-Reply-To: References: <20140916185553.GA32690@megas.kitwarein.com> Message-ID: I briefly looked at that a couple of weeks ago. Sorry I didn't get back to you before now. My findings were: 1) xdm3writer performs the same as xdmf2writer 2) I didn't find a compression option. So, in other words, I don't have a quick fix and someone needs to put some development time in to improve it. The good news is that there is lots of room for improvement and it shouldn't be too hard to do better on the writer end. It is very likely that the ARL guys will have ideas of on ways to compress within libxdmf. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Sep 17, 2014 at 10:16 AM, Su, Simon M CTR USARMY ARL (US) < simon.m.su.ctr at mail.mil> wrote: > thanks Dave. We will remember that when we do the compile after 4.2 > release... > > I tried xdmf3 writer using the File->Save Data option in PV > v4.2.0-RC1-75-gf64ee7a and the 82M pvd file still turn into a 4.4G h5 file. > Not sure if something that I am not doing right? Is there like a > compression flag that I can turn on? thanks... > > thanks > -simon > ------------------------------ > *From:* David E DeMarle [dave.demarle at kitware.com] > *Sent:* Wednesday, September 17, 2014 11:56 AM > *To:* Ben Boeckel > *Cc:* Su, Simon M CTR USARMY ARL (US); paraview at paraview.org > *Subject:* Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with > -DModule_vtkIOXdmf3:BOOL=ON > > I had similar config problems in the DoD HPC machines I tested on. The > root cause was that the system boost was CMakefied and find boost didn't > like it but insisted on using it. > > To get around it I downloaded my own boost (no need to compile it) and > made the my PV build use it by: > In cmakecache.txt > set Boost_NO_SYSTEM_PATHS:BOOL=ON > set Boost_NO_BOOST_CMAKE:BOOL=ON > Then it will ask for an respect your choice of boost headers to use. > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Tue, Sep 16, 2014 at 12:55 PM, Ben Boeckel > wrote: > >> On Tue, Sep 16, 2014 at 16:22:38 +0000, Su, Simon M CTR USARMY ARL (US) >> wrote: >> > I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if >> the file >> > size is still increase 10 fold when saving pvd file to xmf format. >> > >> > However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with >> > -DModule_vtkIOXdmf3:BOOL=ON >> > >> > cmake -DCMAKE_BUILD_TYPE=release >> -DCMAKE_INSTALL_PREFIX=/home/simonsm/tools/ >> > paraview/paraview-v4.2.0-RC1-75-gf64ee7a_mesa >> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON >> > -DPARAVIEW_USE_MPI:BOOL=ON -DPARAVIEW_ENABLE_WEB:BOOL=OFF >> > -DModule_vtkIOXdmf3:BOOL=ON ../ParaView-v4.2.0-RC1-75-gf64ee7a >> > >> > I got whole bunch of boost related cmake error with cmake version 3.0.0 >> and >> > cmake version 2.8.12.2. Some of the error messages are included at the >> end of >> > this email. >> > >> > I am able to compile RC1-22-g9ca4e44 version ok but without >> Module_vtkIOXdmf3 >> > set to ON. Is there anything on the boost side that I am not setting it >> right? >> > I am compiling on RHEL 6.5 with boost-devel-1.41.0-18.el6.x86_64 >> installed. >> >> Looks to be a CMake-ified boost. It worked here on Fedora with 1.54.0 >> (which I don't believe is built using CMake anymore). It seems that it >> doesn't support multiple find_package calls. Try setting >> Boost_NO_BOOST_CMAKE to ON to force the FindBoost.cmake logic to kick >> in. >> >> --Ben >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Sep 17 12:30:19 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 17 Sep 2014 12:30:19 -0400 Subject: [Paraview] Client server volume rendering problem in 4.1 and 4.2RC1 In-Reply-To: References: <398242C76E3D3740BA94E23089B34E2C85F4B969@EXCHMBX03.fed.cclrc.ac.uk> Message-ID: Ron, Here's a fix that makes ParaView use remote-rendering irrespective of remote-rendering threshold when volume rendering: http://review.source.kitware.com/#/t/4672 It'd be great if you could give it a try to confirm that it works. Thanks Utkarsh On Wed, Sep 17, 2014 at 10:09 AM, Utkarsh Ayachit wrote: > Ron, > > Those are good observations. I has been on my todo list to clean up > the remote-local rendering issue. I want ParaView to automatically > switch to remote rendering, if possible when volume rendering. I'll > see what I can do for that. The volume rendering code is currently > being revamped. I'd expect better "smart" rendering in near future. > > Utkarsh > > On Wed, Sep 17, 2014 at 6:29 AM, wrote: >> Hi, >> >> A post by Robert Atwood in June mentioned a problem with client server >> volume visualisation in PV4.1, and I have also seen problems in this case >> both on Linux and Windows systems. >> >> >> >> Fixes (0014794 and 0014792) have been added to 4.2RC1 which allow correct >> rendering of the wavelet test case. I tried this on a Windows 7 system and >> works ok for 4.2RC1, but not for 4.1. >> >> >> >> However I think that the remote/local render problem for volume >> visualisation is really very confusing and needs to be improved. After >> spending more time then I should with it, I conclude that (again on windows >> 7 64 bit): >> >> (1) Volume rendering only works if done on the remote server, not the >> local on (as acknowledged in a tracker ticket, though I have not seen it >> documented elsewhere). >> >> (2) For 4.1 to do this correctly for just a volume image this seems to >> need settings of ?remote render threshold? ticked and ?0 Mbytes? selected. >> It will work for cases when >0 Mbytes is selected, if there is also another >> object displayed (e.g. an isosurface). This led me to think an additional >> surface was always needed to see the volume, which is not the case. >> >> (3) For 4.2RC1 the interface to settings has changed and there is no >> longer a tick box. Instead the slider for remote local render size has a >> much greater range. This should be set to zero to force remote render for >> volume views. It also works for non-zero values less than the size of the >> volume data, e.g. 4Mbytes for a 256^3 volume. This setting did not seem work >> for 4.1 to force a remote rendering of just volume data. >> >> >> >> I think it would be useful if at least the tool tips in the settings panel >> suggested how to make client server volume rendering work. It would also be >> useful if a warning message were displayed when trying (and failing) to do a >> local volume render in client server mode. >> >> >> >> Another problem that has been observed is that the ?smart? option for volume >> rendering is not necessarily that smart when the server nodes have no GPUs >> and the client does. This was on a Linux 64 bit system with 4.1. >> >> >> >> Thanks, >> >> Ron fowler >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> Scanned by iCritical. >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From simon.m.su.ctr at mail.mil Wed Sep 17 13:06:59 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 17 Sep 2014 17:06:59 +0000 Subject: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON In-Reply-To: References: <20140916185553.GA32690@megas.kitwarein.com> , Message-ID: thanks Dave.... I will pass along the info and see what they want to do... -simon ________________________________ From: David E DeMarle [dave.demarle at kitware.com] Sent: Wednesday, September 17, 2014 12:24 PM To: Su, Simon M CTR USARMY ARL (US) Cc: Ben Boeckel; paraview at paraview.org Subject: Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON I briefly looked at that a couple of weeks ago. Sorry I didn't get back to you before now. My findings were: 1) xdm3writer performs the same as xdmf2writer 2) I didn't find a compression option. So, in other words, I don't have a quick fix and someone needs to put some development time in to improve it. The good news is that there is lots of room for improvement and it shouldn't be too hard to do better on the writer end. It is very likely that the ARL guys will have ideas of on ways to compress within libxdmf. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Sep 17, 2014 at 10:16 AM, Su, Simon M CTR USARMY ARL (US) > wrote: thanks Dave. We will remember that when we do the compile after 4.2 release... I tried xdmf3 writer using the File->Save Data option in PV v4.2.0-RC1-75-gf64ee7a and the 82M pvd file still turn into a 4.4G h5 file. Not sure if something that I am not doing right? Is there like a compression flag that I can turn on? thanks... thanks -simon ________________________________ From: David E DeMarle [dave.demarle at kitware.com] Sent: Wednesday, September 17, 2014 11:56 AM To: Ben Boeckel Cc: Su, Simon M CTR USARMY ARL (US); paraview at paraview.org Subject: Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON I had similar config problems in the DoD HPC machines I tested on. The root cause was that the system boost was CMakefied and find boost didn't like it but insisted on using it. To get around it I downloaded my own boost (no need to compile it) and made the my PV build use it by: In cmakecache.txt set Boost_NO_SYSTEM_PATHS:BOOL=ON set Boost_NO_BOOST_CMAKE:BOOL=ON Then it will ask for an respect your choice of boost headers to use. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Sep 16, 2014 at 12:55 PM, Ben Boeckel > wrote: On Tue, Sep 16, 2014 at 16:22:38 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if the file > size is still increase 10 fold when saving pvd file to xmf format. > > However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with > -DModule_vtkIOXdmf3:BOOL=ON > > cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=/home/simonsm/tools/ > paraview/paraview-v4.2.0-RC1-75-gf64ee7a_mesa -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > -DPARAVIEW_USE_MPI:BOOL=ON -DPARAVIEW_ENABLE_WEB:BOOL=OFF > -DModule_vtkIOXdmf3:BOOL=ON ../ParaView-v4.2.0-RC1-75-gf64ee7a > > I got whole bunch of boost related cmake error with cmake version 3.0.0 and > cmake version 2.8.12.2. Some of the error messages are included at the end of > this email. > > I am able to compile RC1-22-g9ca4e44 version ok but without Module_vtkIOXdmf3 > set to ON. Is there anything on the boost side that I am not setting it right? > I am compiling on RHEL 6.5 with boost-devel-1.41.0-18.el6.x86_64 installed. Looks to be a CMake-ified boost. It worked here on Fedora with 1.54.0 (which I don't believe is built using CMake anymore). It seems that it doesn't support multiple find_package calls. Try setting Boost_NO_BOOST_CMAKE to ON to force the FindBoost.cmake logic to kick in. --Ben _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matthias.Zenker at erbe-med.com Thu Sep 18 03:33:29 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Thu, 18 Sep 2014 07:33:29 +0000 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Hi Utkarsh, any news regarding a reload data function (see below)? Matthias > -----Urspr?ngliche Nachricht----- > Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Gesendet: Montag, 15. September 2014 16:50 > An: Zenker, Dr. Matthias > Cc: Cory Quammen; paraview at paraview.org > Betreff: Re: [Paraview] How to simply "Reload" a data file > > Ah. since it's a file series, it would not work the way Cory is suggesting. I'll see > if I can cook up a Python script that can make this possible for now. We're > putting this on the roadmap for the next release (I know I've said that a few > times in the past :) ). > > Utkarsh > > On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias > wrote: > > Normally I load a time series, either a series of vtu files or a time collection > (pvd file containing the vtu file names with asociated timestamps). During > the simulation, new files are added to the series. So it would be nice to watch > the simulation going on by reloading from time to time. > > > > Matthias > > > >> -----Urspr?ngliche Nachricht----- > >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> Gesendet: Montag, 15. September 2014 16:28 > >> An: Zenker, Dr. Matthias > >> Cc: Cory Quammen; paraview at paraview.org > >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> > >> I suspect will not work with vtu. To understand this better, what is > >> that which is changing that you need to reload the file? Are you > >> loading a file series or a single file? > >> > >> Utkarsh > >> > >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias > >> wrote: > >> > Hi Cory, > >> > > >> > I use the reader for vtu format and pvd (vtu time collection). I > >> > tried to > >> modify the xml as follows: > >> > > >> > > >> > > >> > > >> > >> base_proxyname="VTUReader" class="vtuReader"> > >> > >> panel_widget="command_button"/> > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > But I cannot even load it as plugin. Presumably there are special > >> > keyword to > >> use for the name of the original reader. Is there a documentation > >> where I can find more information on that topic? > >> > > >> > Thanks, > >> > > >> > Matthias > >> > > >> >> -----Urspr?ngliche Nachricht----- > >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] > >> >> Gesendet: Montag, 15. September 2014 15:05 > >> >> An: Zenker, Dr. Matthias > >> >> Cc: paraview at paraview.org > >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> > >> >> Matthias, > >> >> > >> >> The method I suggested requires modifying ParaView's source code, > >> >> so it won't work for a binary distribution. > >> >> > >> >> As for the XML method, did you try to load an Xdmf file through > >> >> what should be the new "Xdmf Reader (Refresh button)" reader? If > >> >> you are loading a different type of file, this plugin will have no > >> >> effect because it provides a Refresh button only for the Xdmf > >> >> reader. You could modify the XML for other reader types, though. > >> >> > >> >> Thanks, > >> >> Cory > >> >> > >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias > >> >> wrote: > >> >> > Hi, > >> >> > > >> >> > I wanted to try the "Reload" button which presumably can be > >> >> > created by > >> >> one of the methods outlined below. But I am maybe too naive or am > >> >> missing > >> >> something: I have a Windoze binary distribution of ParaView 4.0.1. > >> >> I did not find the file indicated by Cory, and copying the xml > >> >> code given by S?bastien into a file and loading that as plugin had > >> >> no effect > >> visible to me. > >> >> > > >> >> > What am I missing here? > >> >> > > >> >> > Thank you, > >> >> > > >> >> > Matthias > >> >> > > >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- > >> >> >> bounces at paraview.org] Im Auftrag von paraview- > >> request at paraview.org > >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 > >> >> >> An: paraview at paraview.org > >> >> >> Betreff: Reload a file > >> >> >> > >> >> >> Send ParaView mailing list submissions to > >> >> >> paraview at paraview.org > >> >> >> > >> >> >> To subscribe or unsubscribe via the World Wide Web, visit > >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> or, via email, send a message with subject or body 'help' to > >> >> >> paraview-request at paraview.org > >> >> >> > >> >> >> You can reach the person managing the list at > >> >> >> paraview-owner at paraview.org > >> >> >> > >> >> >> When replying, please edit your Subject line so it is more > >> >> >> specific than > >> >> "Re: > >> >> >> Contents of ParaView digest..." > >> >> >> > >> >> >> > >> >> >> Today's Topics: > >> >> >> > >> >> >> 1. Re: How to simply "Reload" a data file (Cory Quammen) > >> >> >> > >> >> >> > >> >> >> --------------------------------------------------------------- > >> >> >> --- > >> >> >> --- > >> >> >> - > >> >> >> > >> >> >> Message: 1 > >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 > >> >> >> From: Cory Quammen > >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data file > >> >> >> To: Sebastien Jourdain > >> >> >> Cc: Michael Jackson , ParaView > >> >> >> > >> >> >> Message-ID: > >> >> >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> > >> >> >> Content-Type: text/plain; charset=ISO-8859-1 > >> >> >> > >> >> >> For what it's worth, I just experimented with adding the line > >> >> >> > >> >> >> >> >> >> panel_widget="command_button"/> > >> >> >> > >> >> >> to the CSV reader and XDMF reader in > >> >> >> > >> >> >> > >> >> > >> > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers > >> >> >> .xml > >> >> >> > >> >> >> The Refresh button appears among the other property widgets and > >> >> >> it indeed reloads the data set. > >> >> >> > >> >> >> I would happily add this to all the readers and submit a patch > >> >> >> to gerrit if it would be received well by the core ParaView > developers. > >> >> >> > >> >> >> Thanks, > >> >> >> Cory > >> >> >> > >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain > >> >> >> wrote: > >> >> >> > BTW that's the correct XML for you, just need to create a > >> >> >> > file with that in and load it as a plugin and you will have your > "Refresh" > >> button. > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" > >> >> >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> > >> >> >> > >> >> >> > panel_widget="command_button"/> > >> >> >> > > >> >> >> > >> >> >> > file_description="Xdmf Reader (Refresh button)" /> > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain > >> >> >> > wrote: > >> >> >> >> > >> >> >> >> Another approach could be a python macro that invalidate the > >> >> >> >> "active/selected' proxy in the pipeline, but that one will > >> >> >> >> require the usage of ParaView in built-in mode. > >> >> >> >> > >> >> >> >> If interested I can try to write the corresponding python code... > >> >> >> >> > >> >> >> >> Seb > >> >> >> >> > >> >> >> >> > >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain > >> >> >> >> wrote: > >> >> >> >>> > >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... > >> >> >> >>> No code involved... > >> >> >> >>> > >> >> >> >>> In fact, just having the XML that I wrote in a file extend > >> >> >> >>> the UI with a button to refresh the reader should be enough. > >> >> >> >>> Need to figure out why the reader factory did not catch up > >> >> >> >>> the > >> hint. > >> >> >> >>> > >> >> >> >>> That should be the only thing that you would need. > >> >> >> >>> > >> >> >> >>> Seb > >> >> >> >>> > >> >> >> >>> > >> >> >> >>> > >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson > >> >> >> >>> wrote: > >> >> >> >>>> > >> >> >> >>>> I was hoping that ParaView just had something built in. I > >> >> >> >>>> would rather not have to create a plugin and distribute > >> >> >> >>>> that along side my own software and to keep up on builds > >> >> >> >>>> for all the various OS's and all of that. i tried that for > >> >> >> >>>> a while and I just could not > >> >> keep up. > >> >> >> >>>> > >> >> >> >>>> So either I am the only person who has asked for this or > >> >> >> >>>> there is some over riding reason in the design of ParView > >> >> >> >>>> why this type of functionality is not in ParaView. > >> >> >> >>>> > >> >> >> >>>> Thanks > >> >> >> >>>> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> _ > >> >> >> >>>> Mike Jackson Principal Software Engineer > >> >> >> >>>> BlueQuartz Software Dayton, Ohio > >> >> >> >>>> mike.jackson at bluequartz.net www.bluequartz.net > >> >> >> >>>> > >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu > >> >> >> >>>> > >> >> >> >>>> wrote: > >> >> >> >>>> > >> >> >> >>>> > hi you can try the approach of S?bastien > >> >> >> >>>> > > >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html > >> >> >> >>>> > > >> >> >> >>>> > I haven't tested yet. > >> >> >> >>>> > > >> >> >> >>>> > You can save the code as a macro, so you will have a button. > >> >> >> >>>> > > >> >> >> >>>> > Felipe > >> >> >> >>>> > > >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : > >> >> >> >>>> >> Is there button where I can simply reload a data file > >> >> >> >>>> >> that was read in a pipeline? > >> >> >> >>>> >> > >> >> >> >>>> >> We have a workflow where we process data into a file > >> >> >> >>>> >> and view it in ParaView. it is becoming tedious to blow > >> >> >> >>>> >> away the entire pipeline just to reload the new data. > >> >> >> >>>> >> > >> >> >> >>>> >> I know about state files but this still requires the > >> >> >> >>>> >> user to go to the File->Load State... " menu and then > >> >> >> >>>> >> select a state > >> file. > >> >> >> >>>> >> I would like to just select the data file in the > >> >> >> >>>> >> Pipeline browser (XDMF File reader for us), and just > >> >> >> >>>> >> click some button that just reloads data from the file. > >> >> >> >>>> >> > >> >> >> >>>> >> Or am I just missing something? I am using ParaView > >> >> >> >>>> >> 3.98.1. I have to admit I have not tried any of the > >> >> >> >>>> >> 4.0.RC* > >> downloads. > >> >> >> >>>> >> > >> >> >> >>>> >> Thanks > >> >> >> >>>> >> > >> >> >> > >> >> > >> > _________________________________________________________ > >> >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net > >> >> >> >>>> >> BlueQuartz Software www.bluequartz.net > >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio > >> >> >> >>>> >> > _______________________________________________ > >> >> >> >>>> >> Powered by www.kitware.com > >> >> >> >>>> >> > >> >> >> >>>> >> Visit other Kitware open-source projects at > >> >> >> >>>> >> http://www.kitware.com/opensource/opensource.html > >> >> >> >>>> >> > >> >> >> >>>> >> Please keep messages on-topic and check the ParaView > >> >> >> >>>> >> Wiki > >> at: > >> >> >> >>>> >> http://paraview.org/Wiki/ParaView > >> >> >> >>>> >> > >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: > >> >> >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >>>> > > >> >> >> >>>> > > >> >> >> >>>> > -- > >> >> >> >>>> > Felipe Bordeu Weldt > >> >> >> >>>> > Ing?nieur de Recherche > >> >> >> >>>> > ------------------------------------- > >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 > >> >> >> >>>> > Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 > >> >> >> >>>> > ?cole Centrale Nantes > >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE > >> >> >> >>>> > ------------------------------------- > >> >> >> >>>> > > >> >> >> >>>> > > _______________________________________________ > >> >> >> >>>> > Powered by www.kitware.com > >> >> >> >>>> > > >> >> >> >>>> > Visit other Kitware open-source projects at > >> >> >> >>>> > http://www.kitware.com/opensource/opensource.html > >> >> >> >>>> > > >> >> >> >>>> > Please keep messages on-topic and check the ParaView > >> >> >> >>>> > Wiki > >> at: > >> >> >> >>>> > http://paraview.org/Wiki/ParaView > >> >> >> >>>> > > >> >> >> >>>> > Follow this link to subscribe/unsubscribe: > >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >>>> > >> >> >> >>>> _______________________________________________ > >> >> >> >>>> Powered by www.kitware.com > >> >> >> >>>> > >> >> >> >>>> Visit other Kitware open-source projects at > >> >> >> >>>> http://www.kitware.com/opensource/opensource.html > >> >> >> >>>> > >> >> >> >>>> Please keep messages on-topic and check the ParaView Wiki > at: > >> >> >> >>>> http://paraview.org/Wiki/ParaView > >> >> >> >>>> > >> >> >> >>>> Follow this link to subscribe/unsubscribe: > >> >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >>> > >> >> >> >>> > >> >> >> >> > >> >> >> > > >> >> >> > > >> >> >> > _______________________________________________ > >> >> >> > Powered by www.kitware.com > >> >> >> > > >> >> >> > Visit other Kitware open-source projects at > >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> > > >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> > > >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> > > >> >> >> > >> >> >> > >> >> >> > >> >> >> -- > >> >> >> Cory Quammen > >> >> >> Research Associate > >> >> >> Department of Computer Science > >> >> >> The University of North Carolina at Chapel Hill > >> >> >> > >> >> >> > >> >> >> ------------------------------ > >> >> >> > >> >> >> _______________________________________________ > >> >> >> Powered by www.kitware.com > >> >> >> > >> >> >> Visit other Kitware open-source projects at > >> >> >> http://www.kitware.com/opensource/opensource.html > >> >> >> > >> >> >> Please keep messages on-topic and check the ParaView Wiki at: > >> >> >> http://paraview.org/Wiki/ParaView > >> >> >> > >> >> >> Follow this link to subscribe/unsubscribe: > >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> > >> >> >> > >> >> >> End of ParaView Digest, Vol 110, Issue 42 > >> >> >> ***************************************** > >> >> > > >> >> > > >> >> > > >> >> > >> > __________________________________________________________ > >> >> ___________ > >> >> > ERBE Elektromedizin GmbH > >> >> > Firmensitz: 72072 Tuebingen > >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> > Registergericht: Stuttgart HRB 380137 > >> >> > > >> >> > _______________________________________________ > >> >> > Powered by www.kitware.com > >> >> > > >> >> > Visit other Kitware open-source projects at > >> >> > http://www.kitware.com/opensource/opensource.html > >> >> > > >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> > http://paraview.org/Wiki/ParaView > >> >> > > >> >> > Follow this link to subscribe/unsubscribe: > >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > >> > > >> > > >> > __________________________________________________________ > >> ___________ > >> > ERBE Elektromedizin GmbH > >> > Firmensitz: 72072 Tuebingen > >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> > Registergericht: Stuttgart HRB 380137 > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > __________________________________________________________ > ___________ > > ERBE Elektromedizin GmbH > > Firmensitz: 72072 Tuebingen > > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > > Registergericht: Stuttgart HRB 380137 > > _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 From utkarsh.ayachit at kitware.com Thu Sep 18 08:46:06 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 18 Sep 2014 08:46:06 -0400 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Sorry, didn't get around to it yet. Over this weekend is more likely, since I am tracking down some last minute issues with 4.2 right now. Utkarsh On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias wrote: > Hi Utkarsh, > > any news regarding a reload data function (see below)? > > Matthias > >> -----Urspr?ngliche Nachricht----- >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Gesendet: Montag, 15. September 2014 16:50 >> An: Zenker, Dr. Matthias >> Cc: Cory Quammen; paraview at paraview.org >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> Ah. since it's a file series, it would not work the way Cory is suggesting. I'll see >> if I can cook up a Python script that can make this possible for now. We're >> putting this on the roadmap for the next release (I know I've said that a few >> times in the past :) ). >> >> Utkarsh >> >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias >> wrote: >> > Normally I load a time series, either a series of vtu files or a time collection >> (pvd file containing the vtu file names with asociated timestamps). During >> the simulation, new files are added to the series. So it would be nice to watch >> the simulation going on by reloading from time to time. >> > >> > Matthias >> > >> >> -----Urspr?ngliche Nachricht----- >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> Gesendet: Montag, 15. September 2014 16:28 >> >> An: Zenker, Dr. Matthias >> >> Cc: Cory Quammen; paraview at paraview.org >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> I suspect will not work with vtu. To understand this better, what is >> >> that which is changing that you need to reload the file? Are you >> >> loading a file series or a single file? >> >> >> >> Utkarsh >> >> >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias >> >> wrote: >> >> > Hi Cory, >> >> > >> >> > I use the reader for vtu format and pvd (vtu time collection). I >> >> > tried to >> >> modify the xml as follows: >> >> > >> >> > >> >> > >> >> > >> >> > > >> base_proxyname="VTUReader" class="vtuReader"> >> >> > > >> panel_widget="command_button"/> >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > But I cannot even load it as plugin. Presumably there are special >> >> > keyword to >> >> use for the name of the original reader. Is there a documentation >> >> where I can find more information on that topic? >> >> > >> >> > Thanks, >> >> > >> >> > Matthias >> >> > >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] >> >> >> Gesendet: Montag, 15. September 2014 15:05 >> >> >> An: Zenker, Dr. Matthias >> >> >> Cc: paraview at paraview.org >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> Matthias, >> >> >> >> >> >> The method I suggested requires modifying ParaView's source code, >> >> >> so it won't work for a binary distribution. >> >> >> >> >> >> As for the XML method, did you try to load an Xdmf file through >> >> >> what should be the new "Xdmf Reader (Refresh button)" reader? If >> >> >> you are loading a different type of file, this plugin will have no >> >> >> effect because it provides a Refresh button only for the Xdmf >> >> >> reader. You could modify the XML for other reader types, though. >> >> >> >> >> >> Thanks, >> >> >> Cory >> >> >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias >> >> >> wrote: >> >> >> > Hi, >> >> >> > >> >> >> > I wanted to try the "Reload" button which presumably can be >> >> >> > created by >> >> >> one of the methods outlined below. But I am maybe too naive or am >> >> >> missing >> >> >> something: I have a Windoze binary distribution of ParaView 4.0.1. >> >> >> I did not find the file indicated by Cory, and copying the xml >> >> >> code given by S?bastien into a file and loading that as plugin had >> >> >> no effect >> >> visible to me. >> >> >> > >> >> >> > What am I missing here? >> >> >> > >> >> >> > Thank you, >> >> >> > >> >> >> > Matthias >> >> >> > >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- >> >> >> >> bounces at paraview.org] Im Auftrag von paraview- >> >> request at paraview.org >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 >> >> >> >> An: paraview at paraview.org >> >> >> >> Betreff: Reload a file >> >> >> >> >> >> >> >> Send ParaView mailing list submissions to >> >> >> >> paraview at paraview.org >> >> >> >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> or, via email, send a message with subject or body 'help' to >> >> >> >> paraview-request at paraview.org >> >> >> >> >> >> >> >> You can reach the person managing the list at >> >> >> >> paraview-owner at paraview.org >> >> >> >> >> >> >> >> When replying, please edit your Subject line so it is more >> >> >> >> specific than >> >> >> "Re: >> >> >> >> Contents of ParaView digest..." >> >> >> >> >> >> >> >> >> >> >> >> Today's Topics: >> >> >> >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory Quammen) >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------- >> >> >> >> --- >> >> >> >> --- >> >> >> >> - >> >> >> >> >> >> >> >> Message: 1 >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 >> >> >> >> From: Cory Quammen >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> To: Sebastien Jourdain >> >> >> >> Cc: Michael Jackson , ParaView >> >> >> >> >> >> >> >> Message-ID: >> >> >> >> > >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> >> >> >> >> For what it's worth, I just experimented with adding the line >> >> >> >> >> >> >> >> > >> >> >> panel_widget="command_button"/> >> >> >> >> >> >> >> >> to the CSV reader and XDMF reader in >> >> >> >> >> >> >> >> >> >> >> >> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers >> >> >> >> .xml >> >> >> >> >> >> >> >> The Refresh button appears among the other property widgets and >> >> >> >> it indeed reloads the data set. >> >> >> >> >> >> >> >> I would happily add this to all the readers and submit a patch >> >> >> >> to gerrit if it would be received well by the core ParaView >> developers. >> >> >> >> >> >> >> >> Thanks, >> >> >> >> Cory >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain >> >> >> >> wrote: >> >> >> >> > BTW that's the correct XML for you, just need to create a >> >> >> >> > file with that in and load it as a plugin and you will have your >> "Refresh" >> >> button. >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > > >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" >> >> >> >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> >> >> >> >> > > >> >> >> > panel_widget="command_button"/> >> >> >> >> > >> >> >> >> > > >> >> >> > file_description="Xdmf Reader (Refresh button)" /> >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain >> >> >> >> > wrote: >> >> >> >> >> >> >> >> >> >> Another approach could be a python macro that invalidate the >> >> >> >> >> "active/selected' proxy in the pipeline, but that one will >> >> >> >> >> require the usage of ParaView in built-in mode. >> >> >> >> >> >> >> >> >> >> If interested I can try to write the corresponding python code... >> >> >> >> >> >> >> >> >> >> Seb >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain >> >> >> >> >> wrote: >> >> >> >> >>> >> >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... >> >> >> >> >>> No code involved... >> >> >> >> >>> >> >> >> >> >>> In fact, just having the XML that I wrote in a file extend >> >> >> >> >>> the UI with a button to refresh the reader should be enough. >> >> >> >> >>> Need to figure out why the reader factory did not catch up >> >> >> >> >>> the >> >> hint. >> >> >> >> >>> >> >> >> >> >>> That should be the only thing that you would need. >> >> >> >> >>> >> >> >> >> >>> Seb >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson >> >> >> >> >>> wrote: >> >> >> >> >>>> >> >> >> >> >>>> I was hoping that ParaView just had something built in. I >> >> >> >> >>>> would rather not have to create a plugin and distribute >> >> >> >> >>>> that along side my own software and to keep up on builds >> >> >> >> >>>> for all the various OS's and all of that. i tried that for >> >> >> >> >>>> a while and I just could not >> >> >> keep up. >> >> >> >> >>>> >> >> >> >> >>>> So either I am the only person who has asked for this or >> >> >> >> >>>> there is some over riding reason in the design of ParView >> >> >> >> >>>> why this type of functionality is not in ParaView. >> >> >> >> >>>> >> >> >> >> >>>> Thanks >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> _ >> >> >> >> >>>> Mike Jackson Principal Software Engineer >> >> >> >> >>>> BlueQuartz Software Dayton, Ohio >> >> >> >> >>>> mike.jackson at bluequartz.net www.bluequartz.net >> >> >> >> >>>> >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu >> >> >> >> >>>> >> >> >> >> >>>> wrote: >> >> >> >> >>>> >> >> >> >> >>>> > hi you can try the approach of S?bastien >> >> >> >> >>>> > >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html >> >> >> >> >>>> > >> >> >> >> >>>> > I haven't tested yet. >> >> >> >> >>>> > >> >> >> >> >>>> > You can save the code as a macro, so you will have a button. >> >> >> >> >>>> > >> >> >> >> >>>> > Felipe >> >> >> >> >>>> > >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : >> >> >> >> >>>> >> Is there button where I can simply reload a data file >> >> >> >> >>>> >> that was read in a pipeline? >> >> >> >> >>>> >> >> >> >> >> >>>> >> We have a workflow where we process data into a file >> >> >> >> >>>> >> and view it in ParaView. it is becoming tedious to blow >> >> >> >> >>>> >> away the entire pipeline just to reload the new data. >> >> >> >> >>>> >> >> >> >> >> >>>> >> I know about state files but this still requires the >> >> >> >> >>>> >> user to go to the File->Load State... " menu and then >> >> >> >> >>>> >> select a state >> >> file. >> >> >> >> >>>> >> I would like to just select the data file in the >> >> >> >> >>>> >> Pipeline browser (XDMF File reader for us), and just >> >> >> >> >>>> >> click some button that just reloads data from the file. >> >> >> >> >>>> >> >> >> >> >> >>>> >> Or am I just missing something? I am using ParaView >> >> >> >> >>>> >> 3.98.1. I have to admit I have not tried any of the >> >> >> >> >>>> >> 4.0.RC* >> >> downloads. >> >> >> >> >>>> >> >> >> >> >> >>>> >> Thanks >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> _________________________________________________________ >> >> >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net >> >> >> >> >>>> >> BlueQuartz Software www.bluequartz.net >> >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio >> >> >> >> >>>> >> >> _______________________________________________ >> >> >> >> >>>> >> Powered by www.kitware.com >> >> >> >> >>>> >> >> >> >> >> >>>> >> Visit other Kitware open-source projects at >> >> >> >> >>>> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >>>> >> >> >> >> >> >>>> >> Please keep messages on-topic and check the ParaView >> >> >> >> >>>> >> Wiki >> >> at: >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView >> >> >> >> >>>> >> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: >> >> >> >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >>>> > >> >> >> >> >>>> > >> >> >> >> >>>> > -- >> >> >> >> >>>> > Felipe Bordeu Weldt >> >> >> >> >>>> > Ing?nieur de Recherche >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 >> >> >> >> >>>> > Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 >> >> >> >> >>>> > ?cole Centrale Nantes >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >>>> > >> >> >> >> >>>> > >> _______________________________________________ >> >> >> >> >>>> > Powered by www.kitware.com >> >> >> >> >>>> > >> >> >> >> >>>> > Visit other Kitware open-source projects at >> >> >> >> >>>> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >>>> > >> >> >> >> >>>> > Please keep messages on-topic and check the ParaView >> >> >> >> >>>> > Wiki >> >> at: >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView >> >> >> >> >>>> > >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >>>> >> >> >> >> >>>> _______________________________________________ >> >> >> >> >>>> Powered by www.kitware.com >> >> >> >> >>>> >> >> >> >> >>>> Visit other Kitware open-source projects at >> >> >> >> >>>> http://www.kitware.com/opensource/opensource.html >> >> >> >> >>>> >> >> >> >> >>>> Please keep messages on-topic and check the ParaView Wiki >> at: >> >> >> >> >>>> http://paraview.org/Wiki/ParaView >> >> >> >> >>>> >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: >> >> >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >> >> >> >> >> > >> >> >> >> > >> >> >> >> > _______________________________________________ >> >> >> >> > Powered by www.kitware.com >> >> >> >> > >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> > >> >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> > >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> Cory Quammen >> >> >> >> Research Associate >> >> >> >> Department of Computer Science >> >> >> >> The University of North Carolina at Chapel Hill >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------ >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> Powered by www.kitware.com >> >> >> >> >> >> >> >> Visit other Kitware open-source projects at >> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> >> >> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 >> >> >> >> ***************************************** >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> __________________________________________________________ >> >> >> ___________ >> >> >> > ERBE Elektromedizin GmbH >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> > >> >> >> > _______________________________________________ >> >> >> > Powered by www.kitware.com >> >> >> > >> >> >> > Visit other Kitware open-source projects at >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> > >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> > >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> > >> >> > >> >> > >> >> >> __________________________________________________________ >> >> ___________ >> >> > ERBE Elektromedizin GmbH >> >> > Firmensitz: 72072 Tuebingen >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> > Registergericht: Stuttgart HRB 380137 >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> > http://paraview.org/Wiki/ParaView >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> > >> > >> __________________________________________________________ >> ___________ >> > ERBE Elektromedizin GmbH >> > Firmensitz: 72072 Tuebingen >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> > Registergericht: Stuttgart HRB 380137 >> > > > > _____________________________________________________________________ > ERBE Elektromedizin GmbH > Firmensitz: 72072 Tuebingen > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > Registergericht: Stuttgart HRB 380137 > From Matthias.Zenker at erbe-med.com Thu Sep 18 09:34:12 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Thu, 18 Sep 2014 13:34:12 +0000 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: OK - but don't forget that the weekend is also there to have some free time... ;) Matthias > -----Urspr?ngliche Nachricht----- > Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Gesendet: Donnerstag, 18. September 2014 14:46 > An: Zenker, Dr. Matthias > Cc: Cory Quammen; paraview at paraview.org > Betreff: Re: [Paraview] How to simply "Reload" a data file > > Sorry, didn't get around to it yet. Over this weekend is more likely, since I am > tracking down some last minute issues with 4.2 right now. > > Utkarsh > > On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias > wrote: > > Hi Utkarsh, > > > > any news regarding a reload data function (see below)? > > > > Matthias > > > >> -----Urspr?ngliche Nachricht----- > >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> Gesendet: Montag, 15. September 2014 16:50 > >> An: Zenker, Dr. Matthias > >> Cc: Cory Quammen; paraview at paraview.org > >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> > >> Ah. since it's a file series, it would not work the way Cory is > >> suggesting. I'll see if I can cook up a Python script that can make > >> this possible for now. We're putting this on the roadmap for the next > >> release (I know I've said that a few times in the past :) ). > >> > >> Utkarsh > >> > >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias > >> wrote: > >> > Normally I load a time series, either a series of vtu files or a > >> > time collection > >> (pvd file containing the vtu file names with asociated timestamps). > >> During the simulation, new files are added to the series. So it would > >> be nice to watch the simulation going on by reloading from time to time. > >> > > >> > Matthias > >> > > >> >> -----Urspr?ngliche Nachricht----- > >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> Gesendet: Montag, 15. September 2014 16:28 > >> >> An: Zenker, Dr. Matthias > >> >> Cc: Cory Quammen; paraview at paraview.org > >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> > >> >> I suspect will not work with vtu. To understand this better, what > >> >> is that which is changing that you need to reload the file? Are > >> >> you loading a file series or a single file? > >> >> > >> >> Utkarsh > >> >> > >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias > >> >> wrote: > >> >> > Hi Cory, > >> >> > > >> >> > I use the reader for vtu format and pvd (vtu time collection). I > >> >> > tried to > >> >> modify the xml as follows: > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > >> >> base_proxyname="VTUReader" class="vtuReader"> > >> >> > >> >> panel_widget="command_button"/> > >> >> > > >> >> > >> >> > file_description="vtu Reader > >> >> (Refresh button)" /> > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > But I cannot even load it as plugin. Presumably there are > >> >> > special keyword to > >> >> use for the name of the original reader. Is there a documentation > >> >> where I can find more information on that topic? > >> >> > > >> >> > Thanks, > >> >> > > >> >> > Matthias > >> >> > > >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] > >> >> >> Gesendet: Montag, 15. September 2014 15:05 > >> >> >> An: Zenker, Dr. Matthias > >> >> >> Cc: paraview at paraview.org > >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> >> > >> >> >> Matthias, > >> >> >> > >> >> >> The method I suggested requires modifying ParaView's source > >> >> >> code, so it won't work for a binary distribution. > >> >> >> > >> >> >> As for the XML method, did you try to load an Xdmf file through > >> >> >> what should be the new "Xdmf Reader (Refresh button)" reader? > >> >> >> If you are loading a different type of file, this plugin will > >> >> >> have no effect because it provides a Refresh button only for > >> >> >> the Xdmf reader. You could modify the XML for other reader types, > though. > >> >> >> > >> >> >> Thanks, > >> >> >> Cory > >> >> >> > >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias > >> >> >> wrote: > >> >> >> > Hi, > >> >> >> > > >> >> >> > I wanted to try the "Reload" button which presumably can be > >> >> >> > created by > >> >> >> one of the methods outlined below. But I am maybe too naive or > >> >> >> am missing > >> >> >> something: I have a Windoze binary distribution of ParaView 4.0.1. > >> >> >> I did not find the file indicated by Cory, and copying the xml > >> >> >> code given by S?bastien into a file and loading that as plugin > >> >> >> had no effect > >> >> visible to me. > >> >> >> > > >> >> >> > What am I missing here? > >> >> >> > > >> >> >> > Thank you, > >> >> >> > > >> >> >> > Matthias > >> >> >> > > >> >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- > >> >> >> >> bounces at paraview.org] Im Auftrag von paraview- > >> >> request at paraview.org > >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 > >> >> >> >> An: paraview at paraview.org > >> >> >> >> Betreff: Reload a file > >> >> >> >> > >> >> >> >> Send ParaView mailing list submissions to > >> >> >> >> paraview at paraview.org > >> >> >> >> > >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit > >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> or, via email, send a message with subject or body 'help' to > >> >> >> >> paraview-request at paraview.org > >> >> >> >> > >> >> >> >> You can reach the person managing the list at > >> >> >> >> paraview-owner at paraview.org > >> >> >> >> > >> >> >> >> When replying, please edit your Subject line so it is more > >> >> >> >> specific than > >> >> >> "Re: > >> >> >> >> Contents of ParaView digest..." > >> >> >> >> > >> >> >> >> > >> >> >> >> Today's Topics: > >> >> >> >> > >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory Quammen) > >> >> >> >> > >> >> >> >> > >> >> >> >> ------------------------------------------------------------ > >> >> >> >> --- > >> >> >> >> --- > >> >> >> >> --- > >> >> >> >> - > >> >> >> >> > >> >> >> >> Message: 1 > >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 > >> >> >> >> From: Cory Quammen > >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data file > >> >> >> >> To: Sebastien Jourdain > >> >> >> >> Cc: Michael Jackson , > ParaView > >> >> >> >> > >> >> >> >> Message-ID: > >> >> >> >> >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> > >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 > >> >> >> >> > >> >> >> >> For what it's worth, I just experimented with adding the > >> >> >> >> line > >> >> >> >> > >> >> >> >> >> >> >> >> panel_widget="command_button"/> > >> >> >> >> > >> >> >> >> to the CSV reader and XDMF reader in > >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers > >> >> >> >> .xml > >> >> >> >> > >> >> >> >> The Refresh button appears among the other property widgets > >> >> >> >> and it indeed reloads the data set. > >> >> >> >> > >> >> >> >> I would happily add this to all the readers and submit a > >> >> >> >> patch to gerrit if it would be received well by the core > >> >> >> >> ParaView > >> developers. > >> >> >> >> > >> >> >> >> Thanks, > >> >> >> >> Cory > >> >> >> >> > >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain > >> >> >> >> wrote: > >> >> >> >> > BTW that's the correct XML for you, just need to create a > >> >> >> >> > file with that in and load it as a plugin and you will > >> >> >> >> > have your > >> "Refresh" > >> >> button. > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > >> >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" > >> >> >> >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> > >> >> >> >> > >> >> >> >> > panel_widget="command_button"/> > >> >> >> >> > > >> >> >> >> > >> >> >> >> > file_description="Xdmf Reader (Refresh button)" /> > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain > >> >> >> >> > wrote: > >> >> >> >> >> > >> >> >> >> >> Another approach could be a python macro that invalidate > >> >> >> >> >> the "active/selected' proxy in the pipeline, but that one > >> >> >> >> >> will require the usage of ParaView in built-in mode. > >> >> >> >> >> > >> >> >> >> >> If interested I can try to write the corresponding python > code... > >> >> >> >> >> > >> >> >> >> >> Seb > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain > >> >> >> >> >> wrote: > >> >> >> >> >>> > >> >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... > >> >> >> >> >>> No code involved... > >> >> >> >> >>> > >> >> >> >> >>> In fact, just having the XML that I wrote in a file > >> >> >> >> >>> extend the UI with a button to refresh the reader should be > enough. > >> >> >> >> >>> Need to figure out why the reader factory did not catch > >> >> >> >> >>> up the > >> >> hint. > >> >> >> >> >>> > >> >> >> >> >>> That should be the only thing that you would need. > >> >> >> >> >>> > >> >> >> >> >>> Seb > >> >> >> >> >>> > >> >> >> >> >>> > >> >> >> >> >>> > >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson > >> >> >> >> >>> wrote: > >> >> >> >> >>>> > >> >> >> >> >>>> I was hoping that ParaView just had something built in. > >> >> >> >> >>>> I would rather not have to create a plugin and > >> >> >> >> >>>> distribute that along side my own software and to keep > >> >> >> >> >>>> up on builds for all the various OS's and all of that. > >> >> >> >> >>>> i tried that for a while and I just could not > >> >> >> keep up. > >> >> >> >> >>>> > >> >> >> >> >>>> So either I am the only person who has asked for this > >> >> >> >> >>>> or there is some over riding reason in the design of > >> >> >> >> >>>> ParView why this type of functionality is not in ParaView. > >> >> >> >> >>>> > >> >> >> >> >>>> Thanks > >> >> >> >> >>>> > >> >> >> >> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> >> _ > >> >> >> >> >>>> Mike Jackson Principal Software Engineer > >> >> >> >> >>>> BlueQuartz Software Dayton, Ohio > >> >> >> >> >>>> mike.jackson at bluequartz.net www.bluequartz.net > >> >> >> >> >>>> > >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu > >> >> >> >> >>>> > >> >> >> >> >>>> wrote: > >> >> >> >> >>>> > >> >> >> >> >>>> > hi you can try the approach of S?bastien > >> >> >> >> >>>> > > >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html > >> >> >> >> >>>> > > >> >> >> >> >>>> > I haven't tested yet. > >> >> >> >> >>>> > > >> >> >> >> >>>> > You can save the code as a macro, so you will have a > button. > >> >> >> >> >>>> > > >> >> >> >> >>>> > Felipe > >> >> >> >> >>>> > > >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : > >> >> >> >> >>>> >> Is there button where I can simply reload a data > >> >> >> >> >>>> >> file that was read in a pipeline? > >> >> >> >> >>>> >> > >> >> >> >> >>>> >> We have a workflow where we process data into a file > >> >> >> >> >>>> >> and view it in ParaView. it is becoming tedious to > >> >> >> >> >>>> >> blow away the entire pipeline just to reload the new > data. > >> >> >> >> >>>> >> > >> >> >> >> >>>> >> I know about state files but this still requires > >> >> >> >> >>>> >> the user to go to the File->Load State... " menu and > >> >> >> >> >>>> >> then select a state > >> >> file. > >> >> >> >> >>>> >> I would like to just select the data file in the > >> >> >> >> >>>> >> Pipeline browser (XDMF File reader for us), and just > >> >> >> >> >>>> >> click some button that just reloads data from the file. > >> >> >> >> >>>> >> > >> >> >> >> >>>> >> Or am I just missing something? I am using ParaView > >> >> >> >> >>>> >> 3.98.1. I have to admit I have not tried any of the > >> >> >> >> >>>> >> 4.0.RC* > >> >> downloads. > >> >> >> >> >>>> >> > >> >> >> >> >>>> >> Thanks > >> >> >> >> >>>> >> > >> >> >> >> > >> >> >> > >> >> > >> > _________________________________________________________ > >> >> >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net > >> >> >> >> >>>> >> BlueQuartz Software www.bluequartz.net > >> >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio > >> >> >> >> >>>> >> > >> _______________________________________________ > >> >> >> >> >>>> >> Powered by www.kitware.com > >> >> >> >> >>>> >> > >> >> >> >> >>>> >> Visit other Kitware open-source projects at > >> >> >> >> >>>> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >>>> >> > >> >> >> >> >>>> >> Please keep messages on-topic and check the ParaView > >> >> >> >> >>>> >> Wiki > >> >> at: > >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView > >> >> >> >> >>>> >> > >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: > >> >> >> >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >>>> > > >> >> >> >> >>>> > > >> >> >> >> >>>> > -- > >> >> >> >> >>>> > Felipe Bordeu Weldt > >> >> >> >> >>>> > Ing?nieur de Recherche > >> >> >> >> >>>> > ------------------------------------- > >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 > >> >> >> >> >>>> > Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS > >> >> >> >> >>>> > 6183 ?cole Centrale Nantes > >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE > >> >> >> >> >>>> > ------------------------------------- > >> >> >> >> >>>> > > >> >> >> >> >>>> > > >> _______________________________________________ > >> >> >> >> >>>> > Powered by www.kitware.com > >> >> >> >> >>>> > > >> >> >> >> >>>> > Visit other Kitware open-source projects at > >> >> >> >> >>>> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >>>> > > >> >> >> >> >>>> > Please keep messages on-topic and check the ParaView > >> >> >> >> >>>> > Wiki > >> >> at: > >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView > >> >> >> >> >>>> > > >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: > >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >>>> > >> >> >> >> >>>> > _______________________________________________ > >> >> >> >> >>>> Powered by www.kitware.com > >> >> >> >> >>>> > >> >> >> >> >>>> Visit other Kitware open-source projects at > >> >> >> >> >>>> http://www.kitware.com/opensource/opensource.html > >> >> >> >> >>>> > >> >> >> >> >>>> Please keep messages on-topic and check the ParaView > >> >> >> >> >>>> Wiki > >> at: > >> >> >> >> >>>> http://paraview.org/Wiki/ParaView > >> >> >> >> >>>> > >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: > >> >> >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >>> > >> >> >> >> >>> > >> >> >> >> >> > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > _______________________________________________ > >> >> >> >> > Powered by www.kitware.com > >> >> >> >> > > >> >> >> >> > Visit other Kitware open-source projects at > >> >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> > > >> >> >> >> > Please keep messages on-topic and check the ParaView Wiki > at: > >> >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> >> > > >> >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> > > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> -- > >> >> >> >> Cory Quammen > >> >> >> >> Research Associate > >> >> >> >> Department of Computer Science The University of North > >> >> >> >> Carolina at Chapel Hill > >> >> >> >> > >> >> >> >> > >> >> >> >> ------------------------------ > >> >> >> >> > >> >> >> >> _______________________________________________ > >> >> >> >> Powered by www.kitware.com > >> >> >> >> > >> >> >> >> Visit other Kitware open-source projects at > >> >> >> >> http://www.kitware.com/opensource/opensource.html > >> >> >> >> > >> >> >> >> Please keep messages on-topic and check the ParaView Wiki at: > >> >> >> >> http://paraview.org/Wiki/ParaView > >> >> >> >> > >> >> >> >> Follow this link to subscribe/unsubscribe: > >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> > >> >> >> >> > >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 > >> >> >> >> ***************************************** > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> ___________ > >> >> >> > ERBE Elektromedizin GmbH > >> >> >> > Firmensitz: 72072 Tuebingen > >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> >> > Registergericht: Stuttgart HRB 380137 > >> >> >> > > >> >> >> > _______________________________________________ > >> >> >> > Powered by www.kitware.com > >> >> >> > > >> >> >> > Visit other Kitware open-source projects at > >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> > > >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> > > >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> >> > > >> >> > > >> >> > > >> >> > >> > __________________________________________________________ > >> >> ___________ > >> >> > ERBE Elektromedizin GmbH > >> >> > Firmensitz: 72072 Tuebingen > >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> > Registergericht: Stuttgart HRB 380137 > >> >> > > >> >> > _______________________________________________ > >> >> > Powered by www.kitware.com > >> >> > > >> >> > Visit other Kitware open-source projects at > >> >> > http://www.kitware.com/opensource/opensource.html > >> >> > > >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> > http://paraview.org/Wiki/ParaView > >> >> > > >> >> > Follow this link to subscribe/unsubscribe: > >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > >> > > >> > > >> > __________________________________________________________ > >> ___________ > >> > ERBE Elektromedizin GmbH > >> > Firmensitz: 72072 Tuebingen > >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> > Registergericht: Stuttgart HRB 380137 > >> > > > > > > > > __________________________________________________________ > ___________ > > ERBE Elektromedizin GmbH > > Firmensitz: 72072 Tuebingen > > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > > Registergericht: Stuttgart HRB 380137 > > _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 From Robert-Zoltan.Szasz at energy.lth.se Fri Sep 19 02:56:41 2014 From: Robert-Zoltan.Szasz at energy.lth.se (Robert-Zoltan Szasz) Date: Fri, 19 Sep 2014 08:56:41 +0200 Subject: [Paraview] proper formatting of 2D data Message-ID: <541BD3A9.6010206@energy.lth.se> Hi, I tried to visualize 2D structured point data when I observed a strange behavior. If the spacing in Y direction is negative, the data is flipped upside-down in 'Slice' representation mode but shown properly as a 'Surface' representation. Tried in v. 4.0.1 and 4.2rc1 on Linux 64 bit. Here is a small VTK file to test: --8<-- # vtk DataFile Version 2.0 testing ASCII DATASET STRUCTURED_POINTS DIMENSIONS 3 4 1 ORIGIN 0.0 0.0 0.0 SPACING 0.5 -0.75 1.0 POINT_DATA 12 SCALARS test float LOOKUP_TABLE default 0.0 1.0 2.0 1.0 2.0 3.0 2.0 3.0 4.0 3.0 4.0 5.0 -->8-- I am wondering if I missed something when formatting the file or if you have any ideas how to avoid this behavior? Thanks, Robert -- Robert-Zoltan Szasz Div.Fluid Mechanics Tel: +46-46-222 0480 Dept. Energy Sciences, LTH Fax: +46-46-222 4717 Lund University From ronald.fowler at stfc.ac.uk Fri Sep 19 09:34:19 2014 From: ronald.fowler at stfc.ac.uk (ronald.fowler at stfc.ac.uk) Date: Fri, 19 Sep 2014 13:34:19 +0000 Subject: [Paraview] Client server volume rendering problem in 4.1 and 4.2RC1 In-Reply-To: References: <398242C76E3D3740BA94E23089B34E2C85F4B969@EXCHMBX03.fed.cclrc.ac.uk> Message-ID: <398242C76E3D3740BA94E23089B34E2C85F5EA78@EXCHMBX03.fed.cclrc.ac.uk> Hi Utkarsh, I have just downloaded the latest nightly build and it seems to work fine now (on Windows 7/64bit), doing remote volume rendering irrespective of the settings for remote/local. Many thanks for that quick fix. Ron -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: 17 September 2014 17:30 To: Fowler, Ronald (STFC,RAL,SC) Cc: ParaView Subject: Re: [Paraview] Client server volume rendering problem in 4.1 and 4.2RC1 Ron, Here's a fix that makes ParaView use remote-rendering irrespective of remote-rendering threshold when volume rendering: http://review.source.kitware.com/#/t/4672 It'd be great if you could give it a try to confirm that it works. Thanks Utkarsh On Wed, Sep 17, 2014 at 10:09 AM, Utkarsh Ayachit wrote: > Ron, > > Those are good observations. I has been on my todo list to clean up > the remote-local rendering issue. I want ParaView to automatically > switch to remote rendering, if possible when volume rendering. I'll > see what I can do for that. The volume rendering code is currently > being revamped. I'd expect better "smart" rendering in near future. > > Utkarsh > > On Wed, Sep 17, 2014 at 6:29 AM, wrote: >> Hi, >> >> A post by Robert Atwood in June mentioned a problem with client >> server volume visualisation in PV4.1, and I have also seen problems >> in this case both on Linux and Windows systems. >> >> >> >> Fixes (0014794 and 0014792) have been added to 4.2RC1 which allow >> correct rendering of the wavelet test case. I tried this on a Windows >> 7 system and works ok for 4.2RC1, but not for 4.1. >> >> >> >> However I think that the remote/local render problem for volume >> visualisation is really very confusing and needs to be improved. >> After spending more time then I should with it, I conclude that >> (again on windows >> 7 64 bit): >> >> (1) Volume rendering only works if done on the remote server, not the >> local on (as acknowledged in a tracker ticket, though I have not seen >> it documented elsewhere). >> >> (2) For 4.1 to do this correctly for just a volume image this seems to >> need settings of ?remote render threshold? ticked and ?0 Mbytes? selected. >> It will work for cases when >0 Mbytes is selected, if there is also >> another object displayed (e.g. an isosurface). This led me to think >> an additional surface was always needed to see the volume, which is not the case. >> >> (3) For 4.2RC1 the interface to settings has changed and there is no >> longer a tick box. Instead the slider for remote local render size >> has a much greater range. This should be set to zero to force remote >> render for volume views. It also works for non-zero values less than >> the size of the volume data, e.g. 4Mbytes for a 256^3 volume. This >> setting did not seem work for 4.1 to force a remote rendering of just volume data. >> >> >> >> I think it would be useful if at least the tool tips in the settings >> panel suggested how to make client server volume rendering work. It >> would also be useful if a warning message were displayed when trying >> (and failing) to do a local volume render in client server mode. >> >> >> >> Another problem that has been observed is that the ?smart? option for >> volume rendering is not necessarily that smart when the server nodes >> have no GPUs and the client does. This was on a Linux 64 bit system with 4.1. >> >> >> >> Thanks, >> >> Ron fowler >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> Scanned by iCritical. >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From pspeachum at gmail.com Fri Sep 19 10:25:00 2014 From: pspeachum at gmail.com (Philipp E) Date: Fri, 19 Sep 2014 16:25:00 +0200 Subject: [Paraview] 3D contour smoothness Message-ID: <541C3CBC.9080302@googlemail.com> Hello everyone, after extensive search I was desperate enough to post on this list: It appears that the surface smoothing algorithm of the contour filter does not work as "aggressive" as in older version (3.14.1 was the last one we found to do so). As an example I prepared this two screenshots, VTK data are scalars on a structured grid (200x100x100), legacy format. (An additional call of the "smooth" filter does not help.) 3.14.1 http://s7.directupload.net/images/140919/euadfvko.png 4.0.RC1 http://s14.directupload.net/images/140919/84y689mi.png Both versions are running with the shipped settings. Since the effect could be reproduced on several workstations, we are wondering whether there has been an (undocumented?) change in the filter mechanism or some option we/setting/data problem we are not aware of. Kind regards and thanks in advance Philipp Engels. From cory.quammen at kitware.com Fri Sep 19 10:40:32 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 19 Sep 2014 10:40:32 -0400 Subject: [Paraview] 3D contour smoothness In-Reply-To: <541C3CBC.9080302@googlemail.com> References: <541C3CBC.9080302@googlemail.com> Message-ID: Philipp, In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? Also, are the contour values the same between the two versions? Thanks, Cory On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: > Hello everyone, > > after extensive search I was desperate enough to post on this list: > > It appears that the surface smoothing algorithm of the contour filter > does not work as "aggressive" as in older version (3.14.1 was the last > one we found to do so). As an example I prepared this two screenshots, > VTK data are scalars on a structured grid (200x100x100), legacy format. > (An additional call of the "smooth" filter does not help.) > > 3.14.1 > http://s7.directupload.net/images/140919/euadfvko.png > 4.0.RC1 > http://s14.directupload.net/images/140919/84y689mi.png > > Both versions are running with the shipped settings. Since the effect > could be reproduced on several workstations, we are wondering whether > there has been an (undocumented?) change in the filter mechanism or some > option we/setting/data problem we are not aware of. > > Kind regards and thanks in advance > Philipp Engels. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From shawn.waldon at kitware.com Fri Sep 19 10:40:38 2014 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Fri, 19 Sep 2014 10:40:38 -0400 Subject: [Paraview] seg.fault when reading VRML files twice In-Reply-To: References: <20140903.115011.281070362.furutaka.kazuyoshi@jaea.go.jp> <20140905.072750.413866329.furutaka.kazuyoshi@jaea.go.jp> Message-ID: Hi Kazuyoshi, The fix has been merged into the main branch of ParaView and should be available in nightly builds as of today. -Shawn On Fri, Sep 5, 2014 at 9:37 AM, Shawn Waldon wrote: > Hi Kazuyoshi, > > I've tracked down the segfault, which results from a bug in the VTK VRML > importer class. You will get the same thing if you delete a VRML Reader > and re-create it. It will affect any current build of ParaView. Fixing it > is going to require restructuring that class somewhat and will take a day > or two. For now, just try to avoid this particular use case if possible > and I'll let you know as soon as it is fixed and merged into ParaView. > > -Shawn > > On Thu, Sep 4, 2014 at 6:27 PM, Kazuyoshi Furutaka < > furutaka.kazuyoshi at jaea.go.jp> wrote: > >> Updates: >> >> (v) also occurs w/ ParaView-4.2.0-RC1-Windows-32bit.exe as well >> as a 4.2.0-RC1 binary compiled on Fedora 20 (i386). >> >> Any suggestions? >> >> Thanks. >> Kazuyoshi >> >> From: Kazuyoshi Furutaka >> Subject: [Paraview] seg.fault when reading VRML files twice >> Date: Wed, 03 Sep 2014 11:50:11 +0900 (JST) >> >> > Dear ParaView experts... >> > >> > As the subject says, I'm suffering from the segmentation faluts >> > when reading VRML files. >> > >> > It occurs: >> > (i) File->Open a VRML file, display the content, >> > (File->Disconnect) then File->Open a VRML file and display it, >> > >> > (ii) on linux (Fedora 20, binary package: paraview-4.1.0-1.fc20.i686) >> > as well as on windows (Vista Business SP2, "4.1.0 32-bit", >> > ParaView-4.1.0-Windows-32bit.exe, downloaded from >> > http://www.paraview.org/download/ >> > >> > (iii) regardless of whether the second VRML file is the same as >> > or different from the first one, >> > >> > (iV) even with a simple VRML file as the attached one... >> > >> > It DOES NOT occur when loading/displaying multiple VRML files >> > in the same session (w/o disconnecting)... >> > >> > How can I avoid/fix this? >> > >> > I'll attach a trimmed backtrace obtained on linux with gdb... >> > >> > Thanks in advance. >> > >> > Kazuyoshi >> > -- >> > Kazuyoshi Furutaka >> > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp >> -- >> Kazuyoshi Furutaka >> furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pspeachum at gmail.com Fri Sep 19 10:48:15 2014 From: pspeachum at gmail.com (Philipp E) Date: Fri, 19 Sep 2014 16:48:15 +0200 Subject: [Paraview] 3D contour smoothness In-Reply-To: References: <541C3CBC.9080302@googlemail.com> Message-ID: <541C422F.70508@googlemail.com> Hi Cory, thank you for your fast feedback. a) Compute normal is checked. (Without normals, the contour is completely stepped) b) Contour values are the same. Regards Philipp On 09/19/2014 04:40 PM, Cory Quammen wrote: > Philipp, > > In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? > > Also, are the contour values the same between the two versions? > > Thanks, > Cory > > On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: >> Hello everyone, >> >> after extensive search I was desperate enough to post on this list: >> >> It appears that the surface smoothing algorithm of the contour filter >> does not work as "aggressive" as in older version (3.14.1 was the last >> one we found to do so). As an example I prepared this two screenshots, >> VTK data are scalars on a structured grid (200x100x100), legacy format. >> (An additional call of the "smooth" filter does not help.) >> >> 3.14.1 >> http://s7.directupload.net/images/140919/euadfvko.png >> 4.0.RC1 >> http://s14.directupload.net/images/140919/84y689mi.png >> >> Both versions are running with the shipped settings. Since the effect >> could be reproduced on several workstations, we are wondering whether >> there has been an (undocumented?) change in the filter mechanism or some >> option we/setting/data problem we are not aware of. >> >> Kind regards and thanks in advance >> Philipp Engels. >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From cory.quammen at kitware.com Fri Sep 19 10:59:37 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 19 Sep 2014 10:59:37 -0400 Subject: [Paraview] 3D contour smoothness In-Reply-To: <541C422F.70508@googlemail.com> References: <541C3CBC.9080302@googlemail.com> <541C422F.70508@googlemail.com> Message-ID: Phillipp, Do you have a data set similar to the one you've shown that you can share? Thanks, Cory On Fri, Sep 19, 2014 at 10:48 AM, Philipp E wrote: > Hi Cory, > > thank you for your fast feedback. > > a) Compute normal is checked. (Without normals, the contour is > completely stepped) > b) Contour values are the same. > > Regards > Philipp > > On 09/19/2014 04:40 PM, Cory Quammen wrote: >> Philipp, >> >> In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? >> >> Also, are the contour values the same between the two versions? >> >> Thanks, >> Cory >> >> On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: >>> Hello everyone, >>> >>> after extensive search I was desperate enough to post on this list: >>> >>> It appears that the surface smoothing algorithm of the contour filter >>> does not work as "aggressive" as in older version (3.14.1 was the last >>> one we found to do so). As an example I prepared this two screenshots, >>> VTK data are scalars on a structured grid (200x100x100), legacy format. >>> (An additional call of the "smooth" filter does not help.) >>> >>> 3.14.1 >>> http://s7.directupload.net/images/140919/euadfvko.png >>> 4.0.RC1 >>> http://s14.directupload.net/images/140919/84y689mi.png >>> >>> Both versions are running with the shipped settings. Since the effect >>> could be reproduced on several workstations, we are wondering whether >>> there has been an (undocumented?) change in the filter mechanism or some >>> option we/setting/data problem we are not aware of. >>> >>> Kind regards and thanks in advance >>> Philipp Engels. >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview > From cory.quammen at kitware.com Fri Sep 19 11:46:56 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 19 Sep 2014 11:46:56 -0400 Subject: [Paraview] 3D contour smoothness In-Reply-To: <541C48F2.2090704@googlemail.com> References: <541C3CBC.9080302@googlemail.com> <541C422F.70508@googlemail.com> <541C48F2.2090704@googlemail.com> Message-ID: Philipp, I can confirm what you see with a pre 4.2 version of ParaView. However, the number of produced cells is the same. I will try to track down why this changed. Thanks, Cory On Fri, Sep 19, 2014 at 11:17 AM, Philipp E wrote: > Hi Cory > > I managed to compress the data set to a fair size and attached it to > this mail. The data set is pressure, contour value is 0.55. > > By looking again at the data (contour -> information), I just found that > the old version (3.14.1) uses 148432 cells , while the the new one > employs 75232 cells. Hope that helps. > > Kind regards > Philipp > > Errata: I meant 4.2.0RC1 in the previous mails. > > On 09/19/2014 04:59 PM, Cory Quammen wrote: >> Phillipp, >> >> Do you have a data set similar to the one you've shown that you can share? >> >> Thanks, >> Cory >> >> On Fri, Sep 19, 2014 at 10:48 AM, Philipp E wrote: >>> Hi Cory, >>> >>> thank you for your fast feedback. >>> >>> a) Compute normal is checked. (Without normals, the contour is >>> completely stepped) >>> b) Contour values are the same. >>> >>> Regards >>> Philipp >>> >>> On 09/19/2014 04:40 PM, Cory Quammen wrote: >>>> Philipp, >>>> >>>> In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? >>>> >>>> Also, are the contour values the same between the two versions? >>>> >>>> Thanks, >>>> Cory >>>> >>>> On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: >>>>> Hello everyone, >>>>> >>>>> after extensive search I was desperate enough to post on this list: >>>>> >>>>> It appears that the surface smoothing algorithm of the contour filter >>>>> does not work as "aggressive" as in older version (3.14.1 was the last >>>>> one we found to do so). As an example I prepared this two screenshots, >>>>> VTK data are scalars on a structured grid (200x100x100), legacy format. >>>>> (An additional call of the "smooth" filter does not help.) >>>>> >>>>> 3.14.1 >>>>> http://s7.directupload.net/images/140919/euadfvko.png >>>>> 4.0.RC1 >>>>> http://s14.directupload.net/images/140919/84y689mi.png >>>>> >>>>> Both versions are running with the shipped settings. Since the effect >>>>> could be reproduced on several workstations, we are wondering whether >>>>> there has been an (undocumented?) change in the filter mechanism or some >>>>> option we/setting/data problem we are not aware of. >>>>> >>>>> Kind regards and thanks in advance >>>>> Philipp Engels. >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview > From pspeachum at gmail.com Fri Sep 19 12:08:57 2014 From: pspeachum at gmail.com (Philipp E.) Date: Fri, 19 Sep 2014 18:08:57 +0200 Subject: [Paraview] 3D contour smoothness In-Reply-To: References: <541C3CBC.9080302@googlemail.com> <541C422F.70508@googlemail.com> <541C48F2.2090704@googlemail.com> Message-ID: <541C5519.505@googlemail.com> Sorry Cory, you are right. The cell number is the same. Regards Philipp Am 19.09.2014 um 17:46 schrieb Cory Quammen: > Philipp, > > I can confirm what you see with a pre 4.2 version of ParaView. > However, the number of produced cells is the same. > > I will try to track down why this changed. > > Thanks, > Cory > > On Fri, Sep 19, 2014 at 11:17 AM, Philipp E wrote: >> Hi Cory >> >> I managed to compress the data set to a fair size and attached it to >> this mail. The data set is pressure, contour value is 0.55. >> >> By looking again at the data (contour -> information), I just found that >> the old version (3.14.1) uses 148432 cells , while the the new one >> employs 75232 cells. Hope that helps. >> >> Kind regards >> Philipp >> >> Errata: I meant 4.2.0RC1 in the previous mails. >> >> On 09/19/2014 04:59 PM, Cory Quammen wrote: >>> Phillipp, >>> >>> Do you have a data set similar to the one you've shown that you can share? >>> >>> Thanks, >>> Cory >>> >>> On Fri, Sep 19, 2014 at 10:48 AM, Philipp E wrote: >>>> Hi Cory, >>>> >>>> thank you for your fast feedback. >>>> >>>> a) Compute normal is checked. (Without normals, the contour is >>>> completely stepped) >>>> b) Contour values are the same. >>>> >>>> Regards >>>> Philipp >>>> >>>> On 09/19/2014 04:40 PM, Cory Quammen wrote: >>>>> Philipp, >>>>> >>>>> In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? >>>>> >>>>> Also, are the contour values the same between the two versions? >>>>> >>>>> Thanks, >>>>> Cory >>>>> >>>>> On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: >>>>>> Hello everyone, >>>>>> >>>>>> after extensive search I was desperate enough to post on this list: >>>>>> >>>>>> It appears that the surface smoothing algorithm of the contour filter >>>>>> does not work as "aggressive" as in older version (3.14.1 was the last >>>>>> one we found to do so). As an example I prepared this two screenshots, >>>>>> VTK data are scalars on a structured grid (200x100x100), legacy format. >>>>>> (An additional call of the "smooth" filter does not help.) >>>>>> >>>>>> 3.14.1 >>>>>> http://s7.directupload.net/images/140919/euadfvko.png >>>>>> 4.0.RC1 >>>>>> http://s14.directupload.net/images/140919/84y689mi.png >>>>>> >>>>>> Both versions are running with the shipped settings. Since the effect >>>>>> could be reproduced on several workstations, we are wondering whether >>>>>> there has been an (undocumented?) change in the filter mechanism or some >>>>>> option we/setting/data problem we are not aware of. >>>>>> >>>>>> Kind regards and thanks in advance >>>>>> Philipp Engels. >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview From burlen.loring at gmail.com Fri Sep 19 12:24:07 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Fri, 19 Sep 2014 09:24:07 -0700 Subject: [Paraview] proper formatting of 2D data In-Reply-To: <541BD3A9.6010206@energy.lth.se> References: <541BD3A9.6010206@energy.lth.se> Message-ID: <541C58A7.5080108@gmail.com> Hi Robert, Good one! The slice rep uses GPU textures and this behavior looks a bug in the logic that sets up the texture. You should file a bug report. There's an easy workaround. Convert to a positive spacing and adjust the origin accordinigly. The data will the occupy the same region. Here's how your file looks then: --8<-- # vtk DataFile Version 2.0 testing ASCII DATASET STRUCTURED_POINTS DIMENSIONS 3 4 1 ORIGIN 0.0 -2.25 0.0 SPACING 0.5 0.75 1.0 POINT_DATA 12 SCALARS test float LOOKUP_TABLE default 0.0 1.0 2.0 1.0 2.0 3.0 2.0 3.0 4.0 3.0 4.0 5.0 -->8-- Burlen On 09/18/2014 11:56 PM, Robert-Zoltan Szasz wrote: > Hi, > > I tried to visualize 2D structured point data when I observed a > strange behavior. If the spacing in Y direction is negative, the data > is flipped upside-down in 'Slice' representation mode but shown > properly as a 'Surface' representation. Tried in v. 4.0.1 and 4.2rc1 > on Linux 64 bit. Here is a small VTK file to test: > > --8<-- > # vtk DataFile Version 2.0 > testing > ASCII > DATASET STRUCTURED_POINTS > DIMENSIONS 3 4 1 > ORIGIN 0.0 0.0 0.0 > SPACING 0.5 -0.75 1.0 > POINT_DATA 12 > SCALARS test float > LOOKUP_TABLE default > 0.0 > 1.0 > 2.0 > 1.0 > 2.0 > 3.0 > 2.0 > 3.0 > 4.0 > 3.0 > 4.0 > 5.0 > -->8-- > > I am wondering if I missed something when formatting the file or if > you have any ideas how to avoid this behavior? > Thanks, > Robert > From wascott at sandia.gov Fri Sep 19 13:01:33 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 19 Sep 2014 17:01:33 +0000 Subject: [Paraview] [EXTERNAL] proper formatting of 2D data In-Reply-To: <541BD3A9.6010206@energy.lth.se> References: <541BD3A9.6010206@energy.lth.se> Message-ID: Robert, I am pretty sure that is a bug. Mind writing up a bug report? Also, your description and example file are great. Be sure to include them in the bug. Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Robert-Zoltan Szasz Sent: Friday, September 19, 2014 12:57 AM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] proper formatting of 2D data Hi, I tried to visualize 2D structured point data when I observed a strange behavior. If the spacing in Y direction is negative, the data is flipped upside-down in 'Slice' representation mode but shown properly as a 'Surface' representation. Tried in v. 4.0.1 and 4.2rc1 on Linux 64 bit. Here is a small VTK file to test: --8<-- # vtk DataFile Version 2.0 testing ASCII DATASET STRUCTURED_POINTS DIMENSIONS 3 4 1 ORIGIN 0.0 0.0 0.0 SPACING 0.5 -0.75 1.0 POINT_DATA 12 SCALARS test float LOOKUP_TABLE default 0.0 1.0 2.0 1.0 2.0 3.0 2.0 3.0 4.0 3.0 4.0 5.0 -->8-- I am wondering if I missed something when formatting the file or if you have any ideas how to avoid this behavior? Thanks, Robert -- Robert-Zoltan Szasz Div.Fluid Mechanics Tel: +46-46-222 0480 Dept. Energy Sciences, LTH Fax: +46-46-222 4717 Lund University _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From cory.quammen at kitware.com Fri Sep 19 13:15:44 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 19 Sep 2014 13:15:44 -0400 Subject: [Paraview] [EXTERNAL] proper formatting of 2D data In-Reply-To: References: <541BD3A9.6010206@energy.lth.se> Message-ID: Is negative spacing really supported in VTK/ParaView? The VTK File Formats document for legacy data (http://www.vtk.org/VTK/img/file-formats.pdf) states under the description of the structured points data: "The data spacing sx, sy, sz must be greater than 0." This is apparently not enforced in the reader, however. Thanks, Cory On Fri, Sep 19, 2014 at 1:01 PM, Scott, W Alan wrote: > Robert, > I am pretty sure that is a bug. Mind writing up a bug report? Also, your description and example file are great. Be sure to include them in the bug. > > Alan > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Robert-Zoltan Szasz > Sent: Friday, September 19, 2014 12:57 AM > To: paraview at paraview.org > Subject: [EXTERNAL] [Paraview] proper formatting of 2D data > > Hi, > > I tried to visualize 2D structured point data when I observed a strange behavior. If the spacing in Y direction is negative, the data is flipped upside-down in 'Slice' representation mode but shown properly as a 'Surface' representation. Tried in v. 4.0.1 and 4.2rc1 on Linux 64 bit. > Here is a small VTK file to test: > > --8<-- > # vtk DataFile Version 2.0 > testing > ASCII > DATASET STRUCTURED_POINTS > DIMENSIONS 3 4 1 > ORIGIN 0.0 0.0 0.0 > SPACING 0.5 -0.75 1.0 > POINT_DATA 12 > SCALARS test float > LOOKUP_TABLE default > 0.0 > 1.0 > 2.0 > 1.0 > 2.0 > 3.0 > 2.0 > 3.0 > 4.0 > 3.0 > 4.0 > 5.0 > -->8-- > > I am wondering if I missed something when formatting the file or if you have any ideas how to avoid this behavior? > Thanks, > Robert > > -- > Robert-Zoltan Szasz > Div.Fluid Mechanics Tel: +46-46-222 0480 > Dept. Energy Sciences, LTH Fax: +46-46-222 4717 > Lund University > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From cory.quammen at kitware.com Fri Sep 19 13:17:54 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 19 Sep 2014 13:17:54 -0400 Subject: [Paraview] 3D contour smoothness In-Reply-To: <541C5519.505@googlemail.com> References: <541C3CBC.9080302@googlemail.com> <541C422F.70508@googlemail.com> <541C48F2.2090704@googlemail.com> <541C5519.505@googlemail.com> Message-ID: Just a little more info on this. The problem starts with 3.98. On Fri, Sep 19, 2014 at 12:08 PM, Philipp E. wrote: > Sorry Cory, > > you are right. The cell number is the same. > > Regards > Philipp > > > Am 19.09.2014 um 17:46 schrieb Cory Quammen: >> Philipp, >> >> I can confirm what you see with a pre 4.2 version of ParaView. >> However, the number of produced cells is the same. >> >> I will try to track down why this changed. >> >> Thanks, >> Cory >> >> On Fri, Sep 19, 2014 at 11:17 AM, Philipp E wrote: >>> Hi Cory >>> >>> I managed to compress the data set to a fair size and attached it to >>> this mail. The data set is pressure, contour value is 0.55. >>> >>> By looking again at the data (contour -> information), I just found that >>> the old version (3.14.1) uses 148432 cells , while the the new one >>> employs 75232 cells. Hope that helps. >>> >>> Kind regards >>> Philipp >>> >>> Errata: I meant 4.2.0RC1 in the previous mails. >>> >>> On 09/19/2014 04:59 PM, Cory Quammen wrote: >>>> Phillipp, >>>> >>>> Do you have a data set similar to the one you've shown that you can share? >>>> >>>> Thanks, >>>> Cory >>>> >>>> On Fri, Sep 19, 2014 at 10:48 AM, Philipp E wrote: >>>>> Hi Cory, >>>>> >>>>> thank you for your fast feedback. >>>>> >>>>> a) Compute normal is checked. (Without normals, the contour is >>>>> completely stepped) >>>>> b) Contour values are the same. >>>>> >>>>> Regards >>>>> Philipp >>>>> >>>>> On 09/19/2014 04:40 PM, Cory Quammen wrote: >>>>>> Philipp, >>>>>> >>>>>> In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? >>>>>> >>>>>> Also, are the contour values the same between the two versions? >>>>>> >>>>>> Thanks, >>>>>> Cory >>>>>> >>>>>> On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: >>>>>>> Hello everyone, >>>>>>> >>>>>>> after extensive search I was desperate enough to post on this list: >>>>>>> >>>>>>> It appears that the surface smoothing algorithm of the contour filter >>>>>>> does not work as "aggressive" as in older version (3.14.1 was the last >>>>>>> one we found to do so). As an example I prepared this two screenshots, >>>>>>> VTK data are scalars on a structured grid (200x100x100), legacy format. >>>>>>> (An additional call of the "smooth" filter does not help.) >>>>>>> >>>>>>> 3.14.1 >>>>>>> http://s7.directupload.net/images/140919/euadfvko.png >>>>>>> 4.0.RC1 >>>>>>> http://s14.directupload.net/images/140919/84y689mi.png >>>>>>> >>>>>>> Both versions are running with the shipped settings. Since the effect >>>>>>> could be reproduced on several workstations, we are wondering whether >>>>>>> there has been an (undocumented?) change in the filter mechanism or some >>>>>>> option we/setting/data problem we are not aware of. >>>>>>> >>>>>>> Kind regards and thanks in advance >>>>>>> Philipp Engels. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview > From christian.richter at ovgu.de Fri Sep 19 15:38:10 2014 From: christian.richter at ovgu.de (Richter, Christian, Dipl.-Ing.) Date: Fri, 19 Sep 2014 19:38:10 +0000 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: , Message-ID: <16D48FA760BFDC4BB2107C47BAF755D136FF0772@chronos2.ads.uni-magdeburg.de> We use this simple python script for file series (stl, vtk, particle data in LAMMPS text- or binary format (with our own reader)). Feel free to use this as a starting point: https://github.com/richti83/ParaView_Reader_for_LIGGGHTS/blob/master/python_macros/update.py The if-condition in line 68 should be more generous, but for now it works and you can add every source (plane,line,...) there which does not support file series. To use it: first build your tree in the pipeline browser by opening file series (need to have more than one file bc. otherwise the reader_core is used inside PV instead of PV_FileSeriesReader). Than, while the simulation is running, just hit update macro button to reload the file series and jump to the last available timestep. Best, Christian. ________________________________________ Von: ParaView [paraview-bounces at paraview.org]" im Auftrag von "Utkarsh Ayachit [utkarsh.ayachit at kitware.com] Gesendet: Donnerstag, 18. September 2014 14:46 An: Zenker, Dr. Matthias Cc: paraview at paraview.org Betreff: Re: [Paraview] How to simply "Reload" a data file Sorry, didn't get around to it yet. Over this weekend is more likely, since I am tracking down some last minute issues with 4.2 right now. Utkarsh On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias wrote: > Hi Utkarsh, > > any news regarding a reload data function (see below)? > > Matthias > >> -----Urspr?ngliche Nachricht----- >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Gesendet: Montag, 15. September 2014 16:50 >> An: Zenker, Dr. Matthias >> Cc: Cory Quammen; paraview at paraview.org >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> Ah. since it's a file series, it would not work the way Cory is suggesting. I'll see >> if I can cook up a Python script that can make this possible for now. We're >> putting this on the roadmap for the next release (I know I've said that a few >> times in the past :) ). >> >> Utkarsh >> >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias >> wrote: >> > Normally I load a time series, either a series of vtu files or a time collection >> (pvd file containing the vtu file names with asociated timestamps). During >> the simulation, new files are added to the series. So it would be nice to watch >> the simulation going on by reloading from time to time. >> > >> > Matthias >> > >> >> -----Urspr?ngliche Nachricht----- >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> Gesendet: Montag, 15. September 2014 16:28 >> >> An: Zenker, Dr. Matthias >> >> Cc: Cory Quammen; paraview at paraview.org >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> I suspect will not work with vtu. To understand this better, what is >> >> that which is changing that you need to reload the file? Are you >> >> loading a file series or a single file? >> >> >> >> Utkarsh >> >> >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias >> >> wrote: >> >> > Hi Cory, >> >> > >> >> > I use the reader for vtu format and pvd (vtu time collection). I >> >> > tried to >> >> modify the xml as follows: >> >> > >> >> > >> >> > >> >> > >> >> > > >> base_proxyname="VTUReader" class="vtuReader"> >> >> > > >> panel_widget="command_button"/> >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > But I cannot even load it as plugin. Presumably there are special >> >> > keyword to >> >> use for the name of the original reader. Is there a documentation >> >> where I can find more information on that topic? >> >> > >> >> > Thanks, >> >> > >> >> > Matthias >> >> > >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] >> >> >> Gesendet: Montag, 15. September 2014 15:05 >> >> >> An: Zenker, Dr. Matthias >> >> >> Cc: paraview at paraview.org >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> Matthias, >> >> >> >> >> >> The method I suggested requires modifying ParaView's source code, >> >> >> so it won't work for a binary distribution. >> >> >> >> >> >> As for the XML method, did you try to load an Xdmf file through >> >> >> what should be the new "Xdmf Reader (Refresh button)" reader? If >> >> >> you are loading a different type of file, this plugin will have no >> >> >> effect because it provides a Refresh button only for the Xdmf >> >> >> reader. You could modify the XML for other reader types, though. >> >> >> >> >> >> Thanks, >> >> >> Cory >> >> >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias >> >> >> wrote: >> >> >> > Hi, >> >> >> > >> >> >> > I wanted to try the "Reload" button which presumably can be >> >> >> > created by >> >> >> one of the methods outlined below. But I am maybe too naive or am >> >> >> missing >> >> >> something: I have a Windoze binary distribution of ParaView 4.0.1. >> >> >> I did not find the file indicated by Cory, and copying the xml >> >> >> code given by S?bastien into a file and loading that as plugin had >> >> >> no effect >> >> visible to me. >> >> >> > >> >> >> > What am I missing here? >> >> >> > >> >> >> > Thank you, >> >> >> > >> >> >> > Matthias >> >> >> > >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- >> >> >> >> bounces at paraview.org] Im Auftrag von paraview- >> >> request at paraview.org >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 >> >> >> >> An: paraview at paraview.org >> >> >> >> Betreff: Reload a file >> >> >> >> >> >> >> >> Send ParaView mailing list submissions to >> >> >> >> paraview at paraview.org >> >> >> >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> or, via email, send a message with subject or body 'help' to >> >> >> >> paraview-request at paraview.org >> >> >> >> >> >> >> >> You can reach the person managing the list at >> >> >> >> paraview-owner at paraview.org >> >> >> >> >> >> >> >> When replying, please edit your Subject line so it is more >> >> >> >> specific than >> >> >> "Re: >> >> >> >> Contents of ParaView digest..." >> >> >> >> >> >> >> >> >> >> >> >> Today's Topics: >> >> >> >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory Quammen) >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------- >> >> >> >> --- >> >> >> >> --- >> >> >> >> - >> >> >> >> >> >> >> >> Message: 1 >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 >> >> >> >> From: Cory Quammen >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> To: Sebastien Jourdain >> >> >> >> Cc: Michael Jackson , ParaView >> >> >> >> >> >> >> >> Message-ID: >> >> >> >> > >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> >> >> >> >> For what it's worth, I just experimented with adding the line >> >> >> >> >> >> >> >> > >> >> >> panel_widget="command_button"/> >> >> >> >> >> >> >> >> to the CSV reader and XDMF reader in >> >> >> >> >> >> >> >> >> >> >> >> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers >> >> >> >> .xml >> >> >> >> >> >> >> >> The Refresh button appears among the other property widgets and >> >> >> >> it indeed reloads the data set. >> >> >> >> >> >> >> >> I would happily add this to all the readers and submit a patch >> >> >> >> to gerrit if it would be received well by the core ParaView >> developers. >> >> >> >> >> >> >> >> Thanks, >> >> >> >> Cory >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain >> >> >> >> wrote: >> >> >> >> > BTW that's the correct XML for you, just need to create a >> >> >> >> > file with that in and load it as a plugin and you will have your >> "Refresh" >> >> button. >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > > >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" >> >> >> >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> >> >> >> >> > > >> >> >> > panel_widget="command_button"/> >> >> >> >> > >> >> >> >> > > >> >> >> > file_description="Xdmf Reader (Refresh button)" /> >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain >> >> >> >> > wrote: >> >> >> >> >> >> >> >> >> >> Another approach could be a python macro that invalidate the >> >> >> >> >> "active/selected' proxy in the pipeline, but that one will >> >> >> >> >> require the usage of ParaView in built-in mode. >> >> >> >> >> >> >> >> >> >> If interested I can try to write the corresponding python code... >> >> >> >> >> >> >> >> >> >> Seb >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain >> >> >> >> >> wrote: >> >> >> >> >>> >> >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... >> >> >> >> >>> No code involved... >> >> >> >> >>> >> >> >> >> >>> In fact, just having the XML that I wrote in a file extend >> >> >> >> >>> the UI with a button to refresh the reader should be enough. >> >> >> >> >>> Need to figure out why the reader factory did not catch up >> >> >> >> >>> the >> >> hint. >> >> >> >> >>> >> >> >> >> >>> That should be the only thing that you would need. >> >> >> >> >>> >> >> >> >> >>> Seb >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson >> >> >> >> >>> wrote: >> >> >> >> >>>> >> >> >> >> >>>> I was hoping that ParaView just had something built in. I >> >> >> >> >>>> would rather not have to create a plugin and distribute >> >> >> >> >>>> that along side my own software and to keep up on builds >> >> >> >> >>>> for all the various OS's and all of that. i tried that for >> >> >> >> >>>> a while and I just could not >> >> >> keep up. >> >> >> >> >>>> >> >> >> >> >>>> So either I am the only person who has asked for this or >> >> >> >> >>>> there is some over riding reason in the design of ParView >> >> >> >> >>>> why this type of functionality is not in ParaView. >> >> >> >> >>>> >> >> >> >> >>>> Thanks >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> _ >> >> >> >> >>>> Mike Jackson Principal Software Engineer >> >> >> >> >>>> BlueQuartz Software Dayton, Ohio >> >> >> >> >>>> mike.jackson at bluequartz.net www.bluequartz.net >> >> >> >> >>>> >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu >> >> >> >> >>>> >> >> >> >> >>>> wrote: >> >> >> >> >>>> >> >> >> >> >>>> > hi you can try the approach of S?bastien >> >> >> >> >>>> > >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html >> >> >> >> >>>> > >> >> >> >> >>>> > I haven't tested yet. >> >> >> >> >>>> > >> >> >> >> >>>> > You can save the code as a macro, so you will have a button. >> >> >> >> >>>> > >> >> >> >> >>>> > Felipe >> >> >> >> >>>> > >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : >> >> >> >> >>>> >> Is there button where I can simply reload a data file >> >> >> >> >>>> >> that was read in a pipeline? >> >> >> >> >>>> >> >> >> >> >> >>>> >> We have a workflow where we process data into a file >> >> >> >> >>>> >> and view it in ParaView. it is becoming tedious to blow >> >> >> >> >>>> >> away the entire pipeline just to reload the new data. >> >> >> >> >>>> >> >> >> >> >> >>>> >> I know about state files but this still requires the >> >> >> >> >>>> >> user to go to the File->Load State... " menu and then >> >> >> >> >>>> >> select a state >> >> file. >> >> >> >> >>>> >> I would like to just select the data file in the >> >> >> >> >>>> >> Pipeline browser (XDMF File reader for us), and just >> >> >> >> >>>> >> click some button that just reloads data from the file. >> >> >> >> >>>> >> >> >> >> >> >>>> >> Or am I just missing something? I am using ParaView >> >> >> >> >>>> >> 3.98.1. I have to admit I have not tried any of the >> >> >> >> >>>> >> 4.0.RC* >> >> downloads. >> >> >> >> >>>> >> >> >> >> >> >>>> >> Thanks >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> _________________________________________________________ >> >> >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net >> >> >> >> >>>> >> BlueQuartz Software www.bluequartz.net >> >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio >> >> >> >> >>>> >> >> _______________________________________________ >> >> >> >> >>>> >> Powered by www.kitware.com >> >> >> >> >>>> >> >> >> >> >> >>>> >> Visit other Kitware open-source projects at >> >> >> >> >>>> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >>>> >> >> >> >> >> >>>> >> Please keep messages on-topic and check the ParaView >> >> >> >> >>>> >> Wiki >> >> at: >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView >> >> >> >> >>>> >> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: >> >> >> >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >>>> > >> >> >> >> >>>> > >> >> >> >> >>>> > -- >> >> >> >> >>>> > Felipe Bordeu Weldt >> >> >> >> >>>> > Ing?nieur de Recherche >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 >> >> >> >> >>>> > Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS 6183 >> >> >> >> >>>> > ?cole Centrale Nantes >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >>>> > >> >> >> >> >>>> > >> _______________________________________________ >> >> >> >> >>>> > Powered by www.kitware.com >> >> >> >> >>>> > >> >> >> >> >>>> > Visit other Kitware open-source projects at >> >> >> >> >>>> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >>>> > >> >> >> >> >>>> > Please keep messages on-topic and check the ParaView >> >> >> >> >>>> > Wiki >> >> at: >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView >> >> >> >> >>>> > >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >>>> >> >> >> >> >>>> _______________________________________________ >> >> >> >> >>>> Powered by www.kitware.com >> >> >> >> >>>> >> >> >> >> >>>> Visit other Kitware open-source projects at >> >> >> >> >>>> http://www.kitware.com/opensource/opensource.html >> >> >> >> >>>> >> >> >> >> >>>> Please keep messages on-topic and check the ParaView Wiki >> at: >> >> >> >> >>>> http://paraview.org/Wiki/ParaView >> >> >> >> >>>> >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: >> >> >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >> >> >> >> >> > >> >> >> >> > >> >> >> >> > _______________________________________________ >> >> >> >> > Powered by www.kitware.com >> >> >> >> > >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> > >> >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> > >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> Cory Quammen >> >> >> >> Research Associate >> >> >> >> Department of Computer Science >> >> >> >> The University of North Carolina at Chapel Hill >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------ >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> Powered by www.kitware.com >> >> >> >> >> >> >> >> Visit other Kitware open-source projects at >> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> >> >> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 >> >> >> >> ***************************************** >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> __________________________________________________________ >> >> >> ___________ >> >> >> > ERBE Elektromedizin GmbH >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> > >> >> >> > _______________________________________________ >> >> >> > Powered by www.kitware.com >> >> >> > >> >> >> > Visit other Kitware open-source projects at >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> > >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> > >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> > >> >> > >> >> > >> >> >> __________________________________________________________ >> >> ___________ >> >> > ERBE Elektromedizin GmbH >> >> > Firmensitz: 72072 Tuebingen >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> > Registergericht: Stuttgart HRB 380137 >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> > http://paraview.org/Wiki/ParaView >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> > >> > >> __________________________________________________________ >> ___________ >> > ERBE Elektromedizin GmbH >> > Firmensitz: 72072 Tuebingen >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> > Registergericht: Stuttgart HRB 380137 >> > > > > _____________________________________________________________________ > ERBE Elektromedizin GmbH > Firmensitz: 72072 Tuebingen > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > Registergericht: Stuttgart HRB 380137 > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From pradeep.kumar.jha at gmail.com Fri Sep 19 17:14:09 2014 From: pradeep.kumar.jha at gmail.com (Pradeep Jha) Date: Fri, 19 Sep 2014 17:14:09 -0400 Subject: [Paraview] Plotting Nek5000 output data Message-ID: I am outputting my data from Nek5000 in the case.fld* format. I am creating a case.nek5000 file which reads like: ==== filetemplate: case.fld%02d firsttimestep: 1 numtimesteps: 2 ==== When I am opening this *nek5000 file in Paraview 4.1, I don't see the contours. In Visit I see them (images attached). Any tips? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: paraview.jpg Type: image/jpeg Size: 63379 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: visit.jpg Type: image/jpeg Size: 30769 bytes Desc: not available URL: From wascott at sandia.gov Fri Sep 19 17:21:34 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 19 Sep 2014 21:21:34 +0000 Subject: [Paraview] [EXTERNAL] Plotting Nek5000 output data In-Reply-To: References: Message-ID: <0723b7ea9c72409c8114ceb8aa75dc43@ES05AMSNLNT.srn.sandia.gov> Can you post the data here? Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Pradeep Jha Sent: Friday, September 19, 2014 3:14 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Plotting Nek5000 output data I am outputting my data from Nek5000 in the case.fld* format. I am creating a case.nek5000 file which reads like: ==== filetemplate: case.fld%02d firsttimestep: 1 numtimesteps: 2 ==== When I am opening this *nek5000 file in Paraview 4.1, I don't see the contours. In Visit I see them (images attached). Any tips? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkxls23 at gmail.com Sat Sep 20 07:38:55 2014 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Sat, 20 Sep 2014 14:38:55 +0300 Subject: [Paraview] Odd behavior of XDMF files with 3DCORECTMesh Message-ID: <541D674F.2020208@gmail.com> Hi, I lately started to write my data in HDF5/XDMF files. This works so far very well for unstructured data using TopologyType="Mixed" and Polygon cells, but I have some trouble with structured grids. I attached a very simple VTK file, which is correctly visualized in ParaView. More precisely, the DIMENSIONS keyword specifies the dimensions in X Y Z direction and the SPACING and POINT_DATA keywords are specified accordingly. Opening the VTK file in ParaView and exporting the data as XDMF leads to an XDMF file with dimensions and the spacing is in reverse order (Z Y X), where seemingly the data is written in the same order as in the VTK file. Is this intended or a bug? Just to note, the data from the ParaView-created XDMF and the original VTK file are displayed consistently. When I however manually converter the VTK to a XDMF file with dimensions, spacing and data specified as in the VTK file, I get a completely wrong representation in ParaView. Seemingly, in the "Topology" element the "Dimensions" keyword specifies the dimensions in Z Y X direction, which I thing is rather odd. The whole thing gets then completely messed up when specifying the data. Am I doing something wrong when manually creating the XDMF file or is this a bug? Best regards, Armin -- Armin Wehrfritz, Dipl.-Ing. (M.Sc.) Aalto University, School of Engineering Department of Energy Technology PO Box 14300 FI-00076 Aalto, Finland -------------- next part -------------- # vtk DataFile Version 2.0 testing ASCII DATASET STRUCTURED_POINTS DIMENSIONS 3 4 1 ORIGIN 0.0 0.0 0.0 SPACING 0.5 0.5 1.0 POINT_DATA 12 SCALARS test_scalar float LOOKUP_TABLE default 0.0 1.0 2.0 1.0 2.0 3.0 2.0 3.0 4.0 3.0 4.0 5.0 VECTORS test_vector float 0.0 0.0 0.0 1.0 1.0 1.0 2.0 2.0 2.0 1.0 1.0 1.0 2.0 2.0 2.0 3.0 3.0 3.0 2.0 2.0 2.0 3.0 3.0 3.0 4.0 4.0 4.0 3.0 3.0 3.0 4.0 4.0 4.0 5.0 5.0 5.0 -------------- next part -------------- A non-text attachment was scrubbed... Name: test_manual.xmf Type: audio/x-xmf Size: 1349 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test_paraview.xmf Type: audio/x-xmf Size: 1073 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Sun Sep 21 10:17:21 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 21 Sep 2014 10:17:21 -0400 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Matthias, Attached is the Python script that reloads a file-series. You can import this as a macro or just run it from the Python shell. In either case, ensure that the reader to reload is the active reader. Utkarsh On Thu, Sep 18, 2014 at 9:34 AM, Zenker, Dr. Matthias wrote: > OK - but don't forget that the weekend is also there to have some free time... ;) > > Matthias > >> -----Urspr?ngliche Nachricht----- >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Gesendet: Donnerstag, 18. September 2014 14:46 >> An: Zenker, Dr. Matthias >> Cc: Cory Quammen; paraview at paraview.org >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> Sorry, didn't get around to it yet. Over this weekend is more likely, since I am >> tracking down some last minute issues with 4.2 right now. >> >> Utkarsh >> >> On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias >> wrote: >> > Hi Utkarsh, >> > >> > any news regarding a reload data function (see below)? >> > >> > Matthias >> > >> >> -----Urspr?ngliche Nachricht----- >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> Gesendet: Montag, 15. September 2014 16:50 >> >> An: Zenker, Dr. Matthias >> >> Cc: Cory Quammen; paraview at paraview.org >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> Ah. since it's a file series, it would not work the way Cory is >> >> suggesting. I'll see if I can cook up a Python script that can make >> >> this possible for now. We're putting this on the roadmap for the next >> >> release (I know I've said that a few times in the past :) ). >> >> >> >> Utkarsh >> >> >> >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias >> >> wrote: >> >> > Normally I load a time series, either a series of vtu files or a >> >> > time collection >> >> (pvd file containing the vtu file names with asociated timestamps). >> >> During the simulation, new files are added to the series. So it would >> >> be nice to watch the simulation going on by reloading from time to time. >> >> > >> >> > Matthias >> >> > >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> >> Gesendet: Montag, 15. September 2014 16:28 >> >> >> An: Zenker, Dr. Matthias >> >> >> Cc: Cory Quammen; paraview at paraview.org >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> I suspect will not work with vtu. To understand this better, what >> >> >> is that which is changing that you need to reload the file? Are >> >> >> you loading a file series or a single file? >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias >> >> >> wrote: >> >> >> > Hi Cory, >> >> >> > >> >> >> > I use the reader for vtu format and pvd (vtu time collection). I >> >> >> > tried to >> >> >> modify the xml as follows: >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > > >> >> base_proxyname="VTUReader" class="vtuReader"> >> >> >> > > >> >> panel_widget="command_button"/> >> >> >> > >> >> >> > > >> >> > file_description="vtu Reader >> >> >> (Refresh button)" /> >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > But I cannot even load it as plugin. Presumably there are >> >> >> > special keyword to >> >> >> use for the name of the original reader. Is there a documentation >> >> >> where I can find more information on that topic? >> >> >> > >> >> >> > Thanks, >> >> >> > >> >> >> > Matthias >> >> >> > >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] >> >> >> >> Gesendet: Montag, 15. September 2014 15:05 >> >> >> >> An: Zenker, Dr. Matthias >> >> >> >> Cc: paraview at paraview.org >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> >> >> Matthias, >> >> >> >> >> >> >> >> The method I suggested requires modifying ParaView's source >> >> >> >> code, so it won't work for a binary distribution. >> >> >> >> >> >> >> >> As for the XML method, did you try to load an Xdmf file through >> >> >> >> what should be the new "Xdmf Reader (Refresh button)" reader? >> >> >> >> If you are loading a different type of file, this plugin will >> >> >> >> have no effect because it provides a Refresh button only for >> >> >> >> the Xdmf reader. You could modify the XML for other reader types, >> though. >> >> >> >> >> >> >> >> Thanks, >> >> >> >> Cory >> >> >> >> >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias >> >> >> >> wrote: >> >> >> >> > Hi, >> >> >> >> > >> >> >> >> > I wanted to try the "Reload" button which presumably can be >> >> >> >> > created by >> >> >> >> one of the methods outlined below. But I am maybe too naive or >> >> >> >> am missing >> >> >> >> something: I have a Windoze binary distribution of ParaView 4.0.1. >> >> >> >> I did not find the file indicated by Cory, and copying the xml >> >> >> >> code given by S?bastien into a file and loading that as plugin >> >> >> >> had no effect >> >> >> visible to me. >> >> >> >> > >> >> >> >> > What am I missing here? >> >> >> >> > >> >> >> >> > Thank you, >> >> >> >> > >> >> >> >> > Matthias >> >> >> >> > >> >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- >> >> >> >> >> bounces at paraview.org] Im Auftrag von paraview- >> >> >> request at paraview.org >> >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 >> >> >> >> >> An: paraview at paraview.org >> >> >> >> >> Betreff: Reload a file >> >> >> >> >> >> >> >> >> >> Send ParaView mailing list submissions to >> >> >> >> >> paraview at paraview.org >> >> >> >> >> >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> or, via email, send a message with subject or body 'help' to >> >> >> >> >> paraview-request at paraview.org >> >> >> >> >> >> >> >> >> >> You can reach the person managing the list at >> >> >> >> >> paraview-owner at paraview.org >> >> >> >> >> >> >> >> >> >> When replying, please edit your Subject line so it is more >> >> >> >> >> specific than >> >> >> >> "Re: >> >> >> >> >> Contents of ParaView digest..." >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Today's Topics: >> >> >> >> >> >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory Quammen) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------ >> >> >> >> >> --- >> >> >> >> >> --- >> >> >> >> >> --- >> >> >> >> >> - >> >> >> >> >> >> >> >> >> >> Message: 1 >> >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 >> >> >> >> >> From: Cory Quammen >> >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> To: Sebastien Jourdain >> >> >> >> >> Cc: Michael Jackson , >> ParaView >> >> >> >> >> >> >> >> >> >> Message-ID: >> >> >> >> >> > >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> >> >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> >> >> >> >> >> >> For what it's worth, I just experimented with adding the >> >> >> >> >> line >> >> >> >> >> >> >> >> >> >> > >> >> >> >> panel_widget="command_button"/> >> >> >> >> >> >> >> >> >> >> to the CSV reader and XDMF reader in >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers >> >> >> >> >> .xml >> >> >> >> >> >> >> >> >> >> The Refresh button appears among the other property widgets >> >> >> >> >> and it indeed reloads the data set. >> >> >> >> >> >> >> >> >> >> I would happily add this to all the readers and submit a >> >> >> >> >> patch to gerrit if it would be received well by the core >> >> >> >> >> ParaView >> >> developers. >> >> >> >> >> >> >> >> >> >> Thanks, >> >> >> >> >> Cory >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain >> >> >> >> >> wrote: >> >> >> >> >> > BTW that's the correct XML for you, just need to create a >> >> >> >> >> > file with that in and load it as a plugin and you will >> >> >> >> >> > have your >> >> "Refresh" >> >> >> button. >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > > >> >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" >> >> >> >> >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> >> >> >> >> >> > > >> >> >> >> > panel_widget="command_button"/> >> >> >> >> >> > >> >> >> >> >> > > >> >> >> >> > file_description="Xdmf Reader (Refresh button)" /> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain >> >> >> >> >> > wrote: >> >> >> >> >> >> >> >> >> >> >> >> Another approach could be a python macro that invalidate >> >> >> >> >> >> the "active/selected' proxy in the pipeline, but that one >> >> >> >> >> >> will require the usage of ParaView in built-in mode. >> >> >> >> >> >> >> >> >> >> >> >> If interested I can try to write the corresponding python >> code... >> >> >> >> >> >> >> >> >> >> >> >> Seb >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain >> >> >> >> >> >> wrote: >> >> >> >> >> >>> >> >> >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... >> >> >> >> >> >>> No code involved... >> >> >> >> >> >>> >> >> >> >> >> >>> In fact, just having the XML that I wrote in a file >> >> >> >> >> >>> extend the UI with a button to refresh the reader should be >> enough. >> >> >> >> >> >>> Need to figure out why the reader factory did not catch >> >> >> >> >> >>> up the >> >> >> hint. >> >> >> >> >> >>> >> >> >> >> >> >>> That should be the only thing that you would need. >> >> >> >> >> >>> >> >> >> >> >> >>> Seb >> >> >> >> >> >>> >> >> >> >> >> >>> >> >> >> >> >> >>> >> >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson >> >> >> >> >> >>> wrote: >> >> >> >> >> >>>> >> >> >> >> >> >>>> I was hoping that ParaView just had something built in. >> >> >> >> >> >>>> I would rather not have to create a plugin and >> >> >> >> >> >>>> distribute that along side my own software and to keep >> >> >> >> >> >>>> up on builds for all the various OS's and all of that. >> >> >> >> >> >>>> i tried that for a while and I just could not >> >> >> >> keep up. >> >> >> >> >> >>>> >> >> >> >> >> >>>> So either I am the only person who has asked for this >> >> >> >> >> >>>> or there is some over riding reason in the design of >> >> >> >> >> >>>> ParView why this type of functionality is not in ParaView. >> >> >> >> >> >>>> >> >> >> >> >> >>>> Thanks >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> >> _ >> >> >> >> >> >>>> Mike Jackson Principal Software Engineer >> >> >> >> >> >>>> BlueQuartz Software Dayton, Ohio >> >> >> >> >> >>>> mike.jackson at bluequartz.net www.bluequartz.net >> >> >> >> >> >>>> >> >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu >> >> >> >> >> >>>> >> >> >> >> >> >>>> wrote: >> >> >> >> >> >>>> >> >> >> >> >> >>>> > hi you can try the approach of S?bastien >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.html >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > I haven't tested yet. >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > You can save the code as a macro, so you will have a >> button. >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > Felipe >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : >> >> >> >> >> >>>> >> Is there button where I can simply reload a data >> >> >> >> >> >>>> >> file that was read in a pipeline? >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> >> We have a workflow where we process data into a file >> >> >> >> >> >>>> >> and view it in ParaView. it is becoming tedious to >> >> >> >> >> >>>> >> blow away the entire pipeline just to reload the new >> data. >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> >> I know about state files but this still requires >> >> >> >> >> >>>> >> the user to go to the File->Load State... " menu and >> >> >> >> >> >>>> >> then select a state >> >> >> file. >> >> >> >> >> >>>> >> I would like to just select the data file in the >> >> >> >> >> >>>> >> Pipeline browser (XDMF File reader for us), and just >> >> >> >> >> >>>> >> click some button that just reloads data from the file. >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> >> Or am I just missing something? I am using ParaView >> >> >> >> >> >>>> >> 3.98.1. I have to admit I have not tried any of the >> >> >> >> >> >>>> >> 4.0.RC* >> >> >> downloads. >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> >> Thanks >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _________________________________________________________ >> >> >> >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net >> >> >> >> >> >>>> >> BlueQuartz Software www.bluequartz.net >> >> >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio >> >> >> >> >> >>>> >> >> >> _______________________________________________ >> >> >> >> >> >>>> >> Powered by www.kitware.com >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> >> Visit other Kitware open-source projects at >> >> >> >> >> >>>> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> >> Please keep messages on-topic and check the ParaView >> >> >> >> >> >>>> >> Wiki >> >> >> at: >> >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > -- >> >> >> >> >> >>>> > Felipe Bordeu Weldt >> >> >> >> >> >>>> > Ing?nieur de Recherche >> >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 06 >> >> >> >> >> >>>> > Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR CNRS >> >> >> >> >> >>>> > 6183 ?cole Centrale Nantes >> >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE >> >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > >> >> _______________________________________________ >> >> >> >> >> >>>> > Powered by www.kitware.com >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > Visit other Kitware open-source projects at >> >> >> >> >> >>>> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > Please keep messages on-topic and check the ParaView >> >> >> >> >> >>>> > Wiki >> >> >> at: >> >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >>>> >> >> >> >> >> >>>> >> _______________________________________________ >> >> >> >> >> >>>> Powered by www.kitware.com >> >> >> >> >> >>>> >> >> >> >> >> >>>> Visit other Kitware open-source projects at >> >> >> >> >> >>>> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >>>> >> >> >> >> >> >>>> Please keep messages on-topic and check the ParaView >> >> >> >> >> >>>> Wiki >> >> at: >> >> >> >> >> >>>> http://paraview.org/Wiki/ParaView >> >> >> >> >> >>>> >> >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >>> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > _______________________________________________ >> >> >> >> >> > Powered by www.kitware.com >> >> >> >> >> > >> >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >> > >> >> >> >> >> > Please keep messages on-topic and check the ParaView Wiki >> at: >> >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> >> > >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> Cory Quammen >> >> >> >> >> Research Associate >> >> >> >> >> Department of Computer Science The University of North >> >> >> >> >> Carolina at Chapel Hill >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------ >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> Powered by www.kitware.com >> >> >> >> >> >> >> >> >> >> Visit other Kitware open-source projects at >> >> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> >> >> >> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 >> >> >> >> >> ***************************************** >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> ___________ >> >> >> >> > ERBE Elektromedizin GmbH >> >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> >> > >> >> >> >> > _______________________________________________ >> >> >> >> > Powered by www.kitware.com >> >> >> >> > >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> > >> >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> > >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> __________________________________________________________ >> >> >> ___________ >> >> >> > ERBE Elektromedizin GmbH >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> > >> >> >> > _______________________________________________ >> >> >> > Powered by www.kitware.com >> >> >> > >> >> >> > Visit other Kitware open-source projects at >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> > >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> > >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> > >> >> > >> >> > >> >> >> __________________________________________________________ >> >> ___________ >> >> > ERBE Elektromedizin GmbH >> >> > Firmensitz: 72072 Tuebingen >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> > Registergericht: Stuttgart HRB 380137 >> >> > >> > >> > >> > >> __________________________________________________________ >> ___________ >> > ERBE Elektromedizin GmbH >> > Firmensitz: 72072 Tuebingen >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> > Registergericht: Stuttgart HRB 380137 >> > > > > _____________________________________________________________________ > ERBE Elektromedizin GmbH > Firmensitz: 72072 Tuebingen > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > Registergericht: Stuttgart HRB 380137 > -------------- next part -------------- A non-text attachment was scrubbed... Name: RefreshReader.py Type: text/x-python-script Size: 3013 bytes Desc: not available URL: From furutaka.kazuyoshi at jaea.go.jp Mon Sep 22 00:27:11 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Mon, 22 Sep 2014 13:27:11 +0900 (JST) Subject: [Paraview] seg.fault when reading VRML files twice In-Reply-To: References: <20140905.072750.413866329.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <20140922.132711.78509409.furutaka.kazuyoshi@jaea.go.jp> Dear Shawn, Thanks for your fix! Confirmed on the following environments that ParaView does NOT seg.faults when it reads VRML file again : * windows ("4.2.0-RC1-105-g58ab368 32-bit", nightly-build binary ) * linux ("4.2.0-RC1-120-g2ea0acd 32-bit", built by myself from git master which includes commits upto 2ea0acdeb5062ecff9b6e56a26b72c66dd0eb69d at Sat Sep 20 09:15:03 2014 -0400 Thanks again. Kazuyoshi From: Shawn Waldon Subject: Re: [Paraview] seg.fault when reading VRML files twice Date: Fri, 19 Sep 2014 10:40:38 -0400 > Hi Kazuyoshi, > > The fix has been merged into the main branch of ParaView and should be > available in nightly builds as of today. > > -Shawn -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From sartoret at unive.it Mon Sep 22 02:53:12 2014 From: sartoret at unive.it (Flavio Sartoretto) Date: Mon, 22 Sep 2014 08:53:12 +0200 Subject: [Paraview] View 3D cloud of points Message-ID: I must display a 3D cloud of points inside a unit cube. After being unsuccessful, I found ----------------------------------------------------------------------- Subject:Re: [Paraview] Question about showing a few nodes/points using vtk xml [image: permalink] From:Moreland, Kenneth (kmo... @sandia.gov)Date:Jul 6, 2010 9:22:44 amList:org.paraview.paraview By default, ParaView draws cells, not points. (You've found one exception where selected points are drawn.) If you want to see points in general, you will need to create "vertex" cells. One way to do that is to run your data through the glyph filter and select the "2D Glyph" and then "Vected" glyph types. etc. -------------------------------------------------------------------------- I run Delaunay 3D on my cloud. I exported into a vtk file. Reimported. Only point on cube faces are displayed, no one inside Any hint? Best -- Prof. Flavio Sartoretto, Universita` Ca' Foscari Venezia Dipartimento di Scienze Ambientali, Informatica e Statistica Via Torino 155 - 30172 Mestre VE (Italy) Voice: +39.041.234.8411, +39.049.827.1331 / Fax: +39.041.234.8419, +39.049.827.1333 WEB: http://www.dsi.unive.it/~sartoret Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert-Zoltan.Szasz at energy.lth.se Mon Sep 22 03:27:00 2014 From: Robert-Zoltan.Szasz at energy.lth.se (Szasz Robert) Date: Mon, 22 Sep 2014 09:27:00 +0200 Subject: [Paraview] proper formatting of 2D data In-Reply-To: <541C58A7.5080108@gmail.com> References: <541BD3A9.6010206@energy.lth.se> <541C58A7.5080108@gmail.com> Message-ID: <541FCF44.6030505@energy.lth.se> Thank you Burlen, I just filed a bug report this morning. I will also adjust the export routines to avoid negative spacings for the time being. Robert On 2014-09-19 18:24, Burlen Loring wrote: > Hi Robert, > > Good one! The slice rep uses GPU textures and this behavior looks a > bug in the logic that sets up the texture. You should file a bug report. > > There's an easy workaround. Convert to a positive spacing and adjust > the origin accordinigly. The data will the occupy the same region. > Here's how your file looks then: > > --8<-- > # vtk DataFile Version 2.0 > testing > ASCII > DATASET STRUCTURED_POINTS > DIMENSIONS 3 4 1 > ORIGIN 0.0 -2.25 0.0 > SPACING 0.5 0.75 1.0 > POINT_DATA 12 > SCALARS test float > LOOKUP_TABLE default > 0.0 > 1.0 > 2.0 > 1.0 > 2.0 > 3.0 > 2.0 > 3.0 > 4.0 > 3.0 > 4.0 > 5.0 > -->8-- > > Burlen > > On 09/18/2014 11:56 PM, Robert-Zoltan Szasz wrote: >> Hi, >> >> I tried to visualize 2D structured point data when I observed a >> strange behavior. If the spacing in Y direction is negative, the data >> is flipped upside-down in 'Slice' representation mode but shown >> properly as a 'Surface' representation. Tried in v. 4.0.1 and 4.2rc1 >> on Linux 64 bit. Here is a small VTK file to test: >> >> --8<-- >> # vtk DataFile Version 2.0 >> testing >> ASCII >> DATASET STRUCTURED_POINTS >> DIMENSIONS 3 4 1 >> ORIGIN 0.0 0.0 0.0 >> SPACING 0.5 -0.75 1.0 >> POINT_DATA 12 >> SCALARS test float >> LOOKUP_TABLE default >> 0.0 >> 1.0 >> 2.0 >> 1.0 >> 2.0 >> 3.0 >> 2.0 >> 3.0 >> 4.0 >> 3.0 >> 4.0 >> 5.0 >> -->8-- >> >> I am wondering if I missed something when formatting the file or if >> you have any ideas how to avoid this behavior? >> Thanks, >> Robert >> > > > From Robert-Zoltan.Szasz at energy.lth.se Mon Sep 22 03:27:46 2014 From: Robert-Zoltan.Szasz at energy.lth.se (Szasz Robert) Date: Mon, 22 Sep 2014 09:27:46 +0200 Subject: [Paraview] View 3D cloud of points In-Reply-To: References: Message-ID: <541FCF72.30904@energy.lth.se> Hi Flavio, I use the POLYDATA format to save the data and then visualize it with glyphs (usually spheres, but if you just need points I suppose small cubes would work as well). The header looks like: --8<-- # vtk DataFile Version 2.0 Some comment ASCII DATASET POLYDATA POINTS 2 float 0.782901 0.067979 0.784717 1.387618 0.188356 0.766874 POINT_DATA 2 VECTORS u float -0.089651 0.002427 0.992657 0.098818 0.015530 0.877940 --8<-- Robert On 2014-09-22 08:53, Flavio Sartoretto wrote: > I must display a 3D cloud of points inside a unit cube. > After being unsuccessful, I found > ----------------------------------------------------------------------- > Subject: Re: [Paraview] Question about showing a few nodes/points > using vtk xml > permalink > From: Moreland, Kenneth (kmo... at sandia.gov ) > Date: Jul 6, 2010 9:22:44 am > List: org.paraview.paraview > > By default, ParaView draws cells, not points. (You've found one > exception where > selected points are drawn.) If you want to see points in general, you > will need > to create "vertex" cells. One way to do that is to run your data > through the > glyph filter and select the "2D Glyph" and then "Vected" glyph types. > > etc. > > -------------------------------------------------------------------------- > > I run Delaunay 3D on my cloud. I exported into a vtk file. > > Reimported. > > Only point on cube faces are displayed, no one inside > > > Any hint? > > Best > > > -- > Prof. Flavio Sartoretto, Universita` Ca' Foscari Venezia > Dipartimento di Scienze Ambientali, Informatica e Statistica > Via Torino 155 - 30172 Mestre VE (Italy) > Voice: +39.041.234.8411, +39.049.827.1331 / Fax: +39.041.234.8419, > +39.049.827.1333 > WEB: http://www.dsi.unive.it/~sartoret > > Please avoid sending me Word or PowerPoint attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matthias.Zenker at erbe-med.com Mon Sep 22 05:16:01 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Mon, 22 Sep 2014 09:16:01 +0000 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Hi Utkarsh, thank you for the Python script. Having never used Python scripts in ParaView before, I have difficulties to run it. When I open the Python shell and try to launch the script with the "Run Script" button, I get an error message saying: Traceback (most recent call last): File "", line 19, in NameError: name 'GetActiveSource' is not defined I use ParaView 4.0.1 under Windows 7. I have added the lib directory of ParaView to my path, as it says in the ParaView Python documentation. Is there anything else I need to do to run the script? When I load it as a macro, the corresponding button appears, but when I click on it, nothing seems to happen. I have tested it with a pvd time collection where I have commented out the last timestep. When I loaded it, all timesteps but the last one were visible. Then I removed the comment marks around in the last timestep in the pvd file and lauched the Refresh Reader macro. I would expect that now the last timestep in the pvd would be visible, but it wasn't. You said that the reader to reload should be the active reader. How do I see which reader is the active one? The pvd collection was highlighted when I activated the macro. Do I have to do something else? Thanks, Matthias > -----Urspr?ngliche Nachricht----- > Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Gesendet: Sonntag, 21. September 2014 16:17 > An: Zenker, Dr. Matthias > Cc: Cory Quammen; paraview at paraview.org > Betreff: Re: [Paraview] How to simply "Reload" a data file > > Matthias, > > Attached is the Python script that reloads a file-series. You can import this as > a macro or just run it from the Python shell. In either case, ensure that the > reader to reload is the active reader. > > Utkarsh > > > On Thu, Sep 18, 2014 at 9:34 AM, Zenker, Dr. Matthias > wrote: > > OK - but don't forget that the weekend is also there to have some free > > time... ;) > > > > Matthias > > > >> -----Urspr?ngliche Nachricht----- > >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> Gesendet: Donnerstag, 18. September 2014 14:46 > >> An: Zenker, Dr. Matthias > >> Cc: Cory Quammen; paraview at paraview.org > >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> > >> Sorry, didn't get around to it yet. Over this weekend is more likely, > >> since I am tracking down some last minute issues with 4.2 right now. > >> > >> Utkarsh > >> > >> On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias > >> wrote: > >> > Hi Utkarsh, > >> > > >> > any news regarding a reload data function (see below)? > >> > > >> > Matthias > >> > > >> >> -----Urspr?ngliche Nachricht----- > >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> Gesendet: Montag, 15. September 2014 16:50 > >> >> An: Zenker, Dr. Matthias > >> >> Cc: Cory Quammen; paraview at paraview.org > >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> > >> >> Ah. since it's a file series, it would not work the way Cory is > >> >> suggesting. I'll see if I can cook up a Python script that can > >> >> make this possible for now. We're putting this on the roadmap for > >> >> the next release (I know I've said that a few times in the past :) ). > >> >> > >> >> Utkarsh > >> >> > >> >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias > >> >> wrote: > >> >> > Normally I load a time series, either a series of vtu files or a > >> >> > time collection > >> >> (pvd file containing the vtu file names with asociated timestamps). > >> >> During the simulation, new files are added to the series. So it > >> >> would be nice to watch the simulation going on by reloading from time > to time. > >> >> > > >> >> > Matthias > >> >> > > >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> >> Gesendet: Montag, 15. September 2014 16:28 > >> >> >> An: Zenker, Dr. Matthias > >> >> >> Cc: Cory Quammen; paraview at paraview.org > >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> >> > >> >> >> I suspect will not work with vtu. To understand this better, > >> >> >> what is that which is changing that you need to reload the > >> >> >> file? Are you loading a file series or a single file? > >> >> >> > >> >> >> Utkarsh > >> >> >> > >> >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias > >> >> >> wrote: > >> >> >> > Hi Cory, > >> >> >> > > >> >> >> > I use the reader for vtu format and pvd (vtu time > >> >> >> > collection). I tried to > >> >> >> modify the xml as follows: > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > name="VTUrefresh" > >> >> >> > base_proxygroup="sources" > >> >> >> base_proxyname="VTUReader" class="vtuReader"> > >> >> >> > >> >> >> panel_widget="command_button"/> > >> >> >> > > >> >> >> > >> >> >> > file_description="vtu Reader > >> >> >> (Refresh button)" /> > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > But I cannot even load it as plugin. Presumably there are > >> >> >> > special keyword to > >> >> >> use for the name of the original reader. Is there a > >> >> >> documentation where I can find more information on that topic? > >> >> >> > > >> >> >> > Thanks, > >> >> >> > > >> >> >> > Matthias > >> >> >> > > >> >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] > >> >> >> >> Gesendet: Montag, 15. September 2014 15:05 > >> >> >> >> An: Zenker, Dr. Matthias > >> >> >> >> Cc: paraview at paraview.org > >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> >> >> > >> >> >> >> Matthias, > >> >> >> >> > >> >> >> >> The method I suggested requires modifying ParaView's source > >> >> >> >> code, so it won't work for a binary distribution. > >> >> >> >> > >> >> >> >> As for the XML method, did you try to load an Xdmf file > >> >> >> >> through what should be the new "Xdmf Reader (Refresh > button)" reader? > >> >> >> >> If you are loading a different type of file, this plugin > >> >> >> >> will have no effect because it provides a Refresh button > >> >> >> >> only for the Xdmf reader. You could modify the XML for other > >> >> >> >> reader types, > >> though. > >> >> >> >> > >> >> >> >> Thanks, > >> >> >> >> Cory > >> >> >> >> > >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias > >> >> >> >> wrote: > >> >> >> >> > Hi, > >> >> >> >> > > >> >> >> >> > I wanted to try the "Reload" button which presumably can > >> >> >> >> > be created by > >> >> >> >> one of the methods outlined below. But I am maybe too naive > >> >> >> >> or am missing > >> >> >> >> something: I have a Windoze binary distribution of ParaView > 4.0.1. > >> >> >> >> I did not find the file indicated by Cory, and copying the > >> >> >> >> xml code given by S?bastien into a file and loading that as > >> >> >> >> plugin had no effect > >> >> >> visible to me. > >> >> >> >> > > >> >> >> >> > What am I missing here? > >> >> >> >> > > >> >> >> >> > Thank you, > >> >> >> >> > > >> >> >> >> > Matthias > >> >> >> >> > > >> >> >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- > >> >> >> >> >> bounces at paraview.org] Im Auftrag von paraview- > >> >> >> request at paraview.org > >> >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 > >> >> >> >> >> An: paraview at paraview.org > >> >> >> >> >> Betreff: Reload a file > >> >> >> >> >> > >> >> >> >> >> Send ParaView mailing list submissions to > >> >> >> >> >> paraview at paraview.org > >> >> >> >> >> > >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit > >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> or, via email, send a message with subject or body 'help' to > >> >> >> >> >> paraview-request at paraview.org > >> >> >> >> >> > >> >> >> >> >> You can reach the person managing the list at > >> >> >> >> >> paraview-owner at paraview.org > >> >> >> >> >> > >> >> >> >> >> When replying, please edit your Subject line so it is > >> >> >> >> >> more specific than > >> >> >> >> "Re: > >> >> >> >> >> Contents of ParaView digest..." > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> Today's Topics: > >> >> >> >> >> > >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory > >> >> >> >> >> Quammen) > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> --------------------------------------------------------- > >> >> >> >> >> --- > >> >> >> >> >> --- > >> >> >> >> >> --- > >> >> >> >> >> --- > >> >> >> >> >> - > >> >> >> >> >> > >> >> >> >> >> Message: 1 > >> >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 > >> >> >> >> >> From: Cory Quammen > >> >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data > >> >> >> >> >> file > >> >> >> >> >> To: Sebastien Jourdain > >> >> >> >> >> Cc: Michael Jackson , > >> ParaView > >> >> >> >> >> > >> >> >> >> >> Message-ID: > >> >> >> >> >> >> >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> > >> >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 > >> >> >> >> >> > >> >> >> >> >> For what it's worth, I just experimented with adding the > >> >> >> >> >> line > >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> panel_widget="command_button"/> > >> >> >> >> >> > >> >> >> >> >> to the CSV reader and XDMF reader in > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers > >> >> >> >> >> .xml > >> >> >> >> >> > >> >> >> >> >> The Refresh button appears among the other property > >> >> >> >> >> widgets and it indeed reloads the data set. > >> >> >> >> >> > >> >> >> >> >> I would happily add this to all the readers and submit a > >> >> >> >> >> patch to gerrit if it would be received well by the core > >> >> >> >> >> ParaView > >> >> developers. > >> >> >> >> >> > >> >> >> >> >> Thanks, > >> >> >> >> >> Cory > >> >> >> >> >> > >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain > >> >> >> >> >> wrote: > >> >> >> >> >> > BTW that's the correct XML for you, just need to create > >> >> >> >> >> > a file with that in and load it as a plugin and you > >> >> >> >> >> > will have your > >> >> "Refresh" > >> >> >> button. > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > >> >> >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" > >> >> >> >> >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> > >> >> >> >> >> > >> >> >> >> >> > panel_widget="command_button"/> > >> >> >> >> >> > > >> >> >> >> >> > >> >> >> >> >> > file_description="Xdmf Reader (Refresh button)" /> > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain > >> >> >> >> >> > wrote: > >> >> >> >> >> >> > >> >> >> >> >> >> Another approach could be a python macro that > >> >> >> >> >> >> invalidate the "active/selected' proxy in the > >> >> >> >> >> >> pipeline, but that one will require the usage of ParaView > in built-in mode. > >> >> >> >> >> >> > >> >> >> >> >> >> If interested I can try to write the corresponding > >> >> >> >> >> >> python > >> code... > >> >> >> >> >> >> > >> >> >> >> >> >> Seb > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain > >> >> >> >> >> >> wrote: > >> >> >> >> >> >>> > >> >> >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... > >> >> >> >> >> >>> No code involved... > >> >> >> >> >> >>> > >> >> >> >> >> >>> In fact, just having the XML that I wrote in a file > >> >> >> >> >> >>> extend the UI with a button to refresh the reader > >> >> >> >> >> >>> should be > >> enough. > >> >> >> >> >> >>> Need to figure out why the reader factory did not > >> >> >> >> >> >>> catch up the > >> >> >> hint. > >> >> >> >> >> >>> > >> >> >> >> >> >>> That should be the only thing that you would need. > >> >> >> >> >> >>> > >> >> >> >> >> >>> Seb > >> >> >> >> >> >>> > >> >> >> >> >> >>> > >> >> >> >> >> >>> > >> >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson > >> >> >> >> >> >>> wrote: > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> I was hoping that ParaView just had something built in. > >> >> >> >> >> >>>> I would rather not have to create a plugin and > >> >> >> >> >> >>>> distribute that along side my own software and to > >> >> >> >> >> >>>> keep up on builds for all the various OS's and all of that. > >> >> >> >> >> >>>> i tried that for a while and I just could not > >> >> >> >> keep up. > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> So either I am the only person who has asked for > >> >> >> >> >> >>>> this or there is some over riding reason in the > >> >> >> >> >> >>>> design of ParView why this type of functionality is not in > ParaView. > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> Thanks > >> >> >> >> >> >>>> > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> >> >> _ > >> >> >> >> >> >>>> Mike Jackson Principal Software Engineer > >> >> >> >> >> >>>> BlueQuartz Software Dayton, Ohio > >> >> >> >> >> >>>> mike.jackson at bluequartz.net > www.bluequartz.net > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> wrote: > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > hi you can try the approach of S?bastien > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.h > >> >> >> >> >> >>>> > tml > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > I haven't tested yet. > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > You can save the code as a macro, so you will have > >> >> >> >> >> >>>> > a > >> button. > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > Felipe > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : > >> >> >> >> >> >>>> >> Is there button where I can simply reload a data > >> >> >> >> >> >>>> >> file that was read in a pipeline? > >> >> >> >> >> >>>> >> > >> >> >> >> >> >>>> >> We have a workflow where we process data into a > >> >> >> >> >> >>>> >> file and view it in ParaView. it is becoming > >> >> >> >> >> >>>> >> tedious to blow away the entire pipeline just to > >> >> >> >> >> >>>> >> reload the new > >> data. > >> >> >> >> >> >>>> >> > >> >> >> >> >> >>>> >> I know about state files but this still requires > >> >> >> >> >> >>>> >> the user to go to the File->Load State... " menu > >> >> >> >> >> >>>> >> and then select a state > >> >> >> file. > >> >> >> >> >> >>>> >> I would like to just select the data file in the > >> >> >> >> >> >>>> >> Pipeline browser (XDMF File reader for us), and > >> >> >> >> >> >>>> >> just click some button that just reloads data from > the file. > >> >> >> >> >> >>>> >> > >> >> >> >> >> >>>> >> Or am I just missing something? I am using > >> >> >> >> >> >>>> >> ParaView 3.98.1. I have to admit I have not tried > >> >> >> >> >> >>>> >> any of the > >> >> >> >> >> >>>> >> 4.0.RC* > >> >> >> downloads. > >> >> >> >> >> >>>> >> > >> >> >> >> >> >>>> >> Thanks > >> >> >> >> >> >>>> >> > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > _________________________________________________________ > >> >> >> >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net > >> >> >> >> >> >>>> >> BlueQuartz Software www.bluequartz.net > >> >> >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio > >> >> >> >> >> >>>> >> > >> >> _______________________________________________ > >> >> >> >> >> >>>> >> Powered by www.kitware.com > >> >> >> >> >> >>>> >> > >> >> >> >> >> >>>> >> Visit other Kitware open-source projects at > >> >> >> >> >> >>>> >> > >> http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >>>> >> > >> >> >> >> >> >>>> >> Please keep messages on-topic and check the > >> >> >> >> >> >>>> >> ParaView Wiki > >> >> >> at: > >> >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView > >> >> >> >> >> >>>> >> > >> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >>>> >> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > -- > >> >> >> >> >> >>>> > Felipe Bordeu Weldt Ing?nieur de Recherche > >> >> >> >> >> >>>> > ------------------------------------- > >> >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 > >> >> >> >> >> >>>> > 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR > >> >> >> >> >> >>>> > CNRS > >> >> >> >> >> >>>> > 6183 ?cole Centrale Nantes > >> >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE > >> >> >> >> >> >>>> > ------------------------------------- > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > > >> >> _______________________________________________ > >> >> >> >> >> >>>> > Powered by www.kitware.com > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > Visit other Kitware open-source projects at > >> >> >> >> >> >>>> > > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > Please keep messages on-topic and check the > >> >> >> >> >> >>>> > ParaView Wiki > >> >> >> at: > >> >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView > >> >> >> >> >> >>>> > > >> >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > >> _______________________________________________ > >> >> >> >> >> >>>> Powered by www.kitware.com > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> Visit other Kitware open-source projects at > >> >> >> >> >> >>>> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> Please keep messages on-topic and check the ParaView > >> >> >> >> >> >>>> Wiki > >> >> at: > >> >> >> >> >> >>>> http://paraview.org/Wiki/ParaView > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >>> > >> >> >> >> >> >>> > >> >> >> >> >> >> > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > _______________________________________________ > >> >> >> >> >> > Powered by www.kitware.com > >> >> >> >> >> > > >> >> >> >> >> > Visit other Kitware open-source projects at > >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> > > >> >> >> >> >> > Please keep messages on-topic and check the ParaView > >> >> >> >> >> > Wiki > >> at: > >> >> >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> >> >> > > >> >> >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> > > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> -- > >> >> >> >> >> Cory Quammen > >> >> >> >> >> Research Associate > >> >> >> >> >> Department of Computer Science The University of North > >> >> >> >> >> Carolina at Chapel Hill > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> ------------------------------ > >> >> >> >> >> > >> >> >> >> >> > _______________________________________________ > >> >> >> >> >> Powered by www.kitware.com > >> >> >> >> >> > >> >> >> >> >> Visit other Kitware open-source projects at > >> >> >> >> >> http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> > >> >> >> >> >> Please keep messages on-topic and check the ParaView Wiki > at: > >> >> >> >> >> http://paraview.org/Wiki/ParaView > >> >> >> >> >> > >> >> >> >> >> Follow this link to subscribe/unsubscribe: > >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 > >> >> >> >> >> ***************************************** > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> >> ___________ > >> >> >> >> > ERBE Elektromedizin GmbH > >> >> >> >> > Firmensitz: 72072 Tuebingen > >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> >> >> > Registergericht: Stuttgart HRB 380137 > >> >> >> >> > > >> >> >> >> > _______________________________________________ > >> >> >> >> > Powered by www.kitware.com > >> >> >> >> > > >> >> >> >> > Visit other Kitware open-source projects at > >> >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> > > >> >> >> >> > Please keep messages on-topic and check the ParaView Wiki > at: > >> >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> >> > > >> >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> ___________ > >> >> >> > ERBE Elektromedizin GmbH > >> >> >> > Firmensitz: 72072 Tuebingen > >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> >> > Registergericht: Stuttgart HRB 380137 > >> >> >> > > >> >> >> > _______________________________________________ > >> >> >> > Powered by www.kitware.com > >> >> >> > > >> >> >> > Visit other Kitware open-source projects at > >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> > > >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> > > >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> >> > > >> >> > > >> >> > > >> >> > >> > __________________________________________________________ > >> >> ___________ > >> >> > ERBE Elektromedizin GmbH > >> >> > Firmensitz: 72072 Tuebingen > >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> > Registergericht: Stuttgart HRB 380137 > >> >> > > >> > > >> > > >> > > >> > __________________________________________________________ > >> ___________ > >> > ERBE Elektromedizin GmbH > >> > Firmensitz: 72072 Tuebingen > >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> > Registergericht: Stuttgart HRB 380137 > >> > > > > > > > > __________________________________________________________ > ___________ > > ERBE Elektromedizin GmbH > > Firmensitz: 72072 Tuebingen > > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > > Registergericht: Stuttgart HRB 380137 > > _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 From utkarsh.ayachit at kitware.com Mon Sep 22 08:23:01 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 22 Sep 2014 08:23:01 -0400 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Can you try the script with 4.2-RC before we try debugging this? Thanks Utkarsh On Mon, Sep 22, 2014 at 5:16 AM, Zenker, Dr. Matthias wrote: > Hi Utkarsh, > > thank you for the Python script. > Having never used Python scripts in ParaView before, I have difficulties to run it. When I open the Python shell and try to launch the script with the "Run Script" button, I get an error message saying: > > Traceback (most recent call last): > File "", line 19, in > NameError: name 'GetActiveSource' is not defined > > I use ParaView 4.0.1 under Windows 7. I have added the lib directory of ParaView to my path, as it says in the ParaView Python documentation. Is there anything else I need to do to run the script? > > When I load it as a macro, the corresponding button appears, but when I click on it, nothing seems to happen. I have tested it with a pvd time collection where I have commented out the last timestep. When I loaded it, all timesteps but the last one were visible. Then I removed the comment marks around in the last timestep in the pvd file and lauched the Refresh Reader macro. I would expect that now the last timestep in the pvd would be visible, but it wasn't. > > You said that the reader to reload should be the active reader. How do I see which reader is the active one? The pvd collection was highlighted when I activated the macro. Do I have to do something else? > > Thanks, > > Matthias > >> -----Urspr?ngliche Nachricht----- >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Gesendet: Sonntag, 21. September 2014 16:17 >> An: Zenker, Dr. Matthias >> Cc: Cory Quammen; paraview at paraview.org >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> Matthias, >> >> Attached is the Python script that reloads a file-series. You can import this as >> a macro or just run it from the Python shell. In either case, ensure that the >> reader to reload is the active reader. >> >> Utkarsh >> >> >> On Thu, Sep 18, 2014 at 9:34 AM, Zenker, Dr. Matthias >> wrote: >> > OK - but don't forget that the weekend is also there to have some free >> > time... ;) >> > >> > Matthias >> > >> >> -----Urspr?ngliche Nachricht----- >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> Gesendet: Donnerstag, 18. September 2014 14:46 >> >> An: Zenker, Dr. Matthias >> >> Cc: Cory Quammen; paraview at paraview.org >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> Sorry, didn't get around to it yet. Over this weekend is more likely, >> >> since I am tracking down some last minute issues with 4.2 right now. >> >> >> >> Utkarsh >> >> >> >> On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias >> >> wrote: >> >> > Hi Utkarsh, >> >> > >> >> > any news regarding a reload data function (see below)? >> >> > >> >> > Matthias >> >> > >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> >> Gesendet: Montag, 15. September 2014 16:50 >> >> >> An: Zenker, Dr. Matthias >> >> >> Cc: Cory Quammen; paraview at paraview.org >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> Ah. since it's a file series, it would not work the way Cory is >> >> >> suggesting. I'll see if I can cook up a Python script that can >> >> >> make this possible for now. We're putting this on the roadmap for >> >> >> the next release (I know I've said that a few times in the past :) ). >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias >> >> >> wrote: >> >> >> > Normally I load a time series, either a series of vtu files or a >> >> >> > time collection >> >> >> (pvd file containing the vtu file names with asociated timestamps). >> >> >> During the simulation, new files are added to the series. So it >> >> >> would be nice to watch the simulation going on by reloading from time >> to time. >> >> >> > >> >> >> > Matthias >> >> >> > >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> >> >> Gesendet: Montag, 15. September 2014 16:28 >> >> >> >> An: Zenker, Dr. Matthias >> >> >> >> Cc: Cory Quammen; paraview at paraview.org >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> >> >> I suspect will not work with vtu. To understand this better, >> >> >> >> what is that which is changing that you need to reload the >> >> >> >> file? Are you loading a file series or a single file? >> >> >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias >> >> >> >> wrote: >> >> >> >> > Hi Cory, >> >> >> >> > >> >> >> >> > I use the reader for vtu format and pvd (vtu time >> >> >> >> > collection). I tried to >> >> >> >> modify the xml as follows: >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > > name="VTUrefresh" >> >> >> >> > base_proxygroup="sources" >> >> >> >> base_proxyname="VTUReader" class="vtuReader"> >> >> >> >> > > >> >> >> panel_widget="command_button"/> >> >> >> >> > >> >> >> >> > > >> >> >> > file_description="vtu Reader >> >> >> >> (Refresh button)" /> >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > But I cannot even load it as plugin. Presumably there are >> >> >> >> > special keyword to >> >> >> >> use for the name of the original reader. Is there a >> >> >> >> documentation where I can find more information on that topic? >> >> >> >> > >> >> >> >> > Thanks, >> >> >> >> > >> >> >> >> > Matthias >> >> >> >> > >> >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] >> >> >> >> >> Gesendet: Montag, 15. September 2014 15:05 >> >> >> >> >> An: Zenker, Dr. Matthias >> >> >> >> >> Cc: paraview at paraview.org >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> >> >> >> >> Matthias, >> >> >> >> >> >> >> >> >> >> The method I suggested requires modifying ParaView's source >> >> >> >> >> code, so it won't work for a binary distribution. >> >> >> >> >> >> >> >> >> >> As for the XML method, did you try to load an Xdmf file >> >> >> >> >> through what should be the new "Xdmf Reader (Refresh >> button)" reader? >> >> >> >> >> If you are loading a different type of file, this plugin >> >> >> >> >> will have no effect because it provides a Refresh button >> >> >> >> >> only for the Xdmf reader. You could modify the XML for other >> >> >> >> >> reader types, >> >> though. >> >> >> >> >> >> >> >> >> >> Thanks, >> >> >> >> >> Cory >> >> >> >> >> >> >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias >> >> >> >> >> wrote: >> >> >> >> >> > Hi, >> >> >> >> >> > >> >> >> >> >> > I wanted to try the "Reload" button which presumably can >> >> >> >> >> > be created by >> >> >> >> >> one of the methods outlined below. But I am maybe too naive >> >> >> >> >> or am missing >> >> >> >> >> something: I have a Windoze binary distribution of ParaView >> 4.0.1. >> >> >> >> >> I did not find the file indicated by Cory, and copying the >> >> >> >> >> xml code given by S?bastien into a file and loading that as >> >> >> >> >> plugin had no effect >> >> >> >> visible to me. >> >> >> >> >> > >> >> >> >> >> > What am I missing here? >> >> >> >> >> > >> >> >> >> >> > Thank you, >> >> >> >> >> > >> >> >> >> >> > Matthias >> >> >> >> >> > >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- >> >> >> >> >> >> bounces at paraview.org] Im Auftrag von paraview- >> >> >> >> request at paraview.org >> >> >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 >> >> >> >> >> >> An: paraview at paraview.org >> >> >> >> >> >> Betreff: Reload a file >> >> >> >> >> >> >> >> >> >> >> >> Send ParaView mailing list submissions to >> >> >> >> >> >> paraview at paraview.org >> >> >> >> >> >> >> >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> or, via email, send a message with subject or body 'help' to >> >> >> >> >> >> paraview-request at paraview.org >> >> >> >> >> >> >> >> >> >> >> >> You can reach the person managing the list at >> >> >> >> >> >> paraview-owner at paraview.org >> >> >> >> >> >> >> >> >> >> >> >> When replying, please edit your Subject line so it is >> >> >> >> >> >> more specific than >> >> >> >> >> "Re: >> >> >> >> >> >> Contents of ParaView digest..." >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Today's Topics: >> >> >> >> >> >> >> >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory >> >> >> >> >> >> Quammen) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------- >> >> >> >> >> >> --- >> >> >> >> >> >> --- >> >> >> >> >> >> --- >> >> >> >> >> >> --- >> >> >> >> >> >> - >> >> >> >> >> >> >> >> >> >> >> >> Message: 1 >> >> >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 >> >> >> >> >> >> From: Cory Quammen >> >> >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data >> >> >> >> >> >> file >> >> >> >> >> >> To: Sebastien Jourdain >> >> >> >> >> >> Cc: Michael Jackson , >> >> ParaView >> >> >> >> >> >> >> >> >> >> >> >> Message-ID: >> >> >> >> >> >> > >> >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> >> >> >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> >> >> >> >> >> >> >> >> For what it's worth, I just experimented with adding the >> >> >> >> >> >> line >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> panel_widget="command_button"/> >> >> >> >> >> >> >> >> >> >> >> >> to the CSV reader and XDMF reader in >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers >> >> >> >> >> >> .xml >> >> >> >> >> >> >> >> >> >> >> >> The Refresh button appears among the other property >> >> >> >> >> >> widgets and it indeed reloads the data set. >> >> >> >> >> >> >> >> >> >> >> >> I would happily add this to all the readers and submit a >> >> >> >> >> >> patch to gerrit if it would be received well by the core >> >> >> >> >> >> ParaView >> >> >> developers. >> >> >> >> >> >> >> >> >> >> >> >> Thanks, >> >> >> >> >> >> Cory >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain >> >> >> >> >> >> wrote: >> >> >> >> >> >> > BTW that's the correct XML for you, just need to create >> >> >> >> >> >> > a file with that in and load it as a plugin and you >> >> >> >> >> >> > will have your >> >> >> "Refresh" >> >> >> >> button. >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > > >> >> >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" >> >> >> >> >> >> > base_proxyname="XdmfReader" class="vtkXdmfReader"> >> >> >> >> >> >> > > >> >> >> >> >> > panel_widget="command_button"/> >> >> >> >> >> >> > >> >> >> >> >> >> > > >> >> >> >> >> > file_description="Xdmf Reader (Refresh button)" /> >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain >> >> >> >> >> >> > wrote: >> >> >> >> >> >> >> >> >> >> >> >> >> >> Another approach could be a python macro that >> >> >> >> >> >> >> invalidate the "active/selected' proxy in the >> >> >> >> >> >> >> pipeline, but that one will require the usage of ParaView >> in built-in mode. >> >> >> >> >> >> >> >> >> >> >> >> >> >> If interested I can try to write the corresponding >> >> >> >> >> >> >> python >> >> code... >> >> >> >> >> >> >> >> >> >> >> >> >> >> Seb >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien Jourdain >> >> >> >> >> >> >> wrote: >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... >> >> >> >> >> >> >>> No code involved... >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> In fact, just having the XML that I wrote in a file >> >> >> >> >> >> >>> extend the UI with a button to refresh the reader >> >> >> >> >> >> >>> should be >> >> enough. >> >> >> >> >> >> >>> Need to figure out why the reader factory did not >> >> >> >> >> >> >>> catch up the >> >> >> >> hint. >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> That should be the only thing that you would need. >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> Seb >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson >> >> >> >> >> >> >>> wrote: >> >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> I was hoping that ParaView just had something built in. >> >> >> >> >> >> >>>> I would rather not have to create a plugin and >> >> >> >> >> >> >>>> distribute that along side my own software and to >> >> >> >> >> >> >>>> keep up on builds for all the various OS's and all of that. >> >> >> >> >> >> >>>> i tried that for a while and I just could not >> >> >> >> >> keep up. >> >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> So either I am the only person who has asked for >> >> >> >> >> >> >>>> this or there is some over riding reason in the >> >> >> >> >> >> >>>> design of ParView why this type of functionality is not in >> ParaView. >> >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> Thanks >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> >> >> _ >> >> >> >> >> >> >>>> Mike Jackson Principal Software Engineer >> >> >> >> >> >> >>>> BlueQuartz Software Dayton, Ohio >> >> >> >> >> >> >>>> mike.jackson at bluequartz.net >> www.bluequartz.net >> >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu >> >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> wrote: >> >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> > hi you can try the approach of S?bastien >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tools.h >> >> >> >> >> >> >>>> > tml >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > I haven't tested yet. >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > You can save the code as a macro, so you will have >> >> >> >> >> >> >>>> > a >> >> button. >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > Felipe >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : >> >> >> >> >> >> >>>> >> Is there button where I can simply reload a data >> >> >> >> >> >> >>>> >> file that was read in a pipeline? >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> >> We have a workflow where we process data into a >> >> >> >> >> >> >>>> >> file and view it in ParaView. it is becoming >> >> >> >> >> >> >>>> >> tedious to blow away the entire pipeline just to >> >> >> >> >> >> >>>> >> reload the new >> >> data. >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> >> I know about state files but this still requires >> >> >> >> >> >> >>>> >> the user to go to the File->Load State... " menu >> >> >> >> >> >> >>>> >> and then select a state >> >> >> >> file. >> >> >> >> >> >> >>>> >> I would like to just select the data file in the >> >> >> >> >> >> >>>> >> Pipeline browser (XDMF File reader for us), and >> >> >> >> >> >> >>>> >> just click some button that just reloads data from >> the file. >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> >> Or am I just missing something? I am using >> >> >> >> >> >> >>>> >> ParaView 3.98.1. I have to admit I have not tried >> >> >> >> >> >> >>>> >> any of the >> >> >> >> >> >> >>>> >> 4.0.RC* >> >> >> >> downloads. >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> >> Thanks >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _________________________________________________________ >> >> >> >> >> >> >>>> >> Mike Jackson mike.jackson at bluequartz.net >> >> >> >> >> >> >>>> >> BlueQuartz Software www.bluequartz.net >> >> >> >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio >> >> >> >> >> >> >>>> >> >> >> >> _______________________________________________ >> >> >> >> >> >> >>>> >> Powered by www.kitware.com >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> >> Visit other Kitware open-source projects at >> >> >> >> >> >> >>>> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> >> Please keep messages on-topic and check the >> >> >> >> >> >> >>>> >> ParaView Wiki >> >> >> >> at: >> >> >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >>>> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > -- >> >> >> >> >> >> >>>> > Felipe Bordeu Weldt Ing?nieur de Recherche >> >> >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 74 >> >> >> >> >> >> >>>> > 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - UMR >> >> >> >> >> >> >>>> > CNRS >> >> >> >> >> >> >>>> > 6183 ?cole Centrale Nantes >> >> >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE >> >> >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > >> >> >> _______________________________________________ >> >> >> >> >> >> >>>> > Powered by www.kitware.com >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > Visit other Kitware open-source projects at >> >> >> >> >> >> >>>> > >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > Please keep messages on-topic and check the >> >> >> >> >> >> >>>> > ParaView Wiki >> >> >> >> at: >> >> >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> >> >> _______________________________________________ >> >> >> >> >> >> >>>> Powered by www.kitware.com >> >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> Visit other Kitware open-source projects at >> >> >> >> >> >> >>>> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> Please keep messages on-topic and check the ParaView >> >> >> >> >> >> >>>> Wiki >> >> >> at: >> >> >> >> >> >> >>>> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >>>> >> >> >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >>>> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> _______________________________________________ >> >> >> >> >> >> > Powered by www.kitware.com >> >> >> >> >> >> > >> >> >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> > >> >> >> >> >> >> > Please keep messages on-topic and check the ParaView >> >> >> >> >> >> > Wiki >> >> at: >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> >> >> > >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> Cory Quammen >> >> >> >> >> >> Research Associate >> >> >> >> >> >> Department of Computer Science The University of North >> >> >> >> >> >> Carolina at Chapel Hill >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------ >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> >> Powered by www.kitware.com >> >> >> >> >> >> >> >> >> >> >> >> Visit other Kitware open-source projects at >> >> >> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >> >> >> >> >> Please keep messages on-topic and check the ParaView Wiki >> at: >> >> >> >> >> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >> >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 >> >> >> >> >> >> ***************************************** >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> >> ___________ >> >> >> >> >> > ERBE Elektromedizin GmbH >> >> >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> >> >> > >> >> >> >> >> > _______________________________________________ >> >> >> >> >> > Powered by www.kitware.com >> >> >> >> >> > >> >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >> > >> >> >> >> >> > Please keep messages on-topic and check the ParaView Wiki >> at: >> >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> >> > >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> ___________ >> >> >> >> > ERBE Elektromedizin GmbH >> >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> >> > >> >> >> >> > _______________________________________________ >> >> >> >> > Powered by www.kitware.com >> >> >> >> > >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> > >> >> >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> > >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> __________________________________________________________ >> >> >> ___________ >> >> >> > ERBE Elektromedizin GmbH >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> > >> >> > >> >> > >> >> > >> >> >> __________________________________________________________ >> >> ___________ >> >> > ERBE Elektromedizin GmbH >> >> > Firmensitz: 72072 Tuebingen >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> > Registergericht: Stuttgart HRB 380137 >> >> > >> > >> > >> > >> __________________________________________________________ >> ___________ >> > ERBE Elektromedizin GmbH >> > Firmensitz: 72072 Tuebingen >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> > Registergericht: Stuttgart HRB 380137 >> > > > > _____________________________________________________________________ > ERBE Elektromedizin GmbH > Firmensitz: 72072 Tuebingen > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > Registergericht: Stuttgart HRB 380137 > From Matthias.Zenker at erbe-med.com Mon Sep 22 10:03:34 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Mon, 22 Sep 2014 14:03:34 +0000 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Done. Unfortunately, the result is the same: Nothing happens when I reload a pvd collection with added timesteps with the macro. On the console, the error message is different: File "", line 61, in RuntimeError: Failed to locate the file listing. Matthias > -----Urspr?ngliche Nachricht----- > Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Gesendet: Montag, 22. September 2014 14:23 > An: Zenker, Dr. Matthias > Cc: Cory Quammen; paraview at paraview.org > Betreff: Re: [Paraview] How to simply "Reload" a data file > > Can you try the script with 4.2-RC before we try debugging this? > > Thanks > Utkarsh > > On Mon, Sep 22, 2014 at 5:16 AM, Zenker, Dr. Matthias > wrote: > > Hi Utkarsh, > > > > thank you for the Python script. > > Having never used Python scripts in ParaView before, I have difficulties to > run it. When I open the Python shell and try to launch the script with the > "Run Script" button, I get an error message saying: > > > > Traceback (most recent call last): > > File "", line 19, in > > NameError: name 'GetActiveSource' is not defined > > > > I use ParaView 4.0.1 under Windows 7. I have added the lib directory of > ParaView to my path, as it says in the ParaView Python documentation. Is > there anything else I need to do to run the script? > > > > When I load it as a macro, the corresponding button appears, but when I > click on it, nothing seems to happen. I have tested it with a pvd time > collection where I have commented out the last timestep. When I loaded it, > all timesteps but the last one were visible. Then I removed the comment > marks around in the last timestep in the pvd file and lauched the Refresh > Reader macro. I would expect that now the last timestep in the pvd would be > visible, but it wasn't. > > > > You said that the reader to reload should be the active reader. How do I > see which reader is the active one? The pvd collection was highlighted when I > activated the macro. Do I have to do something else? > > > > Thanks, > > > > Matthias > > > >> -----Urspr?ngliche Nachricht----- > >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> Gesendet: Sonntag, 21. September 2014 16:17 > >> An: Zenker, Dr. Matthias > >> Cc: Cory Quammen; paraview at paraview.org > >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> > >> Matthias, > >> > >> Attached is the Python script that reloads a file-series. You can > >> import this as a macro or just run it from the Python shell. In > >> either case, ensure that the reader to reload is the active reader. > >> > >> Utkarsh > >> > >> > >> On Thu, Sep 18, 2014 at 9:34 AM, Zenker, Dr. Matthias > >> wrote: > >> > OK - but don't forget that the weekend is also there to have some > >> > free time... ;) > >> > > >> > Matthias > >> > > >> >> -----Urspr?ngliche Nachricht----- > >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> Gesendet: Donnerstag, 18. September 2014 14:46 > >> >> An: Zenker, Dr. Matthias > >> >> Cc: Cory Quammen; paraview at paraview.org > >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> > >> >> Sorry, didn't get around to it yet. Over this weekend is more > >> >> likely, since I am tracking down some last minute issues with 4.2 right > now. > >> >> > >> >> Utkarsh > >> >> > >> >> On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias > >> >> wrote: > >> >> > Hi Utkarsh, > >> >> > > >> >> > any news regarding a reload data function (see below)? > >> >> > > >> >> > Matthias > >> >> > > >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> >> Gesendet: Montag, 15. September 2014 16:50 > >> >> >> An: Zenker, Dr. Matthias > >> >> >> Cc: Cory Quammen; paraview at paraview.org > >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> >> > >> >> >> Ah. since it's a file series, it would not work the way Cory is > >> >> >> suggesting. I'll see if I can cook up a Python script that can > >> >> >> make this possible for now. We're putting this on the roadmap > >> >> >> for the next release (I know I've said that a few times in the past :) > ). > >> >> >> > >> >> >> Utkarsh > >> >> >> > >> >> >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias > >> >> >> wrote: > >> >> >> > Normally I load a time series, either a series of vtu files > >> >> >> > or a time collection > >> >> >> (pvd file containing the vtu file names with asociated timestamps). > >> >> >> During the simulation, new files are added to the series. So it > >> >> >> would be nice to watch the simulation going on by reloading > >> >> >> from time > >> to time. > >> >> >> > > >> >> >> > Matthias > >> >> >> > > >> >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> >> >> Gesendet: Montag, 15. September 2014 16:28 > >> >> >> >> An: Zenker, Dr. Matthias > >> >> >> >> Cc: Cory Quammen; paraview at paraview.org > >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> >> >> > >> >> >> >> I suspect will not work with vtu. To understand this better, > >> >> >> >> what is that which is changing that you need to reload the > >> >> >> >> file? Are you loading a file series or a single file? > >> >> >> >> > >> >> >> >> Utkarsh > >> >> >> >> > >> >> >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias > >> >> >> >> wrote: > >> >> >> >> > Hi Cory, > >> >> >> >> > > >> >> >> >> > I use the reader for vtu format and pvd (vtu time > >> >> >> >> > collection). I tried to > >> >> >> >> modify the xml as follows: > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > >> name="VTUrefresh" > >> >> >> >> > base_proxygroup="sources" > >> >> >> >> base_proxyname="VTUReader" class="vtuReader"> > >> >> >> >> > >> >> >> >> panel_widget="command_button"/> > >> >> >> >> > > >> >> >> >> > >> >> >> >> > file_description="vtu Reader > >> >> >> >> (Refresh button)" /> > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > But I cannot even load it as plugin. Presumably there are > >> >> >> >> > special keyword to > >> >> >> >> use for the name of the original reader. Is there a > >> >> >> >> documentation where I can find more information on that topic? > >> >> >> >> > > >> >> >> >> > Thanks, > >> >> >> >> > > >> >> >> >> > Matthias > >> >> >> >> > > >> >> >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] > >> >> >> >> >> Gesendet: Montag, 15. September 2014 15:05 > >> >> >> >> >> An: Zenker, Dr. Matthias > >> >> >> >> >> Cc: paraview at paraview.org > >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data > >> >> >> >> >> file > >> >> >> >> >> > >> >> >> >> >> Matthias, > >> >> >> >> >> > >> >> >> >> >> The method I suggested requires modifying ParaView's > >> >> >> >> >> source code, so it won't work for a binary distribution. > >> >> >> >> >> > >> >> >> >> >> As for the XML method, did you try to load an Xdmf file > >> >> >> >> >> through what should be the new "Xdmf Reader (Refresh > >> button)" reader? > >> >> >> >> >> If you are loading a different type of file, this plugin > >> >> >> >> >> will have no effect because it provides a Refresh button > >> >> >> >> >> only for the Xdmf reader. You could modify the XML for > >> >> >> >> >> other reader types, > >> >> though. > >> >> >> >> >> > >> >> >> >> >> Thanks, > >> >> >> >> >> Cory > >> >> >> >> >> > >> >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias > >> >> >> >> >> wrote: > >> >> >> >> >> > Hi, > >> >> >> >> >> > > >> >> >> >> >> > I wanted to try the "Reload" button which presumably > >> >> >> >> >> > can be created by > >> >> >> >> >> one of the methods outlined below. But I am maybe too > >> >> >> >> >> naive or am missing > >> >> >> >> >> something: I have a Windoze binary distribution of > >> >> >> >> >> ParaView > >> 4.0.1. > >> >> >> >> >> I did not find the file indicated by Cory, and copying > >> >> >> >> >> the xml code given by S?bastien into a file and loading > >> >> >> >> >> that as plugin had no effect > >> >> >> >> visible to me. > >> >> >> >> >> > > >> >> >> >> >> > What am I missing here? > >> >> >> >> >> > > >> >> >> >> >> > Thank you, > >> >> >> >> >> > > >> >> >> >> >> > Matthias > >> >> >> >> >> > > >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- > >> >> >> >> >> >> bounces at paraview.org] Im Auftrag von paraview- > >> >> >> >> request at paraview.org > >> >> >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 > >> >> >> >> >> >> An: paraview at paraview.org > >> >> >> >> >> >> Betreff: Reload a file > >> >> >> >> >> >> > >> >> >> >> >> >> Send ParaView mailing list submissions to > >> >> >> >> >> >> paraview at paraview.org > >> >> >> >> >> >> > >> >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit > >> >> >> >> >> >> > >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >> or, via email, send a message with subject or body 'help' > to > >> >> >> >> >> >> paraview-request at paraview.org > >> >> >> >> >> >> > >> >> >> >> >> >> You can reach the person managing the list at > >> >> >> >> >> >> paraview-owner at paraview.org > >> >> >> >> >> >> > >> >> >> >> >> >> When replying, please edit your Subject line so it is > >> >> >> >> >> >> more specific than > >> >> >> >> >> "Re: > >> >> >> >> >> >> Contents of ParaView digest..." > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> Today's Topics: > >> >> >> >> >> >> > >> >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory > >> >> >> >> >> >> Quammen) > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> ------------------------------------------------------ > >> >> >> >> >> >> --- > >> >> >> >> >> >> --- > >> >> >> >> >> >> --- > >> >> >> >> >> >> --- > >> >> >> >> >> >> --- > >> >> >> >> >> >> - > >> >> >> >> >> >> > >> >> >> >> >> >> Message: 1 > >> >> >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 > >> >> >> >> >> >> From: Cory Quammen > >> >> >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data > >> >> >> >> >> >> file > >> >> >> >> >> >> To: Sebastien Jourdain > >> >> >> >> >> >> > >> >> >> >> >> >> Cc: Michael Jackson , > >> >> ParaView > >> >> >> >> >> >> > >> >> >> >> >> >> Message-ID: > >> >> >> >> >> >> >> >> >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> > >> >> >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 > >> >> >> >> >> >> > >> >> >> >> >> >> For what it's worth, I just experimented with adding > >> >> >> >> >> >> the line > >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> panel_widget="command_button"/> > >> >> >> >> >> >> > >> >> >> >> >> >> to the CSV reader and XDMF reader in > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers > >> >> >> >> >> >> .xml > >> >> >> >> >> >> > >> >> >> >> >> >> The Refresh button appears among the other property > >> >> >> >> >> >> widgets and it indeed reloads the data set. > >> >> >> >> >> >> > >> >> >> >> >> >> I would happily add this to all the readers and submit > >> >> >> >> >> >> a patch to gerrit if it would be received well by the > >> >> >> >> >> >> core ParaView > >> >> >> developers. > >> >> >> >> >> >> > >> >> >> >> >> >> Thanks, > >> >> >> >> >> >> Cory > >> >> >> >> >> >> > >> >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain > >> >> >> >> >> >> wrote: > >> >> >> >> >> >> > BTW that's the correct XML for you, just need to > >> >> >> >> >> >> > create a file with that in and load it as a plugin > >> >> >> >> >> >> > and you will have your > >> >> >> "Refresh" > >> >> >> >> button. > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > >> >> >> >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" > >> >> >> >> >> >> > base_proxyname="XdmfReader" > class="vtkXdmfReader"> > >> >> >> >> >> >> > >> >> >> >> >> >> > panel_widget="command_button"/> > >> >> >> >> >> >> > > >> >> >> >> >> >> > >> >> >> >> >> >> > file_description="Xdmf Reader (Refresh button)" /> > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain > >> >> >> >> >> >> > wrote: > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Another approach could be a python macro that > >> >> >> >> >> >> >> invalidate the "active/selected' proxy in the > >> >> >> >> >> >> >> pipeline, but that one will require the usage of > >> >> >> >> >> >> >> ParaView > >> in built-in mode. > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> If interested I can try to write the corresponding > >> >> >> >> >> >> >> python > >> >> code... > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Seb > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien > >> >> >> >> >> >> >> Jourdain wrote: > >> >> >> >> >> >> >>> > >> >> >> >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... > >> >> >> >> >> >> >>> No code involved... > >> >> >> >> >> >> >>> > >> >> >> >> >> >> >>> In fact, just having the XML that I wrote in a > >> >> >> >> >> >> >>> file extend the UI with a button to refresh the > >> >> >> >> >> >> >>> reader should be > >> >> enough. > >> >> >> >> >> >> >>> Need to figure out why the reader factory did not > >> >> >> >> >> >> >>> catch up the > >> >> >> >> hint. > >> >> >> >> >> >> >>> > >> >> >> >> >> >> >>> That should be the only thing that you would need. > >> >> >> >> >> >> >>> > >> >> >> >> >> >> >>> Seb > >> >> >> >> >> >> >>> > >> >> >> >> >> >> >>> > >> >> >> >> >> >> >>> > >> >> >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson > >> >> >> >> >> >> >>> wrote: > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> I was hoping that ParaView just had something built > in. > >> >> >> >> >> >> >>>> I would rather not have to create a plugin and > >> >> >> >> >> >> >>>> distribute that along side my own software and to > >> >> >> >> >> >> >>>> keep up on builds for all the various OS's and all of > that. > >> >> >> >> >> >> >>>> i tried that for a while and I just could not > >> >> >> >> >> keep up. > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> So either I am the only person who has asked for > >> >> >> >> >> >> >>>> this or there is some over riding reason in the > >> >> >> >> >> >> >>>> design of ParView why this type of functionality > >> >> >> >> >> >> >>>> is not in > >> ParaView. > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> Thanks > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> >> >> >> _ > >> >> >> >> >> >> >>>> Mike Jackson Principal Software Engineer > >> >> >> >> >> >> >>>> BlueQuartz Software Dayton, Ohio > >> >> >> >> >> >> >>>> mike.jackson at bluequartz.net > >> www.bluequartz.net > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> wrote: > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > hi you can try the approach of S?bastien > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tool > >> >> >> >> >> >> >>>> > s.h > >> >> >> >> >> >> >>>> > tml > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > I haven't tested yet. > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > You can save the code as a macro, so you will > >> >> >> >> >> >> >>>> > have a > >> >> button. > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > Felipe > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : > >> >> >> >> >> >> >>>> >> Is there button where I can simply reload a > >> >> >> >> >> >> >>>> >> data file that was read in a pipeline? > >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >>>> >> We have a workflow where we process data into > >> >> >> >> >> >> >>>> >> a file and view it in ParaView. it is becoming > >> >> >> >> >> >> >>>> >> tedious to blow away the entire pipeline just > >> >> >> >> >> >> >>>> >> to reload the new > >> >> data. > >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >>>> >> I know about state files but this still > >> >> >> >> >> >> >>>> >> requires the user to go to the File->Load > >> >> >> >> >> >> >>>> >> State... " menu and then select a state > >> >> >> >> file. > >> >> >> >> >> >> >>>> >> I would like to just select the data file in > >> >> >> >> >> >> >>>> >> the Pipeline browser (XDMF File reader for > >> >> >> >> >> >> >>>> >> us), and just click some button that just > >> >> >> >> >> >> >>>> >> reloads data from > >> the file. > >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >>>> >> Or am I just missing something? I am using > >> >> >> >> >> >> >>>> >> ParaView 3.98.1. I have to admit I have not > >> >> >> >> >> >> >>>> >> tried any of the > >> >> >> >> >> >> >>>> >> 4.0.RC* > >> >> >> >> downloads. > >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >>>> >> Thanks > >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > _________________________________________________________ > >> >> >> >> >> >> >>>> >> Mike Jackson > mike.jackson at bluequartz.net > >> >> >> >> >> >> >>>> >> BlueQuartz Software > www.bluequartz.net > >> >> >> >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio > >> >> >> >> >> >> >>>> >> > >> >> >> _______________________________________________ > >> >> >> >> >> >> >>>> >> Powered by www.kitware.com > >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >>>> >> Visit other Kitware open-source projects at > >> >> >> >> >> >> >>>> >> > >> >> http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >>>> >> Please keep messages on-topic and check the > >> >> >> >> >> >> >>>> >> ParaView Wiki > >> >> >> >> at: > >> >> >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> >>>> >> > >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > -- > >> >> >> >> >> >> >>>> > Felipe Bordeu Weldt Ing?nieur de Recherche > >> >> >> >> >> >> >>>> > ------------------------------------- > >> >> >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 > >> >> >> >> >> >> >>>> > 74 > >> >> >> >> >> >> >>>> > 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - > >> >> >> >> >> >> >>>> > UMR CNRS > >> >> >> >> >> >> >>>> > 6183 ?cole Centrale Nantes > >> >> >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE > >> >> >> >> >> >> >>>> > ------------------------------------- > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > > >> >> >> _______________________________________________ > >> >> >> >> >> >> >>>> > Powered by www.kitware.com > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > Visit other Kitware open-source projects at > >> >> >> >> >> >> >>>> > > >> http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > Please keep messages on-topic and check the > >> >> >> >> >> >> >>>> > ParaView Wiki > >> >> >> >> at: > >> >> >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paravi > >> >> >> >> >> >> >>>> > ew > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> > >> >> _______________________________________________ > >> >> >> >> >> >> >>>> Powered by www.kitware.com > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> Visit other Kitware open-source projects at > >> >> >> >> >> >> >>>> > >> http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> Please keep messages on-topic and check the > >> >> >> >> >> >> >>>> ParaView Wiki > >> >> >> at: > >> >> >> >> >> >> >>>> http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >> >>> > >> >> >> >> >> >> >>> > >> >> >> >> >> >> >> > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> _______________________________________________ > >> >> >> >> >> >> > Powered by www.kitware.com > >> >> >> >> >> >> > > >> >> >> >> >> >> > Visit other Kitware open-source projects at > >> >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> > > >> >> >> >> >> >> > Please keep messages on-topic and check the ParaView > >> >> >> >> >> >> > Wiki > >> >> at: > >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> > > >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >> > > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> -- > >> >> >> >> >> >> Cory Quammen > >> >> >> >> >> >> Research Associate > >> >> >> >> >> >> Department of Computer Science The University of North > >> >> >> >> >> >> Carolina at Chapel Hill > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> ------------------------------ > >> >> >> >> >> >> > >> >> >> >> >> >> > >> _______________________________________________ > >> >> >> >> >> >> Powered by www.kitware.com > >> >> >> >> >> >> > >> >> >> >> >> >> Visit other Kitware open-source projects at > >> >> >> >> >> >> http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> > >> >> >> >> >> >> Please keep messages on-topic and check the ParaView > >> >> >> >> >> >> Wiki > >> at: > >> >> >> >> >> >> http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> > >> >> >> >> >> >> Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 > >> >> >> >> >> >> ***************************************** > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> >> >> ___________ > >> >> >> >> >> > ERBE Elektromedizin GmbH > >> >> >> >> >> > Firmensitz: 72072 Tuebingen > >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 > >> >> >> >> >> > > >> >> >> >> >> > > _______________________________________________ > >> >> >> >> >> > Powered by www.kitware.com > >> >> >> >> >> > > >> >> >> >> >> > Visit other Kitware open-source projects at > >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> > > >> >> >> >> >> > Please keep messages on-topic and check the ParaView > >> >> >> >> >> > Wiki > >> at: > >> >> >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> >> >> > > >> >> >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> >> ___________ > >> >> >> >> > ERBE Elektromedizin GmbH > >> >> >> >> > Firmensitz: 72072 Tuebingen > >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> >> >> > Registergericht: Stuttgart HRB 380137 > >> >> >> >> > > >> >> >> >> > _______________________________________________ > >> >> >> >> > Powered by www.kitware.com > >> >> >> >> > > >> >> >> >> > Visit other Kitware open-source projects at > >> >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> > > >> >> >> >> > Please keep messages on-topic and check the ParaView Wiki > at: > >> >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> >> > > >> >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> ___________ > >> >> >> > ERBE Elektromedizin GmbH > >> >> >> > Firmensitz: 72072 Tuebingen > >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> >> > Registergericht: Stuttgart HRB 380137 > >> >> >> > > >> >> > > >> >> > > >> >> > > >> >> > >> > __________________________________________________________ > >> >> ___________ > >> >> > ERBE Elektromedizin GmbH > >> >> > Firmensitz: 72072 Tuebingen > >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> > Registergericht: Stuttgart HRB 380137 > >> >> > > >> > > >> > > >> > > >> > __________________________________________________________ > >> ___________ > >> > ERBE Elektromedizin GmbH > >> > Firmensitz: 72072 Tuebingen > >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> > Registergericht: Stuttgart HRB 380137 > >> > > > > > > > > __________________________________________________________ > ___________ > > ERBE Elektromedizin GmbH > > Firmensitz: 72072 Tuebingen > > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > > Registergericht: Stuttgart HRB 380137 > > _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 From utkarsh.ayachit at kitware.com Mon Sep 22 10:09:22 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 22 Sep 2014 10:09:22 -0400 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: It's not going to work for pvd. From your original email, I gathered that you were using a fileseries of vtu files (maybe mistakenly). I made the script work for a series of vtu files. Utkarsh On Mon, Sep 22, 2014 at 10:03 AM, Zenker, Dr. Matthias wrote: > Done. > > Unfortunately, the result is the same: Nothing happens when I reload a pvd collection with added timesteps with the macro. > > On the console, the error message is different: > > File "", line 61, in > RuntimeError: Failed to locate the file listing. > > Matthias > >> -----Urspr?ngliche Nachricht----- >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Gesendet: Montag, 22. September 2014 14:23 >> An: Zenker, Dr. Matthias >> Cc: Cory Quammen; paraview at paraview.org >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> Can you try the script with 4.2-RC before we try debugging this? >> >> Thanks >> Utkarsh >> >> On Mon, Sep 22, 2014 at 5:16 AM, Zenker, Dr. Matthias >> wrote: >> > Hi Utkarsh, >> > >> > thank you for the Python script. >> > Having never used Python scripts in ParaView before, I have difficulties to >> run it. When I open the Python shell and try to launch the script with the >> "Run Script" button, I get an error message saying: >> > >> > Traceback (most recent call last): >> > File "", line 19, in >> > NameError: name 'GetActiveSource' is not defined >> > >> > I use ParaView 4.0.1 under Windows 7. I have added the lib directory of >> ParaView to my path, as it says in the ParaView Python documentation. Is >> there anything else I need to do to run the script? >> > >> > When I load it as a macro, the corresponding button appears, but when I >> click on it, nothing seems to happen. I have tested it with a pvd time >> collection where I have commented out the last timestep. When I loaded it, >> all timesteps but the last one were visible. Then I removed the comment >> marks around in the last timestep in the pvd file and lauched the Refresh >> Reader macro. I would expect that now the last timestep in the pvd would be >> visible, but it wasn't. >> > >> > You said that the reader to reload should be the active reader. How do I >> see which reader is the active one? The pvd collection was highlighted when I >> activated the macro. Do I have to do something else? >> > >> > Thanks, >> > >> > Matthias >> > >> >> -----Urspr?ngliche Nachricht----- >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> Gesendet: Sonntag, 21. September 2014 16:17 >> >> An: Zenker, Dr. Matthias >> >> Cc: Cory Quammen; paraview at paraview.org >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> Matthias, >> >> >> >> Attached is the Python script that reloads a file-series. You can >> >> import this as a macro or just run it from the Python shell. In >> >> either case, ensure that the reader to reload is the active reader. >> >> >> >> Utkarsh >> >> >> >> >> >> On Thu, Sep 18, 2014 at 9:34 AM, Zenker, Dr. Matthias >> >> wrote: >> >> > OK - but don't forget that the weekend is also there to have some >> >> > free time... ;) >> >> > >> >> > Matthias >> >> > >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> >> Gesendet: Donnerstag, 18. September 2014 14:46 >> >> >> An: Zenker, Dr. Matthias >> >> >> Cc: Cory Quammen; paraview at paraview.org >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> Sorry, didn't get around to it yet. Over this weekend is more >> >> >> likely, since I am tracking down some last minute issues with 4.2 right >> now. >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias >> >> >> wrote: >> >> >> > Hi Utkarsh, >> >> >> > >> >> >> > any news regarding a reload data function (see below)? >> >> >> > >> >> >> > Matthias >> >> >> > >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> >> >> Gesendet: Montag, 15. September 2014 16:50 >> >> >> >> An: Zenker, Dr. Matthias >> >> >> >> Cc: Cory Quammen; paraview at paraview.org >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> >> >> Ah. since it's a file series, it would not work the way Cory is >> >> >> >> suggesting. I'll see if I can cook up a Python script that can >> >> >> >> make this possible for now. We're putting this on the roadmap >> >> >> >> for the next release (I know I've said that a few times in the past :) >> ). >> >> >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias >> >> >> >> wrote: >> >> >> >> > Normally I load a time series, either a series of vtu files >> >> >> >> > or a time collection >> >> >> >> (pvd file containing the vtu file names with asociated timestamps). >> >> >> >> During the simulation, new files are added to the series. So it >> >> >> >> would be nice to watch the simulation going on by reloading >> >> >> >> from time >> >> to time. >> >> >> >> > >> >> >> >> > Matthias >> >> >> >> > >> >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> >> >> >> Gesendet: Montag, 15. September 2014 16:28 >> >> >> >> >> An: Zenker, Dr. Matthias >> >> >> >> >> Cc: Cory Quammen; paraview at paraview.org >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> >> >> >> >> I suspect will not work with vtu. To understand this better, >> >> >> >> >> what is that which is changing that you need to reload the >> >> >> >> >> file? Are you loading a file series or a single file? >> >> >> >> >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias >> >> >> >> >> wrote: >> >> >> >> >> > Hi Cory, >> >> >> >> >> > >> >> >> >> >> > I use the reader for vtu format and pvd (vtu time >> >> >> >> >> > collection). I tried to >> >> >> >> >> modify the xml as follows: >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > > >> name="VTUrefresh" >> >> >> >> >> > base_proxygroup="sources" >> >> >> >> >> base_proxyname="VTUReader" class="vtuReader"> >> >> >> >> >> > > >> >> >> >> panel_widget="command_button"/> >> >> >> >> >> > >> >> >> >> >> > > >> >> >> >> > file_description="vtu Reader >> >> >> >> >> (Refresh button)" /> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > But I cannot even load it as plugin. Presumably there are >> >> >> >> >> > special keyword to >> >> >> >> >> use for the name of the original reader. Is there a >> >> >> >> >> documentation where I can find more information on that topic? >> >> >> >> >> > >> >> >> >> >> > Thanks, >> >> >> >> >> > >> >> >> >> >> > Matthias >> >> >> >> >> > >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> >> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com] >> >> >> >> >> >> Gesendet: Montag, 15. September 2014 15:05 >> >> >> >> >> >> An: Zenker, Dr. Matthias >> >> >> >> >> >> Cc: paraview at paraview.org >> >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data >> >> >> >> >> >> file >> >> >> >> >> >> >> >> >> >> >> >> Matthias, >> >> >> >> >> >> >> >> >> >> >> >> The method I suggested requires modifying ParaView's >> >> >> >> >> >> source code, so it won't work for a binary distribution. >> >> >> >> >> >> >> >> >> >> >> >> As for the XML method, did you try to load an Xdmf file >> >> >> >> >> >> through what should be the new "Xdmf Reader (Refresh >> >> button)" reader? >> >> >> >> >> >> If you are loading a different type of file, this plugin >> >> >> >> >> >> will have no effect because it provides a Refresh button >> >> >> >> >> >> only for the Xdmf reader. You could modify the XML for >> >> >> >> >> >> other reader types, >> >> >> though. >> >> >> >> >> >> >> >> >> >> >> >> Thanks, >> >> >> >> >> >> Cory >> >> >> >> >> >> >> >> >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias >> >> >> >> >> >> wrote: >> >> >> >> >> >> > Hi, >> >> >> >> >> >> > >> >> >> >> >> >> > I wanted to try the "Reload" button which presumably >> >> >> >> >> >> > can be created by >> >> >> >> >> >> one of the methods outlined below. But I am maybe too >> >> >> >> >> >> naive or am missing >> >> >> >> >> >> something: I have a Windoze binary distribution of >> >> >> >> >> >> ParaView >> >> 4.0.1. >> >> >> >> >> >> I did not find the file indicated by Cory, and copying >> >> >> >> >> >> the xml code given by S?bastien into a file and loading >> >> >> >> >> >> that as plugin had no effect >> >> >> >> >> visible to me. >> >> >> >> >> >> > >> >> >> >> >> >> > What am I missing here? >> >> >> >> >> >> > >> >> >> >> >> >> > Thank you, >> >> >> >> >> >> > >> >> >> >> >> >> > Matthias >> >> >> >> >> >> > >> >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> >> >> >> Von: paraview-bounces at paraview.org [mailto:paraview- >> >> >> >> >> >> >> bounces at paraview.org] Im Auftrag von paraview- >> >> >> >> >> request at paraview.org >> >> >> >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 >> >> >> >> >> >> >> An: paraview at paraview.org >> >> >> >> >> >> >> Betreff: Reload a file >> >> >> >> >> >> >> >> >> >> >> >> >> >> Send ParaView mailing list submissions to >> >> >> >> >> >> >> paraview at paraview.org >> >> >> >> >> >> >> >> >> >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> >> >> >> >> >> >> >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> or, via email, send a message with subject or body 'help' >> to >> >> >> >> >> >> >> paraview-request at paraview.org >> >> >> >> >> >> >> >> >> >> >> >> >> >> You can reach the person managing the list at >> >> >> >> >> >> >> paraview-owner at paraview.org >> >> >> >> >> >> >> >> >> >> >> >> >> >> When replying, please edit your Subject line so it is >> >> >> >> >> >> >> more specific than >> >> >> >> >> >> "Re: >> >> >> >> >> >> >> Contents of ParaView digest..." >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Today's Topics: >> >> >> >> >> >> >> >> >> >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory >> >> >> >> >> >> >> Quammen) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------ >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> - >> >> >> >> >> >> >> >> >> >> >> >> >> >> Message: 1 >> >> >> >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 >> >> >> >> >> >> >> From: Cory Quammen >> >> >> >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a data >> >> >> >> >> >> >> file >> >> >> >> >> >> >> To: Sebastien Jourdain >> >> >> >> >> >> >> >> >> >> >> >> >> >> Cc: Michael Jackson , >> >> >> ParaView >> >> >> >> >> >> >> >> >> >> >> >> >> >> Message-ID: >> >> >> >> >> >> >> > >> >> >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> >> >> >> >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> >> >> >> >> >> >> >> >> >> >> For what it's worth, I just experimented with adding >> >> >> >> >> >> >> the line >> >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> panel_widget="command_button"/> >> >> >> >> >> >> >> >> >> >> >> >> >> >> to the CSV reader and XDMF reader in >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers >> >> >> >> >> >> >> .xml >> >> >> >> >> >> >> >> >> >> >> >> >> >> The Refresh button appears among the other property >> >> >> >> >> >> >> widgets and it indeed reloads the data set. >> >> >> >> >> >> >> >> >> >> >> >> >> >> I would happily add this to all the readers and submit >> >> >> >> >> >> >> a patch to gerrit if it would be received well by the >> >> >> >> >> >> >> core ParaView >> >> >> >> developers. >> >> >> >> >> >> >> >> >> >> >> >> >> >> Thanks, >> >> >> >> >> >> >> Cory >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien Jourdain >> >> >> >> >> >> >> wrote: >> >> >> >> >> >> >> > BTW that's the correct XML for you, just need to >> >> >> >> >> >> >> > create a file with that in and load it as a plugin >> >> >> >> >> >> >> > and you will have your >> >> >> >> "Refresh" >> >> >> >> >> button. >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > > >> >> >> >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" >> >> >> >> >> >> >> > base_proxyname="XdmfReader" >> class="vtkXdmfReader"> >> >> >> >> >> >> >> > > >> >> >> >> >> >> > panel_widget="command_button"/> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > > >> >> >> >> >> >> > file_description="Xdmf Reader (Refresh button)" /> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien Jourdain >> >> >> >> >> >> >> > wrote: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Another approach could be a python macro that >> >> >> >> >> >> >> >> invalidate the "active/selected' proxy in the >> >> >> >> >> >> >> >> pipeline, but that one will require the usage of >> >> >> >> >> >> >> >> ParaView >> >> in built-in mode. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> If interested I can try to write the corresponding >> >> >> >> >> >> >> >> python >> >> >> code... >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Seb >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien >> >> >> >> >> >> >> >> Jourdain wrote: >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> I forgot to state the obvious, the plugin is a XML one... >> >> >> >> >> >> >> >>> No code involved... >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> In fact, just having the XML that I wrote in a >> >> >> >> >> >> >> >>> file extend the UI with a button to refresh the >> >> >> >> >> >> >> >>> reader should be >> >> >> enough. >> >> >> >> >> >> >> >>> Need to figure out why the reader factory did not >> >> >> >> >> >> >> >>> catch up the >> >> >> >> >> hint. >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> That should be the only thing that you would need. >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> Seb >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael Jackson >> >> >> >> >> >> >> >>> wrote: >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> I was hoping that ParaView just had something built >> in. >> >> >> >> >> >> >> >>>> I would rather not have to create a plugin and >> >> >> >> >> >> >> >>>> distribute that along side my own software and to >> >> >> >> >> >> >> >>>> keep up on builds for all the various OS's and all of >> that. >> >> >> >> >> >> >> >>>> i tried that for a while and I just could not >> >> >> >> >> >> keep up. >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> So either I am the only person who has asked for >> >> >> >> >> >> >> >>>> this or there is some over riding reason in the >> >> >> >> >> >> >> >>>> design of ParView why this type of functionality >> >> >> >> >> >> >> >>>> is not in >> >> ParaView. >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> Thanks >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> >> >> >> _ >> >> >> >> >> >> >> >>>> Mike Jackson Principal Software Engineer >> >> >> >> >> >> >> >>>> BlueQuartz Software Dayton, Ohio >> >> >> >> >> >> >> >>>> mike.jackson at bluequartz.net >> >> www.bluequartz.net >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> wrote: >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> > hi you can try the approach of S?bastien >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/tool >> >> >> >> >> >> >> >>>> > s.h >> >> >> >> >> >> >> >>>> > tml >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > I haven't tested yet. >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > You can save the code as a macro, so you will >> >> >> >> >> >> >> >>>> > have a >> >> >> button. >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > Felipe >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : >> >> >> >> >> >> >> >>>> >> Is there button where I can simply reload a >> >> >> >> >> >> >> >>>> >> data file that was read in a pipeline? >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> >> We have a workflow where we process data into >> >> >> >> >> >> >> >>>> >> a file and view it in ParaView. it is becoming >> >> >> >> >> >> >> >>>> >> tedious to blow away the entire pipeline just >> >> >> >> >> >> >> >>>> >> to reload the new >> >> >> data. >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> >> I know about state files but this still >> >> >> >> >> >> >> >>>> >> requires the user to go to the File->Load >> >> >> >> >> >> >> >>>> >> State... " menu and then select a state >> >> >> >> >> file. >> >> >> >> >> >> >> >>>> >> I would like to just select the data file in >> >> >> >> >> >> >> >>>> >> the Pipeline browser (XDMF File reader for >> >> >> >> >> >> >> >>>> >> us), and just click some button that just >> >> >> >> >> >> >> >>>> >> reloads data from >> >> the file. >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> >> Or am I just missing something? I am using >> >> >> >> >> >> >> >>>> >> ParaView 3.98.1. I have to admit I have not >> >> >> >> >> >> >> >>>> >> tried any of the >> >> >> >> >> >> >> >>>> >> 4.0.RC* >> >> >> >> >> downloads. >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> >> Thanks >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _________________________________________________________ >> >> >> >> >> >> >> >>>> >> Mike Jackson >> mike.jackson at bluequartz.net >> >> >> >> >> >> >> >>>> >> BlueQuartz Software >> www.bluequartz.net >> >> >> >> >> >> >> >>>> >> Principal Software Engineer Dayton, Ohio >> >> >> >> >> >> >> >>>> >> >> >> >> >> _______________________________________________ >> >> >> >> >> >> >> >>>> >> Powered by www.kitware.com >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> >> Visit other Kitware open-source projects at >> >> >> >> >> >> >> >>>> >> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> >> Please keep messages on-topic and check the >> >> >> >> >> >> >> >>>> >> ParaView Wiki >> >> >> >> >> at: >> >> >> >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> >>>> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > -- >> >> >> >> >> >> >> >>>> > Felipe Bordeu Weldt Ing?nieur de Recherche >> >> >> >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 74 >> >> >> >> >> >> >> >>>> > 74 >> >> >> >> >> >> >> >>>> > 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - >> >> >> >> >> >> >> >>>> > UMR CNRS >> >> >> >> >> >> >> >>>> > 6183 ?cole Centrale Nantes >> >> >> >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE >> >> >> >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > >> >> >> >> _______________________________________________ >> >> >> >> >> >> >> >>>> > Powered by www.kitware.com >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > Visit other Kitware open-source projects at >> >> >> >> >> >> >> >>>> > >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > Please keep messages on-topic and check the >> >> >> >> >> >> >> >>>> > ParaView Wiki >> >> >> >> >> at: >> >> >> >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/paravi >> >> >> >> >> >> >> >>>> > ew >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> >> >> >> _______________________________________________ >> >> >> >> >> >> >> >>>> Powered by www.kitware.com >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> Visit other Kitware open-source projects at >> >> >> >> >> >> >> >>>> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> Please keep messages on-topic and check the >> >> >> >> >> >> >> >>>> ParaView Wiki >> >> >> >> at: >> >> >> >> >> >> >> >>>> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> >>>> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> _______________________________________________ >> >> >> >> >> >> >> > Powered by www.kitware.com >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > Please keep messages on-topic and check the ParaView >> >> >> >> >> >> >> > Wiki >> >> >> at: >> >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> >> Cory Quammen >> >> >> >> >> >> >> Research Associate >> >> >> >> >> >> >> Department of Computer Science The University of North >> >> >> >> >> >> >> Carolina at Chapel Hill >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> >> >> Powered by www.kitware.com >> >> >> >> >> >> >> >> >> >> >> >> >> >> Visit other Kitware open-source projects at >> >> >> >> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >> >> >> >> >> >> >> Please keep messages on-topic and check the ParaView >> >> >> >> >> >> >> Wiki >> >> at: >> >> >> >> >> >> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >> >> >> >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 >> >> >> >> >> >> >> ***************************************** >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> >> >> ___________ >> >> >> >> >> >> > ERBE Elektromedizin GmbH >> >> >> >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> >> >> >> > >> >> >> >> >> >> > >> _______________________________________________ >> >> >> >> >> >> > Powered by www.kitware.com >> >> >> >> >> >> > >> >> >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> > >> >> >> >> >> >> > Please keep messages on-topic and check the ParaView >> >> >> >> >> >> > Wiki >> >> at: >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> >> >> > >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> >> ___________ >> >> >> >> >> > ERBE Elektromedizin GmbH >> >> >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> >> >> > >> >> >> >> >> > _______________________________________________ >> >> >> >> >> > Powered by www.kitware.com >> >> >> >> >> > >> >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >> > >> >> >> >> >> > Please keep messages on-topic and check the ParaView Wiki >> at: >> >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> >> > >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> ___________ >> >> >> >> > ERBE Elektromedizin GmbH >> >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> __________________________________________________________ >> >> >> ___________ >> >> >> > ERBE Elektromedizin GmbH >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> > >> >> > >> >> > >> >> > >> >> >> __________________________________________________________ >> >> ___________ >> >> > ERBE Elektromedizin GmbH >> >> > Firmensitz: 72072 Tuebingen >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> > Registergericht: Stuttgart HRB 380137 >> >> > >> > >> > >> > >> __________________________________________________________ >> ___________ >> > ERBE Elektromedizin GmbH >> > Firmensitz: 72072 Tuebingen >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> > Registergericht: Stuttgart HRB 380137 >> > > > > _____________________________________________________________________ > ERBE Elektromedizin GmbH > Firmensitz: 72072 Tuebingen > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > Registergericht: Stuttgart HRB 380137 > From insley at anl.gov Mon Sep 22 10:10:35 2014 From: insley at anl.gov (Insley, Joseph A.) Date: Mon, 22 Sep 2014 14:10:35 +0000 Subject: [Paraview] Plotting Nek5000 output data In-Reply-To: References: Message-ID: <2A7121FA-1560-4422-B982-971121DF6FDD@anl.gov> Could this just be a matter of representation? From the images it looks like in VisIt you are using the pseudocolor filter, which is just a surface representation colored by some scalar field (x_velocity, it looks like). In ParaView, you are applying the contour filter with a single value, and displaying the surface representation of that. I can't tell from the snapshot, but I am guessing that the representation of the square_nek5000 data set is set to outline, or possibly wireframe. If that is the case, try changing that to surface representation. You may then need to change the colorby selection to be x_velocity, if that is the variable you are interested in. Hope that helps, joe On Sep 19, 2014, at 4:14 PM, Pradeep Jha wrote: I am outputting my data from Nek5000 in the case.fld* format. I am creating a case.nek5000 file which reads like: ==== filetemplate: case.fld%02d firsttimestep: 1 numtimesteps: 2 ==== When I am opening this *nek5000 file in Paraview 4.1, I don't see the contours. In Visit I see them (images attached). Any tips? _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matthias.Zenker at erbe-med.com Mon Sep 22 10:51:34 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Mon, 22 Sep 2014 14:51:34 +0000 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Hi Utkarsh, I tested it for a series of vtu files, and indeed it works with the 4.2 RC (not with 4.0.1). Also there is no error message on the Python console any more. Thank you! Now I can at least follow the simulation going on by loading the vtu series. Would it be possible to make it work also for a pvd...? :) Thanks, Matthias > -----Urspr?ngliche Nachricht----- > Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Gesendet: Montag, 22. September 2014 16:09 > An: Zenker, Dr. Matthias > Cc: Cory Quammen; paraview at paraview.org > Betreff: Re: [Paraview] How to simply "Reload" a data file > > It's not going to work for pvd. From your original email, I gathered that you > were using a fileseries of vtu files (maybe mistakenly). I made the script work > for a series of vtu files. > > Utkarsh > > On Mon, Sep 22, 2014 at 10:03 AM, Zenker, Dr. Matthias > wrote: > > Done. > > > > Unfortunately, the result is the same: Nothing happens when I reload a > pvd collection with added timesteps with the macro. > > > > On the console, the error message is different: > > > > File "", line 61, in > > RuntimeError: Failed to locate the file listing. > > > > Matthias > > > >> -----Urspr?ngliche Nachricht----- > >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> Gesendet: Montag, 22. September 2014 14:23 > >> An: Zenker, Dr. Matthias > >> Cc: Cory Quammen; paraview at paraview.org > >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> > >> Can you try the script with 4.2-RC before we try debugging this? > >> > >> Thanks > >> Utkarsh > >> > >> On Mon, Sep 22, 2014 at 5:16 AM, Zenker, Dr. Matthias > >> wrote: > >> > Hi Utkarsh, > >> > > >> > thank you for the Python script. > >> > Having never used Python scripts in ParaView before, I have > >> > difficulties to > >> run it. When I open the Python shell and try to launch the script > >> with the "Run Script" button, I get an error message saying: > >> > > >> > Traceback (most recent call last): > >> > File "", line 19, in > >> > NameError: name 'GetActiveSource' is not defined > >> > > >> > I use ParaView 4.0.1 under Windows 7. I have added the lib > >> > directory of > >> ParaView to my path, as it says in the ParaView Python documentation. > >> Is there anything else I need to do to run the script? > >> > > >> > When I load it as a macro, the corresponding button appears, but > >> > when I > >> click on it, nothing seems to happen. I have tested it with a pvd > >> time collection where I have commented out the last timestep. When I > >> loaded it, all timesteps but the last one were visible. Then I > >> removed the comment marks around in the last timestep in the pvd file > >> and lauched the Refresh Reader macro. I would expect that now the > >> last timestep in the pvd would be visible, but it wasn't. > >> > > >> > You said that the reader to reload should be the active reader. How > >> > do I > >> see which reader is the active one? The pvd collection was > >> highlighted when I activated the macro. Do I have to do something else? > >> > > >> > Thanks, > >> > > >> > Matthias > >> > > >> >> -----Urspr?ngliche Nachricht----- > >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> Gesendet: Sonntag, 21. September 2014 16:17 > >> >> An: Zenker, Dr. Matthias > >> >> Cc: Cory Quammen; paraview at paraview.org > >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> > >> >> Matthias, > >> >> > >> >> Attached is the Python script that reloads a file-series. You can > >> >> import this as a macro or just run it from the Python shell. In > >> >> either case, ensure that the reader to reload is the active reader. > >> >> > >> >> Utkarsh > >> >> > >> >> > >> >> On Thu, Sep 18, 2014 at 9:34 AM, Zenker, Dr. Matthias > >> >> wrote: > >> >> > OK - but don't forget that the weekend is also there to have > >> >> > some free time... ;) > >> >> > > >> >> > Matthias > >> >> > > >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> >> Gesendet: Donnerstag, 18. September 2014 14:46 > >> >> >> An: Zenker, Dr. Matthias > >> >> >> Cc: Cory Quammen; paraview at paraview.org > >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> >> > >> >> >> Sorry, didn't get around to it yet. Over this weekend is more > >> >> >> likely, since I am tracking down some last minute issues with > >> >> >> 4.2 right > >> now. > >> >> >> > >> >> >> Utkarsh > >> >> >> > >> >> >> On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias > >> >> >> wrote: > >> >> >> > Hi Utkarsh, > >> >> >> > > >> >> >> > any news regarding a reload data function (see below)? > >> >> >> > > >> >> >> > Matthias > >> >> >> > > >> >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> >> >> Gesendet: Montag, 15. September 2014 16:50 > >> >> >> >> An: Zenker, Dr. Matthias > >> >> >> >> Cc: Cory Quammen; paraview at paraview.org > >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file > >> >> >> >> > >> >> >> >> Ah. since it's a file series, it would not work the way Cory > >> >> >> >> is suggesting. I'll see if I can cook up a Python script > >> >> >> >> that can make this possible for now. We're putting this on > >> >> >> >> the roadmap for the next release (I know I've said that a > >> >> >> >> few times in the past :) > >> ). > >> >> >> >> > >> >> >> >> Utkarsh > >> >> >> >> > >> >> >> >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias > >> >> >> >> wrote: > >> >> >> >> > Normally I load a time series, either a series of vtu > >> >> >> >> > files or a time collection > >> >> >> >> (pvd file containing the vtu file names with asociated > timestamps). > >> >> >> >> During the simulation, new files are added to the series. So > >> >> >> >> it would be nice to watch the simulation going on by > >> >> >> >> reloading from time > >> >> to time. > >> >> >> >> > > >> >> >> >> > Matthias > >> >> >> >> > > >> >> >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> >> >> >> >> Gesendet: Montag, 15. September 2014 16:28 > >> >> >> >> >> An: Zenker, Dr. Matthias > >> >> >> >> >> Cc: Cory Quammen; paraview at paraview.org > >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data > >> >> >> >> >> file > >> >> >> >> >> > >> >> >> >> >> I suspect will not work with vtu. To understand this > >> >> >> >> >> better, what is that which is changing that you need to > >> >> >> >> >> reload the file? Are you loading a file series or a single file? > >> >> >> >> >> > >> >> >> >> >> Utkarsh > >> >> >> >> >> > >> >> >> >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias > >> >> >> >> >> wrote: > >> >> >> >> >> > Hi Cory, > >> >> >> >> >> > > >> >> >> >> >> > I use the reader for vtu format and pvd (vtu time > >> >> >> >> >> > collection). I tried to > >> >> >> >> >> modify the xml as follows: > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > >> >> name="VTUrefresh" > >> >> >> >> >> > base_proxygroup="sources" > >> >> >> >> >> base_proxyname="VTUReader" class="vtuReader"> > >> >> >> >> >> > >> >> >> >> >> panel_widget="command_button"/> > >> >> >> >> >> > > >> >> >> >> >> > >> >> >> >> >> > file_description="vtu Reader > >> >> >> >> >> (Refresh button)" /> > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > But I cannot even load it as plugin. Presumably there > >> >> >> >> >> > are special keyword to > >> >> >> >> >> use for the name of the original reader. Is there a > >> >> >> >> >> documentation where I can find more information on that > topic? > >> >> >> >> >> > > >> >> >> >> >> > Thanks, > >> >> >> >> >> > > >> >> >> >> >> > Matthias > >> >> >> >> >> > > >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> >> >> >> Von: Cory Quammen > [mailto:cory.quammen at kitware.com] > >> >> >> >> >> >> Gesendet: Montag, 15. September 2014 15:05 > >> >> >> >> >> >> An: Zenker, Dr. Matthias > >> >> >> >> >> >> Cc: paraview at paraview.org > >> >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data > >> >> >> >> >> >> file > >> >> >> >> >> >> > >> >> >> >> >> >> Matthias, > >> >> >> >> >> >> > >> >> >> >> >> >> The method I suggested requires modifying ParaView's > >> >> >> >> >> >> source code, so it won't work for a binary distribution. > >> >> >> >> >> >> > >> >> >> >> >> >> As for the XML method, did you try to load an Xdmf > >> >> >> >> >> >> file through what should be the new "Xdmf Reader > >> >> >> >> >> >> (Refresh > >> >> button)" reader? > >> >> >> >> >> >> If you are loading a different type of file, this > >> >> >> >> >> >> plugin will have no effect because it provides a > >> >> >> >> >> >> Refresh button only for the Xdmf reader. You could > >> >> >> >> >> >> modify the XML for other reader types, > >> >> >> though. > >> >> >> >> >> >> > >> >> >> >> >> >> Thanks, > >> >> >> >> >> >> Cory > >> >> >> >> >> >> > >> >> >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias > >> >> >> >> >> >> wrote: > >> >> >> >> >> >> > Hi, > >> >> >> >> >> >> > > >> >> >> >> >> >> > I wanted to try the "Reload" button which presumably > >> >> >> >> >> >> > can be created by > >> >> >> >> >> >> one of the methods outlined below. But I am maybe too > >> >> >> >> >> >> naive or am missing > >> >> >> >> >> >> something: I have a Windoze binary distribution of > >> >> >> >> >> >> ParaView > >> >> 4.0.1. > >> >> >> >> >> >> I did not find the file indicated by Cory, and copying > >> >> >> >> >> >> the xml code given by S?bastien into a file and > >> >> >> >> >> >> loading that as plugin had no effect > >> >> >> >> >> visible to me. > >> >> >> >> >> >> > > >> >> >> >> >> >> > What am I missing here? > >> >> >> >> >> >> > > >> >> >> >> >> >> > Thank you, > >> >> >> >> >> >> > > >> >> >> >> >> >> > Matthias > >> >> >> >> >> >> > > >> >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- > >> >> >> >> >> >> >> Von: paraview-bounces at paraview.org > >> >> >> >> >> >> >> [mailto:paraview- bounces at paraview.org] Im Auftrag > >> >> >> >> >> >> >> von paraview- > >> >> >> >> >> request at paraview.org > >> >> >> >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 > >> >> >> >> >> >> >> An: paraview at paraview.org > >> >> >> >> >> >> >> Betreff: Reload a file > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Send ParaView mailing list submissions to > >> >> >> >> >> >> >> paraview at paraview.org > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, > >> >> >> >> >> >> >> visit > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >> >> or, via email, send a message with subject or body > 'help' > >> to > >> >> >> >> >> >> >> paraview-request at paraview.org > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> You can reach the person managing the list at > >> >> >> >> >> >> >> paraview-owner at paraview.org > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> When replying, please edit your Subject line so it > >> >> >> >> >> >> >> is more specific than > >> >> >> >> >> >> "Re: > >> >> >> >> >> >> >> Contents of ParaView digest..." > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Today's Topics: > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory > >> >> >> >> >> >> >> Quammen) > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> --------------------------------------------------- > >> >> >> >> >> >> >> --- > >> >> >> >> >> >> >> --- > >> >> >> >> >> >> >> --- > >> >> >> >> >> >> >> --- > >> >> >> >> >> >> >> --- > >> >> >> >> >> >> >> --- > >> >> >> >> >> >> >> - > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Message: 1 > >> >> >> >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 > >> >> >> >> >> >> >> From: Cory Quammen > >> >> >> >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a > >> >> >> >> >> >> >> data file > >> >> >> >> >> >> >> To: Sebastien Jourdain > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Cc: Michael Jackson , > >> >> >> ParaView > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Message-ID: > >> >> >> >> >> >> >> >> >> >> >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> > >> >> >> >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> For what it's worth, I just experimented with > >> >> >> >> >> >> >> adding the line > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> panel_widget="command_button"/> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> to the CSV reader and XDMF reader in > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers > >> >> >> >> >> >> >> .xml > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> The Refresh button appears among the other property > >> >> >> >> >> >> >> widgets and it indeed reloads the data set. > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> I would happily add this to all the readers and > >> >> >> >> >> >> >> submit a patch to gerrit if it would be received > >> >> >> >> >> >> >> well by the core ParaView > >> >> >> >> developers. > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Thanks, > >> >> >> >> >> >> >> Cory > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien > >> >> >> >> >> >> >> Jourdain wrote: > >> >> >> >> >> >> >> > BTW that's the correct XML for you, just need to > >> >> >> >> >> >> >> > create a file with that in and load it as a > >> >> >> >> >> >> >> > plugin and you will have your > >> >> >> >> "Refresh" > >> >> >> >> >> button. > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" > >> >> >> >> >> >> >> > base_proxyname="XdmfReader" > >> class="vtkXdmfReader"> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > panel_widget="command_button"/> > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > file_description="Xdmf Reader (Refresh button)" /> > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien > >> >> >> >> >> >> >> > Jourdain wrote: > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> Another approach could be a python macro that > >> >> >> >> >> >> >> >> invalidate the "active/selected' proxy in the > >> >> >> >> >> >> >> >> pipeline, but that one will require the usage of > >> >> >> >> >> >> >> >> ParaView > >> >> in built-in mode. > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> If interested I can try to write the > >> >> >> >> >> >> >> >> corresponding python > >> >> >> code... > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> Seb > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien > >> >> >> >> >> >> >> >> Jourdain wrote: > >> >> >> >> >> >> >> >>> > >> >> >> >> >> >> >> >>> I forgot to state the obvious, the plugin is a XML > one... > >> >> >> >> >> >> >> >>> No code involved... > >> >> >> >> >> >> >> >>> > >> >> >> >> >> >> >> >>> In fact, just having the XML that I wrote in a > >> >> >> >> >> >> >> >>> file extend the UI with a button to refresh the > >> >> >> >> >> >> >> >>> reader should be > >> >> >> enough. > >> >> >> >> >> >> >> >>> Need to figure out why the reader factory did > >> >> >> >> >> >> >> >>> not catch up the > >> >> >> >> >> hint. > >> >> >> >> >> >> >> >>> > >> >> >> >> >> >> >> >>> That should be the only thing that you would > need. > >> >> >> >> >> >> >> >>> > >> >> >> >> >> >> >> >>> Seb > >> >> >> >> >> >> >> >>> > >> >> >> >> >> >> >> >>> > >> >> >> >> >> >> >> >>> > >> >> >> >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael > >> >> >> >> >> >> >> >>> Jackson wrote: > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> I was hoping that ParaView just had something > >> >> >> >> >> >> >> >>>> built > >> in. > >> >> >> >> >> >> >> >>>> I would rather not have to create a plugin and > >> >> >> >> >> >> >> >>>> distribute that along side my own software and > >> >> >> >> >> >> >> >>>> to keep up on builds for all the various OS's > >> >> >> >> >> >> >> >>>> and all of > >> that. > >> >> >> >> >> >> >> >>>> i tried that for a while and I just could not > >> >> >> >> >> >> keep up. > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> So either I am the only person who has asked > >> >> >> >> >> >> >> >>>> for this or there is some over riding reason > >> >> >> >> >> >> >> >>>> in the design of ParView why this type of > >> >> >> >> >> >> >> >>>> functionality is not in > >> >> ParaView. > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> Thanks > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> >> >> >> >> _ > >> >> >> >> >> >> >> >>>> Mike Jackson Principal Software > Engineer > >> >> >> >> >> >> >> >>>> BlueQuartz Software Dayton, Ohio > >> >> >> >> >> >> >> >>>> mike.jackson at bluequartz.net > >> >> www.bluequartz.net > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> wrote: > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > hi you can try the approach of S?bastien > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/t > >> >> >> >> >> >> >> >>>> > ool > >> >> >> >> >> >> >> >>>> > s.h > >> >> >> >> >> >> >> >>>> > tml > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > I haven't tested yet. > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > You can save the code as a macro, so you > >> >> >> >> >> >> >> >>>> > will have a > >> >> >> button. > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > Felipe > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a ?crit : > >> >> >> >> >> >> >> >>>> >> Is there button where I can simply reload a > >> >> >> >> >> >> >> >>>> >> data file that was read in a pipeline? > >> >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >> >>>> >> We have a workflow where we process data > >> >> >> >> >> >> >> >>>> >> into a file and view it in ParaView. it is > >> >> >> >> >> >> >> >>>> >> becoming tedious to blow away the entire > >> >> >> >> >> >> >> >>>> >> pipeline just to reload the new > >> >> >> data. > >> >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >> >>>> >> I know about state files but this still > >> >> >> >> >> >> >> >>>> >> requires the user to go to the File->Load > >> >> >> >> >> >> >> >>>> >> State... " menu and then select a state > >> >> >> >> >> file. > >> >> >> >> >> >> >> >>>> >> I would like to just select the data file > >> >> >> >> >> >> >> >>>> >> in the Pipeline browser (XDMF File reader > >> >> >> >> >> >> >> >>>> >> for us), and just click some button that > >> >> >> >> >> >> >> >>>> >> just reloads data from > >> >> the file. > >> >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >> >>>> >> Or am I just missing something? I am using > >> >> >> >> >> >> >> >>>> >> ParaView 3.98.1. I have to admit I have not > >> >> >> >> >> >> >> >>>> >> tried any of the > >> >> >> >> >> >> >> >>>> >> 4.0.RC* > >> >> >> >> >> downloads. > >> >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >> >>>> >> Thanks > >> >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > _________________________________________________________ > >> >> >> >> >> >> >> >>>> >> Mike Jackson > >> mike.jackson at bluequartz.net > >> >> >> >> >> >> >> >>>> >> BlueQuartz Software > >> www.bluequartz.net > >> >> >> >> >> >> >> >>>> >> Principal Software Engineer Dayton, > Ohio > >> >> >> >> >> >> >> >>>> >> > >> >> >> >> _______________________________________________ > >> >> >> >> >> >> >> >>>> >> Powered by www.kitware.com > >> >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >> >>>> >> Visit other Kitware open-source projects at > >> >> >> >> >> >> >> >>>> >> > >> >> >> http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >> >>>> >> Please keep messages on-topic and check the > >> >> >> >> >> >> >> >>>> >> ParaView Wiki > >> >> >> >> >> at: > >> >> >> >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> >> >>>> >> > >> >> >> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> >> >>>> >> > >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > -- > >> >> >> >> >> >> >> >>>> > Felipe Bordeu Weldt Ing?nieur de Recherche > >> >> >> >> >> >> >> >>>> > ------------------------------------- > >> >> >> >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 > >> >> >> >> >> >> >> >>>> > 74 > >> >> >> >> >> >> >> >>>> > 74 > >> >> >> >> >> >> >> >>>> > 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - > >> >> >> >> >> >> >> >>>> > UMR CNRS > >> >> >> >> >> >> >> >>>> > 6183 ?cole Centrale Nantes > >> >> >> >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE > >> >> >> >> >> >> >> >>>> > ------------------------------------- > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > > >> >> >> >> _______________________________________________ > >> >> >> >> >> >> >> >>>> > Powered by www.kitware.com > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > Visit other Kitware open-source projects at > >> >> >> >> >> >> >> >>>> > > >> >> http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > Please keep messages on-topic and check the > >> >> >> >> >> >> >> >>>> > ParaView Wiki > >> >> >> >> >> at: > >> >> >> >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> >> >>>> > > >> >> >> >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/par > >> >> >> >> >> >> >> >>>> > avi > >> >> >> >> >> >> >> >>>> > ew > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> > >> >> >> _______________________________________________ > >> >> >> >> >> >> >> >>>> Powered by www.kitware.com > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> Visit other Kitware open-source projects at > >> >> >> >> >> >> >> >>>> > >> >> http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> Please keep messages on-topic and check the > >> >> >> >> >> >> >> >>>> ParaView Wiki > >> >> >> >> at: > >> >> >> >> >> >> >> >>>> http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> >> >>>> > >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >> >> >>> > >> >> >> >> >> >> >> >>> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > > >> >> _______________________________________________ > >> >> >> >> >> >> >> > Powered by www.kitware.com > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > Visit other Kitware open-source projects at > >> >> >> >> >> >> >> > > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > Please keep messages on-topic and check the > >> >> >> >> >> >> >> > ParaView Wiki > >> >> >> at: > >> >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> -- > >> >> >> >> >> >> >> Cory Quammen > >> >> >> >> >> >> >> Research Associate > >> >> >> >> >> >> >> Department of Computer Science The University of > >> >> >> >> >> >> >> North Carolina at Chapel Hill > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> ------------------------------ > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> _______________________________________________ > >> >> >> >> >> >> >> Powered by www.kitware.com > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Visit other Kitware open-source projects at > >> >> >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Please keep messages on-topic and check the > >> >> >> >> >> >> >> ParaView Wiki > >> >> at: > >> >> >> >> >> >> >> http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 > >> >> >> >> >> >> >> ***************************************** > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> >> >> >> ___________ > >> >> >> >> >> >> > ERBE Elektromedizin GmbH > >> >> >> >> >> >> > Firmensitz: 72072 Tuebingen > >> >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 > >> >> >> >> >> >> > > >> >> >> >> >> >> > > >> _______________________________________________ > >> >> >> >> >> >> > Powered by www.kitware.com > >> >> >> >> >> >> > > >> >> >> >> >> >> > Visit other Kitware open-source projects at > >> >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> >> > > >> >> >> >> >> >> > Please keep messages on-topic and check the ParaView > >> >> >> >> >> >> > Wiki > >> >> at: > >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> >> >> >> > > >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > >> >> >> >> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> >> >> ___________ > >> >> >> >> >> > ERBE Elektromedizin GmbH > >> >> >> >> >> > Firmensitz: 72072 Tuebingen > >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 > >> >> >> >> >> > > >> >> >> >> >> > > _______________________________________________ > >> >> >> >> >> > Powered by www.kitware.com > >> >> >> >> >> > > >> >> >> >> >> > Visit other Kitware open-source projects at > >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >> >> >> >> > > >> >> >> >> >> > Please keep messages on-topic and check the ParaView > >> >> >> >> >> > Wiki > >> at: > >> >> >> >> >> > http://paraview.org/Wiki/ParaView > >> >> >> >> >> > > >> >> >> >> >> > Follow this link to subscribe/unsubscribe: > >> >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> >> ___________ > >> >> >> >> > ERBE Elektromedizin GmbH > >> >> >> >> > Firmensitz: 72072 Tuebingen > >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> >> >> > Registergericht: Stuttgart HRB 380137 > >> >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > >> >> > >> > __________________________________________________________ > >> >> >> ___________ > >> >> >> > ERBE Elektromedizin GmbH > >> >> >> > Firmensitz: 72072 Tuebingen > >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> >> > Registergericht: Stuttgart HRB 380137 > >> >> >> > > >> >> > > >> >> > > >> >> > > >> >> > >> > __________________________________________________________ > >> >> ___________ > >> >> > ERBE Elektromedizin GmbH > >> >> > Firmensitz: 72072 Tuebingen > >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> >> > Registergericht: Stuttgart HRB 380137 > >> >> > > >> > > >> > > >> > > >> > __________________________________________________________ > >> ___________ > >> > ERBE Elektromedizin GmbH > >> > Firmensitz: 72072 Tuebingen > >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > >> > Registergericht: Stuttgart HRB 380137 > >> > > > > > > > > __________________________________________________________ > ___________ > > ERBE Elektromedizin GmbH > > Firmensitz: 72072 Tuebingen > > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede > > Registergericht: Stuttgart HRB 380137 > > _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 From dave.demarle at kitware.com Mon Sep 22 11:48:49 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 22 Sep 2014 09:48:49 -0600 Subject: [Paraview] announce: VTK and ParaView scripting training October 21 at Kitware's North Carolina office Message-ID: Kitware is hosting a VTK-ParaView training course in Carrboro, NC. The course will be held on October 21, 2014. Attendees will gain practical experience in both ParaView, a scalable application for general purpose scientific visualization, and The Visualization Toolkit (VTK), the underlying open-source library from which ParaView is built. The training mixes theory and application to guide attendees through a set of exercises, which are all given in the python programming language. Upon completion of this course, attendees will not only know how to use ParaView and VTK, but they will also know how to extend ParaView at run time, use it in concert with other Python capable applications, and run it in batch processing HPC contexts. Additional details and registration information are available on the Kitware website . The price of the course via early registration is $650. Early registration is available through October 8, 2014. The price of the course via regular registration is $815. In addition, Kitware will be hosting a ?Project Lifecycle Management with the CMake Family of Tools? training course on October 20, 2014. This course will also be hosted in Carrboro. For more information, please visit http://www.kitware.com/products/protraining.php. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Mon Sep 22 16:54:57 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 22 Sep 2014 22:54:57 +0200 Subject: [Paraview] useful plugin: how to do it, really? Message-ID: <54208CA1.7050907@xs4all.nl> Dear Paraview people, I am investigating the option to use Paraview as the base platform for a simulation project that we are currently working on. Paraview's visualisation capabilities, as well as the (alleged) extensibility (by writing plugins) suggest that this is the case indeed. In order to get a better feeling of this, I want to try a small example showing me how this all works. However, I get lost in the documentation and code tree. Browsing the web for information on writing a paraview plugin typically refer to Paraview's web pages, but I must admit that the are not really helpful, despite the amount of words devoted to the topic. I wonder if there is somebody who can help me, or point me to useful information. As a sample problem, this is what I would like to do: 1. Suppose I have created, interactively, a box, a sphere and a cone, using the corresponding entries in the "Sources" menu. 2. Now I would like to *programmatically* (i.e. in a c++ plugin) loop over the sources (here: the box, sphere and cone) and for each of the elements get hold of the parameters that were used to define these sources (i.e. the box dimensions, center, radii etc.). With these parameters I can then do other things to build my own extension, but those details do not matter here. I have looked into the examples, but I really do not recognise in any of them what I'm supposed to do. Maybe it is there, but I find the code tree of such a complexity that I have problems in finding what I need. Your help is greatly appreciated. Kind Regards, Bertwim From utkarsh.ayachit at kitware.com Tue Sep 23 09:01:49 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 23 Sep 2014 09:01:49 -0400 Subject: [Paraview] useful plugin: how to do it, really? In-Reply-To: <54208CA1.7050907@xs4all.nl> References: <54208CA1.7050907@xs4all.nl> Message-ID: Bertwim, I agree the developer docs are little scattered right now. My plan is to start writing blog posts that make this easier to digest. One of these, hopefully, I get around to it :). In the mean time, my replies are inline. > 1. Suppose I have created, interactively, a box, a sphere and a cone, > using the corresponding entries in the "Sources" menu. > > 2. Now I would like to *programmatically* (i.e. in a c++ plugin) loop > over the sources (here: the box, sphere and cone) and for each of the > elements > get hold of the parameters that were used to define these sources (i.e. > the box dimensions, center, radii etc.). With these parameters I can > then do other things to build my own extension, but those details do not > matter here. Several ways for getting to the "proxies" for the sphere, box, etc. created. One way it using the vtkSMSessionProxyManager. a. Using vtkSMSessionProxyManager: a.1 Get access to the active session's proxy manager using pqActiveObjects::instance().proxyManager() [1] a.2 Use vtkSMProxyIterator[2] to iterate over the "sources" group. vtkNew iter; iter->SetSessionProxyManager(pqActiveObjects::instance().proxyManager()); iter->SetModeToOneGroup(); for (iter->Begin("sources"); ! iter->IsAtEndt(); iter->Next()) { iter->GetKey() ---> is the "label" for the proxy you see in the pipeline browser iter->GetProxy() -- > will be the actual proxy object, } To access parameters defined on them, you can access the "properties" on these proxies. If you know which property you're looking for using vtkSMPropertyHelper[3] to get the values e.g. sphereProxy = .. vtkSMPropertyHelper(sphereProxy, "Radius").GetAsDouble() --> the radius To iterate over all properties on the proxy, you can use vtkSMProxy::NewPropertyIterator [4] which will give you a new iterator (don't forget to call iter->Delete() once you're done with the iterator). You can use that to iterate over all properties on the proxy, Hope that helps, Utkarsh [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqActiveObjects.html#a547a93dececb0d5ac7a35f373e5c68ab [2] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMProxyIterator.html [3] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMPropertyHelper.html [4] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMProxy.html#ab0eee37fc2a021334964e9ffcd682a4c From bwvb at xs4all.nl Tue Sep 23 10:34:30 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 23 Sep 2014 16:34:30 +0200 Subject: [Paraview] useful plugin: how to do it, really? In-Reply-To: References: <54208CA1.7050907@xs4all.nl> Message-ID: <542184F6.6020209@xs4all.nl> Hello Utkarsh. Thanks for your response. I will need some time to digest and practice, but I will follow-up on your suggestions. Kind Regards, Bertwim On 09/23/2014 03:01 PM, Utkarsh Ayachit wrote: > Bertwim, > > I agree the developer docs are little scattered right now. My plan is > to start writing blog posts that make this easier to digest. One of > these, hopefully, I get around to it :). In the mean time, my replies > are inline. > > >> 1. Suppose I have created, interactively, a box, a sphere and a cone, >> using the corresponding entries in the "Sources" menu. >> >> 2. Now I would like to *programmatically* (i.e. in a c++ plugin) loop >> over the sources (here: the box, sphere and cone) and for each of the >> elements >> get hold of the parameters that were used to define these sources (i.e. >> the box dimensions, center, radii etc.). With these parameters I can >> then do other things to build my own extension, but those details do not >> matter here. > > Several ways for getting to the "proxies" for the sphere, box, etc. > created. One way it using the vtkSMSessionProxyManager. > > a. Using vtkSMSessionProxyManager: > a.1 Get access to the active session's proxy manager using > pqActiveObjects::instance().proxyManager() [1] > a.2 Use vtkSMProxyIterator[2] to iterate over the "sources" group. > vtkNew iter; > iter->SetSessionProxyManager(pqActiveObjects::instance().proxyManager()); > iter->SetModeToOneGroup(); > for (iter->Begin("sources"); ! iter->IsAtEndt(); iter->Next()) > { > iter->GetKey() ---> is the "label" for the proxy you see in the > pipeline browser > iter->GetProxy() -- > will be the actual proxy object, > } > > To access parameters defined on them, you can access the "properties" > on these proxies. If you know which property you're looking for using > vtkSMPropertyHelper[3] to get the values e.g. > > sphereProxy = .. > vtkSMPropertyHelper(sphereProxy, "Radius").GetAsDouble() --> the radius > > To iterate over all properties on the proxy, you can use > vtkSMProxy::NewPropertyIterator [4] which will give you a new iterator > (don't forget to call iter->Delete() once you're done with the > iterator). You can use that to iterate over all properties on the > proxy, > > Hope that helps, > Utkarsh > > [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqActiveObjects.html#a547a93dececb0d5ac7a35f373e5c68ab > [2] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMProxyIterator.html > [3] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMPropertyHelper.html > [4] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMProxy.html#ab0eee37fc2a021334964e9ffcd682a4c > > From simon.m.su.ctr at mail.mil Tue Sep 23 13:34:45 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 23 Sep 2014 17:34:45 +0000 Subject: [Paraview] python link error when compiling PV-v4.2.0-RC1-128-gc89b0ad + python-2.7.3 + VS2013 Express (UNCLASSIFIED) Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hello, I am trying to get a ParaView + vrpn running on a zSpace. With zSpace VRPN server only available on Windows, here goes the following... I am able to get ParaView build with ninja when I only do -DPARAVIEW_USE_MPI:BOOL=ON and the binary appears to be working. But when I included -DPARAVIEW_ENABLE_PYTHON:BOOL=ON I have linking problem. How do you make sure that I have a working Python library? Dumpbin is reporting python is x64 library and I am trying to compile a x64 ParaView. I am getting some 26 unresolved externals when ninja is "Creating library lib\vtkPythonInterpreter-pv4.2.lib and object lib\vtkPythonInterpreter-pv4.2.exp." and some 123 unresolved externals when ninja is "Creating library lib\vtkWrappingPython27Core-pv4.2.lib and object lib\vtkWrappingPython27Core-pv4.2.exp"- included at the end of this email. The odd thing is, both failed command has python27.lib library in it FAILED: cmd.exe /C "cd . && C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho nInterpreter.cxx.obj VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho nInteractiveInterpreter.cxx.obj /out:bin\vtkPythonInterpreter-pv4.2.dll /implib:lib\vtkPythonInterpreter-pv4.2.lib /pdb:bin\vtkPythonInterpreter-pv4.2.pdb /dll /version:1.0 /machine:x64 /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." And FAILED: cmd.exe /C "cd . && C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonArgs.c xx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonComman d.cxx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonOverlo ad.cxx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonUtil.c xx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkSmartPyObjec t.cxx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKClass.cxx. obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKMutableObj ect.cxx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKObject.cxx .obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKSpecialObj ect.cxx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKTemplate.c xx.obj /out:bin\vtkWrappingPython27Core-pv4.2.dll /implib:lib\vtkWrappingPython27Core-pv4.2.lib /pdb:bin\vtkWrappingPython27Core-pv4.2.pdb /dll /version:1.0 /machine:x64 /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." Do I have to included another python library? If so, what would that be? I am building a 64bit version of ParaView on Windows 7 using 1. VS2013 express version 2. Python-2.7.3 - release version build with cmake + ninja (https://github.com/davidsansome/python-cmake-buildsystem) cmake \ -DCMAKE_INSTALL_PREFIX=C:\tools\python\python-2.7.3 \ -DBUILD_SHARED:BOOL=ON \ -DCMAKE_BUILD_TYPE=Release \ -DZLIB_LIBRARY=C:\tools\zlib\zlib-1.2.8\lib\zlib.lib \ -DZLIB_INCLUDE_DIR=C:\tools\zlib\zlib-1.2.8\include \ ..\python-cmake-buildsystem -G Ninja \ ninja ninja install 3. Ninja-1.5.1 - build using the python-2.7.3 above so, python appears to work python bootstrap.py --x64 4. ParaView-v4.2.0-RC1-128-gc89b0ad git clone git://paraview.org/ParaView.git cd ParaView git pull git submodule update --init cmake \ -G Ninja \ -DCMAKE_INSTALL_PREFIX=C:\tools\ParaView\ParaView-v4.2.0-RC1-100-gfa06130 \ -DCMAKE_BUILD_TYPE=Release \ -DZLIB_LIBRARY=C:\tools\zlib\zlib-1.2.8\lib\zlib.lib \ -DZLIB_INCLUDE_DIR=C:\tools\zlib\zlib-1.2.8\include -DCMAKE_BUILD_TYPE=Release \ -DPARAVIEW_USE_MPI:BOOL=ON \ -DMPI_CXX_LIBRARIES:STRING="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi_cxx.li b" \ -DMPI_C_LIBRARIES:STRING="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi.lib" \ -DMPI_LIBRARY:FILEPATH="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi_cxx.lib" \ -DMPI_CXX_INCLUDE_PATH=C:/tools/openmpi/openmpi-1.4.4/include \ -DMPI_C_INCLUDE_PATH=C:/tools/openmpi/openmpi-1.4.4/include \ -DGLUT_glut_LIBRARY=C:\tools\freeglut\freeglut-2.8.1\lib\freeglut.lib \ -DGLUT_INCLUDE_DIR=C:\tools\freeglut\freeglut-2.8.1\include \ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ -DPYTHON_LIBRARY=C:\tools\python\python-2.7.3\libs\python27.lib \ -DPYTHON_INCLUDE_DIR=C:\tools\python\python-2.7.3\include \ -DPYTHON_EXECUTABLE=C:\tools\python\python-2.7.3\bin\python.exe \ ..\ParaView-v4.2.0-RC1-128-gc89b0ad ninja Any help is much appreciated. Thanks -simon ======================== linking error ======================= [1/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractCellLocato r.cxx.obj [2/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractPointLocat or.cxx.obj [3/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAdjacentVertexIter ator.cxx.obj [4/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRBox.cxx.obj [5/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRUtilities.cxx.o bj [6/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnimationScene.cxx .obj [7/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnnotation.cxx.obj [8/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnnotationLayers.c xx.obj [9/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkArrayData.cxx.obj [10/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAttributesErrorMet ric.cxx.obj [11/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuad.cx x.obj [12/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuadrat icHexahedron.cxx.obj [13/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuadrat icWedge.cxx.obj [14/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticTriangl e.cxx.obj [15/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBox.cxx.obj [16/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBSPCuts.cxx.obj [17/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBSPIntersections.c xx.obj [18/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCell3D.cxx.obj [19/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellArray.cxx.obj [20/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCell.cxx.obj [21/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellData.cxx.obj [22/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellIterator.cxx.o bj [23/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellLinks.cxx.obj [24/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellLocator.cxx.ob j [25/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellTypes.cxx.obj [26/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCompositeDataSet.c xx.obj [27/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCompositeDataItera tor.cxx.obj [28/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCone.cxx.obj [29/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkConvexPointSet.cxx .obj [30/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCubicLine.cxx.obj [31/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCylinder.cxx.obj [32/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetCellIterato r.cxx.obj [33/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectCollecti on.cxx.obj [34/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObject.cxx.obj [35/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTypes.cx x.obj [36/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTree.cxx .obj [37/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTreeIter ator.cxx.obj [38/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetAttributes. cxx.obj [39/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetCollection. cxx.obj [40/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSet.cxx.obj [41/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDirectedAcyclicGra ph.cxx.obj [42/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDirectedGraph.cxx. obj [43/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDistributedGraphHe lper.cxx.obj [44/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEdgeListIterator.c xx.obj [45/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEdgeTable.cxx.obj [46/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEmptyCell.cxx.obj [47/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkExplicitCell.cxx.o bj [48/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkExtractStructuredG ridHelper.cxx.obj [49/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkFieldData.cxx.obj [50/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAdaptorCell .cxx.obj [51/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAttributeCo llection.cxx.obj [52/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAttribute.c xx.obj [53/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCell.cxx.ob j [54/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCellIterato r.cxx.obj [55/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCellTessell ator.cxx.obj [56/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericDataSet.cxx .obj [57/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericEdgeTable.c xx.obj [58/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericInterpolate dVelocityField.cxx.obj [59/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericPointIterat or.cxx.obj [60/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericSubdivision ErrorMetric.cxx.obj [61/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGeometricErrorMetr ic.cxx.obj [62/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraph.cxx.obj [63/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraphEdge.cxx.obj [64/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraphInternals.cxx .obj [65/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHexagonalPrism.cxx .obj [66/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHexahedron.cxx.obj [67/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHierarchicalBoxDat aIterator.cxx.obj [68/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHierarchicalBoxDat aSet.cxx.obj [69/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctreeCursor. cxx.obj [70/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctree.cxx.ob j [71/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctreePointsG rabber.cxx.obj [72/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTree.cxx.obj [73/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTreeCursor.cx x.obj [74/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTreeGrid.cxx. obj [75/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImageData.cxx.obj [76/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImageIterator.cxx. obj [77/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitBoolean.cx x.obj [78/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitDataSet.cx x.obj [79/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitFunctionCo llection.cxx.obj [80/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitFunction.c xx.obj [81/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitHalo.cxx.o bj [82/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitSelectionL oop.cxx.obj [83/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitSum.cxx.ob j [84/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitVolume.cxx .obj [85/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitWindowFunc tion.cxx.obj [86/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalOctreeN ode.cxx.obj [87/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalOctreeP ointLocator.cxx.obj [88/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalPointLo cator.cxx.obj [89/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkInEdgeIterator.cxx .obj [90/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkInformationQuadrat ureSchemeDefinitionVectorKey.cxx.obj [91/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIterativeClosestPo intTransform.cxx.obj [92/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdNode.cxx.obj [93/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdTree.cxx.obj [94/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdTreePointLocator .cxx.obj [95/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkLine.cxx.obj [96/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkLocator.cxx.obj [97/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMarchingSquaresLin eCases.cxx.obj [98/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMarchingCubesTrian gleCases.cxx.obj [99/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMeanValueCoordinat esInterpolator.cxx.obj [100/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMergePoints.cxx.ob j [101/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMultiBlockDataSet. cxx.obj [102/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMultiPieceDataSet. cxx.obj [103/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMutableDirectedGra ph.cxx.obj [104/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMutableUndirectedG raph.cxx.obj [105/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonLinearCell.cxx. obj [106/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonMergingPointLoc ator.cxx.obj [107/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOctreePointLocator .cxx.obj [108/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOctreePointLocator Node.cxx.obj [109/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOrderedTriangulato r.cxx.obj [110/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOutEdgeIterator.cx x.obj [111/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPath.cxx.obj [112/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPentagonalPrism.cx x.obj [113/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPerlinNoise.cxx.ob j [114/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPiecewiseFunction. cxx.obj [115/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPixel.cxx.obj [116/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPixelExtent.cxx.ob j [117/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlaneCollection.cx x.obj [118/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlane.cxx.obj [119/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlanes.cxx.obj [120/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlanesIntersection .cxx.obj [121/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointData.cxx.obj [122/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointLocator.cxx.o bj [123/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointSet.cxx.obj [124/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointSetCellIterat or.cxx.obj [125/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointsProjectedHul l.cxx.obj [126/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyDataCollection .cxx.obj [127/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyData.cxx.obj [128/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolygon.cxx.obj [129/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyhedron.cxx.obj [130/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyLine.cxx.obj [131/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyPlane.cxx.obj [132/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyVertex.cxx.obj [133/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPyramid.cxx.obj [134/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuad.cxx.obj [135/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticEdge.cxx. obj [136/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticHexahedro n.cxx.obj [137/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticLinearQua d.cxx.obj [138/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticLinearWed ge.cxx.obj [139/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticPolygon.c xx.obj [140/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticPyramid.c xx.obj [141/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticQuad.cxx. obj [142/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticTetra.cxx .obj [143/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticTriangle. cxx.obj [144/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticWedge.cxx .obj [145/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadratureSchemeDe finition.cxx.obj [146/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadric.cxx.obj [147/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkRectilinearGrid.cx x.obj [148/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkReebGraph.cxx.obj [149/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkReebGraphSimplific ationMetric.cxx.obj [150/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSelection.cxx.obj [151/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSelectionNode.cxx. obj [152/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSimpleCellTessella tor.cxx.obj [153/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSmoothErrorMetric. cxx.obj [154/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSphere.cxx.obj [155/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSpline.cxx.obj [156/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredData.cxx .obj [157/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredExtent.c xx.obj [158/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredGrid.cxx .obj [159/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredPointsCo llection.cxx.obj [160/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredPoints.c xx.obj [161/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredVisibili tyConstraint.cxx.obj [162/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSuperquadric.cxx.o bj [163/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTable.cxx.obj [164/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTensor.cxx.obj [165/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTetra.cxx.obj [166/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeBFSIterator.cx x.obj [167/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTree.cxx.obj [168/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeDFSIterator.cx x.obj [169/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriangle.cxx.obj [170/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriangleStrip.cxx. obj [171/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriQuadraticHexahe dron.cxx.obj [172/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUndirectedGraph.cx x.obj [173/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGrid.cxx.ob j [174/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGrid.c xx.obj [175/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGridBa se.cxx.obj [176/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGridCe llIterator.cxx.obj [177/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVertex.cxx.obj [178/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVertexListIterator .cxx.obj [179/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVoxel.cxx.obj [180/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkWedge.cxx.obj [181/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkXMLDataElement.cxx .obj [182/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeIterator.cxx.o bj [183/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBoundingBox.cxx.ob j [184/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAtom.cxx.obj [185/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBond.cxx.obj [186/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMolecule.cxx.obj [187/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractElectronic Data.cxx.obj [188/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonOverlappingAMR. cxx.obj [189/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOverlappingAMR.cxx .obj [190/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRInformation.cxx .obj [191/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRDataInternals.c xx.obj [192/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGridAMR.cxx .obj [193/16592] Building CXX object VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGridAMRData Iterator.cxx.obj [194/16592] Linking CXX shared library bin\vtkPythonInterpreter-pv4.2.dll [195/16592] Linking CXX shared library bin\vtkWrappingPython27Core-pv4.2.dll FAILED: cmd.exe /C "cd . && C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho nInterpreter.cxx.obj VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho nInteractiveInterpreter.cxx.obj /out:bin\vtkPythonInterpreter-pv4.2.dll /implib:lib\vtkPythonInterpreter-pv4.2.lib /pdb:bin\vtkPythonInterpreter-pv4.2.pdb /dll /version:1.0 /machine:x64 /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." Creating library lib\vtkPythonInterpreter-pv4.2.lib and object lib\vtkPythonInterpreter-pv4.2.exp vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyType_IsSubtype referenced in function "struct _object * __cdecl vtkWrite(struct _object *,struct _object *)" (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyType_Ready referenced in function "public: static bool __cdecl vtkPythonInterpreter::Initialize(int)" (?Initialize at vtkPythonInterpreter@@SA_NH at Z) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_GenericGetAttr referenced in function "void __cdecl `dynamic initializer for 'vtkPythonStdStreamCaptureHelperType''(void)" (??__EvtkPythonStdStreamCaptureHelperType@@YAXXZ) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_GenericSetAttr referenced in function "void __cdecl `dynamic initializer for 'vtkPythonStdStreamCaptureHelperType''(void)" (??__EvtkPythonStdStreamCaptureHelperType@@YAXXZ) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp__PyObject_New referenced in function "public: static bool __cdecl vtkPythonInterpreter::Initialize(int)" (?Initialize at vtkPythonInterpreter@@SA_NH at Z) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyString_FromString referenced in function "public: static bool __cdecl vtkPythonInterpreter::Initialize(int)" (?Initialize at vtkPythonInterpreter@@SA_NH at Z) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromString vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyList_Insert referenced in function "public: static bool __cdecl vtkPythonInterpreter::Initialize(int)" (?Initialize at vtkPythonInterpreter@@SA_NH at Z) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyArg_ParseTuple referenced in function "struct _object * __cdecl vtkWrite(struct _object *,struct _object *)" (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_BuildValue referenced in function "struct _object * __cdecl vtkWrite(struct _object *,struct _object *)" (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_SetProgramName referenced in function "public: static void __cdecl vtkPythonInterpreter::SetProgramName(char const *)" (?SetProgramName at vtkPythonInterpreter@@SAXPEBD at Z) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_InitializeEx referenced in function "public: static bool __cdecl vtkPythonInterpreter::Initialize(int)" (?Initialize at vtkPythonInterpreter@@SA_NH at Z) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_Finalize referenced in function "public: static void __cdecl vtkPythonInterpreter::Finalize(void)" (?Finalize at vtkPythonInterpreter@@SAXXZ) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_IsInitialized referenced in function "public: static void __cdecl vtkPythonInterpreter::Finalize(void)" (?Finalize at vtkPythonInterpreter@@SAXXZ) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyRun_SimpleStringFlags referenced in function "public: static void __cdecl vtkPythonInterpreter::RunSimpleString(char const *)" (?RunSimpleString at vtkPythonInterpreter@@SAXPEBD at Z) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external symbol __imp_PyRun_SimpleStringFlags vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_Main referenced in function "public: static int __cdecl vtkPythonInterpreter::PyMain(int,char * *)" (?PyMain at vtkPythonInterpreter@@SAHHPEAPEAD at Z) vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PySys_GetObject referenced in function "public: static bool __cdecl vtkPythonInterpreter::Initialize(int)" (?Initialize at vtkPythonInterpreter@@SA_NH at Z) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external symbol __imp_PySys_GetObject vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PySys_SetObject referenced in function "public: static bool __cdecl vtkPythonInterpreter::Initialize(int)" (?Initialize at vtkPythonInterpreter@@SA_NH at Z) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external symbol __imp_PySys_SetObject vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_GetItemString referenced in function "public: struct _object * __cdecl vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE AU_object@@XZ) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyModule_GetDict referenced in function "public: struct _object * __cdecl vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE AU_object@@XZ) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyErr_Clear referenced in function "public: int __cdecl vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyArg_Parse referenced in function "public: bool __cdecl vtkPythonInteractiveInterpreter::Push(char const * const)" (?Push at vtkPythonInteractiveInterpreter@@QEAA_NQEBD at Z) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyRun_StringFlags referenced in function "public: int __cdecl vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyErr_Print referenced in function "public: int __cdecl vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_FlushLine referenced in function "public: int __cdecl vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyImport_AddModule referenced in function "public: struct _object * __cdecl vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE AU_object@@XZ) vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_CallMethod referenced in function "public: bool __cdecl vtkPythonInteractiveInterpreter::Push(char const * const)" (?Push at vtkPythonInteractiveInterpreter@@QEAA_NQEBD at Z) bin\vtkPythonInterpreter-pv4.2.dll : fatal error LNK1120: 26 unresolved externals LINK failed. with 1120 FAILED: cmd.exe /C "cd . && C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonArgs.c xx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonComman d.cxx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonOverlo ad.cxx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonUtil.c xx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkSmartPyObjec t.cxx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKClass.cxx. obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKMutableObj ect.cxx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKObject.cxx .obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKSpecialObj ect.cxx.obj VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKTemplate.c xx.obj /out:bin\vtkWrappingPython27Core-pv4.2.dll /implib:lib\vtkWrappingPython27Core-pv4.2.lib /pdb:bin\vtkWrappingPython27Core-pv4.2.pdb /dll /version:1.0 /machine:x64 /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." Creating library lib\vtkWrappingPython27Core-pv4.2.lib and object lib\vtkWrappingPython27Core-pv4.2.exp vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyType_IsSubtype referenced in function "bool __cdecl vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyType_IsSubtype PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyType_IsSubtype vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_IsTrue referenced in function "bool __cdecl vtkPythonGetArray(struct _object *,bool *,int)" (??$vtkPythonGetArray at _N@@YA_NPEAU_object@@PEA_NH at Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_IsTrue PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_IsTrue vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyCallable_Check referenced in function "public: bool __cdecl vtkPythonArgs::GetFunction(struct _object * &)" (?GetFunction at vtkPythonArgs@@QEAA_NAEAPEAU_object@@@Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyCallable_Check PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyCallable_Check vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp__PyUnicodeUCS2_AsDefaultEncodedString referenced in function "bool __cdecl vtkPythonGetStringValue(struct _object *,char const * &,char const *)" (??$vtkPythonGetStringValue@$$CBD@@YA_NPEAU_object@@AEAPEBDPEBD at Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyUnicodeUCS2_DecodeUTF8 referenced in function "public: static struct _object * __cdecl vtkPythonArgs::BuildValue(class vtkUnicodeString const &)" (?BuildValue at vtkPythonArgs@@SAPEAU_object@@AEBVvtkUnicodeString@@@Z) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyUnicodeUCS2_DecodeUTF8 vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyUnicodeUCS2_AsUTF8String referenced in function "bool __cdecl vtkPythonGetValue(struct _object *,class vtkUnicodeString &)" (?vtkPythonGetValue@@YA_NPEAU_object@@AEAVvtkUnicodeString@@@Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyInt_FromLong referenced in function "struct _object * __cdecl vtkPythonBuildTuple(signed char const *,int)" (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol __imp_PyInt_FromLong PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyInt_FromLong vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyInt_AsLong referenced in function "bool __cdecl vtkPythonGetUnsignedLongLongValue(struct _object *,unsigned __int64 &)" (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol __imp_PyInt_AsLong vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyInt_AsLong vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyBool_FromLong referenced in function "struct _object * __cdecl vtkPythonBuildTuple(bool const *,int)" (??$vtkPythonBuildTuple at _N@@YAPEAU_object@@PEB_NH at Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyLong_FromUnsignedLong referenced in function "struct _object * __cdecl vtkPythonBuildTuple(unsigned int const *,int)" (??$vtkPythonBuildTuple at I@@YAPEAU_object@@PEBIH at Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyLong_AsUnsignedLong referenced in function "bool __cdecl vtkPythonGetValue(struct _object *,unsigned int &)" (?vtkPythonGetValue@@YA_NPEAU_object@@AEAI at Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyLong_FromLongLong referenced in function "struct _object * __cdecl vtkPythonBuildTuple<__int64>(__int64 const *,int)" (??$vtkPythonBuildTuple at _J@@YAPEAU_object@@PEB_JH at Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyLong_FromUnsignedLongLong referenced in function "struct _object * __cdecl vtkPythonBuildTuple(unsigned __int64 const *,int)" (??$vtkPythonBuildTuple at _K@@YAPEAU_object@@PEB_KH at Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyLong_AsLongLong referenced in function "bool __cdecl vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyLong_AsLongLong vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyLong_AsUnsignedLongLong referenced in function "bool __cdecl vtkPythonGetUnsignedLongLongValue(struct _object *,unsigned __int64 &)" (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyFloat_FromDouble referenced in function "struct _object * __cdecl vtkPythonBuildTuple(float const *,int)" (??$vtkPythonBuildTuple at M@@YAPEAU_object@@PEBMH at Z) vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol __imp_PyFloat_FromDouble vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyFloat_AsDouble referenced in function "bool __cdecl vtkPythonGetArray(struct _object *,float *,int)" (??$vtkPythonGetArray at M@@YA_NPEAU_object@@PEAMH at Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyFloat_AsDouble vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyString_FromStringAndSize referenced in function "public: static struct _object * __cdecl vtkPythonArgs::BuildBytes(char const *,int)" (?BuildBytes at vtkPythonArgs@@SAPEAU_object@@PEBDH at Z) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromStringAndSize PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromStringAndSize PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromStringAndSize PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromString PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromString PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromString PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromString vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyString_FromString referenced in function "bool __cdecl vtkPythonSetArray(struct _object *,char const *,int)" (??$vtkPythonSetArray at D@@YA_NPEAU_object@@PEBDH at Z) vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromString vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromString PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_FromString PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_AsString PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_AsString PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_AsString PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol __imp_PyString_AsString referenced in function "public: __cdecl std::error_category::error_category(void)" (??0error_category at std@@QEAA at XZ) vtkPythonArgs.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_AsString vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_AsString vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_AsString PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_AsString vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyString_AsStringAndSize referenced in function "bool __cdecl vtkPythonGetStdStringValue(struct _object *,class std::basic_string,class std::allocator > &,char const *)" (?vtkPythonGetStdStringValue@@YA_NPEAU_object@@AEAV?$basic_string at DU?$char_t raits at D@std@@V?$allocator at D@2@@std@@PEBD at Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyTuple_New referenced in function "struct _object * __cdecl vtkPythonBuildTuple(signed char const *,int)" (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyTuple_New PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp_PyTuple_New PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyTuple_New PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_SetString PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_SetString PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_SetString PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol __imp_PyErr_SetString referenced in function "public: __cdecl std::_Generic_error_category::_Generic_error_category(void)" (??0_Generic_error_category at std@@QEAA at XZ) vtkPythonArgs.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_SetString vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_SetString vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_SetString PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_SetString vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyErr_Occurred referenced in function "bool __cdecl vtkPythonGetArray(struct _object *,float *,int)" (??$vtkPythonGetArray at M@@YA_NPEAU_object@@PEAMH at Z) vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_Occurred vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_Occurred vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_Occurred vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyErr_Fetch referenced in function "protected: bool __cdecl vtkPythonArgs::RefineArgTypeError(int)" (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyErr_Restore referenced in function "protected: bool __cdecl vtkPythonArgs::RefineArgTypeError(int)" (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyErr_ExceptionMatches referenced in function "protected: bool __cdecl vtkPythonArgs::RefineArgTypeError(int)" (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_ExceptionMatches vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_ExceptionMatches PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_ExceptionMatches vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PySequence_Check referenced in function "bool __cdecl vtkPythonGetArray(struct _object *,signed char *,int)" (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PySequence_Check vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PySequence_Size referenced in function "bool __cdecl vtkPythonGetArray(struct _object *,signed char *,int)" (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PySequence_Size PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PySequence_Size vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PySequence_GetItem referenced in function "bool __cdecl vtkPythonGetArray(struct _object *,signed char *,int)" (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PySequence_GetItem PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PySequence_GetItem vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PySequence_SetItem referenced in function "bool __cdecl vtkPythonSetArray(struct _object *,signed char const *,int)" (??$vtkPythonSetArray at C@@YA_NPEAU_object@@PEBCH at Z) PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp__Py_NoneStruct PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp__Py_NoneStruct PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp__Py_NoneStruct vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp__Py_NoneStruct referenced in function "struct _object * __cdecl vtkPythonBuildTuple(signed char const *,int)" (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol __imp__Py_NoneStruct vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp__Py_NoneStruct vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp__Py_NoneStruct vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyFloat_Type referenced in function "bool __cdecl vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyFloat_Type PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyFloat_Type vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyExc_OverflowError referenced in function "bool __cdecl vtkPythonGetUnsignedLongLongValue(struct _object *,unsigned __int64 &)" (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_TypeError PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_TypeError PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_TypeError vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyExc_TypeError referenced in function "bool __cdecl vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_TypeError vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_TypeError PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_TypeError PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_ValueError vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol __imp_PyExc_ValueError referenced in function "protected: bool __cdecl vtkPythonArgs::RefineArgTypeError(int)" (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_ValueError PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_ValueError PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_ValueError vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_GetAttrString referenced in function "public: virtual void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_GetAttrString PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_GetAttrString vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol __imp_PyLong_FromLong referenced in function "public: virtual void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_Clear PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_Clear vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol __imp_PyErr_Clear referenced in function "struct _object * __cdecl `anonymous namespace'::BuildCallDataArgList(struct _object *,char const *,struct _object *)" (?BuildCallDataArgList@?A0xfc44b691@@YAPEAU_object@@PEAU2 at PEBD0@Z) vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_Clear vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_Clear PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_Clear vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol __imp_PyThreadState_Swap referenced in function "public: virtual void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_Py_BuildValue vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_BuildValue referenced in function "struct _object * __cdecl `anonymous namespace'::BuildCallDataArgList(struct _object *,char const *,struct _object *)" (?BuildCallDataArgList@?A0xfc44b691@@YAPEAU_object@@PEAU2 at PEBD0@Z) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_Py_BuildValue PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp_Py_BuildValue PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_Py_BuildValue vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_IsInitialized referenced in function "protected: virtual __cdecl vtkPythonCommand::~vtkPythonCommand(void)" (??1vtkPythonCommand@@MEAA at XZ) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_Py_IsInitialized vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol __imp_PyErr_Print referenced in function "public: virtual void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyErr_Print vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_Exit referenced in function "public: virtual void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_Py_Exit vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol __imp_PyEval_CallObjectWithKeywords referenced in function "public: virtual void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyEval_CallObjectWithKeywords PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp_PyEval_CallObjectWithKeywords PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyEval_CallObjectWithKeywords vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol __imp_PyExc_KeyboardInterrupt referenced in function "public: virtual void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_KeyboardInterrupt vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol __imp_PyString_Size referenced in function "public: static int __cdecl vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyString_Size vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol __imp_PyTuple_Size referenced in function "public: static int __cdecl vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol __imp_PyTuple_Size PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyTuple_Size vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol __imp_PyBool_Type referenced in function "public: static int __cdecl vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_Hash referenced in function "public: static long __cdecl vtkPythonUtil::VariantHash(class vtkVariant const *)" (?VariantHash at vtkPythonUtil@@SAJPEBVvtkVariant@@@Z) vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol __imp__Py_HashPointer referenced in function "public: static long __cdecl vtkPythonUtil::VariantHash(class vtkVariant const *)" (?VariantHash at vtkPythonUtil@@SAJPEBVvtkVariant@@@Z) vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol __imp__PyString_Resize referenced in function "public: static struct _object * __cdecl vtkPythonUtil::BuildDocString(char const * * const)" (?BuildDocString at vtkPythonUtil@@SAPEAU_object@@QEAPEBD at Z) vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_Size referenced in function "public: static void __cdecl vtkPythonUtil::RemoveObjectFromMap(struct _object *)" (?RemoveObjectFromMap at vtkPythonUtil@@SAXPEAU_object@@@Z) PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyDict_Size vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol __imp_PyErr_GivenExceptionMatches referenced in function "public: static void * __cdecl vtkPythonUtil::GetPointerFromSpecialObject(struct _object *,char const *,struct _object * *)" (?GetPointerFromSpecialObject at vtkPythonUtil@@SAPEAXPEAU_object@@PEBDPEAPEAU2 @@Z) vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_AtExit referenced in function "public: static void __cdecl vtkPythonUtil::AddClassToMap(struct _object *,char const *)" (?AddClassToMap at vtkPythonUtil@@SAXPEAU_object@@PEBD at Z) PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_GetAttr referenced in function "struct _object * __cdecl PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_GetAttr PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp__PyObject_GC_New referenced in function "struct _object * __cdecl PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp__PyObject_GC_New PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp__PyObject_GC_New PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_GC_Track referenced in function "struct _object * __cdecl PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_GC_Track PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_GC_Track PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_GC_UnTrack referenced in function "void __cdecl PyVTKClass_Delete(struct _object *)" (?PyVTKClass_Delete@@YAXPEAU_object@@@Z) PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_GC_UnTrack PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_GC_UnTrack PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_GC_Del referenced in function "void __cdecl PyVTKClass_Delete(struct _object *)" (?PyVTKClass_Delete@@YAXPEAU_object@@@Z) PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_GC_Del PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_GC_Del PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyString_InternFromString referenced in function PyVTKClass_New PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyTuple_GetItem referenced in function "struct _object * __cdecl PyVTKClass_GetAttr(struct _object *,struct _object *)" (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyTuple_GetItem PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_New referenced in function "struct _object * __cdecl PyVTKClass_GetAttr(struct _object *,struct _object *)" (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyDict_New PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyDict_New PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_GetItem referenced in function "struct _object * __cdecl PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyDict_GetItem PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_Keys referenced in function "struct _object * __cdecl PyVTKClass_Dir(struct _object *,struct _object *)" (?PyVTKClass_Dir@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_Update referenced in function "struct _object * __cdecl PyVTKClass_Dir(struct _object *,struct _object *)" (?PyVTKClass_Dir@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_GetItemString referenced in function "struct _object * __cdecl PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_SetItemString referenced in function "struct _object * __cdecl PyVTKClass_GetAttr(struct _object *,struct _object *)" (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyDict_SetItemString PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_DelItemString referenced in function "struct _object * __cdecl PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyCFunction_NewEx referenced in function "struct _object * __cdecl PyVTKClass_GetAttr(struct _object *,struct _object *)" (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyCFunction_NewEx PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyCFunction_NewEx PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyArg_ParseTuple referenced in function "struct _object * __cdecl PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyArg_ParseTuple PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyArg_ParseTuple PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyArg_ParseTupleAndKeywords referenced in function "struct _object * __cdecl PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyEval_GetGlobals referenced in function "struct _object * __cdecl PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyType_Type referenced in function "void __cdecl `dynamic initializer for 'PyVTKClassMetaType''(void)" (??__EPyVTKClassMetaType@@YAXXZ) PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyType_Type PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyType_Type PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyType_Type PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyClass_Type referenced in function "void __cdecl `dynamic initializer for 'PyVTKClass_Type''(void)" (??__EPyVTKClass_Type@@YAXXZ) PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol __imp_PyExc_AttributeError referenced in function "struct _object * __cdecl PyVTKClass_GetAttr(struct _object *,struct _object *)" (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_AttributeError PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_AttributeError PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyExc_AttributeError PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_Repr referenced in function "struct _object * __cdecl PyVTKMutableObject_Repr(struct _object *)" (?PyVTKMutableObject_Repr@@YAPEAU_object@@PEAU1@@Z) PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_Repr PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_Str referenced in function "struct _object * __cdecl PyVTKMutableObject_Str(struct _object *)" (?PyVTKMutableObject_Str@@YAPEAU_object@@PEAU1@@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_RichCompare referenced in function "struct _object * __cdecl PyVTKMutableObject_RichCompare(struct _object *,struct _object *,int)" (?PyVTKMutableObject_RichCompare@@YAPEAU_object@@PEAU1 at 0H@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_GenericGetAttr referenced in function "struct _object * __cdecl PyVTKMutableObject_GetAttr(struct _object *,struct _object *)" (?PyVTKMutableObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_HashNotImplemented referenced in function "void __cdecl `dynamic initializer for 'PyVTKMutableObject_Type''(void)" (??__EPyVTKMutableObject_Type@@YAXXZ) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_CoerceEx referenced in function "int __cdecl PyVTKMutableObject_Coerce(struct _object * *,struct _object * *)" (?PyVTKMutableObject_Coerce@@YAHPEAPEAU_object@@0 at Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_Free referenced in function "void __cdecl `dynamic initializer for 'PyVTKMutableObject_Type''(void)" (??__EPyVTKMutableObject_Type@@YAXXZ) PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyObject_Free PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp__PyObject_New referenced in function "struct _object * __cdecl PyVTKMutableObject_New(struct _typeobject *,struct _object *,struct _object *)" (?PyVTKMutableObject_New@@YAPEAU_object@@PEAU_typeobject@@PEAU1 at 1@Z) PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol __imp__PyObject_New PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Add referenced in function "struct _object * __cdecl PyVTKMutableObject_Add(struct _object *,struct _object *)" (?PyVTKMutableObject_Add@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Subtract referenced in function "struct _object * __cdecl PyVTKMutableObject_Subtract(struct _object *,struct _object *)" (?PyVTKMutableObject_Subtract@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Multiply referenced in function "struct _object * __cdecl PyVTKMutableObject_Multiply(struct _object *,struct _object *)" (?PyVTKMutableObject_Multiply@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Divide referenced in function "struct _object * __cdecl PyVTKMutableObject_Divide(struct _object *,struct _object *)" (?PyVTKMutableObject_Divide@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_FloorDivide referenced in function "struct _object * __cdecl PyVTKMutableObject_FloorDivide(struct _object *,struct _object *)" (?PyVTKMutableObject_FloorDivide@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_TrueDivide referenced in function "struct _object * __cdecl PyVTKMutableObject_TrueDivide(struct _object *,struct _object *)" (?PyVTKMutableObject_TrueDivide@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Remainder referenced in function "struct _object * __cdecl PyVTKMutableObject_Remainder(struct _object *,struct _object *)" (?PyVTKMutableObject_Remainder@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Divmod referenced in function "struct _object * __cdecl PyVTKMutableObject_Divmod(struct _object *,struct _object *)" (?PyVTKMutableObject_Divmod@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Power referenced in function "struct _object * __cdecl PyVTKMutableObject_Power(struct _object *,struct _object *,struct _object *)" (?PyVTKMutableObject_Power@@YAPEAU_object@@PEAU1 at 00@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Negative referenced in function "struct _object * __cdecl PyVTKMutableObject_Negative(struct _object *)" (?PyVTKMutableObject_Negative@@YAPEAU_object@@PEAU1@@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Positive referenced in function "struct _object * __cdecl PyVTKMutableObject_Positive(struct _object *)" (?PyVTKMutableObject_Positive@@YAPEAU_object@@PEAU1@@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Absolute referenced in function "struct _object * __cdecl PyVTKMutableObject_Absolute(struct _object *)" (?PyVTKMutableObject_Absolute@@YAPEAU_object@@PEAU1@@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Invert referenced in function "struct _object * __cdecl PyVTKMutableObject_Invert(struct _object *)" (?PyVTKMutableObject_Invert@@YAPEAU_object@@PEAU1@@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Lshift referenced in function "struct _object * __cdecl PyVTKMutableObject_Lshift(struct _object *,struct _object *)" (?PyVTKMutableObject_Lshift@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Rshift referenced in function "struct _object * __cdecl PyVTKMutableObject_InPlaceRshift(struct _object *,struct _object *)" (?PyVTKMutableObject_InPlaceRshift@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_And referenced in function "struct _object * __cdecl PyVTKMutableObject_InPlaceAnd(struct _object *,struct _object *)" (?PyVTKMutableObject_InPlaceAnd@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Xor referenced in function "struct _object * __cdecl PyVTKMutableObject_InPlaceXor(struct _object *,struct _object *)" (?PyVTKMutableObject_InPlaceXor@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Or referenced in function "struct _object * __cdecl PyVTKMutableObject_InPlaceOr(struct _object *,struct _object *)" (?PyVTKMutableObject_InPlaceOr@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Index referenced in function "struct _object * __cdecl PyVTKMutableObject_Index(struct _object *)" (?PyVTKMutableObject_Index@@YAPEAU_object@@PEAU1@@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Int referenced in function "struct _object * __cdecl PyVTKMutableObject_Int(struct _object *)" (?PyVTKMutableObject_Int@@YAPEAU_object@@PEAU1@@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Long referenced in function "struct _object * __cdecl PyVTKMutableObject_Long(struct _object *)" (?PyVTKMutableObject_Long@@YAPEAU_object@@PEAU1@@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_Float referenced in function "struct _object * __cdecl PyVTKMutableObject_Float(struct _object *)" (?PyVTKMutableObject_Float@@YAPEAU_object@@PEAU1@@Z) PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyNumber_ToBase referenced in function "struct _object * __cdecl PyVTKMutableObject_Hex(struct _object *)" (?PyVTKMutableObject_Hex@@YAPEAU_object@@PEAU1@@Z) PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_ClearWeakRefs referenced in function "void __cdecl PyVTKObject_Delete(struct _object *)" (?PyVTKObject_Delete@@YAXPEAU_object@@@Z) PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_SetItem referenced in function "int __cdecl PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol __imp_PyDict_SetItem PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyDict_DelItem referenced in function "int __cdecl PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyMethod_New referenced in function "struct _object * __cdecl PyVTKObject_GetAttr(struct _object *,struct _object *)" (?PyVTKObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyCFunction_Type referenced in function "struct _object * __cdecl PyVTKObject_GetAttr(struct _object *,struct _object *)" (?PyVTKObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyExc_RuntimeError referenced in function "int __cdecl PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyExc_NotImplementedError referenced in function PyVTKObject_New PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyType_Ready referenced in function PyVTKSpecialType_New PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_ReprEnter referenced in function PyVTKSpecialObject_SequenceString PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol __imp_Py_ReprLeave referenced in function PyVTKSpecialObject_SequenceString PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyString_Concat referenced in function PyVTKSpecialObject_SequenceString PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyString_ConcatAndDel referenced in function PyVTKSpecialObject_Repr PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol __imp_PyBaseObject_Type referenced in function PyVTKSpecialObject_Repr PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_CallMethod referenced in function "struct _object * __cdecl PyVTKTemplate_HasKey(struct _object *,struct _object *)" (?PyVTKTemplate_HasKey@@YAPEAU_object@@PEAU1 at 0@Z) PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_Size referenced in function "__int64 __cdecl PyVTKTemplate_Size(struct _object *)" (?PyVTKTemplate_Size@@YA_JPEAU_object@@@Z) PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol __imp_PyObject_GetItem referenced in function "struct _object * __cdecl PyVTKTemplate_GetItem(struct _object *,struct _object *)" (?PyVTKTemplate_GetItem@@YAPEAU_object@@PEAU1 at 0@Z) bin\vtkWrappingPython27Core-pv4.2.dll : fatal error LNK1120: 123 unresolved externals LINK failed. with 1120 ninja: build stopped: subcommand failed. Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Sep 23 15:17:22 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 23 Sep 2014 15:17:22 -0400 Subject: [Paraview] python link error when compiling PV-v4.2.0-RC1-128-gc89b0ad + python-2.7.3 + VS2013 Express (UNCLASSIFIED) In-Reply-To: References: Message-ID: Simon, As this states [1], superbuild on Windows with Python is only supported for VS 2008 currently. We will soon add support for VS2013. If you want to use VS2013, using USE_SYSTEM_python=ON may be worth a try, but these was a discussion on the mailing list a little while ago that too may have problems -- but it wasn't clear if it was build problem, or an environment issue. Worth a shot, however. [1] http://www.paraview.org/Wiki/ParaView/Superbuild#Windows On Tue, Sep 23, 2014 at 1:34 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > I am trying to get a ParaView + vrpn running on a zSpace. With zSpace VRPN > server only available on Windows, here goes the following... > > I am able to get ParaView build with ninja when I only do > -DPARAVIEW_USE_MPI:BOOL=ON and the binary appears to be working. But when I > included > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > I have linking problem. How do you make sure that I have a working Python > library? Dumpbin is reporting python is x64 library and I am trying to > compile a x64 ParaView. > > I am getting some 26 unresolved externals when ninja is "Creating library > lib\vtkPythonInterpreter-pv4.2.lib and object > lib\vtkPythonInterpreter-pv4.2.exp." and some 123 unresolved externals when > ninja is "Creating library lib\vtkWrappingPython27Core-pv4.2.lib and object > lib\vtkWrappingPython27Core-pv4.2.exp"- included at the end of this email. > > The odd thing is, both failed command has python27.lib library in it > > FAILED: cmd.exe /C "cd . && > C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll > C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo > VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho > nInterpreter.cxx.obj > VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho > nInteractiveInterpreter.cxx.obj /out:bin\vtkPythonInterpreter-pv4.2.dll > /implib:lib\vtkPythonInterpreter-pv4.2.lib > /pdb:bin\vtkPythonInterpreter-pv4.2.pdb /dll /version:1.0 /machine:x64 > /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib > C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib > Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib > ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." > > And > > FAILED: cmd.exe /C "cd . && > C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll > C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonArgs.c > xx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonComman > d.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonOverlo > ad.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonUtil.c > xx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkSmartPyObjec > t.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKClass.cxx. > obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKMutableObj > ect.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKObject.cxx > .obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKSpecialObj > ect.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKTemplate.c > xx.obj /out:bin\vtkWrappingPython27Core-pv4.2.dll > /implib:lib\vtkWrappingPython27Core-pv4.2.lib > /pdb:bin\vtkWrappingPython27Core-pv4.2.pdb /dll /version:1.0 /machine:x64 > /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib > C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib > Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib > ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." > > Do I have to included another python library? If so, what would that be? > > > I am building a 64bit version of ParaView on Windows 7 using > 1. VS2013 express version > 2. Python-2.7.3 - release version build with cmake + ninja > (https://github.com/davidsansome/python-cmake-buildsystem) > cmake \ > -DCMAKE_INSTALL_PREFIX=C:\tools\python\python-2.7.3 \ > -DBUILD_SHARED:BOOL=ON \ > -DCMAKE_BUILD_TYPE=Release \ > -DZLIB_LIBRARY=C:\tools\zlib\zlib-1.2.8\lib\zlib.lib \ > -DZLIB_INCLUDE_DIR=C:\tools\zlib\zlib-1.2.8\include \ > ..\python-cmake-buildsystem -G Ninja \ > ninja > ninja install > > 3. Ninja-1.5.1 - build using the python-2.7.3 above so, python appears to > work > python bootstrap.py --x64 > > 4. ParaView-v4.2.0-RC1-128-gc89b0ad > > git clone git://paraview.org/ParaView.git > cd ParaView > git pull > git submodule update --init > > cmake \ > -G Ninja \ > -DCMAKE_INSTALL_PREFIX=C:\tools\ParaView\ParaView-v4.2.0-RC1-100-gfa06130 \ > -DCMAKE_BUILD_TYPE=Release \ > -DZLIB_LIBRARY=C:\tools\zlib\zlib-1.2.8\lib\zlib.lib \ > -DZLIB_INCLUDE_DIR=C:\tools\zlib\zlib-1.2.8\include > -DCMAKE_BUILD_TYPE=Release \ > -DPARAVIEW_USE_MPI:BOOL=ON \ > -DMPI_CXX_LIBRARIES:STRING="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi_cxx.li > b" \ > -DMPI_C_LIBRARIES:STRING="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi.lib" \ > -DMPI_LIBRARY:FILEPATH="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi_cxx.lib" \ > -DMPI_CXX_INCLUDE_PATH=C:/tools/openmpi/openmpi-1.4.4/include \ > -DMPI_C_INCLUDE_PATH=C:/tools/openmpi/openmpi-1.4.4/include \ > -DGLUT_glut_LIBRARY=C:\tools\freeglut\freeglut-2.8.1\lib\freeglut.lib \ > -DGLUT_INCLUDE_DIR=C:\tools\freeglut\freeglut-2.8.1\include \ > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ > -DPYTHON_LIBRARY=C:\tools\python\python-2.7.3\libs\python27.lib \ > -DPYTHON_INCLUDE_DIR=C:\tools\python\python-2.7.3\include \ > -DPYTHON_EXECUTABLE=C:\tools\python\python-2.7.3\bin\python.exe \ > ..\ParaView-v4.2.0-RC1-128-gc89b0ad > > ninja > > > > Any help is much appreciated. > > Thanks > -simon > > > ======================== linking error ======================= > [1/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractCellLocato > r.cxx.obj > [2/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractPointLocat > or.cxx.obj > [3/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAdjacentVertexIter > ator.cxx.obj > [4/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRBox.cxx.obj > [5/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRUtilities.cxx.o > bj > [6/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnimationScene.cxx > .obj > [7/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnnotation.cxx.obj > [8/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnnotationLayers.c > xx.obj > [9/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkArrayData.cxx.obj > [10/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAttributesErrorMet > ric.cxx.obj > [11/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuad.cx > x.obj > [12/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuadrat > icHexahedron.cxx.obj > [13/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuadrat > icWedge.cxx.obj > [14/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticTriangl > e.cxx.obj > [15/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBox.cxx.obj > [16/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBSPCuts.cxx.obj > [17/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBSPIntersections.c > xx.obj > [18/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCell3D.cxx.obj > [19/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellArray.cxx.obj > [20/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCell.cxx.obj > [21/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellData.cxx.obj > [22/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellIterator.cxx.o > bj > [23/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellLinks.cxx.obj > [24/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellLocator.cxx.ob > j > [25/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellTypes.cxx.obj > [26/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCompositeDataSet.c > xx.obj > [27/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCompositeDataItera > tor.cxx.obj > [28/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCone.cxx.obj > [29/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkConvexPointSet.cxx > .obj > [30/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCubicLine.cxx.obj > [31/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCylinder.cxx.obj > [32/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetCellIterato > r.cxx.obj > [33/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectCollecti > on.cxx.obj > [34/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObject.cxx.obj > [35/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTypes.cx > x.obj > [36/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTree.cxx > .obj > [37/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTreeIter > ator.cxx.obj > [38/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetAttributes. > cxx.obj > [39/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetCollection. > cxx.obj > [40/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSet.cxx.obj > [41/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDirectedAcyclicGra > ph.cxx.obj > [42/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDirectedGraph.cxx. > obj > [43/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDistributedGraphHe > lper.cxx.obj > [44/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEdgeListIterator.c > xx.obj > [45/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEdgeTable.cxx.obj > [46/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEmptyCell.cxx.obj > [47/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkExplicitCell.cxx.o > bj > [48/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkExtractStructuredG > ridHelper.cxx.obj > [49/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkFieldData.cxx.obj > [50/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAdaptorCell > .cxx.obj > [51/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAttributeCo > llection.cxx.obj > [52/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAttribute.c > xx.obj > [53/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCell.cxx.ob > j > [54/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCellIterato > r.cxx.obj > [55/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCellTessell > ator.cxx.obj > [56/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericDataSet.cxx > .obj > [57/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericEdgeTable.c > xx.obj > [58/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericInterpolate > dVelocityField.cxx.obj > [59/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericPointIterat > or.cxx.obj > [60/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericSubdivision > ErrorMetric.cxx.obj > [61/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGeometricErrorMetr > ic.cxx.obj > [62/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraph.cxx.obj > [63/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraphEdge.cxx.obj > [64/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraphInternals.cxx > .obj > [65/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHexagonalPrism.cxx > .obj > [66/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHexahedron.cxx.obj > [67/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHierarchicalBoxDat > aIterator.cxx.obj > [68/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHierarchicalBoxDat > aSet.cxx.obj > [69/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctreeCursor. > cxx.obj > [70/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctree.cxx.ob > j > [71/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctreePointsG > rabber.cxx.obj > [72/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTree.cxx.obj > [73/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTreeCursor.cx > x.obj > [74/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTreeGrid.cxx. > obj > [75/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImageData.cxx.obj > [76/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImageIterator.cxx. > obj > [77/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitBoolean.cx > x.obj > [78/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitDataSet.cx > x.obj > [79/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitFunctionCo > llection.cxx.obj > [80/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitFunction.c > xx.obj > [81/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitHalo.cxx.o > bj > [82/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitSelectionL > oop.cxx.obj > [83/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitSum.cxx.ob > j > [84/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitVolume.cxx > .obj > [85/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitWindowFunc > tion.cxx.obj > [86/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalOctreeN > ode.cxx.obj > [87/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalOctreeP > ointLocator.cxx.obj > [88/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalPointLo > cator.cxx.obj > [89/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkInEdgeIterator.cxx > .obj > [90/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkInformationQuadrat > ureSchemeDefinitionVectorKey.cxx.obj > [91/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIterativeClosestPo > intTransform.cxx.obj > [92/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdNode.cxx.obj > [93/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdTree.cxx.obj > [94/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdTreePointLocator > .cxx.obj > [95/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkLine.cxx.obj > [96/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkLocator.cxx.obj > [97/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMarchingSquaresLin > eCases.cxx.obj > [98/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMarchingCubesTrian > gleCases.cxx.obj > [99/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMeanValueCoordinat > esInterpolator.cxx.obj > [100/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMergePoints.cxx.ob > j > [101/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMultiBlockDataSet. > cxx.obj > [102/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMultiPieceDataSet. > cxx.obj > [103/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMutableDirectedGra > ph.cxx.obj > [104/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMutableUndirectedG > raph.cxx.obj > [105/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonLinearCell.cxx. > obj > [106/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonMergingPointLoc > ator.cxx.obj > [107/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOctreePointLocator > .cxx.obj > [108/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOctreePointLocator > Node.cxx.obj > [109/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOrderedTriangulato > r.cxx.obj > [110/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOutEdgeIterator.cx > x.obj > [111/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPath.cxx.obj > [112/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPentagonalPrism.cx > x.obj > [113/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPerlinNoise.cxx.ob > j > [114/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPiecewiseFunction. > cxx.obj > [115/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPixel.cxx.obj > [116/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPixelExtent.cxx.ob > j > [117/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlaneCollection.cx > x.obj > [118/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlane.cxx.obj > [119/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlanes.cxx.obj > [120/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlanesIntersection > .cxx.obj > [121/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointData.cxx.obj > [122/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointLocator.cxx.o > bj > [123/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointSet.cxx.obj > [124/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointSetCellIterat > or.cxx.obj > [125/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointsProjectedHul > l.cxx.obj > [126/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyDataCollection > .cxx.obj > [127/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyData.cxx.obj > [128/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolygon.cxx.obj > [129/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyhedron.cxx.obj > [130/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyLine.cxx.obj > [131/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyPlane.cxx.obj > [132/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyVertex.cxx.obj > [133/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPyramid.cxx.obj > [134/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuad.cxx.obj > [135/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticEdge.cxx. > obj > [136/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticHexahedro > n.cxx.obj > [137/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticLinearQua > d.cxx.obj > [138/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticLinearWed > ge.cxx.obj > [139/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticPolygon.c > xx.obj > [140/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticPyramid.c > xx.obj > [141/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticQuad.cxx. > obj > [142/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticTetra.cxx > .obj > [143/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticTriangle. > cxx.obj > [144/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticWedge.cxx > .obj > [145/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadratureSchemeDe > finition.cxx.obj > [146/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadric.cxx.obj > [147/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkRectilinearGrid.cx > x.obj > [148/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkReebGraph.cxx.obj > [149/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkReebGraphSimplific > ationMetric.cxx.obj > [150/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSelection.cxx.obj > [151/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSelectionNode.cxx. > obj > [152/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSimpleCellTessella > tor.cxx.obj > [153/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSmoothErrorMetric. > cxx.obj > [154/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSphere.cxx.obj > [155/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSpline.cxx.obj > [156/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredData.cxx > .obj > [157/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredExtent.c > xx.obj > [158/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredGrid.cxx > .obj > [159/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredPointsCo > llection.cxx.obj > [160/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredPoints.c > xx.obj > [161/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredVisibili > tyConstraint.cxx.obj > [162/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSuperquadric.cxx.o > bj > [163/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTable.cxx.obj > [164/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTensor.cxx.obj > [165/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTetra.cxx.obj > [166/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeBFSIterator.cx > x.obj > [167/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTree.cxx.obj > [168/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeDFSIterator.cx > x.obj > [169/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriangle.cxx.obj > [170/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriangleStrip.cxx. > obj > [171/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriQuadraticHexahe > dron.cxx.obj > [172/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUndirectedGraph.cx > x.obj > [173/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGrid.cxx.ob > j > [174/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGrid.c > xx.obj > [175/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGridBa > se.cxx.obj > [176/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGridCe > llIterator.cxx.obj > [177/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVertex.cxx.obj > [178/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVertexListIterator > .cxx.obj > [179/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVoxel.cxx.obj > [180/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkWedge.cxx.obj > [181/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkXMLDataElement.cxx > .obj > [182/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeIterator.cxx.o > bj > [183/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBoundingBox.cxx.ob > j > [184/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAtom.cxx.obj > [185/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBond.cxx.obj > [186/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMolecule.cxx.obj > [187/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractElectronic > Data.cxx.obj > [188/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonOverlappingAMR. > cxx.obj > [189/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOverlappingAMR.cxx > .obj > [190/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRInformation.cxx > .obj > [191/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRDataInternals.c > xx.obj > [192/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGridAMR.cxx > .obj > [193/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGridAMRData > Iterator.cxx.obj > [194/16592] Linking CXX shared library bin\vtkPythonInterpreter-pv4.2.dll > [195/16592] Linking CXX shared library bin\vtkWrappingPython27Core-pv4.2.dll > FAILED: cmd.exe /C "cd . && > C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll > C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo > VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho > nInterpreter.cxx.obj > VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho > nInteractiveInterpreter.cxx.obj /out:bin\vtkPythonInterpreter-pv4.2.dll > /implib:lib\vtkPythonInterpreter-pv4.2.lib > /pdb:bin\vtkPythonInterpreter-pv4.2.pdb /dll /version:1.0 /machine:x64 > /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib > C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib > Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib > ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." > Creating library lib\vtkPythonInterpreter-pv4.2.lib and object > lib\vtkPythonInterpreter-pv4.2.exp > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyType_IsSubtype referenced in function "struct _object * __cdecl > vtkWrite(struct _object *,struct _object *)" > (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyType_Ready referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GenericGetAttr referenced in function "void __cdecl `dynamic > initializer for 'vtkPythonStdStreamCaptureHelperType''(void)" > (??__EvtkPythonStdStreamCaptureHelperType@@YAXXZ) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GenericSetAttr referenced in function "void __cdecl `dynamic > initializer for 'vtkPythonStdStreamCaptureHelperType''(void)" > (??__EvtkPythonStdStreamCaptureHelperType@@YAXXZ) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp__PyObject_New referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_FromString referenced in function "public: static bool > __cdecl vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external > symbol __imp_PyString_FromString > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyList_Insert referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyArg_ParseTuple referenced in function "struct _object * __cdecl > vtkWrite(struct _object *,struct _object *)" > (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_BuildValue referenced in function "struct _object * __cdecl > vtkWrite(struct _object *,struct _object *)" > (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_SetProgramName referenced in function "public: static void __cdecl > vtkPythonInterpreter::SetProgramName(char const *)" > (?SetProgramName at vtkPythonInterpreter@@SAXPEBD at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_InitializeEx referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_Finalize referenced in function "public: static void __cdecl > vtkPythonInterpreter::Finalize(void)" > (?Finalize at vtkPythonInterpreter@@SAXXZ) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_IsInitialized referenced in function "public: static void __cdecl > vtkPythonInterpreter::Finalize(void)" > (?Finalize at vtkPythonInterpreter@@SAXXZ) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyRun_SimpleStringFlags referenced in function "public: static void > __cdecl vtkPythonInterpreter::RunSimpleString(char const *)" > (?RunSimpleString at vtkPythonInterpreter@@SAXPEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external > symbol __imp_PyRun_SimpleStringFlags > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_Main referenced in function "public: static int __cdecl > vtkPythonInterpreter::PyMain(int,char * *)" > (?PyMain at vtkPythonInterpreter@@SAHHPEAPEAD at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySys_GetObject referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external > symbol __imp_PySys_GetObject > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySys_SetObject referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external > symbol __imp_PySys_SetObject > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyDict_GetItemString referenced in function "public: struct > _object * __cdecl > vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" > (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE > AU_object@@XZ) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyModule_GetDict referenced in function "public: struct _object > * __cdecl > vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" > (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE > AU_object@@XZ) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyErr_Clear referenced in function "public: int __cdecl > vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" > (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyArg_Parse referenced in function "public: bool __cdecl > vtkPythonInteractiveInterpreter::Push(char const * const)" > (?Push at vtkPythonInteractiveInterpreter@@QEAA_NQEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyRun_StringFlags referenced in function "public: int __cdecl > vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" > (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyErr_Print referenced in function "public: int __cdecl > vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" > (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_Py_FlushLine referenced in function "public: int __cdecl > vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" > (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyImport_AddModule referenced in function "public: struct > _object * __cdecl > vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" > (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE > AU_object@@XZ) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyObject_CallMethod referenced in function "public: bool > __cdecl vtkPythonInteractiveInterpreter::Push(char const * const)" > (?Push at vtkPythonInteractiveInterpreter@@QEAA_NQEBD at Z) > > > bin\vtkPythonInterpreter-pv4.2.dll : fatal error LNK1120: 26 unresolved > externals > > > LINK failed. with 1120 > > FAILED: cmd.exe /C "cd . && > C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll > C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonArgs.c > xx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonComman > d.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonOverlo > ad.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonUtil.c > xx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkSmartPyObjec > t.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKClass.cxx. > obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKMutableObj > ect.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKObject.cxx > .obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKSpecialObj > ect.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKTemplate.c > xx.obj /out:bin\vtkWrappingPython27Core-pv4.2.dll > /implib:lib\vtkWrappingPython27Core-pv4.2.lib > /pdb:bin\vtkWrappingPython27Core-pv4.2.pdb /dll /version:1.0 /machine:x64 > /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib > C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib > Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib > ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." > Creating library lib\vtkWrappingPython27Core-pv4.2.lib and object > lib\vtkWrappingPython27Core-pv4.2.exp > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyType_IsSubtype referenced in function "bool __cdecl > vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" > (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyType_IsSubtype > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyType_IsSubtype > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_IsTrue referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,bool *,int)" > (??$vtkPythonGetArray at _N@@YA_NPEAU_object@@PEA_NH at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_IsTrue > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_IsTrue > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyCallable_Check referenced in function "public: bool __cdecl > vtkPythonArgs::GetFunction(struct _object * &)" > (?GetFunction at vtkPythonArgs@@QEAA_NAEAPEAU_object@@@Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyCallable_Check > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyCallable_Check > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp__PyUnicodeUCS2_AsDefaultEncodedString referenced in function "bool > __cdecl vtkPythonGetStringValue(struct _object *,char const * > &,char const *)" > (??$vtkPythonGetStringValue@$$CBD@@YA_NPEAU_object@@AEAPEBDPEBD at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyUnicodeUCS2_DecodeUTF8 referenced in function "public: static struct > _object * __cdecl vtkPythonArgs::BuildValue(class vtkUnicodeString const &)" > (?BuildValue at vtkPythonArgs@@SAPEAU_object@@AEBVvtkUnicodeString@@@Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyUnicodeUCS2_DecodeUTF8 > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyUnicodeUCS2_AsUTF8String referenced in function "bool __cdecl > vtkPythonGetValue(struct _object *,class vtkUnicodeString &)" > (?vtkPythonGetValue@@YA_NPEAU_object@@AEAVvtkUnicodeString@@@Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyInt_FromLong referenced in function "struct _object * __cdecl > vtkPythonBuildTuple(signed char const *,int)" > (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyInt_FromLong > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyInt_FromLong > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyInt_AsLong referenced in function "bool __cdecl > vtkPythonGetUnsignedLongLongValue(struct _object > *,unsigned __int64 &)" > (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyInt_AsLong > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyInt_AsLong > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyBool_FromLong referenced in function "struct _object * __cdecl > vtkPythonBuildTuple(bool const *,int)" > (??$vtkPythonBuildTuple at _N@@YAPEAU_object@@PEB_NH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_FromUnsignedLong referenced in function "struct _object * > __cdecl vtkPythonBuildTuple(unsigned int const *,int)" > (??$vtkPythonBuildTuple at I@@YAPEAU_object@@PEBIH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_AsUnsignedLong referenced in function "bool __cdecl > vtkPythonGetValue(struct _object *,unsigned int &)" > (?vtkPythonGetValue@@YA_NPEAU_object@@AEAI at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_FromLongLong referenced in function "struct _object * __cdecl > vtkPythonBuildTuple<__int64>(__int64 const *,int)" > (??$vtkPythonBuildTuple at _J@@YAPEAU_object@@PEB_JH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_FromUnsignedLongLong referenced in function "struct _object * > __cdecl vtkPythonBuildTuple(unsigned __int64 const *,int)" > (??$vtkPythonBuildTuple at _K@@YAPEAU_object@@PEB_KH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_AsLongLong referenced in function "bool __cdecl > vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" > (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyLong_AsLongLong > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_AsUnsignedLongLong referenced in function "bool __cdecl > vtkPythonGetUnsignedLongLongValue(struct _object > *,unsigned __int64 &)" > (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyFloat_FromDouble referenced in function "struct _object * __cdecl > vtkPythonBuildTuple(float const *,int)" > (??$vtkPythonBuildTuple at M@@YAPEAU_object@@PEBMH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyFloat_FromDouble > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyFloat_AsDouble referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,float *,int)" > (??$vtkPythonGetArray at M@@YA_NPEAU_object@@PEAMH at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyFloat_AsDouble > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_FromStringAndSize referenced in function "public: static > struct _object * __cdecl vtkPythonArgs::BuildBytes(char const *,int)" > (?BuildBytes at vtkPythonArgs@@SAPEAU_object@@PEBDH at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromStringAndSize > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromStringAndSize > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromStringAndSize > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_FromString referenced in function "bool __cdecl > vtkPythonSetArray(struct _object *,char const *,int)" > (??$vtkPythonSetArray at D@@YA_NPEAU_object@@PEBDH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_AsString referenced in function "public: __cdecl > std::error_category::error_category(void)" (??0error_category at std@@QEAA at XZ) > > > vtkPythonArgs.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_AsStringAndSize referenced in function "bool __cdecl > vtkPythonGetStdStringValue(struct _object *,class > std::basic_string,class > std::allocator > &,char const *)" > (?vtkPythonGetStdStringValue@@YA_NPEAU_object@@AEAV?$basic_string at DU?$char_t > raits at D@std@@V?$allocator at D@2@@std@@PEBD at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyTuple_New referenced in function "struct _object * __cdecl > vtkPythonBuildTuple(signed char const *,int)" > (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_New > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_New > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_New > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_SetString referenced in function "public: __cdecl > std::_Generic_error_category::_Generic_error_category(void)" > (??0_Generic_error_category at std@@QEAA at XZ) > > > vtkPythonArgs.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_Occurred referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,float *,int)" > (??$vtkPythonGetArray at M@@YA_NPEAU_object@@PEAMH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Occurred > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Occurred > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Occurred > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_Fetch referenced in function "protected: bool __cdecl > vtkPythonArgs::RefineArgTypeError(int)" > (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_Restore referenced in function "protected: bool __cdecl > vtkPythonArgs::RefineArgTypeError(int)" > (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_ExceptionMatches referenced in function "protected: bool __cdecl > vtkPythonArgs::RefineArgTypeError(int)" > (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_ExceptionMatches > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_ExceptionMatches > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_ExceptionMatches > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySequence_Check referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,signed char *,int)" > (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PySequence_Check > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySequence_Size referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,signed char *,int)" > (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PySequence_Size > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PySequence_Size > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySequence_GetItem referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,signed char *,int)" > (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PySequence_GetItem > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PySequence_GetItem > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySequence_SetItem referenced in function "bool __cdecl > vtkPythonSetArray(struct _object *,signed char const *,int)" > (??$vtkPythonSetArray at C@@YA_NPEAU_object@@PEBCH at Z) > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp__Py_NoneStruct referenced in function "struct _object * __cdecl > vtkPythonBuildTuple(signed char const *,int)" > (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyFloat_Type referenced in function "bool __cdecl > vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" > (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyFloat_Type > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyFloat_Type > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_OverflowError referenced in function "bool __cdecl > vtkPythonGetUnsignedLongLongValue(struct _object > *,unsigned __int64 &)" > (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_TypeError referenced in function "bool __cdecl > vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" > (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_ValueError > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_ValueError referenced in function "protected: bool __cdecl > vtkPythonArgs::RefineArgTypeError(int)" > (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_ValueError > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_ValueError > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_ValueError > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GetAttrString referenced in function "public: virtual void > __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GetAttrString > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GetAttrString > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_FromLong referenced in function "public: virtual void __cdecl > vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Clear > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Clear > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_Clear referenced in function "struct _object * __cdecl > `anonymous namespace'::BuildCallDataArgList(struct _object *,char const > *,struct _object *)" > (?BuildCallDataArgList@?A0xfc44b691@@YAPEAU_object@@PEAU2 at PEBD0@Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Clear > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Clear > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Clear > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyThreadState_Swap referenced in function "public: virtual void > __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_BuildValue > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_BuildValue referenced in function "struct _object * __cdecl > `anonymous namespace'::BuildCallDataArgList(struct _object *,char const > *,struct _object *)" > (?BuildCallDataArgList@?A0xfc44b691@@YAPEAU_object@@PEAU2 at PEBD0@Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_BuildValue > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_BuildValue > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_BuildValue > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_IsInitialized referenced in function "protected: virtual __cdecl > vtkPythonCommand::~vtkPythonCommand(void)" (??1vtkPythonCommand@@MEAA at XZ) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_IsInitialized > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_Print referenced in function "public: virtual void __cdecl > vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Print > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_Exit referenced in function "public: virtual void __cdecl > vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_Exit > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyEval_CallObjectWithKeywords referenced in function "public: virtual > void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void > *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyEval_CallObjectWithKeywords > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyEval_CallObjectWithKeywords > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyEval_CallObjectWithKeywords > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_KeyboardInterrupt referenced in function "public: virtual void > __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_KeyboardInterrupt > > > vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_Size referenced in function "public: static int __cdecl > vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" > (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_Size > > > vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyTuple_Size referenced in function "public: static int __cdecl > vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" > (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_Size > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_Size > > > vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyBool_Type referenced in function "public: static int __cdecl > vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" > (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_Hash referenced in function "public: static long __cdecl > vtkPythonUtil::VariantHash(class vtkVariant const *)" > (?VariantHash at vtkPythonUtil@@SAJPEBVvtkVariant@@@Z) > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp__Py_HashPointer referenced in function "public: static long __cdecl > vtkPythonUtil::VariantHash(class vtkVariant const *)" > (?VariantHash at vtkPythonUtil@@SAJPEBVvtkVariant@@@Z) > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp__PyString_Resize referenced in function "public: static struct _object > * __cdecl vtkPythonUtil::BuildDocString(char const * * const)" > (?BuildDocString at vtkPythonUtil@@SAPEAU_object@@QEAPEBD at Z) > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_Size referenced in function "public: static void __cdecl > vtkPythonUtil::RemoveObjectFromMap(struct _object *)" > (?RemoveObjectFromMap at vtkPythonUtil@@SAXPEAU_object@@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_Size > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_GivenExceptionMatches referenced in function "public: static > void * __cdecl vtkPythonUtil::GetPointerFromSpecialObject(struct _object > *,char const *,struct _object * *)" > (?GetPointerFromSpecialObject at vtkPythonUtil@@SAPEAXPEAU_object@@PEBDPEAPEAU2 > @@Z) > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_AtExit referenced in function "public: static void __cdecl > vtkPythonUtil::AddClassToMap(struct _object *,char const *)" > (?AddClassToMap at vtkPythonUtil@@SAXPEAU_object@@PEBD at Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GetAttr referenced in function "struct _object * __cdecl > PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GetAttr > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp__PyObject_GC_New referenced in function "struct _object * __cdecl > PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp__PyObject_GC_New > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp__PyObject_GC_New > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GC_Track referenced in function "struct _object * __cdecl > PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_Track > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_Track > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GC_UnTrack referenced in function "void __cdecl > PyVTKClass_Delete(struct _object *)" > (?PyVTKClass_Delete@@YAXPEAU_object@@@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_UnTrack > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_UnTrack > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GC_Del referenced in function "void __cdecl > PyVTKClass_Delete(struct _object *)" > (?PyVTKClass_Delete@@YAXPEAU_object@@@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_Del > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_Del > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_InternFromString referenced in function PyVTKClass_New > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyTuple_GetItem referenced in function "struct _object * __cdecl > PyVTKClass_GetAttr(struct _object *,struct _object *)" > (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_GetItem > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_New referenced in function "struct _object * __cdecl > PyVTKClass_GetAttr(struct _object *,struct _object *)" > (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_New > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_New > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_GetItem referenced in function "struct _object * __cdecl > PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_GetItem > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_Keys referenced in function "struct _object * __cdecl > PyVTKClass_Dir(struct _object *,struct _object *)" > (?PyVTKClass_Dir@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_Update referenced in function "struct _object * __cdecl > PyVTKClass_Dir(struct _object *,struct _object *)" > (?PyVTKClass_Dir@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_GetItemString referenced in function "struct _object * __cdecl > PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_SetItemString referenced in function "struct _object * __cdecl > PyVTKClass_GetAttr(struct _object *,struct _object *)" > (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_SetItemString > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_DelItemString referenced in function "struct _object * __cdecl > PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyCFunction_NewEx referenced in function "struct _object * __cdecl > PyVTKClass_GetAttr(struct _object *,struct _object *)" > (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyCFunction_NewEx > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyCFunction_NewEx > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyArg_ParseTuple referenced in function "struct _object * __cdecl > PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyArg_ParseTuple > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyArg_ParseTuple > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyArg_ParseTupleAndKeywords referenced in function "struct _object * > __cdecl PyVTKClass_NewSubclass(struct _object *,struct _object *,struct > _object *)" (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyEval_GetGlobals referenced in function "struct _object * __cdecl > PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyType_Type referenced in function "void __cdecl `dynamic initializer > for 'PyVTKClassMetaType''(void)" (??__EPyVTKClassMetaType@@YAXXZ) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyType_Type > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyType_Type > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyType_Type > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyClass_Type referenced in function "void __cdecl `dynamic initializer > for 'PyVTKClass_Type''(void)" (??__EPyVTKClass_Type@@YAXXZ) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_AttributeError referenced in function "struct _object * __cdecl > PyVTKClass_GetAttr(struct _object *,struct _object *)" > (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_AttributeError > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_AttributeError > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_AttributeError > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_Repr referenced in function "struct _object * __cdecl > PyVTKMutableObject_Repr(struct _object *)" > (?PyVTKMutableObject_Repr@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_Repr > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_Str referenced in function "struct _object * __cdecl > PyVTKMutableObject_Str(struct _object *)" > (?PyVTKMutableObject_Str@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_RichCompare referenced in function "struct _object * __cdecl > PyVTKMutableObject_RichCompare(struct _object *,struct _object *,int)" > (?PyVTKMutableObject_RichCompare@@YAPEAU_object@@PEAU1 at 0H@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GenericGetAttr referenced in function "struct _object * > __cdecl PyVTKMutableObject_GetAttr(struct _object *,struct _object *)" > (?PyVTKMutableObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_HashNotImplemented referenced in function "void __cdecl > `dynamic initializer for 'PyVTKMutableObject_Type''(void)" > (??__EPyVTKMutableObject_Type@@YAXXZ) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_CoerceEx referenced in function "int __cdecl > PyVTKMutableObject_Coerce(struct _object * *,struct _object * *)" > (?PyVTKMutableObject_Coerce@@YAHPEAPEAU_object@@0 at Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_Free referenced in function "void __cdecl `dynamic > initializer for 'PyVTKMutableObject_Type''(void)" > (??__EPyVTKMutableObject_Type@@YAXXZ) > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_Free > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp__PyObject_New referenced in function "struct _object * __cdecl > PyVTKMutableObject_New(struct _typeobject *,struct _object *,struct _object > *)" (?PyVTKMutableObject_New@@YAPEAU_object@@PEAU_typeobject@@PEAU1 at 1@Z) > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp__PyObject_New > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Add referenced in function "struct _object * __cdecl > PyVTKMutableObject_Add(struct _object *,struct _object *)" > (?PyVTKMutableObject_Add@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Subtract referenced in function "struct _object * __cdecl > PyVTKMutableObject_Subtract(struct _object *,struct _object *)" > (?PyVTKMutableObject_Subtract@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Multiply referenced in function "struct _object * __cdecl > PyVTKMutableObject_Multiply(struct _object *,struct _object *)" > (?PyVTKMutableObject_Multiply@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Divide referenced in function "struct _object * __cdecl > PyVTKMutableObject_Divide(struct _object *,struct _object *)" > (?PyVTKMutableObject_Divide@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_FloorDivide referenced in function "struct _object * __cdecl > PyVTKMutableObject_FloorDivide(struct _object *,struct _object *)" > (?PyVTKMutableObject_FloorDivide@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_TrueDivide referenced in function "struct _object * __cdecl > PyVTKMutableObject_TrueDivide(struct _object *,struct _object *)" > (?PyVTKMutableObject_TrueDivide@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Remainder referenced in function "struct _object * __cdecl > PyVTKMutableObject_Remainder(struct _object *,struct _object *)" > (?PyVTKMutableObject_Remainder@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Divmod referenced in function "struct _object * __cdecl > PyVTKMutableObject_Divmod(struct _object *,struct _object *)" > (?PyVTKMutableObject_Divmod@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Power referenced in function "struct _object * __cdecl > PyVTKMutableObject_Power(struct _object *,struct _object *,struct _object > *)" (?PyVTKMutableObject_Power@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Negative referenced in function "struct _object * __cdecl > PyVTKMutableObject_Negative(struct _object *)" > (?PyVTKMutableObject_Negative@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Positive referenced in function "struct _object * __cdecl > PyVTKMutableObject_Positive(struct _object *)" > (?PyVTKMutableObject_Positive@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Absolute referenced in function "struct _object * __cdecl > PyVTKMutableObject_Absolute(struct _object *)" > (?PyVTKMutableObject_Absolute@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Invert referenced in function "struct _object * __cdecl > PyVTKMutableObject_Invert(struct _object *)" > (?PyVTKMutableObject_Invert@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Lshift referenced in function "struct _object * __cdecl > PyVTKMutableObject_Lshift(struct _object *,struct _object *)" > (?PyVTKMutableObject_Lshift@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Rshift referenced in function "struct _object * __cdecl > PyVTKMutableObject_InPlaceRshift(struct _object *,struct _object *)" > (?PyVTKMutableObject_InPlaceRshift@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_And referenced in function "struct _object * __cdecl > PyVTKMutableObject_InPlaceAnd(struct _object *,struct _object *)" > (?PyVTKMutableObject_InPlaceAnd@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Xor referenced in function "struct _object * __cdecl > PyVTKMutableObject_InPlaceXor(struct _object *,struct _object *)" > (?PyVTKMutableObject_InPlaceXor@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Or referenced in function "struct _object * __cdecl > PyVTKMutableObject_InPlaceOr(struct _object *,struct _object *)" > (?PyVTKMutableObject_InPlaceOr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Index referenced in function "struct _object * __cdecl > PyVTKMutableObject_Index(struct _object *)" > (?PyVTKMutableObject_Index@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Int referenced in function "struct _object * __cdecl > PyVTKMutableObject_Int(struct _object *)" > (?PyVTKMutableObject_Int@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Long referenced in function "struct _object * __cdecl > PyVTKMutableObject_Long(struct _object *)" > (?PyVTKMutableObject_Long@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Float referenced in function "struct _object * __cdecl > PyVTKMutableObject_Float(struct _object *)" > (?PyVTKMutableObject_Float@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_ToBase referenced in function "struct _object * __cdecl > PyVTKMutableObject_Hex(struct _object *)" > (?PyVTKMutableObject_Hex@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_ClearWeakRefs referenced in function "void __cdecl > PyVTKObject_Delete(struct _object *)" > (?PyVTKObject_Delete@@YAXPEAU_object@@@Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_SetItem referenced in function "int __cdecl > PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" > (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_SetItem > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_DelItem referenced in function "int __cdecl > PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" > (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyMethod_New referenced in function "struct _object * __cdecl > PyVTKObject_GetAttr(struct _object *,struct _object *)" > (?PyVTKObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyCFunction_Type referenced in function "struct _object * __cdecl > PyVTKObject_GetAttr(struct _object *,struct _object *)" > (?PyVTKObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_RuntimeError referenced in function "int __cdecl > PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" > (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_NotImplementedError referenced in function PyVTKObject_New > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyType_Ready referenced in function PyVTKSpecialType_New > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_ReprEnter referenced in function PyVTKSpecialObject_SequenceString > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_ReprLeave referenced in function PyVTKSpecialObject_SequenceString > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_Concat referenced in function > PyVTKSpecialObject_SequenceString > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_ConcatAndDel referenced in function PyVTKSpecialObject_Repr > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyBaseObject_Type referenced in function PyVTKSpecialObject_Repr > > > PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_CallMethod referenced in function "struct _object * __cdecl > PyVTKTemplate_HasKey(struct _object *,struct _object *)" > (?PyVTKTemplate_HasKey@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_Size referenced in function "__int64 __cdecl > PyVTKTemplate_Size(struct _object *)" > (?PyVTKTemplate_Size@@YA_JPEAU_object@@@Z) > > > PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GetItem referenced in function "struct _object * __cdecl > PyVTKTemplate_GetItem(struct _object *,struct _object *)" > (?PyVTKTemplate_GetItem@@YAPEAU_object@@PEAU1 at 0@Z) > > > bin\vtkWrappingPython27Core-pv4.2.dll : fatal error LNK1120: 123 unresolved > externals > > > LINK failed. with 1120 > > ninja: build stopped: subcommand failed. > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From simon.m.su.ctr at mail.mil Tue Sep 23 15:48:31 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 23 Sep 2014 19:48:31 +0000 Subject: [Paraview] python link error when compiling PV-v4.2.0-RC1-128-gc89b0ad + python-2.7.3 + VS2013 Express (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Utkarsh, Thanks for the info. I did followed that thread and my conclusion at the end was ParaView for windows compiled for vs2012 :) so, I went a step further to try to get compiled with vs2013Express since that's the compiler I have access to on windows ;) I thought getting python compiled on any of the compiler of choice is the prerequisite... apparently I still don't have python working even after I manage to compile it. :( I am not doing the superbuild and just ParaView git from source build. I ran into too many errors with VS2013Express + ninja-1.5.1 with the superbuild route that I don't even know where/how to begin to ask for help. I will give -DUSE_SYSTEM_PYTHON=ON flag a try. If that doesn't work, I will have my justification to ask for VS2008 purchased/installed on my system. Thanks for your help. Thanks -simon -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Tuesday, September 23, 2014 3:17 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] python link error when compiling PV-v4.2.0-RC1-128-gc89b0ad + python-2.7.3 + VS2013 Express (UNCLASSIFIED) Simon, As this states [1], superbuild on Windows with Python is only supported for VS 2008 currently. We will soon add support for VS2013. If you want to use VS2013, using USE_SYSTEM_python=ON may be worth a try, but these was a discussion on the mailing list a little while ago that too may have problems -- but it wasn't clear if it was build problem, or an environment issue. Worth a shot, however. [1] http://www.paraview.org/Wiki/ParaView/Superbuild#Windows On Tue, Sep 23, 2014 at 1:34 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > I am trying to get a ParaView + vrpn running on a zSpace. With zSpace VRPN > server only available on Windows, here goes the following... > > I am able to get ParaView build with ninja when I only do > -DPARAVIEW_USE_MPI:BOOL=ON and the binary appears to be working. But when I > included > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > I have linking problem. How do you make sure that I have a working Python > library? Dumpbin is reporting python is x64 library and I am trying to > compile a x64 ParaView. > > I am getting some 26 unresolved externals when ninja is "Creating library > lib\vtkPythonInterpreter-pv4.2.lib and object > lib\vtkPythonInterpreter-pv4.2.exp." and some 123 unresolved externals when > ninja is "Creating library lib\vtkWrappingPython27Core-pv4.2.lib and object > lib\vtkWrappingPython27Core-pv4.2.exp"- included at the end of this email. > > The odd thing is, both failed command has python27.lib library in it > > FAILED: cmd.exe /C "cd . && > C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll > C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo > VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho > nInterpreter.cxx.obj > VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho > nInteractiveInterpreter.cxx.obj /out:bin\vtkPythonInterpreter-pv4.2.dll > /implib:lib\vtkPythonInterpreter-pv4.2.lib > /pdb:bin\vtkPythonInterpreter-pv4.2.pdb /dll /version:1.0 /machine:x64 > /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib > C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib > Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib > ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." > > And > > FAILED: cmd.exe /C "cd . && > C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll > C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonArgs.c > xx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonComman > d.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonOverlo > ad.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonUtil.c > xx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkSmartPyObjec > t.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKClass.cxx. > obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKMutableObj > ect.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKObject.cxx > .obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKSpecialObj > ect.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKTemplate.c > xx.obj /out:bin\vtkWrappingPython27Core-pv4.2.dll > /implib:lib\vtkWrappingPython27Core-pv4.2.lib > /pdb:bin\vtkWrappingPython27Core-pv4.2.pdb /dll /version:1.0 /machine:x64 > /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib > C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib > Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib > ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." > > Do I have to included another python library? If so, what would that be? > > > I am building a 64bit version of ParaView on Windows 7 using > 1. VS2013 express version > 2. Python-2.7.3 - release version build with cmake + ninja > (https://github.com/davidsansome/python-cmake-buildsystem) > cmake \ > -DCMAKE_INSTALL_PREFIX=C:\tools\python\python-2.7.3 \ > -DBUILD_SHARED:BOOL=ON \ > -DCMAKE_BUILD_TYPE=Release \ > -DZLIB_LIBRARY=C:\tools\zlib\zlib-1.2.8\lib\zlib.lib \ > -DZLIB_INCLUDE_DIR=C:\tools\zlib\zlib-1.2.8\include \ > ..\python-cmake-buildsystem -G Ninja \ > ninja > ninja install > > 3. Ninja-1.5.1 - build using the python-2.7.3 above so, python appears to > work > python bootstrap.py --x64 > > 4. ParaView-v4.2.0-RC1-128-gc89b0ad > > git clone git://paraview.org/ParaView.git > cd ParaView > git pull > git submodule update --init > > cmake \ > -G Ninja \ > -DCMAKE_INSTALL_PREFIX=C:\tools\ParaView\ParaView-v4.2.0-RC1-100-gfa06130 \ > -DCMAKE_BUILD_TYPE=Release \ > -DZLIB_LIBRARY=C:\tools\zlib\zlib-1.2.8\lib\zlib.lib \ > -DZLIB_INCLUDE_DIR=C:\tools\zlib\zlib-1.2.8\include > -DCMAKE_BUILD_TYPE=Release \ > -DPARAVIEW_USE_MPI:BOOL=ON \ > -DMPI_CXX_LIBRARIES:STRING="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi_cxx.li > b" \ > -DMPI_C_LIBRARIES:STRING="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi.lib" \ > -DMPI_LIBRARY:FILEPATH="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi_cxx.lib" \ > -DMPI_CXX_INCLUDE_PATH=C:/tools/openmpi/openmpi-1.4.4/include \ > -DMPI_C_INCLUDE_PATH=C:/tools/openmpi/openmpi-1.4.4/include \ > -DGLUT_glut_LIBRARY=C:\tools\freeglut\freeglut-2.8.1\lib\freeglut.lib \ > -DGLUT_INCLUDE_DIR=C:\tools\freeglut\freeglut-2.8.1\include \ > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ > -DPYTHON_LIBRARY=C:\tools\python\python-2.7.3\libs\python27.lib \ > -DPYTHON_INCLUDE_DIR=C:\tools\python\python-2.7.3\include \ > -DPYTHON_EXECUTABLE=C:\tools\python\python-2.7.3\bin\python.exe \ > ..\ParaView-v4.2.0-RC1-128-gc89b0ad > > ninja > > > > Any help is much appreciated. > > Thanks > -simon > > > ======================== linking error ======================= > [1/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractCellLocato > r.cxx.obj > [2/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractPointLocat > or.cxx.obj > [3/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAdjacentVertexIter > ator.cxx.obj > [4/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRBox.cxx.obj > [5/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRUtilities.cxx.o > bj > [6/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnimationScene.cxx > .obj > [7/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnnotation.cxx.obj > [8/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnnotationLayers.c > xx.obj > [9/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkArrayData.cxx.obj > [10/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAttributesErrorMet > ric.cxx.obj > [11/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuad.cx > x.obj > [12/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuadrat > icHexahedron.cxx.obj > [13/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuadrat > icWedge.cxx.obj > [14/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticTriangl > e.cxx.obj > [15/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBox.cxx.obj > [16/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBSPCuts.cxx.obj > [17/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBSPIntersections.c > xx.obj > [18/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCell3D.cxx.obj > [19/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellArray.cxx.obj > [20/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCell.cxx.obj > [21/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellData.cxx.obj > [22/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellIterator.cxx.o > bj > [23/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellLinks.cxx.obj > [24/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellLocator.cxx.ob > j > [25/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellTypes.cxx.obj > [26/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCompositeDataSet.c > xx.obj > [27/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCompositeDataItera > tor.cxx.obj > [28/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCone.cxx.obj > [29/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkConvexPointSet.cxx > .obj > [30/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCubicLine.cxx.obj > [31/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCylinder.cxx.obj > [32/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetCellIterato > r.cxx.obj > [33/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectCollecti > on.cxx.obj > [34/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObject.cxx.obj > [35/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTypes.cx > x.obj > [36/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTree.cxx > .obj > [37/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTreeIter > ator.cxx.obj > [38/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetAttributes. > cxx.obj > [39/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetCollection. > cxx.obj > [40/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSet.cxx.obj > [41/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDirectedAcyclicGra > ph.cxx.obj > [42/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDirectedGraph.cxx. > obj > [43/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDistributedGraphHe > lper.cxx.obj > [44/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEdgeListIterator.c > xx.obj > [45/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEdgeTable.cxx.obj > [46/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEmptyCell.cxx.obj > [47/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkExplicitCell.cxx.o > bj > [48/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkExtractStructuredG > ridHelper.cxx.obj > [49/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkFieldData.cxx.obj > [50/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAdaptorCell > .cxx.obj > [51/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAttributeCo > llection.cxx.obj > [52/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAttribute.c > xx.obj > [53/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCell.cxx.ob > j > [54/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCellIterato > r.cxx.obj > [55/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCellTessell > ator.cxx.obj > [56/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericDataSet.cxx > .obj > [57/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericEdgeTable.c > xx.obj > [58/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericInterpolate > dVelocityField.cxx.obj > [59/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericPointIterat > or.cxx.obj > [60/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericSubdivision > ErrorMetric.cxx.obj > [61/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGeometricErrorMetr > ic.cxx.obj > [62/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraph.cxx.obj > [63/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraphEdge.cxx.obj > [64/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraphInternals.cxx > .obj > [65/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHexagonalPrism.cxx > .obj > [66/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHexahedron.cxx.obj > [67/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHierarchicalBoxDat > aIterator.cxx.obj > [68/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHierarchicalBoxDat > aSet.cxx.obj > [69/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctreeCursor. > cxx.obj > [70/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctree.cxx.ob > j > [71/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctreePointsG > rabber.cxx.obj > [72/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTree.cxx.obj > [73/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTreeCursor.cx > x.obj > [74/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTreeGrid.cxx. > obj > [75/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImageData.cxx.obj > [76/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImageIterator.cxx. > obj > [77/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitBoolean.cx > x.obj > [78/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitDataSet.cx > x.obj > [79/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitFunctionCo > llection.cxx.obj > [80/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitFunction.c > xx.obj > [81/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitHalo.cxx.o > bj > [82/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitSelectionL > oop.cxx.obj > [83/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitSum.cxx.ob > j > [84/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitVolume.cxx > .obj > [85/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitWindowFunc > tion.cxx.obj > [86/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalOctreeN > ode.cxx.obj > [87/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalOctreeP > ointLocator.cxx.obj > [88/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalPointLo > cator.cxx.obj > [89/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkInEdgeIterator.cxx > .obj > [90/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkInformationQuadrat > ureSchemeDefinitionVectorKey.cxx.obj > [91/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIterativeClosestPo > intTransform.cxx.obj > [92/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdNode.cxx.obj > [93/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdTree.cxx.obj > [94/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdTreePointLocator > .cxx.obj > [95/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkLine.cxx.obj > [96/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkLocator.cxx.obj > [97/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMarchingSquaresLin > eCases.cxx.obj > [98/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMarchingCubesTrian > gleCases.cxx.obj > [99/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMeanValueCoordinat > esInterpolator.cxx.obj > [100/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMergePoints.cxx.ob > j > [101/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMultiBlockDataSet. > cxx.obj > [102/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMultiPieceDataSet. > cxx.obj > [103/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMutableDirectedGra > ph.cxx.obj > [104/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMutableUndirectedG > raph.cxx.obj > [105/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonLinearCell.cxx. > obj > [106/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonMergingPointLoc > ator.cxx.obj > [107/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOctreePointLocator > .cxx.obj > [108/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOctreePointLocator > Node.cxx.obj > [109/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOrderedTriangulato > r.cxx.obj > [110/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOutEdgeIterator.cx > x.obj > [111/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPath.cxx.obj > [112/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPentagonalPrism.cx > x.obj > [113/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPerlinNoise.cxx.ob > j > [114/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPiecewiseFunction. > cxx.obj > [115/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPixel.cxx.obj > [116/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPixelExtent.cxx.ob > j > [117/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlaneCollection.cx > x.obj > [118/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlane.cxx.obj > [119/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlanes.cxx.obj > [120/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlanesIntersection > .cxx.obj > [121/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointData.cxx.obj > [122/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointLocator.cxx.o > bj > [123/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointSet.cxx.obj > [124/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointSetCellIterat > or.cxx.obj > [125/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointsProjectedHul > l.cxx.obj > [126/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyDataCollection > .cxx.obj > [127/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyData.cxx.obj > [128/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolygon.cxx.obj > [129/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyhedron.cxx.obj > [130/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyLine.cxx.obj > [131/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyPlane.cxx.obj > [132/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyVertex.cxx.obj > [133/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPyramid.cxx.obj > [134/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuad.cxx.obj > [135/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticEdge.cxx. > obj > [136/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticHexahedro > n.cxx.obj > [137/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticLinearQua > d.cxx.obj > [138/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticLinearWed > ge.cxx.obj > [139/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticPolygon.c > xx.obj > [140/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticPyramid.c > xx.obj > [141/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticQuad.cxx. > obj > [142/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticTetra.cxx > .obj > [143/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticTriangle. > cxx.obj > [144/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticWedge.cxx > .obj > [145/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadratureSchemeDe > finition.cxx.obj > [146/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadric.cxx.obj > [147/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkRectilinearGrid.cx > x.obj > [148/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkReebGraph.cxx.obj > [149/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkReebGraphSimplific > ationMetric.cxx.obj > [150/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSelection.cxx.obj > [151/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSelectionNode.cxx. > obj > [152/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSimpleCellTessella > tor.cxx.obj > [153/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSmoothErrorMetric. > cxx.obj > [154/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSphere.cxx.obj > [155/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSpline.cxx.obj > [156/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredData.cxx > .obj > [157/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredExtent.c > xx.obj > [158/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredGrid.cxx > .obj > [159/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredPointsCo > llection.cxx.obj > [160/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredPoints.c > xx.obj > [161/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredVisibili > tyConstraint.cxx.obj > [162/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSuperquadric.cxx.o > bj > [163/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTable.cxx.obj > [164/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTensor.cxx.obj > [165/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTetra.cxx.obj > [166/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeBFSIterator.cx > x.obj > [167/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTree.cxx.obj > [168/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeDFSIterator.cx > x.obj > [169/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriangle.cxx.obj > [170/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriangleStrip.cxx. > obj > [171/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriQuadraticHexahe > dron.cxx.obj > [172/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUndirectedGraph.cx > x.obj > [173/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGrid.cxx.ob > j > [174/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGrid.c > xx.obj > [175/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGridBa > se.cxx.obj > [176/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGridCe > llIterator.cxx.obj > [177/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVertex.cxx.obj > [178/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVertexListIterator > .cxx.obj > [179/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVoxel.cxx.obj > [180/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkWedge.cxx.obj > [181/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkXMLDataElement.cxx > .obj > [182/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeIterator.cxx.o > bj > [183/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBoundingBox.cxx.ob > j > [184/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAtom.cxx.obj > [185/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBond.cxx.obj > [186/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMolecule.cxx.obj > [187/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractElectronic > Data.cxx.obj > [188/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonOverlappingAMR. > cxx.obj > [189/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOverlappingAMR.cxx > .obj > [190/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRInformation.cxx > .obj > [191/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRDataInternals.c > xx.obj > [192/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGridAMR.cxx > .obj > [193/16592] Building CXX object > VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGridAMRData > Iterator.cxx.obj > [194/16592] Linking CXX shared library bin\vtkPythonInterpreter-pv4.2.dll > [195/16592] Linking CXX shared library bin\vtkWrappingPython27Core-pv4.2.dll > FAILED: cmd.exe /C "cd . && > C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll > C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo > VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho > nInterpreter.cxx.obj > VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho > nInteractiveInterpreter.cxx.obj /out:bin\vtkPythonInterpreter-pv4.2.dll > /implib:lib\vtkPythonInterpreter-pv4.2.lib > /pdb:bin\vtkPythonInterpreter-pv4.2.pdb /dll /version:1.0 /machine:x64 > /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib > C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib > Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib > ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." > Creating library lib\vtkPythonInterpreter-pv4.2.lib and object > lib\vtkPythonInterpreter-pv4.2.exp > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyType_IsSubtype referenced in function "struct _object * __cdecl > vtkWrite(struct _object *,struct _object *)" > (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyType_Ready referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GenericGetAttr referenced in function "void __cdecl `dynamic > initializer for 'vtkPythonStdStreamCaptureHelperType''(void)" > (??__EvtkPythonStdStreamCaptureHelperType@@YAXXZ) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GenericSetAttr referenced in function "void __cdecl `dynamic > initializer for 'vtkPythonStdStreamCaptureHelperType''(void)" > (??__EvtkPythonStdStreamCaptureHelperType@@YAXXZ) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp__PyObject_New referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_FromString referenced in function "public: static bool > __cdecl vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external > symbol __imp_PyString_FromString > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyList_Insert referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyArg_ParseTuple referenced in function "struct _object * __cdecl > vtkWrite(struct _object *,struct _object *)" > (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_BuildValue referenced in function "struct _object * __cdecl > vtkWrite(struct _object *,struct _object *)" > (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_SetProgramName referenced in function "public: static void __cdecl > vtkPythonInterpreter::SetProgramName(char const *)" > (?SetProgramName at vtkPythonInterpreter@@SAXPEBD at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_InitializeEx referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_Finalize referenced in function "public: static void __cdecl > vtkPythonInterpreter::Finalize(void)" > (?Finalize at vtkPythonInterpreter@@SAXXZ) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_IsInitialized referenced in function "public: static void __cdecl > vtkPythonInterpreter::Finalize(void)" > (?Finalize at vtkPythonInterpreter@@SAXXZ) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyRun_SimpleStringFlags referenced in function "public: static void > __cdecl vtkPythonInterpreter::RunSimpleString(char const *)" > (?RunSimpleString at vtkPythonInterpreter@@SAXPEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external > symbol __imp_PyRun_SimpleStringFlags > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_Main referenced in function "public: static int __cdecl > vtkPythonInterpreter::PyMain(int,char * *)" > (?PyMain at vtkPythonInterpreter@@SAHHPEAPEAD at Z) > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySys_GetObject referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external > symbol __imp_PySys_GetObject > > > vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySys_SetObject referenced in function "public: static bool __cdecl > vtkPythonInterpreter::Initialize(int)" > (?Initialize at vtkPythonInterpreter@@SA_NH at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external > symbol __imp_PySys_SetObject > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyDict_GetItemString referenced in function "public: struct > _object * __cdecl > vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" > (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE > AU_object@@XZ) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyModule_GetDict referenced in function "public: struct _object > * __cdecl > vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" > (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE > AU_object@@XZ) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyErr_Clear referenced in function "public: int __cdecl > vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" > (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyArg_Parse referenced in function "public: bool __cdecl > vtkPythonInteractiveInterpreter::Push(char const * const)" > (?Push at vtkPythonInteractiveInterpreter@@QEAA_NQEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyRun_StringFlags referenced in function "public: int __cdecl > vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" > (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyErr_Print referenced in function "public: int __cdecl > vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" > (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_Py_FlushLine referenced in function "public: int __cdecl > vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" > (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyImport_AddModule referenced in function "public: struct > _object * __cdecl > vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" > (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE > AU_object@@XZ) > > > vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external > symbol __imp_PyObject_CallMethod referenced in function "public: bool > __cdecl vtkPythonInteractiveInterpreter::Push(char const * const)" > (?Push at vtkPythonInteractiveInterpreter@@QEAA_NQEBD at Z) > > > bin\vtkPythonInterpreter-pv4.2.dll : fatal error LNK1120: 26 unresolved > externals > > > LINK failed. with 1120 > > FAILED: cmd.exe /C "cd . && > C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll > C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonArgs.c > xx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonComman > d.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonOverlo > ad.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonUtil.c > xx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkSmartPyObjec > t.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKClass.cxx. > obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKMutableObj > ect.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKObject.cxx > .obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKSpecialObj > ect.cxx.obj > VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKTemplate.c > xx.obj /out:bin\vtkWrappingPython27Core-pv4.2.dll > /implib:lib\vtkWrappingPython27Core-pv4.2.lib > /pdb:bin\vtkWrappingPython27Core-pv4.2.pdb /dll /version:1.0 /machine:x64 > /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib > C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib > Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib > ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." > Creating library lib\vtkWrappingPython27Core-pv4.2.lib and object > lib\vtkWrappingPython27Core-pv4.2.exp > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyType_IsSubtype referenced in function "bool __cdecl > vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" > (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyType_IsSubtype > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyType_IsSubtype > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_IsTrue referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,bool *,int)" > (??$vtkPythonGetArray at _N@@YA_NPEAU_object@@PEA_NH at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_IsTrue > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_IsTrue > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyCallable_Check referenced in function "public: bool __cdecl > vtkPythonArgs::GetFunction(struct _object * &)" > (?GetFunction at vtkPythonArgs@@QEAA_NAEAPEAU_object@@@Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyCallable_Check > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyCallable_Check > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp__PyUnicodeUCS2_AsDefaultEncodedString referenced in function "bool > __cdecl vtkPythonGetStringValue(struct _object *,char const * > &,char const *)" > (??$vtkPythonGetStringValue@$$CBD@@YA_NPEAU_object@@AEAPEBDPEBD at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyUnicodeUCS2_DecodeUTF8 referenced in function "public: static struct > _object * __cdecl vtkPythonArgs::BuildValue(class vtkUnicodeString const &)" > (?BuildValue at vtkPythonArgs@@SAPEAU_object@@AEBVvtkUnicodeString@@@Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyUnicodeUCS2_DecodeUTF8 > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyUnicodeUCS2_AsUTF8String referenced in function "bool __cdecl > vtkPythonGetValue(struct _object *,class vtkUnicodeString &)" > (?vtkPythonGetValue@@YA_NPEAU_object@@AEAVvtkUnicodeString@@@Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyInt_FromLong referenced in function "struct _object * __cdecl > vtkPythonBuildTuple(signed char const *,int)" > (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyInt_FromLong > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyInt_FromLong > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyInt_AsLong referenced in function "bool __cdecl > vtkPythonGetUnsignedLongLongValue(struct _object > *,unsigned __int64 &)" > (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyInt_AsLong > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyInt_AsLong > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyBool_FromLong referenced in function "struct _object * __cdecl > vtkPythonBuildTuple(bool const *,int)" > (??$vtkPythonBuildTuple at _N@@YAPEAU_object@@PEB_NH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_FromUnsignedLong referenced in function "struct _object * > __cdecl vtkPythonBuildTuple(unsigned int const *,int)" > (??$vtkPythonBuildTuple at I@@YAPEAU_object@@PEBIH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_AsUnsignedLong referenced in function "bool __cdecl > vtkPythonGetValue(struct _object *,unsigned int &)" > (?vtkPythonGetValue@@YA_NPEAU_object@@AEAI at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_FromLongLong referenced in function "struct _object * __cdecl > vtkPythonBuildTuple<__int64>(__int64 const *,int)" > (??$vtkPythonBuildTuple at _J@@YAPEAU_object@@PEB_JH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_FromUnsignedLongLong referenced in function "struct _object * > __cdecl vtkPythonBuildTuple(unsigned __int64 const *,int)" > (??$vtkPythonBuildTuple at _K@@YAPEAU_object@@PEB_KH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_AsLongLong referenced in function "bool __cdecl > vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" > (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyLong_AsLongLong > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_AsUnsignedLongLong referenced in function "bool __cdecl > vtkPythonGetUnsignedLongLongValue(struct _object > *,unsigned __int64 &)" > (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyFloat_FromDouble referenced in function "struct _object * __cdecl > vtkPythonBuildTuple(float const *,int)" > (??$vtkPythonBuildTuple at M@@YAPEAU_object@@PEBMH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyFloat_FromDouble > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyFloat_AsDouble referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,float *,int)" > (??$vtkPythonGetArray at M@@YA_NPEAU_object@@PEAMH at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyFloat_AsDouble > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_FromStringAndSize referenced in function "public: static > struct _object * __cdecl vtkPythonArgs::BuildBytes(char const *,int)" > (?BuildBytes at vtkPythonArgs@@SAPEAU_object@@PEBDH at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromStringAndSize > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromStringAndSize > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromStringAndSize > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_FromString referenced in function "bool __cdecl > vtkPythonSetArray(struct _object *,char const *,int)" > (??$vtkPythonSetArray at D@@YA_NPEAU_object@@PEBDH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_FromString > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_AsString referenced in function "public: __cdecl > std::error_category::error_category(void)" (??0error_category at std@@QEAA at XZ) > > > vtkPythonArgs.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_AsString > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_AsStringAndSize referenced in function "bool __cdecl > vtkPythonGetStdStringValue(struct _object *,class > std::basic_string,class > std::allocator > &,char const *)" > (?vtkPythonGetStdStringValue@@YA_NPEAU_object@@AEAV?$basic_string at DU?$char_t > raits at D@std@@V?$allocator at D@2@@std@@PEBD at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyTuple_New referenced in function "struct _object * __cdecl > vtkPythonBuildTuple(signed char const *,int)" > (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_New > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_New > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_New > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_SetString referenced in function "public: __cdecl > std::_Generic_error_category::_Generic_error_category(void)" > (??0_Generic_error_category at std@@QEAA at XZ) > > > vtkPythonArgs.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_SetString > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_Occurred referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,float *,int)" > (??$vtkPythonGetArray at M@@YA_NPEAU_object@@PEAMH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Occurred > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Occurred > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Occurred > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_Fetch referenced in function "protected: bool __cdecl > vtkPythonArgs::RefineArgTypeError(int)" > (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_Restore referenced in function "protected: bool __cdecl > vtkPythonArgs::RefineArgTypeError(int)" > (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_ExceptionMatches referenced in function "protected: bool __cdecl > vtkPythonArgs::RefineArgTypeError(int)" > (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_ExceptionMatches > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_ExceptionMatches > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_ExceptionMatches > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySequence_Check referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,signed char *,int)" > (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PySequence_Check > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySequence_Size referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,signed char *,int)" > (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PySequence_Size > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PySequence_Size > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySequence_GetItem referenced in function "bool __cdecl > vtkPythonGetArray(struct _object *,signed char *,int)" > (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PySequence_GetItem > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PySequence_GetItem > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PySequence_SetItem referenced in function "bool __cdecl > vtkPythonSetArray(struct _object *,signed char const *,int)" > (??$vtkPythonSetArray at C@@YA_NPEAU_object@@PEBCH at Z) > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp__Py_NoneStruct referenced in function "struct _object * __cdecl > vtkPythonBuildTuple(signed char const *,int)" > (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) > > > vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp__Py_NoneStruct > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyFloat_Type referenced in function "bool __cdecl > vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" > (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyFloat_Type > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyFloat_Type > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_OverflowError referenced in function "bool __cdecl > vtkPythonGetUnsignedLongLongValue(struct _object > *,unsigned __int64 &)" > (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_TypeError referenced in function "bool __cdecl > vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" > (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_TypeError > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_ValueError > > > vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_ValueError referenced in function "protected: bool __cdecl > vtkPythonArgs::RefineArgTypeError(int)" > (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_ValueError > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_ValueError > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_ValueError > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GetAttrString referenced in function "public: virtual void > __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GetAttrString > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GetAttrString > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyLong_FromLong referenced in function "public: virtual void __cdecl > vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Clear > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Clear > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_Clear referenced in function "struct _object * __cdecl > `anonymous namespace'::BuildCallDataArgList(struct _object *,char const > *,struct _object *)" > (?BuildCallDataArgList@?A0xfc44b691@@YAPEAU_object@@PEAU2 at PEBD0@Z) > > > vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Clear > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Clear > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Clear > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyThreadState_Swap referenced in function "public: virtual void > __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_BuildValue > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_BuildValue referenced in function "struct _object * __cdecl > `anonymous namespace'::BuildCallDataArgList(struct _object *,char const > *,struct _object *)" > (?BuildCallDataArgList@?A0xfc44b691@@YAPEAU_object@@PEAU2 at PEBD0@Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_BuildValue > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_BuildValue > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_BuildValue > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_IsInitialized referenced in function "protected: virtual __cdecl > vtkPythonCommand::~vtkPythonCommand(void)" (??1vtkPythonCommand@@MEAA at XZ) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_IsInitialized > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_Print referenced in function "public: virtual void __cdecl > vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyErr_Print > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_Exit referenced in function "public: virtual void __cdecl > vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_Py_Exit > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyEval_CallObjectWithKeywords referenced in function "public: virtual > void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void > *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyEval_CallObjectWithKeywords > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyEval_CallObjectWithKeywords > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyEval_CallObjectWithKeywords > > > vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_KeyboardInterrupt referenced in function "public: virtual void > __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" > (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) > > > vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_KeyboardInterrupt > > > vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_Size referenced in function "public: static int __cdecl > vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" > (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyString_Size > > > vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyTuple_Size referenced in function "public: static int __cdecl > vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" > (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) > > > PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_Size > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_Size > > > vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyBool_Type referenced in function "public: static int __cdecl > vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" > (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_Hash referenced in function "public: static long __cdecl > vtkPythonUtil::VariantHash(class vtkVariant const *)" > (?VariantHash at vtkPythonUtil@@SAJPEBVvtkVariant@@@Z) > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp__Py_HashPointer referenced in function "public: static long __cdecl > vtkPythonUtil::VariantHash(class vtkVariant const *)" > (?VariantHash at vtkPythonUtil@@SAJPEBVvtkVariant@@@Z) > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp__PyString_Resize referenced in function "public: static struct _object > * __cdecl vtkPythonUtil::BuildDocString(char const * * const)" > (?BuildDocString at vtkPythonUtil@@SAPEAU_object@@QEAPEBD at Z) > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_Size referenced in function "public: static void __cdecl > vtkPythonUtil::RemoveObjectFromMap(struct _object *)" > (?RemoveObjectFromMap at vtkPythonUtil@@SAXPEAU_object@@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_Size > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyErr_GivenExceptionMatches referenced in function "public: static > void * __cdecl vtkPythonUtil::GetPointerFromSpecialObject(struct _object > *,char const *,struct _object * *)" > (?GetPointerFromSpecialObject at vtkPythonUtil@@SAPEAXPEAU_object@@PEBDPEAPEAU2 > @@Z) > > > vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_AtExit referenced in function "public: static void __cdecl > vtkPythonUtil::AddClassToMap(struct _object *,char const *)" > (?AddClassToMap at vtkPythonUtil@@SAXPEAU_object@@PEBD at Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GetAttr referenced in function "struct _object * __cdecl > PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GetAttr > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp__PyObject_GC_New referenced in function "struct _object * __cdecl > PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp__PyObject_GC_New > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp__PyObject_GC_New > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GC_Track referenced in function "struct _object * __cdecl > PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_Track > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_Track > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GC_UnTrack referenced in function "void __cdecl > PyVTKClass_Delete(struct _object *)" > (?PyVTKClass_Delete@@YAXPEAU_object@@@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_UnTrack > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_UnTrack > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GC_Del referenced in function "void __cdecl > PyVTKClass_Delete(struct _object *)" > (?PyVTKClass_Delete@@YAXPEAU_object@@@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_Del > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_GC_Del > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_InternFromString referenced in function PyVTKClass_New > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyTuple_GetItem referenced in function "struct _object * __cdecl > PyVTKClass_GetAttr(struct _object *,struct _object *)" > (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyTuple_GetItem > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_New referenced in function "struct _object * __cdecl > PyVTKClass_GetAttr(struct _object *,struct _object *)" > (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_New > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_New > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_GetItem referenced in function "struct _object * __cdecl > PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_GetItem > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_Keys referenced in function "struct _object * __cdecl > PyVTKClass_Dir(struct _object *,struct _object *)" > (?PyVTKClass_Dir@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_Update referenced in function "struct _object * __cdecl > PyVTKClass_Dir(struct _object *,struct _object *)" > (?PyVTKClass_Dir@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_GetItemString referenced in function "struct _object * __cdecl > PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_SetItemString referenced in function "struct _object * __cdecl > PyVTKClass_GetAttr(struct _object *,struct _object *)" > (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_SetItemString > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_DelItemString referenced in function "struct _object * __cdecl > PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyCFunction_NewEx referenced in function "struct _object * __cdecl > PyVTKClass_GetAttr(struct _object *,struct _object *)" > (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyCFunction_NewEx > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyCFunction_NewEx > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyArg_ParseTuple referenced in function "struct _object * __cdecl > PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyArg_ParseTuple > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyArg_ParseTuple > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyArg_ParseTupleAndKeywords referenced in function "struct _object * > __cdecl PyVTKClass_NewSubclass(struct _object *,struct _object *,struct > _object *)" (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyEval_GetGlobals referenced in function "struct _object * __cdecl > PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" > (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyType_Type referenced in function "void __cdecl `dynamic initializer > for 'PyVTKClassMetaType''(void)" (??__EPyVTKClassMetaType@@YAXXZ) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyType_Type > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyType_Type > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyType_Type > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyClass_Type referenced in function "void __cdecl `dynamic initializer > for 'PyVTKClass_Type''(void)" (??__EPyVTKClass_Type@@YAXXZ) > > > PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_AttributeError referenced in function "struct _object * __cdecl > PyVTKClass_GetAttr(struct _object *,struct _object *)" > (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_AttributeError > > > PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_AttributeError > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyExc_AttributeError > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_Repr referenced in function "struct _object * __cdecl > PyVTKMutableObject_Repr(struct _object *)" > (?PyVTKMutableObject_Repr@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_Repr > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_Str referenced in function "struct _object * __cdecl > PyVTKMutableObject_Str(struct _object *)" > (?PyVTKMutableObject_Str@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_RichCompare referenced in function "struct _object * __cdecl > PyVTKMutableObject_RichCompare(struct _object *,struct _object *,int)" > (?PyVTKMutableObject_RichCompare@@YAPEAU_object@@PEAU1 at 0H@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GenericGetAttr referenced in function "struct _object * > __cdecl PyVTKMutableObject_GetAttr(struct _object *,struct _object *)" > (?PyVTKMutableObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_HashNotImplemented referenced in function "void __cdecl > `dynamic initializer for 'PyVTKMutableObject_Type''(void)" > (??__EPyVTKMutableObject_Type@@YAXXZ) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_CoerceEx referenced in function "int __cdecl > PyVTKMutableObject_Coerce(struct _object * *,struct _object * *)" > (?PyVTKMutableObject_Coerce@@YAHPEAPEAU_object@@0 at Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_Free referenced in function "void __cdecl `dynamic > initializer for 'PyVTKMutableObject_Type''(void)" > (??__EPyVTKMutableObject_Type@@YAXXZ) > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyObject_Free > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp__PyObject_New referenced in function "struct _object * __cdecl > PyVTKMutableObject_New(struct _typeobject *,struct _object *,struct _object > *)" (?PyVTKMutableObject_New@@YAPEAU_object@@PEAU_typeobject@@PEAU1 at 1@Z) > > > PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol > __imp__PyObject_New > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Add referenced in function "struct _object * __cdecl > PyVTKMutableObject_Add(struct _object *,struct _object *)" > (?PyVTKMutableObject_Add@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Subtract referenced in function "struct _object * __cdecl > PyVTKMutableObject_Subtract(struct _object *,struct _object *)" > (?PyVTKMutableObject_Subtract@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Multiply referenced in function "struct _object * __cdecl > PyVTKMutableObject_Multiply(struct _object *,struct _object *)" > (?PyVTKMutableObject_Multiply@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Divide referenced in function "struct _object * __cdecl > PyVTKMutableObject_Divide(struct _object *,struct _object *)" > (?PyVTKMutableObject_Divide@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_FloorDivide referenced in function "struct _object * __cdecl > PyVTKMutableObject_FloorDivide(struct _object *,struct _object *)" > (?PyVTKMutableObject_FloorDivide@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_TrueDivide referenced in function "struct _object * __cdecl > PyVTKMutableObject_TrueDivide(struct _object *,struct _object *)" > (?PyVTKMutableObject_TrueDivide@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Remainder referenced in function "struct _object * __cdecl > PyVTKMutableObject_Remainder(struct _object *,struct _object *)" > (?PyVTKMutableObject_Remainder@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Divmod referenced in function "struct _object * __cdecl > PyVTKMutableObject_Divmod(struct _object *,struct _object *)" > (?PyVTKMutableObject_Divmod@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Power referenced in function "struct _object * __cdecl > PyVTKMutableObject_Power(struct _object *,struct _object *,struct _object > *)" (?PyVTKMutableObject_Power@@YAPEAU_object@@PEAU1 at 00@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Negative referenced in function "struct _object * __cdecl > PyVTKMutableObject_Negative(struct _object *)" > (?PyVTKMutableObject_Negative@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Positive referenced in function "struct _object * __cdecl > PyVTKMutableObject_Positive(struct _object *)" > (?PyVTKMutableObject_Positive@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Absolute referenced in function "struct _object * __cdecl > PyVTKMutableObject_Absolute(struct _object *)" > (?PyVTKMutableObject_Absolute@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Invert referenced in function "struct _object * __cdecl > PyVTKMutableObject_Invert(struct _object *)" > (?PyVTKMutableObject_Invert@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Lshift referenced in function "struct _object * __cdecl > PyVTKMutableObject_Lshift(struct _object *,struct _object *)" > (?PyVTKMutableObject_Lshift@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Rshift referenced in function "struct _object * __cdecl > PyVTKMutableObject_InPlaceRshift(struct _object *,struct _object *)" > (?PyVTKMutableObject_InPlaceRshift@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_And referenced in function "struct _object * __cdecl > PyVTKMutableObject_InPlaceAnd(struct _object *,struct _object *)" > (?PyVTKMutableObject_InPlaceAnd@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Xor referenced in function "struct _object * __cdecl > PyVTKMutableObject_InPlaceXor(struct _object *,struct _object *)" > (?PyVTKMutableObject_InPlaceXor@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Or referenced in function "struct _object * __cdecl > PyVTKMutableObject_InPlaceOr(struct _object *,struct _object *)" > (?PyVTKMutableObject_InPlaceOr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Index referenced in function "struct _object * __cdecl > PyVTKMutableObject_Index(struct _object *)" > (?PyVTKMutableObject_Index@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Int referenced in function "struct _object * __cdecl > PyVTKMutableObject_Int(struct _object *)" > (?PyVTKMutableObject_Int@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Long referenced in function "struct _object * __cdecl > PyVTKMutableObject_Long(struct _object *)" > (?PyVTKMutableObject_Long@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_Float referenced in function "struct _object * __cdecl > PyVTKMutableObject_Float(struct _object *)" > (?PyVTKMutableObject_Float@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyNumber_ToBase referenced in function "struct _object * __cdecl > PyVTKMutableObject_Hex(struct _object *)" > (?PyVTKMutableObject_Hex@@YAPEAU_object@@PEAU1@@Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_ClearWeakRefs referenced in function "void __cdecl > PyVTKObject_Delete(struct _object *)" > (?PyVTKObject_Delete@@YAXPEAU_object@@@Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_SetItem referenced in function "int __cdecl > PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" > (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) > > > PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol > __imp_PyDict_SetItem > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyDict_DelItem referenced in function "int __cdecl > PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" > (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyMethod_New referenced in function "struct _object * __cdecl > PyVTKObject_GetAttr(struct _object *,struct _object *)" > (?PyVTKObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyCFunction_Type referenced in function "struct _object * __cdecl > PyVTKObject_GetAttr(struct _object *,struct _object *)" > (?PyVTKObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_RuntimeError referenced in function "int __cdecl > PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" > (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) > > > PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyExc_NotImplementedError referenced in function PyVTKObject_New > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyType_Ready referenced in function PyVTKSpecialType_New > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_ReprEnter referenced in function PyVTKSpecialObject_SequenceString > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_Py_ReprLeave referenced in function PyVTKSpecialObject_SequenceString > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_Concat referenced in function > PyVTKSpecialObject_SequenceString > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyString_ConcatAndDel referenced in function PyVTKSpecialObject_Repr > > > PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyBaseObject_Type referenced in function PyVTKSpecialObject_Repr > > > PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_CallMethod referenced in function "struct _object * __cdecl > PyVTKTemplate_HasKey(struct _object *,struct _object *)" > (?PyVTKTemplate_HasKey@@YAPEAU_object@@PEAU1 at 0@Z) > > > PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_Size referenced in function "__int64 __cdecl > PyVTKTemplate_Size(struct _object *)" > (?PyVTKTemplate_Size@@YA_JPEAU_object@@@Z) > > > PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol > __imp_PyObject_GetItem referenced in function "struct _object * __cdecl > PyVTKTemplate_GetItem(struct _object *,struct _object *)" > (?PyVTKTemplate_GetItem@@YAPEAU_object@@PEAU1 at 0@Z) > > > bin\vtkWrappingPython27Core-pv4.2.dll : fatal error LNK1120: 123 unresolved > externals > > > LINK failed. with 1120 > > ninja: build stopped: subcommand failed. > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Sep 23 16:01:22 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 23 Sep 2014 16:01:22 -0400 Subject: [Paraview] python link error when compiling PV-v4.2.0-RC1-128-gc89b0ad + python-2.7.3 + VS2013 Express (UNCLASSIFIED) In-Reply-To: References: Message-ID: Ah, okay, sorry I missed the part that you were not using the Superbuild. The DUSE_SYSTEM_PYTHON is only for Superbuilds, so it won't matter for your regular ParaView build. My first pass at building ParaView with VS2013 (ParaView not ParaViewSuperbuild) exposed a few issues which I addressed. I can't remember if I built with Python support enabled, however. I'll check that once I am home (since it was on my home machine). Ben, we should have VS2013 dashboard setup on Miranda soon. That'll be the first step before we move to supporting superbuilds with VS2013 too. Simon, I suggest give us a few days to track this own, unless you're feeling adventurous :). Utkarsh On Tue, Sep 23, 2014 at 3:48 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Utkarsh, > > Thanks for the info. I did followed that thread and my conclusion at the end > was ParaView for windows compiled for vs2012 :) so, I went a step further to > try to get compiled with vs2013Express since that's the compiler I have access > to on windows ;) I thought getting python compiled on any of the compiler of > choice is the prerequisite... apparently I still don't have python working > even after I manage to compile it. :( > > I am not doing the superbuild and just ParaView git from source build. I ran > into too many errors with VS2013Express + ninja-1.5.1 with the superbuild > route that I don't even know where/how to begin to ask for help. > > I will give -DUSE_SYSTEM_PYTHON=ON flag a try. If that doesn't work, I will > have my justification to ask for VS2008 purchased/installed on my system. > > Thanks for your help. > > Thanks > -simon > > > > > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Tuesday, September 23, 2014 3:17 PM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] python link error when compiling > PV-v4.2.0-RC1-128-gc89b0ad + python-2.7.3 + VS2013 Express (UNCLASSIFIED) > > Simon, > > As this states [1], superbuild on Windows with Python is only > supported for VS 2008 currently. We will soon add support for VS2013. > If you want to use VS2013, using USE_SYSTEM_python=ON may be worth a > try, but these was a discussion on the mailing list a little while ago > that too may have problems -- but it wasn't clear if it was build > problem, or an environment issue. Worth a shot, however. > > [1] http://www.paraview.org/Wiki/ParaView/Superbuild#Windows > > > On Tue, Sep 23, 2014 at 1:34 PM, Su, Simon M CTR USARMY ARL (US) > wrote: >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> Hello, >> >> I am trying to get a ParaView + vrpn running on a zSpace. With zSpace VRPN >> server only available on Windows, here goes the following... >> >> I am able to get ParaView build with ninja when I only do >> -DPARAVIEW_USE_MPI:BOOL=ON and the binary appears to be working. But when I >> included >> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON >> I have linking problem. How do you make sure that I have a working Python >> library? Dumpbin is reporting python is x64 library and I am trying to >> compile a x64 ParaView. >> >> I am getting some 26 unresolved externals when ninja is "Creating library >> lib\vtkPythonInterpreter-pv4.2.lib and object >> lib\vtkPythonInterpreter-pv4.2.exp." and some 123 unresolved externals when >> ninja is "Creating library lib\vtkWrappingPython27Core-pv4.2.lib and object >> lib\vtkWrappingPython27Core-pv4.2.exp"- included at the end of this email. >> >> The odd thing is, both failed command has python27.lib library in it >> >> FAILED: cmd.exe /C "cd . && >> C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll >> C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo >> VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho >> nInterpreter.cxx.obj >> VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho >> nInteractiveInterpreter.cxx.obj /out:bin\vtkPythonInterpreter-pv4.2.dll >> /implib:lib\vtkPythonInterpreter-pv4.2.lib >> /pdb:bin\vtkPythonInterpreter-pv4.2.pdb /dll /version:1.0 /machine:x64 >> /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib >> C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib >> Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib >> ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." >> >> And >> >> FAILED: cmd.exe /C "cd . && >> C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll >> C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonArgs.c >> xx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonComman >> d.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonOverlo >> ad.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonUtil.c >> xx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkSmartPyObjec >> t.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKClass.cxx. >> obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKMutableObj >> ect.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKObject.cxx >> .obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKSpecialObj >> ect.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKTemplate.c >> xx.obj /out:bin\vtkWrappingPython27Core-pv4.2.dll >> /implib:lib\vtkWrappingPython27Core-pv4.2.lib >> /pdb:bin\vtkWrappingPython27Core-pv4.2.pdb /dll /version:1.0 /machine:x64 >> /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib >> C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib >> Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib >> ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." >> >> Do I have to included another python library? If so, what would that be? >> >> >> I am building a 64bit version of ParaView on Windows 7 using >> 1. VS2013 express version >> 2. Python-2.7.3 - release version build with cmake + ninja >> (https://github.com/davidsansome/python-cmake-buildsystem) >> cmake \ >> -DCMAKE_INSTALL_PREFIX=C:\tools\python\python-2.7.3 \ >> -DBUILD_SHARED:BOOL=ON \ >> -DCMAKE_BUILD_TYPE=Release \ >> -DZLIB_LIBRARY=C:\tools\zlib\zlib-1.2.8\lib\zlib.lib \ >> -DZLIB_INCLUDE_DIR=C:\tools\zlib\zlib-1.2.8\include \ >> ..\python-cmake-buildsystem -G Ninja \ >> ninja >> ninja install >> >> 3. Ninja-1.5.1 - build using the python-2.7.3 above so, python appears to >> work >> python bootstrap.py --x64 >> >> 4. ParaView-v4.2.0-RC1-128-gc89b0ad >> >> git clone git://paraview.org/ParaView.git >> cd ParaView >> git pull >> git submodule update --init >> >> cmake \ >> -G Ninja \ >> -DCMAKE_INSTALL_PREFIX=C:\tools\ParaView\ParaView-v4.2.0-RC1-100-gfa06130 \ >> -DCMAKE_BUILD_TYPE=Release \ >> -DZLIB_LIBRARY=C:\tools\zlib\zlib-1.2.8\lib\zlib.lib \ >> -DZLIB_INCLUDE_DIR=C:\tools\zlib\zlib-1.2.8\include >> -DCMAKE_BUILD_TYPE=Release \ >> -DPARAVIEW_USE_MPI:BOOL=ON \ >> -DMPI_CXX_LIBRARIES:STRING="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi_cxx.li >> b" \ >> -DMPI_C_LIBRARIES:STRING="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi.lib" \ >> -DMPI_LIBRARY:FILEPATH="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi_cxx.lib" \ >> -DMPI_CXX_INCLUDE_PATH=C:/tools/openmpi/openmpi-1.4.4/include \ >> -DMPI_C_INCLUDE_PATH=C:/tools/openmpi/openmpi-1.4.4/include \ >> -DGLUT_glut_LIBRARY=C:\tools\freeglut\freeglut-2.8.1\lib\freeglut.lib \ >> -DGLUT_INCLUDE_DIR=C:\tools\freeglut\freeglut-2.8.1\include \ >> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ >> -DPYTHON_LIBRARY=C:\tools\python\python-2.7.3\libs\python27.lib \ >> -DPYTHON_INCLUDE_DIR=C:\tools\python\python-2.7.3\include \ >> -DPYTHON_EXECUTABLE=C:\tools\python\python-2.7.3\bin\python.exe \ >> ..\ParaView-v4.2.0-RC1-128-gc89b0ad >> >> ninja >> >> >> >> Any help is much appreciated. >> >> Thanks >> -simon >> >> >> ======================== linking error ======================= >> [1/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractCellLocato >> r.cxx.obj >> [2/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractPointLocat >> or.cxx.obj >> [3/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAdjacentVertexIter >> ator.cxx.obj >> [4/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRBox.cxx.obj >> [5/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRUtilities.cxx.o >> bj >> [6/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnimationScene.cxx >> .obj >> [7/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnnotation.cxx.obj >> [8/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnnotationLayers.c >> xx.obj >> [9/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkArrayData.cxx.obj >> [10/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAttributesErrorMet >> ric.cxx.obj >> [11/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuad.cx >> x.obj >> [12/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuadrat >> icHexahedron.cxx.obj >> [13/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuadrat >> icWedge.cxx.obj >> [14/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticTriangl >> e.cxx.obj >> [15/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBox.cxx.obj >> [16/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBSPCuts.cxx.obj >> [17/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBSPIntersections.c >> xx.obj >> [18/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCell3D.cxx.obj >> [19/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellArray.cxx.obj >> [20/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCell.cxx.obj >> [21/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellData.cxx.obj >> [22/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellIterator.cxx.o >> bj >> [23/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellLinks.cxx.obj >> [24/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellLocator.cxx.ob >> j >> [25/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellTypes.cxx.obj >> [26/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCompositeDataSet.c >> xx.obj >> [27/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCompositeDataItera >> tor.cxx.obj >> [28/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCone.cxx.obj >> [29/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkConvexPointSet.cxx >> .obj >> [30/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCubicLine.cxx.obj >> [31/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCylinder.cxx.obj >> [32/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetCellIterato >> r.cxx.obj >> [33/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectCollecti >> on.cxx.obj >> [34/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObject.cxx.obj >> [35/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTypes.cx >> x.obj >> [36/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTree.cxx >> .obj >> [37/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTreeIter >> ator.cxx.obj >> [38/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetAttributes. >> cxx.obj >> [39/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetCollection. >> cxx.obj >> [40/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSet.cxx.obj >> [41/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDirectedAcyclicGra >> ph.cxx.obj >> [42/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDirectedGraph.cxx. >> obj >> [43/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDistributedGraphHe >> lper.cxx.obj >> [44/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEdgeListIterator.c >> xx.obj >> [45/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEdgeTable.cxx.obj >> [46/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEmptyCell.cxx.obj >> [47/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkExplicitCell.cxx.o >> bj >> [48/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkExtractStructuredG >> ridHelper.cxx.obj >> [49/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkFieldData.cxx.obj >> [50/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAdaptorCell >> .cxx.obj >> [51/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAttributeCo >> llection.cxx.obj >> [52/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAttribute.c >> xx.obj >> [53/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCell.cxx.ob >> j >> [54/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCellIterato >> r.cxx.obj >> [55/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCellTessell >> ator.cxx.obj >> [56/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericDataSet.cxx >> .obj >> [57/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericEdgeTable.c >> xx.obj >> [58/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericInterpolate >> dVelocityField.cxx.obj >> [59/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericPointIterat >> or.cxx.obj >> [60/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericSubdivision >> ErrorMetric.cxx.obj >> [61/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGeometricErrorMetr >> ic.cxx.obj >> [62/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraph.cxx.obj >> [63/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraphEdge.cxx.obj >> [64/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraphInternals.cxx >> .obj >> [65/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHexagonalPrism.cxx >> .obj >> [66/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHexahedron.cxx.obj >> [67/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHierarchicalBoxDat >> aIterator.cxx.obj >> [68/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHierarchicalBoxDat >> aSet.cxx.obj >> [69/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctreeCursor. >> cxx.obj >> [70/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctree.cxx.ob >> j >> [71/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctreePointsG >> rabber.cxx.obj >> [72/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTree.cxx.obj >> [73/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTreeCursor.cx >> x.obj >> [74/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTreeGrid.cxx. >> obj >> [75/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImageData.cxx.obj >> [76/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImageIterator.cxx. >> obj >> [77/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitBoolean.cx >> x.obj >> [78/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitDataSet.cx >> x.obj >> [79/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitFunctionCo >> llection.cxx.obj >> [80/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitFunction.c >> xx.obj >> [81/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitHalo.cxx.o >> bj >> [82/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitSelectionL >> oop.cxx.obj >> [83/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitSum.cxx.ob >> j >> [84/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitVolume.cxx >> .obj >> [85/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitWindowFunc >> tion.cxx.obj >> [86/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalOctreeN >> ode.cxx.obj >> [87/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalOctreeP >> ointLocator.cxx.obj >> [88/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalPointLo >> cator.cxx.obj >> [89/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkInEdgeIterator.cxx >> .obj >> [90/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkInformationQuadrat >> ureSchemeDefinitionVectorKey.cxx.obj >> [91/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIterativeClosestPo >> intTransform.cxx.obj >> [92/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdNode.cxx.obj >> [93/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdTree.cxx.obj >> [94/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdTreePointLocator >> .cxx.obj >> [95/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkLine.cxx.obj >> [96/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkLocator.cxx.obj >> [97/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMarchingSquaresLin >> eCases.cxx.obj >> [98/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMarchingCubesTrian >> gleCases.cxx.obj >> [99/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMeanValueCoordinat >> esInterpolator.cxx.obj >> [100/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMergePoints.cxx.ob >> j >> [101/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMultiBlockDataSet. >> cxx.obj >> [102/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMultiPieceDataSet. >> cxx.obj >> [103/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMutableDirectedGra >> ph.cxx.obj >> [104/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMutableUndirectedG >> raph.cxx.obj >> [105/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonLinearCell.cxx. >> obj >> [106/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonMergingPointLoc >> ator.cxx.obj >> [107/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOctreePointLocator >> .cxx.obj >> [108/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOctreePointLocator >> Node.cxx.obj >> [109/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOrderedTriangulato >> r.cxx.obj >> [110/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOutEdgeIterator.cx >> x.obj >> [111/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPath.cxx.obj >> [112/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPentagonalPrism.cx >> x.obj >> [113/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPerlinNoise.cxx.ob >> j >> [114/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPiecewiseFunction. >> cxx.obj >> [115/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPixel.cxx.obj >> [116/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPixelExtent.cxx.ob >> j >> [117/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlaneCollection.cx >> x.obj >> [118/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlane.cxx.obj >> [119/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlanes.cxx.obj >> [120/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlanesIntersection >> .cxx.obj >> [121/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointData.cxx.obj >> [122/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointLocator.cxx.o >> bj >> [123/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointSet.cxx.obj >> [124/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointSetCellIterat >> or.cxx.obj >> [125/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointsProjectedHul >> l.cxx.obj >> [126/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyDataCollection >> .cxx.obj >> [127/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyData.cxx.obj >> [128/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolygon.cxx.obj >> [129/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyhedron.cxx.obj >> [130/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyLine.cxx.obj >> [131/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyPlane.cxx.obj >> [132/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyVertex.cxx.obj >> [133/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPyramid.cxx.obj >> [134/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuad.cxx.obj >> [135/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticEdge.cxx. >> obj >> [136/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticHexahedro >> n.cxx.obj >> [137/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticLinearQua >> d.cxx.obj >> [138/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticLinearWed >> ge.cxx.obj >> [139/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticPolygon.c >> xx.obj >> [140/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticPyramid.c >> xx.obj >> [141/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticQuad.cxx. >> obj >> [142/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticTetra.cxx >> .obj >> [143/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticTriangle. >> cxx.obj >> [144/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticWedge.cxx >> .obj >> [145/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadratureSchemeDe >> finition.cxx.obj >> [146/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadric.cxx.obj >> [147/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkRectilinearGrid.cx >> x.obj >> [148/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkReebGraph.cxx.obj >> [149/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkReebGraphSimplific >> ationMetric.cxx.obj >> [150/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSelection.cxx.obj >> [151/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSelectionNode.cxx. >> obj >> [152/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSimpleCellTessella >> tor.cxx.obj >> [153/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSmoothErrorMetric. >> cxx.obj >> [154/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSphere.cxx.obj >> [155/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSpline.cxx.obj >> [156/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredData.cxx >> .obj >> [157/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredExtent.c >> xx.obj >> [158/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredGrid.cxx >> .obj >> [159/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredPointsCo >> llection.cxx.obj >> [160/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredPoints.c >> xx.obj >> [161/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredVisibili >> tyConstraint.cxx.obj >> [162/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSuperquadric.cxx.o >> bj >> [163/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTable.cxx.obj >> [164/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTensor.cxx.obj >> [165/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTetra.cxx.obj >> [166/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeBFSIterator.cx >> x.obj >> [167/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTree.cxx.obj >> [168/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeDFSIterator.cx >> x.obj >> [169/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriangle.cxx.obj >> [170/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriangleStrip.cxx. >> obj >> [171/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriQuadraticHexahe >> dron.cxx.obj >> [172/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUndirectedGraph.cx >> x.obj >> [173/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGrid.cxx.ob >> j >> [174/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGrid.c >> xx.obj >> [175/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGridBa >> se.cxx.obj >> [176/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGridCe >> llIterator.cxx.obj >> [177/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVertex.cxx.obj >> [178/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVertexListIterator >> .cxx.obj >> [179/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVoxel.cxx.obj >> [180/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkWedge.cxx.obj >> [181/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkXMLDataElement.cxx >> .obj >> [182/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeIterator.cxx.o >> bj >> [183/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBoundingBox.cxx.ob >> j >> [184/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAtom.cxx.obj >> [185/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBond.cxx.obj >> [186/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMolecule.cxx.obj >> [187/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractElectronic >> Data.cxx.obj >> [188/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonOverlappingAMR. >> cxx.obj >> [189/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOverlappingAMR.cxx >> .obj >> [190/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRInformation.cxx >> .obj >> [191/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRDataInternals.c >> xx.obj >> [192/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGridAMR.cxx >> .obj >> [193/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGridAMRData >> Iterator.cxx.obj >> [194/16592] Linking CXX shared library bin\vtkPythonInterpreter-pv4.2.dll >> [195/16592] Linking CXX shared library bin\vtkWrappingPython27Core-pv4.2.dll >> FAILED: cmd.exe /C "cd . && >> C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll >> C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo >> VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho >> nInterpreter.cxx.obj >> VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho >> nInteractiveInterpreter.cxx.obj /out:bin\vtkPythonInterpreter-pv4.2.dll >> /implib:lib\vtkPythonInterpreter-pv4.2.lib >> /pdb:bin\vtkPythonInterpreter-pv4.2.pdb /dll /version:1.0 /machine:x64 >> /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib >> C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib >> Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib >> ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." >> Creating library lib\vtkPythonInterpreter-pv4.2.lib and object >> lib\vtkPythonInterpreter-pv4.2.exp >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyType_IsSubtype referenced in function "struct _object * __cdecl >> vtkWrite(struct _object *,struct _object *)" >> (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyType_Ready referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GenericGetAttr referenced in function "void __cdecl `dynamic >> initializer for 'vtkPythonStdStreamCaptureHelperType''(void)" >> (??__EvtkPythonStdStreamCaptureHelperType@@YAXXZ) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GenericSetAttr referenced in function "void __cdecl `dynamic >> initializer for 'vtkPythonStdStreamCaptureHelperType''(void)" >> (??__EvtkPythonStdStreamCaptureHelperType@@YAXXZ) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp__PyObject_New referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_FromString referenced in function "public: static bool >> __cdecl vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external >> symbol __imp_PyString_FromString >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyList_Insert referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyArg_ParseTuple referenced in function "struct _object * __cdecl >> vtkWrite(struct _object *,struct _object *)" >> (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_BuildValue referenced in function "struct _object * __cdecl >> vtkWrite(struct _object *,struct _object *)" >> (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_SetProgramName referenced in function "public: static void __cdecl >> vtkPythonInterpreter::SetProgramName(char const *)" >> (?SetProgramName at vtkPythonInterpreter@@SAXPEBD at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_InitializeEx referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_Finalize referenced in function "public: static void __cdecl >> vtkPythonInterpreter::Finalize(void)" >> (?Finalize at vtkPythonInterpreter@@SAXXZ) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_IsInitialized referenced in function "public: static void __cdecl >> vtkPythonInterpreter::Finalize(void)" >> (?Finalize at vtkPythonInterpreter@@SAXXZ) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyRun_SimpleStringFlags referenced in function "public: static void >> __cdecl vtkPythonInterpreter::RunSimpleString(char const *)" >> (?RunSimpleString at vtkPythonInterpreter@@SAXPEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external >> symbol __imp_PyRun_SimpleStringFlags >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_Main referenced in function "public: static int __cdecl >> vtkPythonInterpreter::PyMain(int,char * *)" >> (?PyMain at vtkPythonInterpreter@@SAHHPEAPEAD at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySys_GetObject referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external >> symbol __imp_PySys_GetObject >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySys_SetObject referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved external >> symbol __imp_PySys_SetObject >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external >> symbol __imp_PyDict_GetItemString referenced in function "public: struct >> _object * __cdecl >> vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" >> (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE >> AU_object@@XZ) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external >> symbol __imp_PyModule_GetDict referenced in function "public: struct _object >> * __cdecl >> vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" >> (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE >> AU_object@@XZ) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external >> symbol __imp_PyErr_Clear referenced in function "public: int __cdecl >> vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" >> (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external >> symbol __imp_PyArg_Parse referenced in function "public: bool __cdecl >> vtkPythonInteractiveInterpreter::Push(char const * const)" >> (?Push at vtkPythonInteractiveInterpreter@@QEAA_NQEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external >> symbol __imp_PyRun_StringFlags referenced in function "public: int __cdecl >> vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" >> (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external >> symbol __imp_PyErr_Print referenced in function "public: int __cdecl >> vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" >> (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external >> symbol __imp_Py_FlushLine referenced in function "public: int __cdecl >> vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" >> (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external >> symbol __imp_PyImport_AddModule referenced in function "public: struct >> _object * __cdecl >> vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" >> (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE >> AU_object@@XZ) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved external >> symbol __imp_PyObject_CallMethod referenced in function "public: bool >> __cdecl vtkPythonInteractiveInterpreter::Push(char const * const)" >> (?Push at vtkPythonInteractiveInterpreter@@QEAA_NQEBD at Z) >> >> >> bin\vtkPythonInterpreter-pv4.2.dll : fatal error LNK1120: 26 unresolved >> externals >> >> >> LINK failed. with 1120 >> >> FAILED: cmd.exe /C "cd . && >> C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E vs_link_dll >> C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonArgs.c >> xx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonComman >> d.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonOverlo >> ad.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonUtil.c >> xx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkSmartPyObjec >> t.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKClass.cxx. >> obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKMutableObj >> ect.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKObject.cxx >> .obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKSpecialObj >> ect.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKTemplate.c >> xx.obj /out:bin\vtkWrappingPython27Core-pv4.2.dll >> /implib:lib\vtkWrappingPython27Core-pv4.2.lib >> /pdb:bin\vtkWrappingPython27Core-pv4.2.pdb /dll /version:1.0 /machine:x64 >> /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib >> C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib >> Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib >> ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." >> Creating library lib\vtkWrappingPython27Core-pv4.2.lib and object >> lib\vtkWrappingPython27Core-pv4.2.exp >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyType_IsSubtype referenced in function "bool __cdecl >> vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" >> (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyType_IsSubtype >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyType_IsSubtype >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_IsTrue referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,bool *,int)" >> (??$vtkPythonGetArray at _N@@YA_NPEAU_object@@PEA_NH at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_IsTrue >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_IsTrue >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyCallable_Check referenced in function "public: bool __cdecl >> vtkPythonArgs::GetFunction(struct _object * &)" >> (?GetFunction at vtkPythonArgs@@QEAA_NAEAPEAU_object@@@Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyCallable_Check >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyCallable_Check >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp__PyUnicodeUCS2_AsDefaultEncodedString referenced in function "bool >> __cdecl vtkPythonGetStringValue(struct _object *,char const * >> &,char const *)" >> (??$vtkPythonGetStringValue@$$CBD@@YA_NPEAU_object@@AEAPEBDPEBD at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyUnicodeUCS2_DecodeUTF8 referenced in function "public: static struct >> _object * __cdecl vtkPythonArgs::BuildValue(class vtkUnicodeString const &)" >> (?BuildValue at vtkPythonArgs@@SAPEAU_object@@AEBVvtkUnicodeString@@@Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyUnicodeUCS2_DecodeUTF8 >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyUnicodeUCS2_AsUTF8String referenced in function "bool __cdecl >> vtkPythonGetValue(struct _object *,class vtkUnicodeString &)" >> (?vtkPythonGetValue@@YA_NPEAU_object@@AEAVvtkUnicodeString@@@Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyInt_FromLong referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple(signed char const *,int)" >> (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyInt_FromLong >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyInt_FromLong >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyInt_AsLong referenced in function "bool __cdecl >> vtkPythonGetUnsignedLongLongValue(struct _object >> *,unsigned __int64 &)" >> (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyInt_AsLong >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyInt_AsLong >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyBool_FromLong referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple(bool const *,int)" >> (??$vtkPythonBuildTuple at _N@@YAPEAU_object@@PEB_NH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_FromUnsignedLong referenced in function "struct _object * >> __cdecl vtkPythonBuildTuple(unsigned int const *,int)" >> (??$vtkPythonBuildTuple at I@@YAPEAU_object@@PEBIH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_AsUnsignedLong referenced in function "bool __cdecl >> vtkPythonGetValue(struct _object *,unsigned int &)" >> (?vtkPythonGetValue@@YA_NPEAU_object@@AEAI at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_FromLongLong referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple<__int64>(__int64 const *,int)" >> (??$vtkPythonBuildTuple at _J@@YAPEAU_object@@PEB_JH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_FromUnsignedLongLong referenced in function "struct _object * >> __cdecl vtkPythonBuildTuple(unsigned __int64 const *,int)" >> (??$vtkPythonBuildTuple at _K@@YAPEAU_object@@PEB_KH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_AsLongLong referenced in function "bool __cdecl >> vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" >> (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyLong_AsLongLong >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_AsUnsignedLongLong referenced in function "bool __cdecl >> vtkPythonGetUnsignedLongLongValue(struct _object >> *,unsigned __int64 &)" >> (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyFloat_FromDouble referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple(float const *,int)" >> (??$vtkPythonBuildTuple at M@@YAPEAU_object@@PEBMH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyFloat_FromDouble >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyFloat_AsDouble referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,float *,int)" >> (??$vtkPythonGetArray at M@@YA_NPEAU_object@@PEAMH at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyFloat_AsDouble >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_FromStringAndSize referenced in function "public: static >> struct _object * __cdecl vtkPythonArgs::BuildBytes(char const *,int)" >> (?BuildBytes at vtkPythonArgs@@SAPEAU_object@@PEBDH at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromStringAndSize >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromStringAndSize >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromStringAndSize >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_FromString referenced in function "bool __cdecl >> vtkPythonSetArray(struct _object *,char const *,int)" >> (??$vtkPythonSetArray at D@@YA_NPEAU_object@@PEBDH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_AsString referenced in function "public: __cdecl >> std::error_category::error_category(void)" (??0error_category at std@@QEAA at XZ) >> >> >> vtkPythonArgs.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_AsStringAndSize referenced in function "bool __cdecl >> vtkPythonGetStdStringValue(struct _object *,class >> std::basic_string,class >> std::allocator > &,char const *)" >> (?vtkPythonGetStdStringValue@@YA_NPEAU_object@@AEAV?$basic_string at DU?$char_t >> raits at D@std@@V?$allocator at D@2@@std@@PEBD at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyTuple_New referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple(signed char const *,int)" >> (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_New >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_New >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_New >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_SetString referenced in function "public: __cdecl >> std::_Generic_error_category::_Generic_error_category(void)" >> (??0_Generic_error_category at std@@QEAA at XZ) >> >> >> vtkPythonArgs.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_Occurred referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,float *,int)" >> (??$vtkPythonGetArray at M@@YA_NPEAU_object@@PEAMH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Occurred >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Occurred >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Occurred >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_Fetch referenced in function "protected: bool __cdecl >> vtkPythonArgs::RefineArgTypeError(int)" >> (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_Restore referenced in function "protected: bool __cdecl >> vtkPythonArgs::RefineArgTypeError(int)" >> (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_ExceptionMatches referenced in function "protected: bool __cdecl >> vtkPythonArgs::RefineArgTypeError(int)" >> (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_ExceptionMatches >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_ExceptionMatches >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_ExceptionMatches >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySequence_Check referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,signed char *,int)" >> (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PySequence_Check >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySequence_Size referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,signed char *,int)" >> (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PySequence_Size >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PySequence_Size >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySequence_GetItem referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,signed char *,int)" >> (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PySequence_GetItem >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PySequence_GetItem >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySequence_SetItem referenced in function "bool __cdecl >> vtkPythonSetArray(struct _object *,signed char const *,int)" >> (??$vtkPythonSetArray at C@@YA_NPEAU_object@@PEBCH at Z) >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp__Py_NoneStruct referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple(signed char const *,int)" >> (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyFloat_Type referenced in function "bool __cdecl >> vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" >> (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyFloat_Type >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyFloat_Type >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_OverflowError referenced in function "bool __cdecl >> vtkPythonGetUnsignedLongLongValue(struct _object >> *,unsigned __int64 &)" >> (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_TypeError referenced in function "bool __cdecl >> vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" >> (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_ValueError >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_ValueError referenced in function "protected: bool __cdecl >> vtkPythonArgs::RefineArgTypeError(int)" >> (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_ValueError >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_ValueError >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_ValueError >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GetAttrString referenced in function "public: virtual void >> __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GetAttrString >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GetAttrString >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_FromLong referenced in function "public: virtual void __cdecl >> vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Clear >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Clear >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_Clear referenced in function "struct _object * __cdecl >> `anonymous namespace'::BuildCallDataArgList(struct _object *,char const >> *,struct _object *)" >> (?BuildCallDataArgList@?A0xfc44b691@@YAPEAU_object@@PEAU2 at PEBD0@Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Clear >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Clear >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Clear >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyThreadState_Swap referenced in function "public: virtual void >> __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_BuildValue >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_BuildValue referenced in function "struct _object * __cdecl >> `anonymous namespace'::BuildCallDataArgList(struct _object *,char const >> *,struct _object *)" >> (?BuildCallDataArgList@?A0xfc44b691@@YAPEAU_object@@PEAU2 at PEBD0@Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_BuildValue >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_BuildValue >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_BuildValue >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_IsInitialized referenced in function "protected: virtual __cdecl >> vtkPythonCommand::~vtkPythonCommand(void)" (??1vtkPythonCommand@@MEAA at XZ) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_IsInitialized >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_Print referenced in function "public: virtual void __cdecl >> vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Print >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_Exit referenced in function "public: virtual void __cdecl >> vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_Exit >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyEval_CallObjectWithKeywords referenced in function "public: virtual >> void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void >> *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyEval_CallObjectWithKeywords >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyEval_CallObjectWithKeywords >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyEval_CallObjectWithKeywords >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_KeyboardInterrupt referenced in function "public: virtual void >> __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_KeyboardInterrupt >> >> >> vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_Size referenced in function "public: static int __cdecl >> vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" >> (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_Size >> >> >> vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyTuple_Size referenced in function "public: static int __cdecl >> vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" >> (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_Size >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_Size >> >> >> vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyBool_Type referenced in function "public: static int __cdecl >> vtkPythonOverload::CheckArg(struct _object *,char const *,char const *,int)" >> (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_Hash referenced in function "public: static long __cdecl >> vtkPythonUtil::VariantHash(class vtkVariant const *)" >> (?VariantHash at vtkPythonUtil@@SAJPEBVvtkVariant@@@Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp__Py_HashPointer referenced in function "public: static long __cdecl >> vtkPythonUtil::VariantHash(class vtkVariant const *)" >> (?VariantHash at vtkPythonUtil@@SAJPEBVvtkVariant@@@Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp__PyString_Resize referenced in function "public: static struct _object >> * __cdecl vtkPythonUtil::BuildDocString(char const * * const)" >> (?BuildDocString at vtkPythonUtil@@SAPEAU_object@@QEAPEBD at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_Size referenced in function "public: static void __cdecl >> vtkPythonUtil::RemoveObjectFromMap(struct _object *)" >> (?RemoveObjectFromMap at vtkPythonUtil@@SAXPEAU_object@@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_Size >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_GivenExceptionMatches referenced in function "public: static >> void * __cdecl vtkPythonUtil::GetPointerFromSpecialObject(struct _object >> *,char const *,struct _object * *)" >> (?GetPointerFromSpecialObject at vtkPythonUtil@@SAPEAXPEAU_object@@PEBDPEAPEAU2 >> @@Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_AtExit referenced in function "public: static void __cdecl >> vtkPythonUtil::AddClassToMap(struct _object *,char const *)" >> (?AddClassToMap at vtkPythonUtil@@SAXPEAU_object@@PEBD at Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GetAttr referenced in function "struct _object * __cdecl >> PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GetAttr >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp__PyObject_GC_New referenced in function "struct _object * __cdecl >> PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp__PyObject_GC_New >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp__PyObject_GC_New >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GC_Track referenced in function "struct _object * __cdecl >> PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_Track >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_Track >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GC_UnTrack referenced in function "void __cdecl >> PyVTKClass_Delete(struct _object *)" >> (?PyVTKClass_Delete@@YAXPEAU_object@@@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_UnTrack >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_UnTrack >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GC_Del referenced in function "void __cdecl >> PyVTKClass_Delete(struct _object *)" >> (?PyVTKClass_Delete@@YAXPEAU_object@@@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_Del >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_Del >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_InternFromString referenced in function PyVTKClass_New >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyTuple_GetItem referenced in function "struct _object * __cdecl >> PyVTKClass_GetAttr(struct _object *,struct _object *)" >> (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_GetItem >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_New referenced in function "struct _object * __cdecl >> PyVTKClass_GetAttr(struct _object *,struct _object *)" >> (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_New >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_New >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_GetItem referenced in function "struct _object * __cdecl >> PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_GetItem >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_Keys referenced in function "struct _object * __cdecl >> PyVTKClass_Dir(struct _object *,struct _object *)" >> (?PyVTKClass_Dir@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_Update referenced in function "struct _object * __cdecl >> PyVTKClass_Dir(struct _object *,struct _object *)" >> (?PyVTKClass_Dir@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_GetItemString referenced in function "struct _object * __cdecl >> PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_SetItemString referenced in function "struct _object * __cdecl >> PyVTKClass_GetAttr(struct _object *,struct _object *)" >> (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_SetItemString >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_DelItemString referenced in function "struct _object * __cdecl >> PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyCFunction_NewEx referenced in function "struct _object * __cdecl >> PyVTKClass_GetAttr(struct _object *,struct _object *)" >> (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyCFunction_NewEx >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyCFunction_NewEx >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyArg_ParseTuple referenced in function "struct _object * __cdecl >> PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyArg_ParseTuple >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyArg_ParseTuple >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyArg_ParseTupleAndKeywords referenced in function "struct _object * >> __cdecl PyVTKClass_NewSubclass(struct _object *,struct _object *,struct >> _object *)" (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyEval_GetGlobals referenced in function "struct _object * __cdecl >> PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyType_Type referenced in function "void __cdecl `dynamic initializer >> for 'PyVTKClassMetaType''(void)" (??__EPyVTKClassMetaType@@YAXXZ) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyType_Type >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyType_Type >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyType_Type >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyClass_Type referenced in function "void __cdecl `dynamic initializer >> for 'PyVTKClass_Type''(void)" (??__EPyVTKClass_Type@@YAXXZ) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_AttributeError referenced in function "struct _object * __cdecl >> PyVTKClass_GetAttr(struct _object *,struct _object *)" >> (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_AttributeError >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_AttributeError >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_AttributeError >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_Repr referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Repr(struct _object *)" >> (?PyVTKMutableObject_Repr@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_Repr >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_Str referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Str(struct _object *)" >> (?PyVTKMutableObject_Str@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_RichCompare referenced in function "struct _object * __cdecl >> PyVTKMutableObject_RichCompare(struct _object *,struct _object *,int)" >> (?PyVTKMutableObject_RichCompare@@YAPEAU_object@@PEAU1 at 0H@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GenericGetAttr referenced in function "struct _object * >> __cdecl PyVTKMutableObject_GetAttr(struct _object *,struct _object *)" >> (?PyVTKMutableObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_HashNotImplemented referenced in function "void __cdecl >> `dynamic initializer for 'PyVTKMutableObject_Type''(void)" >> (??__EPyVTKMutableObject_Type@@YAXXZ) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_CoerceEx referenced in function "int __cdecl >> PyVTKMutableObject_Coerce(struct _object * *,struct _object * *)" >> (?PyVTKMutableObject_Coerce@@YAHPEAPEAU_object@@0 at Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_Free referenced in function "void __cdecl `dynamic >> initializer for 'PyVTKMutableObject_Type''(void)" >> (??__EPyVTKMutableObject_Type@@YAXXZ) >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_Free >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp__PyObject_New referenced in function "struct _object * __cdecl >> PyVTKMutableObject_New(struct _typeobject *,struct _object *,struct _object >> *)" (?PyVTKMutableObject_New@@YAPEAU_object@@PEAU_typeobject@@PEAU1 at 1@Z) >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp__PyObject_New >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Add referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Add(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Add@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Subtract referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Subtract(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Subtract@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Multiply referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Multiply(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Multiply@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Divide referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Divide(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Divide@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_FloorDivide referenced in function "struct _object * __cdecl >> PyVTKMutableObject_FloorDivide(struct _object *,struct _object *)" >> (?PyVTKMutableObject_FloorDivide@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_TrueDivide referenced in function "struct _object * __cdecl >> PyVTKMutableObject_TrueDivide(struct _object *,struct _object *)" >> (?PyVTKMutableObject_TrueDivide@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Remainder referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Remainder(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Remainder@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Divmod referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Divmod(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Divmod@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Power referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Power(struct _object *,struct _object *,struct _object >> *)" (?PyVTKMutableObject_Power@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Negative referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Negative(struct _object *)" >> (?PyVTKMutableObject_Negative@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Positive referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Positive(struct _object *)" >> (?PyVTKMutableObject_Positive@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Absolute referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Absolute(struct _object *)" >> (?PyVTKMutableObject_Absolute@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Invert referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Invert(struct _object *)" >> (?PyVTKMutableObject_Invert@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Lshift referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Lshift(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Lshift@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Rshift referenced in function "struct _object * __cdecl >> PyVTKMutableObject_InPlaceRshift(struct _object *,struct _object *)" >> (?PyVTKMutableObject_InPlaceRshift@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_And referenced in function "struct _object * __cdecl >> PyVTKMutableObject_InPlaceAnd(struct _object *,struct _object *)" >> (?PyVTKMutableObject_InPlaceAnd@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Xor referenced in function "struct _object * __cdecl >> PyVTKMutableObject_InPlaceXor(struct _object *,struct _object *)" >> (?PyVTKMutableObject_InPlaceXor@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Or referenced in function "struct _object * __cdecl >> PyVTKMutableObject_InPlaceOr(struct _object *,struct _object *)" >> (?PyVTKMutableObject_InPlaceOr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Index referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Index(struct _object *)" >> (?PyVTKMutableObject_Index@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Int referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Int(struct _object *)" >> (?PyVTKMutableObject_Int@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Long referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Long(struct _object *)" >> (?PyVTKMutableObject_Long@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Float referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Float(struct _object *)" >> (?PyVTKMutableObject_Float@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_ToBase referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Hex(struct _object *)" >> (?PyVTKMutableObject_Hex@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_ClearWeakRefs referenced in function "void __cdecl >> PyVTKObject_Delete(struct _object *)" >> (?PyVTKObject_Delete@@YAXPEAU_object@@@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_SetItem referenced in function "int __cdecl >> PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" >> (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_SetItem >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_DelItem referenced in function "int __cdecl >> PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" >> (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyMethod_New referenced in function "struct _object * __cdecl >> PyVTKObject_GetAttr(struct _object *,struct _object *)" >> (?PyVTKObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyCFunction_Type referenced in function "struct _object * __cdecl >> PyVTKObject_GetAttr(struct _object *,struct _object *)" >> (?PyVTKObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_RuntimeError referenced in function "int __cdecl >> PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" >> (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_NotImplementedError referenced in function PyVTKObject_New >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyType_Ready referenced in function PyVTKSpecialType_New >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_ReprEnter referenced in function PyVTKSpecialObject_SequenceString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_ReprLeave referenced in function PyVTKSpecialObject_SequenceString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_Concat referenced in function >> PyVTKSpecialObject_SequenceString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_ConcatAndDel referenced in function PyVTKSpecialObject_Repr >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyBaseObject_Type referenced in function PyVTKSpecialObject_Repr >> >> >> PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_CallMethod referenced in function "struct _object * __cdecl >> PyVTKTemplate_HasKey(struct _object *,struct _object *)" >> (?PyVTKTemplate_HasKey@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_Size referenced in function "__int64 __cdecl >> PyVTKTemplate_Size(struct _object *)" >> (?PyVTKTemplate_Size@@YA_JPEAU_object@@@Z) >> >> >> PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GetItem referenced in function "struct _object * __cdecl >> PyVTKTemplate_GetItem(struct _object *,struct _object *)" >> (?PyVTKTemplate_GetItem@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> bin\vtkWrappingPython27Core-pv4.2.dll : fatal error LNK1120: 123 unresolved >> externals >> >> >> LINK failed. with 1120 >> >> ninja: build stopped: subcommand failed. >> >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > Classification: UNCLASSIFIED > Caveats: NONE > > From simon.m.su.ctr at mail.mil Tue Sep 23 16:11:44 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 23 Sep 2014 20:11:44 +0000 Subject: [Paraview] python link error when compiling PV-v4.2.0-RC1-128-gc89b0ad + python-2.7.3 + VS2013 Express (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Utkarsh, Awesome! I can certainly wait for a few days on linking error with ParaView build with -DPARAVIEW_ENABLE_PYTHON:BOOL=ON . I think I am running out of ideas to try on how to get around that :) At the mean time, I can work on getting VRPN setup with ParaView I compiled with just -DPARAVIEW_USE_MPI:BOOL=ON Thanks Utkarsh and Ben for your help. Thanks -simon -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Tuesday, September 23, 2014 4:01 PM To: Su, Simon M CTR USARMY ARL (US); Ben Boeckel Cc: paraview at paraview.org Subject: Re: [Paraview] python link error when compiling PV-v4.2.0-RC1-128-gc89b0ad + python-2.7.3 + VS2013 Express (UNCLASSIFIED) Ah, okay, sorry I missed the part that you were not using the Superbuild. The DUSE_SYSTEM_PYTHON is only for Superbuilds, so it won't matter for your regular ParaView build. My first pass at building ParaView with VS2013 (ParaView not ParaViewSuperbuild) exposed a few issues which I addressed. I can't remember if I built with Python support enabled, however. I'll check that once I am home (since it was on my home machine). Ben, we should have VS2013 dashboard setup on Miranda soon. That'll be the first step before we move to supporting superbuilds with VS2013 too. Simon, I suggest give us a few days to track this own, unless you're feeling adventurous :). Utkarsh On Tue, Sep 23, 2014 at 3:48 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Utkarsh, > > Thanks for the info. I did followed that thread and my conclusion at the end > was ParaView for windows compiled for vs2012 :) so, I went a step further to > try to get compiled with vs2013Express since that's the compiler I have > access > to on windows ;) I thought getting python compiled on any of the compiler of > choice is the prerequisite... apparently I still don't have python working > even after I manage to compile it. :( > > I am not doing the superbuild and just ParaView git from source build. I ran > into too many errors with VS2013Express + ninja-1.5.1 with the superbuild > route that I don't even know where/how to begin to ask for help. > > I will give -DUSE_SYSTEM_PYTHON=ON flag a try. If that doesn't work, I will > have my justification to ask for VS2008 purchased/installed on my system. > > Thanks for your help. > > Thanks > -simon > > > > > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Tuesday, September 23, 2014 3:17 PM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] python link error when compiling > PV-v4.2.0-RC1-128-gc89b0ad + python-2.7.3 + VS2013 Express (UNCLASSIFIED) > > Simon, > > As this states [1], superbuild on Windows with Python is only > supported for VS 2008 currently. We will soon add support for VS2013. > If you want to use VS2013, using USE_SYSTEM_python=ON may be worth a > try, but these was a discussion on the mailing list a little while ago > that too may have problems -- but it wasn't clear if it was build > problem, or an environment issue. Worth a shot, however. > > [1] http://www.paraview.org/Wiki/ParaView/Superbuild#Windows > > > On Tue, Sep 23, 2014 at 1:34 PM, Su, Simon M CTR USARMY ARL (US) > wrote: >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> Hello, >> >> I am trying to get a ParaView + vrpn running on a zSpace. With zSpace VRPN >> server only available on Windows, here goes the following... >> >> I am able to get ParaView build with ninja when I only do >> -DPARAVIEW_USE_MPI:BOOL=ON and the binary appears to be working. But when I >> included >> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON >> I have linking problem. How do you make sure that I have a working Python >> library? Dumpbin is reporting python is x64 library and I am trying to >> compile a x64 ParaView. >> >> I am getting some 26 unresolved externals when ninja is "Creating library >> lib\vtkPythonInterpreter-pv4.2.lib and object >> lib\vtkPythonInterpreter-pv4.2.exp." and some 123 unresolved externals when >> ninja is "Creating library lib\vtkWrappingPython27Core-pv4.2.lib and object >> lib\vtkWrappingPython27Core-pv4.2.exp"- included at the end of this email. >> >> The odd thing is, both failed command has python27.lib library in it >> >> FAILED: cmd.exe /C "cd . && >> C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E >> vs_link_dll >> C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo >> VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho >> nInterpreter.cxx.obj >> VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho >> nInteractiveInterpreter.cxx.obj /out:bin\vtkPythonInterpreter-pv4.2.dll >> /implib:lib\vtkPythonInterpreter-pv4.2.lib >> /pdb:bin\vtkPythonInterpreter-pv4.2.pdb /dll /version:1.0 /machine:x64 >> /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib >> C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib >> Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib >> ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." >> >> And >> >> FAILED: cmd.exe /C "cd . && >> C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E >> vs_link_dll >> C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonArgs.c >> xx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonComman >> d.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonOverlo >> ad.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonUtil.c >> xx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkSmartPyObjec >> t.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKClass.cxx. >> obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKMutableObj >> ect.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKObject.cxx >> .obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKSpecialObj >> ect.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKTemplate.c >> xx.obj /out:bin\vtkWrappingPython27Core-pv4.2.dll >> /implib:lib\vtkWrappingPython27Core-pv4.2.lib >> /pdb:bin\vtkWrappingPython27Core-pv4.2.pdb /dll /version:1.0 /machine:x64 >> /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib >> C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib >> Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib >> ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." >> >> Do I have to included another python library? If so, what would that be? >> >> >> I am building a 64bit version of ParaView on Windows 7 using >> 1. VS2013 express version >> 2. Python-2.7.3 - release version build with cmake + ninja >> (https://github.com/davidsansome/python-cmake-buildsystem) >> cmake \ >> -DCMAKE_INSTALL_PREFIX=C:\tools\python\python-2.7.3 \ >> -DBUILD_SHARED:BOOL=ON \ >> -DCMAKE_BUILD_TYPE=Release \ >> -DZLIB_LIBRARY=C:\tools\zlib\zlib-1.2.8\lib\zlib.lib \ >> -DZLIB_INCLUDE_DIR=C:\tools\zlib\zlib-1.2.8\include \ >> ..\python-cmake-buildsystem -G Ninja \ >> ninja >> ninja install >> >> 3. Ninja-1.5.1 - build using the python-2.7.3 above so, python appears to >> work >> python bootstrap.py --x64 >> >> 4. ParaView-v4.2.0-RC1-128-gc89b0ad >> >> git clone git://paraview.org/ParaView.git >> cd ParaView >> git pull >> git submodule update --init >> >> cmake \ >> -G Ninja \ >> -DCMAKE_INSTALL_PREFIX=C:\tools\ParaView\ParaView-v4.2.0-RC1-100-gfa06130 \ >> -DCMAKE_BUILD_TYPE=Release \ >> -DZLIB_LIBRARY=C:\tools\zlib\zlib-1.2.8\lib\zlib.lib \ >> -DZLIB_INCLUDE_DIR=C:\tools\zlib\zlib-1.2.8\include >> -DCMAKE_BUILD_TYPE=Release \ >> -DPARAVIEW_USE_MPI:BOOL=ON \ >> -DMPI_CXX_LIBRARIES:STRING="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi_cxx.li >> b" \ >> -DMPI_C_LIBRARIES:STRING="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi.lib" \ >> -DMPI_LIBRARY:FILEPATH="C:\tools\openmpi\openmpi-1.4.4\lib\libmpi_cxx.lib" >> \ >> -DMPI_CXX_INCLUDE_PATH=C:/tools/openmpi/openmpi-1.4.4/include \ >> -DMPI_C_INCLUDE_PATH=C:/tools/openmpi/openmpi-1.4.4/include \ >> -DGLUT_glut_LIBRARY=C:\tools\freeglut\freeglut-2.8.1\lib\freeglut.lib \ >> -DGLUT_INCLUDE_DIR=C:\tools\freeglut\freeglut-2.8.1\include \ >> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ >> -DPYTHON_LIBRARY=C:\tools\python\python-2.7.3\libs\python27.lib \ >> -DPYTHON_INCLUDE_DIR=C:\tools\python\python-2.7.3\include \ >> -DPYTHON_EXECUTABLE=C:\tools\python\python-2.7.3\bin\python.exe \ >> ..\ParaView-v4.2.0-RC1-128-gc89b0ad >> >> ninja >> >> >> >> Any help is much appreciated. >> >> Thanks >> -simon >> >> >> ======================== linking error ======================= >> [1/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractCellLocato >> r.cxx.obj >> [2/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractPointLocat >> or.cxx.obj >> [3/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAdjacentVertexIter >> ator.cxx.obj >> [4/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRBox.cxx.obj >> [5/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRUtilities.cxx.o >> bj >> [6/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnimationScene.cxx >> .obj >> [7/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnnotation.cxx.obj >> [8/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAnnotationLayers.c >> xx.obj >> [9/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkArrayData.cxx.obj >> [10/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAttributesErrorMet >> ric.cxx.obj >> [11/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuad.cx >> x.obj >> [12/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuadrat >> icHexahedron.cxx.obj >> [13/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticQuadrat >> icWedge.cxx.obj >> [14/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBiQuadraticTriangl >> e.cxx.obj >> [15/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBox.cxx.obj >> [16/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBSPCuts.cxx.obj >> [17/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBSPIntersections.c >> xx.obj >> [18/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCell3D.cxx.obj >> [19/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellArray.cxx.obj >> [20/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCell.cxx.obj >> [21/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellData.cxx.obj >> [22/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellIterator.cxx.o >> bj >> [23/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellLinks.cxx.obj >> [24/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellLocator.cxx.ob >> j >> [25/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCellTypes.cxx.obj >> [26/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCompositeDataSet.c >> xx.obj >> [27/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCompositeDataItera >> tor.cxx.obj >> [28/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCone.cxx.obj >> [29/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkConvexPointSet.cxx >> .obj >> [30/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCubicLine.cxx.obj >> [31/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkCylinder.cxx.obj >> [32/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetCellIterato >> r.cxx.obj >> [33/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectCollecti >> on.cxx.obj >> [34/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObject.cxx.obj >> [35/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTypes.cx >> x.obj >> [36/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTree.cxx >> .obj >> [37/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataObjectTreeIter >> ator.cxx.obj >> [38/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetAttributes. >> cxx.obj >> [39/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSetCollection. >> cxx.obj >> [40/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDataSet.cxx.obj >> [41/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDirectedAcyclicGra >> ph.cxx.obj >> [42/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDirectedGraph.cxx. >> obj >> [43/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkDistributedGraphHe >> lper.cxx.obj >> [44/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEdgeListIterator.c >> xx.obj >> [45/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEdgeTable.cxx.obj >> [46/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkEmptyCell.cxx.obj >> [47/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkExplicitCell.cxx.o >> bj >> [48/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkExtractStructuredG >> ridHelper.cxx.obj >> [49/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkFieldData.cxx.obj >> [50/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAdaptorCell >> .cxx.obj >> [51/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAttributeCo >> llection.cxx.obj >> [52/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericAttribute.c >> xx.obj >> [53/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCell.cxx.ob >> j >> [54/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCellIterato >> r.cxx.obj >> [55/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericCellTessell >> ator.cxx.obj >> [56/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericDataSet.cxx >> .obj >> [57/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericEdgeTable.c >> xx.obj >> [58/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericInterpolate >> dVelocityField.cxx.obj >> [59/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericPointIterat >> or.cxx.obj >> [60/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGenericSubdivision >> ErrorMetric.cxx.obj >> [61/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGeometricErrorMetr >> ic.cxx.obj >> [62/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraph.cxx.obj >> [63/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraphEdge.cxx.obj >> [64/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkGraphInternals.cxx >> .obj >> [65/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHexagonalPrism.cxx >> .obj >> [66/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHexahedron.cxx.obj >> [67/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHierarchicalBoxDat >> aIterator.cxx.obj >> [68/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHierarchicalBoxDat >> aSet.cxx.obj >> [69/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctreeCursor. >> cxx.obj >> [70/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctree.cxx.ob >> j >> [71/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperOctreePointsG >> rabber.cxx.obj >> [72/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTree.cxx.obj >> [73/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTreeCursor.cx >> x.obj >> [74/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkHyperTreeGrid.cxx. >> obj >> [75/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImageData.cxx.obj >> [76/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImageIterator.cxx. >> obj >> [77/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitBoolean.cx >> x.obj >> [78/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitDataSet.cx >> x.obj >> [79/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitFunctionCo >> llection.cxx.obj >> [80/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitFunction.c >> xx.obj >> [81/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitHalo.cxx.o >> bj >> [82/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitSelectionL >> oop.cxx.obj >> [83/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitSum.cxx.ob >> j >> [84/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitVolume.cxx >> .obj >> [85/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkImplicitWindowFunc >> tion.cxx.obj >> [86/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalOctreeN >> ode.cxx.obj >> [87/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalOctreeP >> ointLocator.cxx.obj >> [88/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIncrementalPointLo >> cator.cxx.obj >> [89/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkInEdgeIterator.cxx >> .obj >> [90/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkInformationQuadrat >> ureSchemeDefinitionVectorKey.cxx.obj >> [91/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkIterativeClosestPo >> intTransform.cxx.obj >> [92/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdNode.cxx.obj >> [93/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdTree.cxx.obj >> [94/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkKdTreePointLocator >> .cxx.obj >> [95/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkLine.cxx.obj >> [96/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkLocator.cxx.obj >> [97/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMarchingSquaresLin >> eCases.cxx.obj >> [98/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMarchingCubesTrian >> gleCases.cxx.obj >> [99/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMeanValueCoordinat >> esInterpolator.cxx.obj >> [100/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMergePoints.cxx.ob >> j >> [101/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMultiBlockDataSet. >> cxx.obj >> [102/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMultiPieceDataSet. >> cxx.obj >> [103/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMutableDirectedGra >> ph.cxx.obj >> [104/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMutableUndirectedG >> raph.cxx.obj >> [105/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonLinearCell.cxx. >> obj >> [106/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonMergingPointLoc >> ator.cxx.obj >> [107/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOctreePointLocator >> .cxx.obj >> [108/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOctreePointLocator >> Node.cxx.obj >> [109/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOrderedTriangulato >> r.cxx.obj >> [110/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOutEdgeIterator.cx >> x.obj >> [111/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPath.cxx.obj >> [112/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPentagonalPrism.cx >> x.obj >> [113/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPerlinNoise.cxx.ob >> j >> [114/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPiecewiseFunction. >> cxx.obj >> [115/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPixel.cxx.obj >> [116/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPixelExtent.cxx.ob >> j >> [117/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlaneCollection.cx >> x.obj >> [118/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlane.cxx.obj >> [119/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlanes.cxx.obj >> [120/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPlanesIntersection >> .cxx.obj >> [121/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointData.cxx.obj >> [122/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointLocator.cxx.o >> bj >> [123/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointSet.cxx.obj >> [124/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointSetCellIterat >> or.cxx.obj >> [125/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPointsProjectedHul >> l.cxx.obj >> [126/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyDataCollection >> .cxx.obj >> [127/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyData.cxx.obj >> [128/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolygon.cxx.obj >> [129/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyhedron.cxx.obj >> [130/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyLine.cxx.obj >> [131/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyPlane.cxx.obj >> [132/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPolyVertex.cxx.obj >> [133/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkPyramid.cxx.obj >> [134/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuad.cxx.obj >> [135/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticEdge.cxx. >> obj >> [136/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticHexahedro >> n.cxx.obj >> [137/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticLinearQua >> d.cxx.obj >> [138/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticLinearWed >> ge.cxx.obj >> [139/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticPolygon.c >> xx.obj >> [140/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticPyramid.c >> xx.obj >> [141/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticQuad.cxx. >> obj >> [142/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticTetra.cxx >> .obj >> [143/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticTriangle. >> cxx.obj >> [144/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadraticWedge.cxx >> .obj >> [145/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadratureSchemeDe >> finition.cxx.obj >> [146/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkQuadric.cxx.obj >> [147/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkRectilinearGrid.cx >> x.obj >> [148/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkReebGraph.cxx.obj >> [149/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkReebGraphSimplific >> ationMetric.cxx.obj >> [150/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSelection.cxx.obj >> [151/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSelectionNode.cxx. >> obj >> [152/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSimpleCellTessella >> tor.cxx.obj >> [153/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSmoothErrorMetric. >> cxx.obj >> [154/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSphere.cxx.obj >> [155/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSpline.cxx.obj >> [156/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredData.cxx >> .obj >> [157/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredExtent.c >> xx.obj >> [158/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredGrid.cxx >> .obj >> [159/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredPointsCo >> llection.cxx.obj >> [160/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredPoints.c >> xx.obj >> [161/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkStructuredVisibili >> tyConstraint.cxx.obj >> [162/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkSuperquadric.cxx.o >> bj >> [163/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTable.cxx.obj >> [164/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTensor.cxx.obj >> [165/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTetra.cxx.obj >> [166/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeBFSIterator.cx >> x.obj >> [167/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTree.cxx.obj >> [168/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeDFSIterator.cx >> x.obj >> [169/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriangle.cxx.obj >> [170/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriangleStrip.cxx. >> obj >> [171/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTriQuadraticHexahe >> dron.cxx.obj >> [172/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUndirectedGraph.cx >> x.obj >> [173/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGrid.cxx.ob >> j >> [174/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGrid.c >> xx.obj >> [175/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGridBa >> se.cxx.obj >> [176/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUnstructuredGridCe >> llIterator.cxx.obj >> [177/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVertex.cxx.obj >> [178/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVertexListIterator >> .cxx.obj >> [179/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkVoxel.cxx.obj >> [180/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkWedge.cxx.obj >> [181/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkXMLDataElement.cxx >> .obj >> [182/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkTreeIterator.cxx.o >> bj >> [183/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBoundingBox.cxx.ob >> j >> [184/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAtom.cxx.obj >> [185/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkBond.cxx.obj >> [186/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkMolecule.cxx.obj >> [187/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAbstractElectronic >> Data.cxx.obj >> [188/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkNonOverlappingAMR. >> cxx.obj >> [189/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkOverlappingAMR.cxx >> .obj >> [190/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRInformation.cxx >> .obj >> [191/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkAMRDataInternals.c >> xx.obj >> [192/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGridAMR.cxx >> .obj >> [193/16592] Building CXX object >> VTK\Common\DataModel\CMakeFiles\vtkCommonDataModel.dir\vtkUniformGridAMRData >> Iterator.cxx.obj >> [194/16592] Linking CXX shared library bin\vtkPythonInterpreter-pv4.2.dll >> [195/16592] Linking CXX shared library >> bin\vtkWrappingPython27Core-pv4.2.dll >> FAILED: cmd.exe /C "cd . && >> C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E >> vs_link_dll >> C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo >> VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho >> nInterpreter.cxx.obj >> VTK\Utilities\PythonInterpreter\CMakeFiles\vtkPythonInterpreter.dir\vtkPytho >> nInteractiveInterpreter.cxx.obj /out:bin\vtkPythonInterpreter-pv4.2.dll >> /implib:lib\vtkPythonInterpreter-pv4.2.lib >> /pdb:bin\vtkPythonInterpreter-pv4.2.pdb /dll /version:1.0 /machine:x64 >> /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib >> C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib >> Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib >> ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." >> Creating library lib\vtkPythonInterpreter-pv4.2.lib and object >> lib\vtkPythonInterpreter-pv4.2.exp >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyType_IsSubtype referenced in function "struct _object * __cdecl >> vtkWrite(struct _object *,struct _object *)" >> (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyType_Ready referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GenericGetAttr referenced in function "void __cdecl `dynamic >> initializer for 'vtkPythonStdStreamCaptureHelperType''(void)" >> (??__EvtkPythonStdStreamCaptureHelperType@@YAXXZ) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GenericSetAttr referenced in function "void __cdecl `dynamic >> initializer for 'vtkPythonStdStreamCaptureHelperType''(void)" >> (??__EvtkPythonStdStreamCaptureHelperType@@YAXXZ) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp__PyObject_New referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_FromString referenced in function "public: static bool >> __cdecl vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved >> external >> symbol __imp_PyString_FromString >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyList_Insert referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyArg_ParseTuple referenced in function "struct _object * __cdecl >> vtkWrite(struct _object *,struct _object *)" >> (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_BuildValue referenced in function "struct _object * __cdecl >> vtkWrite(struct _object *,struct _object *)" >> (?vtkWrite@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_SetProgramName referenced in function "public: static void __cdecl >> vtkPythonInterpreter::SetProgramName(char const *)" >> (?SetProgramName at vtkPythonInterpreter@@SAXPEBD at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_InitializeEx referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_Finalize referenced in function "public: static void __cdecl >> vtkPythonInterpreter::Finalize(void)" >> (?Finalize at vtkPythonInterpreter@@SAXXZ) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_IsInitialized referenced in function "public: static void __cdecl >> vtkPythonInterpreter::Finalize(void)" >> (?Finalize at vtkPythonInterpreter@@SAXXZ) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyRun_SimpleStringFlags referenced in function "public: static void >> __cdecl vtkPythonInterpreter::RunSimpleString(char const *)" >> (?RunSimpleString at vtkPythonInterpreter@@SAXPEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved >> external >> symbol __imp_PyRun_SimpleStringFlags >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_Main referenced in function "public: static int __cdecl >> vtkPythonInterpreter::PyMain(int,char * *)" >> (?PyMain at vtkPythonInterpreter@@SAHHPEAPEAD at Z) >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySys_GetObject referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved >> external >> symbol __imp_PySys_GetObject >> >> >> vtkPythonInterpreter.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySys_SetObject referenced in function "public: static bool __cdecl >> vtkPythonInterpreter::Initialize(int)" >> (?Initialize at vtkPythonInterpreter@@SA_NH at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2001: unresolved >> external >> symbol __imp_PySys_SetObject >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved >> external >> symbol __imp_PyDict_GetItemString referenced in function "public: struct >> _object * __cdecl >> vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" >> (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE >> AU_object@@XZ) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved >> external >> symbol __imp_PyModule_GetDict referenced in function "public: struct >> _object >> * __cdecl >> vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" >> (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE >> AU_object@@XZ) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved >> external >> symbol __imp_PyErr_Clear referenced in function "public: int __cdecl >> vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" >> (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved >> external >> symbol __imp_PyArg_Parse referenced in function "public: bool __cdecl >> vtkPythonInteractiveInterpreter::Push(char const * const)" >> (?Push at vtkPythonInteractiveInterpreter@@QEAA_NQEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved >> external >> symbol __imp_PyRun_StringFlags referenced in function "public: int __cdecl >> vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" >> (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved >> external >> symbol __imp_PyErr_Print referenced in function "public: int __cdecl >> vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" >> (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved >> external >> symbol __imp_Py_FlushLine referenced in function "public: int __cdecl >> vtkPythonInteractiveInterpreter::RunStringWithConsoleLocals(char const *)" >> (?RunStringWithConsoleLocals at vtkPythonInteractiveInterpreter@@QEAAHPEBD at Z) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved >> external >> symbol __imp_PyImport_AddModule referenced in function "public: struct >> _object * __cdecl >> vtkPythonInteractiveInterpreter::vtkInternals::GetInteractiveConsole(void)" >> (?GetInteractiveConsole at vtkInternals@vtkPythonInteractiveInterpreter@@QEAAPE >> AU_object@@XZ) >> >> >> vtkPythonInteractiveInterpreter.cxx.obj : error LNK2019: unresolved >> external >> symbol __imp_PyObject_CallMethod referenced in function "public: bool >> __cdecl vtkPythonInteractiveInterpreter::Push(char const * const)" >> (?Push at vtkPythonInteractiveInterpreter@@QEAA_NQEBD at Z) >> >> >> bin\vtkPythonInterpreter-pv4.2.dll : fatal error LNK1120: 26 unresolved >> externals >> >> >> LINK failed. with 1120 >> >> FAILED: cmd.exe /C "cd . && >> C:\Users\simon.m.su.ctr\tools\cmake\cmake-3.0.0\bin\cmake.exe -E >> vs_link_dll >> C:\PROGRA~2\MICROS~1.0\VC\bin\X86_AM~1\link.exe /nologo >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonArgs.c >> xx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonComman >> d.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonOverlo >> ad.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkPythonUtil.c >> xx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\vtkSmartPyObjec >> t.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKClass.cxx. >> obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKMutableObj >> ect.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKObject.cxx >> .obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKSpecialObj >> ect.cxx.obj >> VTK\Wrapping\PythonCore\CMakeFiles\vtkWrappingPythonCore.dir\PyVTKTemplate.c >> xx.obj /out:bin\vtkWrappingPython27Core-pv4.2.dll >> /implib:lib\vtkWrappingPython27Core-pv4.2.lib >> /pdb:bin\vtkWrappingPython27Core-pv4.2.pdb /dll /version:1.0 /machine:x64 >> /INCREMENTAL:NO lib\vtkCommonCore-pv4.2.lib >> C:\tmp\python-2.7.3\libs\python27.lib lib\vtksys-pv4.2.lib ws2_32.lib >> Psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib >> ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." >> Creating library lib\vtkWrappingPython27Core-pv4.2.lib and object >> lib\vtkWrappingPython27Core-pv4.2.exp >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyType_IsSubtype referenced in function "bool __cdecl >> vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" >> (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyType_IsSubtype >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyType_IsSubtype >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_IsTrue referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,bool *,int)" >> (??$vtkPythonGetArray at _N@@YA_NPEAU_object@@PEA_NH at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_IsTrue >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_IsTrue >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyCallable_Check referenced in function "public: bool __cdecl >> vtkPythonArgs::GetFunction(struct _object * &)" >> (?GetFunction at vtkPythonArgs@@QEAA_NAEAPEAU_object@@@Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyCallable_Check >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyCallable_Check >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp__PyUnicodeUCS2_AsDefaultEncodedString referenced in function "bool >> __cdecl vtkPythonGetStringValue(struct _object *,char const * >> &,char const *)" >> (??$vtkPythonGetStringValue@$$CBD@@YA_NPEAU_object@@AEAPEBDPEBD at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyUnicodeUCS2_DecodeUTF8 referenced in function "public: static >> struct >> _object * __cdecl vtkPythonArgs::BuildValue(class vtkUnicodeString const >> &)" >> (?BuildValue at vtkPythonArgs@@SAPEAU_object@@AEBVvtkUnicodeString@@@Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyUnicodeUCS2_DecodeUTF8 >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyUnicodeUCS2_AsUTF8String referenced in function "bool __cdecl >> vtkPythonGetValue(struct _object *,class vtkUnicodeString &)" >> (?vtkPythonGetValue@@YA_NPEAU_object@@AEAVvtkUnicodeString@@@Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyInt_FromLong referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple(signed char const *,int)" >> (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyInt_FromLong >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyInt_FromLong >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyInt_AsLong referenced in function "bool __cdecl >> vtkPythonGetUnsignedLongLongValue(struct _object >> *,unsigned __int64 &)" >> (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyInt_AsLong >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyInt_AsLong >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyBool_FromLong referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple(bool const *,int)" >> (??$vtkPythonBuildTuple at _N@@YAPEAU_object@@PEB_NH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_FromUnsignedLong referenced in function "struct _object * >> __cdecl vtkPythonBuildTuple(unsigned int const *,int)" >> (??$vtkPythonBuildTuple at I@@YAPEAU_object@@PEBIH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_AsUnsignedLong referenced in function "bool __cdecl >> vtkPythonGetValue(struct _object *,unsigned int &)" >> (?vtkPythonGetValue@@YA_NPEAU_object@@AEAI at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_FromLongLong referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple<__int64>(__int64 const *,int)" >> (??$vtkPythonBuildTuple at _J@@YAPEAU_object@@PEB_JH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_FromUnsignedLongLong referenced in function "struct _object * >> __cdecl vtkPythonBuildTuple(unsigned __int64 const >> *,int)" >> (??$vtkPythonBuildTuple at _K@@YAPEAU_object@@PEB_KH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_AsLongLong referenced in function "bool __cdecl >> vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" >> (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyLong_AsLongLong >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_AsUnsignedLongLong referenced in function "bool __cdecl >> vtkPythonGetUnsignedLongLongValue(struct _object >> *,unsigned __int64 &)" >> (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyFloat_FromDouble referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple(float const *,int)" >> (??$vtkPythonBuildTuple at M@@YAPEAU_object@@PEBMH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyFloat_FromDouble >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyFloat_AsDouble referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,float *,int)" >> (??$vtkPythonGetArray at M@@YA_NPEAU_object@@PEAMH at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyFloat_AsDouble >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_FromStringAndSize referenced in function "public: static >> struct _object * __cdecl vtkPythonArgs::BuildBytes(char const *,int)" >> (?BuildBytes at vtkPythonArgs@@SAPEAU_object@@PEBDH at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromStringAndSize >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromStringAndSize >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromStringAndSize >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_FromString referenced in function "bool __cdecl >> vtkPythonSetArray(struct _object *,char const *,int)" >> (??$vtkPythonSetArray at D@@YA_NPEAU_object@@PEBDH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_FromString >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_AsString referenced in function "public: __cdecl >> std::error_category::error_category(void)" (??0error_category at std@@QEAA at XZ) >> >> >> vtkPythonArgs.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_AsString >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_AsStringAndSize referenced in function "bool __cdecl >> vtkPythonGetStdStringValue(struct _object *,class >> std::basic_string,class >> std::allocator > &,char const *)" >> (?vtkPythonGetStdStringValue@@YA_NPEAU_object@@AEAV?$basic_string at DU?$char_t >> raits at D@std@@V?$allocator at D@2@@std@@PEBD at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyTuple_New referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple(signed char const *,int)" >> (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_New >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_New >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_New >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_SetString referenced in function "public: __cdecl >> std::_Generic_error_category::_Generic_error_category(void)" >> (??0_Generic_error_category at std@@QEAA at XZ) >> >> >> vtkPythonArgs.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_SetString >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_Occurred referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,float *,int)" >> (??$vtkPythonGetArray at M@@YA_NPEAU_object@@PEAMH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Occurred >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Occurred >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Occurred >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_Fetch referenced in function "protected: bool __cdecl >> vtkPythonArgs::RefineArgTypeError(int)" >> (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_Restore referenced in function "protected: bool __cdecl >> vtkPythonArgs::RefineArgTypeError(int)" >> (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_ExceptionMatches referenced in function "protected: bool >> __cdecl >> vtkPythonArgs::RefineArgTypeError(int)" >> (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_ExceptionMatches >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_ExceptionMatches >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_ExceptionMatches >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySequence_Check referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,signed char *,int)" >> (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PySequence_Check >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySequence_Size referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,signed char *,int)" >> (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PySequence_Size >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PySequence_Size >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySequence_GetItem referenced in function "bool __cdecl >> vtkPythonGetArray(struct _object *,signed char *,int)" >> (??$vtkPythonGetArray at C@@YA_NPEAU_object@@PEACH at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PySequence_GetItem >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PySequence_GetItem >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PySequence_SetItem referenced in function "bool __cdecl >> vtkPythonSetArray(struct _object *,signed char const *,int)" >> (??$vtkPythonSetArray at C@@YA_NPEAU_object@@PEBCH at Z) >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp__Py_NoneStruct referenced in function "struct _object * __cdecl >> vtkPythonBuildTuple(signed char const *,int)" >> (??$vtkPythonBuildTuple at C@@YAPEAU_object@@PEBCH at Z) >> >> >> vtkPythonCommand.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp__Py_NoneStruct >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyFloat_Type referenced in function "bool __cdecl >> vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" >> (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyFloat_Type >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyFloat_Type >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_OverflowError referenced in function "bool __cdecl >> vtkPythonGetUnsignedLongLongValue(struct _object >> *,unsigned __int64 &)" >> (??$vtkPythonGetUnsignedLongLongValue at _K@@YA_NPEAU_object@@AEA_K at Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_TypeError referenced in function "bool __cdecl >> vtkPythonGetLongLongValue<__int64>(struct _object *,__int64 &)" >> (??$vtkPythonGetLongLongValue at _J@@YA_NPEAU_object@@AEA_J at Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_TypeError >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_ValueError >> >> >> vtkPythonArgs.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_ValueError referenced in function "protected: bool __cdecl >> vtkPythonArgs::RefineArgTypeError(int)" >> (?RefineArgTypeError at vtkPythonArgs@@IEAA_NH at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_ValueError >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_ValueError >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_ValueError >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GetAttrString referenced in function "public: virtual void >> __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GetAttrString >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GetAttrString >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyLong_FromLong referenced in function "public: virtual void __cdecl >> vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Clear >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Clear >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_Clear referenced in function "struct _object * __cdecl >> `anonymous namespace'::BuildCallDataArgList(struct _object *,char const >> *,struct _object *)" >> (?BuildCallDataArgList@?A0xfc44b691@@YAPEAU_object@@PEAU2 at PEBD0@Z) >> >> >> vtkPythonOverload.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Clear >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Clear >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Clear >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyThreadState_Swap referenced in function "public: virtual void >> __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_BuildValue >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_BuildValue referenced in function "struct _object * __cdecl >> `anonymous namespace'::BuildCallDataArgList(struct _object *,char const >> *,struct _object *)" >> (?BuildCallDataArgList@?A0xfc44b691@@YAPEAU_object@@PEAU2 at PEBD0@Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_BuildValue >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_BuildValue >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_BuildValue >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_IsInitialized referenced in function "protected: virtual __cdecl >> vtkPythonCommand::~vtkPythonCommand(void)" (??1vtkPythonCommand@@MEAA at XZ) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_IsInitialized >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_Print referenced in function "public: virtual void __cdecl >> vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyErr_Print >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_Exit referenced in function "public: virtual void __cdecl >> vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_Py_Exit >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyEval_CallObjectWithKeywords referenced in function "public: virtual >> void __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void >> *)" (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyEval_CallObjectWithKeywords >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyEval_CallObjectWithKeywords >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyEval_CallObjectWithKeywords >> >> >> vtkPythonCommand.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_KeyboardInterrupt referenced in function "public: virtual void >> __cdecl vtkPythonCommand::Execute(class vtkObject *,unsigned long,void *)" >> (?Execute at vtkPythonCommand@@UEAAXPEAVvtkObject@@KPEAX at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_KeyboardInterrupt >> >> >> vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_Size referenced in function "public: static int __cdecl >> vtkPythonOverload::CheckArg(struct _object *,char const *,char const >> *,int)" >> (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyString_Size >> >> >> vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyTuple_Size referenced in function "public: static int __cdecl >> vtkPythonOverload::CheckArg(struct _object *,char const *,char const >> *,int)" >> (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) >> >> >> PyVTKClass.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_Size >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_Size >> >> >> vtkPythonOverload.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyBool_Type referenced in function "public: static int __cdecl >> vtkPythonOverload::CheckArg(struct _object *,char const *,char const >> *,int)" >> (?CheckArg at vtkPythonOverload@@SAHPEAU_object@@PEBD1H at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_Hash referenced in function "public: static long __cdecl >> vtkPythonUtil::VariantHash(class vtkVariant const *)" >> (?VariantHash at vtkPythonUtil@@SAJPEBVvtkVariant@@@Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp__Py_HashPointer referenced in function "public: static long __cdecl >> vtkPythonUtil::VariantHash(class vtkVariant const *)" >> (?VariantHash at vtkPythonUtil@@SAJPEBVvtkVariant@@@Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp__PyString_Resize referenced in function "public: static struct >> _object >> * __cdecl vtkPythonUtil::BuildDocString(char const * * const)" >> (?BuildDocString at vtkPythonUtil@@SAPEAU_object@@QEAPEBD at Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_Size referenced in function "public: static void __cdecl >> vtkPythonUtil::RemoveObjectFromMap(struct _object *)" >> (?RemoveObjectFromMap at vtkPythonUtil@@SAXPEAU_object@@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_Size >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyErr_GivenExceptionMatches referenced in function "public: static >> void * __cdecl vtkPythonUtil::GetPointerFromSpecialObject(struct _object >> *,char const *,struct _object * *)" >> (?GetPointerFromSpecialObject at vtkPythonUtil@@SAPEAXPEAU_object@@PEBDPEAPEAU2 >> @@Z) >> >> >> vtkPythonUtil.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_AtExit referenced in function "public: static void __cdecl >> vtkPythonUtil::AddClassToMap(struct _object *,char const *)" >> (?AddClassToMap at vtkPythonUtil@@SAXPEAU_object@@PEBD at Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GetAttr referenced in function "struct _object * __cdecl >> PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GetAttr >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp__PyObject_GC_New referenced in function "struct _object * __cdecl >> PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp__PyObject_GC_New >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp__PyObject_GC_New >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GC_Track referenced in function "struct _object * __cdecl >> PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_Track >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_Track >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GC_UnTrack referenced in function "void __cdecl >> PyVTKClass_Delete(struct _object *)" >> (?PyVTKClass_Delete@@YAXPEAU_object@@@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_UnTrack >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_UnTrack >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GC_Del referenced in function "void __cdecl >> PyVTKClass_Delete(struct _object *)" >> (?PyVTKClass_Delete@@YAXPEAU_object@@@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_Del >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_GC_Del >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_InternFromString referenced in function PyVTKClass_New >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyTuple_GetItem referenced in function "struct _object * __cdecl >> PyVTKClass_GetAttr(struct _object *,struct _object *)" >> (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyTuple_GetItem >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_New referenced in function "struct _object * __cdecl >> PyVTKClass_GetAttr(struct _object *,struct _object *)" >> (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_New >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_New >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_GetItem referenced in function "struct _object * __cdecl >> PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_GetItem >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_Keys referenced in function "struct _object * __cdecl >> PyVTKClass_Dir(struct _object *,struct _object *)" >> (?PyVTKClass_Dir@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_Update referenced in function "struct _object * __cdecl >> PyVTKClass_Dir(struct _object *,struct _object *)" >> (?PyVTKClass_Dir@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_GetItemString referenced in function "struct _object * __cdecl >> PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_SetItemString referenced in function "struct _object * __cdecl >> PyVTKClass_GetAttr(struct _object *,struct _object *)" >> (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_SetItemString >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_DelItemString referenced in function "struct _object * __cdecl >> PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyCFunction_NewEx referenced in function "struct _object * __cdecl >> PyVTKClass_GetAttr(struct _object *,struct _object *)" >> (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyCFunction_NewEx >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyCFunction_NewEx >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyArg_ParseTuple referenced in function "struct _object * __cdecl >> PyVTKClass_Call(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_Call@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyArg_ParseTuple >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyArg_ParseTuple >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyArg_ParseTupleAndKeywords referenced in function "struct _object * >> __cdecl PyVTKClass_NewSubclass(struct _object *,struct _object *,struct >> _object *)" (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyEval_GetGlobals referenced in function "struct _object * __cdecl >> PyVTKClass_NewSubclass(struct _object *,struct _object *,struct _object *)" >> (?PyVTKClass_NewSubclass@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyType_Type referenced in function "void __cdecl `dynamic initializer >> for 'PyVTKClassMetaType''(void)" (??__EPyVTKClassMetaType@@YAXXZ) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyType_Type >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyType_Type >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyType_Type >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyClass_Type referenced in function "void __cdecl `dynamic >> initializer >> for 'PyVTKClass_Type''(void)" (??__EPyVTKClass_Type@@YAXXZ) >> >> >> PyVTKClass.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_AttributeError referenced in function "struct _object * __cdecl >> PyVTKClass_GetAttr(struct _object *,struct _object *)" >> (?PyVTKClass_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_AttributeError >> >> >> PyVTKObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_AttributeError >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyExc_AttributeError >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_Repr referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Repr(struct _object *)" >> (?PyVTKMutableObject_Repr@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_Repr >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_Str referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Str(struct _object *)" >> (?PyVTKMutableObject_Str@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_RichCompare referenced in function "struct _object * __cdecl >> PyVTKMutableObject_RichCompare(struct _object *,struct _object *,int)" >> (?PyVTKMutableObject_RichCompare@@YAPEAU_object@@PEAU1 at 0H@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GenericGetAttr referenced in function "struct _object * >> __cdecl PyVTKMutableObject_GetAttr(struct _object *,struct _object *)" >> (?PyVTKMutableObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_HashNotImplemented referenced in function "void __cdecl >> `dynamic initializer for 'PyVTKMutableObject_Type''(void)" >> (??__EPyVTKMutableObject_Type@@YAXXZ) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_CoerceEx referenced in function "int __cdecl >> PyVTKMutableObject_Coerce(struct _object * *,struct _object * *)" >> (?PyVTKMutableObject_Coerce@@YAHPEAPEAU_object@@0 at Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_Free referenced in function "void __cdecl `dynamic >> initializer for 'PyVTKMutableObject_Type''(void)" >> (??__EPyVTKMutableObject_Type@@YAXXZ) >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyObject_Free >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp__PyObject_New referenced in function "struct _object * __cdecl >> PyVTKMutableObject_New(struct _typeobject *,struct _object *,struct _object >> *)" (?PyVTKMutableObject_New@@YAPEAU_object@@PEAU_typeobject@@PEAU1 at 1@Z) >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2001: unresolved external symbol >> __imp__PyObject_New >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Add referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Add(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Add@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Subtract referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Subtract(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Subtract@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Multiply referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Multiply(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Multiply@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Divide referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Divide(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Divide@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_FloorDivide referenced in function "struct _object * __cdecl >> PyVTKMutableObject_FloorDivide(struct _object *,struct _object *)" >> (?PyVTKMutableObject_FloorDivide@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_TrueDivide referenced in function "struct _object * __cdecl >> PyVTKMutableObject_TrueDivide(struct _object *,struct _object *)" >> (?PyVTKMutableObject_TrueDivide@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Remainder referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Remainder(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Remainder@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Divmod referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Divmod(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Divmod@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Power referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Power(struct _object *,struct _object *,struct _object >> *)" (?PyVTKMutableObject_Power@@YAPEAU_object@@PEAU1 at 00@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Negative referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Negative(struct _object *)" >> (?PyVTKMutableObject_Negative@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Positive referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Positive(struct _object *)" >> (?PyVTKMutableObject_Positive@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Absolute referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Absolute(struct _object *)" >> (?PyVTKMutableObject_Absolute@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Invert referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Invert(struct _object *)" >> (?PyVTKMutableObject_Invert@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Lshift referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Lshift(struct _object *,struct _object *)" >> (?PyVTKMutableObject_Lshift@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Rshift referenced in function "struct _object * __cdecl >> PyVTKMutableObject_InPlaceRshift(struct _object *,struct _object *)" >> (?PyVTKMutableObject_InPlaceRshift@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_And referenced in function "struct _object * __cdecl >> PyVTKMutableObject_InPlaceAnd(struct _object *,struct _object *)" >> (?PyVTKMutableObject_InPlaceAnd@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Xor referenced in function "struct _object * __cdecl >> PyVTKMutableObject_InPlaceXor(struct _object *,struct _object *)" >> (?PyVTKMutableObject_InPlaceXor@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Or referenced in function "struct _object * __cdecl >> PyVTKMutableObject_InPlaceOr(struct _object *,struct _object *)" >> (?PyVTKMutableObject_InPlaceOr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Index referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Index(struct _object *)" >> (?PyVTKMutableObject_Index@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Int referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Int(struct _object *)" >> (?PyVTKMutableObject_Int@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Long referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Long(struct _object *)" >> (?PyVTKMutableObject_Long@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_Float referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Float(struct _object *)" >> (?PyVTKMutableObject_Float@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKMutableObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyNumber_ToBase referenced in function "struct _object * __cdecl >> PyVTKMutableObject_Hex(struct _object *)" >> (?PyVTKMutableObject_Hex@@YAPEAU_object@@PEAU1@@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_ClearWeakRefs referenced in function "void __cdecl >> PyVTKObject_Delete(struct _object *)" >> (?PyVTKObject_Delete@@YAXPEAU_object@@@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_SetItem referenced in function "int __cdecl >> PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" >> (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) >> >> >> PyVTKTemplate.cxx.obj : error LNK2001: unresolved external symbol >> __imp_PyDict_SetItem >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyDict_DelItem referenced in function "int __cdecl >> PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" >> (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyMethod_New referenced in function "struct _object * __cdecl >> PyVTKObject_GetAttr(struct _object *,struct _object *)" >> (?PyVTKObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyCFunction_Type referenced in function "struct _object * __cdecl >> PyVTKObject_GetAttr(struct _object *,struct _object *)" >> (?PyVTKObject_GetAttr@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_RuntimeError referenced in function "int __cdecl >> PyVTKObject_SetAttr(struct _object *,struct _object *,struct _object *)" >> (?PyVTKObject_SetAttr@@YAHPEAU_object@@00 at Z) >> >> >> PyVTKObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyExc_NotImplementedError referenced in function PyVTKObject_New >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyType_Ready referenced in function PyVTKSpecialType_New >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_ReprEnter referenced in function PyVTKSpecialObject_SequenceString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_Py_ReprLeave referenced in function PyVTKSpecialObject_SequenceString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_Concat referenced in function >> PyVTKSpecialObject_SequenceString >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyString_ConcatAndDel referenced in function PyVTKSpecialObject_Repr >> >> >> PyVTKSpecialObject.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyBaseObject_Type referenced in function PyVTKSpecialObject_Repr >> >> >> PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_CallMethod referenced in function "struct _object * __cdecl >> PyVTKTemplate_HasKey(struct _object *,struct _object *)" >> (?PyVTKTemplate_HasKey@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_Size referenced in function "__int64 __cdecl >> PyVTKTemplate_Size(struct _object *)" >> (?PyVTKTemplate_Size@@YA_JPEAU_object@@@Z) >> >> >> PyVTKTemplate.cxx.obj : error LNK2019: unresolved external symbol >> __imp_PyObject_GetItem referenced in function "struct _object * __cdecl >> PyVTKTemplate_GetItem(struct _object *,struct _object *)" >> (?PyVTKTemplate_GetItem@@YAPEAU_object@@PEAU1 at 0@Z) >> >> >> bin\vtkWrappingPython27Core-pv4.2.dll : fatal error LNK1120: 123 unresolved >> externals >> >> >> LINK failed. with 1120 >> >> ninja: build stopped: subcommand failed. >> >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > Classification: UNCLASSIFIED > Caveats: NONE > > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From lifeandfree at gmail.com Wed Sep 24 01:30:11 2014 From: lifeandfree at gmail.com (=?UTF-8?B?0JjQu9GM0Y8g0KHRg9GF0LDRh9C10LI=?=) Date: Wed, 24 Sep 2014 11:30:11 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Good day! Prompt please. I used the instructions for deployment on Linux Ubuntu Paraviewweb ( http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) Unfolded, but for some reason I can not open in the web browser Visualizer (http: // localhost / apps / Visualizer /) When deployment by using the ( http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only as 1 Ceci. How do I get access to many jobs, and through the web? Thank you Sincerely, Sukhachev Ilya! -------------- next part -------------- An HTML attachment was scrubbed... URL: From danyang.su at gmail.com Wed Sep 24 02:26:00 2014 From: danyang.su at gmail.com (Danyang Su) Date: Tue, 23 Sep 2014 23:26:00 -0700 Subject: [Paraview] How to create streamlines from tecplot velocity data Message-ID: <542263F8.5000001@gmail.com> Dear All, I have tecplot velocity dataset that I want to view with Paraview. I can successfully import the data to paraview, but neither 'cell data to point data' nor 'stream tracer' button is available (grey). The data set is in ascii format as shown below. The source data is also attached. Would anybody please give me some tips? I am a new to paraview and only have basic knowledge of it. Thanks, Danyang title = "dataset concrete-decalc" variables = "x", "y", "z", "vx", "vy", "vz" zone t = "velocities, solution time = 1.000E+02 years " i = 83, j = 159, k = 1, f=point 0.2626316E-04 0.0000000E+00 0.1052632E-02 0.3647120E-11 0.0000000E+00 -0.6160582E-05 0.7878948E-04 0.0000000E+00 0.1052632E-02 0.1094119E-10 0.0000000E+00 -0.6160582E-05 0.1313158E-03 0.0000000E+00 0.1052632E-02 0.1823477E-10 0.0000000E+00 -0.6160581E-05 0.1838421E-03 0.0000000E+00 0.1052632E-02 0.2552754E-10 0.0000000E+00 -0.6160580E-05 0.2363684E-03 0.0000000E+00 0.1052632E-02 0.3281916E-10 0.0000000E+00 -0.6160578E-05 0.2888947E-03 0.0000000E+00 0.1052632E-02 0.4010932E-10 0.0000000E+00 -0.6160576E-05 0.3414211E-03 0.0000000E+00 0.1052632E-02 0.4739768E-10 0.0000000E+00 -0.6160574E-05 0.3939474E-03 0.0000000E+00 0.1052632E-02 0.5468392E-10 0.0000000E+00 -0.6160572E-05 0.4464737E-03 0.0000000E+00 0.1052632E-02 0.6196771E-10 0.0000000E+00 -0.6160569E-05 -------------- next part -------------- A non-text attachment was scrubbed... Name: concrete-decalc_3.vel.7z Type: application/x-7z-compressed Size: 86267 bytes Desc: not available URL: From yemengli1990 at gmail.com Wed Sep 24 08:48:08 2014 From: yemengli1990 at gmail.com (=?UTF-8?B?5p2O5Y+26JCM?=) Date: Wed, 24 Sep 2014 20:48:08 +0800 Subject: [Paraview] Help: cannot run paraview Message-ID: <5422BD88.9010900@gmail.com> Dear all, I got some problem when running paraview in terminal (under Linux mint). The terminal shows something wrong as follow,and I cannot see the paraview window. Do you have any ideals of what's going on? Reinstallation using Synaptic Package Manager does not do any help. Thank you Yemeng *** glibc detected *** /usr/lib/paraview/paraview: munmap_chunk(): invalid pointer: 0x0000000001f99500 *** ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f894110fb96] /usr/lib/paraview/libvtkRendering.so.pv3.14(_ZN21vtkOpenGLRenderWindow12GetPixelDataEiiiiiPh+0xd4)[0x7f893dc60ab4] /usr/lib/paraview/libvtkRendering.so.pv3.14(_ZN21vtkOpenGLRenderWindow12GetPixelDataEiiiiiP20vtkUnsignedCharArray+0xe0)[0x7f893dc60c90] /usr/lib/paraview/libQVTK.so.pv3.14(_ZN10QVTKWidget16saveImageToCacheEv+0xe3)[0x7f893e381c53] /usr/lib/paraview/libvtkCommon.so.pv3.14(_ZN18vtkCallbackCommand7ExecuteEP9vtkObjectmPv+0x19)[0x7f893f283949] /usr/lib/paraview/libvtkCommon.so.pv3.14(+0x16efc7)[0x7f893f31dfc7] /usr/lib/paraview/libvtkRendering.so.pv3.14(_ZN15vtkRenderWindow15CopyResultFrameEv+0x5c)[0x7f893dba0aec] /usr/lib/paraview/libvtkRendering.so.pv3.14(_ZN15vtkRenderWindow6RenderEv+0x1c7)[0x7f893dba1cf7] /usr/lib/paraview/libvtkRendering.so.pv3.14(_ZN22vtkXOpenGLRenderWindow6RenderEv and I cannot see the paraview window. From sebastien.jourdain at kitware.com Wed Sep 24 10:30:20 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 24 Sep 2014 08:30:20 -0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Hi Sukhachev, The one thing that might not be explicit about the ubuntu_14_04 guide might be that the script "/data/pvw/bin/start.sh" should be launched with a DISPLAY setup. Otherwise, you will have to be more explicit on what you've done and what is not working. The log files usually helps to see what was skipped from the documentation. Seb On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? wrote: > Good day! > Prompt please. > I used the instructions for deployment on Linux Ubuntu Paraviewweb ( > http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) > Unfolded, but for some reason I can not open in the web browser Visualizer > (http: // localhost / apps / Visualizer /) > When deployment by using the ( > http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only as 1 > Ceci. > How do I get access to many jobs, and through the web? > Thank you > > Sincerely, > Sukhachev Ilya! > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Sep 24 10:33:25 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 24 Sep 2014 08:33:25 -0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Moreover, the documentation that get's updated automatically can be found at the following address. (Which might be more accurate.) http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html This is the one you find when you go on paraview.org and go to the documentation section. Seb On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Hi Sukhachev, > > The one thing that might not be explicit about the ubuntu_14_04 guide > might be that the script "/data/pvw/bin/start.sh" should be launched with > a DISPLAY setup. > Otherwise, you will have to be more explicit on what you've done and what > is not working. The log files usually helps to see what was skipped from > the documentation. > > Seb > > On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? > wrote: > >> Good day! >> Prompt please. >> I used the instructions for deployment on Linux Ubuntu Paraviewweb ( >> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >> Unfolded, but for some reason I can not open in the web browser Visualizer >> (http: // localhost / apps / Visualizer /) >> When deployment by using the ( >> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only as 1 >> Ceci. >> How do I get access to many jobs, and through the web? >> Thank you >> >> Sincerely, >> Sukhachev Ilya! >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Wed Sep 24 13:56:09 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Wed, 24 Sep 2014 19:56:09 +0200 Subject: [Paraview] useful plugin: how to do it, really? In-Reply-To: References: <54208CA1.7050907@xs4all.nl> Message-ID: <542305B9.90308@xs4all.nl> Utkarth, I followed-up on your advice, and it works. Thanks very much! I have still one question: When iterating over the proxy objects, I need to find out what kind of object the proxy is referring to (Sphere, box, etc.) In my trial code, I do that via the "XMLName" followed by a string comparison, like this: // prx is proxy, obtained as you describe via iter->GetProxy() std::string srctype = prx->GetXMLName(); if ( srctype == "SphereSource" ) { // Code for sphere } else if ( srctype == "CylinderSource" ) { // Code for Cyliner } else // etc { ...; } Is this indeed the way to do it, or are there (more efficient) alternatives? Kind Regards, Bertwim On 09/23/2014 03:01 PM, Utkarsh Ayachit wrote: > Bertwim, > > I agree the developer docs are little scattered right now. My plan is > to start writing blog posts that make this easier to digest. One of > these, hopefully, I get around to it :). In the mean time, my replies > are inline. > > >> 1. Suppose I have created, interactively, a box, a sphere and a cone, >> using the corresponding entries in the "Sources" menu. >> >> 2. Now I would like to *programmatically* (i.e. in a c++ plugin) loop >> over the sources (here: the box, sphere and cone) and for each of the >> elements >> get hold of the parameters that were used to define these sources (i.e. >> the box dimensions, center, radii etc.). With these parameters I can >> then do other things to build my own extension, but those details do not >> matter here. > > Several ways for getting to the "proxies" for the sphere, box, etc. > created. One way it using the vtkSMSessionProxyManager. > > a. Using vtkSMSessionProxyManager: > a.1 Get access to the active session's proxy manager using > pqActiveObjects::instance().proxyManager() [1] > a.2 Use vtkSMProxyIterator[2] to iterate over the "sources" group. > vtkNew iter; > iter->SetSessionProxyManager(pqActiveObjects::instance().proxyManager()); > iter->SetModeToOneGroup(); > for (iter->Begin("sources"); ! iter->IsAtEndt(); iter->Next()) > { > iter->GetKey() ---> is the "label" for the proxy you see in the > pipeline browser > iter->GetProxy() -- > will be the actual proxy object, > } > > To access parameters defined on them, you can access the "properties" > on these proxies. If you know which property you're looking for using > vtkSMPropertyHelper[3] to get the values e.g. > > sphereProxy = .. > vtkSMPropertyHelper(sphereProxy, "Radius").GetAsDouble() --> the radius > > To iterate over all properties on the proxy, you can use > vtkSMProxy::NewPropertyIterator [4] which will give you a new iterator > (don't forget to call iter->Delete() once you're done with the > iterator). You can use that to iterate over all properties on the > proxy, > > Hope that helps, > Utkarsh > > [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqActiveObjects.html#a547a93dececb0d5ac7a35f373e5c68ab > [2] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMProxyIterator.html > [3] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMPropertyHelper.html > [4] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMProxy.html#ab0eee37fc2a021334964e9ffcd682a4c > > From utkarsh.ayachit at kitware.com Wed Sep 24 14:59:43 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Sep 2014 14:59:43 -0400 Subject: [Paraview] useful plugin: how to do it, really? In-Reply-To: <542305B9.90308@xs4all.nl> References: <54208CA1.7050907@xs4all.nl> <542305B9.90308@xs4all.nl> Message-ID: That's pretty much what you have to do, I'm afraid. On Wed, Sep 24, 2014 at 1:56 PM, B.W.H. van Beest wrote: > Utkarth, > > I followed-up on your advice, and it works. Thanks very much! > > I have still one question: When iterating over the proxy objects, I > need to find out what kind of object the proxy is referring to (Sphere, > box, etc.) > In my trial code, I do that via the "XMLName" followed by a string > comparison, like this: > > // prx is proxy, obtained as you describe via iter->GetProxy() > > std::string srctype = prx->GetXMLName(); > > if ( srctype == "SphereSource" ) > { > // Code for sphere > } > else if ( srctype == "CylinderSource" ) > { > // Code for Cyliner > } > else // etc > { > ...; > } > > Is this indeed the way to do it, or are there (more efficient) > alternatives? > > Kind Regards, > Bertwim > > > On 09/23/2014 03:01 PM, Utkarsh Ayachit wrote: >> Bertwim, >> >> I agree the developer docs are little scattered right now. My plan is >> to start writing blog posts that make this easier to digest. One of >> these, hopefully, I get around to it :). In the mean time, my replies >> are inline. >> >> >>> 1. Suppose I have created, interactively, a box, a sphere and a cone, >>> using the corresponding entries in the "Sources" menu. >>> >>> 2. Now I would like to *programmatically* (i.e. in a c++ plugin) loop >>> over the sources (here: the box, sphere and cone) and for each of the >>> elements >>> get hold of the parameters that were used to define these sources (i.e. >>> the box dimensions, center, radii etc.). With these parameters I can >>> then do other things to build my own extension, but those details do not >>> matter here. >> >> Several ways for getting to the "proxies" for the sphere, box, etc. >> created. One way it using the vtkSMSessionProxyManager. >> >> a. Using vtkSMSessionProxyManager: >> a.1 Get access to the active session's proxy manager using >> pqActiveObjects::instance().proxyManager() [1] >> a.2 Use vtkSMProxyIterator[2] to iterate over the "sources" group. >> vtkNew iter; >> iter->SetSessionProxyManager(pqActiveObjects::instance().proxyManager()); >> iter->SetModeToOneGroup(); >> for (iter->Begin("sources"); ! iter->IsAtEndt(); iter->Next()) >> { >> iter->GetKey() ---> is the "label" for the proxy you see in the >> pipeline browser >> iter->GetProxy() -- > will be the actual proxy object, >> } >> >> To access parameters defined on them, you can access the "properties" >> on these proxies. If you know which property you're looking for using >> vtkSMPropertyHelper[3] to get the values e.g. >> >> sphereProxy = .. >> vtkSMPropertyHelper(sphereProxy, "Radius").GetAsDouble() --> the radius >> >> To iterate over all properties on the proxy, you can use >> vtkSMProxy::NewPropertyIterator [4] which will give you a new iterator >> (don't forget to call iter->Delete() once you're done with the >> iterator). You can use that to iterate over all properties on the >> proxy, >> >> Hope that helps, >> Utkarsh >> >> [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqActiveObjects.html#a547a93dececb0d5ac7a35f373e5c68ab >> [2] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMProxyIterator.html >> [3] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMPropertyHelper.html >> [4] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSMProxy.html#ab0eee37fc2a021334964e9ffcd682a4c >> >> > From bwvb at xs4all.nl Wed Sep 24 16:07:21 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Wed, 24 Sep 2014 22:07:21 +0200 Subject: [Paraview] How to compile a new file??? Message-ID: <54232479.7060603@xs4all.nl> Hello, I'm trying to understand how ParaView's build system determines which files are to be compiled. The problem I encounter is that newly added files are not being picked-up by the makefiles. My guess is this must be something simple, but so far my attempts yield no result. This is what I do: Let's assume I'm working on a plugin, the code of which residing in /ParaView/Examples/Plugins/ The build directory is in /ParaView/build. The plugin directory was obtained by copying and renaming the example plugin named "SourceToolbar". After that I did, in the build directory, a ccmake ..; So far, so good. Changes made in a source file (not in the build directory) are seen by make (when done in the build directory). However, when I add a new source file (.cxx), I can't get make/cmake to add this sourcefile to the build. How is this supposed to work? Any help greatly appreciated. Kind Regards, Bertwim From dave.demarle at kitware.com Wed Sep 24 16:13:29 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 24 Sep 2014 16:13:29 -0400 Subject: [Paraview] How to compile a new file??? In-Reply-To: <54232479.7060603@xs4all.nl> References: <54232479.7060603@xs4all.nl> Message-ID: Add the new file's name to the CMakeLists.txt file in its source directory. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Sep 24, 2014 at 4:07 PM, B.W.H. van Beest wrote: > Hello, > > I'm trying to understand how ParaView's build system determines which > files are to be compiled. The problem I encounter is that newly added > files are not being picked-up by the makefiles. My guess is this must be > something simple, but so far my attempts yield no result. > > This is what I do: > Let's assume I'm working on a plugin, the code of which residing in > /ParaView/Examples/Plugins/ > The build directory is in /ParaView/build. > > The plugin directory was obtained by copying and > renaming the example plugin named "SourceToolbar". > After that I did, in the build directory, a ccmake ..; So far, so good. > Changes made in a source file (not in the build directory) are seen by > make (when done in the build directory). > > However, when I add a new source file (.cxx), I can't get > make/cmake to add this sourcefile to the build. > How is this supposed to work? > > Any help greatly appreciated. > > > Kind Regards, > Bertwim > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Wed Sep 24 16:47:06 2014 From: bwvb at xs4all.nl (bwvb) Date: Thu, 25 Sep 2014 02:17:06 +0530 Subject: [Paraview] Fwd: Re: How to compile a new file??? Message-ID: Sent from Samsung Mobile
-------- Original message --------
From: bwvb
Date:2014/09/25 02:14 (GMT+05:30)
To: David E DeMarle
Subject: Re: [Paraview] How to compile a new file???
Ah, now I see. The macro ADD_PARAVIEW_PLUGIN has as one of its argument a SOURCES keyword. Adding to list indeed helps. Thanks for the hint. Regards Bertwim Sent from Samsung Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrhyde at stanford.edu Wed Sep 24 16:56:01 2014 From: mrhyde at stanford.edu (D H) Date: Wed, 24 Sep 2014 13:56:01 -0700 (PDT) Subject: [Paraview] Exporting to PDF from Python In-Reply-To: <1115533102.7600754.1411591876388.JavaMail.zimbra@stanford.edu> Message-ID: <463744129.7614860.1411592161048.JavaMail.zimbra@stanford.edu> Hi, I have a scene in Paraview 4.1 that I'd like to export to a PDF from a Python script. Ideally I'd like to be able to use the GL2PSExporter and set options there (such as "Cull Hidden Primitives") like I do in the PV GUI (under File->Export Scene). I've looked online and seen that I can export to a PDF via WriteImage("test.pdf",Writer="vtkPostScriptWriter"), but this doesn't offer me any of the flexibility I have when exporting from the GUI. Can someone recommend a way to export a PV view to PDF from Python that gives me the options of GL2PS? Any suggestions are greatly appreciated - thanks very much! Best, David From mrhyde at stanford.edu Wed Sep 24 17:05:40 2014 From: mrhyde at stanford.edu (D H) Date: Wed, 24 Sep 2014 14:05:40 -0700 (PDT) Subject: [Paraview] Keeping Only Clips In-Reply-To: <1503665259.7620612.1411592332191.JavaMail.zimbra@stanford.edu> Message-ID: <916060444.7641189.1411592740080.JavaMail.zimbra@stanford.edu> Hi, I have some VTK files (legacy VTK format, unstructured grid) that I'm rendering in Paraview. For each file, I load the file into Paraview, then do a scalar clip of that data. I render only the clip for each file. The thing is that doing this for a large number of files uses up a lot of memory. Each LegacyVTKReader uses about 30MB of RAM, and each clip uses only about 0.15MB of RAM. If I just kept the Clips in memory and could discard each LegacyVTKReader as soon as I made the corresponding clip, there's clearly a lot of memory that could be saved. This may be a silly question, but is there any way to "separate" a Clip from its parent data set? Like, can I just make the Clip its own (3D) geometric object, and forget about the fact that it originally came from a VTK file? Maybe this is impossible, but I thought I would ask in case there is some way to achieve what I'm thinking of and save a great deal of memory. Thanks very much! David From lifeandfree at gmail.com Thu Sep 25 05:02:31 2014 From: lifeandfree at gmail.com (=?UTF-8?B?0JjQu9GM0Y8g0KHRg9GF0LDRh9C10LI=?=) Date: Thu, 25 Sep 2014 15:02:31 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Hi, Sebastien Thank you. I just took advantage of this documentation and to deploy. I ran the script /data/pvw/bin/start.sh. But when entering the address: http://localhost/apps/Visualizer is only displayed only the green bar at the top of the window, and nothing more. That in this case? Sincerely, Sukhachev Ilya! 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < sebastien.jourdain at kitware.com>: > Moreover, the documentation that get's updated automatically can be found > at the following address. (Which might be more accurate.) > > http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html > > This is the one you find when you go on paraview.org and go to the > documentation section. > > Seb > > On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> Hi Sukhachev, >> >> The one thing that might not be explicit about the ubuntu_14_04 guide >> might be that the script "/data/pvw/bin/start.sh" should be launched >> with a DISPLAY setup. >> Otherwise, you will have to be more explicit on what you've done and what >> is not working. The log files usually helps to see what was skipped from >> the documentation. >> >> Seb >> >> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? >> wrote: >> >>> Good day! >>> Prompt please. >>> I used the instructions for deployment on Linux Ubuntu Paraviewweb ( >>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>> Unfolded, but for some reason I can not open in the web browser Visualizer >>> (http: // localhost / apps / Visualizer /) >>> When deployment by using the ( >>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only as >>> 1 Ceci. >>> How do I get access to many jobs, and through the web? >>> Thank you >>> >>> Sincerely, >>> Sukhachev Ilya! >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -- ? ?????????, ??????? ????! +7 912 216 72 72 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tristan.schloegl at ltd.uni-erlangen.de Thu Sep 25 05:49:16 2014 From: tristan.schloegl at ltd.uni-erlangen.de (Tristan =?ISO-8859-1?B?U2NobPZnbA==?=) Date: Thu, 25 Sep 2014 11:49:16 +0200 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Hi, I'm facing the same problem and would be quite interested in a solution as well. I'm loading pvd files, however the number of linked vtu files is not varying in my case. Just the content of the existing files changes. Something like a reload button or context menu entry in a future release would be perfect. Tristan Am 22.09.14 16:51 schrieb "Zenker, Dr. Matthias" unter : >Hi Utkarsh, > >I tested it for a series of vtu files, and indeed it works with the 4.2 >RC (not with 4.0.1). Also there is no error message on the Python console >any more. >Thank you! >Now I can at least follow the simulation going on by loading the vtu >series. > >Would it be possible to make it work also for a pvd...? :) > >Thanks, > >Matthias > >> -----Urspr?ngliche Nachricht----- >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Gesendet: Montag, 22. September 2014 16:09 >> An: Zenker, Dr. Matthias >> Cc: Cory Quammen; paraview at paraview.org >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> It's not going to work for pvd. From your original email, I gathered >>that you >> were using a fileseries of vtu files (maybe mistakenly). I made the >>script work >> for a series of vtu files. >> >> Utkarsh >> >> On Mon, Sep 22, 2014 at 10:03 AM, Zenker, Dr. Matthias >> wrote: >> > Done. >> > >> > Unfortunately, the result is the same: Nothing happens when I reload a >> pvd collection with added timesteps with the macro. >> > >> > On the console, the error message is different: >> > >> > File "", line 61, in >> > RuntimeError: Failed to locate the file listing. >> > >> > Matthias >> > >> >> -----Urspr?ngliche Nachricht----- >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> Gesendet: Montag, 22. September 2014 14:23 >> >> An: Zenker, Dr. Matthias >> >> Cc: Cory Quammen; paraview at paraview.org >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> Can you try the script with 4.2-RC before we try debugging this? >> >> >> >> Thanks >> >> Utkarsh >> >> >> >> On Mon, Sep 22, 2014 at 5:16 AM, Zenker, Dr. Matthias >> >> wrote: >> >> > Hi Utkarsh, >> >> > >> >> > thank you for the Python script. >> >> > Having never used Python scripts in ParaView before, I have >> >> > difficulties to >> >> run it. When I open the Python shell and try to launch the script >> >> with the "Run Script" button, I get an error message saying: >> >> > >> >> > Traceback (most recent call last): >> >> > File "", line 19, in >> >> > NameError: name 'GetActiveSource' is not defined >> >> > >> >> > I use ParaView 4.0.1 under Windows 7. I have added the lib >> >> > directory of >> >> ParaView to my path, as it says in the ParaView Python documentation. >> >> Is there anything else I need to do to run the script? >> >> > >> >> > When I load it as a macro, the corresponding button appears, but >> >> > when I >> >> click on it, nothing seems to happen. I have tested it with a pvd >> >> time collection where I have commented out the last timestep. When I >> >> loaded it, all timesteps but the last one were visible. Then I >> >> removed the comment marks around in the last timestep in the pvd file >> >> and lauched the Refresh Reader macro. I would expect that now the >> >> last timestep in the pvd would be visible, but it wasn't. >> >> > >> >> > You said that the reader to reload should be the active reader. How >> >> > do I >> >> see which reader is the active one? The pvd collection was >> >> highlighted when I activated the macro. Do I have to do something >>else? >> >> > >> >> > Thanks, >> >> > >> >> > Matthias >> >> > >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> >> Gesendet: Sonntag, 21. September 2014 16:17 >> >> >> An: Zenker, Dr. Matthias >> >> >> Cc: Cory Quammen; paraview at paraview.org >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> Matthias, >> >> >> >> >> >> Attached is the Python script that reloads a file-series. You can >> >> >> import this as a macro or just run it from the Python shell. In >> >> >> either case, ensure that the reader to reload is the active >>reader. >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> >> On Thu, Sep 18, 2014 at 9:34 AM, Zenker, Dr. Matthias >> >> >> wrote: >> >> >> > OK - but don't forget that the weekend is also there to have >> >> >> > some free time... ;) >> >> >> > >> >> >> > Matthias >> >> >> > >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> >> >> Gesendet: Donnerstag, 18. September 2014 14:46 >> >> >> >> An: Zenker, Dr. Matthias >> >> >> >> Cc: Cory Quammen; paraview at paraview.org >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> >> >> Sorry, didn't get around to it yet. Over this weekend is more >> >> >> >> likely, since I am tracking down some last minute issues with >> >> >> >> 4.2 right >> >> now. >> >> >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias >> >> >> >> wrote: >> >> >> >> > Hi Utkarsh, >> >> >> >> > >> >> >> >> > any news regarding a reload data function (see below)? >> >> >> >> > >> >> >> >> > Matthias >> >> >> >> > >> >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> >> >> >> Gesendet: Montag, 15. September 2014 16:50 >> >> >> >> >> An: Zenker, Dr. Matthias >> >> >> >> >> Cc: Cory Quammen; paraview at paraview.org >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >> >> >> >> >> >> >> >> >> >> Ah. since it's a file series, it would not work the way Cory >> >> >> >> >> is suggesting. I'll see if I can cook up a Python script >> >> >> >> >> that can make this possible for now. We're putting this on >> >> >> >> >> the roadmap for the next release (I know I've said that a >> >> >> >> >> few times in the past :) >> >> ). >> >> >> >> >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> >> >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias >> >> >> >> >> wrote: >> >> >> >> >> > Normally I load a time series, either a series of vtu >> >> >> >> >> > files or a time collection >> >> >> >> >> (pvd file containing the vtu file names with asociated >> timestamps). >> >> >> >> >> During the simulation, new files are added to the series. So >> >> >> >> >> it would be nice to watch the simulation going on by >> >> >> >> >> reloading from time >> >> >> to time. >> >> >> >> >> > >> >> >> >> >> > Matthias >> >> >> >> >> > >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> >> >> >> >> Gesendet: Montag, 15. September 2014 16:28 >> >> >> >> >> >> An: Zenker, Dr. Matthias >> >> >> >> >> >> Cc: Cory Quammen; paraview at paraview.org >> >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data >> >> >> >> >> >> file >> >> >> >> >> >> >> >> >> >> >> >> I suspect will not work with vtu. To understand this >> >> >> >> >> >> better, what is that which is changing that you need to >> >> >> >> >> >> reload the file? Are you loading a file series or a >>single file? >> >> >> >> >> >> >> >> >> >> >> >> Utkarsh >> >> >> >> >> >> >> >> >> >> >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias >> >> >> >> >> >> wrote: >> >> >> >> >> >> > Hi Cory, >> >> >> >> >> >> > >> >> >> >> >> >> > I use the reader for vtu format and pvd (vtu time >> >> >> >> >> >> > collection). I tried to >> >> >> >> >> >> modify the xml as follows: >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > > >> >> name="VTUrefresh" >> >> >> >> >> >> > base_proxygroup="sources" >> >> >> >> >> >> base_proxyname="VTUReader" class="vtuReader"> >> >> >> >> >> >> > > >> >> >> >> >> panel_widget="command_button"/> >> >> >> >> >> >> > >> >> >> >> >> >> > > >> >> >> >> >> > file_description="vtu Reader >> >> >> >> >> >> (Refresh button)" /> >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > But I cannot even load it as plugin. Presumably there >> >> >> >> >> >> > are special keyword to >> >> >> >> >> >> use for the name of the original reader. Is there a >> >> >> >> >> >> documentation where I can find more information on that >> topic? >> >> >> >> >> >> > >> >> >> >> >> >> > Thanks, >> >> >> >> >> >> > >> >> >> >> >> >> > Matthias >> >> >> >> >> >> > >> >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> >> >> >> Von: Cory Quammen >> [mailto:cory.quammen at kitware.com] >> >> >> >> >> >> >> Gesendet: Montag, 15. September 2014 15:05 >> >> >> >> >> >> >> An: Zenker, Dr. Matthias >> >> >> >> >> >> >> Cc: paraview at paraview.org >> >> >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data >> >> >> >> >> >> >> file >> >> >> >> >> >> >> >> >> >> >> >> >> >> Matthias, >> >> >> >> >> >> >> >> >> >> >> >> >> >> The method I suggested requires modifying ParaView's >> >> >> >> >> >> >> source code, so it won't work for a binary >>distribution. >> >> >> >> >> >> >> >> >> >> >> >> >> >> As for the XML method, did you try to load an Xdmf >> >> >> >> >> >> >> file through what should be the new "Xdmf Reader >> >> >> >> >> >> >> (Refresh >> >> >> button)" reader? >> >> >> >> >> >> >> If you are loading a different type of file, this >> >> >> >> >> >> >> plugin will have no effect because it provides a >> >> >> >> >> >> >> Refresh button only for the Xdmf reader. You could >> >> >> >> >> >> >> modify the XML for other reader types, >> >> >> >> though. >> >> >> >> >> >> >> >> >> >> >> >> >> >> Thanks, >> >> >> >> >> >> >> Cory >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias >> >> >> >> >> >> >> wrote: >> >> >> >> >> >> >> > Hi, >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > I wanted to try the "Reload" button which presumably >> >> >> >> >> >> >> > can be created by >> >> >> >> >> >> >> one of the methods outlined below. But I am maybe too >> >> >> >> >> >> >> naive or am missing >> >> >> >> >> >> >> something: I have a Windoze binary distribution of >> >> >> >> >> >> >> ParaView >> >> >> 4.0.1. >> >> >> >> >> >> >> I did not find the file indicated by Cory, and copying >> >> >> >> >> >> >> the xml code given by S?bastien into a file and >> >> >> >> >> >> >> loading that as plugin had no effect >> >> >> >> >> >> visible to me. >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > What am I missing here? >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > Thank you, >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > Matthias >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >> >> >> >> >> >> Von: paraview-bounces at paraview.org >> >> >> >> >> >> >> >> [mailto:paraview- bounces at paraview.org] Im Auftrag >> >> >> >> >> >> >> >> von paraview- >> >> >> >> >> >> request at paraview.org >> >> >> >> >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 >> >> >> >> >> >> >> >> An: paraview at paraview.org >> >> >> >> >> >> >> >> Betreff: Reload a file >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Send ParaView mailing list submissions to >> >> >> >> >> >> >> >> paraview at paraview.org >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, >> >> >> >> >> >> >> >> visit >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> or, via email, send a message with subject or body >> 'help' >> >> to >> >> >> >> >> >> >> >> paraview-request at paraview.org >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> You can reach the person managing the list at >> >> >> >> >> >> >> >> paraview-owner at paraview.org >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> When replying, please edit your Subject line so it >> >> >> >> >> >> >> >> is more specific than >> >> >> >> >> >> >> "Re: >> >> >> >> >> >> >> >> Contents of ParaView digest..." >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Today's Topics: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory >> >> >> >> >> >> >> >> Quammen) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------- >> >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> >> --- >> >> >> >> >> >> >> >> - >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Message: 1 >> >> >> >> >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 >> >> >> >> >> >> >> >> From: Cory Quammen >> >> >> >> >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a >> >> >> >> >> >> >> >> data file >> >> >> >> >> >> >> >> To: Sebastien Jourdain >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Cc: Michael Jackson , >> >> >> >> ParaView >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Message-ID: >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> >> >> >> >> >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> For what it's worth, I just experimented with >> >> >> >> >> >> >> >> adding the line >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> panel_widget="command_button"/> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> to the CSV reader and XDMF reader in >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers >> >> >> >> >> >> >> >> .xml >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> The Refresh button appears among the other property >> >> >> >> >> >> >> >> widgets and it indeed reloads the data set. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> I would happily add this to all the readers and >> >> >> >> >> >> >> >> submit a patch to gerrit if it would be received >> >> >> >> >> >> >> >> well by the core ParaView >> >> >> >> >> developers. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Thanks, >> >> >> >> >> >> >> >> Cory >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien >> >> >> >> >> >> >> >> Jourdain wrote: >> >> >> >> >> >> >> >> > BTW that's the correct XML for you, just need to >> >> >> >> >> >> >> >> > create a file with that in and load it as a >> >> >> >> >> >> >> >> > plugin and you will have your >> >> >> >> >> "Refresh" >> >> >> >> >> >> button. >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" >> >> >> >> >> >> >> >> > base_proxyname="XdmfReader" >> >> class="vtkXdmfReader"> >> >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > panel_widget="command_button"/> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > > >> >> >> >> >> >> >> > file_description="Xdmf Reader (Refresh button)" >>/> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien >> >> >> >> >> >> >> >> > Jourdain wrote: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Another approach could be a python macro that >> >> >> >> >> >> >> >> >> invalidate the "active/selected' proxy in the >> >> >> >> >> >> >> >> >> pipeline, but that one will require the usage of >> >> >> >> >> >> >> >> >> ParaView >> >> >> in built-in mode. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> If interested I can try to write the >> >> >> >> >> >> >> >> >> corresponding python >> >> >> >> code... >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Seb >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien >> >> >> >> >> >> >> >> >> Jourdain wrote: >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >>> I forgot to state the obvious, the plugin is a >>XML >> one... >> >> >> >> >> >> >> >> >>> No code involved... >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >>> In fact, just having the XML that I wrote in a >> >> >> >> >> >> >> >> >>> file extend the UI with a button to refresh the >> >> >> >> >> >> >> >> >>> reader should be >> >> >> >> enough. >> >> >> >> >> >> >> >> >>> Need to figure out why the reader factory did >> >> >> >> >> >> >> >> >>> not catch up the >> >> >> >> >> >> hint. >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >>> That should be the only thing that you would >> need. >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >>> Seb >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael >> >> >> >> >> >> >> >> >>> Jackson wrote: >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> I was hoping that ParaView just had something >> >> >> >> >> >> >> >> >>>> built >> >> in. >> >> >> >> >> >> >> >> >>>> I would rather not have to create a plugin and >> >> >> >> >> >> >> >> >>>> distribute that along side my own software and >> >> >> >> >> >> >> >> >>>> to keep up on builds for all the various OS's >> >> >> >> >> >> >> >> >>>> and all of >> >> that. >> >> >> >> >> >> >> >> >>>> i tried that for a while and I just could not >> >> >> >> >> >> >> keep up. >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> So either I am the only person who has asked >> >> >> >> >> >> >> >> >>>> for this or there is some over riding reason >> >> >> >> >> >> >> >> >>>> in the design of ParView why this type of >> >> >> >> >> >> >> >> >>>> functionality is not in >> >> >> ParaView. >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> Thanks >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> >> >> >> >> _ >> >> >> >> >> >> >> >> >>>> Mike Jackson Principal >>Software >> Engineer >> >> >> >> >> >> >> >> >>>> BlueQuartz Software >> Dayton, Ohio >> >> >> >> >> >> >> >> >>>> mike.jackson at bluequartz.net >> >> >> www.bluequartz.net >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> wrote: >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> > hi you can try the approach of S?bastien >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/t >> >> >> >> >> >> >> >> >>>> > ool >> >> >> >> >> >> >> >> >>>> > s.h >> >> >> >> >> >> >> >> >>>> > tml >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > I haven't tested yet. >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > You can save the code as a macro, so you >> >> >> >> >> >> >> >> >>>> > will have a >> >> >> >> button. >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > Felipe >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a >>?crit : >> >> >> >> >> >> >> >> >>>> >> Is there button where I can simply reload a >> >> >> >> >> >> >> >> >>>> >> data file that was read in a pipeline? >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >>>> >> We have a workflow where we process data >> >> >> >> >> >> >> >> >>>> >> into a file and view it in ParaView. it is >> >> >> >> >> >> >> >> >>>> >> becoming tedious to blow away the entire >> >> >> >> >> >> >> >> >>>> >> pipeline just to reload the new >> >> >> >> data. >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >>>> >> I know about state files but this still >> >> >> >> >> >> >> >> >>>> >> requires the user to go to the File->Load >> >> >> >> >> >> >> >> >>>> >> State... " menu and then select a state >> >> >> >> >> >> file. >> >> >> >> >> >> >> >> >>>> >> I would like to just select the data file >> >> >> >> >> >> >> >> >>>> >> in the Pipeline browser (XDMF File reader >> >> >> >> >> >> >> >> >>>> >> for us), and just click some button that >> >> >> >> >> >> >> >> >>>> >> just reloads data from >> >> >> the file. >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >>>> >> Or am I just missing something? I am using >> >> >> >> >> >> >> >> >>>> >> ParaView 3.98.1. I have to admit I have not >> >> >> >> >> >> >> >> >>>> >> tried any of the >> >> >> >> >> >> >> >> >>>> >> 4.0.RC* >> >> >> >> >> >> downloads. >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >>>> >> Thanks >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _________________________________________________________ >> >> >> >> >> >> >> >> >>>> >> Mike Jackson >> >> mike.jackson at bluequartz.net >> >> >> >> >> >> >> >> >>>> >> BlueQuartz Software >> >> www.bluequartz.net >> >> >> >> >> >> >> >> >>>> >> Principal Software Engineer >> Dayton, >> Ohio >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> >> >> >> >>>> >> Powered by www.kitware.com >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >>>> >> Visit other Kitware open-source projects at >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >>>> >> Please keep messages on-topic and check the >> >> >> >> >> >> >> >> >>>> >> ParaView Wiki >> >> >> >> >> >> at: >> >> >> >> >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> >> >>>> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > -- >> >> >> >> >> >> >> >> >>>> > Felipe Bordeu Weldt Ing?nieur de Recherche >> >> >> >> >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 >> >> >> >> >> >> >> >> >>>> > 74 >> >> >> >> >> >> >> >> >>>> > 74 >> >> >> >> >> >> >> >> >>>> > 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - >> >> >> >> >> >> >> >> >>>> > UMR CNRS >> >> >> >> >> >> >> >> >>>> > 6183 ?cole Centrale Nantes >> >> >> >> >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE >> >> >> >> >> >> >> >> >>>> > ------------------------------------- >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> _______________________________________________ >> >> >> >> >> >> >> >> >>>> > Powered by www.kitware.com >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > Visit other Kitware open-source projects at >> >> >> >> >> >> >> >> >>>> > >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > Please keep messages on-topic and check the >> >> >> >> >> >> >> >> >>>> > ParaView Wiki >> >> >> >> >> >> at: >> >> >> >> >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >> >>>> > >> >> >> >> >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/par >> >> >> >> >> >> >> >> >>>> > avi >> >> >> >> >> >> >> >> >>>> > ew >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> >> >> >> >> _______________________________________________ >> >> >> >> >> >> >> >> >>>> Powered by www.kitware.com >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> Visit other Kitware open-source projects at >> >> >> >> >> >> >> >> >>>> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> Please keep messages on-topic and check the >> >> >> >> >> >> >> >> >>>> ParaView Wiki >> >> >> >> >> at: >> >> >> >> >> >> >> >> >>>> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >> >>>> >> >> >> >> >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> >> >>>> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> _______________________________________________ >> >> >> >> >> >> >> >> > Powered by www.kitware.com >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> >> >> >> >> > >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > Please keep messages on-topic and check the >> >> >> >> >> >> >> >> > ParaView Wiki >> >> >> >> at: >> >> >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> >> >> Cory Quammen >> >> >> >> >> >> >> >> Research Associate >> >> >> >> >> >> >> >> Department of Computer Science The University of >> >> >> >> >> >> >> >> North Carolina at Chapel Hill >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> >> >> >> >> Powered by www.kitware.com >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Visit other Kitware open-source projects at >> >> >> >> >> >> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Please keep messages on-topic and check the >> >> >> >> >> >> >> >> ParaView Wiki >> >> >> at: >> >> >> >> >> >> >> >> http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 >> >> >> >> >> >> >> >> ***************************************** >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> >> >> >> ___________ >> >> >> >> >> >> >> > ERBE Elektromedizin GmbH >> >> >> >> >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> _______________________________________________ >> >> >> >> >> >> >> > Powered by www.kitware.com >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > Please keep messages on-topic and check the ParaView >> >> >> >> >> >> >> > Wiki >> >> >> at: >> >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> >> >> ___________ >> >> >> >> >> >> > ERBE Elektromedizin GmbH >> >> >> >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> >> >> >> > >> >> >> >> >> >> > >> _______________________________________________ >> >> >> >> >> >> > Powered by www.kitware.com >> >> >> >> >> >> > >> >> >> >> >> >> > Visit other Kitware open-source projects at >> >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >> >> >> >> > >> >> >> >> >> >> > Please keep messages on-topic and check the ParaView >> >> >> >> >> >> > Wiki >> >> at: >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView >> >> >> >> >> >> > >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> >> ___________ >> >> >> >> >> > ERBE Elektromedizin GmbH >> >> >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> >> >> >> >> >> >> __________________________________________________________ >> >> >> >> ___________ >> >> >> >> > ERBE Elektromedizin GmbH >> >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> __________________________________________________________ >> >> >> ___________ >> >> >> > ERBE Elektromedizin GmbH >> >> >> > Firmensitz: 72072 Tuebingen >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> >> > Registergericht: Stuttgart HRB 380137 >> >> >> > >> >> > >> >> > >> >> > >> >> >> __________________________________________________________ >> >> ___________ >> >> > ERBE Elektromedizin GmbH >> >> > Firmensitz: 72072 Tuebingen >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> >> > Registergericht: Stuttgart HRB 380137 >> >> > >> > >> > >> > >> __________________________________________________________ >> ___________ >> > ERBE Elektromedizin GmbH >> > Firmensitz: 72072 Tuebingen >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >> > Registergericht: Stuttgart HRB 380137 >> > > > >_____________________________________________________________________ >ERBE Elektromedizin GmbH >Firmensitz: 72072 Tuebingen >Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >Registergericht: Stuttgart HRB 380137 > >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at >http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: >http://paraview.org/Wiki/ParaView > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview From sebastien.jourdain at kitware.com Thu Sep 25 09:21:48 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 25 Sep 2014 07:21:48 -0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: The top bar is not green anymore. Try to replace the directory /lib, /apps, /ext within the ParaView /www inside the directory you serve with Apache. Moreover, can you enable the development tools on your browser to see what kind of error you got? Did you look also at the different types of logs? Apache, Launcher (see config to know where you choose to put them). That could also give you an idea on what went wrong. Seb On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? wrote: > Hi, Sebastien > > Thank you. > I just took advantage of this documentation and to deploy. > I ran the script /data/pvw/bin/start.sh. > But when entering the address: http://localhost/apps/Visualizer is only > displayed only the green bar at the top of the window, and nothing more. > That in this case? > > Sincerely, > Sukhachev Ilya! > > 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < > sebastien.jourdain at kitware.com>: > >> Moreover, the documentation that get's updated automatically can be found >> at the following address. (Which might be more accurate.) >> >> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >> >> This is the one you find when you go on paraview.org and go to the >> documentation section. >> >> Seb >> >> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >> sebastien.jourdain at kitware.com> wrote: >> >>> Hi Sukhachev, >>> >>> The one thing that might not be explicit about the ubuntu_14_04 guide >>> might be that the script "/data/pvw/bin/start.sh" should be launched >>> with a DISPLAY setup. >>> Otherwise, you will have to be more explicit on what you've done and >>> what is not working. The log files usually helps to see what was skipped >>> from the documentation. >>> >>> Seb >>> >>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? >>> wrote: >>> >>>> Good day! >>>> Prompt please. >>>> I used the instructions for deployment on Linux Ubuntu Paraviewweb ( >>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>> (http: // localhost / apps / Visualizer /) >>>> When deployment by using the ( >>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only as >>>> 1 Ceci. >>>> How do I get access to many jobs, and through the web? >>>> Thank you >>>> >>>> Sincerely, >>>> Sukhachev Ilya! >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > > > -- > ? ?????????, > ??????? ????! > +7 912 216 72 72 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ganesh.iitm at gmail.com Thu Sep 25 09:46:39 2014 From: ganesh.iitm at gmail.com (Ganesh Vijayakumar) Date: Thu, 25 Sep 2014 09:46:39 -0400 Subject: [Paraview] Keeping Only Clips In-Reply-To: <916060444.7641189.1411592740080.JavaMail.zimbra@stanford.edu> References: <1503665259.7620612.1411592332191.JavaMail.zimbra@stanford.edu> <916060444.7641189.1411592740080.JavaMail.zimbra@stanford.edu> Message-ID: I've done something similar in the past. I just write it out to a different dataset and read it in again. Do File -> Save Data. It can even save all data in the time series as individual datasets. On Wed, Sep 24, 2014 at 5:05 PM, D H wrote: > Hi, > > I have some VTK files (legacy VTK format, unstructured grid) that I'm > rendering in Paraview. For each file, I load the file into Paraview, then > do a scalar clip of that data. I render only the clip for each file. > > The thing is that doing this for a large number of files uses up a lot of > memory. Each LegacyVTKReader uses about 30MB of RAM, and each clip uses > only about 0.15MB of RAM. If I just kept the Clips in memory and could > discard each LegacyVTKReader as soon as I made the corresponding clip, > there's clearly a lot of memory that could be saved. > > This may be a silly question, but is there any way to "separate" a Clip > from its parent data set? Like, can I just make the Clip its own (3D) > geometric object, and forget about the fact that it originally came from a > VTK file? Maybe this is impossible, but I thought I would ask in case > there is some way to achieve what I'm thinking of and save a great deal of > memory. > > Thanks very much! > > David > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Sep 25 09:58:24 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 25 Sep 2014 09:58:24 -0400 Subject: [Paraview] How to simply "Reload" a data file In-Reply-To: References: Message-ID: Attached is a PVD reloader script. It should work for Matthias case where the pvd file changes to add more timesteps. I suspect it will work for you case too, Tristan. Worth a shot. Utkarsh On Thu, Sep 25, 2014 at 5:49 AM, Tristan Schl?gl wrote: > Hi, > > I'm facing the same problem and would be quite interested in a solution as > well. I'm loading pvd files, however the number of linked vtu files is not > varying in my case. Just the content of the existing files changes. > Something like a reload button or context menu entry in a future release > would be perfect. > > Tristan > > > > Am 22.09.14 16:51 schrieb "Zenker, Dr. Matthias" unter > : > >>Hi Utkarsh, >> >>I tested it for a series of vtu files, and indeed it works with the 4.2 >>RC (not with 4.0.1). Also there is no error message on the Python console >>any more. >>Thank you! >>Now I can at least follow the simulation going on by loading the vtu >>series. >> >>Would it be possible to make it work also for a pvd...? :) >> >>Thanks, >> >>Matthias >> >>> -----Urspr?ngliche Nachricht----- >>> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >>> Gesendet: Montag, 22. September 2014 16:09 >>> An: Zenker, Dr. Matthias >>> Cc: Cory Quammen; paraview at paraview.org >>> Betreff: Re: [Paraview] How to simply "Reload" a data file >>> >>> It's not going to work for pvd. From your original email, I gathered >>>that you >>> were using a fileseries of vtu files (maybe mistakenly). I made the >>>script work >>> for a series of vtu files. >>> >>> Utkarsh >>> >>> On Mon, Sep 22, 2014 at 10:03 AM, Zenker, Dr. Matthias >>> wrote: >>> > Done. >>> > >>> > Unfortunately, the result is the same: Nothing happens when I reload a >>> pvd collection with added timesteps with the macro. >>> > >>> > On the console, the error message is different: >>> > >>> > File "", line 61, in >>> > RuntimeError: Failed to locate the file listing. >>> > >>> > Matthias >>> > >>> >> -----Urspr?ngliche Nachricht----- >>> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >>> >> Gesendet: Montag, 22. September 2014 14:23 >>> >> An: Zenker, Dr. Matthias >>> >> Cc: Cory Quammen; paraview at paraview.org >>> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >>> >> >>> >> Can you try the script with 4.2-RC before we try debugging this? >>> >> >>> >> Thanks >>> >> Utkarsh >>> >> >>> >> On Mon, Sep 22, 2014 at 5:16 AM, Zenker, Dr. Matthias >>> >> wrote: >>> >> > Hi Utkarsh, >>> >> > >>> >> > thank you for the Python script. >>> >> > Having never used Python scripts in ParaView before, I have >>> >> > difficulties to >>> >> run it. When I open the Python shell and try to launch the script >>> >> with the "Run Script" button, I get an error message saying: >>> >> > >>> >> > Traceback (most recent call last): >>> >> > File "", line 19, in >>> >> > NameError: name 'GetActiveSource' is not defined >>> >> > >>> >> > I use ParaView 4.0.1 under Windows 7. I have added the lib >>> >> > directory of >>> >> ParaView to my path, as it says in the ParaView Python documentation. >>> >> Is there anything else I need to do to run the script? >>> >> > >>> >> > When I load it as a macro, the corresponding button appears, but >>> >> > when I >>> >> click on it, nothing seems to happen. I have tested it with a pvd >>> >> time collection where I have commented out the last timestep. When I >>> >> loaded it, all timesteps but the last one were visible. Then I >>> >> removed the comment marks around in the last timestep in the pvd file >>> >> and lauched the Refresh Reader macro. I would expect that now the >>> >> last timestep in the pvd would be visible, but it wasn't. >>> >> > >>> >> > You said that the reader to reload should be the active reader. How >>> >> > do I >>> >> see which reader is the active one? The pvd collection was >>> >> highlighted when I activated the macro. Do I have to do something >>>else? >>> >> > >>> >> > Thanks, >>> >> > >>> >> > Matthias >>> >> > >>> >> >> -----Urspr?ngliche Nachricht----- >>> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >>> >> >> Gesendet: Sonntag, 21. September 2014 16:17 >>> >> >> An: Zenker, Dr. Matthias >>> >> >> Cc: Cory Quammen; paraview at paraview.org >>> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >>> >> >> >>> >> >> Matthias, >>> >> >> >>> >> >> Attached is the Python script that reloads a file-series. You can >>> >> >> import this as a macro or just run it from the Python shell. In >>> >> >> either case, ensure that the reader to reload is the active >>>reader. >>> >> >> >>> >> >> Utkarsh >>> >> >> >>> >> >> >>> >> >> On Thu, Sep 18, 2014 at 9:34 AM, Zenker, Dr. Matthias >>> >> >> wrote: >>> >> >> > OK - but don't forget that the weekend is also there to have >>> >> >> > some free time... ;) >>> >> >> > >>> >> >> > Matthias >>> >> >> > >>> >> >> >> -----Urspr?ngliche Nachricht----- >>> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >>> >> >> >> Gesendet: Donnerstag, 18. September 2014 14:46 >>> >> >> >> An: Zenker, Dr. Matthias >>> >> >> >> Cc: Cory Quammen; paraview at paraview.org >>> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >>> >> >> >> >>> >> >> >> Sorry, didn't get around to it yet. Over this weekend is more >>> >> >> >> likely, since I am tracking down some last minute issues with >>> >> >> >> 4.2 right >>> >> now. >>> >> >> >> >>> >> >> >> Utkarsh >>> >> >> >> >>> >> >> >> On Thu, Sep 18, 2014 at 3:33 AM, Zenker, Dr. Matthias >>> >> >> >> wrote: >>> >> >> >> > Hi Utkarsh, >>> >> >> >> > >>> >> >> >> > any news regarding a reload data function (see below)? >>> >> >> >> > >>> >> >> >> > Matthias >>> >> >> >> > >>> >> >> >> >> -----Urspr?ngliche Nachricht----- >>> >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >>> >> >> >> >> Gesendet: Montag, 15. September 2014 16:50 >>> >> >> >> >> An: Zenker, Dr. Matthias >>> >> >> >> >> Cc: Cory Quammen; paraview at paraview.org >>> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data file >>> >> >> >> >> >>> >> >> >> >> Ah. since it's a file series, it would not work the way Cory >>> >> >> >> >> is suggesting. I'll see if I can cook up a Python script >>> >> >> >> >> that can make this possible for now. We're putting this on >>> >> >> >> >> the roadmap for the next release (I know I've said that a >>> >> >> >> >> few times in the past :) >>> >> ). >>> >> >> >> >> >>> >> >> >> >> Utkarsh >>> >> >> >> >> >>> >> >> >> >> On Mon, Sep 15, 2014 at 10:31 AM, Zenker, Dr. Matthias >>> >> >> >> >> wrote: >>> >> >> >> >> > Normally I load a time series, either a series of vtu >>> >> >> >> >> > files or a time collection >>> >> >> >> >> (pvd file containing the vtu file names with asociated >>> timestamps). >>> >> >> >> >> During the simulation, new files are added to the series. So >>> >> >> >> >> it would be nice to watch the simulation going on by >>> >> >> >> >> reloading from time >>> >> >> to time. >>> >> >> >> >> > >>> >> >> >> >> > Matthias >>> >> >> >> >> > >>> >> >> >> >> >> -----Urspr?ngliche Nachricht----- >>> >> >> >> >> >> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >>> >> >> >> >> >> Gesendet: Montag, 15. September 2014 16:28 >>> >> >> >> >> >> An: Zenker, Dr. Matthias >>> >> >> >> >> >> Cc: Cory Quammen; paraview at paraview.org >>> >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data >>> >> >> >> >> >> file >>> >> >> >> >> >> >>> >> >> >> >> >> I suspect will not work with vtu. To understand this >>> >> >> >> >> >> better, what is that which is changing that you need to >>> >> >> >> >> >> reload the file? Are you loading a file series or a >>>single file? >>> >> >> >> >> >> >>> >> >> >> >> >> Utkarsh >>> >> >> >> >> >> >>> >> >> >> >> >> On Mon, Sep 15, 2014 at 9:54 AM, Zenker, Dr. Matthias >>> >> >> >> >> >> wrote: >>> >> >> >> >> >> > Hi Cory, >>> >> >> >> >> >> > >>> >> >> >> >> >> > I use the reader for vtu format and pvd (vtu time >>> >> >> >> >> >> > collection). I tried to >>> >> >> >> >> >> modify the xml as follows: >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > >> >> >> name="VTUrefresh" >>> >> >> >> >> >> > base_proxygroup="sources" >>> >> >> >> >> >> base_proxyname="VTUReader" class="vtuReader"> >>> >> >> >> >> >> > >> >> >> >> >> >> panel_widget="command_button"/> >>> >> >> >> >> >> > >>> >> >> >> >> >> > >> >> >> >> >> >> > file_description="vtu Reader >>> >> >> >> >> >> (Refresh button)" /> >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > But I cannot even load it as plugin. Presumably there >>> >> >> >> >> >> > are special keyword to >>> >> >> >> >> >> use for the name of the original reader. Is there a >>> >> >> >> >> >> documentation where I can find more information on that >>> topic? >>> >> >> >> >> >> > >>> >> >> >> >> >> > Thanks, >>> >> >> >> >> >> > >>> >> >> >> >> >> > Matthias >>> >> >> >> >> >> > >>> >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- >>> >> >> >> >> >> >> Von: Cory Quammen >>> [mailto:cory.quammen at kitware.com] >>> >> >> >> >> >> >> Gesendet: Montag, 15. September 2014 15:05 >>> >> >> >> >> >> >> An: Zenker, Dr. Matthias >>> >> >> >> >> >> >> Cc: paraview at paraview.org >>> >> >> >> >> >> >> Betreff: Re: [Paraview] How to simply "Reload" a data >>> >> >> >> >> >> >> file >>> >> >> >> >> >> >> >>> >> >> >> >> >> >> Matthias, >>> >> >> >> >> >> >> >>> >> >> >> >> >> >> The method I suggested requires modifying ParaView's >>> >> >> >> >> >> >> source code, so it won't work for a binary >>>distribution. >>> >> >> >> >> >> >> >>> >> >> >> >> >> >> As for the XML method, did you try to load an Xdmf >>> >> >> >> >> >> >> file through what should be the new "Xdmf Reader >>> >> >> >> >> >> >> (Refresh >>> >> >> button)" reader? >>> >> >> >> >> >> >> If you are loading a different type of file, this >>> >> >> >> >> >> >> plugin will have no effect because it provides a >>> >> >> >> >> >> >> Refresh button only for the Xdmf reader. You could >>> >> >> >> >> >> >> modify the XML for other reader types, >>> >> >> >> though. >>> >> >> >> >> >> >> >>> >> >> >> >> >> >> Thanks, >>> >> >> >> >> >> >> Cory >>> >> >> >> >> >> >> >>> >> >> >> >> >> >> On Mon, Sep 15, 2014 at 4:16 AM, Zenker, Dr. Matthias >>> >> >> >> >> >> >> wrote: >>> >> >> >> >> >> >> > Hi, >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> > I wanted to try the "Reload" button which presumably >>> >> >> >> >> >> >> > can be created by >>> >> >> >> >> >> >> one of the methods outlined below. But I am maybe too >>> >> >> >> >> >> >> naive or am missing >>> >> >> >> >> >> >> something: I have a Windoze binary distribution of >>> >> >> >> >> >> >> ParaView >>> >> >> 4.0.1. >>> >> >> >> >> >> >> I did not find the file indicated by Cory, and copying >>> >> >> >> >> >> >> the xml code given by S?bastien into a file and >>> >> >> >> >> >> >> loading that as plugin had no effect >>> >> >> >> >> >> visible to me. >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> > What am I missing here? >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> > Thank you, >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> > Matthias >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> -----Urspr?ngliche Nachricht----- >>> >> >> >> >> >> >> >> Von: paraview-bounces at paraview.org >>> >> >> >> >> >> >> >> [mailto:paraview- bounces at paraview.org] Im Auftrag >>> >> >> >> >> >> >> >> von paraview- >>> >> >> >> >> >> request at paraview.org >>> >> >> >> >> >> >> >> Gesendet: Samstag, 15. Juni 2013 18:00 >>> >> >> >> >> >> >> >> An: paraview at paraview.org >>> >> >> >> >> >> >> >> Betreff: Reload a file >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> Send ParaView mailing list submissions to >>> >> >> >> >> >> >> >> paraview at paraview.org >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, >>> >> >> >> >> >> >> >> visit >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >>> >> >> >> >> >> >> >> or, via email, send a message with subject or body >>> 'help' >>> >> to >>> >> >> >> >> >> >> >> paraview-request at paraview.org >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> You can reach the person managing the list at >>> >> >> >> >> >> >> >> paraview-owner at paraview.org >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> When replying, please edit your Subject line so it >>> >> >> >> >> >> >> >> is more specific than >>> >> >> >> >> >> >> "Re: >>> >> >> >> >> >> >> >> Contents of ParaView digest..." >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> Today's Topics: >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> 1. Re: How to simply "Reload" a data file (Cory >>> >> >> >> >> >> >> >> Quammen) >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> --------------------------------------------------- >>> >> >> >> >> >> >> >> --- >>> >> >> >> >> >> >> >> --- >>> >> >> >> >> >> >> >> --- >>> >> >> >> >> >> >> >> --- >>> >> >> >> >> >> >> >> --- >>> >> >> >> >> >> >> >> --- >>> >> >> >> >> >> >> >> - >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> Message: 1 >>> >> >> >> >> >> >> >> Date: Fri, 14 Jun 2013 13:42:34 -0400 >>> >> >> >> >> >> >> >> From: Cory Quammen >>> >> >> >> >> >> >> >> Subject: Re: [Paraview] How to simply "Reload" a >>> >> >> >> >> >> >> >> data file >>> >> >> >> >> >> >> >> To: Sebastien Jourdain >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> Cc: Michael Jackson , >>> >> >> >> ParaView >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> Message-ID: >>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> OeRVRSrNbZUSQXg at mail.gmail.com> >>> >> >> >> >> >> >> >> Content-Type: text/plain; charset=ISO-8859-1 >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> For what it's worth, I just experimented with >>> >> >> >> >> >> >> >> adding the line >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> panel_widget="command_button"/> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> to the CSV reader and XDMF reader in >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> >> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >>> >> >> >>> >> >>> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers >>> >> >> >> >> >> >> >> .xml >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> The Refresh button appears among the other property >>> >> >> >> >> >> >> >> widgets and it indeed reloads the data set. >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> I would happily add this to all the readers and >>> >> >> >> >> >> >> >> submit a patch to gerrit if it would be received >>> >> >> >> >> >> >> >> well by the core ParaView >>> >> >> >> >> developers. >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> Thanks, >>> >> >> >> >> >> >> >> Cory >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 11:57 AM, Sebastien >>> >> >> >> >> >> >> >> Jourdain wrote: >>> >> >> >> >> >> >> >> > BTW that's the correct XML for you, just need to >>> >> >> >> >> >> >> >> > create a file with that in and load it as a >>> >> >> >> >> >> >> >> > plugin and you will have your >>> >> >> >> >> "Refresh" >>> >> >> >> >> >> button. >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > name="XDMFRrefresh" base_proxygroup="sources" >>> >> >> >> >> >> >> >> > base_proxyname="XdmfReader" >>> >> class="vtkXdmfReader"> >>> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > panel_widget="command_button"/> >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > file_description="Xdmf Reader (Refresh button)" >>>/> >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > On Fri, Jun 14, 2013 at 10:27 AM, Sebastien >>> >> >> >> >> >> >> >> > Jourdain wrote: >>> >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> Another approach could be a python macro that >>> >> >> >> >> >> >> >> >> invalidate the "active/selected' proxy in the >>> >> >> >> >> >> >> >> >> pipeline, but that one will require the usage of >>> >> >> >> >> >> >> >> >> ParaView >>> >> >> in built-in mode. >>> >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> If interested I can try to write the >>> >> >> >> >> >> >> >> >> corresponding python >>> >> >> >> code... >>> >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> Seb >>> >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >> On Fri, Jun 14, 2013 at 10:24 AM, Sebastien >>> >> >> >> >> >> >> >> >> Jourdain wrote: >>> >> >> >> >> >> >> >> >>> >>> >> >> >> >> >> >> >> >>> I forgot to state the obvious, the plugin is a >>>XML >>> one... >>> >> >> >> >> >> >> >> >>> No code involved... >>> >> >> >> >> >> >> >> >>> >>> >> >> >> >> >> >> >> >>> In fact, just having the XML that I wrote in a >>> >> >> >> >> >> >> >> >>> file extend the UI with a button to refresh the >>> >> >> >> >> >> >> >> >>> reader should be >>> >> >> >> enough. >>> >> >> >> >> >> >> >> >>> Need to figure out why the reader factory did >>> >> >> >> >> >> >> >> >>> not catch up the >>> >> >> >> >> >> hint. >>> >> >> >> >> >> >> >> >>> >>> >> >> >> >> >> >> >> >>> That should be the only thing that you would >>> need. >>> >> >> >> >> >> >> >> >>> >>> >> >> >> >> >> >> >> >>> Seb >>> >> >> >> >> >> >> >> >>> >>> >> >> >> >> >> >> >> >>> >>> >> >> >> >> >> >> >> >>> >>> >> >> >> >> >> >> >> >>> On Fri, Jun 14, 2013 at 10:08 AM, Michael >>> >> >> >> >> >> >> >> >>> Jackson wrote: >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>>> I was hoping that ParaView just had something >>> >> >> >> >> >> >> >> >>>> built >>> >> in. >>> >> >> >> >> >> >> >> >>>> I would rather not have to create a plugin and >>> >> >> >> >> >> >> >> >>>> distribute that along side my own software and >>> >> >> >> >> >> >> >> >>>> to keep up on builds for all the various OS's >>> >> >> >> >> >> >> >> >>>> and all of >>> >> that. >>> >> >> >> >> >> >> >> >>>> i tried that for a while and I just could not >>> >> >> >> >> >> >> keep up. >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>>> So either I am the only person who has asked >>> >> >> >> >> >> >> >> >>>> for this or there is some over riding reason >>> >> >> >> >> >> >> >> >>>> in the design of ParView why this type of >>> >> >> >> >> >> >> >> >>>> functionality is not in >>> >> >> ParaView. >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>>> Thanks >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> >> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >>> >> >> >>> >> >>> __________________________________________________________ >>> >> >> >> >> >> >> >> _ >>> >> >> >> >> >> >> >> >>>> Mike Jackson Principal >>>Software >>> Engineer >>> >> >> >> >> >> >> >> >>>> BlueQuartz Software >>> Dayton, Ohio >>> >> >> >> >> >> >> >> >>>> mike.jackson at bluequartz.net >>> >> >> www.bluequartz.net >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>>> On Jun 14, 2013, at 3:40 PM, Felipe Bordeu >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>>> wrote: >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>>> > hi you can try the approach of S?bastien >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > http://perso.uclouvain.be/sebastien.blaise/t >>> >> >> >> >> >> >> >> >>>> > ool >>> >> >> >> >> >> >> >> >>>> > s.h >>> >> >> >> >> >> >> >> >>>> > tml >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > I haven't tested yet. >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > You can save the code as a macro, so you >>> >> >> >> >> >> >> >> >>>> > will have a >>> >> >> >> button. >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > Felipe >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > Le 14/06/2013 09:42, Michael Jackson a >>>?crit : >>> >> >> >> >> >> >> >> >>>> >> Is there button where I can simply reload a >>> >> >> >> >> >> >> >> >>>> >> data file that was read in a pipeline? >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> >> >> >> >> >> >>>> >> We have a workflow where we process data >>> >> >> >> >> >> >> >> >>>> >> into a file and view it in ParaView. it is >>> >> >> >> >> >> >> >> >>>> >> becoming tedious to blow away the entire >>> >> >> >> >> >> >> >> >>>> >> pipeline just to reload the new >>> >> >> >> data. >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> >> >> >> >> >> >>>> >> I know about state files but this still >>> >> >> >> >> >> >> >> >>>> >> requires the user to go to the File->Load >>> >> >> >> >> >> >> >> >>>> >> State... " menu and then select a state >>> >> >> >> >> >> file. >>> >> >> >> >> >> >> >> >>>> >> I would like to just select the data file >>> >> >> >> >> >> >> >> >>>> >> in the Pipeline browser (XDMF File reader >>> >> >> >> >> >> >> >> >>>> >> for us), and just click some button that >>> >> >> >> >> >> >> >> >>>> >> just reloads data from >>> >> >> the file. >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> >> >> >> >> >> >>>> >> Or am I just missing something? I am using >>> >> >> >> >> >> >> >> >>>> >> ParaView 3.98.1. I have to admit I have not >>> >> >> >> >> >> >> >> >>>> >> tried any of the >>> >> >> >> >> >> >> >> >>>> >> 4.0.RC* >>> >> >> >> >> >> downloads. >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> >> >> >> >> >> >>>> >> Thanks >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >>> >> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >>> >> >> >>> >> >>> _________________________________________________________ >>> >> >> >> >> >> >> >> >>>> >> Mike Jackson >>> >> mike.jackson at bluequartz.net >>> >> >> >> >> >> >> >> >>>> >> BlueQuartz Software >>> >> www.bluequartz.net >>> >> >> >> >> >> >> >> >>>> >> Principal Software Engineer >>> Dayton, >>> Ohio >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> >> >> _______________________________________________ >>> >> >> >> >> >> >> >> >>>> >> Powered by www.kitware.com >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> >> >> >> >> >> >>>> >> Visit other Kitware open-source projects at >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> >> http://www.kitware.com/opensource/opensource.html >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> >> >> >> >> >> >>>> >> Please keep messages on-topic and check the >>> >> >> >> >> >> >> >> >>>> >> ParaView Wiki >>> >> >> >> >> >> at: >>> >> >> >> >> >> >> >> >>>> >> http://paraview.org/Wiki/ParaView >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> >> >> >> >> >> >>>> >> Follow this link to subscribe/unsubscribe: >>> >> >> >> >> >> >> >> >>>> >> >>> >> >> http://www.paraview.org/mailman/listinfo/paraview >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > -- >>> >> >> >> >> >> >> >> >>>> > Felipe Bordeu Weldt Ing?nieur de Recherche >>> >> >> >> >> >> >> >> >>>> > ------------------------------------- >>> >> >> >> >> >> >> >> >>>> > T?l. : 33 (0)2 40 37 16 57 Fax. : 33 (0)2 40 >>> >> >> >> >> >> >> >> >>>> > 74 >>> >> >> >> >> >> >> >> >>>> > 74 >>> >> >> >> >> >> >> >> >>>> > 06 Felipe.Bordeu at ec-nantes.fr Institut GeM - >>> >> >> >> >> >> >> >> >>>> > UMR CNRS >>> >> >> >> >> >> >> >> >>>> > 6183 ?cole Centrale Nantes >>> >> >> >> >> >> >> >> >>>> > 1 Rue de La No?, 44321 Nantes, FRANCE >>> >> >> >> >> >> >> >> >>>> > ------------------------------------- >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> _______________________________________________ >>> >> >> >> >> >> >> >> >>>> > Powered by www.kitware.com >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > Visit other Kitware open-source projects at >>> >> >> >> >> >> >> >> >>>> > >>> >> >> http://www.kitware.com/opensource/opensource.html >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > Please keep messages on-topic and check the >>> >> >> >> >> >> >> >> >>>> > ParaView Wiki >>> >> >> >> >> >> at: >>> >> >> >> >> >> >> >> >>>> > http://paraview.org/Wiki/ParaView >>> >> >> >> >> >> >> >> >>>> > >>> >> >> >> >> >> >> >> >>>> > Follow this link to subscribe/unsubscribe: >>> >> >> >> >> >> >> >> >>>> > http://www.paraview.org/mailman/listinfo/par >>> >> >> >> >> >> >> >> >>>> > avi >>> >> >> >> >> >> >> >> >>>> > ew >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> _______________________________________________ >>> >> >> >> >> >> >> >> >>>> Powered by www.kitware.com >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>>> Visit other Kitware open-source projects at >>> >> >> >> >> >> >> >> >>>> >>> >> >> http://www.kitware.com/opensource/opensource.html >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>>> Please keep messages on-topic and check the >>> >> >> >> >> >> >> >> >>>> ParaView Wiki >>> >> >> >> >> at: >>> >> >> >> >> >> >> >> >>>> http://paraview.org/Wiki/ParaView >>> >> >> >> >> >> >> >> >>>> >>> >> >> >> >> >> >> >> >>>> Follow this link to subscribe/unsubscribe: >>> >> >> >> >> >> >> >> >>>> >>> >> http://www.paraview.org/mailman/listinfo/paraview >>> >> >> >> >> >> >> >> >>> >>> >> >> >> >> >> >> >> >>> >>> >> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > >>> >> >> _______________________________________________ >>> >> >> >> >> >> >> >> > Powered by www.kitware.com >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > Visit other Kitware open-source projects at >>> >> >> >> >> >> >> >> > >>> http://www.kitware.com/opensource/opensource.html >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > Please keep messages on-topic and check the >>> >> >> >> >> >> >> >> > ParaView Wiki >>> >> >> >> at: >>> >> >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >>> >> >> >> >> >> >> >> > http://www.paraview.org/mailman/listinfo/paraview >>> >> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> -- >>> >> >> >> >> >> >> >> Cory Quammen >>> >> >> >> >> >> >> >> Research Associate >>> >> >> >> >> >> >> >> Department of Computer Science The University of >>> >> >> >> >> >> >> >> North Carolina at Chapel Hill >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> ------------------------------ >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> _______________________________________________ >>> >> >> >> >> >> >> >> Powered by www.kitware.com >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> Visit other Kitware open-source projects at >>> >> >> >> >> >> >> >> >>> http://www.kitware.com/opensource/opensource.html >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> Please keep messages on-topic and check the >>> >> >> >> >> >> >> >> ParaView Wiki >>> >> >> at: >>> >> >> >> >> >> >> >> http://paraview.org/Wiki/ParaView >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> Follow this link to subscribe/unsubscribe: >>> >> >> >> >> >> >> >> http://www.paraview.org/mailman/listinfo/paraview >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> >>> >> >> >> >> >> >> >> End of ParaView Digest, Vol 110, Issue 42 >>> >> >> >> >> >> >> >> ***************************************** >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> >>> >> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >>> >> >> >>> >> >>> __________________________________________________________ >>> >> >> >> >> >> >> ___________ >>> >> >> >> >> >> >> > ERBE Elektromedizin GmbH >>> >> >> >> >> >> >> > Firmensitz: 72072 Tuebingen >>> >> >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >>> >> >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> > >>> >> _______________________________________________ >>> >> >> >> >> >> >> > Powered by www.kitware.com >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> > Visit other Kitware open-source projects at >>> >> >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> > Please keep messages on-topic and check the ParaView >>> >> >> >> >> >> >> > Wiki >>> >> >> at: >>> >> >> >> >> >> >> > http://paraview.org/Wiki/ParaView >>> >> >> >> >> >> >> > >>> >> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >>> >> >> >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> >> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >>> >> >> >>> >> >>> __________________________________________________________ >>> >> >> >> >> >> ___________ >>> >> >> >> >> >> > ERBE Elektromedizin GmbH >>> >> >> >> >> >> > Firmensitz: 72072 Tuebingen >>> >> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >>> >> >> >> >> >> > Registergericht: Stuttgart HRB 380137 >>> >> >> >> >> >> > >>> >> >> >> >> >> > >>> _______________________________________________ >>> >> >> >> >> >> > Powered by www.kitware.com >>> >> >> >> >> >> > >>> >> >> >> >> >> > Visit other Kitware open-source projects at >>> >> >> >> >> >> > http://www.kitware.com/opensource/opensource.html >>> >> >> >> >> >> > >>> >> >> >> >> >> > Please keep messages on-topic and check the ParaView >>> >> >> >> >> >> > Wiki >>> >> at: >>> >> >> >> >> >> > http://paraview.org/Wiki/ParaView >>> >> >> >> >> >> > >>> >> >> >> >> >> > Follow this link to subscribe/unsubscribe: >>> >> >> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> >> > >>> >> >> >> >> > >>> >> >> >> >> > >>> >> >> >> >> >>> >> >> >> >>> >> >> >>> >> >>> __________________________________________________________ >>> >> >> >> >> ___________ >>> >> >> >> >> > ERBE Elektromedizin GmbH >>> >> >> >> >> > Firmensitz: 72072 Tuebingen >>> >> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >>> >> >> >> >> > Registergericht: Stuttgart HRB 380137 >>> >> >> >> >> > >>> >> >> >> > >>> >> >> >> > >>> >> >> >> > >>> >> >> >> >>> >> >> >>> >> >>> __________________________________________________________ >>> >> >> >> ___________ >>> >> >> >> > ERBE Elektromedizin GmbH >>> >> >> >> > Firmensitz: 72072 Tuebingen >>> >> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >>> >> >> >> > Registergericht: Stuttgart HRB 380137 >>> >> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> >>> >> >>> __________________________________________________________ >>> >> >> ___________ >>> >> >> > ERBE Elektromedizin GmbH >>> >> >> > Firmensitz: 72072 Tuebingen >>> >> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >>> >> >> > Registergericht: Stuttgart HRB 380137 >>> >> >> > >>> >> > >>> >> > >>> >> > >>> >> >>> __________________________________________________________ >>> >> ___________ >>> >> > ERBE Elektromedizin GmbH >>> >> > Firmensitz: 72072 Tuebingen >>> >> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >>> >> > Registergericht: Stuttgart HRB 380137 >>> >> > >>> > >>> > >>> > >>> __________________________________________________________ >>> ___________ >>> > ERBE Elektromedizin GmbH >>> > Firmensitz: 72072 Tuebingen >>> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >>> > Registergericht: Stuttgart HRB 380137 >>> > >> >> >>_____________________________________________________________________ >>ERBE Elektromedizin GmbH >>Firmensitz: 72072 Tuebingen >>Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede >>Registergericht: Stuttgart HRB 380137 >> >>_______________________________________________ >>Powered by www.kitware.com >> >>Visit other Kitware open-source projects at >>http://www.kitware.com/opensource/opensource.html >> >>Please keep messages on-topic and check the ParaView Wiki at: >>http://paraview.org/Wiki/ParaView >> >>Follow this link to subscribe/unsubscribe: >>http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- A non-text attachment was scrubbed... Name: RefreshReaderPVD.py Type: text/x-python Size: 1475 bytes Desc: not available URL: From Matthias.Zenker at erbe-med.com Thu Sep 25 10:59:35 2014 From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias) Date: Thu, 25 Sep 2014 14:59:35 +0000 Subject: [Paraview] How to simply "Reload" a data file Message-ID: I have quickly tested the script, it works for me. Thank you Utkarsh! Matthias > Attached is a PVD reloader script. It should work for Matthias case > where the pvd file changes to add more timesteps. I suspect it will > work for you case too, Tristan. Worth a shot. > > Utkarsh _____________________________________________________________________ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.Murphy at lasp.colorado.edu Thu Sep 25 12:45:01 2014 From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy) Date: Thu, 25 Sep 2014 10:45:01 -0600 Subject: [Paraview] using calculator filter on a table? Message-ID: <8D5C1B82EA40014E8B222E92B9076325021358774366@MAILBOX.LASP.colorado.edu> Hello all, Is there a way to use the Calculator filter on a table? My reader loads a bunch of auxiliary files that loads time-series information for a specific point (at a higher temporal resolution than the 3D model output). I need to be able to convert the units in the time series information with some simple calculations so that I can match the units of the remainder of my work. Is there a way to use the calculator filter to do this? It is greyed out when I have the table selected... Are there some other steps I need to do to make it work? Thanks, Josh From utkarsh.ayachit at kitware.com Thu Sep 25 13:23:21 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 25 Sep 2014 13:23:21 -0400 Subject: [Paraview] using calculator filter on a table? In-Reply-To: <8D5C1B82EA40014E8B222E92B9076325021358774366@MAILBOX.LASP.colorado.edu> References: <8D5C1B82EA40014E8B222E92B9076325021358774366@MAILBOX.LASP.colorado.edu> Message-ID: For now, with 4.2 RC1, stick to using "Programmable Filter" with "Script" as follows: expr = inputs[0].RowData["RTData"] * 2.0 output.RowData.append(expr, "result") If you can add a bug to the bug tracker for this, that'd be great too. Thanks Utkarsh On Thu, Sep 25, 2014 at 12:45 PM, Joshua Murphy wrote: > Hello all, > > Is there a way to use the Calculator filter on a table? > > My reader loads a bunch of auxiliary files that loads time-series information for a specific point (at a higher temporal resolution than the 3D model output). I need to be able to convert the units in the time series information with some simple calculations so that I can match the units of the remainder of my work. > > Is there a way to use the calculator filter to do this? It is greyed out when I have the table selected... Are there some other steps I need to do to make it work? > > Thanks, > Josh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Thu Sep 25 13:35:13 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 25 Sep 2014 13:35:13 -0400 Subject: [Paraview] Exporting to PDF from Python In-Reply-To: <463744129.7614860.1411592161048.JavaMail.zimbra@stanford.edu> References: <1115533102.7600754.1411591876388.JavaMail.zimbra@stanford.edu> <463744129.7614860.1411592161048.JavaMail.zimbra@stanford.edu> Message-ID: With ParaView 4.2-RC, you can use the Python trace to generate the script to use for exporting. It looks something like so: ExportView('/tmp/sample.pdf', view=renderView1, Plottitle='MyPlot', Compressoutputfile=1, Linewidthscalingfactor=1.0, Pointsizescalingfactor=1.0) For 4.1, look at the implementation of "ExportView" in [1]. You can use a similar code for the same effect. Utkarsh [1] https://github.com/Kitware/ParaView/blob/master/Wrapping/Python/paraview/simple.py On Wed, Sep 24, 2014 at 4:56 PM, D H wrote: > Hi, > > I have a scene in Paraview 4.1 that I'd like to export to a PDF from a Python script. Ideally I'd like to be able to use the GL2PSExporter and set options there (such as "Cull Hidden Primitives") like I do in the PV GUI (under File->Export Scene). I've looked online and seen that I can export to a PDF via WriteImage("test.pdf",Writer="vtkPostScriptWriter"), but this doesn't offer me any of the flexibility I have when exporting from the GUI. > > Can someone recommend a way to export a PV view to PDF from Python that gives me the options of GL2PS? Any suggestions are greatly appreciated - thanks very much! > > Best, > > David > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From jlih at masonlive.gmu.edu Thu Sep 25 14:17:37 2014 From: jlih at masonlive.gmu.edu (jlih) Date: Thu, 25 Sep 2014 18:17:37 +0000 Subject: [Paraview] Connect to multiple servers to visualize one file Message-ID: <1411669057318.4927@masonlive.gmu.edu> Dear all, I have a few questions regarding the server configuration of the remote visualization framework. For instance,I have two render nodes at Location A and four render nodes at Location B, all nodes can access a copy of a dataset. 1. Can I connect to multiple servers that the same time? For example: connection1 =Connect('ip1',11111) connection1 =Connect('ip2',11111) ##some render codes Disconnect() 2. If I can connect to multiple servers at the same time, can the client access all nodes and visualize the dataset in parallel at the same time? That is, nodes at Location A render a portion of the data and nodes at Location B render the rest part of the data. Do I need to split the dataset? 3. If I can not visualize the same data with servers at different locations, what is the best approach to utilize all nodes at different locations in parallel? Thanks in advance. Jing -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.Murphy at lasp.colorado.edu Thu Sep 25 14:26:47 2014 From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy) Date: Thu, 25 Sep 2014 12:26:47 -0600 Subject: [Paraview] using calculator filter on a table? In-Reply-To: References: <8D5C1B82EA40014E8B222E92B9076325021358774366@MAILBOX.LASP.colorado.edu>, Message-ID: <8D5C1B82EA40014E8B222E92B9076325021358774368@MAILBOX.LASP.colorado.edu> Hi Utkarsh, I am trying to get this to work. I am trying it on 4.1 currently, as I have not yet compiled against 4.2. When I try the code you gave me I get a segfault. I wasn't expecting it to work first try (as all I did was copy/paste and change the variable name to one in the table), but I didn't expect the segfault. The failure may be related to the fact that my table is a member of a multi-block... how do I address the specific block from the programmable filter? if you can advise, that would be great. -Josh ________________________________________ From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] Sent: Thursday, September 25, 2014 11:23 AM To: Joshua Murphy Cc: paraview at paraview.org Subject: Re: [Paraview] using calculator filter on a table? For now, with 4.2 RC1, stick to using "Programmable Filter" with "Script" as follows: expr = inputs[0].RowData["RTData"] * 2.0 output.RowData.append(expr, "result") If you can add a bug to the bug tracker for this, that'd be great too. Thanks Utkarsh On Thu, Sep 25, 2014 at 12:45 PM, Joshua Murphy wrote: > Hello all, > > Is there a way to use the Calculator filter on a table? > > My reader loads a bunch of auxiliary files that loads time-series information for a specific point (at a higher temporal resolution than the 3D model output). I need to be able to convert the units in the time series information with some simple calculations so that I can match the units of the remainder of my work. > > Is there a way to use the calculator filter to do this? It is greyed out when I have the table selected... Are there some other steps I need to do to make it work? > > Thanks, > Josh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From zjzhang at gmail.com Thu Sep 25 15:09:09 2014 From: zjzhang at gmail.com (Zhijun Zhang) Date: Thu, 25 Sep 2014 12:09:09 -0700 Subject: [Paraview] question about geometry caching Message-ID: Dear all: I have found a problem with geometry caching starting from version higher than the Paraview 4.1. In Paraview 4.1, this function work well. What I am trying to do is like this: 1. To display the deformation of a sequence of mesh model (*vtk files) under 20 time points. 2. In version 4.1, when the mesh sequence is opened, I can select edit->setting->animation->Cache Limit (in KBs) and set the value to be very big, e.g. 51024000. Then when I click the play and loop toolbar button, after 1 or 2 cycles, the mesh will be displayed very smoothly. However, in the Paraview4.1+ version, 1. In the setting menu, I can not find the animation directly. In the General tab, I tried to search "cache" in the blank, and I can see the animation again. 2. But when I still set it to the large value like mentioned above, the cache does not work. I would like to know if there is a solution for this? and did I set it correct to use cache function? Hope anybody can give me a quick solution. Thank you very much. regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.Murphy at lasp.colorado.edu Thu Sep 25 15:15:23 2014 From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy) Date: Thu, 25 Sep 2014 13:15:23 -0600 Subject: [Paraview] custom reader question regarding python access Message-ID: <8D5C1B82EA40014E8B222E92B9076325021358774369@MAILBOX.LASP.colorado.edu> Hi all, I am adding features to my custom reader, and I need some help. My reader does the following: 1) Reads the main time-dependent model data 2) Reads 0 or more non model-time dependent files that provide time series information specific points at high temporal resolution. Currently, I am reading the main model data as a structured grid on Port 0 and the time series files into a multi-block table on port 1. This works great, as far as it goes, but I cannot figure out how to access any of the port 1 information from within Python. Everytime I try to fetch data for the source, I get a vtkStructuredGrid structure, with no sign of the multi-block tables. Can someone give me some advice on how to go about accessing the port1 data from within python? Thanks, Josh From Joshua.Murphy at lasp.colorado.edu Thu Sep 25 18:18:26 2014 From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy) Date: Thu, 25 Sep 2014 16:18:26 -0600 Subject: [Paraview] using calculator filter on a table? In-Reply-To: References: <8D5C1B82EA40014E8B222E92B9076325021358774366@MAILBOX.LASP.colorado.edu>, Message-ID: <8D5C1B82EA40014E8B222E92B907632502135877436A@MAILBOX.LASP.colorado.edu> Hi Utkarsh, I have tried this once again in v4.2.0, and I am getting the same segfault. any thoughts? my input is a multi-block table... -Josh ________________________________________ From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] Sent: Thursday, September 25, 2014 11:23 AM To: Joshua Murphy Cc: paraview at paraview.org Subject: Re: [Paraview] using calculator filter on a table? For now, with 4.2 RC1, stick to using "Programmable Filter" with "Script" as follows: expr = inputs[0].RowData["RTData"] * 2.0 output.RowData.append(expr, "result") If you can add a bug to the bug tracker for this, that'd be great too. Thanks Utkarsh On Thu, Sep 25, 2014 at 12:45 PM, Joshua Murphy wrote: > Hello all, > > Is there a way to use the Calculator filter on a table? > > My reader loads a bunch of auxiliary files that loads time-series information for a specific point (at a higher temporal resolution than the 3D model output). I need to be able to convert the units in the time series information with some simple calculations so that I can match the units of the remainder of my work. > > Is there a way to use the calculator filter to do this? It is greyed out when I have the table selected... Are there some other steps I need to do to make it work? > > Thanks, > Josh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From fhsantanna at yahoo.com.br Thu Sep 25 18:25:55 2014 From: fhsantanna at yahoo.com.br (Fernando Hayashi Sant Anna) Date: Thu, 25 Sep 2014 15:25:55 -0700 Subject: [Paraview] 3d scatterplot Message-ID: <1411683955.18053.YahooMailNeo@web120003.mail.ne1.yahoo.com> Hi everyone. I am trying to make a 3D Scatterplot from a principal component analysis data. Above I present the general format of my cvs table: type,PC 1,PC 2,PC 3 s35,-1.1678,-0.81478,0.61832 s35,-0.54306,-0.52355,0.4743 s35,-1.4862,-0.67112,0.24996 s35,-1.5646,-0.43992,0.37869 s35,-3.6895,-0.3267,-0.90597 s35,-3.2705,-0.34452,-0.47978 s35,1.5185,-0.53932,0.57408 Bacillus,0.5931,0.25691,-0.47788 Bacillus,0.67359,-0.012615,-0.29663 Bacillus,0.80718,0.13031,-0.34567 Bacillus,1.0766,-0.052194,-0.36311 Bacillus,1.6975,-0.11165,-0.15835 Bacillus,0.44962,0.2936,-0.42939 Bacillus,1.3748,-0.0011358,-0.36139 Here is what I tried so far: I loaded the table and activated the filter "Table to points". For each axis (XYZ), I attributed a PC column ( X=PC1, Y=PC2 and Z=PC3). After clicking in "Split horizontal" and "3D view", I got a 3D scatterplot. The problem is that I can't color the points based on the variable "type". In properties, In the color scale editor I attributed each value ("type") to a color, but it is not dysplayed in the scatterplot. Do you know what can I do? Thanks in advance. Fernando Hayashi Sant'Anna Doutor em Biologia Celular e Molecular Instituto de Recursos Naturales y Agrobiolog?a de Sevilla Av. Reina Mercedes, 10. Sevilla, Espa?a. -------------- next part -------------- An HTML attachment was scrubbed... URL: From insley at anl.gov Thu Sep 25 19:08:10 2014 From: insley at anl.gov (Insley, Joseph A.) Date: Thu, 25 Sep 2014 23:08:10 +0000 Subject: [Paraview] custom reader question regarding python access In-Reply-To: <8D5C1B82EA40014E8B222E92B9076325021358774369@MAILBOX.LASP.colorado.edu> References: <8D5C1B82EA40014E8B222E92B9076325021358774369@MAILBOX.LASP.colorado.edu> Message-ID: <17AED6E6-C3BB-4AF2-B93F-4B383872728E@anl.gov> Josh, I had a similar issue a while back, where I had a custom reader with multiple outputs. In order to get access to output port 1 I ended up doing something along the lines of: fooFilter = servermanager.OutputPort(my_reader, 1) SetActiveSource(fooFilter) fooFilter.UpdatePipeline() # may not be required # to see the names of the point data arrays on this output port dataInfo = fooFilter.GetDataInformation() pointDataInfo = dataInfo.getPointDataInformation() numArrays = pointDataInfo.GetNumberOfArrays() for foo in range(numArrays): aName = pointDataInfo.GetArrayInformation(foo) print "name (", foo, "): ", aName (thanks to Utkarsh, who pointed me in the right direction when I was originally trying to do this) Hope this helps, joe =================================================== joseph a. insley insley at anl.gov argonne leadership computing facility (630) 252-5649 argonne national laboratory On Sep 25, 2014, at 2:15 PM, Joshua Murphy > wrote: Hi all, I am adding features to my custom reader, and I need some help. My reader does the following: 1) Reads the main time-dependent model data 2) Reads 0 or more non model-time dependent files that provide time series information specific points at high temporal resolution. Currently, I am reading the main model data as a structured grid on Port 0 and the time series files into a multi-block table on port 1. This works great, as far as it goes, but I cannot figure out how to access any of the port 1 information from within Python. Everytime I try to fetch data for the source, I get a vtkStructuredGrid structure, with no sign of the multi-block tables. Can someone give me some advice on how to go about accessing the port1 data from within python? Thanks, Josh _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruggiero.guida at gmail.com Fri Sep 26 00:44:17 2014 From: ruggiero.guida at gmail.com (Ruggiero Guida) Date: Fri, 26 Sep 2014 08:44:17 +0400 Subject: [Paraview] Fwd: VTK interpolation help In-Reply-To: References: Message-ID: Dear group, I hope I will be able to find an answer to my problem here. I am not sure I understand how the interpolation works. I have generated a VTK file (attached) and I am trying to visualizing it in Paraview. The data represent the solar radiation on the ground around various buildings. My algorithm calculates the radiation in each node of a constrained delauney triangulation. The plan is to visualize this in paraview to have a nice smooth fillled contour. The image I get though, does not make sense to me; it seems that paraview is interpolating only within the triangles and not in the x,y directions. Am I missing something? Thanks a lot for any help Ruggiero -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: view1.png Type: image/png Size: 59470 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: view2.png Type: image/png Size: 38961 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Area4_Scenario00-Baseline_InsolationMap_4138.vtk Type: application/octet-stream Size: 118518 bytes Desc: not available URL: From lifeandfree at gmail.com Fri Sep 26 06:57:47 2014 From: lifeandfree at gmail.com (=?UTF-8?B?0JjQu9GM0Y8g0KHRg9GF0LDRh9C10LI=?=) Date: Fri, 26 Sep 2014 16:57:47 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: thank you, ok. try to understand. I put the stable version and not the release candidate. But there are a few more questions. Do files are responsible for localization? I need to replace the language in the design parawiewweb. And the second. Is there a possibility of the file from which the object is loaded into the web, continuously read the data? That is to update the image in the browser loading new data, but this is not in the manual and automatic. Sincerely, Sukhachev Ilya! 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < sebastien.jourdain at kitware.com>: > The top bar is not green anymore. Try to replace the directory /lib, > /apps, /ext within the ParaView /www inside the directory you serve with > Apache. > Moreover, can you enable the development tools on your browser to see what > kind of error you got? > > Did you look also at the different types of logs? Apache, Launcher (see > config to know where you choose to put them). > That could also give you an idea on what went wrong. > > Seb > > On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? > wrote: > >> Hi, Sebastien >> >> Thank you. >> I just took advantage of this documentation and to deploy. >> I ran the script /data/pvw/bin/start.sh. >> But when entering the address: http://localhost/apps/Visualizer is only >> displayed only the green bar at the top of the window, and nothing more. >> That in this case? >> >> Sincerely, >> Sukhachev Ilya! >> >> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >> sebastien.jourdain at kitware.com>: >> >>> Moreover, the documentation that get's updated automatically can be >>> found at the following address. (Which might be more accurate.) >>> >>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>> >>> This is the one you find when you go on paraview.org and go to the >>> documentation section. >>> >>> Seb >>> >>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>> sebastien.jourdain at kitware.com> wrote: >>> >>>> Hi Sukhachev, >>>> >>>> The one thing that might not be explicit about the ubuntu_14_04 guide >>>> might be that the script "/data/pvw/bin/start.sh" should be launched >>>> with a DISPLAY setup. >>>> Otherwise, you will have to be more explicit on what you've done and >>>> what is not working. The log files usually helps to see what was skipped >>>> from the documentation. >>>> >>>> Seb >>>> >>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? >>>> wrote: >>>> >>>>> Good day! >>>>> Prompt please. >>>>> I used the instructions for deployment on Linux Ubuntu Paraviewweb ( >>>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>> (http: // localhost / apps / Visualizer /) >>>>> When deployment by using the ( >>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>> as 1 Ceci. >>>>> How do I get access to many jobs, and through the web? >>>>> Thank you >>>>> >>>>> Sincerely, >>>>> Sukhachev Ilya! >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >> >> >> -- >> ? ?????????, >> ??????? ????! >> +7 912 216 72 72 >> > > -- ? ?????????, ??????? ????! +7 912 216 72 72 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Sep 26 10:18:07 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 26 Sep 2014 10:18:07 -0400 Subject: [Paraview] 3d scatterplot In-Reply-To: <1411683955.18053.YahooMailNeo@web120003.mail.ne1.yahoo.com> References: <1411683955.18053.YahooMailNeo@web120003.mail.ne1.yahoo.com> Message-ID: ParaView currently only supports coloring with numerical values. I'd suggest adding another row to the CSV to map the "type" to integers and then use categorical colors [1] to label the colors appropriately. Utkarsh [1] http://www.kitware.com/blog/home/post/582 On Thu, Sep 25, 2014 at 6:25 PM, Fernando Hayashi Sant Anna wrote: > Hi everyone. > I am trying to make a 3D Scatterplot from a principal component analysis > data. > Above I present the general format of my cvs table: > > type,PC 1,PC 2,PC 3 > s35,-1.1678,-0.81478,0.61832 > s35,-0.54306,-0.52355,0.4743 > s35,-1.4862,-0.67112,0.24996 > s35,-1.5646,-0.43992,0.37869 > s35,-3.6895,-0.3267,-0.90597 > s35,-3.2705,-0.34452,-0.47978 > s35,1.5185,-0.53932,0.57408 > Bacillus,0.5931,0.25691,-0.47788 > Bacillus,0.67359,-0.012615,-0.29663 > Bacillus,0.80718,0.13031,-0.34567 > Bacillus,1.0766,-0.052194,-0.36311 > Bacillus,1.6975,-0.11165,-0.15835 > Bacillus,0.44962,0.2936,-0.42939 > Bacillus,1.3748,-0.0011358,-0.36139 > > Here is what I tried so far: > I loaded the table and activated the filter "Table to points". For each axis > (XYZ), I attributed a PC column ( X=PC1, Y=PC2 and Z=PC3). After clicking in > "Split horizontal" and "3D view", I got a 3D scatterplot. > The problem is that I can't color the points based on the variable "type". > In properties, In the color scale editor I attributed each value ("type") > to a color, but it is not dysplayed in the scatterplot. > Do you know what can I do? > > Thanks in advance. > > Fernando Hayashi Sant'Anna > Doutor em Biologia Celular e Molecular > Instituto de Recursos Naturales y Agrobiolog?a de Sevilla > Av. Reina Mercedes, 10. Sevilla, Espa?a. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From sebastien.jourdain at kitware.com Fri Sep 26 10:18:39 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Fri, 26 Sep 2014 08:18:39 -0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: ParaView 4.2 has been released, so that would be the latest stable version available. There is no localization per say but the filter names could be customized the way you want. For continuous live visualization it is possible but that will be a custom development. And for that you can contact Kitware for either a support contract (http://www.kitware.com/products/support.html) or an end-product development (http://www.kitware.com/products/consulting.html). Seb On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? wrote: > thank you, ok. try to understand. I put the stable version and not the > release candidate. > > But there are a few more questions. > Do files are responsible for localization? I need to replace the language in > the design parawiewweb. > And the second. Is there a possibility of the file from which the object is > loaded into the web, continuously read the data? That is to update the > image in the browser loading new data, but this is not in the manual and > automatic. > > Sincerely, > Sukhachev Ilya! > > > 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < > sebastien.jourdain at kitware.com>: > >> The top bar is not green anymore. Try to replace the directory /lib, >> /apps, /ext within the ParaView /www inside the directory you serve with >> Apache. >> Moreover, can you enable the development tools on your browser to see >> what kind of error you got? >> >> Did you look also at the different types of logs? Apache, Launcher (see >> config to know where you choose to put them). >> That could also give you an idea on what went wrong. >> >> Seb >> >> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? >> wrote: >> >>> Hi, Sebastien >>> >>> Thank you. >>> I just took advantage of this documentation and to deploy. >>> I ran the script /data/pvw/bin/start.sh. >>> But when entering the address: http://localhost/apps/Visualizer is only >>> displayed only the green bar at the top of the window, and nothing more. >>> That in this case? >>> >>> Sincerely, >>> Sukhachev Ilya! >>> >>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>> sebastien.jourdain at kitware.com>: >>> >>>> Moreover, the documentation that get's updated automatically can be >>>> found at the following address. (Which might be more accurate.) >>>> >>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>> >>>> This is the one you find when you go on paraview.org and go to the >>>> documentation section. >>>> >>>> Seb >>>> >>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>> sebastien.jourdain at kitware.com> wrote: >>>> >>>>> Hi Sukhachev, >>>>> >>>>> The one thing that might not be explicit about the ubuntu_14_04 guide >>>>> might be that the script "/data/pvw/bin/start.sh" should be launched >>>>> with a DISPLAY setup. >>>>> Otherwise, you will have to be more explicit on what you've done and >>>>> what is not working. The log files usually helps to see what was skipped >>>>> from the documentation. >>>>> >>>>> Seb >>>>> >>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? >>>>> wrote: >>>>> >>>>>> Good day! >>>>>> Prompt please. >>>>>> I used the instructions for deployment on Linux Ubuntu Paraviewweb ( >>>>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>>> (http: // localhost / apps / Visualizer /) >>>>>> When deployment by using the ( >>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>>> as 1 Ceci. >>>>>> How do I get access to many jobs, and through the web? >>>>>> Thank you >>>>>> >>>>>> Sincerely, >>>>>> Sukhachev Ilya! >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>> >>> >>> -- >>> ? ?????????, >>> ??????? ????! >>> +7 912 216 72 72 >>> >> >> > > > -- > ? ?????????, > ??????? ????! > +7 912 216 72 72 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerrit.laube at ufz.de Fri Sep 26 10:49:03 2014 From: gerrit.laube at ufz.de (Gerrit Laube) Date: Fri, 26 Sep 2014 16:49:03 +0200 Subject: [Paraview] Paraview-Wiki: OSMesa Message-ID: <54257CDF.2040409@ufz.de> Hi Paraview Users, developers or wiki-maintainers (whoever that is), not sure, who's editing the paraview-wiki, but I think, I came across a problematic statement on the OSMesa-page: here http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D in chapter "Configuring ParaView for use with OSMesa" it says: ... -DOPENGL_gl_LIBRARY=\"\" \ ... but here http://www.paraview.org/pipermail/paraview/2013-November/029961.html it says, that you should avoid empty quotes in this variable. I experienced similar problems and i think ... -DOPENGL_gl_LIBRARY= \ ... finally fixed it. You might want to correct or mention this issue in the wiki. Regards! Gerrit From kmorel at sandia.gov Fri Sep 26 11:01:57 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 26 Sep 2014 15:01:57 +0000 Subject: [Paraview] Fwd: VTK interpolation help Message-ID: Yes, ParaView will use the triangles to interpolate values between points. The interpolation you are getting is exactly as I would expect based on your data and topology. I'm not sure what you mean by "not [interpolating] in the x,y directions". The triangles are in the x-y plane and interpolation is happening in this x-y plane. Moving into guesswork, I am imagining that you are expecting a smooth and fairly straight contour at some distance from the buildings. The reason you don't see this is due to the representation in your data. I notice that your data contains only two values for "RadiationOnPerson." The value is either 0 or 205.7. Presumably there is some contour in space where this field discontinuously transitions from 0 to 205.7, but there is no way to accurately predict where that is from the data you are providing. Instead, ParaView is just linearly interpolating between these values, which is wrong but probably the best you can do with the data provided. The problem is made even worse by the irregular sampling of the field. -Ken From: Ruggiero Guida > Date: Thursday, September 25, 2014 at 10:44 PM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Fwd: VTK interpolation help Dear group, I hope I will be able to find an answer to my problem here. I am not sure I understand how the interpolation works. I have generated a VTK file (attached) and I am trying to visualizing it in Paraview. The data represent the solar radiation on the ground around various buildings. My algorithm calculates the radiation in each node of a constrained delauney triangulation. The plan is to visualize this in paraview to have a nice smooth fillled contour. The image I get though, does not make sense to me; it seems that paraview is interpolating only within the triangles and not in the x,y directions. Am I missing something? Thanks a lot for any help Ruggiero -------------- next part -------------- An HTML attachment was scrubbed... URL: From S.R.Kharche at exeter.ac.uk Fri Sep 26 13:19:15 2014 From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay) Date: Fri, 26 Sep 2014 17:19:15 +0000 Subject: [Paraview] PVBatch Message-ID: Dear All I am trying to visualise a series of VTK files using pvbatch and I get an error. I write VTK files with a header as ascii, and then data as a 32 bit int binary. I can visualise individual files. As there are many files, I would like to automate this process. To do so, I produce a pvsm file using ParaView interactively. To loop over the pvsm, I have constructed the following python script: from paraview.simple import * servermanager.LoadState("kuntest.pvsm") SetActiveView(GetRenderView()) for i in range(1,40, 3): print 'h%04d.vtk' % (i) FindSource("h0001.vtk").FileNames ='h%04d.vtk' % (i) WriteImage('h_%06d.png' % (i)) When I try to run the visualisation simulation by the command, I get an error that I do not understand: h0001.vtk Traceback (most recent call last): File "crn3d_color_sync_frames.py", line 7, in FindSource("h0001.vtk").FileNames ='h%04d.vtk' % (i) AttributeError: 'NoneType' object has no attribute 'FileNames' Can you comment? thanks Sanjay -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Fri Sep 26 14:26:11 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 26 Sep 2014 14:26:11 -0400 Subject: [Paraview] PVBatch In-Reply-To: References: Message-ID: > > FindSource("h0001.vtk").FileNames ='h%04d.vtk' % (i) > ... > AttributeError: 'NoneType' object has no attribute 'FileNames' Means that FindSource("h0001.vtk") returned none. Do a print GetSources() to see what it might be instead of "h0001.vtk". > Can you comment? > > thanks > Sanjay > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Fri Sep 26 14:43:43 2014 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 26 Sep 2014 11:43:43 -0700 Subject: [Paraview] Paraview-Wiki: OSMesa In-Reply-To: <54257CDF.2040409@ufz.de> References: <54257CDF.2040409@ufz.de> Message-ID: <5425B3DF.70004@lbl.gov> Hi Gerrit, The code on the Wiki has been tested with PV 4.0.0, but it sounds like it no longer works. The issue is that if you do not put *something in the GL library then CMake will fill it in with the system libGL. That is the wrong thing to do when using OSMesa and can lead to run time issues if you don't set LD_LIBRARY_PATH. In recent builds I've been putting libOSMesa in place of the empty string and that has worked. We can update the Wiki, however the real solution will be to remove linking of libGL and X11 libraries when using OSMesa. Burlen On 9/26/2014 7:49 AM, Gerrit Laube wrote: > Hi Paraview Users, developers or wiki-maintainers (whoever that is), > > not sure, who's editing the paraview-wiki, but I think, I came across > a problematic statement on the OSMesa-page: > > here > http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D > in chapter "Configuring ParaView for use with OSMesa" it says: > ... > -DOPENGL_gl_LIBRARY=\"\" \ > ... > but here > http://www.paraview.org/pipermail/paraview/2013-November/029961.html > it says, that you should avoid empty quotes in this variable. I > experienced similar problems and i think > ... > -DOPENGL_gl_LIBRARY= \ > ... > finally fixed it. You might want to correct or mention this issue in > the wiki. > > Regards! > > Gerrit > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From S.R.Kharche at exeter.ac.uk Fri Sep 26 14:44:54 2014 From: S.R.Kharche at exeter.ac.uk (Kharche, Sanjay) Date: Fri, 26 Sep 2014 18:44:54 +0000 Subject: [Paraview] PVBatch In-Reply-To: References: , Message-ID: Hi I just worked out what the problem was. One file should be used to set up the pvsm and not the complete data set. cheers Sanjay ________________________________ From: David E DeMarle [dave.demarle at kitware.com] Sent: 26 September 2014 19:26 To: Kharche, Sanjay Cc: paraview at paraview.org Subject: Re: [Paraview] PVBatch FindSource("h0001.vtk").FileNames ='h%04d.vtk' % (i) ... AttributeError: 'NoneType' object has no attribute 'FileNames' Means that FindSource("h0001.vtk") returned none. Do a print GetSources() to see what it might be instead of "h0001.vtk". Can you comment? thanks Sanjay _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From praveenn at nvidia.com Fri Sep 26 17:34:43 2014 From: praveenn at nvidia.com (Praveen Narayanan) Date: Fri, 26 Sep 2014 21:34:43 +0000 Subject: [Paraview] Sphere benchmark runs and max number of polygons Message-ID: Greetings There are two points that I would like to bring up. 1) Firstly, in Paraview 4/4.1, the accessing the attribute (servermanager.)fromGUI causing problems for me. https://github.com/Kitware/ParaView/blob/master/Wrapping/Python/paraview/benchmark.py In def __render(?), the attribute fromGUI is not part of server manager (replace with paraview.fromGUI to make it work). praveen at kakrafoon:~/projects/benchmark$ vglrun python Python 2.7.6 (default, Mar 22 2014, 22:59:56) [GCC 4.8.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from paraview import benchmark paraview version 4.0.1 >>> benchmark.run() ============================================================ display lists, no triangle strips, solid color Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/paraview/benchmark.py", line 628, in run results.append(__render(ss, v, title, nframes)) File "/usr/lib/python2.7/dist-packages/paraview/benchmark.py", line 592, in __render if not servermanager.fromGUI: AttributeError: 'module' object has no attribute 'fromGUI' 2) Secondly, the number of polygons maxes out to 2 million taking about 90 MB. Is there a flag to change the max buffer size? I would like to run a bigger problem running more number of polygons. I am running on an NVIDIA GTX Titan. Thanks Praveen ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ----------------------------------------------------------------------------------- From ruggiero.guida at gmail.com Sat Sep 27 07:41:13 2014 From: ruggiero.guida at gmail.com (Ruggiero Guida) Date: Sat, 27 Sep 2014 15:41:13 +0400 Subject: [Paraview] Fwd: VTK interpolation help In-Reply-To: References: Message-ID: Thanks Ken. Got it. It makes sense. It seems that the only way to improve the quality is to have a finer grid and a more detailed calculation of the amount of radiation (the previous image included only the direct). New images are at this link https://www.dropbox.com/s/z9m2nr7ybj5mqqp/finermesh.zip?dl=0 I was wondering whether there was a way to at least smooth the results (see other attached image). I have looked at the filters available, but there is no such thing. When I import these results onto StarCCM I definitely see a smoother interpolation. Thanks Ruggiero On 26 September 2014 19:01, Moreland, Kenneth wrote: > Yes, ParaView will use the triangles to interpolate values between > points. The interpolation you are getting is exactly as I would expect > based on your data and topology. I'm not sure what you mean by "not > [interpolating] in the x,y directions". The triangles are in the x-y plane > and interpolation is happening in this x-y plane. > > Moving into guesswork, I am imagining that you are expecting a smooth > and fairly straight contour at some distance from the buildings. The > reason you don't see this is due to the representation in your data. I > notice that your data contains only two values for "RadiationOnPerson." The > value is either 0 or 205.7. Presumably there is some contour in space where > this field discontinuously transitions from 0 to 205.7, but there is no way > to accurately predict where that is from the data you are providing. > Instead, ParaView is just linearly interpolating between these values, > which is wrong but probably the best you can do with the data provided. The > problem is made even worse by the irregular sampling of the field. > > -Ken > > From: Ruggiero Guida > Date: Thursday, September 25, 2014 at 10:44 PM > To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Fwd: VTK interpolation help > > Dear group, > > I hope I will be able to find an answer to my problem here. > > I am not sure I understand how the interpolation works. I have generated > a VTK file (attached) and I am trying to visualizing it in Paraview. The > data represent the solar radiation on the ground around various buildings. > > My algorithm calculates the radiation in each node of a constrained > delauney triangulation. The plan is to visualize this in paraview to have a > nice smooth fillled contour. > > The image I get though, does not make sense to me; it seems that > paraview is interpolating only within the triangles and not in the x,y > directions. Am I missing something? > > Thanks a lot for any help > Ruggiero > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fraser.callaghan at sydney.edu.au Sat Sep 27 08:10:48 2014 From: fraser.callaghan at sydney.edu.au (Fraser Callaghan) Date: Sat, 27 Sep 2014 12:10:48 +0000 Subject: [Paraview] python programmable filter via xml with multiple input Message-ID: <220BE31773B69D4C985CA5660D992DB16D5BF8CB@ex-mbx-pro-03> Hi, I am able to run a python programmable filter accessing multiple inputs selected from the pipe line e.g: # numInputs = self.GetNumberOfInputConnections(0) for i in range(numInputs): print self.GetInputDataObject(0,i).GetNumberOfPoints() ## I am able to use the xml format to define multiple inputs in a cleaner way, but can not access the input data (example below). Changing "command" value does not help. How should I be accessing the inputs available from the xml setup? Thanks for the help, Fraser xml file: Input data 0. Input data 1 This property contains the text of a python program that the programmable source runs. Error on loading: ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkAlgorithm.cxx, line 893 vtkPythonProgrammableFilter (0x56aff30): Attempt to connect input port index 1 for an algorithm with 1 input ports. From bwvb at xs4all.nl Sat Sep 27 09:31:25 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Sat, 27 Sep 2014 15:31:25 +0200 Subject: [Paraview] HOWto create / extend sources? Message-ID: <5426BC2D.7000505@xs4all.nl> Hello, I just can;'t figure out how how to do the following in Paraview (programmatically, that is. I'm writing a new C++plugin). I found description/examples of how to create youre own reader, writer, filter. But what about a new Source? In particular: a) How to create a new source ("MyNewSource") b) How can I extend an existing source (box, sphere, etc.) with new properties and methods ("MyBox, "MySphere"). Any help or suggestions are greatly appreciated. Kind Regards, Bertwim From w.h.greene at gmail.com Sun Sep 28 09:18:52 2014 From: w.h.greene at gmail.com (Bill Greene) Date: Sun, 28 Sep 2014 09:18:52 -0400 Subject: [Paraview] Failure plotting cell labels Message-ID: I'm trying to plot Cell labels in Paraview 4.1.0 by defining a string array of cell data. However, I get an error in Find Data dialog when I try to select the cells. This very simple vtu file demonstrates the problem. Interestingly, when I attach a string array as point data in essentially the same way as I add the cell data, I don't have any problems plotting Point labels. If someone can tell me what I'm doing wrong, I would be most appreciative. Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test.vtu Type: application/octet-stream Size: 1132 bytes Desc: not available URL: From lifeandfree at gmail.com Mon Sep 29 00:30:15 2014 From: lifeandfree at gmail.com (=?UTF-8?B?0JjQu9GM0Y8g0KHRg9GF0LDRh9C10LI=?=) Date: Mon, 29 Sep 2014 10:30:15 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Good day. Thank you. You may be able to explain. What kind of filter is it? Ilya 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < sebastien.jourdain at kitware.com>: > ParaView 4.2 has been released, so that would be the latest stable version > available. > There is no localization per say but the filter names could be customized > the way you want. > > For continuous live visualization it is possible but that will be a custom > development. And for that you can contact Kitware for either a support > contract (http://www.kitware.com/products/support.html) or an end-product > development (http://www.kitware.com/products/consulting.html). > > Seb > > On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? > wrote: > >> thank you, ok. try to understand. I put the stable version and not the >> release candidate. >> >> But there are a few more questions. >> Do files are responsible for localization? I need to replace the language in >> the design parawiewweb. >> And the second. Is there a possibility of the file from which the object is >> loaded into the web, continuously read the data? That is to update the >> image in the browser loading new data, but this is not in the manual and >> automatic. >> >> Sincerely, >> Sukhachev Ilya! >> >> >> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >> sebastien.jourdain at kitware.com>: >> >>> The top bar is not green anymore. Try to replace the directory /lib, >>> /apps, /ext within the ParaView /www inside the directory you serve with >>> Apache. >>> Moreover, can you enable the development tools on your browser to see >>> what kind of error you got? >>> >>> Did you look also at the different types of logs? Apache, Launcher (see >>> config to know where you choose to put them). >>> That could also give you an idea on what went wrong. >>> >>> Seb >>> >>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? >>> wrote: >>> >>>> Hi, Sebastien >>>> >>>> Thank you. >>>> I just took advantage of this documentation and to deploy. >>>> I ran the script /data/pvw/bin/start.sh. >>>> But when entering the address: http://localhost/apps/Visualizer is >>>> only displayed only the green bar at the top of the window, and >>>> nothing more. >>>> That in this case? >>>> >>>> Sincerely, >>>> Sukhachev Ilya! >>>> >>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>> sebastien.jourdain at kitware.com>: >>>> >>>>> Moreover, the documentation that get's updated automatically can be >>>>> found at the following address. (Which might be more accurate.) >>>>> >>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>> >>>>> This is the one you find when you go on paraview.org and go to the >>>>> documentation section. >>>>> >>>>> Seb >>>>> >>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>> sebastien.jourdain at kitware.com> wrote: >>>>> >>>>>> Hi Sukhachev, >>>>>> >>>>>> The one thing that might not be explicit about the ubuntu_14_04 guide >>>>>> might be that the script "/data/pvw/bin/start.sh" should be launched >>>>>> with a DISPLAY setup. >>>>>> Otherwise, you will have to be more explicit on what you've done and >>>>>> what is not working. The log files usually helps to see what was skipped >>>>>> from the documentation. >>>>>> >>>>>> Seb >>>>>> >>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? >>>>> > wrote: >>>>>> >>>>>>> Good day! >>>>>>> Prompt please. >>>>>>> I used the instructions for deployment on Linux Ubuntu Paraviewweb ( >>>>>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>>>> (http: // localhost / apps / Visualizer /) >>>>>>> When deployment by using the ( >>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>>>> as 1 Ceci. >>>>>>> How do I get access to many jobs, and through the web? >>>>>>> Thank you >>>>>>> >>>>>>> Sincerely, >>>>>>> Sukhachev Ilya! >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> ? ?????????, >>>> ??????? ????! >>>> +7 912 216 72 72 >>>> >>> >>> >> >> >> -- >> ? ?????????, >> ??????? ????! >> +7 912 216 72 72 >> > > -- ? ?????????, ??????? ????! +7 912 216 72 72 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lifeandfree at gmail.com Mon Sep 29 03:43:11 2014 From: lifeandfree at gmail.com (=?UTF-8?B?0JjQu9GM0Y8g0KHRg9GF0LDRh9C10LI=?=) Date: Mon, 29 Sep 2014 13:43:11 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: And there is another question. Deployed software. I go to http://localhost/apps/Visualizer /. As a result, I see only the inscription ParaViewWeb and flailing wheel. And he gave me a list of errors in the console: Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1439, in dataReceived finishCallback(data[contentLength:]) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1668, in _finishRequestBody self.allContentReceived() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1731, in allContentReceived req.requestReceived(command, path, version) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 827, in requestReceived self.process() --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 189, in process self.render(resrc) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 238, in render body = resrc.render(self) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", line 250, in render return m(request) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 399, in render_POST session = self.session_manager.createSession(payload) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 182, in createSession options['cmd'] = replaceList(self.config['apps'][options['application']]['cmd'], [options, self.config['properties']]) exceptions.KeyError: u'visualizer' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 321, in processingFailed % webutil.formatFailure(reason)) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", line 425, in formatFailure flattenString(None, FailureElement(myFailure)).addBoth(result.append) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 420, in flattenString d = flatten(request, root, io.write) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 402, in flatten _writeFlattenedData(state, write, result) --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 359, in _writeFlattenedData element = state.next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 326, in _flattenTree raise FlattenerError(e, roots, extract_tb(exc_info()[2])) twisted.web.error.FlattenerError: Exception while flattening: File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 317, in _flattenTree element = stack[-1].next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 286, in _flattenElement result = root.render(request) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", line 184, in render return loader.load() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 465, in load self._loadedTemplate = self._loadDoc() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 446, in _loadDoc f = self._path.open('r') File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", line 828, in open return open(self.path, mode + 'b') IOError: [Errno 2] No such file or directory: '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1439, in dataReceived finishCallback(data[contentLength:]) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1668, in _finishRequestBody self.allContentReceived() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1731, in allContentReceived req.requestReceived(command, path, version) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 827, in requestReceived self.process() --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 189, in process self.render(resrc) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 238, in render body = resrc.render(self) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", line 250, in render return m(request) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 399, in render_POST session = self.session_manager.createSession(payload) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 182, in createSession options['cmd'] = replaceList(self.config['apps'][options['application']]['cmd'], [options, self.config['properties']]) exceptions.KeyError: u'visualizer' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 321, in processingFailed % webutil.formatFailure(reason)) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", line 425, in formatFailure flattenString(None, FailureElement(myFailure)).addBoth(result.append) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 420, in flattenString d = flatten(request, root, io.write) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 402, in flatten _writeFlattenedData(state, write, result) --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 359, in _writeFlattenedData element = state.next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 326, in _flattenTree raise FlattenerError(e, roots, extract_tb(exc_info()[2])) twisted.web.error.FlattenerError: Exception while flattening: File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 317, in _flattenTree element = stack[-1].next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 286, in _flattenElement result = root.render(request) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", line 184, in render return loader.load() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 465, in load self._loadedTemplate = self._loadDoc() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 446, in _loadDoc f = self._path.open('r') File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", line 828, in open return open(self.path, mode + 'b') IOError: [Errno 2] No such file or directory: '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1439, in dataReceived finishCallback(data[contentLength:]) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1668, in _finishRequestBody self.allContentReceived() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1731, in allContentReceived req.requestReceived(command, path, version) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 827, in requestReceived self.process() --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 189, in process self.render(resrc) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 238, in render body = resrc.render(self) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", line 250, in render return m(request) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 399, in render_POST session = self.session_manager.createSession(payload) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 182, in createSession options['cmd'] = replaceList(self.config['apps'][options['application']]['cmd'], [options, self.config['properties']]) exceptions.KeyError: u'visualizer' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 321, in processingFailed % webutil.formatFailure(reason)) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", line 425, in formatFailure flattenString(None, FailureElement(myFailure)).addBoth(result.append) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 420, in flattenString d = flatten(request, root, io.write) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 402, in flatten _writeFlattenedData(state, write, result) --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 359, in _writeFlattenedData element = state.next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 326, in _flattenTree raise FlattenerError(e, roots, extract_tb(exc_info()[2])) twisted.web.error.FlattenerError: Exception while flattening: File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 317, in _flattenTree element = stack[-1].next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 286, in _flattenElement result = root.render(request) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", line 184, in render return loader.load() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 465, in load self._loadedTemplate = self._loadDoc() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 446, in _loadDoc f = self._path.open('r') File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", line 828, in open return open(self.path, mode + 'b') IOError: [Errno 2] No such file or directory: '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1439, in dataReceived finishCallback(data[contentLength:]) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1668, in _finishRequestBody self.allContentReceived() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1731, in allContentReceived req.requestReceived(command, path, version) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 827, in requestReceived self.process() --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 189, in process self.render(resrc) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 238, in render body = resrc.render(self) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", line 250, in render return m(request) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 399, in render_POST session = self.session_manager.createSession(payload) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 182, in createSession options['cmd'] = replaceList(self.config['apps'][options['application']]['cmd'], [options, self.config['properties']]) exceptions.KeyError: u'visualizer' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 321, in processingFailed % webutil.formatFailure(reason)) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", line 425, in formatFailure flattenString(None, FailureElement(myFailure)).addBoth(result.append) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 420, in flattenString d = flatten(request, root, io.write) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 402, in flatten _writeFlattenedData(state, write, result) --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 359, in _writeFlattenedData element = state.next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 326, in _flattenTree raise FlattenerError(e, roots, extract_tb(exc_info()[2])) twisted.web.error.FlattenerError: Exception while flattening: File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 317, in _flattenTree element = stack[-1].next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 286, in _flattenElement result = root.render(request) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", line 184, in render return loader.load() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 465, in load self._loadedTemplate = self._loadDoc() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 446, in _loadDoc f = self._path.open('r') File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", line 828, in open return open(self.path, mode + 'b') IOError: [Errno 2] No such file or directory: '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1439, in dataReceived finishCallback(data[contentLength:]) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1668, in _finishRequestBody self.allContentReceived() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1731, in allContentReceived req.requestReceived(command, path, version) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 827, in requestReceived self.process() --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 189, in process self.render(resrc) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 238, in render body = resrc.render(self) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", line 250, in render return m(request) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 399, in render_POST session = self.session_manager.createSession(payload) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 182, in createSession options['cmd'] = replaceList(self.config['apps'][options['application']]['cmd'], [options, self.config['properties']]) exceptions.KeyError: u'visualizer' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 321, in processingFailed % webutil.formatFailure(reason)) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", line 425, in formatFailure flattenString(None, FailureElement(myFailure)).addBoth(result.append) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 420, in flattenString d = flatten(request, root, io.write) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 402, in flatten _writeFlattenedData(state, write, result) --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 359, in _writeFlattenedData element = state.next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 326, in _flattenTree raise FlattenerError(e, roots, extract_tb(exc_info()[2])) twisted.web.error.FlattenerError: Exception while flattening: File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 317, in _flattenTree element = stack[-1].next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 286, in _flattenElement result = root.render(request) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", line 184, in render return loader.load() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 465, in load self._loadedTemplate = self._loadDoc() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 446, in _loadDoc f = self._path.open('r') File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", line 828, in open return open(self.path, mode + 'b') IOError: [Errno 2] No such file or directory: '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1439, in dataReceived finishCallback(data[contentLength:]) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1668, in _finishRequestBody self.allContentReceived() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1731, in allContentReceived req.requestReceived(command, path, version) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 827, in requestReceived self.process() --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 189, in process self.render(resrc) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 238, in render body = resrc.render(self) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", line 250, in render return m(request) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 399, in render_POST session = self.session_manager.createSession(payload) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 182, in createSession options['cmd'] = replaceList(self.config['apps'][options['application']]['cmd'], [options, self.config['properties']]) exceptions.KeyError: u'visualizer' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 321, in processingFailed % webutil.formatFailure(reason)) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", line 425, in formatFailure flattenString(None, FailureElement(myFailure)).addBoth(result.append) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 420, in flattenString d = flatten(request, root, io.write) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 402, in flatten _writeFlattenedData(state, write, result) --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 359, in _writeFlattenedData element = state.next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 326, in _flattenTree raise FlattenerError(e, roots, extract_tb(exc_info()[2])) twisted.web.error.FlattenerError: Exception while flattening: File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 317, in _flattenTree element = stack[-1].next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 286, in _flattenElement result = root.render(request) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", line 184, in render return loader.load() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 465, in load self._loadedTemplate = self._loadDoc() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 446, in _loadDoc f = self._path.open('r') File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", line 828, in open return open(self.path, mode + 'b') IOError: [Errno 2] No such file or directory: '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1439, in dataReceived finishCallback(data[contentLength:]) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1668, in _finishRequestBody self.allContentReceived() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 1731, in allContentReceived req.requestReceived(command, path, version) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", line 827, in requestReceived self.process() --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 189, in process self.render(resrc) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 238, in render body = resrc.render(self) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", line 250, in render return m(request) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 399, in render_POST session = self.session_manager.createSession(payload) File "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", line 182, in createSession options['cmd'] = replaceList(self.config['apps'][options['application']]['cmd'], [options, self.config['properties']]) exceptions.KeyError: u'visualizer' Unhandled Error Traceback (most recent call last): File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", line 321, in processingFailed % webutil.formatFailure(reason)) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", line 425, in formatFailure flattenString(None, FailureElement(myFailure)).addBoth(result.append) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 420, in flattenString d = flatten(request, root, io.write) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 402, in flatten _writeFlattenedData(state, write, result) --- --- File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 359, in _writeFlattenedData element = state.next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 326, in _flattenTree raise FlattenerError(e, roots, extract_tb(exc_info()[2])) twisted.web.error.FlattenerError: Exception while flattening: File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 317, in _flattenTree element = stack[-1].next() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", line 286, in _flattenElement result = root.render(request) File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", line 184, in render return loader.load() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 465, in load self._loadedTemplate = self._loadDoc() File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", line 446, in _loadDoc f = self._path.open('r') File "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", line 828, in open return open(self.path, mode + 'b') IOError: [Errno 2] No such file or directory: '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' In logs file error.log: [Mon Sep 29 13:34:03.884092 2014] [proxy_http:error] [pid 14562:tid 140533745776384] (20014)Internal error: [client 127.0.0.1:38924] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:03.905642 2014] [proxy_http:error] [pid 14562:tid 140533720598272] (20014)Internal error: [client 127.0.0.1:38923] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:03.908441 2014] [proxy_http:error] [pid 14563:tid 140533787739904] (20014)Internal error: [client 127.0.0.1:38925] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:03.923450 2014] [proxy_http:error] [pid 14563:tid 140533762561792] (20014)Internal error: [client 127.0.0.1:38926] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:03.925919 2014] [proxy_http:error] [pid 14563:tid 140533754169088] (20014)Internal error: [client 127.0.0.1:38922] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:03.928206 2014] [proxy_http:error] [pid 14563:tid 140533745776384] (20014)Internal error: [client 127.0.0.1:38921] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:03.930176 2014] [proxy_http:error] [pid 14563:tid 140533737383680] (20014)Internal error: [client 127.0.0.1:38933] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:03.930197 2014] [proxy:error] [pid 14563:tid 140533737383680] [client 127.0.0.1:38933] AH00898: Error reading from remote server returned by /paraview/, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:20.357181 2014] [proxy_http:error] [pid 14563:tid 140533787739904] (20014)Internal error: [client 127.0.0.1:38939] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:20.359293 2014] [proxy_http:error] [pid 14563:tid 140533762561792] (20014)Internal error: [client 127.0.0.1:38940] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:20.361335 2014] [proxy_http:error] [pid 14562:tid 140533829703424] (20014)Internal error: [client 127.0.0.1:38944] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:20.363796 2014] [proxy_http:error] [pid 14562:tid 140533854881536] (20014)Internal error: [client 127.0.0.1:38943] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:20.366176 2014] [proxy_http:error] [pid 14562:tid 140533821310720] (20014)Internal error: [client 127.0.0.1:38942] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:20.368434 2014] [proxy_http:error] [pid 14562:tid 140533804525312] (20014)Internal error: [client 127.0.0.1:38941] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:20.370937 2014] [proxy_http:error] [pid 14563:tid 140533754169088] (20014)Internal error: [client 127.0.0.1:38951] AH01102: error reading status line from remote server localhost:8080, referer: http://localhost/apps/Visualizer/ [Mon Sep 29 13:34:20.370960 2014] [proxy:error] [pid 14563:tid 140533754169088] [client 127.0.0.1:38951] AH00898: Error reading from remote server returned by /paraview/, referer: http://localhost/apps/Visualizer/ 2014-09-29 10:30 GMT+06:00 ???? ??????? : > Good day. > Thank you. > > You may be able to explain. What kind of filter is it? > > Ilya > > 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < > sebastien.jourdain at kitware.com>: > >> ParaView 4.2 has been released, so that would be the latest stable >> version available. >> There is no localization per say but the filter names could be customized >> the way you want. >> >> For continuous live visualization it is possible but that will be a >> custom development. And for that you can contact Kitware for either a >> support contract (http://www.kitware.com/products/support.html) or an >> end-product development (http://www.kitware.com/products/consulting.html >> ). >> >> Seb >> >> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? >> wrote: >> >>> thank you, ok. try to understand. I put the stable version and not the >>> release candidate. >>> >>> But there are a few more questions. >>> Do files are responsible for localization? I need to replace the >>> language in the design parawiewweb. >>> And the second. Is there a possibility of the file from which the object is >>> loaded into the web, continuously read the data? That is to update the >>> image in the browser loading new data, but this is not in the manual and >>> automatic. >>> >>> Sincerely, >>> Sukhachev Ilya! >>> >>> >>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>> sebastien.jourdain at kitware.com>: >>> >>>> The top bar is not green anymore. Try to replace the directory /lib, >>>> /apps, /ext within the ParaView /www inside the directory you serve with >>>> Apache. >>>> Moreover, can you enable the development tools on your browser to see >>>> what kind of error you got? >>>> >>>> Did you look also at the different types of logs? Apache, Launcher (see >>>> config to know where you choose to put them). >>>> That could also give you an idea on what went wrong. >>>> >>>> Seb >>>> >>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? >>>> wrote: >>>> >>>>> Hi, Sebastien >>>>> >>>>> Thank you. >>>>> I just took advantage of this documentation and to deploy. >>>>> I ran the script /data/pvw/bin/start.sh. >>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>> only displayed only the green bar at the top of the window, and >>>>> nothing more. >>>>> That in this case? >>>>> >>>>> Sincerely, >>>>> Sukhachev Ilya! >>>>> >>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>> sebastien.jourdain at kitware.com>: >>>>> >>>>>> Moreover, the documentation that get's updated automatically can be >>>>>> found at the following address. (Which might be more accurate.) >>>>>> >>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>> >>>>>> This is the one you find when you go on paraview.org and go to the >>>>>> documentation section. >>>>>> >>>>>> Seb >>>>>> >>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>> >>>>>>> Hi Sukhachev, >>>>>>> >>>>>>> The one thing that might not be explicit about the ubuntu_14_04 >>>>>>> guide might be that the script "/data/pvw/bin/start.sh" should be >>>>>>> launched with a DISPLAY setup. >>>>>>> Otherwise, you will have to be more explicit on what you've done and >>>>>>> what is not working. The log files usually helps to see what was skipped >>>>>>> from the documentation. >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>> lifeandfree at gmail.com> wrote: >>>>>>> >>>>>>>> Good day! >>>>>>>> Prompt please. >>>>>>>> I used the instructions for deployment on Linux Ubuntu Paraviewweb >>>>>>>> (http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>>>>> (http: // localhost / apps / Visualizer /) >>>>>>>> When deployment by using the ( >>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>>>>> as 1 Ceci. >>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>> Thank you >>>>>>>> >>>>>>>> Sincerely, >>>>>>>> Sukhachev Ilya! >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> ? ?????????, >>>>> ??????? ????! >>>>> +7 912 216 72 72 >>>>> >>>> >>>> >>> >>> >>> -- >>> ? ?????????, >>> ??????? ????! >>> +7 912 216 72 72 >>> >> >> > > > -- > ? ?????????, > ??????? ????! > +7 912 216 72 72 > -- ? ?????????, ??????? ????! +7 912 216 72 72 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Sep 29 08:46:12 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 29 Sep 2014 08:46:12 -0400 Subject: [Paraview] HOWto create / extend sources? In-Reply-To: <5426BC2D.7000505@xs4all.nl> References: <5426BC2D.7000505@xs4all.nl> Message-ID: > a) How to create a new source ("MyNewSource") You define the 'proxy' under the "sources" group, rather than filters. It will automatically show up in the Menu. Look at sources.xml under [1] to see other source proxy definitions. > b) How can I extend an existing source (box, sphere, etc.) with new > properties and methods ("MyBox, "MySphere"). Similar to the filters, you basically need to write a new VTK algorithm with these new methods. You can subclass the existing VTK source. Looking at sources.xml, you can find out which proxy using which VTK algorithm, e.g. "SphereSource" (labelled as "Sphere") uses "vtkSphereSource". After adding the methods on the VTK algorithm, next part is exposing those methods as properties using the XML. [1] https://github.com/Kitware/ParaView/tree/master/ParaViewCore/ServerManager/SMApplication/Resources > > Any help or suggestions are greatly appreciated. > > Kind Regards, > Bertwim > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Mon Sep 29 08:48:43 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 29 Sep 2014 08:48:43 -0400 Subject: [Paraview] python programmable filter via xml with multiple input In-Reply-To: <220BE31773B69D4C985CA5660D992DB16D5BF8CB@ex-mbx-pro-03> References: <220BE31773B69D4C985CA5660D992DB16D5BF8CB@ex-mbx-pro-03> Message-ID: In your example, your XML is setup to provide the inputs on multiple "ports", while you're code is expecting multiple "connections" on same port. Use the following script, instead. print self.GetInputDataObject(0, 0).GetNumberOfPoints() print self.GetInputDataObject(1, 0).GetNumberOfPoints() Utkarsh On Sat, Sep 27, 2014 at 8:10 AM, Fraser Callaghan wrote: > Hi, > > I am able to run a python programmable filter accessing multiple inputs selected from the pipe line e.g: > # > numInputs = self.GetNumberOfInputConnections(0) > for i in range(numInputs): > print self.GetInputDataObject(0,i).GetNumberOfPoints() > ## > > I am able to use the xml format to define multiple inputs in a cleaner way, but can not access the input data (example below). > Changing "command" value does not help. > How should I be accessing the inputs available from the xml setup? > > Thanks for the help, > Fraser > > xml file: > > > > > > long_help="long help." > short_help="short help."> > > > name="Input0" > port_index="0" > command="SetInputConnection"> > > > > > > > > > Input data 0. > > > > name="Input1" > port_index="1" > command="SetInputConnection"> > > > > > > > > > Input data 1 > > > > > name="Script" > command="SetScript" > number_of_elements="1" > default_values="print 'Filter Working' print self.GetInputDataObject(0,0) #prints polydata print self.GetInputDataObject(0,1) #prints None " > panel_visibility="advanced"> > > > > This property contains the text of a python program that > the programmable source runs. > > > > > > > > > > > Error on loading: > > ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkAlgorithm.cxx, line 893 > vtkPythonProgrammableFilter (0x56aff30): Attempt to connect input port index 1 for an algorithm with 1 input ports. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From dave.demarle at kitware.com Mon Sep 29 10:11:39 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 29 Sep 2014 10:11:39 -0400 Subject: [Paraview] Sphere benchmark runs and max number of polygons In-Reply-To: References: Message-ID: On Fri, Sep 26, 2014 at 5:34 PM, Praveen Narayanan wrote: > Greetings > > There are two points that I would like to bring up. > > 1) Firstly, in Paraview 4/4.1, the accessing the attribute > (servermanager.)fromGUI causing problems for me. > > > https://github.com/Kitware/ParaView/blob/master/Wrapping/Python/paraview/benchmark.py > > In def __render(?), the attribute fromGUI is not part of server manager > (replace with paraview.fromGUI to make it work). > > > praveen at kakrafoon:~/projects/benchmark$ vglrun python > Python 2.7.6 (default, Mar 22 2014, 22:59:56) > [GCC 4.8.2] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> from paraview import benchmark > paraview version 4.0.1 > >>> benchmark.run() > ============================================================ > display lists, no triangle strips, solid color > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python2.7/dist-packages/paraview/benchmark.py", line 628, > in run > results.append(__render(ss, v, title, nframes)) > File "/usr/lib/python2.7/dist-packages/paraview/benchmark.py", line 592, > in __render > if not servermanager.fromGUI: > AttributeError: 'module' object has no attribute 'fromGUI' > > > Thanks, I can patch that if you don't have the patience. See: http://www.paraview.org/Wiki/ParaView/Git/Develop for instructions. > 2) Secondly, the number of polygons maxes out to 2 million taking about 90 > MB. Is there a flag to change the max buffer size? > > I would like to run a bigger problem running more number of polygons. I am > running on an NVIDIA GTX Titan. > > I don't understand. What buffer do are you talking about? cheers, Thanks > Praveen > > ----------------------------------------------------------------------------------- > This email message is for the sole use of the intended recipient(s) and > may contain > confidential information. Any unauthorized review, use, disclosure or > distribution > is prohibited. If you are not the intended recipient, please contact the > sender by > reply email and destroy all copies of the original message. > > ----------------------------------------------------------------------------------- > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Mon Sep 29 10:54:58 2014 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Mon, 29 Sep 2014 08:54:58 -0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Can you share your launcher configuration file? It appears you may have no "visualizer" application command line configured. Cheers, Scott On Mon, Sep 29, 2014 at 1:43 AM, ???? ??????? wrote: > > And there is another question. > Deployed software. I go to http://localhost/apps/Visualizer /. As a > result, I see only the inscription ParaViewWeb and flailing wheel. And he > gave me a list of errors in the console: > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1439, in dataReceived > finishCallback(data[contentLength:]) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1668, in _finishRequestBody > self.allContentReceived() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1731, in allContentReceived > req.requestReceived(command, path, version) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 827, in requestReceived > self.process() > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 189, in process > self.render(resrc) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 238, in render > body = resrc.render(self) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", > line 250, in render > return m(request) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 399, in render_POST > session = self.session_manager.createSession(payload) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 182, in createSession > options['cmd'] = > replaceList(self.config['apps'][options['application']]['cmd'], [options, > self.config['properties']]) > exceptions.KeyError: u'visualizer' > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 321, in processingFailed > % webutil.formatFailure(reason)) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", > line 425, in formatFailure > flattenString(None, FailureElement(myFailure)).addBoth(result.append) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 420, in flattenString > d = flatten(request, root, io.write) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 402, in flatten > _writeFlattenedData(state, write, result) > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 359, in _writeFlattenedData > element = state.next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 326, in _flattenTree > raise FlattenerError(e, roots, extract_tb(exc_info()[2])) > twisted.web.error.FlattenerError: Exception while flattening: > > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 317, in _flattenTree > element = stack[-1].next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 286, in _flattenElement > result = root.render(request) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", > line 184, in render > return loader.load() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 465, in load > self._loadedTemplate = self._loadDoc() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 446, in _loadDoc > f = self._path.open('r') > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", > line 828, in open > return open(self.path, mode + 'b') > IOError: [Errno 2] No such file or directory: > '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' > > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1439, in dataReceived > finishCallback(data[contentLength:]) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1668, in _finishRequestBody > self.allContentReceived() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1731, in allContentReceived > req.requestReceived(command, path, version) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 827, in requestReceived > self.process() > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 189, in process > self.render(resrc) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 238, in render > body = resrc.render(self) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", > line 250, in render > return m(request) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 399, in render_POST > session = self.session_manager.createSession(payload) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 182, in createSession > options['cmd'] = > replaceList(self.config['apps'][options['application']]['cmd'], [options, > self.config['properties']]) > exceptions.KeyError: u'visualizer' > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 321, in processingFailed > % webutil.formatFailure(reason)) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", > line 425, in formatFailure > flattenString(None, FailureElement(myFailure)).addBoth(result.append) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 420, in flattenString > d = flatten(request, root, io.write) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 402, in flatten > _writeFlattenedData(state, write, result) > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 359, in _writeFlattenedData > element = state.next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 326, in _flattenTree > raise FlattenerError(e, roots, extract_tb(exc_info()[2])) > twisted.web.error.FlattenerError: Exception while flattening: > > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 317, in _flattenTree > element = stack[-1].next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 286, in _flattenElement > result = root.render(request) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", > line 184, in render > return loader.load() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 465, in load > self._loadedTemplate = self._loadDoc() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 446, in _loadDoc > f = self._path.open('r') > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", > line 828, in open > return open(self.path, mode + 'b') > IOError: [Errno 2] No such file or directory: > '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' > > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1439, in dataReceived > finishCallback(data[contentLength:]) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1668, in _finishRequestBody > self.allContentReceived() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1731, in allContentReceived > req.requestReceived(command, path, version) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 827, in requestReceived > self.process() > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 189, in process > self.render(resrc) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 238, in render > body = resrc.render(self) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", > line 250, in render > return m(request) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 399, in render_POST > session = self.session_manager.createSession(payload) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 182, in createSession > options['cmd'] = > replaceList(self.config['apps'][options['application']]['cmd'], [options, > self.config['properties']]) > exceptions.KeyError: u'visualizer' > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 321, in processingFailed > % webutil.formatFailure(reason)) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", > line 425, in formatFailure > flattenString(None, FailureElement(myFailure)).addBoth(result.append) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 420, in flattenString > d = flatten(request, root, io.write) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 402, in flatten > _writeFlattenedData(state, write, result) > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 359, in _writeFlattenedData > element = state.next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 326, in _flattenTree > raise FlattenerError(e, roots, extract_tb(exc_info()[2])) > twisted.web.error.FlattenerError: Exception while flattening: > > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 317, in _flattenTree > element = stack[-1].next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 286, in _flattenElement > result = root.render(request) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", > line 184, in render > return loader.load() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 465, in load > self._loadedTemplate = self._loadDoc() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 446, in _loadDoc > f = self._path.open('r') > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", > line 828, in open > return open(self.path, mode + 'b') > IOError: [Errno 2] No such file or directory: > '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' > > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1439, in dataReceived > finishCallback(data[contentLength:]) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1668, in _finishRequestBody > self.allContentReceived() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1731, in allContentReceived > req.requestReceived(command, path, version) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 827, in requestReceived > self.process() > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 189, in process > self.render(resrc) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 238, in render > body = resrc.render(self) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", > line 250, in render > return m(request) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 399, in render_POST > session = self.session_manager.createSession(payload) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 182, in createSession > options['cmd'] = > replaceList(self.config['apps'][options['application']]['cmd'], [options, > self.config['properties']]) > exceptions.KeyError: u'visualizer' > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 321, in processingFailed > % webutil.formatFailure(reason)) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", > line 425, in formatFailure > flattenString(None, FailureElement(myFailure)).addBoth(result.append) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 420, in flattenString > d = flatten(request, root, io.write) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 402, in flatten > _writeFlattenedData(state, write, result) > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 359, in _writeFlattenedData > element = state.next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 326, in _flattenTree > raise FlattenerError(e, roots, extract_tb(exc_info()[2])) > twisted.web.error.FlattenerError: Exception while flattening: > > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 317, in _flattenTree > element = stack[-1].next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 286, in _flattenElement > result = root.render(request) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", > line 184, in render > return loader.load() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 465, in load > self._loadedTemplate = self._loadDoc() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 446, in _loadDoc > f = self._path.open('r') > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", > line 828, in open > return open(self.path, mode + 'b') > IOError: [Errno 2] No such file or directory: > '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' > > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1439, in dataReceived > finishCallback(data[contentLength:]) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1668, in _finishRequestBody > self.allContentReceived() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1731, in allContentReceived > req.requestReceived(command, path, version) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 827, in requestReceived > self.process() > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 189, in process > self.render(resrc) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 238, in render > body = resrc.render(self) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", > line 250, in render > return m(request) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 399, in render_POST > session = self.session_manager.createSession(payload) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 182, in createSession > options['cmd'] = > replaceList(self.config['apps'][options['application']]['cmd'], [options, > self.config['properties']]) > exceptions.KeyError: u'visualizer' > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 321, in processingFailed > % webutil.formatFailure(reason)) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", > line 425, in formatFailure > flattenString(None, FailureElement(myFailure)).addBoth(result.append) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 420, in flattenString > d = flatten(request, root, io.write) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 402, in flatten > _writeFlattenedData(state, write, result) > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 359, in _writeFlattenedData > element = state.next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 326, in _flattenTree > raise FlattenerError(e, roots, extract_tb(exc_info()[2])) > twisted.web.error.FlattenerError: Exception while flattening: > > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 317, in _flattenTree > element = stack[-1].next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 286, in _flattenElement > result = root.render(request) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", > line 184, in render > return loader.load() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 465, in load > self._loadedTemplate = self._loadDoc() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 446, in _loadDoc > f = self._path.open('r') > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", > line 828, in open > return open(self.path, mode + 'b') > IOError: [Errno 2] No such file or directory: > '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' > > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1439, in dataReceived > finishCallback(data[contentLength:]) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1668, in _finishRequestBody > self.allContentReceived() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1731, in allContentReceived > req.requestReceived(command, path, version) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 827, in requestReceived > self.process() > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 189, in process > self.render(resrc) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 238, in render > body = resrc.render(self) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", > line 250, in render > return m(request) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 399, in render_POST > session = self.session_manager.createSession(payload) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 182, in createSession > options['cmd'] = > replaceList(self.config['apps'][options['application']]['cmd'], [options, > self.config['properties']]) > exceptions.KeyError: u'visualizer' > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 321, in processingFailed > % webutil.formatFailure(reason)) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", > line 425, in formatFailure > flattenString(None, FailureElement(myFailure)).addBoth(result.append) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 420, in flattenString > d = flatten(request, root, io.write) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 402, in flatten > _writeFlattenedData(state, write, result) > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 359, in _writeFlattenedData > element = state.next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 326, in _flattenTree > raise FlattenerError(e, roots, extract_tb(exc_info()[2])) > twisted.web.error.FlattenerError: Exception while flattening: > > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 317, in _flattenTree > element = stack[-1].next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 286, in _flattenElement > result = root.render(request) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", > line 184, in render > return loader.load() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 465, in load > self._loadedTemplate = self._loadDoc() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 446, in _loadDoc > f = self._path.open('r') > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", > line 828, in open > return open(self.path, mode + 'b') > IOError: [Errno 2] No such file or directory: > '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' > > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1439, in dataReceived > finishCallback(data[contentLength:]) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1668, in _finishRequestBody > self.allContentReceived() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 1731, in allContentReceived > req.requestReceived(command, path, version) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", > line 827, in requestReceived > self.process() > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 189, in process > self.render(resrc) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 238, in render > body = resrc.render(self) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", > line 250, in render > return m(request) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 399, in render_POST > session = self.session_manager.createSession(payload) > File > "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", > line 182, in createSession > options['cmd'] = > replaceList(self.config['apps'][options['application']]['cmd'], [options, > self.config['properties']]) > exceptions.KeyError: u'visualizer' > Unhandled Error > Traceback (most recent call last): > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", > line 321, in processingFailed > % webutil.formatFailure(reason)) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", > line 425, in formatFailure > flattenString(None, FailureElement(myFailure)).addBoth(result.append) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 420, in flattenString > d = flatten(request, root, io.write) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 402, in flatten > _writeFlattenedData(state, write, result) > --- --- > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 359, in _writeFlattenedData > element = state.next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 326, in _flattenTree > raise FlattenerError(e, roots, extract_tb(exc_info()[2])) > twisted.web.error.FlattenerError: Exception while flattening: > > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 317, in _flattenTree > element = stack[-1].next() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", > line 286, in _flattenElement > result = root.render(request) > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", > line 184, in render > return loader.load() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 465, in load > self._loadedTemplate = self._loadDoc() > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", > line 446, in _loadDoc > f = self._path.open('r') > File > "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", > line 828, in open > return open(self.path, mode + 'b') > IOError: [Errno 2] No such file or directory: > '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' > > > In logs file error.log: > [Mon Sep 29 13:34:03.884092 2014] [proxy_http:error] [pid 14562:tid > 140533745776384] (20014)Internal error: [client 127.0.0.1:38924] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:03.905642 2014] [proxy_http:error] [pid 14562:tid > 140533720598272] (20014)Internal error: [client 127.0.0.1:38923] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:03.908441 2014] [proxy_http:error] [pid 14563:tid > 140533787739904] (20014)Internal error: [client 127.0.0.1:38925] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:03.923450 2014] [proxy_http:error] [pid 14563:tid > 140533762561792] (20014)Internal error: [client 127.0.0.1:38926] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:03.925919 2014] [proxy_http:error] [pid 14563:tid > 140533754169088] (20014)Internal error: [client 127.0.0.1:38922] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:03.928206 2014] [proxy_http:error] [pid 14563:tid > 140533745776384] (20014)Internal error: [client 127.0.0.1:38921] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:03.930176 2014] [proxy_http:error] [pid 14563:tid > 140533737383680] (20014)Internal error: [client 127.0.0.1:38933] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:03.930197 2014] [proxy:error] [pid 14563:tid > 140533737383680] [client 127.0.0.1:38933] AH00898: Error reading from > remote server returned by /paraview/, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:20.357181 2014] [proxy_http:error] [pid 14563:tid > 140533787739904] (20014)Internal error: [client 127.0.0.1:38939] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:20.359293 2014] [proxy_http:error] [pid 14563:tid > 140533762561792] (20014)Internal error: [client 127.0.0.1:38940] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:20.361335 2014] [proxy_http:error] [pid 14562:tid > 140533829703424] (20014)Internal error: [client 127.0.0.1:38944] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:20.363796 2014] [proxy_http:error] [pid 14562:tid > 140533854881536] (20014)Internal error: [client 127.0.0.1:38943] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:20.366176 2014] [proxy_http:error] [pid 14562:tid > 140533821310720] (20014)Internal error: [client 127.0.0.1:38942] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:20.368434 2014] [proxy_http:error] [pid 14562:tid > 140533804525312] (20014)Internal error: [client 127.0.0.1:38941] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:20.370937 2014] [proxy_http:error] [pid 14563:tid > 140533754169088] (20014)Internal error: [client 127.0.0.1:38951] AH01102: > error reading status line from remote server localhost:8080, referer: > http://localhost/apps/Visualizer/ > [Mon Sep 29 13:34:20.370960 2014] [proxy:error] [pid 14563:tid > 140533754169088] [client 127.0.0.1:38951] AH00898: Error reading from > remote server returned by /paraview/, referer: > http://localhost/apps/Visualizer/ > > > 2014-09-29 10:30 GMT+06:00 ???? ??????? : > >> Good day. >> Thank you. >> >> You may be able to explain. What kind of filter is it? >> >> Ilya >> >> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >> sebastien.jourdain at kitware.com>: >> >>> ParaView 4.2 has been released, so that would be the latest stable >>> version available. >>> There is no localization per say but the filter names could be >>> customized the way you want. >>> >>> For continuous live visualization it is possible but that will be a >>> custom development. And for that you can contact Kitware for either a >>> support contract (http://www.kitware.com/products/support.html) or an >>> end-product development (http://www.kitware.com/products/consulting.html >>> ). >>> >>> Seb >>> >>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? >>> wrote: >>> >>>> thank you, ok. try to understand. I put the stable version and not the >>>> release candidate. >>>> >>>> But there are a few more questions. >>>> Do files are responsible for localization? I need to replace the >>>> language in the design parawiewweb. >>>> And the second. Is there a possibility of the file from which the >>>> object is loaded into the web, continuously read the data? That is to >>>> update the image in the browser loading new data, but this is not in >>>> the manual and automatic. >>>> >>>> Sincerely, >>>> Sukhachev Ilya! >>>> >>>> >>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>> sebastien.jourdain at kitware.com>: >>>> >>>>> The top bar is not green anymore. Try to replace the directory /lib, >>>>> /apps, /ext within the ParaView /www inside the directory you serve with >>>>> Apache. >>>>> Moreover, can you enable the development tools on your browser to see >>>>> what kind of error you got? >>>>> >>>>> Did you look also at the different types of logs? Apache, Launcher >>>>> (see config to know where you choose to put them). >>>>> That could also give you an idea on what went wrong. >>>>> >>>>> Seb >>>>> >>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? >>>>> wrote: >>>>> >>>>>> Hi, Sebastien >>>>>> >>>>>> Thank you. >>>>>> I just took advantage of this documentation and to deploy. >>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>>> only displayed only the green bar at the top of the window, and >>>>>> nothing more. >>>>>> That in this case? >>>>>> >>>>>> Sincerely, >>>>>> Sukhachev Ilya! >>>>>> >>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>> sebastien.jourdain at kitware.com>: >>>>>> >>>>>>> Moreover, the documentation that get's updated automatically can be >>>>>>> found at the following address. (Which might be more accurate.) >>>>>>> >>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>> >>>>>>> This is the one you find when you go on paraview.org and go to the >>>>>>> documentation section. >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>> >>>>>>>> Hi Sukhachev, >>>>>>>> >>>>>>>> The one thing that might not be explicit about the ubuntu_14_04 >>>>>>>> guide might be that the script "/data/pvw/bin/start.sh" should be >>>>>>>> launched with a DISPLAY setup. >>>>>>>> Otherwise, you will have to be more explicit on what you've done >>>>>>>> and what is not working. The log files usually helps to see what >>>>>>>> was skipped from the documentation. >>>>>>>> >>>>>>>> Seb >>>>>>>> >>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>> >>>>>>>>> Good day! >>>>>>>>> Prompt please. >>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>> Paraviewweb (http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>>>>>> (http: // localhost / apps / Visualizer /) >>>>>>>>> When deployment by using the ( >>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>>>>>> as 1 Ceci. >>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>> Thank you >>>>>>>>> >>>>>>>>> Sincerely, >>>>>>>>> Sukhachev Ilya! >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Powered by www.kitware.com >>>>>>>>> >>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>> >>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>> >>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> ? ?????????, >>>>>> ??????? ????! >>>>>> +7 912 216 72 72 >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> ? ?????????, >>>> ??????? ????! >>>> +7 912 216 72 72 >>>> >>> >>> >> >> >> -- >> ? ?????????, >> ??????? ????! >> +7 912 216 72 72 >> > > > > -- > ? ?????????, > ??????? ????! > +7 912 216 72 72 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Mon Sep 29 11:14:50 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 29 Sep 2014 11:14:50 -0400 Subject: [Paraview] Fwd: Odd behavior of XDMF files with 3DCORECTMesh In-Reply-To: References: <541D674F.2020208@gmail.com> Message-ID: Just noticed I failed to reply-ALL. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 ---------- Forwarded message ---------- From: David E DeMarle Date: Wed, Sep 24, 2014 at 6:00 PM Subject: Re: [Paraview] Odd behavior of XDMF files with 3DCORECTMesh To: Armin Wehrfritz I think this is a very very old bug. For some reason, *RECTMesh (vtkRectilinearGrid) has been ijk instead of kji for as long as I can remember. *SMesh (vtkStructuredGrid) and *CoRectMesh (vtkImageData) are normal on the other hand. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Sat, Sep 20, 2014 at 7:38 AM, Armin Wehrfritz wrote: > Hi, > > I lately started to write my data in HDF5/XDMF files. This works so far > very well for unstructured data using TopologyType="Mixed" and Polygon > cells, but I have some trouble with structured grids. > > I attached a very simple VTK file, which is correctly visualized in > ParaView. More precisely, the DIMENSIONS keyword specifies the > dimensions in X Y Z direction and the SPACING and POINT_DATA keywords > are specified accordingly. > > Opening the VTK file in ParaView and exporting the data as XDMF leads to > an XDMF file with dimensions and the spacing is in reverse order (Z Y > X), where seemingly the data is written in the same order as in the VTK > file. > Is this intended or a bug? > Just to note, the data from the ParaView-created XDMF and the original > VTK file are displayed consistently. > > When I however manually converter the VTK to a XDMF file with > dimensions, spacing and data specified as in the VTK file, I get a > completely wrong representation in ParaView. > Seemingly, in the "Topology" element the "Dimensions" keyword specifies > the dimensions in Z Y X direction, which I thing is rather odd. > The whole thing gets then completely messed up when specifying the data. > > Am I doing something wrong when manually creating the XDMF file or is > this a bug? > > Best regards, > Armin > > > > -- > Armin Wehrfritz, Dipl.-Ing. (M.Sc.) > Aalto University, School of Engineering > Department of Energy Technology > PO Box 14300 > FI-00076 Aalto, Finland > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Sep 29 11:52:00 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 29 Sep 2014 11:52:00 -0400 Subject: [Paraview] ANN: ParaView 4.2.0 is available for download Message-ID: Folks, ParaView 4.2.0 is now available for download. Checkout to the release notes on the Kitware blog [1]. As always, we look forward to your feedback [2]. Also stay tuned to the Kitware Blog [3] for upcoming features and enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much more! - The ParaView team [1] http://www.kitware.com/blog/home/post/744 [2] http://paraview.uservoice.com [3] http://www.kitware.com/blog/ From kmorel at sandia.gov Mon Sep 29 12:06:51 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 29 Sep 2014 16:06:51 +0000 Subject: [Paraview] Change of default Scale Mode in Glyph filter Message-ID: In the new release of ParaView 4.2, I notice that the behavior of the Scale Mode property has changed a bit. The default used to be "vector" but now the default is "off." Is there a reason for the change? Also, the "Scalars" and "Vectors" attributes used to get disabled when they have no effect on the output. Now they never get grayed out. -Ken **** Kenneth Moreland *** Sandia National Laboratories *********** *** *** *** email: kmorel at sandia.gov ** *** ** phone: (505) 844-8919 *** web: http://www.sandia.gov/~kmorel -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Mon Sep 29 12:33:26 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 29 Sep 2014 16:33:26 +0000 Subject: [Paraview] Fwd: VTK interpolation help Message-ID: I couldn't see the files you posted to dropbox because they were deleted before I got a chance to see them. I also cannot even guess what Star-CCM is doing since I haven't seen that either. One thing you can try is to apply the loop subdivision filter. That filter subdivides triangles in a polygonal mesh and applies some nonlinear smoothing to the data. To use this filter, first apply the "Extract Surface" filter to your data (to convert it to polygons), and then apply "Loop Subdivision." -Ken From: Ruggiero Guida > Date: Saturday, September 27, 2014 at 5:41 AM To: Kenneth Moreland > Cc: "paraview at paraview.org" > Subject: [EXTERNAL] Re: [Paraview] Fwd: VTK interpolation help Thanks Ken. Got it. It makes sense. It seems that the only way to improve the quality is to have a finer grid and a more detailed calculation of the amount of radiation (the previous image included only the direct). New images are at this link https://www.dropbox.com/s/z9m2nr7ybj5mqqp/finermesh.zip?dl=0 I was wondering whether there was a way to at least smooth the results (see other attached image). I have looked at the filters available, but there is no such thing. When I import these results onto StarCCM I definitely see a smoother interpolation. Thanks Ruggiero On 26 September 2014 19:01, Moreland, Kenneth > wrote: Yes, ParaView will use the triangles to interpolate values between points. The interpolation you are getting is exactly as I would expect based on your data and topology. I'm not sure what you mean by "not [interpolating] in the x,y directions". The triangles are in the x-y plane and interpolation is happening in this x-y plane. Moving into guesswork, I am imagining that you are expecting a smooth and fairly straight contour at some distance from the buildings. The reason you don't see this is due to the representation in your data. I notice that your data contains only two values for "RadiationOnPerson." The value is either 0 or 205.7. Presumably there is some contour in space where this field discontinuously transitions from 0 to 205.7, but there is no way to accurately predict where that is from the data you are providing. Instead, ParaView is just linearly interpolating between these values, which is wrong but probably the best you can do with the data provided. The problem is made even worse by the irregular sampling of the field. -Ken From: Ruggiero Guida > Date: Thursday, September 25, 2014 at 10:44 PM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Fwd: VTK interpolation help Dear group, I hope I will be able to find an answer to my problem here. I am not sure I understand how the interpolation works. I have generated a VTK file (attached) and I am trying to visualizing it in Paraview. The data represent the solar radiation on the ground around various buildings. My algorithm calculates the radiation in each node of a constrained delauney triangulation. The plan is to visualize this in paraview to have a nice smooth fillled contour. The image I get though, does not make sense to me; it seems that paraview is interpolating only within the triangles and not in the x,y directions. Am I missing something? Thanks a lot for any help Ruggiero -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkxls23 at gmail.com Mon Sep 29 12:34:10 2014 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Mon, 29 Sep 2014 19:34:10 +0300 Subject: [Paraview] Odd behavior of XDMF files with 3DCORECTMesh In-Reply-To: References: <541D674F.2020208@gmail.com> Message-ID: <54298A02.7050900@gmail.com> Thanks for your reply! I'm not quite sure if that is really the problem, but it could be related. I still think there is something wrong in the XDMF class itself. I did some quick conversion tests for the the different mesh types using the example data from vtk.org/VTKData.git : VTKData/Data/SampleStructGrid.vtk: DATASET STRUCTURED_GRID DIMENSIONS 20 30 40 => VTKData/Data/RectGrid2.vtk: DATASET RECTILINEAR_GRID DIMENSIONS 47 33 11 => VTKData/Data/matrix.vtk DATASET STRUCTURED_POINTS DIMENSIONS 10 5 1 => In all cases, the XDMF class reads and writes the dimensions in the "wrong" way, i.e. ZYX instead of XYZ. Also the data arrays are read/written in ZYX order. The most important part for me to notice was that "ORIGIN_DXDYDZ" (*CoRectMesh) actually specifies the spacing in ZYX and not as the name suggests in XYZ. Whereas the data items in "VXVYVZ" ( *RectMesh) specify the XYZ data. In my opinion this is kind of a bit messy, but probably not really a bug. In my specific case, I have HDF5 files with data-arrays in XYZ order, i.e. z is iterated over the fastest, then y, and x is iterated over the slowest. After some trial and error I managed to create a valid .xmf file and read my data correctly into paraview, though the coordinate axes are still kind of wrong (ZYX instead of XYZ). Important to notice here was that the "Dimensions" in the Topology section need to match the data-structure in the HDF5 file. Thanks for your help! -Armin On 09/25/2014 01:00 AM, David E DeMarle wrote: > I think this is a very very old bug. > > For some reason, *RECTMesh (vtkRectilinearGrid) has been ijk instead of > kji for as long as I can remember. > > *SMesh (vtkStructuredGrid) and *CoRectMesh (vtkImageData) are normal on > the other hand. > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Sat, Sep 20, 2014 at 7:38 AM, Armin Wehrfritz > >> wrote: > > Hi, > > I lately started to write my data in HDF5/XDMF files. This works so far > very well for unstructured data using TopologyType="Mixed" and Polygon > cells, but I have some trouble with structured grids. > > I attached a very simple VTK file, which is correctly visualized in > ParaView. More precisely, the DIMENSIONS keyword specifies the > dimensions in X Y Z direction and the SPACING and POINT_DATA keywords > are specified accordingly. > > Opening the VTK file in ParaView and exporting the data as XDMF leads to > an XDMF file with dimensions and the spacing is in reverse order (Z Y > X), where seemingly the data is written in the same order as in the VTK > file. > Is this intended or a bug? > Just to note, the data from the ParaView-created XDMF and the original > VTK file are displayed consistently. > > When I however manually converter the VTK to a XDMF file with > dimensions, spacing and data specified as in the VTK file, I get a > completely wrong representation in ParaView. > Seemingly, in the "Topology" element the "Dimensions" keyword specifies > the dimensions in Z Y X direction, which I thing is rather odd. > The whole thing gets then completely messed up when specifying the data. > > Am I doing something wrong when manually creating the XDMF file or is > this a bug? > > Best regards, > Armin > > > > -- > Armin Wehrfritz, Dipl.-Ing. (M.Sc.) > Aalto University, School of Engineering > Department of Energy Technology > PO Box 14300 > FI-00076 Aalto, Finland > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > From Joshua.Murphy at lasp.colorado.edu Mon Sep 29 13:06:33 2014 From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy) Date: Mon, 29 Sep 2014 11:06:33 -0600 Subject: [Paraview] urgent: need python help Message-ID: <8D5C1B82EA40014E8B222E92B907632502135877436E@MAILBOX.LASP.colorado.edu> Hi all, This is fairly urgent, so any good pointers would be greatly appreciated! I am trying to (still) access the multi-block table in port 1 of my reader from python. Everything I have tried has returned the vtkSructuredGrid of port 0... Can someone in the know let me know how I can get at the data in port 1? I have tried: port1 = servermanager.OutputPort(reader,1) mb = servermanager.Fetch(port1) I have even tried doing this interactively: 1) select port 1 in the gui 2) port1 = GetActiveSource() 3) mb = servermanager.Fetch(port1) But It is returning a vtkStructuredGrid object that appears to be the data on Port 0. Port 1 should be a multiblock dataset with multiple vtkTables within. again, help would be greatly appreciated! -Josh From utkarsh.ayachit at kitware.com Mon Sep 29 13:18:04 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 29 Sep 2014 13:18:04 -0400 Subject: [Paraview] urgent: need python help In-Reply-To: <8D5C1B82EA40014E8B222E92B907632502135877436E@MAILBOX.LASP.colorado.edu> References: <8D5C1B82EA40014E8B222E92B907632502135877436E@MAILBOX.LASP.colorado.edu> Message-ID: Josh, Refer to [1]. You can pass an optional "idx" argument to Fetch to say which port to fetch from. >>> data = servermanager.Fetch(reader, idx=1) [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/paraview.servermanager.html#paraview.servermanager.Fetch On Mon, Sep 29, 2014 at 1:06 PM, Joshua Murphy wrote: > Hi all, > > This is fairly urgent, so any good pointers would be greatly appreciated! > > I am trying to (still) access the multi-block table in port 1 of my reader from python. Everything I have tried has returned the vtkSructuredGrid of port 0... > > Can someone in the know let me know how I can get at the data in port 1? > > I have tried: > > port1 = servermanager.OutputPort(reader,1) > mb = servermanager.Fetch(port1) > > I have even tried doing this interactively: > 1) select port 1 in the gui > 2) port1 = GetActiveSource() > 3) mb = servermanager.Fetch(port1) > > But It is returning a vtkStructuredGrid object that appears to be the data on Port 0. Port 1 should be a multiblock dataset with multiple vtkTables within. > > again, help would be greatly appreciated! > > -Josh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From Joshua.Murphy at lasp.colorado.edu Mon Sep 29 13:20:19 2014 From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy) Date: Mon, 29 Sep 2014 11:20:19 -0600 Subject: [Paraview] disregard - figured it out Message-ID: <8D5C1B82EA40014E8B222E92B907632502135877436F@MAILBOX.LASP.colorado.edu> Hi All, Disregard my last request for help. I figured it out. I wasn't calling Fetch with the idx=1 argument. -Josh From utkarsh.ayachit at kitware.com Mon Sep 29 13:41:46 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 29 Sep 2014 13:41:46 -0400 Subject: [Paraview] Change of default Scale Mode in Glyph filter In-Reply-To: References: Message-ID: On Mon, Sep 29, 2014 at 12:06 PM, Moreland, Kenneth wrote: > In the new release of ParaView 4.2, I notice that the behavior of the Scale > Mode property has changed a bit. The default used to be "vector" but now the > default is "off." Is there a reason for the change? Ken, the reason for this change was that if the "scale factor" was not setup properly, the glyphs would end up going crazy. e.g. + Open can.ex2, all variables, apply + Apply "Glyph" with everything default, except "Scale Mode" changed to "vector". + Now step forward 1 timestep, it will render insanely large glyphs. > Also, the "Scalars" and "Vectors" attributes used to get disabled when they > have no effect on the output. Now they never get grayed out. That's oversight. I updated the panel to not be a custom panel and forgot missed this enable/disable aspect. Mind adding a bug for that? Should be easy to fix. BTW, this version has new modes for seeding glyphs. The old version is still accessible as "Legacy Glyph", in case you want to do a comparison between the two. Utkarsh From kmorel at sandia.gov Mon Sep 29 14:30:15 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 29 Sep 2014 18:30:15 +0000 Subject: [Paraview] Change of default Scale Mode in Glyph filter Message-ID: >Ken, the reason for this change was that if the "scale factor" was not >setup properly, the glyphs would end up going crazy. e.g. >+ Open can.ex2, all variables, apply >+ Apply "Glyph" with everything default, except "Scale Mode" changed >to "vector". >+ Now step forward 1 timestep, it will render insanely large glyphs. I guess that makes sense. I'll just need to go back and modify the exercises in the tutorial to introduce the couple of steps to scale and rescale. -Ken From dan.lipsa at kitware.com Mon Sep 29 15:00:20 2014 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 29 Sep 2014 15:00:20 -0400 Subject: [Paraview] Catalyst question In-Reply-To: <50320452A334BD42A5EC72BAD214509916BFF0CE@MBX210.d.ethz.ch> References: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509916BFF0CE@MBX210.d.ethz.ch> Message-ID: Hi John, We just posted more information about Catalyst Live features that went into ParaView 4.2. http://www.kitware.com/blog/home/post/722 Regards, Dan On Tue, Aug 26, 2014 at 9:39 AM, Biddiscombe, John A. wrote: > Andy > > > > Thanks for the info, great news that the live stuff is ongoing. My current > test uses cxx only, so I didn?t play with the python pipelines and hadn?t > noticed the live viz option. I will experiment and get back to you. > > > > I saw a bunch of questions recently about doing GPU based stuff inside > catalyst and it is my aim to get my cuda/piston based renderers working > in-situ. I?ll let you know how I get on. > > If there are commits on branches you think I might want to test, please > say. > > > > thanks again > > > > JB > > > > > > > > > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com] > *Sent:* 26 August 2014 15:34 > *To:* Biddiscombe, John A. > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Catalyst question > > > > Hi John, > > This live capability is now available and recently has been cleaned up > quite a bit. There are still a couple more small changes that are waiting a > code review process before they go into the master branch. The user's guide > needs an update for a bunch of new information (live, catalyst editions, > zero-copy arrays) that's important for Catalyst. We're also doing some > preliminary testing with a newly developed ADIOS writer for better IO > performance as well. > > Getting back to the live viz stuff, when you create a Catalyst Python > script and export it using the wizard you'll have the option to enable live > viz (it's the same wizard page as the screenshot output specification). > Then, while your simulation is running use the Catalyst->Connect option to > connect. There are two tests (pv.CatalystLiveSetBreakpoint and > pvcs.CatalystLiveSetBreakpoint) that demonstrate the newly implemented live > functionality which now includes the option to set a breakpoint in the > simulation. > > If you get a chance to try it out, let me know what you think. > > Andy > > > > On Tue, Aug 26, 2014 at 3:40 AM, Biddiscombe, John A. > wrote: > > Dear Catalyst people > > > > I dragged out an old simulation demo I created some time ago and got it > working with paraview/catalyst from git master branch - my plan was to test > a live visualization of the simulation with the paraview GUI connected to > the simulation. I had thought this capability was now possible, but I have > not been following development closely and it looks like I was mistaken. > > > > Is it possible to visualize the simulation live - rather than just > generate images (which works fine). (I had a quick skim through the user > manual, but didn?t see this feature mentioned). > > > > 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 > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Mon Sep 29 16:14:14 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 29 Sep 2014 16:14:14 -0400 Subject: [Paraview] Failure plotting cell labels In-Reply-To: References: Message-ID: <20140929201414.GA28220@megas.kitwarein.com> On Sun, Sep 28, 2014 at 09:18:52 -0400, Bill Greene wrote: > I'm trying to plot Cell labels in Paraview 4.1.0 > by defining a string array of cell data. However, > I get an error in Find Data dialog when I try to select > the cells. This very simple vtu file demonstrates the > problem. > > Interestingly, when I attach a string array as point data > in essentially the same way as I add the cell data, I don't > have any problems plotting Point labels. > > If someone can tell me what I'm doing wrong, I would > be most appreciative. When selecting which labels to use, there's a "gear" icon towards the right of the dialog for settings. In there, it has entries for the format string to use for the labels. Currently, the default is: %-#6.3g which isn't that useful for string or integer arrays. Instead, if you use: %s it appears to work here. What we should do is change the default format string based on the array being used rather than just assuming everything is floating point data. I'll file a bug for it. It also appears that using an improper format string is an easy way to make ParaView crash; I'll track that down now. --Ben From leonardopessanha74 at gmail.com Mon Sep 29 18:07:20 2014 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Mon, 29 Sep 2014 19:07:20 -0300 Subject: [Paraview] Question about surfaces Message-ID: Hi, I have a CSV file with the collums x,y,z and temperature - the points are not equally spaced When i open this file and apply the table to points filter, i get the image "surface" attached, the points does not form a surface When i load a csv file with equally spaced points, i get the complete image represented as a surface like in the "surfacecorrect" file. I`ve tried the extract surface filter and it didn`t help me Can someone help me? Att, Leonardo Pessanha -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Surface.jpg Type: image/jpeg Size: 241358 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Surfacecorrect.jpg Type: image/jpeg Size: 40710 bytes Desc: not available URL: From fraser.callaghan at sydney.edu.au Mon Sep 29 18:35:14 2014 From: fraser.callaghan at sydney.edu.au (Fraser Callaghan) Date: Mon, 29 Sep 2014 22:35:14 +0000 Subject: [Paraview] python programmable filter via xml with multiple input In-Reply-To: References: <220BE31773B69D4C985CA5660D992DB16D5BF8CB@ex-mbx-pro-03> Message-ID: <220BE31773B69D4C985CA5660D992DB16D5BFAE6@ex-mbx-pro-03> Thanks for the clarification. I had tried this with the following error: vtkPythonProgrammableFilter (0x5458a60): Attempt to connect input port index 1 for an algorithm with 1 input ports. I gather that 'SetNumberOfInputPorts()' should be called in the constructor of the filter, which I gather is governed by the xml file? If so, how can I expose editing of the algorithm constructor via the xml file? Thanks, Fraser On Mon, 2014-09-29 at 08:48 -0400, Utkarsh Ayachit wrote: > In your example, your XML is setup to provide the inputs on multiple > "ports", while you're code is expecting multiple "connections" on same > port. Use the following script, instead. > > print self.GetInputDataObject(0, 0).GetNumberOfPoints() > print self.GetInputDataObject(1, 0).GetNumberOfPoints() > > Utkarsh > > On Sat, Sep 27, 2014 at 8:10 AM, Fraser Callaghan > wrote: > > Hi, > > > > I am able to run a python programmable filter accessing multiple inputs selected from the pipe line e.g: > > # > > numInputs = self.GetNumberOfInputConnections(0) > > for i in range(numInputs): > > print self.GetInputDataObject(0,i).GetNumberOfPoints() > > ## > > > > I am able to use the xml format to define multiple inputs in a cleaner way, but can not access the input data (example below). > > Changing "command" value does not help. > > How should I be accessing the inputs available from the xml setup? > > > > Thanks for the help, > > Fraser > > > > xml file: > > > > > > > > > > > > > long_help="long help." > > short_help="short help."> > > > > > > > name="Input0" > > port_index="0" > > command="SetInputConnection"> > > > > > > > > > > > > > > > > > > Input data 0. > > > > > > > > > name="Input1" > > port_index="1" > > command="SetInputConnection"> > > > > > > > > > > > > > > > > > > Input data 1 > > > > > > > > > > > name="Script" > > command="SetScript" > > number_of_elements="1" > > default_values="print 'Filter Working' print self.GetInputDataObject(0,0) #prints polydata print self.GetInputDataObject(0,1) #prints None " > > panel_visibility="advanced"> > > > > > > > > This property contains the text of a python program that > > the programmable source runs. > > > > > > > > > > > > > > > > > > > > > > Error on loading: > > > > ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkAlgorithm.cxx, line 893 > > vtkPythonProgrammableFilter (0x56aff30): Attempt to connect input port index 1 for an algorithm with 1 input ports. > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview -- Dr Fraser Callaghan Research Fellow Sydney Translational Imaging Laboratory Charles Perkins Centre The University of Sydney NSW 2006 Australia p: 02 8627 1700 e: fraser.callaghan at sydney.edu.au From bwvb at xs4all.nl Mon Sep 29 22:23:32 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 30 Sep 2014 04:23:32 +0200 Subject: [Paraview] HOWto create / extend sources? In-Reply-To: References: <5426BC2D.7000505@xs4all.nl> Message-ID: <542A1424.5020203@xs4all.nl> Utkarsh, Thanks for the pointers. I'll follow-up according your suggestions. I'm only recently doing stuff with ParaView (i.e. plugin-development). Please accept my compliments for the way you answer questions in this forum. The few answers you gave me + link to appropriate documentation have been very iseful! Regards, Bertwim On 09/29/2014 02:46 PM, Utkarsh Ayachit wrote: >> a) How to create a new source ("MyNewSource") > You define the 'proxy' under the "sources" group, rather than filters. > It will automatically show up in the Menu. Look at sources.xml under > [1] to see other source proxy definitions. > >> b) How can I extend an existing source (box, sphere, etc.) with new >> properties and methods ("MyBox, "MySphere"). > Similar to the filters, you basically need to write a new VTK > algorithm with these new methods. You can subclass the existing VTK > source. Looking at sources.xml, you can find out which proxy using > which VTK algorithm, e.g. "SphereSource" (labelled as "Sphere") uses > "vtkSphereSource". After adding the methods on the VTK algorithm, next > part is exposing those methods as properties using the XML. > > [1] https://github.com/Kitware/ParaView/tree/master/ParaViewCore/ServerManager/SMApplication/Resources > >> Any help or suggestions are greatly appreciated. >> >> Kind Regards, >> Bertwim >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From lifeandfree at gmail.com Mon Sep 29 23:36:10 2014 From: lifeandfree at gmail.com (Ilya Sukhachev) Date: Tue, 30 Sep 2014 09:36:10 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Good day! Yes, of course Attached. Also put the configuration file Apache. Ilya 2014-09-29 20:54 GMT+06:00 Scott Wittenburg : > Can you share your launcher configuration file? It appears you may have > no "visualizer" application command line configured. > > Cheers, > Scott > > > On Mon, Sep 29, 2014 at 1:43 AM, ???? ??????? > wrote: > >> >> And there is another question. >> Deployed software. I go to http://localhost/apps/Visualizer /. As a >> result, I see only the inscription ParaViewWeb and flailing wheel. And he >> gave me a list of errors in the console: >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1439, in dataReceived >> finishCallback(data[contentLength:]) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1668, in _finishRequestBody >> self.allContentReceived() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1731, in allContentReceived >> req.requestReceived(command, path, version) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 827, in requestReceived >> self.process() >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 189, in process >> self.render(resrc) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 238, in render >> body = resrc.render(self) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >> line 250, in render >> return m(request) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 399, in render_POST >> session = self.session_manager.createSession(payload) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 182, in createSession >> options['cmd'] = >> replaceList(self.config['apps'][options['application']]['cmd'], [options, >> self.config['properties']]) >> exceptions.KeyError: u'visualizer' >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 321, in processingFailed >> % webutil.formatFailure(reason)) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >> line 425, in formatFailure >> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 420, in flattenString >> d = flatten(request, root, io.write) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 402, in flatten >> _writeFlattenedData(state, write, result) >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 359, in _writeFlattenedData >> element = state.next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 326, in _flattenTree >> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >> twisted.web.error.FlattenerError: Exception while flattening: >> >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 317, in _flattenTree >> element = stack[-1].next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 286, in _flattenElement >> result = root.render(request) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >> line 184, in render >> return loader.load() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 465, in load >> self._loadedTemplate = self._loadDoc() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 446, in _loadDoc >> f = self._path.open('r') >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >> line 828, in open >> return open(self.path, mode + 'b') >> IOError: [Errno 2] No such file or directory: >> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >> >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1439, in dataReceived >> finishCallback(data[contentLength:]) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1668, in _finishRequestBody >> self.allContentReceived() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1731, in allContentReceived >> req.requestReceived(command, path, version) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 827, in requestReceived >> self.process() >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 189, in process >> self.render(resrc) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 238, in render >> body = resrc.render(self) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >> line 250, in render >> return m(request) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 399, in render_POST >> session = self.session_manager.createSession(payload) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 182, in createSession >> options['cmd'] = >> replaceList(self.config['apps'][options['application']]['cmd'], [options, >> self.config['properties']]) >> exceptions.KeyError: u'visualizer' >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 321, in processingFailed >> % webutil.formatFailure(reason)) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >> line 425, in formatFailure >> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 420, in flattenString >> d = flatten(request, root, io.write) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 402, in flatten >> _writeFlattenedData(state, write, result) >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 359, in _writeFlattenedData >> element = state.next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 326, in _flattenTree >> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >> twisted.web.error.FlattenerError: Exception while flattening: >> >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 317, in _flattenTree >> element = stack[-1].next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 286, in _flattenElement >> result = root.render(request) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >> line 184, in render >> return loader.load() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 465, in load >> self._loadedTemplate = self._loadDoc() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 446, in _loadDoc >> f = self._path.open('r') >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >> line 828, in open >> return open(self.path, mode + 'b') >> IOError: [Errno 2] No such file or directory: >> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >> >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1439, in dataReceived >> finishCallback(data[contentLength:]) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1668, in _finishRequestBody >> self.allContentReceived() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1731, in allContentReceived >> req.requestReceived(command, path, version) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 827, in requestReceived >> self.process() >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 189, in process >> self.render(resrc) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 238, in render >> body = resrc.render(self) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >> line 250, in render >> return m(request) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 399, in render_POST >> session = self.session_manager.createSession(payload) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 182, in createSession >> options['cmd'] = >> replaceList(self.config['apps'][options['application']]['cmd'], [options, >> self.config['properties']]) >> exceptions.KeyError: u'visualizer' >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 321, in processingFailed >> % webutil.formatFailure(reason)) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >> line 425, in formatFailure >> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 420, in flattenString >> d = flatten(request, root, io.write) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 402, in flatten >> _writeFlattenedData(state, write, result) >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 359, in _writeFlattenedData >> element = state.next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 326, in _flattenTree >> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >> twisted.web.error.FlattenerError: Exception while flattening: >> >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 317, in _flattenTree >> element = stack[-1].next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 286, in _flattenElement >> result = root.render(request) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >> line 184, in render >> return loader.load() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 465, in load >> self._loadedTemplate = self._loadDoc() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 446, in _loadDoc >> f = self._path.open('r') >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >> line 828, in open >> return open(self.path, mode + 'b') >> IOError: [Errno 2] No such file or directory: >> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >> >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1439, in dataReceived >> finishCallback(data[contentLength:]) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1668, in _finishRequestBody >> self.allContentReceived() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1731, in allContentReceived >> req.requestReceived(command, path, version) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 827, in requestReceived >> self.process() >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 189, in process >> self.render(resrc) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 238, in render >> body = resrc.render(self) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >> line 250, in render >> return m(request) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 399, in render_POST >> session = self.session_manager.createSession(payload) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 182, in createSession >> options['cmd'] = >> replaceList(self.config['apps'][options['application']]['cmd'], [options, >> self.config['properties']]) >> exceptions.KeyError: u'visualizer' >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 321, in processingFailed >> % webutil.formatFailure(reason)) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >> line 425, in formatFailure >> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 420, in flattenString >> d = flatten(request, root, io.write) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 402, in flatten >> _writeFlattenedData(state, write, result) >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 359, in _writeFlattenedData >> element = state.next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 326, in _flattenTree >> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >> twisted.web.error.FlattenerError: Exception while flattening: >> >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 317, in _flattenTree >> element = stack[-1].next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 286, in _flattenElement >> result = root.render(request) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >> line 184, in render >> return loader.load() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 465, in load >> self._loadedTemplate = self._loadDoc() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 446, in _loadDoc >> f = self._path.open('r') >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >> line 828, in open >> return open(self.path, mode + 'b') >> IOError: [Errno 2] No such file or directory: >> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >> >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1439, in dataReceived >> finishCallback(data[contentLength:]) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1668, in _finishRequestBody >> self.allContentReceived() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1731, in allContentReceived >> req.requestReceived(command, path, version) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 827, in requestReceived >> self.process() >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 189, in process >> self.render(resrc) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 238, in render >> body = resrc.render(self) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >> line 250, in render >> return m(request) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 399, in render_POST >> session = self.session_manager.createSession(payload) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 182, in createSession >> options['cmd'] = >> replaceList(self.config['apps'][options['application']]['cmd'], [options, >> self.config['properties']]) >> exceptions.KeyError: u'visualizer' >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 321, in processingFailed >> % webutil.formatFailure(reason)) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >> line 425, in formatFailure >> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 420, in flattenString >> d = flatten(request, root, io.write) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 402, in flatten >> _writeFlattenedData(state, write, result) >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 359, in _writeFlattenedData >> element = state.next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 326, in _flattenTree >> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >> twisted.web.error.FlattenerError: Exception while flattening: >> >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 317, in _flattenTree >> element = stack[-1].next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 286, in _flattenElement >> result = root.render(request) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >> line 184, in render >> return loader.load() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 465, in load >> self._loadedTemplate = self._loadDoc() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 446, in _loadDoc >> f = self._path.open('r') >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >> line 828, in open >> return open(self.path, mode + 'b') >> IOError: [Errno 2] No such file or directory: >> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >> >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1439, in dataReceived >> finishCallback(data[contentLength:]) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1668, in _finishRequestBody >> self.allContentReceived() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1731, in allContentReceived >> req.requestReceived(command, path, version) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 827, in requestReceived >> self.process() >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 189, in process >> self.render(resrc) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 238, in render >> body = resrc.render(self) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >> line 250, in render >> return m(request) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 399, in render_POST >> session = self.session_manager.createSession(payload) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 182, in createSession >> options['cmd'] = >> replaceList(self.config['apps'][options['application']]['cmd'], [options, >> self.config['properties']]) >> exceptions.KeyError: u'visualizer' >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 321, in processingFailed >> % webutil.formatFailure(reason)) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >> line 425, in formatFailure >> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 420, in flattenString >> d = flatten(request, root, io.write) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 402, in flatten >> _writeFlattenedData(state, write, result) >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 359, in _writeFlattenedData >> element = state.next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 326, in _flattenTree >> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >> twisted.web.error.FlattenerError: Exception while flattening: >> >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 317, in _flattenTree >> element = stack[-1].next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 286, in _flattenElement >> result = root.render(request) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >> line 184, in render >> return loader.load() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 465, in load >> self._loadedTemplate = self._loadDoc() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 446, in _loadDoc >> f = self._path.open('r') >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >> line 828, in open >> return open(self.path, mode + 'b') >> IOError: [Errno 2] No such file or directory: >> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >> >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1439, in dataReceived >> finishCallback(data[contentLength:]) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1668, in _finishRequestBody >> self.allContentReceived() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 1731, in allContentReceived >> req.requestReceived(command, path, version) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >> line 827, in requestReceived >> self.process() >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 189, in process >> self.render(resrc) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 238, in render >> body = resrc.render(self) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >> line 250, in render >> return m(request) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 399, in render_POST >> session = self.session_manager.createSession(payload) >> File >> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >> line 182, in createSession >> options['cmd'] = >> replaceList(self.config['apps'][options['application']]['cmd'], [options, >> self.config['properties']]) >> exceptions.KeyError: u'visualizer' >> Unhandled Error >> Traceback (most recent call last): >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >> line 321, in processingFailed >> % webutil.formatFailure(reason)) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >> line 425, in formatFailure >> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 420, in flattenString >> d = flatten(request, root, io.write) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 402, in flatten >> _writeFlattenedData(state, write, result) >> --- --- >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 359, in _writeFlattenedData >> element = state.next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 326, in _flattenTree >> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >> twisted.web.error.FlattenerError: Exception while flattening: >> >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 317, in _flattenTree >> element = stack[-1].next() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >> line 286, in _flattenElement >> result = root.render(request) >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >> line 184, in render >> return loader.load() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 465, in load >> self._loadedTemplate = self._loadDoc() >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >> line 446, in _loadDoc >> f = self._path.open('r') >> File >> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >> line 828, in open >> return open(self.path, mode + 'b') >> IOError: [Errno 2] No such file or directory: >> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >> >> >> In logs file error.log: >> [Mon Sep 29 13:34:03.884092 2014] [proxy_http:error] [pid 14562:tid >> 140533745776384] (20014)Internal error: [client 127.0.0.1:38924] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:03.905642 2014] [proxy_http:error] [pid 14562:tid >> 140533720598272] (20014)Internal error: [client 127.0.0.1:38923] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:03.908441 2014] [proxy_http:error] [pid 14563:tid >> 140533787739904] (20014)Internal error: [client 127.0.0.1:38925] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:03.923450 2014] [proxy_http:error] [pid 14563:tid >> 140533762561792] (20014)Internal error: [client 127.0.0.1:38926] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:03.925919 2014] [proxy_http:error] [pid 14563:tid >> 140533754169088] (20014)Internal error: [client 127.0.0.1:38922] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:03.928206 2014] [proxy_http:error] [pid 14563:tid >> 140533745776384] (20014)Internal error: [client 127.0.0.1:38921] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:03.930176 2014] [proxy_http:error] [pid 14563:tid >> 140533737383680] (20014)Internal error: [client 127.0.0.1:38933] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:03.930197 2014] [proxy:error] [pid 14563:tid >> 140533737383680] [client 127.0.0.1:38933] AH00898: Error reading from >> remote server returned by /paraview/, referer: >> http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:20.357181 2014] [proxy_http:error] [pid 14563:tid >> 140533787739904] (20014)Internal error: [client 127.0.0.1:38939] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:20.359293 2014] [proxy_http:error] [pid 14563:tid >> 140533762561792] (20014)Internal error: [client 127.0.0.1:38940] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:20.361335 2014] [proxy_http:error] [pid 14562:tid >> 140533829703424] (20014)Internal error: [client 127.0.0.1:38944] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:20.363796 2014] [proxy_http:error] [pid 14562:tid >> 140533854881536] (20014)Internal error: [client 127.0.0.1:38943] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:20.366176 2014] [proxy_http:error] [pid 14562:tid >> 140533821310720] (20014)Internal error: [client 127.0.0.1:38942] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:20.368434 2014] [proxy_http:error] [pid 14562:tid >> 140533804525312] (20014)Internal error: [client 127.0.0.1:38941] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:20.370937 2014] [proxy_http:error] [pid 14563:tid >> 140533754169088] (20014)Internal error: [client 127.0.0.1:38951] >> AH01102: error reading status line from remote server localhost:8080, >> referer: http://localhost/apps/Visualizer/ >> [Mon Sep 29 13:34:20.370960 2014] [proxy:error] [pid 14563:tid >> 140533754169088] [client 127.0.0.1:38951] AH00898: Error reading from >> remote server returned by /paraview/, referer: >> http://localhost/apps/Visualizer/ >> >> >> 2014-09-29 10:30 GMT+06:00 ???? ??????? : >> >>> Good day. >>> Thank you. >>> >>> You may be able to explain. What kind of filter is it? >>> >>> Ilya >>> >>> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >>> sebastien.jourdain at kitware.com>: >>> >>>> ParaView 4.2 has been released, so that would be the latest stable >>>> version available. >>>> There is no localization per say but the filter names could be >>>> customized the way you want. >>>> >>>> For continuous live visualization it is possible but that will be a >>>> custom development. And for that you can contact Kitware for either a >>>> support contract (http://www.kitware.com/products/support.html) or an >>>> end-product development ( >>>> http://www.kitware.com/products/consulting.html). >>>> >>>> Seb >>>> >>>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? >>>> wrote: >>>> >>>>> thank you, ok. try to understand. I put the stable version and not the >>>>> release candidate. >>>>> >>>>> But there are a few more questions. >>>>> Do files are responsible for localization? I need to replace the >>>>> language in the design parawiewweb. >>>>> And the second. Is there a possibility of the file from which the >>>>> object is loaded into the web, continuously read the data? That is to >>>>> update the image in the browser loading new data, but this is not in >>>>> the manual and automatic. >>>>> >>>>> Sincerely, >>>>> Sukhachev Ilya! >>>>> >>>>> >>>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>>> sebastien.jourdain at kitware.com>: >>>>> >>>>>> The top bar is not green anymore. Try to replace the directory /lib, >>>>>> /apps, /ext within the ParaView /www inside the directory you serve with >>>>>> Apache. >>>>>> Moreover, can you enable the development tools on your browser to see >>>>>> what kind of error you got? >>>>>> >>>>>> Did you look also at the different types of logs? Apache, Launcher >>>>>> (see config to know where you choose to put them). >>>>>> That could also give you an idea on what went wrong. >>>>>> >>>>>> Seb >>>>>> >>>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? >>>>>> wrote: >>>>>> >>>>>>> Hi, Sebastien >>>>>>> >>>>>>> Thank you. >>>>>>> I just took advantage of this documentation and to deploy. >>>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>>>> only displayed only the green bar at the top of the window, and >>>>>>> nothing more. >>>>>>> That in this case? >>>>>>> >>>>>>> Sincerely, >>>>>>> Sukhachev Ilya! >>>>>>> >>>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>>> sebastien.jourdain at kitware.com>: >>>>>>> >>>>>>>> Moreover, the documentation that get's updated automatically can be >>>>>>>> found at the following address. (Which might be more accurate.) >>>>>>>> >>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>>> >>>>>>>> This is the one you find when you go on paraview.org and go to the >>>>>>>> documentation section. >>>>>>>> >>>>>>>> Seb >>>>>>>> >>>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>>> >>>>>>>>> Hi Sukhachev, >>>>>>>>> >>>>>>>>> The one thing that might not be explicit about the ubuntu_14_04 >>>>>>>>> guide might be that the script "/data/pvw/bin/start.sh" should be >>>>>>>>> launched with a DISPLAY setup. >>>>>>>>> Otherwise, you will have to be more explicit on what you've done >>>>>>>>> and what is not working. The log files usually helps to see what >>>>>>>>> was skipped from the documentation. >>>>>>>>> >>>>>>>>> Seb >>>>>>>>> >>>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Good day! >>>>>>>>>> Prompt please. >>>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>>> Paraviewweb (http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04 >>>>>>>>>> ) >>>>>>>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>>>>>>> (http: // localhost / apps / Visualizer /) >>>>>>>>>> When deployment by using the ( >>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>>>>>>> as 1 Ceci. >>>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>>> Thank you >>>>>>>>>> >>>>>>>>>> Sincerely, >>>>>>>>>> Sukhachev Ilya! >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Powered by www.kitware.com >>>>>>>>>> >>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>> >>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>> >>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> ? ?????????, >>>>>>> ??????? ????! >>>>>>> +7 912 216 72 72 >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> ? ?????????, >>>>> ??????? ????! >>>>> +7 912 216 72 72 >>>>> >>>> >>>> >>> >>> >>> -- >>> ? ?????????, >>> ??????? ????! >>> +7 912 216 72 72 >>> >> >> >> >> -- >> ? ?????????, >> ??????? ????! >> +7 912 216 72 72 >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -- ? ?????????, ??????? ????! +7 912 216 72 72 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: launcher.json Type: application/json Size: 1410 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 001-pvw.conf Type: application/octet-stream Size: 774 bytes Desc: not available URL: From lifeandfree at gmail.com Tue Sep 30 01:08:14 2014 From: lifeandfree at gmail.com (Ilya Sukhachev) Date: Tue, 30 Sep 2014 11:08:14 +0600 Subject: [Paraview] Edit xmf Message-ID: Good day to all! Please tell me how to do. I need to create a simple shape of the lines in ParaView. Further save the file and open it in ParaViewWeb. But there is a condition necessary to keep in the text file, for example, in the format type * .xmf. It is necessary that manually edit the file. And to boot again in ParaViewWeb. And also. Why when I try to "File -> Save Data", retained only one line, rather than the entire set of lines? Sincerely, Ilya -------------- next part -------------- An HTML attachment was scrubbed... URL: From ioannis.vogiatzis at psi.ch Tue Sep 30 02:51:48 2014 From: ioannis.vogiatzis at psi.ch (Ioannis Vogiatzis Oikonomidis) Date: Tue, 30 Sep 2014 08:51:48 +0200 Subject: [Paraview] paraview module In-Reply-To: References: Message-ID: Hi I have canopy installed on my Mac I would like to have paraview as a module to canopy my default python installation I have installed paraview using the dmg file I have added almost all the folders from the contents folder to my path When I am trying to >From paraview.simple import * I get the know error of dlopen(/Applications/paraview.app/Contents/Python/vtk/vtkCommonCorePython.so , 2): Library not loaded: @executable_path/../Libraries/libvtkCommonCorePython26D-pv4.1.1.dylib Referenced from: /Applications/paraview.app/Contents/Python/vtk/vtkCommonCorePython.so Reason: image not found Could someone help? Thanks Cheers Yannis -------------- next part -------------- An HTML attachment was scrubbed... URL: From praveenn at nvidia.com Tue Sep 30 03:45:52 2014 From: praveenn at nvidia.com (Praveen Narayanan) Date: Tue, 30 Sep 2014 07:45:52 +0000 Subject: [Paraview] Sphere benchmark runs and max number of polygons In-Reply-To: References: Message-ID: On Sep 29, 2014, at 7:11 AM, David E DeMarle wrote: Thanks, I can patch that if you don't have the patience. See: http://www.paraview.org/Wiki/ParaView/Git/Develop for instructions. I can handle that. 2) Secondly, the number of polygons maxes out to 2 million taking about 90 MB. Is there a flag to change the max buffer size? I would like to run a bigger problem running more number of polygons. I am running on an NVIDIA GTX Titan. I don't understand. What buffer do are you talking about? With (thetares, phires)=(1000,1000) it gives the number of cells as 1996000 and memory of 86 MB with a geometry of 130 MB. See http://imgur.com/f8vIsHR for the screenshot. The number of polygons does not increase when the resolution is changed - (thetares,phires)=(1000,4000) gives 2044000 cells, with the memory used 87.82 MB and 135.73 MB for geometry. Screenshot at http://i.imgur.com/zF8vMHu.png I would like to use an image with let us say, 100 M cells in Shpere(). cheers, Thanks Praveen ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ----------------------------------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From jason.fleming at seahorsecoastal.com Tue Sep 30 08:00:06 2014 From: jason.fleming at seahorsecoastal.com (Jason Fleming) Date: Tue, 30 Sep 2014 08:00:06 -0400 Subject: [Paraview] Edit xmf In-Reply-To: References: Message-ID: Can you send a sample file? Cheers Jason On Tue, Sep 30, 2014 at 1:08 AM, Ilya Sukhachev wrote: > Good day to all! > > Please tell me how to do. > I need to create a simple shape of the lines in ParaView. Further save the > file and open it in ParaViewWeb. But there is a condition necessary to > keep in the text file, for example, in the format type * .xmf. It is > necessary that manually edit the file. And to boot again in ParaViewWeb. > And also. Why when I try to "File -> Save Data", retained only one line, rather > than the entire set of lines? > > Sincerely, Ilya > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Dr. Jason G. Fleming Chief Engineer, Seahorse Coastal Consulting 3103 Mandy Ln Morehead City, NC 28557 Tel: (252) 726-6323 Mobile: (252) 269-0962 Web: http://www.seahorsecoastal.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.grenon at onera.fr Tue Sep 30 07:48:38 2014 From: richard.grenon at onera.fr (Richard Grenon) Date: Tue, 30 Sep 2014 13:48:38 +0200 Subject: [Paraview] PV 420 unable to read state file from PV 410 Message-ID: <542A9896.7020201@onera.fr> Hello. I am trying the new PV 420 release using the Linux 64 bits binaries from PV download page. I am trying to load a state file that was created by PV 410 and that reads 13 Tecplot files. The expected plot should show LIC surfaces colored by aerodynamic parameters (pressure or skin friction) and some streamlines. When loading this state file with PV 420, I get many errors (see below), all surfaces are white, and some surfaces are missing. I can't share the data, but I send also the state file in a tar.gz archive. Best regards. Richard > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x563f840): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x563f3e0) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x56403e0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x563fe00) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c5551e0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c554d70) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c555d90): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c555960) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c558000): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c557bd0) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c558bb0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c558780) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c55af20): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c55aa80) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c55ba80): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c55b650) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c55dd40): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c55d930) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c55e880): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c55e450) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c560aa0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c560670) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c561160): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c560d50) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c563560): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c563300) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c563ed0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c563ac0) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c5659b0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c566170) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c566730): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c566940) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c568be0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c568da0) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c569cb0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c569c00) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c56b890): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c56bcd0) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c56c640): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c56c820) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c56eee0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c56ebd0) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c56f650): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c56f9c0) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c571ab0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c571ba0) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c572a20): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c572530) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c574bf0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c574950) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c575940): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c5754a0) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c577b60): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c577730) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c5786c0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c578290) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c57a8e0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c57a4b0) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c57b440): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c57b010) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c57d660): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c57d230) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c57e1c0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c57dd90) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c580610): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c580200) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c581180): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c580d70) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c582c70): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c5830e0) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c583230): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c5838b0) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c585a60): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c585ed0) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c586ae0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c5865d0) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c588da0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c588830) is 0 112 0 8 0 0, which is outside the > whole extent 0 28 0 8 0 0. > > > > ERROR: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, > line 857 > > vtkStreamingDemandDrivenPipeline (0x1c588fb0): The update extent > specified in the information for output port 0 on algorithm > vtkTrivialProducer(0x1c5898c0) is 0 112 0 8 0 0, which is outside the > whole extent 0 40 0 8 0 0. > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x564eb90): Point array Friction with 3 > components, has 53280 tuples but there are only 50166 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x564eb90): Point array frictionmodulus with 1 > components, has 53280 tuples but there are only 50166 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x564eb90): Point array frictionvectorx with 1 > components, has 53280 tuples but there are only 50166 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x564eb90): Point array frictionvectory with 1 > components, has 53280 tuples but there are only 50166 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x564eb90): Point array frictionvectorz with 1 > components, has 53280 tuples but there are only 50166 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x564eb90): Point array x with 1 components, has > 53280 tuples but there are only 50166 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x564eb90): Point array y with 1 components, has > 53280 tuples but there are only 50166 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x564eb90): Point array yplusmeshsize with 1 > components, has 53280 tuples but there are only 50166 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x564eb90): Point array z with 1 components, has > 53280 tuples but there are only 50166 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x568f560): Point array Friction with 3 > components, has 15660 tuples but there are only 14676 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x568f560): Point array frictionmodulus with 1 > components, has 15660 tuples but there are only 14676 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x568f560): Point array frictionvectorx with 1 > components, has 15660 tuples but there are only 14676 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x568f560): Point array frictionvectory with 1 > components, has 15660 tuples but there are only 14676 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x568f560): Point array frictionvectorz with 1 > components, has 15660 tuples but there are only 14676 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x568f560): Point array x with 1 components, has > 15660 tuples but there are only 14676 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x568f560): Point array y with 1 components, has > 15660 tuples but there are only 14676 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x568f560): Point array yplusmeshsize with 1 > components, has 15660 tuples but there are only 14676 points > > > > Warning: In > /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/DataModel/vtkDataSet.cxx, > line 421 > > vtkUnstructuredGrid (0x568f560): Point array z with 1 components, has > 15660 tuples but there are only 14676 points > > > > -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:Richard.Grenon at onera.fr http://www.onera.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pv410statefile.tar.gz Type: application/x-gzip Size: 116323 bytes Desc: not available URL: From dave.demarle at kitware.com Tue Sep 30 09:08:07 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 30 Sep 2014 09:08:07 -0400 Subject: [Paraview] Sphere benchmark runs and max number of polygons In-Reply-To: References: Message-ID: ... > The number of polygons does not increase when the resolution is changed > - (thetares,phires)=(1000,4000) gives 2044000 cells, with the memory used > 87.82 MB and 135.73 MB for geometry. Screenshot at > http://i.imgur.com/zF8vMHu.png > > I would like to use an image with let us say, 100 M cells in Shpere(). > ? Ah, I see. There is a constant in vtkSphereSource.h that defines a max resolution of 1000. You can change that locally, or simply make more spheres or otherwise make a more complicated scene. Plugins/Manta/vtkMantaTestSource.h was written for the sole purpose of making lots and lots of polygons (reproducibly and in parallel) in order to benchmark rendering with. > > > > > cheers, > > Thanks >> Praveen >> >> ----------------------------------------------------------------------------------- >> This email message is for the sole use of the intended recipient(s) and >> may contain >> confidential information. Any unauthorized review, use, disclosure or >> distribution >> is prohibited. If you are not the intended recipient, please contact the >> sender by >> reply email and destroy all copies of the original message. >> >> ----------------------------------------------------------------------------------- >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.grenon at onera.fr Tue Sep 30 09:23:19 2014 From: richard.grenon at onera.fr (Richard Grenon) Date: Tue, 30 Sep 2014 15:23:19 +0200 Subject: [Paraview] PV 420 unable to read state file from PV 410 In-Reply-To: <542A9896.7020201@onera.fr> References: <542A9896.7020201@onera.fr> Message-ID: <542AAEC7.7040405@onera.fr> Hello, The problem in PV 420 seems to be related with the "MergeBlocks" filter: when I open two Tecplot files, I first make a group with these two datasets, then I apply MergeBlocks on the group, and I see that there is a missing part on the result of MergeBlocks between the two datasets. I attach two pictures, one obtained with a pipeline built in PV 410 (Merge is OK) and the other obtained with the same pipeline built in PV 420 (Merge is not OK). Richard Le 30/09/2014 13:48, Richard Grenon a ?crit : > Hello. > > I am trying the new PV 420 release using the Linux 64 bits binaries > from PV download page. > > I am trying to load a state file that was created by PV 410 and that > reads 13 Tecplot files. The expected plot should show LIC surfaces > colored by aerodynamic parameters (pressure or skin friction) and some > streamlines. > > When loading this state file with PV 420, I get many errors (see > below), all surfaces are white, and some surfaces are missing. > > I can't share the data, but I send also the state file in a tar.gz > archive. > > Best regards. > > Richard -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:Richard.Grenon at onera.fr http://www.onera.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pic410.png Type: image/png Size: 28764 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pic420.png Type: image/png Size: 40649 bytes Desc: not available URL: From simon.m.su.ctr at mail.mil Tue Sep 30 10:18:19 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 30 Sep 2014 14:18:19 +0000 Subject: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hello, PV 4.2 superbuild make to completion. ============================================================================ ========== [... snip ......] -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/rbox.txt -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/rbox.man -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/qhalf.htm -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/qhull.htm -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/qh-opto.htm -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/qhull.txt -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/qhull-cpp.xml -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/qh-faq.htm -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/qh-eg.htm -- Installing: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/index.htm -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/qh--dt.gif -- Up-to-date: /home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-bu ild/install/share/doc/qhull/qdelaun.htm [ 99%] Completed 'qhull' [100%] Built target qhull Install the project... -- Install configuration: "Release" -- [download 0% complete] -- [download 3% complete] [... snip ......] ============================================================================ ========== But at the end of the make install, it is complaining about missing files. ============================================================================ ========== [... snip ......] -- Up-to-date: /home/ssu/pv-test/4.2.0_osmesa/lib/paraview-4.2/libvtkxdmf2-pv4.2.so.1 -- Up-to-date: /home/ssu/pv-test/4.2.0_osmesa/lib/paraview-4.2/libvtkzlib-pv4.2.so.1 -- Installing: /home/ssu/pv-test/4.2.0_osmesa/lib/paraview-4.2/libgcc_s.so.1 -- Installing: /home/ssu/pv-test/4.2.0_osmesa/bin/pvserver -- Installing: /home/ssu/pv-test/4.2.0_osmesa/bin/pvdataserver -- Installing: /home/ssu/pv-test/4.2.0_osmesa/bin/pvrenderserver -- Installing: /home/ssu/pv-test/4.2.0_osmesa/bin/pvbatch -- Installing: /home/ssu/pv-test/4.2.0_osmesa/bin/pvpython CMake Error at cmake_install.cmake:90 (FILE): file INSTALL cannot find "/home/ssu/build/paraview/Build_osmesa-2014-09-29/ParaViewSuperbuild_4.2.0-b uild/install/share/appdata". make: *** [install] Error 1 ============================================================================ ========== the same is happening on 4 different machines I have similar build script running. Is his something I should be worried or is it an optional error :) ? There is no appdata directory under the install/share directory. PV 4.2 superbuild is configured as follow. ====================== build script ========== git clone http://paraview.org/ParaViewSuperbuild.git ParaViewSuperbuild_${version} cd ParaViewSuperbuild_${version} git checkout v4.2.0 cd .. mkdir ParaViewSuperbuild_${version}-build cd ParaViewSuperbuild_${version}-build cmake \ -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \ -DCMAKE_BUILD_TYPE=Release \ -DParaView_FROM_GIT=ON \ -DENABLE_boost=ON \ -DENABLE_cgns=OFF \ -DENABLE_ffmpeg=ON \ -DENABLE_fontconfig=ON \ -DENABLE_freetype=ON \ -DENABLE_hdf5=ON \ -DENABLE_libxml2=ON \ -DENABLE_matplotlib=ON \ -DENABLE_mesa=OFF \ -DENABLE_mpi=ON \ -DENABLE_numpy=ON \ -DENABLE_osmesa=ON \ -DENABLE_paraview=ON \ -DENABLE_png=ON \ -DENABLE_python=ON \ -DENABLE_qhull=ON \ -DENABLE_qt=OFF \ -DENABLE_silo=ON \ -DENABLE_szip=ON \ -DENABLE_visitbridge=ON \ -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpi chcxx.so" \ -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpich .so" \ -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpichcx x.so" \ -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include /" \ -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/" \ -DUSE_SYSTEM_mpi=ON \ -DUSE_SYSTEM_python=OFF \ -DUSE_SYSTEM_qt=OFF \ -DUSE_SYSTEM_zlib=ON \ ../ParaViewSuperbuild_${version} make make install ======================================================== Any help is much appreciated. Thanks -simon Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From praveenn at nvidia.com Tue Sep 30 10:19:56 2014 From: praveenn at nvidia.com (Praveen Narayanan) Date: Tue, 30 Sep 2014 14:19:56 +0000 Subject: [Paraview] Sphere benchmark runs and max number of polygons In-Reply-To: References: Message-ID: <1538F132-59E1-4F54-83DB-B1DA64E9D891@nvidia.com> Excellent information re. manta. Thanks David. On Sep 30, 2014, at 6:08 AM, David E DeMarle wrote: ... The number of polygons does not increase when the resolution is changed - (thetares,phires)=(1000,4000) gives 2044000 cells, with the memory used 87.82 MB and 135.73 MB for geometry. Screenshot at http://i.imgur.com/zF8vMHu.png I would like to use an image with let us say, 100 M cells in Shpere(). ? Ah, I see. There is a constant in vtkSphereSource.h that defines a max resolution of 1000. You can change that locally, or simply make more spheres or otherwise make a more complicated scene. Plugins/Manta/vtkMantaTestSource.h was written for the sole purpose of making lots and lots of polygons (reproducibly and in parallel) in order to benchmark rendering with. cheers, Thanks Praveen ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ----------------------------------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Tue Sep 30 10:43:58 2014 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Tue, 30 Sep 2014 08:43:58 -0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Your client side request to the launcher is asking for the "visualizer" application, while the launcher (according to your launcher config) doesn't know about a command line to start that application. Try changing the "pipeline" key under the "apps" section to "visualizer". Cheers, Scott On Mon, Sep 29, 2014 at 9:36 PM, Ilya Sukhachev wrote: > Good day! > > Yes, of course > Attached. > Also put the configuration file Apache. > > Ilya > > 2014-09-29 20:54 GMT+06:00 Scott Wittenburg > : > >> Can you share your launcher configuration file? It appears you may have >> no "visualizer" application command line configured. >> >> Cheers, >> Scott >> >> >> On Mon, Sep 29, 2014 at 1:43 AM, ???? ??????? >> wrote: >> >>> >>> And there is another question. >>> Deployed software. I go to http://localhost/apps/Visualizer /. As a >>> result, I see only the inscription ParaViewWeb and flailing wheel. And >>> he gave me a list of errors in the console: >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1439, in dataReceived >>> finishCallback(data[contentLength:]) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1668, in _finishRequestBody >>> self.allContentReceived() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1731, in allContentReceived >>> req.requestReceived(command, path, version) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 827, in requestReceived >>> self.process() >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 189, in process >>> self.render(resrc) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 238, in render >>> body = resrc.render(self) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>> line 250, in render >>> return m(request) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 399, in render_POST >>> session = self.session_manager.createSession(payload) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 182, in createSession >>> options['cmd'] = >>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>> self.config['properties']]) >>> exceptions.KeyError: u'visualizer' >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 321, in processingFailed >>> % webutil.formatFailure(reason)) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>> line 425, in formatFailure >>> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 420, in flattenString >>> d = flatten(request, root, io.write) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 402, in flatten >>> _writeFlattenedData(state, write, result) >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 359, in _writeFlattenedData >>> element = state.next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 326, in _flattenTree >>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>> twisted.web.error.FlattenerError: Exception while flattening: >>> >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 317, in _flattenTree >>> element = stack[-1].next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 286, in _flattenElement >>> result = root.render(request) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>> line 184, in render >>> return loader.load() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 465, in load >>> self._loadedTemplate = self._loadDoc() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 446, in _loadDoc >>> f = self._path.open('r') >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>> line 828, in open >>> return open(self.path, mode + 'b') >>> IOError: [Errno 2] No such file or directory: >>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>> >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1439, in dataReceived >>> finishCallback(data[contentLength:]) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1668, in _finishRequestBody >>> self.allContentReceived() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1731, in allContentReceived >>> req.requestReceived(command, path, version) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 827, in requestReceived >>> self.process() >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 189, in process >>> self.render(resrc) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 238, in render >>> body = resrc.render(self) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>> line 250, in render >>> return m(request) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 399, in render_POST >>> session = self.session_manager.createSession(payload) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 182, in createSession >>> options['cmd'] = >>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>> self.config['properties']]) >>> exceptions.KeyError: u'visualizer' >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 321, in processingFailed >>> % webutil.formatFailure(reason)) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>> line 425, in formatFailure >>> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 420, in flattenString >>> d = flatten(request, root, io.write) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 402, in flatten >>> _writeFlattenedData(state, write, result) >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 359, in _writeFlattenedData >>> element = state.next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 326, in _flattenTree >>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>> twisted.web.error.FlattenerError: Exception while flattening: >>> >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 317, in _flattenTree >>> element = stack[-1].next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 286, in _flattenElement >>> result = root.render(request) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>> line 184, in render >>> return loader.load() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 465, in load >>> self._loadedTemplate = self._loadDoc() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 446, in _loadDoc >>> f = self._path.open('r') >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>> line 828, in open >>> return open(self.path, mode + 'b') >>> IOError: [Errno 2] No such file or directory: >>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>> >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1439, in dataReceived >>> finishCallback(data[contentLength:]) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1668, in _finishRequestBody >>> self.allContentReceived() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1731, in allContentReceived >>> req.requestReceived(command, path, version) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 827, in requestReceived >>> self.process() >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 189, in process >>> self.render(resrc) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 238, in render >>> body = resrc.render(self) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>> line 250, in render >>> return m(request) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 399, in render_POST >>> session = self.session_manager.createSession(payload) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 182, in createSession >>> options['cmd'] = >>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>> self.config['properties']]) >>> exceptions.KeyError: u'visualizer' >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 321, in processingFailed >>> % webutil.formatFailure(reason)) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>> line 425, in formatFailure >>> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 420, in flattenString >>> d = flatten(request, root, io.write) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 402, in flatten >>> _writeFlattenedData(state, write, result) >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 359, in _writeFlattenedData >>> element = state.next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 326, in _flattenTree >>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>> twisted.web.error.FlattenerError: Exception while flattening: >>> >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 317, in _flattenTree >>> element = stack[-1].next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 286, in _flattenElement >>> result = root.render(request) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>> line 184, in render >>> return loader.load() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 465, in load >>> self._loadedTemplate = self._loadDoc() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 446, in _loadDoc >>> f = self._path.open('r') >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>> line 828, in open >>> return open(self.path, mode + 'b') >>> IOError: [Errno 2] No such file or directory: >>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>> >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1439, in dataReceived >>> finishCallback(data[contentLength:]) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1668, in _finishRequestBody >>> self.allContentReceived() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1731, in allContentReceived >>> req.requestReceived(command, path, version) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 827, in requestReceived >>> self.process() >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 189, in process >>> self.render(resrc) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 238, in render >>> body = resrc.render(self) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>> line 250, in render >>> return m(request) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 399, in render_POST >>> session = self.session_manager.createSession(payload) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 182, in createSession >>> options['cmd'] = >>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>> self.config['properties']]) >>> exceptions.KeyError: u'visualizer' >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 321, in processingFailed >>> % webutil.formatFailure(reason)) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>> line 425, in formatFailure >>> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 420, in flattenString >>> d = flatten(request, root, io.write) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 402, in flatten >>> _writeFlattenedData(state, write, result) >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 359, in _writeFlattenedData >>> element = state.next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 326, in _flattenTree >>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>> twisted.web.error.FlattenerError: Exception while flattening: >>> >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 317, in _flattenTree >>> element = stack[-1].next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 286, in _flattenElement >>> result = root.render(request) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>> line 184, in render >>> return loader.load() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 465, in load >>> self._loadedTemplate = self._loadDoc() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 446, in _loadDoc >>> f = self._path.open('r') >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>> line 828, in open >>> return open(self.path, mode + 'b') >>> IOError: [Errno 2] No such file or directory: >>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>> >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1439, in dataReceived >>> finishCallback(data[contentLength:]) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1668, in _finishRequestBody >>> self.allContentReceived() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1731, in allContentReceived >>> req.requestReceived(command, path, version) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 827, in requestReceived >>> self.process() >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 189, in process >>> self.render(resrc) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 238, in render >>> body = resrc.render(self) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>> line 250, in render >>> return m(request) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 399, in render_POST >>> session = self.session_manager.createSession(payload) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 182, in createSession >>> options['cmd'] = >>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>> self.config['properties']]) >>> exceptions.KeyError: u'visualizer' >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 321, in processingFailed >>> % webutil.formatFailure(reason)) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>> line 425, in formatFailure >>> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 420, in flattenString >>> d = flatten(request, root, io.write) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 402, in flatten >>> _writeFlattenedData(state, write, result) >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 359, in _writeFlattenedData >>> element = state.next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 326, in _flattenTree >>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>> twisted.web.error.FlattenerError: Exception while flattening: >>> >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 317, in _flattenTree >>> element = stack[-1].next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 286, in _flattenElement >>> result = root.render(request) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>> line 184, in render >>> return loader.load() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 465, in load >>> self._loadedTemplate = self._loadDoc() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 446, in _loadDoc >>> f = self._path.open('r') >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>> line 828, in open >>> return open(self.path, mode + 'b') >>> IOError: [Errno 2] No such file or directory: >>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>> >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1439, in dataReceived >>> finishCallback(data[contentLength:]) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1668, in _finishRequestBody >>> self.allContentReceived() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1731, in allContentReceived >>> req.requestReceived(command, path, version) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 827, in requestReceived >>> self.process() >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 189, in process >>> self.render(resrc) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 238, in render >>> body = resrc.render(self) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>> line 250, in render >>> return m(request) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 399, in render_POST >>> session = self.session_manager.createSession(payload) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 182, in createSession >>> options['cmd'] = >>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>> self.config['properties']]) >>> exceptions.KeyError: u'visualizer' >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 321, in processingFailed >>> % webutil.formatFailure(reason)) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>> line 425, in formatFailure >>> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 420, in flattenString >>> d = flatten(request, root, io.write) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 402, in flatten >>> _writeFlattenedData(state, write, result) >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 359, in _writeFlattenedData >>> element = state.next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 326, in _flattenTree >>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>> twisted.web.error.FlattenerError: Exception while flattening: >>> >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 317, in _flattenTree >>> element = stack[-1].next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 286, in _flattenElement >>> result = root.render(request) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>> line 184, in render >>> return loader.load() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 465, in load >>> self._loadedTemplate = self._loadDoc() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 446, in _loadDoc >>> f = self._path.open('r') >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>> line 828, in open >>> return open(self.path, mode + 'b') >>> IOError: [Errno 2] No such file or directory: >>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>> >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1439, in dataReceived >>> finishCallback(data[contentLength:]) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1668, in _finishRequestBody >>> self.allContentReceived() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 1731, in allContentReceived >>> req.requestReceived(command, path, version) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>> line 827, in requestReceived >>> self.process() >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 189, in process >>> self.render(resrc) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 238, in render >>> body = resrc.render(self) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>> line 250, in render >>> return m(request) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 399, in render_POST >>> session = self.session_manager.createSession(payload) >>> File >>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>> line 182, in createSession >>> options['cmd'] = >>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>> self.config['properties']]) >>> exceptions.KeyError: u'visualizer' >>> Unhandled Error >>> Traceback (most recent call last): >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>> line 321, in processingFailed >>> % webutil.formatFailure(reason)) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>> line 425, in formatFailure >>> flattenString(None, FailureElement(myFailure)).addBoth(result.append) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 420, in flattenString >>> d = flatten(request, root, io.write) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 402, in flatten >>> _writeFlattenedData(state, write, result) >>> --- --- >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 359, in _writeFlattenedData >>> element = state.next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 326, in _flattenTree >>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>> twisted.web.error.FlattenerError: Exception while flattening: >>> >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 317, in _flattenTree >>> element = stack[-1].next() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>> line 286, in _flattenElement >>> result = root.render(request) >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>> line 184, in render >>> return loader.load() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 465, in load >>> self._loadedTemplate = self._loadDoc() >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>> line 446, in _loadDoc >>> f = self._path.open('r') >>> File >>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>> line 828, in open >>> return open(self.path, mode + 'b') >>> IOError: [Errno 2] No such file or directory: >>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>> >>> >>> In logs file error.log: >>> [Mon Sep 29 13:34:03.884092 2014] [proxy_http:error] [pid 14562:tid >>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38924] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:03.905642 2014] [proxy_http:error] [pid 14562:tid >>> 140533720598272] (20014)Internal error: [client 127.0.0.1:38923] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:03.908441 2014] [proxy_http:error] [pid 14563:tid >>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38925] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:03.923450 2014] [proxy_http:error] [pid 14563:tid >>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38926] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:03.925919 2014] [proxy_http:error] [pid 14563:tid >>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38922] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:03.928206 2014] [proxy_http:error] [pid 14563:tid >>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38921] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:03.930176 2014] [proxy_http:error] [pid 14563:tid >>> 140533737383680] (20014)Internal error: [client 127.0.0.1:38933] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:03.930197 2014] [proxy:error] [pid 14563:tid >>> 140533737383680] [client 127.0.0.1:38933] AH00898: Error reading from >>> remote server returned by /paraview/, referer: >>> http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:20.357181 2014] [proxy_http:error] [pid 14563:tid >>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38939] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:20.359293 2014] [proxy_http:error] [pid 14563:tid >>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38940] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:20.361335 2014] [proxy_http:error] [pid 14562:tid >>> 140533829703424] (20014)Internal error: [client 127.0.0.1:38944] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:20.363796 2014] [proxy_http:error] [pid 14562:tid >>> 140533854881536] (20014)Internal error: [client 127.0.0.1:38943] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:20.366176 2014] [proxy_http:error] [pid 14562:tid >>> 140533821310720] (20014)Internal error: [client 127.0.0.1:38942] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:20.368434 2014] [proxy_http:error] [pid 14562:tid >>> 140533804525312] (20014)Internal error: [client 127.0.0.1:38941] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:20.370937 2014] [proxy_http:error] [pid 14563:tid >>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38951] >>> AH01102: error reading status line from remote server localhost:8080, >>> referer: http://localhost/apps/Visualizer/ >>> [Mon Sep 29 13:34:20.370960 2014] [proxy:error] [pid 14563:tid >>> 140533754169088] [client 127.0.0.1:38951] AH00898: Error reading from >>> remote server returned by /paraview/, referer: >>> http://localhost/apps/Visualizer/ >>> >>> >>> 2014-09-29 10:30 GMT+06:00 ???? ??????? : >>> >>>> Good day. >>>> Thank you. >>>> >>>> You may be able to explain. What kind of filter is it? >>>> >>>> Ilya >>>> >>>> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >>>> sebastien.jourdain at kitware.com>: >>>> >>>>> ParaView 4.2 has been released, so that would be the latest stable >>>>> version available. >>>>> There is no localization per say but the filter names could be >>>>> customized the way you want. >>>>> >>>>> For continuous live visualization it is possible but that will be a >>>>> custom development. And for that you can contact Kitware for either a >>>>> support contract (http://www.kitware.com/products/support.html) or an >>>>> end-product development ( >>>>> http://www.kitware.com/products/consulting.html). >>>>> >>>>> Seb >>>>> >>>>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? >>>>> wrote: >>>>> >>>>>> thank you, ok. try to understand. I put the stable version and not the >>>>>> release candidate. >>>>>> >>>>>> But there are a few more questions. >>>>>> Do files are responsible for localization? I need to replace the >>>>>> language in the design parawiewweb. >>>>>> And the second. Is there a possibility of the file from which the >>>>>> object is loaded into the web, continuously read the data? That is to >>>>>> update the image in the browser loading new data, but this is not in >>>>>> the manual and automatic. >>>>>> >>>>>> Sincerely, >>>>>> Sukhachev Ilya! >>>>>> >>>>>> >>>>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>>>> sebastien.jourdain at kitware.com>: >>>>>> >>>>>>> The top bar is not green anymore. Try to replace the directory /lib, >>>>>>> /apps, /ext within the ParaView /www inside the directory you serve with >>>>>>> Apache. >>>>>>> Moreover, can you enable the development tools on your browser to >>>>>>> see what kind of error you got? >>>>>>> >>>>>>> Did you look also at the different types of logs? Apache, Launcher >>>>>>> (see config to know where you choose to put them). >>>>>>> That could also give you an idea on what went wrong. >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? >>>>>> > wrote: >>>>>>> >>>>>>>> Hi, Sebastien >>>>>>>> >>>>>>>> Thank you. >>>>>>>> I just took advantage of this documentation and to deploy. >>>>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>>>>> only displayed only the green bar at the top of the window, and >>>>>>>> nothing more. >>>>>>>> That in this case? >>>>>>>> >>>>>>>> Sincerely, >>>>>>>> Sukhachev Ilya! >>>>>>>> >>>>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>> >>>>>>>>> Moreover, the documentation that get's updated automatically can >>>>>>>>> be found at the following address. (Which might be more accurate.) >>>>>>>>> >>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>>>> >>>>>>>>> This is the one you find when you go on paraview.org and go to >>>>>>>>> the documentation section. >>>>>>>>> >>>>>>>>> Seb >>>>>>>>> >>>>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Sukhachev, >>>>>>>>>> >>>>>>>>>> The one thing that might not be explicit about the ubuntu_14_04 >>>>>>>>>> guide might be that the script "/data/pvw/bin/start.sh" should >>>>>>>>>> be launched with a DISPLAY setup. >>>>>>>>>> Otherwise, you will have to be more explicit on what you've done >>>>>>>>>> and what is not working. The log files usually helps to see what >>>>>>>>>> was skipped from the documentation. >>>>>>>>>> >>>>>>>>>> Seb >>>>>>>>>> >>>>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Good day! >>>>>>>>>>> Prompt please. >>>>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>>>> Paraviewweb ( >>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>>>>>>>> (http: // localhost / apps / Visualizer /) >>>>>>>>>>> When deployment by using the ( >>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>>>>>>>> as 1 Ceci. >>>>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>>>> Thank you >>>>>>>>>>> >>>>>>>>>>> Sincerely, >>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>> >>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>> >>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>>> >>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> ? ?????????, >>>>>>>> ??????? ????! >>>>>>>> +7 912 216 72 72 >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> ? ?????????, >>>>>> ??????? ????! >>>>>> +7 912 216 72 72 >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> ? ?????????, >>>> ??????? ????! >>>> +7 912 216 72 72 >>>> >>> >>> >>> >>> -- >>> ? ?????????, >>> ??????? ????! >>> +7 912 216 72 72 >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > > > -- > ? ?????????, > ??????? ????! > +7 912 216 72 72 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Sep 30 10:53:30 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 10:53:30 -0400 Subject: [Paraview] HOWto create / extend sources? In-Reply-To: <542A1424.5020203@xs4all.nl> References: <5426BC2D.7000505@xs4all.nl> <542A1424.5020203@xs4all.nl> Message-ID: Glad to help :). Utkarsh On Mon, Sep 29, 2014 at 10:23 PM, B.W.H. van Beest wrote: > Utkarsh, > > > Thanks for the pointers. I'll follow-up according your suggestions. > > I'm only recently doing stuff with ParaView (i.e. plugin-development). > Please accept my compliments for the way you answer questions in this > forum. The few answers you gave me + link to appropriate documentation > have been very iseful! > > Regards, > Bertwim > > > On 09/29/2014 02:46 PM, Utkarsh Ayachit wrote: >>> a) How to create a new source ("MyNewSource") >> You define the 'proxy' under the "sources" group, rather than filters. >> It will automatically show up in the Menu. Look at sources.xml under >> [1] to see other source proxy definitions. >> >>> b) How can I extend an existing source (box, sphere, etc.) with new >>> properties and methods ("MyBox, "MySphere"). >> Similar to the filters, you basically need to write a new VTK >> algorithm with these new methods. You can subclass the existing VTK >> source. Looking at sources.xml, you can find out which proxy using >> which VTK algorithm, e.g. "SphereSource" (labelled as "Sphere") uses >> "vtkSphereSource". After adding the methods on the VTK algorithm, next >> part is exposing those methods as properties using the XML. >> >> [1] https://github.com/Kitware/ParaView/tree/master/ParaViewCore/ServerManager/SMApplication/Resources >> >>> Any help or suggestions are greatly appreciated. >>> >>> Kind Regards, >>> Bertwim >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview > From ben.boeckel at kitware.com Tue Sep 30 11:03:56 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 30 Sep 2014 11:03:56 -0400 Subject: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) In-Reply-To: References: Message-ID: <20140930150356.GC12969@megas.kitwarein.com> On Tue, Sep 30, 2014 at 14:18:19 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > Any help is much appreciated. I added the appdata stuff; looking into it. --Ben From ben.boeckel at kitware.com Tue Sep 30 11:42:10 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 30 Sep 2014 11:42:10 -0400 Subject: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) In-Reply-To: <20140930150356.GC12969@megas.kitwarein.com> References: <20140930150356.GC12969@megas.kitwarein.com> Message-ID: <20140930154210.GA6846@megas.kitwarein.com> On Tue, Sep 30, 2014 at 11:03:56 -0400, Ben Boeckel wrote: > On Tue, Sep 30, 2014 at 14:18:19 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > > Any help is much appreciated. > > I added the appdata stuff; looking into it. Seems that the fact that ParaView's superbuild only builds the paraview executable (which is tied to the appdata files) is controlled by whether Qt is enabled in the superbuild and this wasn't used to expect the appdata directory properly: http://review.source.kitware.com/#/c/17283/ --Ben From bwvb at xs4all.nl Tue Sep 30 14:09:58 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 30 Sep 2014 20:09:58 +0200 Subject: [Paraview] HOWto create / extend sources? In-Reply-To: References: <5426BC2D.7000505@xs4all.nl> Message-ID: <542AF1F6.4050901@xs4all.nl> Utkash, I followed-up on your suggestions, but apparently I am doing something wrong. I hope you or somebody else can point me to the solution. This is what I did. 1) new class: sphBoxSource. I extended class vtkCubeSource with one data member, with corresponding get/set method. (Code below) 2) I added an xml-file, with the source description taken from source.xml (CubeSource). (Below) 3) I modified the CMakeList.txt accordingly. (Below) Magically, the new source appeared in the menu. But when clicking it, the program crashed. The error message I get is: ERROR: In /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 307 vtkSISourceProxy (0x30289e0): Failed to create sphBoxSource. Aborting for debugging purposes. I noticed that several people running into similar problems, but so far I haven't been able to find the clue to the solution. Before showing the code, I give the result of the compilation. @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ chopin Plugins/SPHToolbar# make clean chopin Plugins/SPHToolbar# make [ 0%] Generating Documentation HTMLs from xmls Processing wiki sources Processing wiki filters Processing wiki writers Processing wiki readers [ 10%] Generating qrc_sph_icons.cxx [ 10%] Compiling Qt help project SPHToolbar.qhp Building up file structure... Insert custom filters... Insert help data for filter section (1 of 1)... Insert files... Warning: The file /usr/local/git/ParaView/build/Examples/All/Plugins/SPHToolbar/doc/*.css does not exist! Skipping it. Warning: The file /usr/local/git/ParaView/build/Examples/All/Plugins/SPHToolbar/doc/*.png does not exist! Skipping it. Warning: The file /usr/local/git/ParaView/build/Examples/All/Plugins/SPHToolbar/doc/*.jpg does not exist! Skipping it. Insert contents... Insert indices... Documentation successfully generated. [ 10%] Generating SPHToolbar_doc.h -- Generate module: SPHToolbar [ 10%] Generating vtkSMXML_SPHToolbar.h -- Generate module: sph_sources [ 20%] Generating moc_SPHToolbarActions.cpp [ 20%] Generating moc_sphBActionCreateSource.cpp [ 30%] Generating moc_sphBAction.cpp [ 30%] Generating moc_SPHToolbarActionsImplementation.cpp [ 40%] Generating moc_SPHToolbar_Plugin.cpp Scanning dependencies of target SPHToolbar [ 50%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/qrc_sph_icons.o [ 50%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_SPHToolbarActions.o [ 60%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_sphBActionCreateSource.o [ 60%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_sphBAction.o [ 60%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/SPHToolbarActionsImplementation.o [ 70%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_SPHToolbarActionsImplementation.o [ 70%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/SPHToolbarActions.o [ 80%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphBActionCreateSource.o [ 80%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphBActionRegionInventory.o [ 90%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphBoxSource.o [ 90%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphUndoStack.o [ 90%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphObjectTracer.o [100%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/SPHToolbar_Plugin.o [100%] Building CXX object Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_SPHToolbar_Plugin.o Linking CXX shared library /usr/local/git/ParaView/build/lib/libSPHToolbar.so [100%] Built target SPHToolbar chopin Plugins/SPHToolbar# @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ ====================================================== Here is the new class: #include "vtkCubeSource.h" class sphBoxSource : public vtkCubeSource { private: int _type; public: static sphBoxSource *New(); // Monkey see, monkey do ?????????????? vtkTypeMacro(sphBoxSource,vtkCubeSource); // Monkey see, monkey do ?????????????? public: sphBoxSource( double=1.0, double=1.0, double=1.0 ); ~sphBoxSource(); public: void setType( int ); int getType() const; }; ============================================================ XML-file "sph_sources.xml": (adapted from sources.xml) ============================================================ The Box source can be used to add a box to the 3D scene. The output of the Box source is polygonal data containing both normals and texture coordinates. This property specifies the length of the box in the X direction. This property specifies the length of the box in the Y direction. This property specifies the length of the box in the Z direction. This property specifies the center of the box. ====================================================================== Finally, the CMakeList.txt reads: ====================================================================== CMAKE_MINIMUM_REQUIRED(VERSION 2.4) IF(NOT ParaView_BINARY_DIR) FIND_PACKAGE(ParaView REQUIRED) INCLUDE(${PARAVIEW_USE_FILE}) ENDIF(NOT ParaView_BINARY_DIR) IF(PARAVIEW_BUILD_QT_GUI) # We need to wrap for Qt stuff such as signals/slots etc. to work correctly. IF (PARAVIEW_QT_VERSION VERSION_GREATER "4") QT5_WRAP_CPP(MOC_SRCS SPHToolbarActions.h sphBActionCreateSource.h sphBAction.h ) ELSE () QT4_WRAP_CPP(MOC_SRCS SPHToolbarActions.h sphBActionCreateSource.h sphBAction.h ) ENDIF () # This is a macro for adding QActionGroup subclasses automatically as toolbars. ADD_PARAVIEW_ACTION_GROUP(IFACES IFACE_SRCS CLASS_NAME SPHToolbarActions GROUP_NAME "ToolBar/SPHToolbar") # Now create a plugin for the toolbar. Here we pass IFACES and IFACE_SRCS # which are filled up by the above macro with relevant entries ADD_PARAVIEW_PLUGIN(SPHToolbar "1.0" GUI_INTERFACES ${IFACES} GUI_RESOURCES sph_icons.qrc SERVER_MANAGER_XML sph_sources.xml SOURCES ${MOC_SRCS} ${IFACE_SRCS} SPHToolbarActions.cpp sphBActionCreateSource.cpp sphBActionRegionInventory.cpp sphBoxSource.cpp sphUndoStack.cpp sphObjectTracer.cpp ) ENDIF(PARAVIEW_BUILD_QT_GUI) ====================================================================== On 09/29/2014 02:46 PM, Utkarsh Ayachit wrote: >> a) How to create a new source ("MyNewSource") > You define the 'proxy' under the "sources" group, rather than filters. > It will automatically show up in the Menu. Look at sources.xml under > [1] to see other source proxy definitions. > >> b) How can I extend an existing source (box, sphere, etc.) with new >> properties and methods ("MyBox, "MySphere"). > Similar to the filters, you basically need to write a new VTK > algorithm with these new methods. You can subclass the existing VTK > source. Looking at sources.xml, you can find out which proxy using > which VTK algorithm, e.g. "SphereSource" (labelled as "Sphere") uses > "vtkSphereSource". After adding the methods on the VTK algorithm, next > part is exposing those methods as properties using the XML. > > [1] https://github.com/Kitware/ParaView/tree/master/ParaViewCore/ServerManager/SMApplication/Resources > >> Any help or suggestions are greatly appreciated. >> >> Kind Regards, >> Bertwim >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From jeffrey.c.becker at nasa.gov Tue Sep 30 14:12:21 2014 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Tue, 30 Sep 2014 11:12:21 -0700 Subject: [Paraview] viewing data files with different scales (apologies if this is posted twice) Message-ID: <542AF285.9090008@nasa.gov> Hi. I'd like to use Paraview 4.2 to overlay a dataset of air species concentration data (range 0 - 1e-16) over a map of earth elevation data (range -7700 to 7700). Is there a way to view both, e.g., with different colormaps and scales? Thanks. -jeff From jeffrey.c.becker at nasa.gov Tue Sep 30 13:48:38 2014 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Tue, 30 Sep 2014 10:48:38 -0700 Subject: [Paraview] viewing data files with different scales Message-ID: <542AECF6.8090606@nasa.gov> Hi. I'd like to use Paraview 4.2 to overlay a dataset of air species concentration data (range 0 - 1e-16) over a map of earth elevation data (range -7700 to 7700). Is there a way to view both, e.g., with different colormaps and scales? Thanks. -jeff From cabcias at hotmail.com Tue Sep 30 15:16:00 2014 From: cabcias at hotmail.com (=?iso-8859-1?B?Q2FybG9zIEFuZHLpcyBCZXJuYWwgQ2FzdHJv?=) Date: Tue, 30 Sep 2014 14:16:00 -0500 Subject: [Paraview] Edit Color Map Message-ID: To whom it may concern, Hello... my name is Andres Bernal and I am a London South Bank University student carrying out a thesis about the influence of the buildings shape onto the atmospheric pollutants concentration due to the innovative forms of them nowadays. I am working on a building known as "The Walkie-Talkie Building" and the third stage of the project was to read the simulations (coming from Fluidity) . In order to move along with the project we need to see/read the dispersion of pollutants (tracers) around the building (coming from some sources that I set up, in this case/file, 7 sources which means 7 Tracers ) with Paraview. When I set up a "Slice" in order to see such dispersion at a certain height I cannot see anything and it seems to be this could be worked out in the "Edit Color Map". I would like you to help me in this issue as I have been trying to figure out the problem but I have not been able to and I got stuck for this matter. I would be really grateful, thanks. The heights of the tracers are: Tracer 1 = 0.3 Tracer 2 = 0.5 Tracer 3 = 0.7 Tracer 4 = 0.3 Tracer 5 = 0.8 Tracer 6 = 0.5 Tracer 7 = 0.762 The file attached below is a very simple scenario as I am working on several more complex scenarios even with more buildings. I would just like you to help me to sort out the colours issue to see the tracers, please. Any advice would be much appreciated. Kind Regards, Andres Bernal Carlos Andr?s Bernal CastroIngeniero Ambiental Y SanitarioUniversidad De La Salle Carlos Andr?s tiene un archivo para compartir contigo en OneDrive. Para verlo, haz clic en el siguiente v?nculo. Walkie-Curved_29.vtu -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Tue Sep 30 15:36:13 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 30 Sep 2014 19:36:13 +0000 Subject: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) In-Reply-To: <20140930154210.GA6846@megas.kitwarein.com> References: <20140930150356.GC12969@megas.kitwarein.com>, <20140930154210.GA6846@megas.kitwarein.com> Message-ID: Ben, can I safely ignore the error? Can we assume the binary installation is complete? or are there additional installation steps after appdata step that is needed for a proper ParaView binary installation? If so, how do I get around it? thanks -simon ________________________________________ From: Ben Boeckel [ben.boeckel at kitware.com] Sent: Tuesday, September 30, 2014 11:42 AM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) On Tue, Sep 30, 2014 at 11:03:56 -0400, Ben Boeckel wrote: > On Tue, Sep 30, 2014 at 14:18:19 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > > Any help is much appreciated. > > I added the appdata stuff; looking into it. Seems that the fact that ParaView's superbuild only builds the paraview executable (which is tied to the appdata files) is controlled by whether Qt is enabled in the superbuild and this wasn't used to expect the appdata directory properly: http://review.source.kitware.com/#/c/17283/ --Ben From utkarsh.ayachit at kitware.com Tue Sep 30 16:22:33 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 16:22:33 -0400 Subject: [Paraview] viewing data files with different scales In-Reply-To: <542AECF6.8090606@nasa.gov> References: <542AECF6.8090606@nasa.gov> Message-ID: Jeff, Try applying the "Calculator" filter with an empty "Function" to create a second dataset which is simply pass through of the original dataset. Now, you can show both the original dataset and the output of the Calculator in the same view. Select different coloring arrays and ranges and you'd be all set. Utkarsh On Tue, Sep 30, 2014 at 1:48 PM, Jeff Becker wrote: > Hi. I'd like to use Paraview 4.2 to overlay a dataset of air species > concentration data (range 0 - 1e-16) over a map of earth elevation data > (range -7700 to 7700). Is there a way to view both, e.g., with different > colormaps and scales? Thanks. > > -jeff > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Tue Sep 30 16:24:07 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 16:24:07 -0400 Subject: [Paraview] PV 420 unable to read state file from PV 410 In-Reply-To: <542AAEC7.7040405@onera.fr> References: <542A9896.7020201@onera.fr> <542AAEC7.7040405@onera.fr> Message-ID: This is a little less surprising since this release does include some major refactors to VTK when relating to structured extents. Is it possible to get some other dummy dataset that would help reproduce this issue? That'll make the tracking down easier. Thanks Utkarsh On Tue, Sep 30, 2014 at 9:23 AM, Richard Grenon wrote: > Hello, > > The problem in PV 420 seems to be related with the "MergeBlocks" filter: > when I open two Tecplot files, I first make a group with these two datasets, > then I apply MergeBlocks on the group, and I see that there is a missing > part on the result of MergeBlocks between the two datasets. I attach two > pictures, one obtained with a pipeline built in PV 410 (Merge is OK) and the > other obtained with the same pipeline built in PV 420 (Merge is not OK). > > Richard > > Le 30/09/2014 13:48, Richard Grenon a ?crit : > > Hello. > > I am trying the new PV 420 release using the Linux 64 bits binaries from PV > download page. > > I am trying to load a state file that was created by PV 410 and that reads > 13 Tecplot files. The expected plot should show LIC surfaces colored by > aerodynamic parameters (pressure or skin friction) and some streamlines. > > When loading this state file with PV 420, I get many errors (see below), all > surfaces are white, and some surfaces are missing. > > I can't share the data, but I send also the state file in a tar.gz archive. > > Best regards. > > Richard > > > -- > Richard GRENON > ONERA > Departement d'Aerodynamique Appliquee - DAAP/ACI > 8 rue des Vertugadins > 92190 MEUDON - FRANCE > phone : +33 1 46 73 42 17 > fax : +33 1 46 73 41 46 > mailto:Richard.Grenon at onera.fr > http://www.onera.fr > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From ben.boeckel at kitware.com Tue Sep 30 17:15:40 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 30 Sep 2014 17:15:40 -0400 Subject: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) In-Reply-To: References: <20140930150356.GC12969@megas.kitwarein.com> <20140930154210.GA6846@megas.kitwarein.com> Message-ID: <20140930211540.GA25473@megas.kitwarein.com> On Tue, Sep 30, 2014 at 19:36:13 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > can I safely ignore the error? Can we assume the binary installation > is complete? or are there additional installation steps after appdata > step that is needed for a proper ParaView binary installation? If so, > how do I get around it? There are probably more files which need installed after the appdata, but making the changes in the changeset should allow your "make install" from the superbuild to complete fully. Once that happens, the install should be fine. --Ben From simon.m.su.ctr at mail.mil Tue Sep 30 17:24:26 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 30 Sep 2014 21:24:26 +0000 Subject: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) In-Reply-To: <20140930211540.GA25473@megas.kitwarein.com> References: <20140930150356.GC12969@megas.kitwarein.com> <20140930154210.GA6846@megas.kitwarein.com> <20140930211540.GA25473@megas.kitwarein.com> Message-ID: Classification: UNCLASSIFIED Caveats: NONE Ben, Have we talked about how to make the changes? The network setting at ARL is not letting me through the link... Thanks -simon -----Original Message----- From: Ben Boeckel [mailto:ben.boeckel at kitware.com] Sent: Tuesday, September 30, 2014 5:16 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) On Tue, Sep 30, 2014 at 19:36:13 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > can I safely ignore the error? Can we assume the binary installation > is complete? or are there additional installation steps after appdata > step that is needed for a proper ParaView binary installation? If so, > how do I get around it? There are probably more files which need installed after the appdata, but making the changes in the changeset should allow your "make install" from the superbuild to complete fully. Once that happens, the install should be fine. --Ben Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Sep 30 20:33:17 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 20:33:17 -0400 Subject: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) In-Reply-To: References: <20140930150356.GC12969@megas.kitwarein.com> <20140930154210.GA6846@megas.kitwarein.com> <20140930211540.GA25473@megas.kitwarein.com> Message-ID: Simon, Attached is a patch. It basically disables the "install" failing components with the Qt components are not being built. Let me know if that works and I can have these changes merged into the repository. Utkarsh On Tue, Sep 30, 2014 at 5:24 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Ben, > > Have we talked about how to make the changes? The network setting at ARL is > not letting me through the link... > > Thanks > -simon > > -----Original Message----- > From: Ben Boeckel [mailto:ben.boeckel at kitware.com] > Sent: Tuesday, September 30, 2014 5:16 PM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) > > On Tue, Sep 30, 2014 at 19:36:13 +0000, Su, Simon M CTR USARMY ARL (US) wrote: >> can I safely ignore the error? Can we assume the binary installation >> is complete? or are there additional installation steps after appdata >> step that is needed for a proper ParaView binary installation? If so, >> how do I get around it? > > There are probably more files which need installed after the appdata, but > making the changes in the changeset should allow your "make install" > from the superbuild to complete fully. Once that happens, the install should > be fine. > > --Ben > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: SuperBuild.patch Type: text/x-patch Size: 1663 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Sep 30 21:55:51 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 21:55:51 -0400 Subject: [Paraview] HOWto create / extend sources? In-Reply-To: <542AF1F6.4050901@xs4all.nl> References: <5426BC2D.7000505@xs4all.nl> <542AF1F6.4050901@xs4all.nl> Message-ID: Bert, The problem is the CMakeLists.txt. The sphBoxSource needs to be added as SERVER_MANAGER_SOURCES, not SOURCES. A a rule of thumb, if it's a vtkObject subclass and not a Qt class, you generally want to put that under SERVER_MANAGER_SOURCES. This ensure that it will get wrapped so that ParaView can instantiate classes through their names defined in the XML. Utkarsh On Tue, Sep 30, 2014 at 2:09 PM, B.W.H. van Beest wrote: > Utkash, > > I followed-up on your suggestions, but apparently I am doing something > wrong. I hope you or somebody else can point me to the solution. > > This is what I did. > > 1) new class: sphBoxSource. I extended class vtkCubeSource with one > data member, with corresponding get/set method. (Code below) > 2) I added an xml-file, with the source description taken from > source.xml (CubeSource). (Below) > 3) I modified the CMakeList.txt accordingly. (Below) > > Magically, the new source appeared in the menu. But when clicking it, > the program crashed. > The error message I get is: > > ERROR: In > /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, > line 307 > vtkSISourceProxy (0x30289e0): Failed to create sphBoxSource. Aborting > for debugging purposes. > > > I noticed that several people running into similar problems, but so far > I haven't been able to find the clue to the solution. > > > Before showing the code, I give the result of the compilation. > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > > chopin Plugins/SPHToolbar# make clean > chopin Plugins/SPHToolbar# make > [ 0%] Generating Documentation HTMLs from xmls > Processing wiki sources > Processing wiki filters > Processing wiki writers > Processing wiki readers > [ 10%] Generating qrc_sph_icons.cxx > [ 10%] Compiling Qt help project SPHToolbar.qhp > Building up file structure... > Insert custom filters... > Insert help data for filter section (1 of 1)... > Insert files... > Warning: The file > /usr/local/git/ParaView/build/Examples/All/Plugins/SPHToolbar/doc/*.css > does not exist! Skipping it. > Warning: The file > /usr/local/git/ParaView/build/Examples/All/Plugins/SPHToolbar/doc/*.png > does not exist! Skipping it. > Warning: The file > /usr/local/git/ParaView/build/Examples/All/Plugins/SPHToolbar/doc/*.jpg > does not exist! Skipping it. > Insert contents... > Insert indices... > Documentation successfully generated. > [ 10%] Generating SPHToolbar_doc.h > -- Generate module: SPHToolbar > [ 10%] Generating vtkSMXML_SPHToolbar.h > -- Generate module: sph_sources > [ 20%] Generating moc_SPHToolbarActions.cpp > [ 20%] Generating moc_sphBActionCreateSource.cpp > [ 30%] Generating moc_sphBAction.cpp > [ 30%] Generating moc_SPHToolbarActionsImplementation.cpp > [ 40%] Generating moc_SPHToolbar_Plugin.cpp > Scanning dependencies of target SPHToolbar > [ 50%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/qrc_sph_icons.o > [ 50%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_SPHToolbarActions.o > [ 60%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_sphBActionCreateSource.o > [ 60%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_sphBAction.o > [ 60%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/SPHToolbarActionsImplementation.o > [ 70%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_SPHToolbarActionsImplementation.o > [ 70%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/SPHToolbarActions.o > [ 80%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphBActionCreateSource.o > [ 80%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphBActionRegionInventory.o > [ 90%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphBoxSource.o > [ 90%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphUndoStack.o > [ 90%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphObjectTracer.o > [100%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/SPHToolbar_Plugin.o > [100%] Building CXX object > Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_SPHToolbar_Plugin.o > Linking CXX shared library > /usr/local/git/ParaView/build/lib/libSPHToolbar.so > [100%] Built target SPHToolbar > chopin Plugins/SPHToolbar# > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > > > > > > > > > > > ====================================================== > Here is the new class: > > #include "vtkCubeSource.h" > class sphBoxSource : public vtkCubeSource > { > private: > int _type; > > public: > static sphBoxSource *New(); // Monkey > see, monkey do ?????????????? > vtkTypeMacro(sphBoxSource,vtkCubeSource); // Monkey see, monkey > do ?????????????? > > public: > sphBoxSource( double=1.0, double=1.0, double=1.0 ); > ~sphBoxSource(); > > public: > void setType( int ); > int getType() const; > }; > ============================================================ > > XML-file "sph_sources.xml": (adapted from sources.xml) > ============================================================ > > > label="SPHBox" > name="SPHBoxSource"> > short_help="3D box with specified X, Y, and Z > lengths">The > Box source can be used to add a box to the 3D > scene. The > output of the Box source is polygonal data > containing both > normals and texture coordinates. > command="SetXLength" > default_values="1.0" > name="XLength" > number_of_elements="1" > panel_visibility="default"> > name="range" /> > This property specifies the length of the box in > the X > direction. > > command="SetYLength" > default_values="1.0" > name="YLength" > number_of_elements="1" > panel_visibility="default"> > name="range" /> > This property specifies the length of the box in > the Y > direction. > > command="SetZLength" > default_values="1.0" > name="ZLength" > number_of_elements="1" > panel_visibility="default"> > name="range" /> > This property specifies the length of the box in > the Z > direction. > > command="SetCenter" > default_values="0.0 0.0 0.0" > name="Center" > number_of_elements="3" > panel_visibility="default"> > > This property specifies the center of the > box. > > > > > > ====================================================================== > > Finally, the CMakeList.txt reads: > ====================================================================== > > CMAKE_MINIMUM_REQUIRED(VERSION 2.4) > > IF(NOT ParaView_BINARY_DIR) > FIND_PACKAGE(ParaView REQUIRED) > INCLUDE(${PARAVIEW_USE_FILE}) > ENDIF(NOT ParaView_BINARY_DIR) > > IF(PARAVIEW_BUILD_QT_GUI) > # We need to wrap for Qt stuff such as signals/slots etc. to work > correctly. > IF (PARAVIEW_QT_VERSION VERSION_GREATER "4") > QT5_WRAP_CPP(MOC_SRCS SPHToolbarActions.h sphBActionCreateSource.h > sphBAction.h ) > ELSE () > QT4_WRAP_CPP(MOC_SRCS SPHToolbarActions.h sphBActionCreateSource.h > sphBAction.h ) > ENDIF () > > # This is a macro for adding QActionGroup subclasses automatically as > toolbars. > ADD_PARAVIEW_ACTION_GROUP(IFACES IFACE_SRCS > CLASS_NAME SPHToolbarActions > GROUP_NAME "ToolBar/SPHToolbar") > > # Now create a plugin for the toolbar. Here we pass IFACES and IFACE_SRCS > # which are filled up by the above macro with relevant entries > ADD_PARAVIEW_PLUGIN(SPHToolbar "1.0" > GUI_INTERFACES ${IFACES} > GUI_RESOURCES sph_icons.qrc > SERVER_MANAGER_XML sph_sources.xml > SOURCES ${MOC_SRCS} ${IFACE_SRCS} > SPHToolbarActions.cpp > sphBActionCreateSource.cpp sphBActionRegionInventory.cpp > sphBoxSource.cpp > sphUndoStack.cpp sphObjectTracer.cpp ) > ENDIF(PARAVIEW_BUILD_QT_GUI) > > ====================================================================== > > On 09/29/2014 02:46 PM, Utkarsh Ayachit wrote: >>> a) How to create a new source ("MyNewSource") >> You define the 'proxy' under the "sources" group, rather than filters. >> It will automatically show up in the Menu. Look at sources.xml under >> [1] to see other source proxy definitions. >> >>> b) How can I extend an existing source (box, sphere, etc.) with new >>> properties and methods ("MyBox, "MySphere"). >> Similar to the filters, you basically need to write a new VTK >> algorithm with these new methods. You can subclass the existing VTK >> source. Looking at sources.xml, you can find out which proxy using >> which VTK algorithm, e.g. "SphereSource" (labelled as "Sphere") uses >> "vtkSphereSource". After adding the methods on the VTK algorithm, next >> part is exposing those methods as properties using the XML. >> >> [1] https://github.com/Kitware/ParaView/tree/master/ParaViewCore/ServerManager/SMApplication/Resources >> >>> Any help or suggestions are greatly appreciated. >>> >>> Kind Regards, >>> Bertwim >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Tue Sep 30 22:22:19 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 22:22:19 -0400 Subject: [Paraview] python programmable filter via xml with multiple input In-Reply-To: <220BE31773B69D4C985CA5660D992DB16D5BFAE6@ex-mbx-pro-03> References: <220BE31773B69D4C985CA5660D992DB16D5BF8CB@ex-mbx-pro-03> <220BE31773B69D4C985CA5660D992DB16D5BFAE6@ex-mbx-pro-03> Message-ID: Ah, sorry I missed that. Yea, if you want to simply use the vtkPythonProgrammableFilter, I'm afraid you'll have to stick with 1 input port accepting multiple connections, rather than separate input ports. Thus, you'll need to change your XML to just have 1 , however you can set the "multiple_input" attribute to make to accept multiple input connections on the same port. ... Hope that helps. Utkarsh On Mon, Sep 29, 2014 at 6:35 PM, Fraser Callaghan wrote: > Thanks for the clarification. I had tried this with the following error: > vtkPythonProgrammableFilter (0x5458a60): Attempt to connect input port > index 1 for an algorithm with 1 input ports. > > I gather that 'SetNumberOfInputPorts()' should be called in the > constructor of the filter, which I gather is governed by the xml file? > > If so, how can I expose editing of the algorithm constructor via the xml > file? > > Thanks, > Fraser > > > > > On Mon, 2014-09-29 at 08:48 -0400, Utkarsh Ayachit wrote: >> In your example, your XML is setup to provide the inputs on multiple >> "ports", while you're code is expecting multiple "connections" on same >> port. Use the following script, instead. >> >> print self.GetInputDataObject(0, 0).GetNumberOfPoints() >> print self.GetInputDataObject(1, 0).GetNumberOfPoints() >> >> Utkarsh >> >> On Sat, Sep 27, 2014 at 8:10 AM, Fraser Callaghan >> wrote: >> > Hi, >> > >> > I am able to run a python programmable filter accessing multiple inputs selected from the pipe line e.g: >> > # >> > numInputs = self.GetNumberOfInputConnections(0) >> > for i in range(numInputs): >> > print self.GetInputDataObject(0,i).GetNumberOfPoints() >> > ## >> > >> > I am able to use the xml format to define multiple inputs in a cleaner way, but can not access the input data (example below). >> > Changing "command" value does not help. >> > How should I be accessing the inputs available from the xml setup? >> > >> > Thanks for the help, >> > Fraser >> > >> > xml file: >> > >> > >> > >> > >> > >> > > > long_help="long help." >> > short_help="short help."> >> > >> > >> > > > name="Input0" >> > port_index="0" >> > command="SetInputConnection"> >> > >> > >> > >> > >> > >> > >> > >> > >> > Input data 0. >> > >> > >> > >> > > > name="Input1" >> > port_index="1" >> > command="SetInputConnection"> >> > >> > >> > >> > >> > >> > >> > >> > >> > Input data 1 >> > >> > >> > >> > >> > > > name="Script" >> > command="SetScript" >> > number_of_elements="1" >> > default_values="print 'Filter Working' print self.GetInputDataObject(0,0) #prints polydata print self.GetInputDataObject(0,1) #prints None " >> > panel_visibility="advanced"> >> > >> > >> > >> > This property contains the text of a python program that >> > the programmable source runs. >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > Error on loading: >> > >> > ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkAlgorithm.cxx, line 893 >> > vtkPythonProgrammableFilter (0x56aff30): Attempt to connect input port index 1 for an algorithm with 1 input ports. >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview > > -- > Dr Fraser Callaghan > Research Fellow > Sydney Translational Imaging Laboratory > Charles Perkins Centre > The University of Sydney > NSW 2006 Australia > p: 02 8627 1700 > e: fraser.callaghan at sydney.edu.au From fspaolo at gmail.com Tue Sep 30 22:22:11 2014 From: fspaolo at gmail.com (Fernando Paolo) Date: Tue, 30 Sep 2014 19:22:11 -0700 Subject: [Paraview] Problem installing Paraview 4.2 in Mac OSX 10.6 Message-ID: Hello, I am receiving an error message saying that Paraview version 4.2 is not compatible with my OSX system 10.6 (does not open after installation). -fernando -- Fernando Paolo Institute of Geophysics & Planetary Physics Scripps Institution of Oceanography University of California, San Diego web: fspaolo.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Sep 30 22:18:58 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 22:18:58 -0400 Subject: [Paraview] Edit Color Map In-Reply-To: References: Message-ID: Andres, Edit Color Map is not really the thing you're looking for, I think. Once you've set up a slice to a specific Z value for a tracer, you need to ensure that you're coloring with the appropriate array, "Tracer1", "Tracer2" and so on. Attached is state generated using ParaView 4.2. That renders 2 slices showing tracer 1 and 2 in separate views. Is that what you're looking for? Utkarsh On Tue, Sep 30, 2014 at 3:16 PM, Carlos Andr?s Bernal Castro wrote: > > To whom it may concern, > > Hello... my name is Andres Bernal and I am a London South Bank University > student carrying out a thesis about the influence of the buildings shape > onto the atmospheric pollutants concentration due to the innovative forms of > them nowadays. I am working on a building known as "The Walkie-Talkie > Building" and the third stage of the project was to read the simulations > (coming from Fluidity) . In order to move along with the project we need to > see/read the dispersion of pollutants (tracers) around the building (coming > from some sources that I set up, in this case/file, 7 sources which means 7 > Tracers ) with Paraview. When I set up a "Slice" in order to see such > dispersion at a certain height I cannot see anything and it seems to be this > could be worked out in the "Edit Color Map". I would like you to help me in > this issue as I have been trying to figure out the problem but I have not > been able to and I got stuck for this matter. I would be really grateful, > thanks. > > The heights of the tracers are: > > Tracer 1 = 0.3 > Tracer 2 = 0.5 > Tracer 3 = 0.7 > Tracer 4 = 0.3 > Tracer 5 = 0.8 > Tracer 6 = 0.5 > Tracer 7 = 0.762 > > The file attached below is a very simple scenario as I am working on several > more complex scenarios even with more buildings. I would just like you to > help me to sort out the colours issue to see the tracers, please. > > Any advice would be much appreciated. > > Kind Regards, > > Andres Bernal > > Carlos Andr?s Bernal Castro > Ingeniero Ambiental Y Sanitario > Universidad De La Salle > Carlos Andr?s tiene un archivo para compartir contigo en OneDrive. Para > verlo, haz clic en el siguiente v?nculo. > Walkie-Curved_29.vtu > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: Walkie.pvsm Type: application/octet-stream Size: 329157 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2014-09-30 22:18:38.png Type: image/png Size: 196738 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Sep 30 22:26:01 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 22:26:01 -0400 Subject: [Paraview] Problem installing Paraview 4.2 in Mac OSX 10.6 In-Reply-To: References: Message-ID: There are two OsX binaries available on the download page. Pick the 2'nd binary, suffixed with "Snow Leopard" for 10.6. http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.2&type=binary&os=osx&downloadFile=ParaView-4.2.0-Darwin-64bit-SnowLeopard.dmg On Tue, Sep 30, 2014 at 10:22 PM, Fernando Paolo wrote: > Hello, > > I am receiving an error message saying that Paraview version 4.2 is not > compatible with my OSX system 10.6 (does not open after installation). > > -fernando > > > -- > Fernando Paolo > Institute of Geophysics & Planetary Physics > Scripps Institution of Oceanography > University of California, San Diego > > web: fspaolo.net > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Tue Sep 30 22:30:27 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 22:30:27 -0400 Subject: [Paraview] paraview module In-Reply-To: References: Message-ID: Assuming Canopy is built with the same Python 2.7.1 version that we build our binaries against, you'll need to setup several environment variables. Attached is an old script I used for ParaView 4.1 (which was build with Python 2.6), but that'll give you hints for the variables and the paths in the app bundle that you'd need to point to. Utkarsh On Tue, Sep 30, 2014 at 2:51 AM, Ioannis Vogiatzis Oikonomidis wrote: > Hi > > I have canopy installed on my Mac > I would like to have paraview as a module to canopy my default python > installation > I have installed paraview using the dmg file > I have added almost all the folders from the contents folder to my path > When I am trying to > From paraview.simple import * > > I get the know error of > > dlopen(/Applications/paraview.app/Contents/Python/vtk/vtkCommonCorePython.so, > 2): Library not loaded: > @executable_path/../Libraries/libvtkCommonCorePython26D-pv4.1.1.dylib > > Referenced from: > /Applications/paraview.app/Contents/Python/vtk/vtkCommonCorePython.so > > Reason: image not found > > > Could someone help? > > > Thanks > > > Cheers > > Yannis > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: runPython26.sh Type: application/x-sh Size: 645 bytes Desc: not available URL: From fspaolo at gmail.com Tue Sep 30 22:39:24 2014 From: fspaolo at gmail.com (Fernando Paolo) Date: Tue, 30 Sep 2014 19:39:24 -0700 Subject: [Paraview] Problem installing Paraview 4.2 in Mac OSX 10.6 In-Reply-To: References: Message-ID: I am receiving the exact same error: Process: paraview [10851] Path: /Applications/paraview.app/Contents/MacOS/paraview Identifier: paraview Version: ??? (???) Code Type: X86-64 (Native) Parent Process: launchd [205] Date/Time: 2014-09-30 19:37:54.326 -0700 OS Version: Mac OS X 10.6.8 (10K549) Report Version: 6 Interval Since Last Report: 777959 sec Crashes Since Last Report: 6 Per-App Crashes Since Last Report: 4 Anonymous UUID: 85966E22-E0D4-4F86-BA2E-4F2130C9A4C5 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Crashed Thread: 0 Dyld Error Message: Library not loaded: /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation Referenced from: /Applications/paraview.app/Contents/MacOS/../Libraries/libavformat.55.48.100.dylib Reason: image not found Binary Images: 0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld On Tue, Sep 30, 2014 at 7:26 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > There are two OsX binaries available on the download page. Pick the > 2'nd binary, suffixed with "Snow Leopard" for 10.6. > > > http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.2&type=binary&os=osx&downloadFile=ParaView-4.2.0-Darwin-64bit-SnowLeopard.dmg > > On Tue, Sep 30, 2014 at 10:22 PM, Fernando Paolo > wrote: > > Hello, > > > > I am receiving an error message saying that Paraview version 4.2 is not > > compatible with my OSX system 10.6 (does not open after installation). > > > > -fernando > > > > > > -- > > Fernando Paolo > > Institute of Geophysics & Planetary Physics > > Scripps Institution of Oceanography > > University of California, San Diego > > > > web: fspaolo.net > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -- Fernando Paolo Institute of Geophysics & Planetary Physics Scripps Institution of Oceanography University of California, San Diego web: fspaolo.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Sep 30 22:43:33 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 22:43:33 -0400 Subject: [Paraview] Problem installing Paraview 4.2 in Mac OSX 10.6 In-Reply-To: References: Message-ID: Hmm...can you try downloading from the dashboard directly: http://open.cdash.org/viewFiles.php?buildid=3508570 Utkarsh On Tue, Sep 30, 2014 at 10:39 PM, Fernando Paolo wrote: > I am receiving the exact same error: > > Process: paraview [10851] > Path: /Applications/paraview.app/Contents/MacOS/paraview > Identifier: paraview > Version: ??? (???) > Code Type: X86-64 (Native) > Parent Process: launchd [205] > > Date/Time: 2014-09-30 19:37:54.326 -0700 > OS Version: Mac OS X 10.6.8 (10K549) > Report Version: 6 > > Interval Since Last Report: 777959 sec > Crashes Since Last Report: 6 > Per-App Crashes Since Last Report: 4 > Anonymous UUID: 85966E22-E0D4-4F86-BA2E-4F2130C9A4C5 > > Exception Type: EXC_BREAKPOINT (SIGTRAP) > Exception Codes: 0x0000000000000002, 0x0000000000000000 > Crashed Thread: 0 > > Dyld Error Message: > Library not loaded: > /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation > Referenced from: > /Applications/paraview.app/Contents/MacOS/../Libraries/libavformat.55.48.100.dylib > Reason: image not found > > Binary Images: > 0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) > <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld > > > On Tue, Sep 30, 2014 at 7:26 PM, Utkarsh Ayachit > wrote: >> >> There are two OsX binaries available on the download page. Pick the >> 2'nd binary, suffixed with "Snow Leopard" for 10.6. >> >> >> http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.2&type=binary&os=osx&downloadFile=ParaView-4.2.0-Darwin-64bit-SnowLeopard.dmg >> >> On Tue, Sep 30, 2014 at 10:22 PM, Fernando Paolo >> wrote: >> > Hello, >> > >> > I am receiving an error message saying that Paraview version 4.2 is not >> > compatible with my OSX system 10.6 (does not open after installation). >> > >> > -fernando >> > >> > >> > -- >> > Fernando Paolo >> > Institute of Geophysics & Planetary Physics >> > Scripps Institution of Oceanography >> > University of California, San Diego >> > >> > web: fspaolo.net >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > > > > > > -- > Fernando Paolo > Institute of Geophysics & Planetary Physics > Scripps Institution of Oceanography > University of California, San Diego > > web: fspaolo.net From fspaolo at gmail.com Tue Sep 30 22:47:24 2014 From: fspaolo at gmail.com (Fernando Paolo) Date: Tue, 30 Sep 2014 19:47:24 -0700 Subject: [Paraview] Problem installing Paraview 4.2 in Mac OSX 10.6 In-Reply-To: References: Message-ID: Isn't the Dashboard binary the one incompatible with OSX 10.6: ParaView-4.2.0-Darwin-64bit.dmg On Tue, Sep 30, 2014 at 7:43 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Hmm...can you try downloading from the dashboard directly: > > http://open.cdash.org/viewFiles.php?buildid=3508570 > > Utkarsh > > On Tue, Sep 30, 2014 at 10:39 PM, Fernando Paolo > wrote: > > I am receiving the exact same error: > > > > Process: paraview [10851] > > Path: /Applications/paraview.app/Contents/MacOS/paraview > > Identifier: paraview > > Version: ??? (???) > > Code Type: X86-64 (Native) > > Parent Process: launchd [205] > > > > Date/Time: 2014-09-30 19:37:54.326 -0700 > > OS Version: Mac OS X 10.6.8 (10K549) > > Report Version: 6 > > > > Interval Since Last Report: 777959 sec > > Crashes Since Last Report: 6 > > Per-App Crashes Since Last Report: 4 > > Anonymous UUID: 85966E22-E0D4-4F86-BA2E-4F2130C9A4C5 > > > > Exception Type: EXC_BREAKPOINT (SIGTRAP) > > Exception Codes: 0x0000000000000002, 0x0000000000000000 > > Crashed Thread: 0 > > > > Dyld Error Message: > > Library not loaded: > > /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation > > Referenced from: > > > /Applications/paraview.app/Contents/MacOS/../Libraries/libavformat.55.48.100.dylib > > Reason: image not found > > > > Binary Images: > > 0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) > > <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld > > > > > > On Tue, Sep 30, 2014 at 7:26 PM, Utkarsh Ayachit > > wrote: > >> > >> There are two OsX binaries available on the download page. Pick the > >> 2'nd binary, suffixed with "Snow Leopard" for 10.6. > >> > >> > >> > http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.2&type=binary&os=osx&downloadFile=ParaView-4.2.0-Darwin-64bit-SnowLeopard.dmg > >> > >> On Tue, Sep 30, 2014 at 10:22 PM, Fernando Paolo > >> wrote: > >> > Hello, > >> > > >> > I am receiving an error message saying that Paraview version 4.2 is > not > >> > compatible with my OSX system 10.6 (does not open after installation). > >> > > >> > -fernando > >> > > >> > > >> > -- > >> > Fernando Paolo > >> > Institute of Geophysics & Planetary Physics > >> > Scripps Institution of Oceanography > >> > University of California, San Diego > >> > > >> > web: fspaolo.net > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > > > > > > > > > > -- > > Fernando Paolo > > Institute of Geophysics & Planetary Physics > > Scripps Institution of Oceanography > > University of California, San Diego > > > > web: fspaolo.net > -- Fernando Paolo Institute of Geophysics & Planetary Physics Scripps Institution of Oceanography University of California, San Diego web: fspaolo.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Sep 30 23:17:34 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 30 Sep 2014 23:17:34 -0400 Subject: [Paraview] Problem installing Paraview 4.2 in Mac OSX 10.6 In-Reply-To: References: Message-ID: In theory, it shouldn't be. If it is, then we may have a configuration issue. I don't have immediate access to Snow Leopard to test it out. I am assuming it's not working for you even with the dashboard binary? Utkarsh On Tue, Sep 30, 2014 at 10:47 PM, Fernando Paolo wrote: > Isn't the Dashboard binary the one incompatible with OSX 10.6: > > ParaView-4.2.0-Darwin-64bit.dmg > > > > On Tue, Sep 30, 2014 at 7:43 PM, Utkarsh Ayachit > wrote: >> >> Hmm...can you try downloading from the dashboard directly: >> >> http://open.cdash.org/viewFiles.php?buildid=3508570 >> >> Utkarsh >> >> On Tue, Sep 30, 2014 at 10:39 PM, Fernando Paolo >> wrote: >> > I am receiving the exact same error: >> > >> > Process: paraview [10851] >> > Path: /Applications/paraview.app/Contents/MacOS/paraview >> > Identifier: paraview >> > Version: ??? (???) >> > Code Type: X86-64 (Native) >> > Parent Process: launchd [205] >> > >> > Date/Time: 2014-09-30 19:37:54.326 -0700 >> > OS Version: Mac OS X 10.6.8 (10K549) >> > Report Version: 6 >> > >> > Interval Since Last Report: 777959 sec >> > Crashes Since Last Report: 6 >> > Per-App Crashes Since Last Report: 4 >> > Anonymous UUID: >> > 85966E22-E0D4-4F86-BA2E-4F2130C9A4C5 >> > >> > Exception Type: EXC_BREAKPOINT (SIGTRAP) >> > Exception Codes: 0x0000000000000002, 0x0000000000000000 >> > Crashed Thread: 0 >> > >> > Dyld Error Message: >> > Library not loaded: >> > >> > /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation >> > Referenced from: >> > >> > /Applications/paraview.app/Contents/MacOS/../Libraries/libavformat.55.48.100.dylib >> > Reason: image not found >> > >> > Binary Images: >> > 0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) >> > <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld >> > >> > >> > On Tue, Sep 30, 2014 at 7:26 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> There are two OsX binaries available on the download page. Pick the >> >> 2'nd binary, suffixed with "Snow Leopard" for 10.6. >> >> >> >> >> >> >> >> http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.2&type=binary&os=osx&downloadFile=ParaView-4.2.0-Darwin-64bit-SnowLeopard.dmg >> >> >> >> On Tue, Sep 30, 2014 at 10:22 PM, Fernando Paolo >> >> wrote: >> >> > Hello, >> >> > >> >> > I am receiving an error message saying that Paraview version 4.2 is >> >> > not >> >> > compatible with my OSX system 10.6 (does not open after >> >> > installation). >> >> > >> >> > -fernando >> >> > >> >> > >> >> > -- >> >> > Fernando Paolo >> >> > Institute of Geophysics & Planetary Physics >> >> > Scripps Institution of Oceanography >> >> > University of California, San Diego >> >> > >> >> > web: fspaolo.net >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> > http://paraview.org/Wiki/ParaView >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview >> >> > >> > >> > >> > >> > >> > -- >> > Fernando Paolo >> > Institute of Geophysics & Planetary Physics >> > Scripps Institution of Oceanography >> > University of California, San Diego >> > >> > web: fspaolo.net > > > > > -- > Fernando Paolo > Institute of Geophysics & Planetary Physics > Scripps Institution of Oceanography > University of California, San Diego > > web: fspaolo.net From fspaolo at gmail.com Tue Sep 30 23:27:07 2014 From: fspaolo at gmail.com (Fernando Paolo) Date: Tue, 30 Sep 2014 20:27:07 -0700 Subject: [Paraview] Problem installing Paraview 4.2 in Mac OSX 10.6 In-Reply-To: References: Message-ID: Correct, Utkarsh. Not working with the dashboard either. -fernando On Tue, Sep 30, 2014 at 8:17 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > In theory, it shouldn't be. If it is, then we may have a configuration > issue. I don't have immediate access to Snow Leopard to test it out. I > am assuming it's not working for you even with the dashboard binary? > > Utkarsh > > On Tue, Sep 30, 2014 at 10:47 PM, Fernando Paolo > wrote: > > Isn't the Dashboard binary the one incompatible with OSX 10.6: > > > > ParaView-4.2.0-Darwin-64bit.dmg > > > > > > > > On Tue, Sep 30, 2014 at 7:43 PM, Utkarsh Ayachit > > wrote: > >> > >> Hmm...can you try downloading from the dashboard directly: > >> > >> http://open.cdash.org/viewFiles.php?buildid=3508570 > >> > >> Utkarsh > >> > >> On Tue, Sep 30, 2014 at 10:39 PM, Fernando Paolo > >> wrote: > >> > I am receiving the exact same error: > >> > > >> > Process: paraview [10851] > >> > Path: /Applications/paraview.app/Contents/MacOS/paraview > >> > Identifier: paraview > >> > Version: ??? (???) > >> > Code Type: X86-64 (Native) > >> > Parent Process: launchd [205] > >> > > >> > Date/Time: 2014-09-30 19:37:54.326 -0700 > >> > OS Version: Mac OS X 10.6.8 (10K549) > >> > Report Version: 6 > >> > > >> > Interval Since Last Report: 777959 sec > >> > Crashes Since Last Report: 6 > >> > Per-App Crashes Since Last Report: 4 > >> > Anonymous UUID: > >> > 85966E22-E0D4-4F86-BA2E-4F2130C9A4C5 > >> > > >> > Exception Type: EXC_BREAKPOINT (SIGTRAP) > >> > Exception Codes: 0x0000000000000002, 0x0000000000000000 > >> > Crashed Thread: 0 > >> > > >> > Dyld Error Message: > >> > Library not loaded: > >> > > >> > > /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation > >> > Referenced from: > >> > > >> > > /Applications/paraview.app/Contents/MacOS/../Libraries/libavformat.55.48.100.dylib > >> > Reason: image not found > >> > > >> > Binary Images: > >> > 0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) > >> > <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld > >> > > >> > > >> > On Tue, Sep 30, 2014 at 7:26 PM, Utkarsh Ayachit > >> > wrote: > >> >> > >> >> There are two OsX binaries available on the download page. Pick the > >> >> 2'nd binary, suffixed with "Snow Leopard" for 10.6. > >> >> > >> >> > >> >> > >> >> > http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.2&type=binary&os=osx&downloadFile=ParaView-4.2.0-Darwin-64bit-SnowLeopard.dmg > >> >> > >> >> On Tue, Sep 30, 2014 at 10:22 PM, Fernando Paolo > >> >> wrote: > >> >> > Hello, > >> >> > > >> >> > I am receiving an error message saying that Paraview version 4.2 is > >> >> > not > >> >> > compatible with my OSX system 10.6 (does not open after > >> >> > installation). > >> >> > > >> >> > -fernando > >> >> > > >> >> > > >> >> > -- > >> >> > Fernando Paolo > >> >> > Institute of Geophysics & Planetary Physics > >> >> > Scripps Institution of Oceanography > >> >> > University of California, San Diego > >> >> > > >> >> > web: fspaolo.net > >> >> > > >> >> > _______________________________________________ > >> >> > Powered by www.kitware.com > >> >> > > >> >> > Visit other Kitware open-source projects at > >> >> > http://www.kitware.com/opensource/opensource.html > >> >> > > >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> > http://paraview.org/Wiki/ParaView > >> >> > > >> >> > Follow this link to subscribe/unsubscribe: > >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> >> > > >> > > >> > > >> > > >> > > >> > -- > >> > Fernando Paolo > >> > Institute of Geophysics & Planetary Physics > >> > Scripps Institution of Oceanography > >> > University of California, San Diego > >> > > >> > web: fspaolo.net > > > > > > > > > > -- > > Fernando Paolo > > Institute of Geophysics & Planetary Physics > > Scripps Institution of Oceanography > > University of California, San Diego > > > > web: fspaolo.net > -- Fernando Paolo Institute of Geophysics & Planetary Physics Scripps Institution of Oceanography University of California, San Diego web: fspaolo.net -------------- next part -------------- An HTML attachment was scrubbed... URL: