From Matthias.Wiesenberger at uibk.ac.at Tue Dec 1 07:13:08 2015 From: Matthias.Wiesenberger at uibk.ac.at (Wiesenberger, Matthias) Date: Tue, 1 Dec 2015 12:13:08 +0000 Subject: [Paraview] netcdf-4 structured grid in paraview Message-ID: <4E5215E5BFF302498EEEE6D65C76C9B6420BD058@XMBX4.uibk.ac.at> Dear all, I've already sent this mail some weeks ago but I still haven't figured out a solution. I use netcdf-4 to write fields (density, temperature,...) in 3 dimensions to disk. These fields are given on a curvilinear grid (e.g. toroidal coordinates X,Y,Z). I have vectors containing the cartesian coordinates dependent on the curvilinear coordinates x(X,Y,Z), y(X,Y,Z), z(X,Y,Z) where x,y,z are cartesian coordinates and X,Y,Z are the curvilinear coordinates. The CF - conventions tell that these vectors should be written out as auxiliary coordinates and the variables that depend on them should have the auxiliary coordinates as an attribute. Now I cannot make paraview plot the fields correctly. When I read in the file it always shows me a rectangular box instead of a torus. I would like to know if there is a working example somewhere on the internet showing how to use netcdf and paraview to first write and then plot a field on a structured grid that is not a simple cartesian or spherical grid. (I spent some time searching for this topic on the net but I couldn't find anything useful) What do I have to do to make paraview recognize my auxiliary coordinates? Or in general how does paraview recognize a structured grid in a netcdf-4 file? Any hint would be very useful Thanks Matthias -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Tue Dec 1 08:48:05 2015 From: jfavre at cscs.ch (Favre Jean) Date: Tue, 1 Dec 2015 13:48:05 +0000 Subject: [Paraview] netcdf-4 structured grid in paraview In-Reply-To: <4E5215E5BFF302498EEEE6D65C76C9B6420BD058@XMBX4.uibk.ac.at> References: <4E5215E5BFF302498EEEE6D65C76C9B6420BD058@XMBX4.uibk.ac.at> Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F68435296F7@MBX111.d.ethz.ch> What you need can be simply implemented with a Python Programmable Filter, extracting the 3 coordinate arrays from the PointData fields, making a vector with algs.make_vector(), assigning it to output.Points, and appending all the other attributes from inputs[0].PointData if you supply a small test case, I could provide the python script. ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Tue Dec 1 10:36:30 2015 From: jfavre at cscs.ch (Favre Jean) Date: Tue, 1 Dec 2015 15:36:30 +0000 Subject: [Paraview] netcdf-4 structured grid in paraview In-Reply-To: <4E5215E5BFF302498EEEE6D65C76C9B6420BE085@XMBX4.uibk.ac.at> References: <4E5215E5BFF302498EEEE6D65C76C9B6420BD058@XMBX4.uibk.ac.at>, <0EB9B6375711A04B820E6B6F5CCA9F68435296F7@MBX111.d.ethz.ch>, <4E5215E5BFF302498EEEE6D65C76C9B6420BE085@XMBX4.uibk.ac.at> Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F68435297AA@MBX111.d.ethz.ch> I have tested the following solution which consists in using a Python programmable filter, copying the non-spatial data attributes, and creating a new coordinate array with the spatial attributes (x, x and z) see the included python code. I suggest using ParaView 4.4 or 5.0RC1. Note that the solution provided is independent of the input grid resolution, and that it ought to work in parallel too for large scale grids. I have tested it using 4 pvservers. Enjoy. ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cylindrical.py Type: text/x-python Size: 3359 bytes Desc: cylindrical.py URL: From sebastien.jourdain at kitware.com Tue Dec 1 11:15:52 2015 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Tue, 1 Dec 2015 09:15:52 -0700 Subject: [Paraview] ParaViewWeb JS API: get camera position In-Reply-To: References: Message-ID: I don't see any but you can add your own method such as @exportRpc("viewport.camera.get") def getCamera(self, view_id): view = self.getView(view_id) return { focal: view.CameraFocalPoint, up: view.CameraViewUp, position: view.CameraPosition } On Mon, Nov 30, 2015 at 5:06 PM, David Allen < david.allen at meliorinnovations.com> wrote: > I have been using the JavaScript API to set the camera position by calling > updateCamera() (registered as ?viewport.camera.update?). However, now I > would like to get the camera position after mouse events, etc. Is this > possible through the JavaScript API? I couldn?t find it in the docs. > > Thanks, > Dave > This e-mail is covered by the Electronic Communication Privacy Act, 18 > U.S.C. Section 2510-2521 and may be legally privileged. If you have > received this transmission in error, please notify the original sender > immediately by return e-mail or by telephone at the telephone number > provided above and delete/trash the original message from your system. > Thank you for your assistance. The information contained herein is > confidential information provided only for the use of the individual or > entity for whom it was intended. If the reader of this message received it > in error, is not the intended recipient, or if an attachment is made in > error, the reader is hereby notified that any dissemination, distribution > or copying of this communication is strictly prohibited. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.kospach at gmx.at Tue Dec 1 12:26:57 2015 From: a.kospach at gmx.at (Alexander Kospach) Date: Tue, 1 Dec 2015 18:26:57 +0100 Subject: [Paraview] Installing a new site-packages In-Reply-To: References: , Message-ID: An HTML attachment was scrubbed... URL: From david.lonie at kitware.com Tue Dec 1 13:56:29 2015 From: david.lonie at kitware.com (David Lonie) Date: Tue, 1 Dec 2015 13:56:29 -0500 Subject: [Paraview] Labels using mathtext notation In-Reply-To: References: Message-ID: Hi Steven, Thanks for the report. I've confirmed this issue and opened a bug for it: http://www.vtk.org/Bug/view.php?id=15859 I'll try to have this fixed soon, but in the meantime, it looks like adding some whitespace between the $$ (e.g. "$x $") will workaround the bug. Thanks, Dave On Tue, Nov 24, 2015 at 12:19 PM, Hahn, Steven E. wrote: > Hi, > > I am trying to generate a plot using ParaView v5.0.0-RC1 where the axes > contain mathtext labels. If the label is 2 or more characters long, then > everything is OK. If my label is one character only, it plots the $ signs. > > Here is a simple way to reproduce this issue: > - Use a sphere source. > - Show the axes > - Edit axes grid > - At the end of X Title string add ?$x$? > - At the end of Y Title string add ?$yy$? > > The X axis title is ?X Axis $x$?. The Y axis title is ?Y Axis yy? where yy > is italic. > > Best, > Steven Hahn > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From keinepostnurmuell at gmail.com Wed Dec 2 05:43:05 2015 From: keinepostnurmuell at gmail.com (no name) Date: Wed, 2 Dec 2015 11:43:05 +0100 Subject: [Paraview] Bug in the Animation export? Message-ID: Hi there I have an odd problem I am trying to come over, but so far with no success - I am using ParaView 4.4 and I have 200 Files I read in (*.INP) and I want to export an animation. The files themselves run through a pipeline, consisting of "Gradient of unstructured DataSet" and Calculators and some thresholds. All in all there are about a dozen filters applied. Now I start with INP 0001 and go to INP 0202 by hand -> all works fine. Now I start with INP 0001 and use "Export Animation" and at INP 0117 the picture does not change any more. From now on the picture stays, whatever I do in paraview, so if I go back to INP 0001 I still see INP 0117. Or it disappears completely. Has anyone an idea of how I could proceed? Thanks Richard From padamsen at grundfos.com Wed Dec 2 06:43:01 2015 From: padamsen at grundfos.com (Per Adamsen) Date: Wed, 2 Dec 2015 11:43:01 +0000 Subject: [Paraview] ParticleTracer filter makes Paraview crash on 'play' In-Reply-To: References: Message-ID: Hi Andy, This puzzles me? 1. I was following your steps but when I hit ?play? particles are only shown for initial timestep. 2. Particles disappear in the following timesteps and nothing is shown at all. 3. Returning to initial timestep makes paraview crash. Regards, Per From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: 30. november 2015 18:53 To: Per Adamsen Cc: paraview at paraview.org Subject: Re: [Paraview] ParticleTracer filter makes Paraview crash on 'play' Hi, I was able to get around this issue by doing the following: 1. Load your data set with just the U field 2. Use the Pass Arrays filter to only pass the U point data field. 3. Create a seed source (I used the line source) 4. Create the Particle Tracer filter Please let me know if this doesn't work for you. Best, Andy On Mon, Nov 23, 2015 at 10:18 AM, Andy Bauer > wrote: Hi, My guess is that it has to do with OpenFOAM's way of saving out extra fields for the initial time step. Several temporal filters assume that the arrays are ordered the same for different time steps but the OpenFOAM reader doesn't follow this convention. Can you share a data set that reproduces the issue? Andy On Mon, Nov 23, 2015 at 8:23 AM, Per Adamsen > wrote: Hi, I have been trying to visualize flow using the particle tracers as described at http://openfoamwiki.net/index.php/HowTo_use_particle_tracer_in_paraFoam. It works when using it on the cavity tutorial but when I try to transfer the setup to one of my own 3D OpenFOAM cases of a pump volute with e.g. 20 timesteps and 900,000 cells Paraview crashes with a segmentation fault when I hit the ?Play? button to step through the individual timesteps. The pipeline setup is exactly as described in the HowTo (linked above) and I have tried both with and without the Temporal Interpolator and on Linux and Windows platform ? all with the same crash result. I have tried the following 64-bit version: 3.98.1 on Win7 4.4.0 on Win7 4.2.0 on Linux HPC cluster At first I thought the reason for the crash was due to the use of interfaces in the model but I have tried a model without interfaces at all and the result is the same. Are there any restriction to the data which can be used? The following is the trace right up to pressing ?Play?: #### import the simple module from the paraview from paraview.simple import * #### disable automatic camera reset on 'Show' paraview.simple._DisableFirstRenderCameraReset() # get active source. q97_volutefoam = GetActiveSource() # Properties modified on q97_volutefoam q97_volutefoam.CaseType = 'Decomposed Case' # get active view renderView1 = GetActiveViewOrCreate('RenderView') # uncomment following to set a specific view size # renderView1.ViewSize = [1025, 773] # get color transfer function/color map for 'p' pLUT = GetColorTransferFunction('p') # show data in view q97_volutefoamDisplay = Show(q97_volutefoam, renderView1) # trace defaults for the display properties. q97_volutefoamDisplay.ColorArrayName = ['POINTS', 'p'] q97_volutefoamDisplay.LookupTable = pLUT q97_volutefoamDisplay.ScalarOpacityUnitDistance = 0.01089979797382614 q97_volutefoamDisplay.SelectInputVectors = ['POINTS', 'U'] q97_volutefoamDisplay.WriteLog = '' # reset view to fit data renderView1.ResetCamera() # show color bar/color legend q97_volutefoamDisplay.SetScalarBarVisibility(renderView1, True) # get animation scene animationScene1 = GetAnimationScene() # update animation scene based on data timesteps animationScene1.UpdateAnimationUsingDataTimeSteps() # get opacity transfer function/opacity map for 'p' pPWF = GetOpacityTransferFunction('p') # create a new 'Plane' plane1 = Plane() # Properties modified on q97_volutefoam q97_volutefoam.CellArrays = ['U', 'k', 'nut', 'omega', 'p', 'gradP', 'myPtot', 'myYPlus', 'uPlus', 'y', 'yPlus'] # Properties modified on plane1 plane1.XResolution = 100 plane1.YResolution = 100 # show data in view plane1Display = Show(plane1, renderView1) # trace defaults for the display properties. plane1Display.ColorArrayName = [None, ''] plane1Display.SelectInputVectors = ['POINTS', 'Normals'] plane1Display.WriteLog = '' # create a new 'ParticleTracer' particleTracer1 = ParticleTracer(Input=q97_volutefoam, SeedSource=plane1) particleTracer1.SelectInputVectors = ['POINTS', 'U'] # Properties modified on particleTracer1 particleTracer1.StaticSeeds = 1 particleTracer1.StaticMesh = 1 # show data in view particleTracer1Display = Show(particleTracer1, renderView1) # trace defaults for the display properties. particleTracer1Display.ColorArrayName = ['POINTS', 'p'] particleTracer1Display.LookupTable = pLUT particleTracer1Display.SelectInputVectors = ['POINTS', 'U'] particleTracer1Display.WriteLog = '' # hide data in view Hide(q97_volutefoam, renderView1) # hide data in view Hide(plane1, renderView1) # show color bar/color legend particleTracer1Display.SetScalarBarVisibility(renderView1, True) Regards, Per Adamsen _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Dec 2 10:13:45 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 2 Dec 2015 10:13:45 -0500 Subject: [Paraview] Blurred volume rendering In-Reply-To: References: Message-ID: Thomas, I am looking at your data in VTK. I will report back. In ParaView, you cannot choose linear or nearest as of now. We have a plan to expose all of the volume property parameters in ParaView (hopefully soon). Thanks, On Mon, Nov 30, 2015 at 3:06 PM, Thomas Oliveira wrote: > Dear Aashish, > > Can I choose the interpolation (linear vs nearest) or is it hard-coded on > the call of VTK from Paraview? > > A dataset can be downloaded from > http://www3.imperial.ac.uk/pls/portallive/docs/1/33505696.ZIP . > Please extract the Berea.raw file from the zip. > I loaded it using: > """ > Raw (binary) Files > Data Scalar Type: unsigned char > Data Byte Order: Little Endian > Data Extent: 0-399, 0-399, 0-399 > """ > > Thank you for your attention, > > Thomas Oliveira > > > On Mon, Nov 30, 2015 at 4:31 PM, Aashish Chaudhary < > aashish.chaudhary at kitware.com> wrote: > >> Thomas, >> >> >> >> On Mon, Nov 30, 2015 at 10:34 AM, Thomas Oliveira < >> thomas.oliveira at gmail.com> wrote: >> >>> Dear Aashish, >>> >>> >>> I'm using Paraview 4.4.0 64-bit , OpenGL Version 4.5.0 NVIDIA 352.55, >>> OpenGL Renderer Quadro K600/PCIe/SSE2. >>> >>> Tweaking the transfer function improved the result, but the corners are >>> rendererd rounded, whereas in the original file I have only cubic voxels. >>> >> >> I am wondering if that would be because of the interpolation (linear vs >> nearest) since linear will smooth out the edges just a bit. Is there a >> sample dataset you can send my way? >> >> >>> I though that unsetting "Properties > Scalar Coloring > Interpolate >>> Scalars Before Mapping" would improve the image, but I saw no change. >>> >>> You suggested to enable shading, but I couldn't find it. Where is it? >>> >> >> Its on the same panel (left side), scroll to the bottom or search for >> "shade" you should be see it. >> >> - aashish >> >>> >>> >>> Thank you for your help, >>> >>> Thomas Oliveira >>> >>> >>> On Mon, Nov 30, 2015 at 3:07 PM, Aashish Chaudhary < >>> aashish.chaudhary at kitware.com> wrote: >>> >>>> Hi Thomas, >>>> >>>> On Mon, Nov 30, 2015 at 8:54 AM, Thomas Oliveira < >>>> thomas.oliveira at gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> The Sample.png file attached is an image of a pore medium. Each voxel >>>>> in the image is a cube that is either solid or void. >>>>> >>>>> The Zoom.png file attached is a zoom of it, where it can be seen that >>>>> the curved interior solid walls are approximated by a staircase >>>>> discretization. >>>>> >>>>> How can I render this staircase geometry more clearly? >>>>> >>>> >>>> Did you try to tweak the transfer function? Also, you can enable >>>> shading to have a look of a solid surface. >>>> >>>> >>>>> I have tried tweaking many properties on ParaView but I still get it >>>>> blurred. >>>>> >>>> >>>> Just to be sure, what version of ParaView you are using and what OpenGL >>>> backend? >>>> >>>>> >>>>> Thank you for your help, >>>>> >>>>> Thomas Oliveira >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>>> * >>>> *| http://www.kitware.com/company/team/chaudhary.html >>>> * >>>> >>> >>> >> >> >> -- >> >> >> >> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >> * >> *| http://www.kitware.com/company/team/chaudhary.html >> * >> > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandre.ancel at cemosis.fr Wed Dec 2 11:47:59 2015 From: alexandre.ancel at cemosis.fr (Alexandre Ancel) Date: Wed, 2 Dec 2015 17:47:59 +0100 Subject: [Paraview] Catalyst: simulation steering during In-Situ visualization Message-ID: Hello, We are currently using Catalyst for In-Situ visualization in the context of our finite element library and it is working very well. We would like to implement simulation steering while using Catalyst. The idea would consist in having a ParaView plugin that we load in the ParaView client. Within the code of this plugin, we would like to send data to the simulation code to modify its behavior. First question: Is it possible to do so ? Then, How would the whole process be run ? The ideal scenario would be the following: - Launch ParaView & connect to the distant pverver & enable Catalyst - Load the plugin in ParaView - Launch the simulation - Receive data until timestep N then stop the simulation - Send data to the simulation through the loaded plugin - Continue with the simulation Would it be possible to do so ? If yes, could you give me keypoints about how to do this ? Thanks in advance for your answers, Best regards, Alexandre Ancel -- Alexandre Ancel Docteur, Ing?nieur de recherche / Phd, Research Engineer Cemosis - alexandre.ancel at cemosis.fr Tel: +33 (0)3 68 8*5 02 06* IRMA - 7, rue Ren? Descartes 67 000 Strasbourg, France -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Dec 2 11:59:24 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 2 Dec 2015 11:59:24 -0500 Subject: [Paraview] Blurred volume rendering In-Reply-To: References: Message-ID: Hi Thomas, Please find the attached image which I rendered using VTK code and in there I used nearest interpolation. Please let me know if this is what you expect. I will see if we can push a change to ParaView to expose this feature. Thanks, int TestGPURayCastVolumeUpdate(int argc, char *argv[]) { cout << "CTEST_FULL_OUTPUT (Avoid ctest truncation of output)" << endl; double scalarRange[2]; vtkNew outlineActor; vtkNew outlineMapper; vtkNew volumeMapper; vtkNew reader; reader->SetFilePrefix("/home/chaudhary/tools/paraview_main/Image/Berea.raw"); reader->SetFilePattern("%s"); reader->SetFileDimensionality(3); reader->SetDataByteOrderToLittleEndian(); reader->SetDataScalarTypeToUnsignedChar(); reader->SetDataExtent(0, 399, 0, 399, 0, 399); reader->SetFileLowerLeft(1); reader->SetDataOrigin(0, 0, 0); reader->SetDataSpacing(1.0, 1.0, 1.0); reader->SetInputArrayToProcess(0, 0, 0, vtkDataObject::FIELD_ASSOCIATION_POINTS, "ImageFile"); reader->Update(); volumeMapper->SetInputConnection(reader->GetOutputPort()); // Add outline filter vtkNew outlineFilter; outlineFilter->SetInputConnection(reader->GetOutputPort()); outlineMapper->SetInputConnection(outlineFilter->GetOutputPort()); outlineActor->SetMapper(outlineMapper.GetPointer()); volumeMapper->GetInput()->GetScalarRange(scalarRange); volumeMapper->SetAutoAdjustSampleDistances(0); volumeMapper->SetBlendModeToComposite(); vtkNew renWin; renWin->SetMultiSamples(0); renWin->SetSize(400, 400); vtkNew iren; iren->SetRenderWindow(renWin.GetPointer()); vtkNew style; iren->SetInteractorStyle(style.GetPointer()); renWin->Render(); // make sure we have an OpenGL context. vtkNew ren; ren->SetBackground(0.2, 0.2, 0.5); renWin->AddRenderer(ren.GetPointer()); vtkNew scalarOpacity; scalarOpacity->AddPoint(0.0, 0.0); scalarOpacity->AddPoint(0.4, 0.0); scalarOpacity->AddPoint(0.4, 0.1); scalarOpacity->AddPoint(1.0, 0.2); vtkNew volumeProperty; * volumeProperty->SetInterpolationType(VTK_NEAREST_INTERPOLATION);* volumeProperty->SetScalarOpacity(scalarOpacity.GetPointer()); volumeProperty->ShadeOn(); vtkNew colorTransferFunction; colorTransferFunction->RemoveAllPoints(); colorTransferFunction->AddRGBPoint(scalarRange[0], 0.6, 0.4, 0.4); colorTransferFunction->AddRGBPoint(scalarRange[1], 1.0, 1.0, 0.4); volumeProperty->SetColor(colorTransferFunction.GetPointer()); vtkNew volume; volume->SetMapper(volumeMapper.GetPointer()); volume->SetProperty(volumeProperty.GetPointer()); /// Add sphere in the center of volume int dims[3]; double spacing[3], center[3], origin[3]; reader->Update(); vtkSmartPointer im = reader->GetOutput(); im->GetDimensions(dims); im->GetOrigin(origin); im->GetSpacing(spacing); center[0] = origin[0] + spacing[0]*dims[0]/2.0; center[1] = origin[1] + spacing[1]*dims[1]/2.0; center[2] = origin[2] + spacing[2]*dims[2]/2.0; ren->AddVolume(volume.GetPointer()); ren->AddActor(outlineActor.GetPointer()); ren->ResetCamera(); renWin->Render(); iren->Initialize(); iren->Start(); } On Wed, Dec 2, 2015 at 10:13 AM, Aashish Chaudhary < aashish.chaudhary at kitware.com> wrote: > Thomas, > > I am looking at your data in VTK. I will report back. In ParaView, you > cannot choose linear or nearest as of now. We have a plan to expose all of > the volume property parameters in ParaView (hopefully soon). > > Thanks, > > > On Mon, Nov 30, 2015 at 3:06 PM, Thomas Oliveira < > thomas.oliveira at gmail.com> wrote: > >> Dear Aashish, >> >> Can I choose the interpolation (linear vs nearest) or is it hard-coded on >> the call of VTK from Paraview? >> >> A dataset can be downloaded from >> http://www3.imperial.ac.uk/pls/portallive/docs/1/33505696.ZIP . >> Please extract the Berea.raw file from the zip. >> I loaded it using: >> """ >> Raw (binary) Files >> Data Scalar Type: unsigned char >> Data Byte Order: Little Endian >> Data Extent: 0-399, 0-399, 0-399 >> """ >> >> Thank you for your attention, >> >> Thomas Oliveira >> >> >> On Mon, Nov 30, 2015 at 4:31 PM, Aashish Chaudhary < >> aashish.chaudhary at kitware.com> wrote: >> >>> Thomas, >>> >>> >>> >>> On Mon, Nov 30, 2015 at 10:34 AM, Thomas Oliveira < >>> thomas.oliveira at gmail.com> wrote: >>> >>>> Dear Aashish, >>>> >>>> >>>> I'm using Paraview 4.4.0 64-bit , OpenGL Version 4.5.0 NVIDIA 352.55, >>>> OpenGL Renderer Quadro K600/PCIe/SSE2. >>>> >>>> Tweaking the transfer function improved the result, but the corners are >>>> rendererd rounded, whereas in the original file I have only cubic voxels. >>>> >>> >>> I am wondering if that would be because of the interpolation (linear vs >>> nearest) since linear will smooth out the edges just a bit. Is there a >>> sample dataset you can send my way? >>> >>> >>>> I though that unsetting "Properties > Scalar Coloring > Interpolate >>>> Scalars Before Mapping" would improve the image, but I saw no change. >>>> >>>> You suggested to enable shading, but I couldn't find it. Where is it? >>>> >>> >>> Its on the same panel (left side), scroll to the bottom or search for >>> "shade" you should be see it. >>> >>> - aashish >>> >>>> >>>> >>>> Thank you for your help, >>>> >>>> Thomas Oliveira >>>> >>>> >>>> On Mon, Nov 30, 2015 at 3:07 PM, Aashish Chaudhary < >>>> aashish.chaudhary at kitware.com> wrote: >>>> >>>>> Hi Thomas, >>>>> >>>>> On Mon, Nov 30, 2015 at 8:54 AM, Thomas Oliveira < >>>>> thomas.oliveira at gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> The Sample.png file attached is an image of a pore medium. Each voxel >>>>>> in the image is a cube that is either solid or void. >>>>>> >>>>>> The Zoom.png file attached is a zoom of it, where it can be seen that >>>>>> the curved interior solid walls are approximated by a staircase >>>>>> discretization. >>>>>> >>>>>> How can I render this staircase geometry more clearly? >>>>>> >>>>> >>>>> Did you try to tweak the transfer function? Also, you can enable >>>>> shading to have a look of a solid surface. >>>>> >>>>> >>>>>> I have tried tweaking many properties on ParaView but I still get it >>>>>> blurred. >>>>>> >>>>> >>>>> Just to be sure, what version of ParaView you are using and what >>>>> OpenGL backend? >>>>> >>>>>> >>>>>> Thank you for your help, >>>>>> >>>>>> Thomas Oliveira >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> >>>>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>>>> * >>>>> *| http://www.kitware.com/company/team/chaudhary.html >>>>> * >>>>> >>>> >>>> >>> >>> >>> -- >>> >>> >>> >>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>> * >>> *| http://www.kitware.com/company/team/chaudhary.html >>> * >>> >> >> > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. * > *| http://www.kitware.com/company/team/chaudhary.html > * > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sc.png Type: image/png Size: 22560 bytes Desc: not available URL: From tim.gallagher at gatech.edu Wed Dec 2 12:02:28 2015 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Wed, 2 Dec 2015 12:02:28 -0500 (EST) Subject: [Paraview] Catalyst: simulation steering during In-Situ visualization In-Reply-To: Message-ID: <410086627.18066958.1449075748216.JavaMail.root@mail.gatech.edu> Hi Alexandre, I don't know if this is possible or not with Catalyst, hopefully somebody else comes along to answer that. But, we did this in our code using signal handling and POSIX signals (see http://man7.org/linux/man-pages/man7/signal.7.html). We define 3 behaviors in our code -- reload the input file and change simulation behavior accordingly; create a restart file at the next available chance and keep running; create a restart file and exit immediately. We use SIGUSR1 and SIGUSR2 for the first two options and then we use SIGTERM for the last behavior. This is helpful because most queue systems on HPC clusters will send SIGTERM 60 seconds before your wall-time is about to run out, so catching that signal and using it to write a restart file and exit means we always get our data right before our job runs out of time. Signals can be sent locally using `kill` or can be sent through PBS using `qsig`. It works quite nicely. Tim ----- Original Message ----- From: "Alexandre Ancel" To: "paraview" Sent: Wednesday, December 2, 2015 11:47:59 AM Subject: [Paraview] Catalyst: simulation steering during In-Situ visualization Hello, We are currently using Catalyst for In-Situ visualization in the context of our finite element library and it is working very well. We would like to implement simulation steering while using Catalyst. The idea would consist in having a ParaView plugin that we load in the ParaView client. Within the code of this plugin, we would like to send data to the simulation code to modify its behavior. First question: Is it possible to do so ? Then, How would the whole process be run ? The ideal scenario would be the following: - Launch ParaView & connect to the distant pverver & enable Catalyst - Load the plugin in ParaView - Launch the simulation - Receive data until timestep N then stop the simulation - Send data to the simulation through the loaded plugin - Continue with the simulation Would it be possible to do so ? If yes, could you give me keypoints about how to do this ? Thanks in advance for your answers, Best regards, Alexandre Ancel -- Alexandre Ancel Docteur, Ing?nieur de recherche / Phd, Research Engineer Ce mosis - alexandre.ancel at cemosis.fr Tel: +33 (0)3 68 8 5 02 06 IRMA - 7, rue Ren? Descartes 67 000 Strasbourg, 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Dec 2 12:45:11 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 2 Dec 2015 17:45:11 +0000 Subject: [Paraview] [EXTERNAL] Bug in the Animation export? In-Reply-To: References: Message-ID: That is strange. Can you pass the dataset, along with good directions, to Kitware? Write up a bug report? To get around your specific issue, one idea would be to do it in multiple steps. In other words: * Set up visualization. * Save state file * Save Animation for timesteps 0 through 99 as .png files * kill, reload ParaView * Load state file. If camera angle has changed, save and restore camera angle. * Save Animation for timesteps 100 through 199 as .png files * Stitch all .png files together into a movie. Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of no name Sent: Wednesday, December 02, 2015 3:43 AM To: ParaView Subject: [EXTERNAL] [Paraview] Bug in the Animation export? Hi there I have an odd problem I am trying to come over, but so far with no success - I am using ParaView 4.4 and I have 200 Files I read in (*.INP) and I want to export an animation. The files themselves run through a pipeline, consisting of "Gradient of unstructured DataSet" and Calculators and some thresholds. All in all there are about a dozen filters applied. Now I start with INP 0001 and go to INP 0202 by hand -> all works fine. Now I start with INP 0001 and use "Export Animation" and at INP 0117 the picture does not change any more. From now on the picture stays, whatever I do in paraview, so if I go back to INP 0001 I still see INP 0117. Or it disappears completely. Has anyone an idea of how I could proceed? Thanks Richard _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From andy.bauer at kitware.com Wed Dec 2 12:47:46 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 2 Dec 2015 12:47:46 -0500 Subject: [Paraview] Catalyst: simulation steering during In-Situ visualization In-Reply-To: <410086627.18066958.1449075748216.JavaMail.root@mail.gatech.edu> References: <410086627.18066958.1449075748216.JavaMail.root@mail.gatech.edu> Message-ID: Yes, it should be doable in ParaView through a plugin. The vtkCPDataDescription class has a UserData member that is a vtkFieldData pointer which can be used to pass information back and forth between the Catalyst pipelines and the adaptor. It's also Python wrapped so it's available in the Catalyst Python pipeline scripts as well. In the adaptor you would have to know how to process that data to your computational steering on the simulation side (i.e. take the Catalyst input). There may be a simple hack for the live connection to pass information from the GUI back to Catalyst in which case you might not even need a plugin. Otherwise, you should probably look at the code for the live connection (i.e. the stuff under the Catalyst GUI menu) to see how to pass other information back and forth between the GUI and Catalyst. On Wed, Dec 2, 2015 at 12:02 PM, Tim Gallagher wrote: > Hi Alexandre, > > I don't know if this is possible or not with Catalyst, hopefully somebody > else comes along to answer that. > > But, we did this in our code using signal handling and POSIX signals (see > http://man7.org/linux/man-pages/man7/signal.7.html). We define 3 > behaviors in our code -- reload the input file and change simulation > behavior accordingly; create a restart file at the next available chance > and keep running; create a restart file and exit immediately. We use > SIGUSR1 and SIGUSR2 for the first two options and then we use SIGTERM for > the last behavior. This is helpful because most queue systems on HPC > clusters will send SIGTERM 60 seconds before your wall-time is about to run > out, so catching that signal and using it to write a restart file and exit > means we always get our data right before our job runs out of time. > > Signals can be sent locally using `kill` or can be sent through PBS using > `qsig`. It works quite nicely. > > Tim > > ------------------------------ > *From: *"Alexandre Ancel" > *To: *"paraview" > *Sent: *Wednesday, December 2, 2015 11:47:59 AM > *Subject: *[Paraview] Catalyst: simulation steering during > In-Situ visualization > > > Hello, > > We are currently using Catalyst for In-Situ visualization in the context > of our finite element library and it is working very well. > > We would like to implement simulation steering while using Catalyst. > The idea would consist in having a ParaView plugin that we load in the > ParaView client. Within the code of this plugin, we would like to send data > to the simulation code to modify its behavior. > > First question: Is it possible to do so ? > Then, How would the whole process be run ? > The ideal scenario would be the following: > - Launch ParaView & connect to the distant pverver & enable Catalyst > - Load the plugin in ParaView > - Launch the simulation > - Receive data until timestep N then stop the simulation > - Send data to the simulation through the loaded plugin > - Continue with the simulation > Would it be possible to do so ? If yes, could you give me keypoints about > how to do this ? > > Thanks in advance for your answers, > > Best regards, > Alexandre Ancel > > -- > Alexandre Ancel > Docteur, Ing?nieur de recherche / Phd, Research Engineer > Cemosis - alexandre.ancel at cemosis.fr > Tel: +33 (0)3 68 8*5 02 06* > IRMA - 7, rue Ren? Descartes > 67 000 Strasbourg, France > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Dec 2 15:25:27 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 2 Dec 2015 15:25:27 -0500 Subject: [Paraview] Rendering offscreen images from parallel simulation using Catalyst In-Reply-To: <201511251728.tAPHS3Si029006@msw1.awe.co.uk> References: <201511251728.tAPHS3Si029006@msw1.awe.co.uk> Message-ID: Hi Jim, I think at this point the best option is to build Catalyst with OSMesa. Cheers, Andy ps. I cc'ed the mailing list in case someone else has a better answer than mine. On Wed, Nov 25, 2015 at 12:28 PM, wrote: > Hi Andy, > > > > Thank you for your reply. > > > > I seem to get the same behaviour with pvbatch. When I run in parallel > using pvbatch like so: > > > > mpirun -np 4 pvbatch ./myscript.py > > > > Four windows are created. The outputted image file from the script is > incomplete. > > > > If I use the --use-offscreen-rendering option like so: > > > > mpirun -np 4 pvbatch --use-offscreen-rendering ./myscript.py > > > > no windows appear and the final image looks correct. > > > > Should I build ParaView with osmesa for use with my Catalyst simulations? > > > > Kind regards, > > Jim > > > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com] > *Sent:* 25 November 2015 15:30 > *To:* Eliot Jim AWE > *Cc:* paraview at paraview.org > *Subject:* EXTERNAL: Re: [Paraview] Rendering offscreen images from > parallel simulation using Catalyst > > > > Hi Jim, > > You can use OSMesa if you want offscreen rendering to work. There has been > some work with EGL with NVIDIA but I haven't tried that yet myself since I > don't have the EGL libraries on my machine. Intel's OpenSWR may also be an > option but I haven't tried that either. > > > > I think this issue though is independent of Catalyst. Can you try creating > a Python script that outputs an image and try running that in parallel with > pvbatch? Let me know if you get the same behaviour or not. > > Cheers, > > Andy > > > > On Tue, Nov 24, 2015 at 6:04 AM, wrote: > > > > Good morning all, > > > > I have experienced some problems when trying to render images in parallel > from a multipiece dataset using ParaView Catalyst. It seems to work when I > connect live using the ParaView client ? I see the full mesh, and a plot of > vtkCompositeIndex looks sensible. > > > > However when I try to render out images, one render window appears on > screen for each parallel process (in a stack). The windows appear to > contain one chunk each. If I manually grab the windows and spread them out > so that each is visible on screen, then chunk zero plots updates to include > the whole dataset, i.e. it looks as if it is grabbing the data from the > screen. > > > > Is there a way to make ParaView Catalyst render offscreen? > > > > I am using ParaView 4.4.0 on my workstation (which has a graphics card) > built from source using Superbuild without mesa. > > > > When I run on a remote platform (no graphics cards) where I build ParaView > using osmesa, the images render without creating a window and contain all > the chunks. > > > > Should I be using a separate ParaView build for my Catalyst simulations > that is built with osmesa? > > > > Apologies if there is not much to go on here ? it would be tricky to share > the simulation code and the catalyst adaptor code that I am using. If more > information is needed, I?ll try to put together a representative > simulation/adaptor. > > > > Thanks everyone, > > Jim > > > > > > *Jim Eliot* > > *High Performance Computing Group* > > AWE, Aldermaston, Reading, RG7 4PR > > > > The information in this email and in any attachment(s) is commercial in > confidence. If you are not the named addressee(s) or if you receive this > email in error then any distribution, copying or use of this communication > or the information in it is strictly prohibited. Please notify us > immediately by email at admin.internet(at)awe.co.uk, and then delete this > message from your computer. While attachments are virus checked, AWE plc > does not accept any liability in respect of any virus which is not > detected. AWE Plc Registered in England and Wales Registration No 02763902 > AWE, Aldermaston, Reading, RG7 4PR > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > The information in this email and in any attachment(s) is commercial in > confidence. If you are not the named addressee(s) or if you receive this > email in error then any distribution, copying or use of this communication > or the information in it is strictly prohibited. Please notify us > immediately by email at admin.internet(at)awe.co.uk, and then delete this > message from your computer. While attachments are virus checked, AWE plc > does not accept any liability in respect of any virus which is not > detected. AWE Plc Registered in England and Wales Registration No 02763902 > AWE, Aldermaston, Reading, RG7 4PR > -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonardopessanha74 at gmail.com Wed Dec 2 16:07:38 2015 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Wed, 2 Dec 2015 19:07:38 -0200 Subject: [Paraview] Write data with date and time in the name so PV recognizes as TimeSeries Message-ID: Hello everyone, I've been trying to do the following: - Write some data like: foo01_01_2013_00_00_00.vtk foo01_01_2013_06_00_00.vtk foo01_01_2013_12_00_00.vtk foo01_01_2013_18_00_00.vtk foo02_01_2013_00_00_00.vtk foo02_01_2013_06_00_00.vtk foo02_01_2013_12_00_00.vtk foo02_01_2013_18_00_00.vtk Template: foo[day]_[month]_[year]_[hour]_[minute]_[second] In a way that paraview recognizes as file series. But I can't get it done. Can someone help me? The wiki says the following: ParaView recognizes file series named using certain patterns including: - foo*N*.vtk - foo_*N*.vtk - foo-*N*.vtk - foo.*N*.vtk - *N*foo.vtk - *N*.foo.vtk - foo.vtk.*N* - foo.vtk-s*N* Where N is an integer (with any number of leading zeros). To load a file series, first make sure that the file names match one of the patterns described above. Next, navigate to the directory where the file series is. The file browser should look like this: -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Thu Dec 3 00:31:44 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Thu, 3 Dec 2015 00:31:44 -0500 Subject: [Paraview] Blurred volume rendering In-Reply-To: References: Message-ID: Dear Thomas, If it is possible for you to build ParaView from master (as of today) with OpenGL2 backend, then apply this patch (attached) and see if this works for you. This might work on older version or OpenGL1 backend but I haven't tested it, so use at your risk. Once applied and build, you can find for "Interpolation" option in advance search box. It will show "Nearest, Linear, and Cubic". Thanks, On Wed, Dec 2, 2015 at 11:59 AM, Aashish Chaudhary < aashish.chaudhary at kitware.com> wrote: > Hi Thomas, > > Please find the attached image which I rendered using VTK code and in > there I used nearest interpolation. Please let me know if this is what you > expect. I will see if we can push a change to ParaView to expose this > feature. > > Thanks, > > > int TestGPURayCastVolumeUpdate(int argc, char *argv[]) > > { > > cout << "CTEST_FULL_OUTPUT (Avoid ctest truncation of output)" << endl; > > > double scalarRange[2]; > > > vtkNew outlineActor; > > vtkNew outlineMapper; > > vtkNew volumeMapper; > > > vtkNew reader; > > reader->SetFilePrefix("/home/chaudhary/tools/paraview_main/Image/Berea.raw"); > > reader->SetFilePattern("%s"); > > reader->SetFileDimensionality(3); > > reader->SetDataByteOrderToLittleEndian(); > > reader->SetDataScalarTypeToUnsignedChar(); > > reader->SetDataExtent(0, 399, 0, 399, 0, 399); > > reader->SetFileLowerLeft(1); > > reader->SetDataOrigin(0, 0, 0); > > reader->SetDataSpacing(1.0, 1.0, 1.0); > > reader->SetInputArrayToProcess(0, 0, 0, vtkDataObject::FIELD_ASSOCIATION_POINTS, "ImageFile"); > > reader->Update(); > > > volumeMapper->SetInputConnection(reader->GetOutputPort()); > > > // Add outline filter > > vtkNew outlineFilter; > > outlineFilter->SetInputConnection(reader->GetOutputPort()); > > outlineMapper->SetInputConnection(outlineFilter->GetOutputPort()); > > outlineActor->SetMapper(outlineMapper.GetPointer()); > > > volumeMapper->GetInput()->GetScalarRange(scalarRange); > > volumeMapper->SetAutoAdjustSampleDistances(0); > > volumeMapper->SetBlendModeToComposite(); > > > vtkNew renWin; > > renWin->SetMultiSamples(0); > > renWin->SetSize(400, 400); > > > vtkNew iren; > > iren->SetRenderWindow(renWin.GetPointer()); > > vtkNew style; > > iren->SetInteractorStyle(style.GetPointer()); > > > renWin->Render(); // make sure we have an OpenGL context. > > > vtkNew ren; > > ren->SetBackground(0.2, 0.2, 0.5); > > renWin->AddRenderer(ren.GetPointer()); > > > vtkNew scalarOpacity; > > scalarOpacity->AddPoint(0.0, 0.0); > > scalarOpacity->AddPoint(0.4, 0.0); > > scalarOpacity->AddPoint(0.4, 0.1); > > scalarOpacity->AddPoint(1.0, 0.2); > > > vtkNew volumeProperty; > > * volumeProperty->SetInterpolationType(VTK_NEAREST_INTERPOLATION);* > > volumeProperty->SetScalarOpacity(scalarOpacity.GetPointer()); > > volumeProperty->ShadeOn(); > > > vtkNew colorTransferFunction; > > colorTransferFunction->RemoveAllPoints(); > > colorTransferFunction->AddRGBPoint(scalarRange[0], 0.6, 0.4, 0.4); > > colorTransferFunction->AddRGBPoint(scalarRange[1], 1.0, 1.0, 0.4); > > volumeProperty->SetColor(colorTransferFunction.GetPointer()); > > > vtkNew volume; > > volume->SetMapper(volumeMapper.GetPointer()); > > volume->SetProperty(volumeProperty.GetPointer()); > > > /// Add sphere in the center of volume > > int dims[3]; > > double spacing[3], center[3], origin[3]; > > reader->Update(); > > vtkSmartPointer im = reader->GetOutput(); > > im->GetDimensions(dims); > > im->GetOrigin(origin); > > im->GetSpacing(spacing); > > > center[0] = origin[0] + spacing[0]*dims[0]/2.0; > > center[1] = origin[1] + spacing[1]*dims[1]/2.0; > > center[2] = origin[2] + spacing[2]*dims[2]/2.0; > > > ren->AddVolume(volume.GetPointer()); > > ren->AddActor(outlineActor.GetPointer()); > > ren->ResetCamera(); > > renWin->Render(); > > > iren->Initialize(); > > iren->Start(); > > } > > > On Wed, Dec 2, 2015 at 10:13 AM, Aashish Chaudhary < > aashish.chaudhary at kitware.com> wrote: > >> Thomas, >> >> I am looking at your data in VTK. I will report back. In ParaView, you >> cannot choose linear or nearest as of now. We have a plan to expose all of >> the volume property parameters in ParaView (hopefully soon). >> >> Thanks, >> >> >> On Mon, Nov 30, 2015 at 3:06 PM, Thomas Oliveira < >> thomas.oliveira at gmail.com> wrote: >> >>> Dear Aashish, >>> >>> Can I choose the interpolation (linear vs nearest) or is it hard-coded >>> on the call of VTK from Paraview? >>> >>> A dataset can be downloaded from >>> http://www3.imperial.ac.uk/pls/portallive/docs/1/33505696.ZIP . >>> Please extract the Berea.raw file from the zip. >>> I loaded it using: >>> """ >>> Raw (binary) Files >>> Data Scalar Type: unsigned char >>> Data Byte Order: Little Endian >>> Data Extent: 0-399, 0-399, 0-399 >>> """ >>> >>> Thank you for your attention, >>> >>> Thomas Oliveira >>> >>> >>> On Mon, Nov 30, 2015 at 4:31 PM, Aashish Chaudhary < >>> aashish.chaudhary at kitware.com> wrote: >>> >>>> Thomas, >>>> >>>> >>>> >>>> On Mon, Nov 30, 2015 at 10:34 AM, Thomas Oliveira < >>>> thomas.oliveira at gmail.com> wrote: >>>> >>>>> Dear Aashish, >>>>> >>>>> >>>>> I'm using Paraview 4.4.0 64-bit , OpenGL Version 4.5.0 NVIDIA 352.55, >>>>> OpenGL Renderer Quadro K600/PCIe/SSE2. >>>>> >>>>> Tweaking the transfer function improved the result, but the corners >>>>> are rendererd rounded, whereas in the original file I have only cubic >>>>> voxels. >>>>> >>>> >>>> I am wondering if that would be because of the interpolation (linear vs >>>> nearest) since linear will smooth out the edges just a bit. Is there a >>>> sample dataset you can send my way? >>>> >>>> >>>>> I though that unsetting "Properties > Scalar Coloring > Interpolate >>>>> Scalars Before Mapping" would improve the image, but I saw no change. >>>>> >>>>> You suggested to enable shading, but I couldn't find it. Where is it? >>>>> >>>> >>>> Its on the same panel (left side), scroll to the bottom or search for >>>> "shade" you should be see it. >>>> >>>> - aashish >>>> >>>>> >>>>> >>>>> Thank you for your help, >>>>> >>>>> Thomas Oliveira >>>>> >>>>> >>>>> On Mon, Nov 30, 2015 at 3:07 PM, Aashish Chaudhary < >>>>> aashish.chaudhary at kitware.com> wrote: >>>>> >>>>>> Hi Thomas, >>>>>> >>>>>> On Mon, Nov 30, 2015 at 8:54 AM, Thomas Oliveira < >>>>>> thomas.oliveira at gmail.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> The Sample.png file attached is an image of a pore medium. Each >>>>>>> voxel in the image is a cube that is either solid or void. >>>>>>> >>>>>>> The Zoom.png file attached is a zoom of it, where it can be seen >>>>>>> that the curved interior solid walls are approximated by a staircase >>>>>>> discretization. >>>>>>> >>>>>>> How can I render this staircase geometry more clearly? >>>>>>> >>>>>> >>>>>> Did you try to tweak the transfer function? Also, you can enable >>>>>> shading to have a look of a solid surface. >>>>>> >>>>>> >>>>>>> I have tried tweaking many properties on ParaView but I still get it >>>>>>> blurred. >>>>>>> >>>>>> >>>>>> Just to be sure, what version of ParaView you are using and what >>>>>> OpenGL backend? >>>>>> >>>>>>> >>>>>>> Thank you for your help, >>>>>>> >>>>>>> Thomas Oliveira >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> >>>>>> >>>>>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>>>>> * >>>>>> *| http://www.kitware.com/company/team/chaudhary.html >>>>>> * >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>>> * >>>> *| http://www.kitware.com/company/team/chaudhary.html >>>> * >>>> >>> >>> >> >> >> -- >> >> >> >> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >> * >> *| http://www.kitware.com/company/team/chaudhary.html >> * >> > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. * > *| http://www.kitware.com/company/team/chaudhary.html > * > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: expose_interpolation.patch Type: text/x-patch Size: 1133 bytes Desc: not available URL: From alexandre.ancel at cemosis.fr Thu Dec 3 03:59:54 2015 From: alexandre.ancel at cemosis.fr (Alexandre Ancel) Date: Thu, 3 Dec 2015 09:59:54 +0100 Subject: [Paraview] Catalyst: simulation steering during In-Situ visualization In-Reply-To: References: <410086627.18066958.1449075748216.JavaMail.root@mail.gatech.edu> Message-ID: Hello, @Tim: Thanks for the nice tips regarding to queue systems and signals on HPC clusters, I wasn't aware of that. I'll look into it on our local cluster, and we have a stop/restart method in our library, so it could work ! @Andy: Indeed I was aware of the UserData member, I already used it in fact. Do you have something specific in mind, when you say that there may be a simple hack for the live connection to pass information from the GUI back to Catalyst ? The main interest I see with using a plugin is to have flexibility regarding what the user can provide to the simulation. He could directly use the option format we define in the library and define those as graphical elements in the plugin. I'll definitely have at look at the code behind the Catalyst GUI, I guess the answer is behind. Thanks you ! Best regards, Alexandre Ancel On Wed, Dec 2, 2015 at 6:47 PM, Andy Bauer wrote: > Yes, it should be doable in ParaView through a plugin. The > vtkCPDataDescription class has a UserData member that is a vtkFieldData > pointer which can be used to pass information back and forth between the > Catalyst pipelines and the adaptor. It's also Python wrapped so it's > available in the Catalyst Python pipeline scripts as well. In the adaptor > you would have to know how to process that data to your computational > steering on the simulation side (i.e. take the Catalyst input). There may > be a simple hack for the live connection to pass information from the GUI > back to Catalyst in which case you might not even need a plugin. Otherwise, > you should probably look at the code for the live connection (i.e. the > stuff under the Catalyst GUI menu) to see how to pass other information > back and forth between the GUI and Catalyst. > > On Wed, Dec 2, 2015 at 12:02 PM, Tim Gallagher > wrote: > >> Hi Alexandre, >> >> I don't know if this is possible or not with Catalyst, hopefully somebody >> else comes along to answer that. >> >> But, we did this in our code using signal handling and POSIX signals (see >> http://man7.org/linux/man-pages/man7/signal.7.html). We define 3 >> behaviors in our code -- reload the input file and change simulation >> behavior accordingly; create a restart file at the next available chance >> and keep running; create a restart file and exit immediately. We use >> SIGUSR1 and SIGUSR2 for the first two options and then we use SIGTERM for >> the last behavior. This is helpful because most queue systems on HPC >> clusters will send SIGTERM 60 seconds before your wall-time is about to run >> out, so catching that signal and using it to write a restart file and exit >> means we always get our data right before our job runs out of time. >> >> Signals can be sent locally using `kill` or can be sent through PBS using >> `qsig`. It works quite nicely. >> >> Tim >> >> ------------------------------ >> *From: *"Alexandre Ancel" >> *To: *"paraview" >> *Sent: *Wednesday, December 2, 2015 11:47:59 AM >> *Subject: *[Paraview] Catalyst: simulation steering during >> In-Situ visualization >> >> >> Hello, >> >> We are currently using Catalyst for In-Situ visualization in the context >> of our finite element library and it is working very well. >> >> We would like to implement simulation steering while using Catalyst. >> The idea would consist in having a ParaView plugin that we load in the >> ParaView client. Within the code of this plugin, we would like to send data >> to the simulation code to modify its behavior. >> >> First question: Is it possible to do so ? >> Then, How would the whole process be run ? >> The ideal scenario would be the following: >> - Launch ParaView & connect to the distant pverver & enable Catalyst >> - Load the plugin in ParaView >> - Launch the simulation >> - Receive data until timestep N then stop the simulation >> - Send data to the simulation through the loaded plugin >> - Continue with the simulation >> Would it be possible to do so ? If yes, could you give me keypoints about >> how to do this ? >> >> Thanks in advance for your answers, >> >> Best regards, >> Alexandre Ancel >> >> -- >> Alexandre Ancel >> Docteur, Ing?nieur de recherche / Phd, Research Engineer >> Cemosis - alexandre.ancel at cemosis.fr >> Tel: +33 (0)3 68 8*5 02 06* >> IRMA - 7, rue Ren? Descartes >> 67 000 Strasbourg, France >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -- Alexandre Ancel Docteur, Ing?nieur de recherche / Phd, Research Engineer Cemosis - alexandre.ancel at cemosis.fr Tel: +33 (0)3 68 8*5 02 06* IRMA - 7, rue Ren? Descartes 67 000 Strasbourg, France -------------- next part -------------- An HTML attachment was scrubbed... URL: From apeczak at ara.co.uk Thu Dec 3 06:42:02 2015 From: apeczak at ara.co.uk (Andrzej Peczak) Date: Thu, 3 Dec 2015 11:42:02 +0000 Subject: [Paraview] Paraview 4.4.0 - Plugin with a custom 3d widget Message-ID: <5DF928D22AC3AC4B964903E98F2E54515A3D5CE4@sooty3.win.ara> Hi I am trying to customise a plugin with an implicit function widget. As an example I choose vtkPVBox class to check if I can register it under a different name. To do it I created a SM file as following, but the plugin seems not seeing the object I am registering. Can anybody explain how do I register my own widget ? Thanks Andrzej ********************************************************************** Please consider the environment. Only print this email if absolutely necessary. This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ********************************************************************** From svzj at centrum.cz Thu Dec 3 07:39:46 2015 From: svzj at centrum.cz (=?utf-8?q?Jiri_Vyskocil?=) Date: Thu, 03 Dec 2015 13:39:46 +0100 Subject: [Paraview] =?utf-8?q?Compiling_5=2E0=2E0-RC1_vit_VisItBridge_link?= =?utf-8?q?ing_failure_on_Fedora_23?= Message-ID: <20151203133946.94E9EF6C@centrum.cz> Hello, I'm trying to compile Paraview with MPI and VisIt bridge on Fedora 23 with OpenMPI. Paraview compiles, and runs fine without VisitBridge. If I enable the PARAVIEW_USE_VISITBRIDGE option (I'm using ccmake), I get the following error: [ 26%] Linking CXX shared library ../../../lib/libvtkIOVisItBridge-pv5.0.so CMakeFiles/vtkIOVisItBridge.dir/vtkVisItChomboReader.cxx.o: In function `MPI::Win::Set_name(char const*)': vtkVisItChomboReader.cxx:(.text._ZN3MPI3Win8Set_nameEPKc[_ZN3MPI3Win8Set_nameEPKc]+0x5): undefined reference to `MPI_Win_set_name' CMakeFiles/vtkIOVisItBridge.dir/vtkVisItChomboReader.cxx.o: In function `MPI::Win::Set_attr(int, void const*)': vtkVisItChomboReader.cxx:(.text._ZN3MPI3Win8Set_attrEiPKv[_ZN3MPI3Win8Set_attrEiPKv]+0x5): undefined reference to `MPI_Win_set_attr' ..... snip a couple hundred similar lines ..... vtkVisItChomboReader.cxx:(.text._ZNK3MPI9Intracomm6CreateERKNS_5GroupE[_ZNK3MPI9Intracomm6CreateERKNS_5GroupE]+0x6e): undefined reference to `ompi_mpi_comm_null' CMakeFiles/vtkIOVisItBridge.dir/vtkVisItChomboReader.cxx.o:(.data.rel.ro._ZTVN3MPI8DatatypeE[_ZTVN3MPI8DatatypeE]+0x78): undefined reference to `MPI::Datatype::Free()' CMakeFiles/vtkIOVisItBridge.dir/vtkVisItChomboReader.cxx.o:(.data.rel.ro._ZTVN3MPI3WinE[_ZTVN3MPI3WinE]+0x48): undefined reference to `MPI::Win::Free()' collect2: error: ld returned 1 exit status Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/build.make:8485: recipe for target 'lib/libvtkIOVisItBridge-pv5.0.so.1' failed make[2]: *** [lib/libvtkIOVisItBridge-pv5.0.so.1] Error 1 CMakeFiles/Makefile2:13468: recipe for target 'Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all' failed make[1]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all] Error 2 Makefile:149: recipe for target 'all' failed make: *** [all] Error 2 Any ideas how to fix this? From david.lonie at kitware.com Thu Dec 3 09:14:01 2015 From: david.lonie at kitware.com (David Lonie) Date: Thu, 3 Dec 2015 09:14:01 -0500 Subject: [Paraview] Labels using mathtext notation In-Reply-To: References: Message-ID: The bugfix is in master, see https://gitlab.kitware.com/vtk/vtk/merge_requests/955. Thanks again for the report! On Tue, Dec 1, 2015 at 1:56 PM, David Lonie wrote: > Hi Steven, > > Thanks for the report. I've confirmed this issue and opened a bug for it: > http://www.vtk.org/Bug/view.php?id=15859 > > I'll try to have this fixed soon, but in the meantime, it looks like > adding some whitespace between the $$ (e.g. "$x $") will workaround the bug. > > Thanks, > Dave > > On Tue, Nov 24, 2015 at 12:19 PM, Hahn, Steven E. wrote: > >> Hi, >> >> I am trying to generate a plot using ParaView v5.0.0-RC1 where the axes >> contain mathtext labels. If the label is 2 or more characters long, then >> everything is OK. If my label is one character only, it plots the $ signs. >> >> Here is a simple way to reproduce this issue: >> - Use a sphere source. >> - Show the axes >> - Edit axes grid >> - At the end of X Title string add ?$x$? >> - At the end of Y Title string add ?$yy$? >> >> The X axis title is ?X Axis $x$?. The Y axis title is ?Y Axis yy? where yy >> is italic. >> >> Best, >> Steven Hahn >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Dec 3 09:17:47 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 3 Dec 2015 09:17:47 -0500 Subject: [Paraview] Paraview 4.4.0 - Plugin with a custom 3d widget In-Reply-To: <5DF928D22AC3AC4B964903E98F2E54515A3D5CE4@sooty3.win.ara> References: <5DF928D22AC3AC4B964903E98F2E54515A3D5CE4@sooty3.win.ara> Message-ID: Andrzej, I believe the ProxyGroup name for the widget should be set with instead of HTH, Cory On Thu, Dec 3, 2015 at 6:42 AM, Andrzej Peczak wrote: > Hi > > I am trying to customise a plugin with an implicit function widget. As an > example I choose vtkPVBox class to check if I can register it under a > different name. To do it I created a SM file as following, but the plugin > seems not seeing the object I am registering. Can anybody explain how do I > register my own widget ? > > Thanks > > Andrzej > > > > > name="TranslateFilter"> > name="Input" > panel_visibility="default"> > > > > > > > > value="vtkRectilinearGrid" /> > > > name="TranslateFilter" > panel_visibility="default"> > > > > > name="Translate3" /> > > > > > > > > > > default_values="0 1 0 1 0 1" name="Bounds" > number_of_elements="6"> > > command="SetPosition" > default_values="0.0 0.0 0.0" > name="Position" number_of_elements="3"> > > > command="SetRotation" > default_values="0.0 0.0 0.0" > name="Rotation" number_of_elements="3"> > > > command="SetScale" > default_values="1.0 1.0 1.0" name="Scale" > number_of_elements="3"> > > > > > > name="Position" /> > name="Rotation" /> > name="Scale" /> > name="Bounds" /> > > > > > > > > default_values="0.0 0.0 0.0" > information_property="PositionInfo" > label="Translate" name="Position" number_of_elements="3"> > > > default_values="0.0 0.0 0.0" information_only="1" > name="PositionInfo" > number_of_elements="3" /> > > > > > > > > > > > > > > ********************************************************************** > Please consider the environment. Only print this email if absolutely > necessary. > > This email contains information that is private and confidential and is > intended only for the addressee. > If you are not the intended recipient please delete it and notify us > immediately by e-mailing the sender. > Note: All email sent to or from this address may be accessed by someone > other than the recipient, for > system management and security reasons. > Aircraft Research Association Ltd. Registered in England, Registration No > 503668 Registered Office: > Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 > > ********************************************************************** > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From apeczak at ara.co.uk Thu Dec 3 10:00:50 2015 From: apeczak at ara.co.uk (Andrzej Peczak) Date: Thu, 3 Dec 2015 15:00:50 +0000 Subject: [Paraview] Paraview 4.4.0 - Plugin with a custom 3d widget In-Reply-To: References: <5DF928D22AC3AC4B964903E98F2E54515A3D5CE4@sooty3.win.ara> Message-ID: <5DF928D22AC3AC4B964903E98F2E54515A3D5D6E@sooty3.win.ara> Cory I had tried to place the widget in utilities.xml under earlier without the success. The filter sees the standard Box but not MyBox. Andrzej From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: 03 December 2015 14:18 To: Andrzej Peczak Cc: paraview at paraview.org Subject: Re: [Paraview] Paraview 4.4.0 - Plugin with a custom 3d widget Andrzej, I believe the ProxyGroup name for the widget should be set with instead of? HTH, Cory On Thu, Dec 3, 2015 at 6:42 AM, Andrzej Peczak wrote: Hi I am trying to customise a plugin with an implicit function widget. As an example I choose vtkPVBox class to check if I can register it under a different name. To do it I created a SM file as following, but the plugin seems not seeing the object I am registering. Can anybody explain how do I register my own widget ? Thanks Andrzej ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ********************************************************************** Please consider the environment. Only print this email if absolutely necessary. This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd.? Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ********************************************************************** _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen R&D Engineer Kitware, Inc. ********************************************************************** Please consider the environment. Only print this email if absolutely necessary. This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ********************************************************************** From Saideep.Pavuluri at pet.hw.ac.uk Thu Dec 3 11:59:36 2015 From: Saideep.Pavuluri at pet.hw.ac.uk (Saideep Pavuluri) Date: Thu, 3 Dec 2015 16:59:36 +0000 Subject: [Paraview] Varying distance between threshold values plot over time in paraview Message-ID: Hi guys; I would like to collect data of specific varying distance between two threshold values in paraview varying over time. How can I do that? Using a ruler for each time step looks to be a tedious job. Any suggestions.. thanks, Saideep ----- We invite research leaders and ambitious early career researchers to join us in leading and driving research in key inter-disciplinary themes. Please see www.hw.ac.uk/researchleaders for further information and how to apply. Heriot-Watt University is a Scottish charity registered under charity number SC000278. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Dec 3 16:47:39 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 3 Dec 2015 21:47:39 +0000 Subject: [Paraview] Can ParaView create "envelope" or cumulative maximums? Message-ID: I have a user that needs to create a new array, with each cell in the array holding the maximum value of each cell over all time. I have heard this called a cumulative maximum for all cells. The then wants to paint his 3d object with this new array. For instance, if you have a variable array (maybe von mises stress), three cells and four timesteps, as follows: Three cells: 0.0 0.0 0.0 (Timestep 0) 1.0 0.0 0.0 (Timestep 1) 2.0 1.0 0.0 (Timestep 2) 1.0 3.0 1.0 (Timestep 3) Results, to be used to paint the object in a 3d view: 2.0 3.0 1.0 (Result) Does anyone know how to do this? My user feels comfortable with Python and the Programmable filter/ Python Calculator. Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From hahnse at ornl.gov Thu Dec 3 17:42:53 2015 From: hahnse at ornl.gov (Hahn, Steven E.) Date: Thu, 3 Dec 2015 22:42:53 +0000 Subject: [Paraview] Labels using mathtext notation In-Reply-To: References: Message-ID: Hi Dave, Thank you for looking into and quickly fixing this issue. Will this bugfix be included in ParaView 5? Best, Steven From: David Lonie > Date: Thursday, December 3, 2015 at 9:14 AM To: Steven Hahn > Cc: "paraview at paraview.org" > Subject: Re: [Paraview] Labels using mathtext notation The bugfix is in master, see https://gitlab.kitware.com/vtk/vtk/merge_requests/955. Thanks again for the report! On Tue, Dec 1, 2015 at 1:56 PM, David Lonie > wrote: Hi Steven, Thanks for the report. I've confirmed this issue and opened a bug for it: http://www.vtk.org/Bug/view.php?id=15859 I'll try to have this fixed soon, but in the meantime, it looks like adding some whitespace between the $$ (e.g. "$x $") will workaround the bug. Thanks, Dave On Tue, Nov 24, 2015 at 12:19 PM, Hahn, Steven E. > wrote: Hi, I am trying to generate a plot using ParaView v5.0.0-RC1 where the axes contain mathtext labels. If the label is 2 or more characters long, then everything is OK. If my label is one character only, it plots the $ signs. Here is a simple way to reproduce this issue: - Use a sphere source. - Show the axes - Edit axes grid - At the end of X Title string add ?$x$? - At the end of Y Title string add ?$yy$? The X axis title is ?X Axis $x$?. The Y axis title is ?Y Axis yy? where yy is italic. Best, Steven Hahn _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.oliveira at gmail.com Thu Dec 3 18:03:49 2015 From: thomas.oliveira at gmail.com (Thomas Oliveira) Date: Thu, 3 Dec 2015 23:03:49 +0000 Subject: [Paraview] Error while building, H5_SIZEOF_SIZE_T is undefined Message-ID: Dear all, When building paraview, master branch, commit d00c2cfed216bd07122f8b38c41329c40b510b50, I get the error: /opt/paraview/VTK/ThirdParty/hdf5/vtkhdf5/src/H5public.h:166:5: error: #error "nothing appropriate for ssize_t" The context of it is: #if H5_SIZEOF_SSIZE_T==0 /* Undefine this size, we will re-define it in one of the sections below */ #undef H5_SIZEOF_SSIZE_T #if H5_SIZEOF_SIZE_T==H5_SIZEOF_INT #ifdef WIN32 #undef ssize_t #endif typedef int ssize_t; # define H5_SIZEOF_SSIZE_T H5_SIZEOF_INT #elif H5_SIZEOF_SIZE_T==H5_SIZEOF_LONG typedef long ssize_t; # define H5_SIZEOF_SSIZE_T H5_SIZEOF_LONG #elif H5_SIZEOF_SIZE_T==H5_SIZEOF_LONG_LONG typedef long long ssize_t; # define H5_SIZEOF_SSIZE_T H5_SIZEOF_LONG_LONG #else /* Can't find matching type for ssize_t */ # error "nothing appropriate for ssize_t" #endif #endif Checking the value of some variables with #pragma message, I verified that at the beginning of this part, not only *H5_SIZEOF_SSIZE_T is undefined*, *but also* *H5_SIZEOF_SIZE_T is undefined.* I wasn't able to diagnose the problem further than that. Would you have any suggestion? Is there some configuration of CMake that I am doing wrong? Thank you for your attention, Thomas Oliveira -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Fri Dec 4 11:07:44 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Fri, 4 Dec 2015 16:07:44 +0000 Subject: [Paraview] Re: Can ParaView create "envelope" or cumulative maximums Message-ID: Alan, My first thought is to run Temporal Statistics with Maximum selected and paint by that. Is that not working? Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Fri Dec 4 11:29:06 2015 From: jfavre at cscs.ch (Favre Jean) Date: Fri, 4 Dec 2015 16:29:06 +0000 Subject: [Paraview] Can ParaView create "envelope" or cumulative maximums? In-Reply-To: References: Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684352A951@MBX111.d.ethz.ch> Incidentally, I tried to achieve this with a Python programmable filter since that was Alan's question. I did not succeed. I am removing the TIME_STEPS() and TIME_RANGE() in the RequestInformationScript script. I am setting a different UPDATE_TIME_STEP() at each iteration of the RequestUpdateExtentScript. I am setting CONTINUE_EXECUTING() in the main Script, but ParaView just does not loop after the first iteration. I have the feeling I am not setting CONTINUE_EXECUTING on the right object. Question: how does one get the request object from the executive? When I look at C code, I see int vtkTemporalStatistics::RequestData(vtkInformation *request, vtkInformationVector **inputVector, vtkInformationVector *outputVector) { ... request->Set(vtkStreamingDemandDrivenPipeline::CONTINUE_EXECUTING(), 1) ... } What is the equivalent in Python within a ProgrammableFilter()? Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.lonie at kitware.com Fri Dec 4 11:34:27 2015 From: david.lonie at kitware.com (David Lonie) Date: Fri, 4 Dec 2015 11:34:27 -0500 Subject: [Paraview] Labels using mathtext notation In-Reply-To: References: Message-ID: On Thu, Dec 3, 2015 at 5:42 PM, Hahn, Steven E. wrote: > Hi Dave, > > Thank you for looking into and quickly fixing this issue. Will this bugfix > be included in ParaView 5? > Yes, this should be fixed in the next release. Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Fri Dec 4 12:21:53 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Fri, 4 Dec 2015 17:21:53 +0000 Subject: [Paraview] Can ParaView create "envelope" or cumulative maximums Message-ID: Jean, Manipulating time inside pipeline objects is explained pretty well here: http://www.kitware.com/blog/home/post/989 Dennis From: Dennis Conklin Sent: Friday, December 04, 2015 11:08 AM To: 'paraview at paraview.org' Cc: Alan Scott (wascott at sandia.gov) Subject: [Paraview] Re: Can ParaView create "envelope" or cumulative maximums Alan, My first thought is to run Temporal Statistics with Maximum selected and paint by that. Is that not working? Dennis Incidentally, I tried to achieve this with a Python programmable filter since that was Alan's question. I did not succeed. I am removing the TIME_STEPS() and TIME_RANGE() in the RequestInformationScript script. I am setting a different UPDATE_TIME_STEP() at each iteration of the RequestUpdateExtentScript. I am setting CONTINUE_EXECUTING() in the main Script, but ParaView just does not loop after the first iteration. I have the feeling I am not setting CONTINUE_EXECUTING on the right object. Question: how does one get the request object from the executive? When I look at C code, I see int vtkTemporalStatistics::RequestData(vtkInformation *request, vtkInformationVector **inputVector, vtkInformationVector *outputVector) { ... request->Set(vtkStreamingDemandDrivenPipeline::CONTINUE_EXECUTING(), 1) ... } What is the equivalent in Python within a ProgrammableFilter()? 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview (c) 2007-2014 MarkLogic Corporation. All rights reserved. Home | paraview Home | Browse | FAQ | Advertising | Blog | Feedback | MarkMail(tm) Legale -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Fri Dec 4 14:41:53 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 4 Dec 2015 14:41:53 -0500 Subject: [Paraview] Error while building, H5_SIZEOF_SIZE_T is undefined In-Reply-To: References: Message-ID: <20151204194153.GB18798@megas.khq.kitware.com> On Thu, Dec 03, 2015 at 23:03:49 +0000, Thomas Oliveira wrote: > I wasn't able to diagnose the problem further than that. Would you have any > suggestion? Is there some configuration of CMake that I am doing wrong? ISTR some related workaround for this code: https://gitlab.kitware.com/ben.boeckel/common-superbuild/blob/superbuild-revamp/projects/win32/patches/hdf5-fix-ssize_t-redefine.patch but it isn't the same thing (particularly that you aren't on Windows), but it does indicate that HDF5 has problems with detecting size_t and ssize_t on 32-bit Windows builds. What platform/compiler are you building on? Is there any output during configure from HDF5 that looks suspicious? What happens if you delete the H5_SIZEOF_SIZE_T and H5_SIZEOF_SSIZE_T variables from the CMakeCache.txt and reconfigure? Thanks, --Ben From berk.geveci at kitware.com Fri Dec 4 15:03:37 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Fri, 4 Dec 2015 15:03:37 -0500 Subject: [Paraview] ANNOUNCE HPDAV workshop: Call for papers Message-ID: HPDAV 2016 Call for papers ____________________________________________________________________________________ The workshop on High Performance Data Analysis and Visualization (HPDAV) 2016 http://vis.lbl.gov/Events/HPDAV-IPDPS-2016/ May 23, 2016 To be held in conjunction with 30th IEEE International Parallel and Distributed Processing Symposium http://www.ipdps.org/ May 23-26, 2016 Chicago Hyatt Regency, Chicago, Illinois, USA Important Dates (AoE) ____________________________________________________________________________________ Paper Submission: Jan. 10, 2016 Paper Notification: Feb. 7, 2016 Camera-Ready: Feb. 21, 2016 Workshop Scope and Goals ____________________________________________________________________________________ While the purpose of visualization and analysis is insight, realizing that objective requires solving complex problems related to crafting or adapting algorithms and applications to take advantage of evolving architectures, and to solve increasingly complex data understanding problems for ever larger and more complex data. These architectures, and the systems from which they are built, have increasingly deep memory hierarchies, increasing concurrency, decreasing relative per-core/per-node I/O capacity, lessening memory per core, are increasingly prone to failures, and face power limitations. The purpose of this workshop is to bring together researchers, engineers, and architects of data-intensive computing technologies, which span visualization, analysis, and data management, to present and discuss research topics germane to high performance data analysis and visualization. Specifically, this workshop focuses on research topics related to adapting/creating algorithms, technologies, and applications for use on emerging computational architectures and platforms. The workshop format includes traditional research papers (8-10 pages) for in-depth topics, short papers (4 pages) for works in progress, and a panel discussion. Proceedings of the workshops are distributed at the conference and are submitted for inclusion in the IEEE Xplore Digital Library after the conference. We invite papers on original, unpublished research in the following topic areas under the general umbrella of high performance visualization and analysis: - Increasing concurrency at the node level, and at the systemwide level. - Optimizations for improving performance, e.g., decreasing runtime, leveraging a deepening memory hierarchy, reducing data movement, reducing power consumption. - Applications of visualization and analysis, where there is a strong thematic element related to being able to solve a larger or more complex problem because of algorithmic or design advances that take advantage of increasing concurrency, architectural features, etc. - Data analysis and/or visualization systems/designs/architectures having an emphasis upon scalability, resilience, high-throughput/high-capacity, and that are able to take advantage of emerging architectures. Paper submission guidelines: see http://vis.lbl.gov/Events/HPDAV-IPDPS-2016 Program Committee ____________________________________________________________________________________ Jeff Baumes, Kitware Janine Bennett, Sandia National Laboratory Wes Bethel, Lawrence Berkeley National Laboratory Randall Frank, Applied Research Associates Kelly Gaither, Texas Advanced Computing Center Christoph Garth, University of Kaiserslautern Berk Geveci, Kitware Pat McCormick, Los Alamos National Laboratory Vijay Natarajan, Indian Institute of Science Paul Navratil, Texas Advanced Computing Center Sang-Yun Oh, University of California -- Santa Barbara Rob Ross, Argonne National Laboratory Yogesh Simmhan, Indian Institute of Science Venkat Vishwanath, Argonne National Laboratory Johann Won, Seoul National University John Wu, Lawrence Berkeley National Laboratory -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Fri Dec 4 15:17:24 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Fri, 4 Dec 2015 15:17:24 -0500 Subject: [Paraview] Can ParaView create "envelope" or cumulative maximums? In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F684352A951@MBX111.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F684352A951@MBX111.d.ethz.ch> Message-ID: Somebody kindly defined a variable called "request" in the programmable filter. So you can do: request.Set(vtk.vtkStreamingDemandDrivenPipeline.CONTINUE_EXECUTING(), 1) I believe. On Fri, Dec 4, 2015 at 11:29 AM, Favre Jean wrote: > > Incidentally, I tried to achieve this with a Python programmable filter > since that was Alan's question. > > I did not succeed. I am removing the TIME_STEPS() and TIME_RANGE() in > the RequestInformationScript script. I am setting a different > UPDATE_TIME_STEP() at each iteration of the RequestUpdateExtentScript. I am > setting CONTINUE_EXECUTING() in the main Script, but ParaView just does not > loop after the first iteration. > > I have the feeling I am not setting CONTINUE_EXECUTING on the right > object. Question: > > how does one get the request object from the executive? When I look at C > code, I see > > int vtkTemporalStatistics::RequestData(vtkInformation *request, > vtkInformationVector **inputVector, > vtkInformationVector *outputVector) > { > ... > request->Set(vtkStreamingDemandDrivenPipeline::CONTINUE_EXECUTING(), 1) > ... > } > > What is the equivalent in Python within a ProgrammableFilter()? > > 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 > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 4 15:38:05 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 4 Dec 2015 15:38:05 -0500 Subject: [Paraview] Paraview 4.4.0 - Plugin with a custom 3d widget In-Reply-To: <5DF928D22AC3AC4B964903E98F2E54515A3D5D6E@sooty3.win.ara> References: <5DF928D22AC3AC4B964903E98F2E54515A3D5CE4@sooty3.win.ara> <5DF928D22AC3AC4B964903E98F2E54515A3D5D6E@sooty3.win.ara> Message-ID: Can you just use the standard box widget? Or are you planning to create a new widget in your plugin? On Thu, Dec 3, 2015 at 10:00 AM, Andrzej Peczak wrote: > Cory > > I had tried to place the widget in utilities.xml under name="implicit_functions"> earlier without the success. The filter sees the > standard Box but not MyBox. > > Andrzej > > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: 03 December 2015 14:18 > To: Andrzej Peczak > Cc: paraview at paraview.org > Subject: Re: [Paraview] Paraview 4.4.0 - Plugin with a custom 3d widget > > Andrzej, > > I believe the ProxyGroup name for the widget should be set with > > > > instead of > > > > HTH, > Cory > > On Thu, Dec 3, 2015 at 6:42 AM, Andrzej Peczak wrote: > Hi > > I am trying to customise a plugin with an implicit function widget. As an > example I choose vtkPVBox class to check if I can register it under a > different name. To do it I created a SM file as following, but the plugin > seems not seeing the object I am registering. Can anybody explain how do I > register my own widget ? > > Thanks > > Andrzej > > > > > name="TranslateFilter"> > name="Input" > panel_visibility="default"> > > > > > > > > value="vtkRectilinearGrid" /> > > > name="TranslateFilter" > panel_visibility="default"> > > > > > name="Translate3" /> > > > > > > > > > > default_values="0 1 0 1 0 1" name="Bounds" > number_of_elements="6"> > > command="SetPosition" > default_values="0.0 0.0 0.0" > name="Position" number_of_elements="3"> > > > command="SetRotation" > default_values="0.0 0.0 0.0" > name="Rotation" number_of_elements="3"> > > > command="SetScale" > default_values="1.0 1.0 1.0" name="Scale" > number_of_elements="3"> > > > > > > name="Position" /> > name="Rotation" /> > name="Scale" /> > name="Bounds" /> > > > > > > > > default_values="0.0 0.0 0.0" > information_property="PositionInfo" > label="Translate" name="Position" number_of_elements="3"> > > > default_values="0.0 0.0 0.0" information_only="1" > name="PositionInfo" > number_of_elements="3" /> > > > > > > > > > > > > > > ********************************************************************** > Please consider the environment. Only print this email if absolutely > necessary. > > This email contains information that is private and confidential and is > intended only for the addressee. > If you are not the intended recipient please delete it and notify us > immediately by e-mailing the sender. > Note: All email sent to or from this address may be accessed by someone > other than the recipient, for > system management and security reasons. > Aircraft Research Association Ltd. Registered in England, Registration No > 503668 Registered Office: > Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 > > ********************************************************************** > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > > ********************************************************************** > Please consider the environment. Only print this email if absolutely > necessary. > > This email contains information that is private and confidential and is > intended only for the addressee. > If you are not the intended recipient please delete it and notify us > immediately by e-mailing the sender. > Note: All email sent to or from this address may be accessed by someone > other than the recipient, for > system management and security reasons. > Aircraft Research Association Ltd. Registered in England, Registration No > 503668 Registered Office: > Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 > > ********************************************************************** > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 4 15:42:35 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 4 Dec 2015 15:42:35 -0500 Subject: [Paraview] Customize time values displayed in time annotation [take 2] In-Reply-To: <565624F7.9030201@yahoo.co.uk> References: <1636719764.8988613.1447692160230.JavaMail.yahoo.ref@mail.yahoo.com> <565624F7.9030201@yahoo.co.uk> Message-ID: Hi Giordano, You can use a .pvd file to assign time values to different files in the way you want. Please see http://www.paraview.org/Wiki/ParaView/Data_formats#PVD_File_Format HTH, Cory On Wed, Nov 25, 2015 at 4:15 PM, Giordano Lipari < giordano_lipari at yahoo.co.uk> wrote: > Hi all! I am reposting this after several days since I fear that the > first take was swamped in a dense digest. Hope this is OK. > > I work with Paraview 4.3.1. I use an existing state file (*.pvsm) as a > template to create a new animation (with four panels combined). > > The names of the legacy vtk files that I am loading as frames, are > tailed by a progressive file counter (such as *.0001.vtk, *.0002.vtk and > so forth). At this stage I am not able/inclined to change this situation. > > The time annotation in the animation shows the 0-based file counter, > whereas I would like to show the time values out of a given sequence. > > I then thought that editing the property field "TimestepValues" in the > state file from > number_of_elements="6"> > > > > > > > > into, for example, > number_of_elements="6"> > > > > > > > > would have worked well. (I repeat this for all occurrences of > TimestepValues owing to the four-panel arrangement.) > > However, this is not sufficient. The new values are ignored and even > overwritten when I save the modified state file. > > --1-- > Is there any other feature in the pvsm file that I should tweak to make > this substitution effective? > --2-- > Or is this idea ill-fated from the outset? > --3-- > If 2==true is the case, is there any recommended way such that the time > annotation marks a user-defined sequence of values? > > Thanks for thinking along and helping me out with tips and wisdom. > > Giordano > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 4 15:46:18 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 4 Dec 2015 15:46:18 -0500 Subject: [Paraview] Inconsistent new view with the defalut In-Reply-To: References: Message-ID: Yoshimi, I can confirm this behavior. I'll look into a fix. Cory On Tue, Nov 24, 2015 at 11:17 PM, kenichiro yoshimi wrote: > Hi Everyone, > > I am using 5.0.0-RC1 64-bit on Windows. > > I save the parallel projection setting as default: > - Toggle the advanced properties. > - Open view (Render view). > - Check "Camera Parallel Projection". > - Click on the save button shows "Save current view settings values as > default". > > After reopening ParaView, the check box of "Camera Parallel Projection" is > checked, but new view is not parallel. I think it is a bug that needs to be > fixed in 5.0.0. > > Thanks, > yoshimi > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 4 16:54:23 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 4 Dec 2015 16:54:23 -0500 Subject: [Paraview] small ParaView Script not working In-Reply-To: <565844AE.5060206@student.ethz.ch> References: <565762CE.3080804@student.ethz.ch> <565844AE.5060206@student.ethz.ch> Message-ID: Marco, Which part of your script isn't working? Are the files not being saved? Thanks, Cory On Fri, Nov 27, 2015 at 6:55 AM, Marco Kokic wrote: > I found the reason for print cells_ None, which is that I used the wrong > datareader, instead the script should look like this: > > #!/usr/bin/pvpython > > #setup paraview connection > from paraview.simple import * > > cells_ = > XMLMultiBlockDataReader(FileName=['/home/me/Dokumente/TEST/Cells_0.vtm', > '/home/me/Dokumente/TEST/Cells_100.vtm', > '/home/me/Dokumente/TEST/Cells_200.vtm']) > > # create a new 'Integrate Variables' > integrateVariables1 = IntegrateVariables(Input=cells_) > # set active source > SetActiveSource(integrateVariables1) > # create a new 'Plot Selection Over Time' > plotSelectionOverTime1 = PlotSelectionOverTime(Input=integrateVariables1) > # save data > SaveData('/home/me/Dokumente/TEST/TEST.csv', proxy=plotSelectionOverTime1) > > > Still the rest of the script doesn't work. I tried to trace every step > when using the gui and saved it as a macro. Doesn't work. > > > > > > > > > > > > > > > > Am 26.11.2015 um 20:51 schrieb Marco Kokic: > >> Dear ParaViewers, >> >> I have written and tested the following script, which I hope is >> self-explanatory. It doesn't work though (print cells_ gives "None") and I >> can't see what I missed. I'm thankful for any suggestions. >> >> #!/usr/bin/pvpython >> >> #setup paraview connection >> from paraview.simple import * >> >> def my_range(start, end, step): >> while start <= end: >> yield start >> start += step >> >> def LoadMultipleFiles(FilePrefix, Low, High): >> for i in my_range(Low,High+1,100): >> reader = XMLMultiBlockDataReader(FileName='/path-to-files/' + >> FilePrefix + str(i) + '.vtm') >> >> cells_ = LoadMultipleFiles('Cells_', 0, 1000) >> print cells_ >> >> # create a new 'Integrate Variables' >> #integrateVariables1 = IntegrateVariables(Input=cells_) >> # create a new 'Plot Selection Over Time' >> #plotSelectionOverTime1 = >> PlotSelectionOverTime(Input=integrateVariables1,Selection=None) >> # save data >> #SaveData('/path-to-files/output10_areaovertime.csv', >> proxy=plotSelectionOverTime1, >> Precision=5,UseScientificNotation=0,WriteAllTimeSteps=0) >> >> >> >> >> >> >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 4 16:56:29 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 4 Dec 2015 16:56:29 -0500 Subject: [Paraview] Inconsistent new view with the defalut In-Reply-To: References: Message-ID: Yoshimi, I looked into this issue some more. The server manager property is loaded as expected from the settings file. However, camera settings are a little special as they are not updated from the server manager. Data flows from the camera on the client to the server only, not back. I'll have to think of a way to handle this case. Best regards, Cory On Fri, Dec 4, 2015 at 3:46 PM, Cory Quammen wrote: > Yoshimi, > > I can confirm this behavior. I'll look into a fix. > > Cory > > On Tue, Nov 24, 2015 at 11:17 PM, kenichiro yoshimi < > rccm.kyoshimi at gmail.com> wrote: > >> Hi Everyone, >> >> I am using 5.0.0-RC1 64-bit on Windows. >> >> I save the parallel projection setting as default: >> - Toggle the advanced properties. >> - Open view (Render view). >> - Check "Camera Parallel Projection". >> - Click on the save button shows "Save current view settings values as >> default". >> >> After reopening ParaView, the check box of "Camera Parallel Projection" >> is checked, but new view is not parallel. I think it is a bug that needs to >> be fixed in 5.0.0. >> >> Thanks, >> yoshimi >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 4 17:06:34 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 4 Dec 2015 17:06:34 -0500 Subject: [Paraview] [vtkusers] Saving custom array class instance to *.vti file with time information In-Reply-To: <1447352677.2990.28.camel@tachikoma-mint> References: <1447352677.2990.28.camel@tachikoma-mint> Message-ID: HI Gael, Saving each time step to a VTI file is very reasonable in the way that you are doing it. I would recommend doing that. To assign times to each VTI file, I recommend also writing a .pvd file, which is an XML file that describes a list of files that can be loaded by ParaView. You can describe your VTI files in the .pvd file and assign a time to each VTI file. Please see http://www.paraview.org/Wiki/ParaView/Data_formats#PVD_File_Format for more details on the PVD file. Hope that helps, Cory On Thu, Nov 12, 2015 at 1:24 PM, lorieul wrote: > Hello, > > I wanted to know the cleanest way to save a custom array class instance > to a *.vti file with time information. I searched through the > documentation and found some threads in the mailing list archives but > could not find compelling answers (quite to my surprise? I'm sure the > information must be there somewhere?). > > I am designing a C++ software that performs CFD (Computational Fluid > Dynamics) simulations. I start from known initial conditions and iterate > in time. After each iteration, I know the definition of each of the flow > variables (e.g. I know the velocity field at each time step). I want to > save this information into a *.vti file so that I can visualise it with > paraview and (for instance) animate it. > > My code uses its own array class which I'll call DblArr. Hence when I > want to save a field to a file, I need to use a vtkImageData object and > copy all the data from the DblArr object into it. This means that for > each DblArr array I want to save, I need a corresponding vtkImageData > object (hence additional memory and computation costs). Is that the best > way to do so ? > > Besides, how do I store the time information ? Should I call : > > myImgData->GetInformation()->Set( > vtkDataObject::DATA_TIME_STEPS(), & currentTime, 1); > > Or is there a better way to do so ? (I found very little reference to > DATA_TIME_STEPS() in the documentation) > > Gael Lorieul > PhD student at Universit? catholique de Louvain > > > > > > Getting more into details : > > for each DblArr that I might want to save, I instanciate a Svr_vti > object (which is another custom class). The purpose of this class is to > perform the save operation to a *.vti file. It does three things : > 1. allocating memory i.e. instanciation of vtkImageData object at the > beginning of the simulation > 2. handling the copying of data from the DblArr object to the > vtkImageData > object > 3. writing the *.vti file. > > Once again, I have strong doubts that this is the best solution to my > problem? > > Currently I have a class called Svr_vti which holds : (amongst other > things) > @ a constructor > @ a save() member function > @ a vtkImageData member object called _ImgData > @ a vtkXMLImageDataWriter object called _Wrtr > @ a reference to a DblArr called _Arr > > Constructor(DblArr & MyArr) performs : > > _ImgData = vtkSmartPointer::New() > _Wrtr = vtkSmartPointer::New() > _Arr = MyArr > // > _ImgData->SetDimensions(***,***,***); > _ImgData->AllocateScalars( VTK_DOUBLE, * ); > _ImgData->SetOrigin(***, ***, ***); > _ImgData->SetSpacing(***, ***, ***) > // > _Wrtr->SetInputData( _ImgData ); > > > save(DblArr &) member function performs : > > for each node (i,j,k) in domain : > double * pxl = _ImgData->GetScalarPointer(i,j,k) > for each component in vector : > pxl[ind] = Arr(i,j,k, ind) > } > } > // > //The file name embeds the number of current time step > //Hence the file name is different each time save() is called > _Wrtr->SetFileName( *** ); > _Wrtr->Write(); > > Note : this is pseudo-code, it might contain syntax errors and/or > abreviations > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the VTK FAQ at: > http://www.vtk.org/Wiki/VTK_FAQ > > Search the list archives at: http://markmail.org/search/?q=vtkusers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtkusers > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From giuseppe.bilotta at gmail.com Sat Dec 5 03:58:48 2015 From: giuseppe.bilotta at gmail.com (Giuseppe Bilotta) Date: Sat, 5 Dec 2015 09:58:48 +0100 Subject: [Paraview] Inconsistent new view with the defalut In-Reply-To: References: Message-ID: On Fri, Dec 4, 2015 at 10:56 PM, Cory Quammen wrote: > Yoshimi, > > I looked into this issue some more. > > The server manager property is loaded as expected from the settings file. > However, camera settings are a little special as they are not updated from > the server manager. Data flows from the camera on the client to the server > only, not back. > I'll have to think of a way to handle this case. Wouldn't it be possible to pass the value of that setting when the camera is created, or use the same mechanism that is used to switch between parallel and orthographic when clicking on the checkbox? (I'll confess to having looked at the problem before (it's one of the reasons why I started looking into ways to contribute to paraview), but I couldn't make head or tail of it. It's very difficult for me to follow the code.) -- Giuseppe "Oblomov" Bilotta From dkxls23 at gmail.com Sat Dec 5 13:53:49 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Sat, 5 Dec 2015 20:53:49 +0200 Subject: [Paraview] rpath error when compiling ParaView 5.0 Message-ID: <566332BD.2080008@gmail.com> Hi, I'm building ParaView (version 5.0 RC1) for openSUSE Tumbleweed (using gcc 5.2.1) and get an error related to rpath (see below). I cannot say much more about this, since don't really understand what's going wrong here. Does anybody have some hints how to solve this? Please let me know if you need more information. Cheers, Armin >... > -- Installing: /home/abuild/rpmbuild/BUILDROOT/paraview50-5.0.0-1.1.x86_64/opt/paraview/5.0/include/paraview-5.0/vtkSIUnstructuredGridVolumeRepresentationProxy.h > -- Installing: /home/abuild/rpmbuild/BUILDROOT/paraview50-5.0.0-1.1.x86_64/opt/paraview/5.0/include/paraview-5.0/vtkPVServerImplementationRenderingModule.h > -- Installing: /home/abuild/rpmbuild/BUILDROOT/paraview50-5.0.0-1.1.x86_64/opt/paraview/5.0/lib/cmake/paraview-5.0/Modules/vtkUtilitiesProcessXML.cmake > -- Installing: /home/abuild/rpmbuild/BUILDROOT/paraview50-5.0.0-1.1.x86_64/opt/paraview/5.0/bin/vtkkwProcessXML-pv5.0 > CMake Error at Utilities/ProcessXML/cmake_install.cmake:49 (file): > file RPATH_CHANGE could not write new RPATH: > > $ORIGIN/../lib/paraview-5.0 > > to the file: > > /home/abuild/rpmbuild/BUILDROOT/paraview50-5.0.0-1.1.x86_64/opt/paraview/5.0/bin/vtkkwProcessXML-pv5.0 > > The current RUNPATH is: > > /home/abuild/rpmbuild/BUILD/ParaView-v5.0.0-RC1-source/build-paraview50/lib:/usr/lib64/mpi/gcc/openmpi/lib64 > > which does not contain: > > /home/abuild/rpmbuild/BUILD/ParaView-v5.0.0-RC1-source/build-paraview50/lib: > > as was expected. > Call Stack (most recent call first): > VTK/cmake_install.cmake:221 (include) > cmake_install.cmake:117 (include) >... From goebbert at vr.rwth-aachen.de Sun Dec 6 10:30:02 2015 From: goebbert at vr.rwth-aachen.de (=?iso-8859-1?Q?G=F6bbert=2C_Jens_Henrik?=) Date: Sun, 6 Dec 2015 15:30:02 +0000 Subject: [Paraview] use stereo-ParaView on a 3D projector Message-ID: <1449415802730.45520@vr.rwth-aachen.de> Hi everyone, anyone out there, who has tried ParaView in combination with a 3d projector already? Can you give me some information about the requirements and your experiences? Any help, links and hints would be great. I am wondering what minimum hardware and software is required. I would like to use a projector, which already supports active 3d shutter-glasses like the Sony VPL-HW65es (http://www.sony.co.uk/pro/product/vpl-hw65es). The best web-page describing possible stereo-setups I found was http://cismm.cs.unc.edu/core-projects/visualization-and-analysis/setting-up-a-simple-stereo-system. But it might be a bit outdated. --- quad-buffering required or not? I read, that ParaView required support for quad-buffering if you want to use it on stereoscopic displays. Is that true, or only true for stereo mode "Crystal Eyes"? Because additionally I read, that ParaView has run with NVIDIA 3DTV on Geforce grafikcards, too, which have no quad-buffering support. (... but the development of NVIDIA 3DTV has stopped with Windows 7 (http://www.nvidia.com/object/3dtv-play-system-requirements.html) ) This seems to work, if stereo mode is set for example to "Checkerboard". Hence, I wonder why there is no quad-buffering required for this setup. --- stereo-ParaView on Windows 8+ connected to a 3d projector? Is NVIDIA 3D Vision Pro still required to be able to send the stereoscopic view to a 3d projector on Windows 8+? Windows 8+ has native support for stereoscopic displays (https://msdn.microsoft.com/en-us/library/windows/hardware/dn653361%28v=vs.85%29.aspx). Does that mean, that the 3d projector has to be recognised as a stereoscopic display by Windows and can ParaView then send its 3D view to the 3d projector via HDMI 1.4a+? --- stereo-ParaView on Linux connected to a 3d projector? What would I need beside an NVIDIA Quadro to use this under Linux? Or can I use a non-Quadro card with a ParaView stereo-mode other than "Crystal Eyes"? --- stereo-ParaView on Mac connected to a 3d projector? ...? Sorry, lots of questions. I hope you can give me any help, links or hints on that. Best, Jens -------------- next part -------------- An HTML attachment was scrubbed... URL: From vianamp at gmail.com Sun Dec 6 23:05:23 2015 From: vianamp at gmail.com (Matheus Viana) Date: Mon, 7 Dec 2015 02:05:23 -0200 Subject: [Paraview] How to get the folder of the active source Message-ID: Hi list. I was wondering whether it is possible to determine the folder where the active source was loaded from in a Python script. Thanks, *Matheus Viana* *Postdoctoral Research Employee* *Developmental and Cell Biology* *University of California Irvine* -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Sun Dec 6 23:36:49 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Sun, 6 Dec 2015 23:36:49 -0500 Subject: [Paraview] How to get the folder of the active source In-Reply-To: References: Message-ID: Matheus, activeSource.FileName will get you the path to the file. This ought to work for most file readers. os.path.dirname(activeSource.FileName) will get you the directory. HTH, Cory On Sun, Dec 6, 2015 at 11:05 PM, Matheus Viana wrote: > Hi list. > > I was wondering whether it is possible to determine the folder where the > active source was loaded from in a Python script. > > Thanks, > > *Matheus Viana* > *Postdoctoral Research Employee* > *Developmental and Cell Biology* > *University of California Irvine* > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vianamp at gmail.com Mon Dec 7 00:00:18 2015 From: vianamp at gmail.com (Matheus Viana) Date: Mon, 7 Dec 2015 03:00:18 -0200 Subject: [Paraview] How to get the folder of the active source In-Reply-To: References: Message-ID: Thanks Cory. Exactly what I wanted. -m *Matheus Viana* *Postdoctoral Research Employee* *Developmental and Cell Biology* *University of California Irvine* 2015-12-07 2:36 GMT-02:00 Cory Quammen : > Matheus, > > activeSource.FileName > > will get you the path to the file. This ought to work for most file > readers. > > os.path.dirname(activeSource.FileName) > > will get you the directory. > > HTH, > Cory > > On Sun, Dec 6, 2015 at 11:05 PM, Matheus Viana wrote: > >> Hi list. >> >> I was wondering whether it is possible to determine the folder where the >> active source was loaded from in a Python script. >> >> Thanks, >> >> *Matheus Viana* >> *Postdoctoral Research Employee* >> *Developmental and Cell Biology* >> *University of California Irvine* >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vianamp at gmail.com Mon Dec 7 00:28:15 2015 From: vianamp at gmail.com (Matheus Viana) Date: Mon, 7 Dec 2015 03:28:15 -0200 Subject: [Paraview] Sync time update for a vtkTable and vtkPolyData Message-ID: Hi guys. I am facing an interesting problem. I loaded in Paraview a polyData surface that changes in time. I have 10 time steps for this surface. At the same time, I have for each time step, a text file containing xyz coordinates. When I load these text files in Paraview, they are represented as vtkTables. My problem is that the polydata surface and the vtkTable cannot be displayed on the same view in Paraview as far as I know. Therefore, when I use view = GetActiveView() view.ViewTime = time_step_I_want Render() to update the time to the time step I want, only one of the two are actually updated, depending on which is is being shown in the view. Is there any way to force a given source (surface and table in this case) to jump to a particular time step? Thanks, *Matheus Viana* *Postdoctoral Research Employee* *Developmental and Cell Biology* *University of California Irvine* -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Dec 7 09:24:35 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 7 Dec 2015 09:24:35 -0500 Subject: [Paraview] can't do stereo animation output in batch mode In-Reply-To: References: Message-ID: Ryan, In case you are still working on this, try adding this line before setting the StereoType view.StereoRender = 1 view.StereoType = st.capitalize() HTH, Cory On Fri, Nov 6, 2015 at 8:58 AM, Ryan Abernathey wrote: > Any thoughts on this issue? > > Has anyone else successfully output stereo images from pvbatch? > > On Fri, Oct 30, 2015 at 3:38 PM, Ryan Abernathey < > ryan.abernathey at gmail.com> wrote: > >> I am trying to output an animation using batch mode in stereo. I want to >> output one set of images for the left eye and one for the right eye. In my >> script, I tried to do this by setting view.StereoType = "Left" or "Right". >> However, this doesn't work; both produce identical output. >> >> Can you give me some advice? Script is below. I am executing this with >> pvbatch. >> >> >> import os >> paraview.simple._DisableFirstRenderCameraReset() >> >> state_dir = '/scratch/Paraview/hurricane/long_hourly_rotating/try4' >> fname = 'filter_pre_render.pvsm' >> st = 'left' >> # or >> # st = 'right' >> >> >> servermanager.LoadState(os.path.join(state_dir, fname)) >> outdir = >> '/scratch/Paraview/hurricane/long_hourly_rotating/output/top_view/' + st >> view = GetRenderView() >> view.ViewSize = [1920, 1080] >> view.StereoType = st.capitalize() >> SetActiveView(view) >> Render() >> WriteAnimation(os.path.join(outdir, 'top_view_%s.png' % st)) >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Dec 7 09:32:28 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 7 Dec 2015 09:32:28 -0500 Subject: [Paraview] Inconsistent new view with the defalut In-Reply-To: References: Message-ID: Yes, that should be possible. I have a potential fix for this problem and should hopefully have it resolved in the next couple days. Cory On Sat, Dec 5, 2015 at 3:58 AM, Giuseppe Bilotta wrote: > On Fri, Dec 4, 2015 at 10:56 PM, Cory Quammen > wrote: > > Yoshimi, > > > > I looked into this issue some more. > > > > The server manager property is loaded as expected from the settings file. > > However, camera settings are a little special as they are not updated > from > > the server manager. Data flows from the camera on the client to the > server > > only, not back. > > I'll have to think of a way to handle this case. > > Wouldn't it be possible to pass the value of that setting when the > camera is created, or use the same mechanism that is used to switch > between parallel and orthographic when clicking on the checkbox? > > (I'll confess to having looked at the problem before (it's one of the > reasons why I started looking into ways to contribute to paraview), > but I couldn't make head or tail of it. It's very difficult for me to > follow the code.) > > -- > Giuseppe "Oblomov" Bilotta > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Dec 7 09:48:23 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 7 Dec 2015 09:48:23 -0500 Subject: [Paraview] Inconsistent new view with the defalut In-Reply-To: References: Message-ID: Patch posted here: https://gitlab.kitware.com/paraview/paraview/merge_requests/505 On Mon, Dec 7, 2015 at 9:32 AM, Cory Quammen wrote: > Yes, that should be possible. I have a potential fix for this problem and > should hopefully have it resolved in the next couple days. > > Cory > > On Sat, Dec 5, 2015 at 3:58 AM, Giuseppe Bilotta < > giuseppe.bilotta at gmail.com> wrote: > >> On Fri, Dec 4, 2015 at 10:56 PM, Cory Quammen >> wrote: >> > Yoshimi, >> > >> > I looked into this issue some more. >> > >> > The server manager property is loaded as expected from the settings >> file. >> > However, camera settings are a little special as they are not updated >> from >> > the server manager. Data flows from the camera on the client to the >> server >> > only, not back. >> > I'll have to think of a way to handle this case. >> >> Wouldn't it be possible to pass the value of that setting when the >> camera is created, or use the same mechanism that is used to switch >> between parallel and orthographic when clicking on the checkbox? >> >> (I'll confess to having looked at the problem before (it's one of the >> reasons why I started looking into ways to contribute to paraview), >> but I couldn't make head or tail of it. It's very difficult for me to >> follow the code.) >> >> -- >> Giuseppe "Oblomov" Bilotta >> > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Mon Dec 7 11:38:35 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 7 Dec 2015 11:38:35 -0500 Subject: [Paraview] rpath error when compiling ParaView 5.0 In-Reply-To: <566332BD.2080008@gmail.com> References: <566332BD.2080008@gmail.com> Message-ID: <20151207163835.GA3080@megas.khq.kitware.com> On Sat, Dec 05, 2015 at 20:53:49 +0200, Armin Wehrfritz wrote: > I'm building ParaView (version 5.0 RC1) for openSUSE Tumbleweed (using > gcc 5.2.1) and get an error related to rpath (see below). I cannot say > much more about this, since don't really understand what's going wrong here. > > Does anybody have some hints how to solve this? Are you giving any rpath-related settings to CMake? What is the configure line? > Please let me know if you need more information. What version of CMake are you using? --Ben From grothausmann.roman at mh-hannover.de Mon Dec 7 11:50:49 2015 From: grothausmann.roman at mh-hannover.de (Grothausmann, Roman Dr.) Date: Mon, 07 Dec 2015 17:50:49 +0100 Subject: [Paraview] pvpython: assigning a 2D texture image to an object that has TCords Message-ID: <5665B8E9.9060805@mh-hannover.de> Dear mailing list members, Is it possible to assign a 2D texture image to an object that has TCords in python? I found quite a few people trying and reporting that it does not work nor does the Trace Option under paraview tell what happens if a texture is assigned in the GUI: http://www.paraview.org/pipermail/paraview/2012-March/024255.html http://www.paraview.org/Bug/view.php?id=12953 I've tried: import paraview.simple as pvs reader = pvs.OpenDataFile("test.png) #reader.UpdatePipelineInformation() reader.UpdatePipeline() print reader.GetDataInformation().GetBounds() # needs UpdatePipeline obj = pvs.Plane() plane1Display = pvs.Show(obj) plane1Display.Texture = reader dp = pvs.GetDisplayProperties(obj) dp.Representation = 'Surface With Edges' dp.Texture = reader but neither plane1Display.Texture nor dp.Texture seem to allow to set the texture (see error below) Any help or hints are very much appreciated Roman RROR: In /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 390 vtkPVSessionCore (0x258c2e0): Object type: vtkGlyph3DRepresentation, could not find requested method: "SetTexture" or the method was called with incorrect arguments. while processing Message 0 = Invoke Argument 0 = vtk_object_pointer {vtkGlyph3DRepresentation (0x551b0a0)} Argument 1 = string_value {SetTexture} Argument 2 = vtk_object_pointer {vtkImageFileSeriesReader (0x4f68190)} ERROR: In /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 391 vtkPVSessionCore (0x258c2e0): Aborting execution for debugging purposes. ############ ABORT ############# ERROR: In /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 134 vtkSISourceProxy (0x551af30): Error pushing property state: Texture global_id: 396 location: 21 [paraview_protobuf.ProxyState.property] { name: "Texture" value { type: INPUT proxy_global_id: 350 port_number: 0 } } ERROR: In /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 390 vtkPVSessionCore (0x258c2e0): Object type: vtkOutlineRepresentation, could not find requested method: "SetTexture" or the method was called with incorrect arguments. while processing Message 0 = Invoke Argument 0 = vtk_object_pointer {vtkOutlineRepresentation (0x5549800)} Argument 1 = string_value {SetTexture} Argument 2 = vtk_object_pointer {vtkImageFileSeriesReader (0x4f68190)} ERROR: In /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 391 vtkPVSessionCore (0x258c2e0): Aborting execution for debugging purposes. ############ ABORT ############# ERROR: In /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 134 vtkSISourceProxy (0x5549690): Error pushing property state: Texture global_id: 407 location: 21 [paraview_protobuf.ProxyState.property] { name: "Texture" value { type: INPUT proxy_global_id: 350 port_number: 0 } } ERROR: In /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 390 vtkPVSessionCore (0x258c2e0): Object type: vtkGeometryRepresentationWithFaces, could not find requested method: "SetTexture" or the method was called with incorrect arguments. while processing Message 0 = Invoke Argument 0 = vtk_object_pointer {vtkGeometryRepresentationWithFaces (0x59a6df0)} Argument 1 = string_value {SetTexture} Argument 2 = vtk_object_pointer {vtkImageFileSeriesReader (0x4f68190)} ERROR: In /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 391 vtkPVSessionCore (0x258c2e0): Aborting execution for debugging purposes. ############ ABORT ############# ERROR: In /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 134 vtkSISourceProxy (0x5afc8e0): Error pushing property state: Texture global_id: 440 location: 21 [paraview_protobuf.ProxyState.property] { name: "Texture" value { type: INPUT proxy_global_id: 350 port_number: 0 } } -- Dr. Roman Grothausmann Tomographie und Digitale Bildverarbeitung Tomography and Digital Image Analysis Institut f?r Funktionelle und Angewandte Anatomie, OE 4120 Medizinische Hochschule Hannover Carl-Neuberg-Str. 1 D-30625 Hannover Tel. +49 511 532-2900 From tim.thirion at kitware.com Mon Dec 7 14:49:51 2015 From: tim.thirion at kitware.com (Tim Thirion) Date: Mon, 7 Dec 2015 14:49:51 -0500 Subject: [Paraview] OpenGL Backend Identification Message-ID: Hi ParaView devs, I'm looking to provide run-time identification of the current OpenGL backend in use. Some questions: 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is there a particular reason we have both? 2. Is there an ideal place to define such a constant? Perhaps on the render window? TT -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.larsson at sth.kth.se Mon Dec 7 16:11:39 2015 From: david.larsson at sth.kth.se (David Larsson) Date: Mon, 7 Dec 2015 21:11:39 +0000 Subject: [Paraview] Velocity field analysis - lambda2 Message-ID: <1449522699250.18566@sth.kth.se> Dear all, I'm working with velocity vector fields over multiple time steps. I would like to compute a number of entities for the velocity field - most importantly the lambda2-scalar, but being relatively new to paraview I'm not really sure how to do that. I can do some simple modifications using the calculator but can't really find my way to grad() or curl() etc. I guess the solution is going over to pvpython (which would also be preferred with regards to doing automated analysis). Does anyone have any experience with performing numerical analysis of vector velocity fields in pvpython that could give some hints on how to get started? Or does anyone even have performed lambda2-analysis on such? I've seen some similar questions in the mail-list from before but can't seem to find a conclusive answer, so I thought I'd give it a try myself. Thanks for the help. /David -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Mon Dec 7 16:47:49 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 7 Dec 2015 16:47:49 -0500 Subject: [Paraview] Velocity field analysis - lambda2 In-Reply-To: <1449522699250.18566@sth.kth.se> References: <1449522699250.18566@sth.kth.se> Message-ID: Have you tried numpy expressions in the python calculator? http://www.vtk.org/Wiki/Python_Calculator hth David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Dec 7, 2015 at 4:11 PM, David Larsson wrote: > Dear all, > > > I'm working with velocity vector fields over multiple time steps. I would > like to compute a number of entities for the velocity field - most > importantly the lambda2-scalar, but being relatively new to paraview I'm > not really sure how to do that. > > > I can do some simple modifications using the calculator but can't really > find my way to grad() or curl() etc. I guess the solution is going over to > pvpython (which would also be preferred with regards to doing automated > analysis). > > > Does anyone have any experience with performing numerical analysis of > vector velocity fields in pvpython that could give some hints on how to get > started? Or does anyone even have performed lambda2-analysis on such? > > > I've seen some similar questions in the mail-list from before but can't > seem to find a conclusive answer, so I thought I'd give it a try myself. > > > Thanks for the help. > > > /David > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Mon Dec 7 17:11:30 2015 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Mon, 7 Dec 2015 17:11:30 -0500 (EST) Subject: [Paraview] Velocity field analysis - lambda2 In-Reply-To: <1449522699250.18566@sth.kth.se> Message-ID: <597591809.19003727.1449526290714.JavaMail.root@mail.gatech.edu> David, I haven't taken on lambda-2 yet, but I have been able to build a pipeline for Q-Criterion. It looks something like: Data -> CellDataToPointData (if it isn't already point data) -> ComputeDerivatives (set the gradient option to vorticity and the tensor option to strain) -> CellDataToPointData -> Calculator (compute |S|^2) -> Calculator (compute |\Omega|^2) -> Calculator (compute Q-criterion) Since lambda_2 = S_ik S_ij + \Omega_ik \Omega_kj, you can use the same procedure and use just the standard calculators if you want to expand the Einstein summation and plug them all. Once I've done this, I save the set of 3 calculators as a custom filter. When I use pvpython, I load my custom filter in the server manager and then use the CD2PD and ComputeDerivatives filters as needed. The python calculator might be a better way to do it, but I haven't tried that yet. Tim ----- Original Message ----- From: "David Larsson" To: paraview at paraview.org Sent: Monday, December 7, 2015 4:11:39 PM Subject: [Paraview] Velocity field analysis - lambda2 Dear all, I'm working with velocity vector fields over multiple time steps. I would like to compute a number of entities for the velocity field - most importantly the lambda2-scalar, but being relatively new to paraview I'm not really sure how to do that. I can do some simple modifications using the calculator but can't really find my way to grad() or curl() etc. I guess the solution is going over to pvpython (which would also be preferred with regards to doing automated analysis). Does anyone have any experience with performing numerical analysis of vector velocity fields in pvpython that could give some hints on how to get started? Or does anyone even have performed lambda2-analysis on such? I've seen some similar questions in the mail-list from before but can't seem to find a conclusive answer, so I thought I'd give it a try myself. Thanks for the help. /David _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Mon Dec 7 17:16:50 2015 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Mon, 7 Dec 2015 17:16:50 -0500 (EST) Subject: [Paraview] Velocity field analysis - lambda2 In-Reply-To: <597591809.19003727.1449526290714.JavaMail.root@mail.gatech.edu> Message-ID: <423515563.19004573.1449526610447.JavaMail.root@mail.gatech.edu> For the sake of people years later who come across this thread, there is a typo in my definition and it should be: lambda_2 = S_ik S_kj + \Omega_ik \Omega_kj Tim ----- Original Message ----- From: "Tim Gallagher" To: "David Larsson" Cc: paraview at paraview.org Sent: Monday, December 7, 2015 5:11:30 PM Subject: Re: [Paraview] Velocity field analysis - lambda2 David, I haven't taken on lambda-2 yet, but I have been able to build a pipeline for Q-Criterion. It looks something like: Data -> CellDataToPointData (if it isn't already point data) -> ComputeDerivatives (set the gradient option to vorticity and the tensor option to strain) -> CellDataToPointData -> Calculator (compute |S|^2) -> Calculator (compute |\Omega|^2) -> Calculator (compute Q-criterion) Since lambda_2 = S_ik S_ij + \Omega_ik \Omega_kj, you can use the same procedure and use just the standard calculators if you want to expand the Einstein summation and plug them all. Once I've done this, I save the set of 3 calculators as a custom filter. When I use pvpython, I load my custom filter in the server manager and then use the CD2PD and ComputeDerivatives filters as needed. The python calculator might be a better way to do it, but I haven't tried that yet. Tim ----- Original Message ----- From: "David Larsson" To: paraview at paraview.org Sent: Monday, December 7, 2015 4:11:39 PM Subject: [Paraview] Velocity field analysis - lambda2 Dear all, I'm working with velocity vector fields over multiple time steps. I would like to compute a number of entities for the velocity field - most importantly the lambda2-scalar, but being relatively new to paraview I'm not really sure how to do that. I can do some simple modifications using the calculator but can't really find my way to grad() or curl() etc. I guess the solution is going over to pvpython (which would also be preferred with regards to doing automated analysis). Does anyone have any experience with performing numerical analysis of vector velocity fields in pvpython that could give some hints on how to get started? Or does anyone even have performed lambda2-analysis on such? I've seen some similar questions in the mail-list from before but can't seem to find a conclusive answer, so I thought I'd give it a try myself. Thanks for the help. /David _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.oliveira at gmail.com Mon Dec 7 20:58:14 2015 From: thomas.oliveira at gmail.com (Thomas Oliveira) Date: Tue, 8 Dec 2015 01:58:14 +0000 Subject: [Paraview] Blurred volume rendering In-Reply-To: References: Message-ID: Dear Aashish, I tried to build ParaView from master, but I get an error that is the subject of another discussion on the list ("Error while building, H5_SIZEOF_SIZE_T is undefined"). Could I try to apply the patch on some version available from http://www.paraview.org/download/, maybe a nightly build? Best wishes, Thomas On Thu, Dec 3, 2015 at 5:31 AM, Aashish Chaudhary < aashish.chaudhary at kitware.com> wrote: > Dear Thomas, > > If it is possible for you to build ParaView from master (as of today) with > OpenGL2 backend, then apply this patch (attached) and see if this works for > you. This might work on older version or OpenGL1 backend but I haven't > tested it, so use at your risk. Once applied and build, you can find for > "Interpolation" option in advance search box. It will show "Nearest, > Linear, and Cubic". > > Thanks, > > > On Wed, Dec 2, 2015 at 11:59 AM, Aashish Chaudhary < > aashish.chaudhary at kitware.com> wrote: > >> Hi Thomas, >> >> Please find the attached image which I rendered using VTK code and in >> there I used nearest interpolation. Please let me know if this is what you >> expect. I will see if we can push a change to ParaView to expose this >> feature. >> >> Thanks, >> >> >> int TestGPURayCastVolumeUpdate(int argc, char *argv[]) >> >> { >> >> cout << "CTEST_FULL_OUTPUT (Avoid ctest truncation of output)" << endl; >> >> >> double scalarRange[2]; >> >> >> vtkNew outlineActor; >> >> vtkNew outlineMapper; >> >> vtkNew volumeMapper; >> >> >> vtkNew reader; >> >> reader->SetFilePrefix("/home/chaudhary/tools/paraview_main/Image/Berea.raw"); >> >> reader->SetFilePattern("%s"); >> >> reader->SetFileDimensionality(3); >> >> reader->SetDataByteOrderToLittleEndian(); >> >> reader->SetDataScalarTypeToUnsignedChar(); >> >> reader->SetDataExtent(0, 399, 0, 399, 0, 399); >> >> reader->SetFileLowerLeft(1); >> >> reader->SetDataOrigin(0, 0, 0); >> >> reader->SetDataSpacing(1.0, 1.0, 1.0); >> >> reader->SetInputArrayToProcess(0, 0, 0, vtkDataObject::FIELD_ASSOCIATION_POINTS, "ImageFile"); >> >> reader->Update(); >> >> >> volumeMapper->SetInputConnection(reader->GetOutputPort()); >> >> >> // Add outline filter >> >> vtkNew outlineFilter; >> >> outlineFilter->SetInputConnection(reader->GetOutputPort()); >> >> outlineMapper->SetInputConnection(outlineFilter->GetOutputPort()); >> >> outlineActor->SetMapper(outlineMapper.GetPointer()); >> >> >> volumeMapper->GetInput()->GetScalarRange(scalarRange); >> >> volumeMapper->SetAutoAdjustSampleDistances(0); >> >> volumeMapper->SetBlendModeToComposite(); >> >> >> vtkNew renWin; >> >> renWin->SetMultiSamples(0); >> >> renWin->SetSize(400, 400); >> >> >> vtkNew iren; >> >> iren->SetRenderWindow(renWin.GetPointer()); >> >> vtkNew style; >> >> iren->SetInteractorStyle(style.GetPointer()); >> >> >> renWin->Render(); // make sure we have an OpenGL context. >> >> >> vtkNew ren; >> >> ren->SetBackground(0.2, 0.2, 0.5); >> >> renWin->AddRenderer(ren.GetPointer()); >> >> >> vtkNew scalarOpacity; >> >> scalarOpacity->AddPoint(0.0, 0.0); >> >> scalarOpacity->AddPoint(0.4, 0.0); >> >> scalarOpacity->AddPoint(0.4, 0.1); >> >> scalarOpacity->AddPoint(1.0, 0.2); >> >> >> vtkNew volumeProperty; >> >> * volumeProperty->SetInterpolationType(VTK_NEAREST_INTERPOLATION);* >> >> volumeProperty->SetScalarOpacity(scalarOpacity.GetPointer()); >> >> volumeProperty->ShadeOn(); >> >> >> vtkNew colorTransferFunction; >> >> colorTransferFunction->RemoveAllPoints(); >> >> colorTransferFunction->AddRGBPoint(scalarRange[0], 0.6, 0.4, 0.4); >> >> colorTransferFunction->AddRGBPoint(scalarRange[1], 1.0, 1.0, 0.4); >> >> volumeProperty->SetColor(colorTransferFunction.GetPointer()); >> >> >> vtkNew volume; >> >> volume->SetMapper(volumeMapper.GetPointer()); >> >> volume->SetProperty(volumeProperty.GetPointer()); >> >> >> /// Add sphere in the center of volume >> >> int dims[3]; >> >> double spacing[3], center[3], origin[3]; >> >> reader->Update(); >> >> vtkSmartPointer im = reader->GetOutput(); >> >> im->GetDimensions(dims); >> >> im->GetOrigin(origin); >> >> im->GetSpacing(spacing); >> >> >> center[0] = origin[0] + spacing[0]*dims[0]/2.0; >> >> center[1] = origin[1] + spacing[1]*dims[1]/2.0; >> >> center[2] = origin[2] + spacing[2]*dims[2]/2.0; >> >> >> ren->AddVolume(volume.GetPointer()); >> >> ren->AddActor(outlineActor.GetPointer()); >> >> ren->ResetCamera(); >> >> renWin->Render(); >> >> >> iren->Initialize(); >> >> iren->Start(); >> >> } >> >> >> On Wed, Dec 2, 2015 at 10:13 AM, Aashish Chaudhary < >> aashish.chaudhary at kitware.com> wrote: >> >>> Thomas, >>> >>> I am looking at your data in VTK. I will report back. In ParaView, you >>> cannot choose linear or nearest as of now. We have a plan to expose all of >>> the volume property parameters in ParaView (hopefully soon). >>> >>> Thanks, >>> >>> >>> On Mon, Nov 30, 2015 at 3:06 PM, Thomas Oliveira < >>> thomas.oliveira at gmail.com> wrote: >>> >>>> Dear Aashish, >>>> >>>> Can I choose the interpolation (linear vs nearest) or is it hard-coded >>>> on the call of VTK from Paraview? >>>> >>>> A dataset can be downloaded from >>>> http://www3.imperial.ac.uk/pls/portallive/docs/1/33505696.ZIP . >>>> Please extract the Berea.raw file from the zip. >>>> I loaded it using: >>>> """ >>>> Raw (binary) Files >>>> Data Scalar Type: unsigned char >>>> Data Byte Order: Little Endian >>>> Data Extent: 0-399, 0-399, 0-399 >>>> """ >>>> >>>> Thank you for your attention, >>>> >>>> Thomas Oliveira >>>> >>>> >>>> On Mon, Nov 30, 2015 at 4:31 PM, Aashish Chaudhary < >>>> aashish.chaudhary at kitware.com> wrote: >>>> >>>>> Thomas, >>>>> >>>>> >>>>> >>>>> On Mon, Nov 30, 2015 at 10:34 AM, Thomas Oliveira < >>>>> thomas.oliveira at gmail.com> wrote: >>>>> >>>>>> Dear Aashish, >>>>>> >>>>>> >>>>>> I'm using Paraview 4.4.0 64-bit , OpenGL Version 4.5.0 NVIDIA 352.55, >>>>>> OpenGL Renderer Quadro K600/PCIe/SSE2. >>>>>> >>>>>> Tweaking the transfer function improved the result, but the corners >>>>>> are rendererd rounded, whereas in the original file I have only cubic >>>>>> voxels. >>>>>> >>>>> >>>>> I am wondering if that would be because of the interpolation (linear >>>>> vs nearest) since linear will smooth out the edges just a bit. Is there a >>>>> sample dataset you can send my way? >>>>> >>>>> >>>>>> I though that unsetting "Properties > Scalar Coloring > Interpolate >>>>>> Scalars Before Mapping" would improve the image, but I saw no change. >>>>>> >>>>>> You suggested to enable shading, but I couldn't find it. Where is it? >>>>>> >>>>> >>>>> Its on the same panel (left side), scroll to the bottom or search for >>>>> "shade" you should be see it. >>>>> >>>>> - aashish >>>>> >>>>>> >>>>>> >>>>>> Thank you for your help, >>>>>> >>>>>> Thomas Oliveira >>>>>> >>>>>> >>>>>> On Mon, Nov 30, 2015 at 3:07 PM, Aashish Chaudhary < >>>>>> aashish.chaudhary at kitware.com> wrote: >>>>>> >>>>>>> Hi Thomas, >>>>>>> >>>>>>> On Mon, Nov 30, 2015 at 8:54 AM, Thomas Oliveira < >>>>>>> thomas.oliveira at gmail.com> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> The Sample.png file attached is an image of a pore medium. Each >>>>>>>> voxel in the image is a cube that is either solid or void. >>>>>>>> >>>>>>>> The Zoom.png file attached is a zoom of it, where it can be seen >>>>>>>> that the curved interior solid walls are approximated by a staircase >>>>>>>> discretization. >>>>>>>> >>>>>>>> How can I render this staircase geometry more clearly? >>>>>>>> >>>>>>> >>>>>>> Did you try to tweak the transfer function? Also, you can enable >>>>>>> shading to have a look of a solid surface. >>>>>>> >>>>>>> >>>>>>>> I have tried tweaking many properties on ParaView but I still get >>>>>>>> it blurred. >>>>>>>> >>>>>>> >>>>>>> Just to be sure, what version of ParaView you are using and what >>>>>>> OpenGL backend? >>>>>>> >>>>>>>> >>>>>>>> Thank you for your help, >>>>>>>> >>>>>>>> Thomas Oliveira >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> >>>>>>> >>>>>>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>>>>>> * >>>>>>> *| http://www.kitware.com/company/team/chaudhary.html >>>>>>> * >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> >>>>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>>>> * >>>>> *| http://www.kitware.com/company/team/chaudhary.html >>>>> * >>>>> >>>> >>>> >>> >>> >>> -- >>> >>> >>> >>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>> * >>> *| http://www.kitware.com/company/team/chaudhary.html >>> * >>> >> >> >> >> -- >> >> >> >> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >> * >> *| http://www.kitware.com/company/team/chaudhary.html >> * >> > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. * > *| http://www.kitware.com/company/team/chaudhary.html > * > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vianamp at gmail.com Mon Dec 7 21:05:11 2015 From: vianamp at gmail.com (Matheus Viana) Date: Tue, 8 Dec 2015 00:05:11 -0200 Subject: [Paraview] Sync time update for a vtkTable and vtkPolyData In-Reply-To: References: Message-ID: Hi guys. I found a solution to this problem, but I don't think it is the easiest one. Anyway, it goes like this: Two views are created, the 1st is a 3D RenderView and the 2nd is a SpreadSheetView. The time-varying surfaces are shown in the first view and the time-varying tables are shown in the second view. Then, all I need to do in my Python script is to iterate over these two views and set the time step I want. Views = GetViews() for time in range(0,NMaxSteps): for view in range(0,numpy.size(Views)): SetActiveView(Views[view]) GetActiveView().ViewTime = time Render() Thanks, *Matheus Viana* *Postdoctoral Research Employee* *Developmental and Cell Biology* *University of California Irvine* 2015-12-07 3:28 GMT-02:00 Matheus Viana : > Hi guys. > > I am facing an interesting problem. I loaded in Paraview a polyData > surface that changes in time. I have 10 time steps for this surface. At the > same time, I have for each time step, a text file containing xyz > coordinates. When I load these text files in Paraview, they are represented > as vtkTables. > > My problem is that the polydata surface and the vtkTable cannot be > displayed on the same view in Paraview as far as I know. Therefore, when I > use > > view = GetActiveView() > view.ViewTime = time_step_I_want > Render() > > to update the time to the time step I want, only one of the two are > actually updated, depending on which is is being shown in the view. > > Is there any way to force a given source (surface and table in this case) > to jump to a particular time step? > > Thanks, > > *Matheus Viana* > *Postdoctoral Research Employee* > *Developmental and Cell Biology* > *University of California Irvine* > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Dec 7 22:07:35 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 7 Dec 2015 22:07:35 -0500 Subject: [Paraview] Sync time update for a vtkTable and vtkPolyData In-Reply-To: References: Message-ID: That seems as good as any solution I might have proposed. Cory On Mon, Dec 7, 2015 at 9:05 PM, Matheus Viana wrote: > Hi guys. > > I found a solution to this problem, but I don't think it is the easiest > one. Anyway, it goes like this: > > Two views are created, the 1st is a 3D RenderView and the 2nd is a > SpreadSheetView. The time-varying surfaces are shown in the first view and > the time-varying tables are shown in the second view. Then, all I need to > do in my Python script is to iterate over these two views and set the time > step I want. > > Views = GetViews() > > for time in range(0,NMaxSteps): > > for view in range(0,numpy.size(Views)): > SetActiveView(Views[view]) > GetActiveView().ViewTime = time > Render() > > Thanks, > > *Matheus Viana* > *Postdoctoral Research Employee* > *Developmental and Cell Biology* > *University of California Irvine* > > > > 2015-12-07 3:28 GMT-02:00 Matheus Viana : > >> Hi guys. >> >> I am facing an interesting problem. I loaded in Paraview a polyData >> surface that changes in time. I have 10 time steps for this surface. At the >> same time, I have for each time step, a text file containing xyz >> coordinates. When I load these text files in Paraview, they are represented >> as vtkTables. >> >> My problem is that the polydata surface and the vtkTable cannot be >> displayed on the same view in Paraview as far as I know. Therefore, when I >> use >> >> view = GetActiveView() >> view.ViewTime = time_step_I_want >> Render() >> >> to update the time to the time step I want, only one of the two are >> actually updated, depending on which is is being shown in the view. >> >> Is there any way to force a given source (surface and table in this case) >> to jump to a particular time step? >> >> Thanks, >> >> *Matheus Viana* >> *Postdoctoral Research Employee* >> *Developmental and Cell Biology* >> *University of California Irvine* >> >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Mon Dec 7 23:10:27 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 7 Dec 2015 23:10:27 -0500 Subject: [Paraview] Blurred volume rendering In-Reply-To: References: Message-ID: You can try that. If it does not work, its a very minor change, hopefully you can find the file and change it manually. Thanks, On Mon, Dec 7, 2015 at 8:58 PM, Thomas Oliveira wrote: > Dear Aashish, > > I tried to build ParaView from master, but I get an error that is the > subject of another discussion on the list ("Error while building, > H5_SIZEOF_SIZE_T is undefined"). Could I try to apply the patch on some > version available from http://www.paraview.org/download/, maybe a nightly > build? > > Best wishes, > > Thomas > > On Thu, Dec 3, 2015 at 5:31 AM, Aashish Chaudhary < > aashish.chaudhary at kitware.com> wrote: > >> Dear Thomas, >> >> If it is possible for you to build ParaView from master (as of today) >> with OpenGL2 backend, then apply this patch (attached) and see if this >> works for you. This might work on older version or OpenGL1 backend but I >> haven't tested it, so use at your risk. Once applied and build, you can >> find for "Interpolation" option in advance search box. It will show >> "Nearest, Linear, and Cubic". >> >> Thanks, >> >> >> On Wed, Dec 2, 2015 at 11:59 AM, Aashish Chaudhary < >> aashish.chaudhary at kitware.com> wrote: >> >>> Hi Thomas, >>> >>> Please find the attached image which I rendered using VTK code and in >>> there I used nearest interpolation. Please let me know if this is what you >>> expect. I will see if we can push a change to ParaView to expose this >>> feature. >>> >>> Thanks, >>> >>> >>> int TestGPURayCastVolumeUpdate(int argc, char *argv[]) >>> >>> { >>> >>> cout << "CTEST_FULL_OUTPUT (Avoid ctest truncation of output)" << endl; >>> >>> >>> double scalarRange[2]; >>> >>> >>> vtkNew outlineActor; >>> >>> vtkNew outlineMapper; >>> >>> vtkNew volumeMapper; >>> >>> >>> vtkNew reader; >>> >>> reader->SetFilePrefix("/home/chaudhary/tools/paraview_main/Image/Berea.raw"); >>> >>> reader->SetFilePattern("%s"); >>> >>> reader->SetFileDimensionality(3); >>> >>> reader->SetDataByteOrderToLittleEndian(); >>> >>> reader->SetDataScalarTypeToUnsignedChar(); >>> >>> reader->SetDataExtent(0, 399, 0, 399, 0, 399); >>> >>> reader->SetFileLowerLeft(1); >>> >>> reader->SetDataOrigin(0, 0, 0); >>> >>> reader->SetDataSpacing(1.0, 1.0, 1.0); >>> >>> reader->SetInputArrayToProcess(0, 0, 0, vtkDataObject::FIELD_ASSOCIATION_POINTS, "ImageFile"); >>> >>> reader->Update(); >>> >>> >>> volumeMapper->SetInputConnection(reader->GetOutputPort()); >>> >>> >>> // Add outline filter >>> >>> vtkNew outlineFilter; >>> >>> outlineFilter->SetInputConnection(reader->GetOutputPort()); >>> >>> outlineMapper->SetInputConnection(outlineFilter->GetOutputPort()); >>> >>> outlineActor->SetMapper(outlineMapper.GetPointer()); >>> >>> >>> volumeMapper->GetInput()->GetScalarRange(scalarRange); >>> >>> volumeMapper->SetAutoAdjustSampleDistances(0); >>> >>> volumeMapper->SetBlendModeToComposite(); >>> >>> >>> vtkNew renWin; >>> >>> renWin->SetMultiSamples(0); >>> >>> renWin->SetSize(400, 400); >>> >>> >>> vtkNew iren; >>> >>> iren->SetRenderWindow(renWin.GetPointer()); >>> >>> vtkNew style; >>> >>> iren->SetInteractorStyle(style.GetPointer()); >>> >>> >>> renWin->Render(); // make sure we have an OpenGL context. >>> >>> >>> vtkNew ren; >>> >>> ren->SetBackground(0.2, 0.2, 0.5); >>> >>> renWin->AddRenderer(ren.GetPointer()); >>> >>> >>> vtkNew scalarOpacity; >>> >>> scalarOpacity->AddPoint(0.0, 0.0); >>> >>> scalarOpacity->AddPoint(0.4, 0.0); >>> >>> scalarOpacity->AddPoint(0.4, 0.1); >>> >>> scalarOpacity->AddPoint(1.0, 0.2); >>> >>> >>> vtkNew volumeProperty; >>> >>> * volumeProperty->SetInterpolationType(VTK_NEAREST_INTERPOLATION);* >>> >>> volumeProperty->SetScalarOpacity(scalarOpacity.GetPointer()); >>> >>> volumeProperty->ShadeOn(); >>> >>> >>> vtkNew colorTransferFunction; >>> >>> colorTransferFunction->RemoveAllPoints(); >>> >>> colorTransferFunction->AddRGBPoint(scalarRange[0], 0.6, 0.4, 0.4); >>> >>> colorTransferFunction->AddRGBPoint(scalarRange[1], 1.0, 1.0, 0.4); >>> >>> volumeProperty->SetColor(colorTransferFunction.GetPointer()); >>> >>> >>> vtkNew volume; >>> >>> volume->SetMapper(volumeMapper.GetPointer()); >>> >>> volume->SetProperty(volumeProperty.GetPointer()); >>> >>> >>> /// Add sphere in the center of volume >>> >>> int dims[3]; >>> >>> double spacing[3], center[3], origin[3]; >>> >>> reader->Update(); >>> >>> vtkSmartPointer im = reader->GetOutput(); >>> >>> im->GetDimensions(dims); >>> >>> im->GetOrigin(origin); >>> >>> im->GetSpacing(spacing); >>> >>> >>> center[0] = origin[0] + spacing[0]*dims[0]/2.0; >>> >>> center[1] = origin[1] + spacing[1]*dims[1]/2.0; >>> >>> center[2] = origin[2] + spacing[2]*dims[2]/2.0; >>> >>> >>> ren->AddVolume(volume.GetPointer()); >>> >>> ren->AddActor(outlineActor.GetPointer()); >>> >>> ren->ResetCamera(); >>> >>> renWin->Render(); >>> >>> >>> iren->Initialize(); >>> >>> iren->Start(); >>> >>> } >>> >>> >>> On Wed, Dec 2, 2015 at 10:13 AM, Aashish Chaudhary < >>> aashish.chaudhary at kitware.com> wrote: >>> >>>> Thomas, >>>> >>>> I am looking at your data in VTK. I will report back. In ParaView, you >>>> cannot choose linear or nearest as of now. We have a plan to expose all of >>>> the volume property parameters in ParaView (hopefully soon). >>>> >>>> Thanks, >>>> >>>> >>>> On Mon, Nov 30, 2015 at 3:06 PM, Thomas Oliveira < >>>> thomas.oliveira at gmail.com> wrote: >>>> >>>>> Dear Aashish, >>>>> >>>>> Can I choose the interpolation (linear vs nearest) or is it hard-coded >>>>> on the call of VTK from Paraview? >>>>> >>>>> A dataset can be downloaded from >>>>> http://www3.imperial.ac.uk/pls/portallive/docs/1/33505696.ZIP . >>>>> Please extract the Berea.raw file from the zip. >>>>> I loaded it using: >>>>> """ >>>>> Raw (binary) Files >>>>> Data Scalar Type: unsigned char >>>>> Data Byte Order: Little Endian >>>>> Data Extent: 0-399, 0-399, 0-399 >>>>> """ >>>>> >>>>> Thank you for your attention, >>>>> >>>>> Thomas Oliveira >>>>> >>>>> >>>>> On Mon, Nov 30, 2015 at 4:31 PM, Aashish Chaudhary < >>>>> aashish.chaudhary at kitware.com> wrote: >>>>> >>>>>> Thomas, >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Nov 30, 2015 at 10:34 AM, Thomas Oliveira < >>>>>> thomas.oliveira at gmail.com> wrote: >>>>>> >>>>>>> Dear Aashish, >>>>>>> >>>>>>> >>>>>>> I'm using Paraview 4.4.0 64-bit , OpenGL Version 4.5.0 NVIDIA >>>>>>> 352.55, OpenGL Renderer Quadro K600/PCIe/SSE2. >>>>>>> >>>>>>> Tweaking the transfer function improved the result, but the corners >>>>>>> are rendererd rounded, whereas in the original file I have only cubic >>>>>>> voxels. >>>>>>> >>>>>> >>>>>> I am wondering if that would be because of the interpolation (linear >>>>>> vs nearest) since linear will smooth out the edges just a bit. Is there a >>>>>> sample dataset you can send my way? >>>>>> >>>>>> >>>>>>> I though that unsetting "Properties > Scalar Coloring > Interpolate >>>>>>> Scalars Before Mapping" would improve the image, but I saw no change. >>>>>>> >>>>>>> You suggested to enable shading, but I couldn't find it. Where is it? >>>>>>> >>>>>> >>>>>> Its on the same panel (left side), scroll to the bottom or search for >>>>>> "shade" you should be see it. >>>>>> >>>>>> - aashish >>>>>> >>>>>>> >>>>>>> >>>>>>> Thank you for your help, >>>>>>> >>>>>>> Thomas Oliveira >>>>>>> >>>>>>> >>>>>>> On Mon, Nov 30, 2015 at 3:07 PM, Aashish Chaudhary < >>>>>>> aashish.chaudhary at kitware.com> wrote: >>>>>>> >>>>>>>> Hi Thomas, >>>>>>>> >>>>>>>> On Mon, Nov 30, 2015 at 8:54 AM, Thomas Oliveira < >>>>>>>> thomas.oliveira at gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> The Sample.png file attached is an image of a pore medium. Each >>>>>>>>> voxel in the image is a cube that is either solid or void. >>>>>>>>> >>>>>>>>> The Zoom.png file attached is a zoom of it, where it can be seen >>>>>>>>> that the curved interior solid walls are approximated by a staircase >>>>>>>>> discretization. >>>>>>>>> >>>>>>>>> How can I render this staircase geometry more clearly? >>>>>>>>> >>>>>>>> >>>>>>>> Did you try to tweak the transfer function? Also, you can enable >>>>>>>> shading to have a look of a solid surface. >>>>>>>> >>>>>>>> >>>>>>>>> I have tried tweaking many properties on ParaView but I still get >>>>>>>>> it blurred. >>>>>>>>> >>>>>>>> >>>>>>>> Just to be sure, what version of ParaView you are using and what >>>>>>>> OpenGL backend? >>>>>>>> >>>>>>>>> >>>>>>>>> Thank you for your help, >>>>>>>>> >>>>>>>>> Thomas Oliveira >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Powered by www.kitware.com >>>>>>>>> >>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>> >>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>> >>>>>>>>> Search the list archives at: >>>>>>>>> http://markmail.org/search/?q=ParaView >>>>>>>>> >>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>>>>>>> * >>>>>>>> *| http://www.kitware.com/company/team/chaudhary.html >>>>>>>> * >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> >>>>>> >>>>>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>>>>> * >>>>>> *| http://www.kitware.com/company/team/chaudhary.html >>>>>> * >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>>> * >>>> *| http://www.kitware.com/company/team/chaudhary.html >>>> * >>>> >>> >>> >>> >>> -- >>> >>> >>> >>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>> * >>> *| http://www.kitware.com/company/team/chaudhary.html >>> * >>> >> >> >> >> -- >> >> >> >> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >> * >> *| http://www.kitware.com/company/team/chaudhary.html >> * >> > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From grothausmann.roman at mh-hannover.de Tue Dec 8 05:01:21 2015 From: grothausmann.roman at mh-hannover.de (Grothausmann, Roman Dr.) Date: Tue, 08 Dec 2015 11:01:21 +0100 Subject: [Paraview] state-file does not contain 2D texture if assigned by python In-Reply-To: <5665B8E9.9060805@mh-hannover.de> References: <5665B8E9.9060805@mh-hannover.de> Message-ID: <5666AA71.3020204@mh-hannover.de> After some hours of searching I found an answer that sadly was not linked to the question: http://www.paraview.org/pipermail/paraview/2012-March/024261.html The code below run as a macro in paraview shows a plane with a texture. However, saving the state in a *.pvsm either by code or within the GUI does not save the texture and its assignment. What is missing to save the texture and its assignment in a state file? ______________________________________________________ import paraview.simple as pvs plane1 = pvs.Plane(guiName="xz-plane") dp = pvs.GetDisplayProperties(plane1) dp.Representation = 'Surface With Edges' texProxy = pvs.servermanager.CreateProxy("textures", "ImageTexture") texProxy.GetProperty("FileName").SetElement(0, "texture.png") texProxy.UpdateVTKObjects() dp.Texture= texProxy print dp.Texture pvs.Render() pvs.servermanager.SaveState("test.pvsm") On 07/12/15 17:50, Grothausmann, Roman Dr. wrote: > Dear mailing list members, > > > Is it possible to assign a 2D texture image to an object that has TCords in python? > I found quite a few people trying and reporting that it does not work nor does > the Trace Option under paraview tell what happens if a texture is assigned in > the GUI: > http://www.paraview.org/pipermail/paraview/2012-March/024255.html > http://www.paraview.org/Bug/view.php?id=12953 > > I've tried: > > import paraview.simple as pvs > > > reader = pvs.OpenDataFile("test.png) > #reader.UpdatePipelineInformation() > reader.UpdatePipeline() > print reader.GetDataInformation().GetBounds() # needs UpdatePipeline > > obj = pvs.Plane() > plane1Display = pvs.Show(obj) > plane1Display.Texture = reader > > dp = pvs.GetDisplayProperties(obj) > dp.Representation = 'Surface With Edges' > > dp.Texture = reader > > > but neither plane1Display.Texture nor dp.Texture seem to allow to set the > texture (see error below) > > Any help or hints are very much appreciated > Roman > > > RROR: In > /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, > line 390 > vtkPVSessionCore (0x258c2e0): Object type: vtkGlyph3DRepresentation, could not > find requested method: "SetTexture" > or the method was called with incorrect arguments. > > while processing > Message 0 = Invoke > Argument 0 = vtk_object_pointer {vtkGlyph3DRepresentation (0x551b0a0)} > Argument 1 = string_value {SetTexture} > Argument 2 = vtk_object_pointer {vtkImageFileSeriesReader (0x4f68190)} > > > ERROR: In > /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, > line 391 > vtkPVSessionCore (0x258c2e0): Aborting execution for debugging purposes. > > ############ ABORT ############# > ERROR: In > /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, > line 134 > vtkSISourceProxy (0x551af30): Error pushing property state: Texture > > global_id: 396 > location: 21 > [paraview_protobuf.ProxyState.property] { > name: "Texture" > value { > type: INPUT > proxy_global_id: 350 > port_number: 0 > } > } > ERROR: In > /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, > line 390 > vtkPVSessionCore (0x258c2e0): Object type: vtkOutlineRepresentation, could not > find requested method: "SetTexture" > or the method was called with incorrect arguments. > > while processing > Message 0 = Invoke > Argument 0 = vtk_object_pointer {vtkOutlineRepresentation (0x5549800)} > Argument 1 = string_value {SetTexture} > Argument 2 = vtk_object_pointer {vtkImageFileSeriesReader (0x4f68190)} > > > ERROR: In > /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, > line 391 > vtkPVSessionCore (0x258c2e0): Aborting execution for debugging purposes. > > ############ ABORT ############# > ERROR: In > /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, > line 134 > vtkSISourceProxy (0x5549690): Error pushing property state: Texture > > global_id: 407 > location: 21 > [paraview_protobuf.ProxyState.property] { > name: "Texture" > value { > type: INPUT > proxy_global_id: 350 > port_number: 0 > } > } > ERROR: In > /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, > line 390 > vtkPVSessionCore (0x258c2e0): Object type: vtkGeometryRepresentationWithFaces, > could not find requested method: "SetTexture" > or the method was called with incorrect arguments. > > while processing > Message 0 = Invoke > Argument 0 = vtk_object_pointer {vtkGeometryRepresentationWithFaces (0x59a6df0)} > Argument 1 = string_value {SetTexture} > Argument 2 = vtk_object_pointer {vtkImageFileSeriesReader (0x4f68190)} > > > ERROR: In > /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, > line 391 > vtkPVSessionCore (0x258c2e0): Aborting execution for debugging purposes. > > ############ ABORT ############# > ERROR: In > /opt/compilation/paraview-git/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, > line 134 > vtkSISourceProxy (0x5afc8e0): Error pushing property state: Texture > > global_id: 440 > location: 21 > [paraview_protobuf.ProxyState.property] { > name: "Texture" > value { > type: INPUT > proxy_global_id: 350 > port_number: 0 > } > } > > -- Dr. Roman Grothausmann Tomographie und Digitale Bildverarbeitung Tomography and Digital Image Analysis Institut f?r Funktionelle und Angewandte Anatomie, OE 4120 Medizinische Hochschule Hannover Carl-Neuberg-Str. 1 D-30625 Hannover Tel. +49 511 532-2900 From david.larsson at sth.kth.se Tue Dec 8 06:30:28 2015 From: david.larsson at sth.kth.se (David Larsson) Date: Tue, 8 Dec 2015 11:30:28 +0000 Subject: [Paraview] Velocity field analysis - lambda2 In-Reply-To: <423515563.19004573.1449526610447.JavaMail.root@mail.gatech.edu> References: <597591809.19003727.1449526290714.JavaMail.root@mail.gatech.edu>, <423515563.19004573.1449526610447.JavaMail.root@mail.gatech.edu> Message-ID: <1449574228617.82642@sth.kth.se> Hi Tim, thanks for your answer. Your method sound straight-forward. The only issue I have now is that I'm simply not sure how to control the Calculator of paraview. Following your steps, I want to set e.g.: 'Result Array Name': S_squared and then compute using the calculator something like (gradient(velocity) + transpose(gradient(velocity)))^2/2 but this gives me a calculator error ('Syntax Error: expecting a variable name'). So I assume I'm simply using the calculator the wrong way (giving input in an incorrect manor). Could you specify how you give input to the calculator following your outlined steps? Also, do you know the difference between the 'ComputeDerivative' and 'Gradient' is? Thanks again for the help, /David ________________________________ Fr?n: Tim Gallagher Skickat: den 7 december 2015 23:16 Till: tim gallagher Kopia: paraview at paraview.org; David Larsson ?mne: Re: [Paraview] Velocity field analysis - lambda2 For the sake of people years later who come across this thread, there is a typo in my definition and it should be: lambda_2 = S_ik S_kj + \Omega_ik \Omega_kj Tim ________________________________ From: "Tim Gallagher" To: "David Larsson" Cc: paraview at paraview.org Sent: Monday, December 7, 2015 5:11:30 PM Subject: Re: [Paraview] Velocity field analysis - lambda2 David, I haven't taken on lambda-2 yet, but I have been able to build a pipeline for Q-Criterion. It looks something like: Data -> CellDataToPointData (if it isn't already point data) -> ComputeDerivatives (set the gradient option to vorticity and the tensor option to strain) -> CellDataToPointData -> Calculator (compute |S|^2) -> Calculator (compute |\Omega|^2) -> Calculator (compute Q-criterion) Since lambda_2 = S_ik S_ij + \Omega_ik \Omega_kj, you can use the same procedure and use just the standard calculators if you want to expand the Einstein summation and plug them all. Once I've done this, I save the set of 3 calculators as a custom filter. When I use pvpython, I load my custom filter in the server manager and then use the CD2PD and ComputeDerivatives filters as needed. The python calculator might be a better way to do it, but I haven't tried that yet. Tim ________________________________ From: "David Larsson" To: paraview at paraview.org Sent: Monday, December 7, 2015 4:11:39 PM Subject: [Paraview] Velocity field analysis - lambda2 Dear all, I'm working with velocity vector fields over multiple time steps. I would like to compute a number of entities for the velocity field - most importantly the lambda2-scalar, but being relatively new to paraview I'm not really sure how to do that. I can do some simple modifications using the calculator but can't really find my way to grad() or curl() etc. I guess the solution is going over to pvpython (which would also be preferred with regards to doing automated analysis). Does anyone have any experience with performing numerical analysis of vector velocity fields in pvpython that could give some hints on how to get started? Or does anyone even have performed lambda2-analysis on such? I've seen some similar questions in the mail-list from before but can't seem to find a conclusive answer, so I thought I'd give it a try myself. Thanks for the help. /David _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Tue Dec 8 06:45:17 2015 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Tue, 8 Dec 2015 06:45:17 -0500 (EST) Subject: [Paraview] Velocity field analysis - lambda2 In-Reply-To: <1449574228617.82642@sth.kth.se> Message-ID: <1750838886.19046971.1449575117937.JavaMail.root@mail.gatech.edu> David, If you are using the filter called Calculator, there is no gradient nor transpose functions in it. The only functions you can use are the ones you can click on the little buttons in the GUI (you can type them instead of clicking, but those are the only ones available). So you must use the ComputeDerivative filter before the Calculator because you won't get the gradient any other way. Additionally, keep in mind that velocity is a vector and so the vector gradient of velocity will be a tensor output. It will have variable names like VectorGradient_0 through VectorGradient_8 when used inside the calculator. Only the scalar components are available, it doesn't work like a matrix in the Calculator filter. If you want to compute the strain (what I think your S is), you should use the ComputeDerivatives filter and set the "Vectors" to your velocity vector, set the "Output Tensor Type" to "Strain" and since you are after lambda_2, you should set the "Output Vector Type" to "Vorticity". Once this is done, you will have cell-data fields for strain and for vorticity. You probably want to do a CellDataToPointData filter to get this back to node-centered data (which is required if you want iso-surfaces). Once that is done, in your Calculator filter, you now have access to scalars called Strain_0 through Strain_8 and Vorticity_X, Vorticity_Y and Vorticity_Z. Strain_0 is S_xx, Strain_1 is S_xy, Strain_2 is S_xz, Strain_3 is S_yx... through to Strain_8 = S_zz. With all of those individual components, your Calculator filter for Lambda_2 will just be a bunch of products and sums of those terms. Tim ----- Original Message ----- From: "David Larsson" To: "Tim Gallagher" Cc: paraview at paraview.org Sent: Tuesday, December 8, 2015 6:30:28 AM Subject: SV: [Paraview] Velocity field analysis - lambda2 Hi Tim, thanks for your answer. Your method sound straight-forward. The only issue I have now is that I'm simply not sure how to control the Calculator of paraview. Following your steps, I want to set e.g.: 'Result Array Name': S_squared and then compute using the calculator something like (gradient(velocity) + transpose(gradient(velocity)))^2/2 but this gives me a calculator error ('Syntax Error: expecting a variable name'). So I assume I'm simply using the calculator the wrong way (giving input in an incorrect manor). Could you specify how you give input to the calculator following your outlined steps? Also, do you know the difference between the 'ComputeDerivative' and 'Gradient' is? Thanks again for the help, /David Fr?n: Tim Gallagher Skickat: den 7 december 2015 23:16 Till: tim gallagher Kopia: paraview at paraview.org; David Larsson ?mne: Re: [Paraview] Velocity field analysis - lambda2 For the sake of people years later who come across this thread, there is a typo in my definition and it should be: lambda_2 = S_ik S_kj + \Omega_ik \Omega_kj Tim ----- Original Message ----- From: "Tim Gallagher" To: "David Larsson" Cc: paraview at paraview.org Sent: Monday, December 7, 2015 5:11:30 PM Subject: Re: [Paraview] Velocity field analysis - lambda2 David, I haven't taken on lambda-2 yet, but I have been able to build a pipeline for Q-Criterion. It looks something like: Data -> CellDataToPointData (if it isn't already point data) -> ComputeDerivatives (set the gradient option to vorticity and the tensor option to strain) -> CellDataToPointData -> Calculator (compute |S|^2) -> Calculator (compute |\Omega|^2) -> Calculator (compute Q-criterion) Since lambda_2 = S_ik S_ij + \Omega_ik \Omega_kj, you can use the same procedure and use just the standard calculators if you want to expand the Einstein summation and plug them all. Once I've done this, I save the set of 3 calculators as a custom filter. When I use pvpython, I load my custom filter in the server manager and then use the CD2PD and ComputeDerivatives filters as needed. The python calculator might be a better way to do it, but I haven't tried that yet. Tim ----- Original Message ----- From: "David Larsson" To: paraview at paraview.org Sent: Monday, December 7, 2015 4:11:39 PM Subject: [Paraview] Velocity field analysis - lambda2 Dear all, I'm working with velocity vector fields over multiple time steps. I would like to compute a number of entities for the velocity field - most importantly the lambda2-scalar, but being relatively new to paraview I'm not really sure how to do that. I can do some simple modifications using the calculator but can't really find my way to grad() or curl() etc. I guess the solution is going over to pvpython (which would also be preferred with regards to doing automated analysis). Does anyone have any experience with performing numerical analysis of vector velocity fields in pvpython that could give some hints on how to get started? Or does anyone even have performed lambda2-analysis on such? I've seen some similar questions in the mail-list from before but can't seem to find a conclusive answer, so I thought I'd give it a try myself. Thanks for the help. /David _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Dec 8 13:58:00 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 8 Dec 2015 13:58:00 -0500 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: References: Message-ID: <20151208185800.GB23288@megas.khq.kitware.com> On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote: > I'm looking to provide run-time identification of the current OpenGL > backend in use. Some questions: > > 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is there a > particular reason we have both? VTK used to have both. VTKGL2 should be migrated to VTK_OPENGL2 (as VTK did). > 2. Is there an ideal place to define such a constant? Perhaps on the render > window? The About dialog has a list of information already (versions of Python, matplotlib, numpy, Qt, etc.). --Ben From dkxls23 at gmail.com Tue Dec 8 15:15:56 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Tue, 8 Dec 2015 22:15:56 +0200 Subject: [Paraview] Velocity field analysis - lambda2 In-Reply-To: <1750838886.19046971.1449575117937.JavaMail.root@mail.gatech.edu> References: <1750838886.19046971.1449575117937.JavaMail.root@mail.gatech.edu> Message-ID: <56673A7C.2010407@gmail.com> Hi, ParaView has several possibilities for user defined expressions, e.g: 1) "Calculator" filter 2) "Python Calculator" filter 3) "Programmable Filter" The "Calculator" filter is very limited and only suited for simple calculations (basically what you see in the GUI). The "Python Calculator" filter has a wider selection of functions, including a gradient function. For really advanced things, the "Programmable Filter" probably gives you the most flexibility. I have attached a very simple state file, that demonstrates how to use the "Python Calculator" filter with an arbitrary expression, i.e. "curl(gradient(RTData))" where RTData is a scalar field. The expression itself doesn't make much sense, but shows the basic principle. A really good introduction to all of this functionality is given in the ParaView user guide (section 5.8 and 13): http://www.paraview.org/paraview-guide/ HTH -Armin On 12/08/2015 01:45 PM, Tim Gallagher wrote: > David, > > If you are using the filter called Calculator, there is no gradient nor > transpose functions in it. The only functions you can use are the ones > you can click on the little buttons in the GUI (you can type them > instead of clicking, but those are the only ones available). So you must > use the ComputeDerivative filter before the Calculator because you won't > get the gradient any other way. > > Additionally, keep in mind that velocity is a vector and so the vector > gradient of velocity will be a tensor output. It will have variable > names like VectorGradient_0 through VectorGradient_8 when used inside > the calculator. Only the scalar components are available, it doesn't > work like a matrix in the Calculator filter. > > If you want to compute the strain (what I think your S is), you should > use the ComputeDerivatives filter and set the "Vectors" to your velocity > vector, set the "Output Tensor Type" to "Strain" and since you are > after lambda_2, you should set the "Output Vector Type" to "Vorticity". > > Once this is done, you will have cell-data fields for strain and for > vorticity. You probably want to do a CellDataToPointData filter to get > this back to node-centered data (which is required if you want > iso-surfaces). Once that is done, in your Calculator filter, you now > have access to scalars called Strain_0 through Strain_8 and Vorticity_X, > Vorticity_Y and Vorticity_Z. > > Strain_0 is S_xx, Strain_1 is S_xy, Strain_2 is S_xz, Strain_3 is > S_yx... through to Strain_8 = S_zz. > > With all of those individual components, your Calculator filter for > Lambda_2 will just be a bunch of products and sums of those terms. > > Tim > > ------------------------------------------------------------------------ > *From: *"David Larsson" > *To: *"Tim Gallagher" > *Cc: *paraview at paraview.org > *Sent: *Tuesday, December 8, 2015 6:30:28 AM > *Subject: *SV: [Paraview] Velocity field analysis - lambda2 > > Hi Tim, > > > thanks for your answer. Your method sound straight-forward. The only > issue I have now is that I'm simply not sure how to control the > Calculator of paraview. Following your steps, I want to set e.g.: > > > 'Result Array Name': S_squared > > > and then compute using the calculator something like > > > (gradient(velocity) + transpose(gradient(velocity)))^2/2 > > > but this gives me a calculator error ('Syntax Error: expecting a > variable name'). So I assume I'm simply using the calculator the wrong > way (giving input in an incorrect manor). > > > Could you specify how you give input to the calculator following your > outlined steps? Also, do you know the difference between the > 'ComputeDerivative' and 'Gradient' is? > > > Thanks again for the help, > > > /David > > > > > > ------------------------------------------------------------------------ > *Fr?n:* Tim Gallagher > *Skickat:* den 7 december 2015 23:16 > *Till:* tim gallagher > *Kopia:* paraview at paraview.org; David Larsson > *?mne:* Re: [Paraview] Velocity field analysis - lambda2 > For the sake of people years later who come across this thread, there is > a typo in my definition and it should be: > > lambda_2 = S_ik S_kj + \Omega_ik \Omega_kj > > Tim > > ------------------------------------------------------------------------ > *From: *"Tim Gallagher" > *To: *"David Larsson" > *Cc: *paraview at paraview.org > *Sent: *Monday, December 7, 2015 5:11:30 PM > *Subject: *Re: [Paraview] Velocity field analysis - lambda2 > > David, > > I haven't taken on lambda-2 yet, but I have been able to build a > pipeline for Q-Criterion. It looks something like: > > Data -> CellDataToPointData (if it isn't already point data) -> > ComputeDerivatives (set the gradient option to vorticity and the tensor > option to strain) -> CellDataToPointData -> Calculator (compute |S|^2) > -> Calculator (compute |\Omega|^2) -> Calculator (compute Q-criterion) > > Since lambda_2 = S_ik S_ij + \Omega_ik \Omega_kj, you can use the same > procedure and use just the standard calculators if you want to expand > the Einstein summation and plug them all. > > Once I've done this, I save the set of 3 calculators as a custom filter. > When I use pvpython, I load my custom filter in the server manager and > then use the CD2PD and ComputeDerivatives filters as needed. The python > calculator might be a better way to do it, but I haven't tried that yet. > > Tim > > ------------------------------------------------------------------------ > *From: *"David Larsson" > *To: *paraview at paraview.org > *Sent: *Monday, December 7, 2015 4:11:39 PM > *Subject: *[Paraview] Velocity field analysis - lambda2 > > Dear all, > > > I'm working with velocity vector fields over multiple time steps. I > would like to compute a number of entities for the velocity field - most > importantly the lambda2-scalar, but being relatively new to paraview I'm > not really sure how to do that. > > > I can do some simple modifications using the calculator but can't really > find my way to grad() or curl() etc. I guess the solution is going over > to pvpython (which would also be preferred with regards to doing > automated analysis). > > > Does anyone have any experience with performing numerical analysis of > vector velocity fields in pvpython that could give some hints on how to > get started? Or does anyone even have performed lambda2-analysis on such? > > > I've seen some similar questions in the mail-list from before but can't > seem to find a conclusive answer, so I thought I'd give it a try myself. > > > Thanks for the help. > > > /David > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- From vianamp at gmail.com Tue Dec 8 20:49:27 2015 From: vianamp at gmail.com (Matheus Viana) Date: Tue, 8 Dec 2015 23:49:27 -0200 Subject: [Paraview] How to get VTK source displayed in the view using python script Message-ID: Hi guys. If instead of creating a sphere using S=Sphere(), I use S = vtk.vtkSphereSource(), how do I get S displayed in the view? Thanks, *Matheus Viana* *Postdoctoral Research Employee* *Developmental and Cell Biology* *University of California Irvine* -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.larsson at sth.kth.se Wed Dec 9 07:35:57 2015 From: david.larsson at sth.kth.se (David Larsson) Date: Wed, 9 Dec 2015 12:35:57 +0000 Subject: [Paraview] Velocity field analysis - lambda2 In-Reply-To: <56673A7C.2010407@gmail.com> References: <1750838886.19046971.1449575117937.JavaMail.root@mail.gatech.edu> <56673A7C.2010407@gmail.com> Message-ID: <97ec026a63114854868abb0177424ee3@exdb01.ug.kth.se> Hi Armin and Tim, Thanks both for the helpful instructions. I think using your Python Calculator tip Armin is the way to go - however, I can't seem to find any transpose function there (according to http://www.vtk.org/Wiki/Python_Calculator ). Following numpy it should be something on the lines of myTensor.T but that doesn't seem to work... Anyway thanks for all the advice. Cheers David -----Ursprungligt meddelande----- Fr?n: ParaView [mailto:paraview-bounces at paraview.org] F?r Armin Wehrfritz Skickat: den 8 december 2015 21:16 Till: paraview at paraview.org ?mne: Re: [Paraview] Velocity field analysis - lambda2 Hi, ParaView has several possibilities for user defined expressions, e.g: 1) "Calculator" filter 2) "Python Calculator" filter 3) "Programmable Filter" The "Calculator" filter is very limited and only suited for simple calculations (basically what you see in the GUI). The "Python Calculator" filter has a wider selection of functions, including a gradient function. For really advanced things, the "Programmable Filter" probably gives you the most flexibility. I have attached a very simple state file, that demonstrates how to use the "Python Calculator" filter with an arbitrary expression, i.e. "curl(gradient(RTData))" where RTData is a scalar field. The expression itself doesn't make much sense, but shows the basic principle. A really good introduction to all of this functionality is given in the ParaView user guide (section 5.8 and 13): http://www.paraview.org/paraview-guide/ HTH -Armin On 12/08/2015 01:45 PM, Tim Gallagher wrote: > David, > > If you are using the filter called Calculator, there is no gradient > nor transpose functions in it. The only functions you can use are the > ones you can click on the little buttons in the GUI (you can type them > instead of clicking, but those are the only ones available). So you > must use the ComputeDerivative filter before the Calculator because > you won't get the gradient any other way. > > Additionally, keep in mind that velocity is a vector and so the vector > gradient of velocity will be a tensor output. It will have variable > names like VectorGradient_0 through VectorGradient_8 when used inside > the calculator. Only the scalar components are available, it doesn't > work like a matrix in the Calculator filter. > > If you want to compute the strain (what I think your S is), you should > use the ComputeDerivatives filter and set the "Vectors" to your > velocity vector, set the "Output Tensor Type" to "Strain" and since > you are after lambda_2, you should set the "Output Vector Type" to "Vorticity". > > Once this is done, you will have cell-data fields for strain and for > vorticity. You probably want to do a CellDataToPointData filter to get > this back to node-centered data (which is required if you want > iso-surfaces). Once that is done, in your Calculator filter, you now > have access to scalars called Strain_0 through Strain_8 and > Vorticity_X, Vorticity_Y and Vorticity_Z. > > Strain_0 is S_xx, Strain_1 is S_xy, Strain_2 is S_xz, Strain_3 is > S_yx... through to Strain_8 = S_zz. > > With all of those individual components, your Calculator filter for > Lambda_2 will just be a bunch of products and sums of those terms. > > Tim > > ---------------------------------------------------------------------- > -- > *From: *"David Larsson" > *To: *"Tim Gallagher" > *Cc: *paraview at paraview.org > *Sent: *Tuesday, December 8, 2015 6:30:28 AM > *Subject: *SV: [Paraview] Velocity field analysis - lambda2 > > Hi Tim, > > > thanks for your answer. Your method sound straight-forward. The only > issue I have now is that I'm simply not sure how to control the > Calculator of paraview. Following your steps, I want to set e.g.: > > > 'Result Array Name': S_squared > > > and then compute using the calculator something like > > > (gradient(velocity) + transpose(gradient(velocity)))^2/2 > > > but this gives me a calculator error ('Syntax Error: expecting a > variable name'). So I assume I'm simply using the calculator the wrong > way (giving input in an incorrect manor). > > > Could you specify how you give input to the calculator following your > outlined steps? Also, do you know the difference between the > 'ComputeDerivative' and 'Gradient' is? > > > Thanks again for the help, > > > /David > > > > tEIlfcjHJ6nx0MeBY57EwkoSX2SdYQPib-GqeXHouLYnDA.&URL=mailto%3adavid.lar > sson%40sth.kth.se> > > ---------------------------------------------------------------------- > -- > *Fr?n:* Tim Gallagher > *Skickat:* den 7 december 2015 23:16 > *Till:* tim gallagher > *Kopia:* paraview at paraview.org; David Larsson > *?mne:* Re: [Paraview] Velocity field analysis - lambda2 For the sake > of people years later who come across this thread, there is a typo in > my definition and it should be: > > lambda_2 = S_ik S_kj + \Omega_ik \Omega_kj > > Tim > > ---------------------------------------------------------------------- > -- > *From: *"Tim Gallagher" > *To: *"David Larsson" > *Cc: *paraview at paraview.org > *Sent: *Monday, December 7, 2015 5:11:30 PM > *Subject: *Re: [Paraview] Velocity field analysis - lambda2 > > David, > > I haven't taken on lambda-2 yet, but I have been able to build a > pipeline for Q-Criterion. It looks something like: > > Data -> CellDataToPointData (if it isn't already point data) -> > ComputeDerivatives (set the gradient option to vorticity and the > tensor option to strain) -> CellDataToPointData -> Calculator (compute > |S|^2) > -> Calculator (compute |\Omega|^2) -> Calculator (compute Q-criterion) > > Since lambda_2 = S_ik S_ij + \Omega_ik \Omega_kj, you can use the same > procedure and use just the standard calculators if you want to expand > the Einstein summation and plug them all. > > Once I've done this, I save the set of 3 calculators as a custom filter. > When I use pvpython, I load my custom filter in the server manager and > then use the CD2PD and ComputeDerivatives filters as needed. The > python calculator might be a better way to do it, but I haven't tried that yet. > > Tim > > ---------------------------------------------------------------------- > -- > *From: *"David Larsson" > *To: *paraview at paraview.org > *Sent: *Monday, December 7, 2015 4:11:39 PM > *Subject: *[Paraview] Velocity field analysis - lambda2 > > Dear all, > > > I'm working with velocity vector fields over multiple time steps. I > would like to compute a number of entities for the velocity field - > most importantly the lambda2-scalar, but being relatively new to > paraview I'm not really sure how to do that. > > > I can do some simple modifications using the calculator but can't > really find my way to grad() or curl() etc. I guess the solution is > going over to pvpython (which would also be preferred with regards to > doing automated analysis). > > > Does anyone have any experience with performing numerical analysis of > vector velocity fields in pvpython that could give some hints on how > to get started? Or does anyone even have performed lambda2-analysis on such? > > > I've seen some similar questions in the mail-list from before but > can't seem to find a conclusive answer, so I thought I'd give it a try myself. > > > Thanks for the help. > > > /David > > > > tEIlfcjHJ6nx0MeBY57EwkoSX2SdYQPib-GqeXHouLYnDA.&URL=mailto%3adavid.lar > sson%40sth.kth.se> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From archaerolog at mail.ru Wed Dec 9 09:11:36 2015 From: archaerolog at mail.ru (Gena Bug) Date: Wed, 9 Dec 2015 17:11:36 +0300 Subject: [Paraview] Can't set custom range value too small Message-ID: <56683698.4070500@mail.ru> Hi! Tried PV rc1 (5.0.0-RC1-20-g58e9aa1 64-bit) and found that I can't set range value (maximum) if it less than 1e-16 in Color Map Editor (Rescale to custom range). Yes, it's not a very good value, however, minimum can be set to less values. From joachim.pouderoux at kitware.com Wed Dec 9 11:12:09 2015 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Wed, 9 Dec 2015 17:12:09 +0100 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: <20151208185800.GB23288@megas.khq.kitware.com> References: <20151208185800.GB23288@megas.khq.kitware.com> Message-ID: BTW, I took a look but I do not see any way for a third party VTK or PV application that would not use CMake machinery (and use VTK_OPENGL_BACKEND) to know if the VTK it uses is based on OpenGL backend 1 or 2. VTK_OPENGL2 is a compiler definition provided to build VTK or PV but, as there is no global VTK configuration header, shouldn't we add a function in vtkRenderWindow to return the version of the backend it is based on? *Joachim Pouderoux* *PhD, Technical Expert* *Kitware SAS * 2015-12-08 19:58 GMT+01:00 Ben Boeckel : > On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote: > > I'm looking to provide run-time identification of the current OpenGL > > backend in use. Some questions: > > > > 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is there a > > particular reason we have both? > > VTK used to have both. VTKGL2 should be migrated to VTK_OPENGL2 (as VTK > did). > > > 2. Is there an ideal place to define such a constant? Perhaps on the > render > > window? > > The About dialog has a list of information already (versions of Python, > matplotlib, numpy, Qt, etc.). > > --Ben > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jim.Eliot at awe.co.uk Wed Dec 9 11:15:20 2015 From: Jim.Eliot at awe.co.uk (Jim.Eliot at awe.co.uk) Date: Wed, 9 Dec 2015 16:15:20 +0000 Subject: [Paraview] Displaying Cinema output Message-ID: <201512091615.tB9GFR9E011115@msw1.awe.co.uk> Good afternoon, How do I visualise ParaView Cinema output? I have been investigating ParaView Catalyst and am interested in the Cinema output option. I have run some simulations and have some images for a selection of angles, elevations and timesteps with an accompanying json file. Is there a way to visualise this data in ParaView or is another tool required? Kind regards, Jim Jim Eliot High Performance Computing Group AWE, Aldermaston, Reading, RG7 4PR The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Dec 9 11:34:23 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 9 Dec 2015 11:34:23 -0500 Subject: [Paraview] Displaying Cinema output In-Reply-To: <201512091615.tB9GFR9E011115@msw1.awe.co.uk> References: <201512091615.tB9GFR9E011115@msw1.awe.co.uk> Message-ID: Hi Jim, ParaView isn't the proper tool to view Cinema results. There are viewers available at http://www.cinemascience.org/download/. Under www.cinemascience.org there are links for documentation, getting started and sample data. The basic usage of the installer is to start the Cinema viewer and just load the json file. The controls in the upper-right corner are used to search through the different angles, elevations, time steps, etc. Please let us know if you have any questions. Best, Andy On Wed, Dec 9, 2015 at 11:15 AM, wrote: > > > Good afternoon, > > > > How do I visualise ParaView Cinema output? > > > > I have been investigating ParaView Catalyst and am interested in the > Cinema output option. I have run some simulations and have some images for > a selection of angles, elevations and timesteps with an accompanying json > file. > > > > Is there a way to visualise this data in ParaView or is another tool > required? > > > > Kind regards, > > Jim > > > > *Jim Eliot* > > *High Performance Computing Group* > > AWE, Aldermaston, Reading, RG7 4PR > > > > The information in this email and in any attachment(s) is commercial in > confidence. If you are not the named addressee(s) or if you receive this > email in error then any distribution, copying or use of this communication > or the information in it is strictly prohibited. Please notify us > immediately by email at admin.internet(at)awe.co.uk, and then delete this > message from your computer. While attachments are virus checked, AWE plc > does not accept any liability in respect of any virus which is not > detected. AWE Plc Registered in England and Wales Registration No 02763902 > AWE, Aldermaston, Reading, RG7 4PR > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Dec 9 11:37:11 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 9 Dec 2015 11:37:11 -0500 Subject: [Paraview] Displaying Cinema output In-Reply-To: <201512091615.tB9GFR9E011115@msw1.awe.co.uk> References: <201512091615.tB9GFR9E011115@msw1.awe.co.uk> Message-ID: Hi Jim. Head over to cinema science.org and download the desktop viewer. The web based viewer is also an option if you would like to put the results online. cheers, David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Dec 9, 2015 at 11:15 AM, wrote: > > > Good afternoon, > > > > How do I visualise ParaView Cinema output? > > > > I have been investigating ParaView Catalyst and am interested in the > Cinema output option. I have run some simulations and have some images for > a selection of angles, elevations and timesteps with an accompanying json > file. > > > > Is there a way to visualise this data in ParaView or is another tool > required? > > > > Kind regards, > > Jim > > > > *Jim Eliot* > > *High Performance Computing Group* > > AWE, Aldermaston, Reading, RG7 4PR > > > > The information in this email and in any attachment(s) is commercial in > confidence. If you are not the named addressee(s) or if you receive this > email in error then any distribution, copying or use of this communication > or the information in it is strictly prohibited. Please notify us > immediately by email at admin.internet(at)awe.co.uk, and then delete this > message from your computer. While attachments are virus checked, AWE plc > does not accept any liability in respect of any virus which is not > detected. AWE Plc Registered in England and Wales Registration No 02763902 > AWE, Aldermaston, Reading, RG7 4PR > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.thirion at kitware.com Wed Dec 9 11:54:46 2015 From: tim.thirion at kitware.com (Tim Thirion) Date: Wed, 9 Dec 2015 11:54:46 -0500 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: References: <20151208185800.GB23288@megas.khq.kitware.com> Message-ID: Yes, that was my original question. :) Is the vtkRenderWindow the best place for this? I'm happy to add it. On Wed, Dec 9, 2015 at 11:12 AM, Joachim Pouderoux < joachim.pouderoux at kitware.com> wrote: > BTW, I took a look but I do not see any way for a third party VTK or PV > application that would not use CMake machinery (and use VTK_OPENGL_BACKEND) > to know if the VTK it uses is based on OpenGL backend 1 or 2. > VTK_OPENGL2 is a compiler definition provided to build VTK or PV but, as > there is no global VTK configuration header, shouldn't we add a function in > vtkRenderWindow to return the version of the backend it is based on? > > *Joachim Pouderoux* > > *PhD, Technical Expert* > *Kitware SAS * > > > 2015-12-08 19:58 GMT+01:00 Ben Boeckel : > >> On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote: >> > I'm looking to provide run-time identification of the current OpenGL >> > backend in use. Some questions: >> > >> > 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is there a >> > particular reason we have both? >> >> VTK used to have both. VTKGL2 should be migrated to VTK_OPENGL2 (as VTK >> did). >> >> > 2. Is there an ideal place to define such a constant? Perhaps on the >> render >> > window? >> >> The About dialog has a list of information already (versions of Python, >> matplotlib, numpy, Qt, etc.). >> >> --Ben >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Wed Dec 9 12:00:26 2015 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Wed, 9 Dec 2015 12:00:26 -0500 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: References: <20151208185800.GB23288@megas.khq.kitware.com> Message-ID: There *is* a global VTK configuration header. vtkConfigure.h has many of these definitions and is included in vtkObjectBase.h (so pretty much everywhere). But you may be right that this should go somewhere in the rendering code rather than in there. I am not sure that vtkRenderWindow is the best location for it, but I am not as familiar with the code that uses the compiler definition. Does everywhere that #ifdefs VTK_OPENGL2 include vtkRenderWindow.h? Or would we have to pull in that header just for that macro? Shawn On Wed, Dec 9, 2015 at 11:54 AM, Tim Thirion wrote: > Yes, that was my original question. :) Is the vtkRenderWindow the best > place for this? I'm happy to add it. > > On Wed, Dec 9, 2015 at 11:12 AM, Joachim Pouderoux < > joachim.pouderoux at kitware.com> wrote: > >> BTW, I took a look but I do not see any way for a third party VTK or PV >> application that would not use CMake machinery (and use VTK_OPENGL_BACKEND) >> to know if the VTK it uses is based on OpenGL backend 1 or 2. >> VTK_OPENGL2 is a compiler definition provided to build VTK or PV but, as >> there is no global VTK configuration header, shouldn't we add a function in >> vtkRenderWindow to return the version of the backend it is based on? >> >> *Joachim Pouderoux* >> >> *PhD, Technical Expert* >> *Kitware SAS * >> >> >> 2015-12-08 19:58 GMT+01:00 Ben Boeckel : >> >>> On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote: >>> > I'm looking to provide run-time identification of the current OpenGL >>> > backend in use. Some questions: >>> > >>> > 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is there a >>> > particular reason we have both? >>> >>> VTK used to have both. VTKGL2 should be migrated to VTK_OPENGL2 (as VTK >>> did). >>> >>> > 2. Is there an ideal place to define such a constant? Perhaps on the >>> render >>> > window? >>> >>> The About dialog has a list of information already (versions of Python, >>> matplotlib, numpy, Qt, etc.). >>> >>> --Ben >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcus.hanwell at kitware.com Wed Dec 9 12:43:18 2015 From: marcus.hanwell at kitware.com (Marcus D. Hanwell) Date: Wed, 9 Dec 2015 12:43:18 -0500 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: References: <20151208185800.GB23288@megas.khq.kitware.com> Message-ID: vtkConfigure.h is definitely not the right place for this, and we worked pretty hard to move things out of it that didn't need to be there. It will cause almost all classes to recompile, and nothing in common is even aware of rendering backends. There is a configured header in the modules that record some settings (such as Cocoa, Carbon, X11, etc as far as I remember) that would be more appropriate. I haven't looked at the code in a while, adding something to configure it in seems reasonable. It is something we originally hoped could be decided at link time, and it has since become something that can only really be decided at compile time (which backend to use). With that in mind, you could simply define something in vtkRenderingCore's configured header stating which backend it was compiled with. Marcus On Wed, Dec 9, 2015 at 12:00 PM, Shawn Waldon wrote: > There *is* a global VTK configuration header. vtkConfigure.h has many of > these definitions and is included in vtkObjectBase.h (so pretty much > everywhere). But you may be right that this should go somewhere in the > rendering code rather than in there. I am not sure that vtkRenderWindow is > the best location for it, but I am not as familiar with the code that uses > the compiler definition. Does everywhere that #ifdefs VTK_OPENGL2 include > vtkRenderWindow.h? Or would we have to pull in that header just for that > macro? > > Shawn > > On Wed, Dec 9, 2015 at 11:54 AM, Tim Thirion > wrote: >> >> Yes, that was my original question. :) Is the vtkRenderWindow the best >> place for this? I'm happy to add it. >> >> On Wed, Dec 9, 2015 at 11:12 AM, Joachim Pouderoux >> wrote: >>> >>> BTW, I took a look but I do not see any way for a third party VTK or PV >>> application that would not use CMake machinery (and use VTK_OPENGL_BACKEND) >>> to know if the VTK it uses is based on OpenGL backend 1 or 2. >>> VTK_OPENGL2 is a compiler definition provided to build VTK or PV but, as >>> there is no global VTK configuration header, shouldn't we add a function in >>> vtkRenderWindow to return the version of the backend it is based on? >>> >>> Joachim Pouderoux >>> >>> PhD, Technical Expert >>> Kitware SAS >>> >>> >>> 2015-12-08 19:58 GMT+01:00 Ben Boeckel : >>>> >>>> On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote: >>>> > I'm looking to provide run-time identification of the current OpenGL >>>> > backend in use. Some questions: >>>> > >>>> > 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is there a >>>> > particular reason we have both? >>>> >>>> VTK used to have both. VTKGL2 should be migrated to VTK_OPENGL2 (as VTK >>>> did). >>>> >>>> > 2. Is there an ideal place to define such a constant? Perhaps on the >>>> > render >>>> > window? >>>> >>>> The About dialog has a list of information already (versions of Python, >>>> matplotlib, numpy, Qt, etc.). >>>> >>>> --Ben >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From cory.quammen at kitware.com Wed Dec 9 13:28:08 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 9 Dec 2015 13:28:08 -0500 Subject: [Paraview] Inconsistent new view with the defalut In-Reply-To: References: Message-ID: Hi all, Utkarsh merged a patch that should fix this issue in ParaView master. It will be available in the nightly builds in a few days and in the 5.0 release. Thanks, Cory On Mon, Dec 7, 2015 at 9:48 AM, Cory Quammen wrote: > Patch posted here: > https://gitlab.kitware.com/paraview/paraview/merge_requests/505 > > On Mon, Dec 7, 2015 at 9:32 AM, Cory Quammen > wrote: > >> Yes, that should be possible. I have a potential fix for this problem and >> should hopefully have it resolved in the next couple days. >> >> Cory >> >> On Sat, Dec 5, 2015 at 3:58 AM, Giuseppe Bilotta < >> giuseppe.bilotta at gmail.com> wrote: >> >>> On Fri, Dec 4, 2015 at 10:56 PM, Cory Quammen >>> wrote: >>> > Yoshimi, >>> > >>> > I looked into this issue some more. >>> > >>> > The server manager property is loaded as expected from the settings >>> file. >>> > However, camera settings are a little special as they are not updated >>> from >>> > the server manager. Data flows from the camera on the client to the >>> server >>> > only, not back. >>> > I'll have to think of a way to handle this case. >>> >>> Wouldn't it be possible to pass the value of that setting when the >>> camera is created, or use the same mechanism that is used to switch >>> between parallel and orthographic when clicking on the checkbox? >>> >>> (I'll confess to having looked at the problem before (it's one of the >>> reasons why I started looking into ways to contribute to paraview), >>> but I couldn't make head or tail of it. It's very difficult for me to >>> follow the code.) >>> >>> -- >>> Giuseppe "Oblomov" Bilotta >>> >> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From giuseppe.bilotta at gmail.com Wed Dec 9 14:42:02 2015 From: giuseppe.bilotta at gmail.com (Giuseppe Bilotta) Date: Wed, 9 Dec 2015 20:42:02 +0100 Subject: [Paraview] Inconsistent new view with the defalut In-Reply-To: References: Message-ID: On Wed, Dec 9, 2015 at 7:28 PM, Cory Quammen wrote: > Hi all, > > Utkarsh merged a patch that should fix this issue in ParaView master. It > will be available in the nightly builds in a few days and in the 5.0 > release. I can confirm that current master preserves the parallel projection as set on load (at least for me). -- Giuseppe "Oblomov" Bilotta From giuseppe.bilotta at gmail.com Wed Dec 9 14:48:01 2015 From: giuseppe.bilotta at gmail.com (Giuseppe Bilotta) Date: Wed, 9 Dec 2015 20:48:01 +0100 Subject: [Paraview] 'Plot Data' missing Points X/Y/Z as option for X axis on 5.0-RC? Message-ID: Hello, up until 4.4 I could use the Plot Data filter to plot any quantity over any spatial coordinate for the points. I would Pick "Points (0)" or "Points (1)" or "Points (2)" as X Array Name (after un-checking "Use index") and select any array I wanted to plot in the Series parameters. In 5.0-RC this doesn't seem to be possible anymore: I have Points X, Points Y and Points Z as options for the Series, but not for the X Array. There is a horrible workaround to plot a single array (pick the array as X and the Points X as Series), but it's a hack and it can't be use for multiple series. Suggestions? -- Giuseppe "Oblomov" Bilotta From wascott at sandia.gov Wed Dec 9 19:29:36 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 10 Dec 2015 00:29:36 +0000 Subject: [Paraview] Selecting a point in Python Message-ID: <9c2561ccdb6e4849b424e20638aa6c08@ES01AMSNLNT.srn.sandia.gov> I am trying to create a python script that will create a plot selection over time. Here is what I am trying to do: * Read in the can.exo. All vars on. Apply * Select point on can. (This is the line that does not record in the Trace Recorder, and I need). * Plot selection over time (I can't get here without the previous step). How is a selection done in Python? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Dec 9 19:33:50 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 10 Dec 2015 00:33:50 +0000 Subject: [Paraview] Plot3D function files over time Message-ID: <74016d790158419788290bf93bae822b@ES01AMSNLNT.srn.sandia.gov> Berk helped me loading Plot3D function files over numerous time steps, and I wanted to document it here. Here is my e-mail I sent to my user. ParaView can read and correctly handle Plot3D function files over numerous time steps. The trick is that you need to create a master file that tells the Plot3D function reader how to find the files it needs, and how to read them. Using your example datasets, I created a master file named master.p3d. (You can name it anything, but the extension must be p3d.) Inside this file, I wrote the following. Be sure to watch the comas at the end of the lines. { "auto-detect-format" : true, "filenames" : [ { "time" : 0, "xyz" : "solver.xyz", "function" : "solver-0070000.fun" }, { "time" : 1, "xyz" : "solver.xyz", "function" : "solver-0070100.fun" }, { "time" : 2, "xyz" : "solver.xyz", "function" : "solver-0070200.fun" } ] } Then, file/ open the master.p3d file. Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Thu Dec 10 03:51:41 2015 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Thu, 10 Dec 2015 09:51:41 +0100 Subject: [Paraview] ParaView Environment Variables In-Reply-To: References: <5620138A.9060407@indiana.edu> Message-ID: This is a good idea and for information Utkarsh started to write this documentation in Utilities/Doxygen/pages/EnvironmentVariables.md For now it is just in a merge request (and it is not complete) but no doubt if will be in master very soon! https://gitlab.kitware.com/paraview/paraview/merge_requests/511 Joachim *Joachim Pouderoux* *PhD, Technical Expert* *Kitware SAS * 2015-10-19 19:31 GMT+02:00 Cory Quammen : > Hi Bill, > > This is a good project. Perhaps we can include a version of your man page > in the user's guide when it is finished? > > I know about some of these environment variables: > > - PARAVIEW_DATA_ROOT - used to point ParaView to a testing data > repository. This is really only used when ParaView's tests are run and > likely isn't useful to users. > > - PV_NO_OFFSCREEN_SCREENSHOTS - just what it sounds like. If set, > offscreen rendering will not be used for generating screenshots, even if > the ParaView settings say that offscreen rendering should be used for > generating screenshots. > > - VTK_AUTOLOAD_PATH - users shouldn't need to set this. From the > vtkObjectFactory documentation: "The first time CreateInstance is called, > all dll's or shared libraries in the environment variable VTK_AUTOLOAD_PATH > are loaded into the current process." > > - VTK_RENDERER - this looks like a historical way to choose which render > window to instantiate. It doesn't look like it is used anymore. > > - PV_DEBUG_LEAKS_VIEW - enables a window that shows the number of > instances of all VTK classes. Useful for debugging, not really useful for > users. > > -PV_DEBUG_TEST - I don't see this in the ParaView source anywhere > > - PV_SETTINGS_DEBUG - turns on debugging message related to loading > ParaView's settings files, e.g., where it looked for the settings file. > > - PV_PLUGIN_DEBUG - print debugging output having to do with where > ParaView looks for plugins. > > - PV_PLUGIN_PATH - adds search path for plugins > > - VTK_MATPLOTLIB_DEBUG - Enable verbose debugging output during > initialization of matplotlib. > > Hope that helps, > Cory > > On Thu, Oct 15, 2015 at 4:58 PM, Bill Sherman > wrote: > >> Hello all, >> >> Perhaps an odd question -- I'm wondering what important environment >> variables are associated with ParaView, and in some cases what they >> do. >> >> I ask because for an installation of ParaView on an HPC system, I >> am creating a traditional man-page. And one of the traditional >> sections of man pages for applications is "ENVIRONMENT VARIABLES". >> >> I happened to find that NERSC had previously done a similar thing, >> but based on the command line arguments as well as the environment >> variables it gives no longer in existence, it would seem that this >> is from a rather old version of ParaView, so I'm basically starting >> from scratch. >> >> Searching through the source for "getenv", I found several refernces >> to environment variables, and I'd like to get advice on what should/ >> should not be included. >> >> So there are a couple of categories the environment variables can >> be classified as. >> >> 1) ParaView specific variables: >> - PV_ICET_WINDOW_BORDERS >> - PARAVIEW_DATA_ROOT >> - PV_NO_OFFSCREEN_SCREENSHOTS >> >> So I know what the first of those does, and I had an assumption of >> what the second one (PARAVIEW_DATA_ROOT) does -- but I couldn't find >> a way to make it have an effect! And I can half-guess what the third >> one does -- explanations welcome. >> >> >> 2) VTK related variables: >> - VTK_AUTOLOAD_PATH >> - VTK_RENDERER >> >> And I don't really know what either of them do. >> >> >> 3) Generic environment variables that ParaView accesses: >> - DISPLAY >> - HOME >> - HOSTNAME >> - LOGNAME >> - PATH >> - LD_LIBRARY_PATH >> - PWD (VTK/Utilities/KWSys/vtksys/SystemTools.cxx) >> - PYTHONPATH >> - TCL_LIBRARY (vtkTclUtil.cxx) >> - TK_LIBRARY (vtkTclUtil.cxx) >> - R_HOME (vtkRInterface.cxx) >> - COLUMNS (VTK/Utilities/KWSys/vtksys/SystemTools.cxx) >> - APPDATA -- for MS-Windows only? >> - COMMON_APPDATA -- for MS-Windows only? >> >> So I don't know that I'd need to include those as part of a ParaView >> man-page. >> >> >> 4) Other variables that are probably just for internal testing: >> - PV_DEBUG_LEAKS_VIEW >> - PV_DEBUG_TEST >> - PV_SETTINGS_DEBUG >> - PV_PLUGIN_DEBUG >> - PV_PLUGIN_PATH >> - DASHBOARD_TEST_FROM_CTEST >> - DART_TEST_FROM_DART >> - VERBOSE_TESTING (Exodus) >> - VERY_VERBOSE_TESTING (Exodus) >> - FLIP_CAM_MANIP (Interactor Style Unicam) >> - VTK_MATPLOTLIB_DEBUG (vtkMatplotlibMathTextUtilities.cxx) >> - QT_MAC_NO_NATIVE_MENUBAR >> (ThirdParty/QtTesting/vtkqttesting/pqTestUtility.cxx) >> >> Again, probably wouldn't include these in a man-page, unless they are >> something the end-user could possibly want to affect. >> >> >> Happy to share the man-page when I'm done. >> >> Thanks, >> Bill >> >> -- >> Bill Sherman >> Sr. Technology Advisor >> Advanced Visualization Lab >> Pervasive Technology Inst >> Indiana University >> shermanw at indiana.edu >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Thu Dec 10 04:53:52 2015 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Thu, 10 Dec 2015 10:53:52 +0100 Subject: [Paraview] 'Plot Data' missing Points X/Y/Z as option for X axis on 5.0-RC? In-Reply-To: References: Message-ID: Giuseppe, You are right. I think this is something we should have addressed with https://gitlab.kitware.com/paraview/paraview/merge_requests/385 So I have just made a patch for this: https://gitlab.kitware.com/paraview/paraview/merge_requests/515 If it is all OK it should be ready for 5.0RC2 (at worst for 5.0 final). Best, *Joachim Pouderoux* *PhD, Technical Expert* *Kitware SAS * 2015-12-09 20:48 GMT+01:00 Giuseppe Bilotta : > Hello, > > up until 4.4 I could use the Plot Data filter to plot any quantity > over any spatial coordinate for the points. I would Pick "Points (0)" > or "Points (1)" or "Points (2)" as X Array Name (after un-checking > "Use index") and select any array I wanted to plot in the Series > parameters. > > In 5.0-RC this doesn't seem to be possible anymore: I have Points X, > Points Y and Points Z as options for the Series, but not for the X > Array. There is a horrible workaround to plot a single array (pick the > array as X and the Points X as Series), but it's a hack and it can't > be use for multiple series. > > Suggestions? > > -- > Giuseppe "Oblomov" Bilotta > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Dec 10 08:29:48 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 10 Dec 2015 08:29:48 -0500 Subject: [Paraview] www.paraview.org down for maintenance Thursday, 5:30pm EST Message-ID: www.paraview.org will be offline for an hour or so for maintenance starting today (Thursday, December 10, 2015) at 5:30pm EST. Git repositories on paraview.org will also be unavailable. Cheers, Cory -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank.albina at sauber-motorsport.com Thu Dec 10 08:47:45 2015 From: frank.albina at sauber-motorsport.com (Albina, Frank) Date: Thu, 10 Dec 2015 14:47:45 +0100 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 Message-ID: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> Hi all! First of all, thanks for all the effort spent on porting the rendering engine to support the OpenGL2 backend by default on PV 5.0.0. Early tests with the binary from the download page shows a massive improvement over the PV 4.1 to 4.3 versions in terms of rendering time. I have repeated the test over a few different GPUs and got the same results. Which brought me to thinking that similar performance improvements could be also achieved when performing software rendering with the MESA libraries. I downloaded the PV sources for the 5.0.0-RC1 release yesterday and compiled it with MESA and MPI support. MPI version is Intel 5.0.1 and MESA version is 10.5.5. The MESA libraries are compiled using: ./configure --enable-64-bit --enable-texture-float --enable-osmesa --disable-egl --disable-xorg --disable-xvmc --disable-opencl --disable-glx --disable-dri --disable-va --disable-shared-glapi --enable-gallium-llvm=no --with-gnu-ld --with-osmesa-bits=8 --disable-vdpau --enable-dependency-tracking --with-gallium-drivers="" --with-dri-drivers="" --with-egl-platforms="" Which corresponds to a "classic" compilation without LLVM support. Believe it or not, this was found to run faster on our CPU cluster than with the LLVM drivers. After linking PV 5.0.0 against the MESA libs with the OpenGL2 backend, I started running a simple benchmark to check possible performance benefits and here is the error output I got: GL_Version: 2.1 Mesa 10.5.5 Warning: In /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 549 vtkOSOpenGLRenderWindow (0x3c0eef60): VTK is designed to work with OpenGL version 3.2 but it appears it has been given a context that does not support 3.2. VTK will run in a compatibility mode designed to work with OpenGL 2.1 but some features may not work. ERROR: In /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, line 369 vtkShaderProgram (0x4d4dbfe0): 1: #version 120 2: #extension GL_EXT_gpu_shader4 : require 3: #define highp 4: #define mediump 5: #define lowp 6: 7: /*========================================================================= 8: 9: Program: Visualization Toolkit 10: Module: vtkPolyDataFS.glsl 11: 12: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 13: All rights reserved. 14: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 15: 16: This software is distributed WITHOUT ANY WARRANTY; without even 17: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 18: PURPOSE. See the above copyright notice for more information. 19: 20: =========================================================================*/ 21: // Template for the polydata mappers fragment shader 22: 23: uniform int PrimitiveIDOffset; 24: 25: // VC position of this fragment 26: varying vec4 vertexVCVSOutput; 27: 28: // optional color passed in from the vertex shader, vertexColor 29: uniform bool OverridesColor; 30: uniform float opacityUniform; // the fragment opacity 31: uniform vec3 ambientColorUniform; // intensity weighted color 32: uniform vec3 diffuseColorUniform; // intensity weighted color 33: uniform vec3 specularColorUniform; // intensity weighted color 34: uniform float specularPowerUniform; 35: 36: 37: // optional surface normal declaration 38: uniform int cameraParallel; 39: 40: // extra lighting parameters 41: uniform int numberOfLights; 42: uniform vec3 lightColor[6]; 43: uniform vec3 lightDirectionVC[6]; // normalized 44: uniform vec3 lightHalfAngleVC[6]; // normalized 45: 46: // Texture coordinates 47: varying vec2 tcoordVCVSOutput; uniform sampler2D texture1; 48: 49: // picking support 50: //VTK::Picking::Dec 51: 52: // Depth Peeling Support 53: //VTK::DepthPeeling::Dec 54: 55: // clipping plane vars 56: //VTK::Clip::Dec 57: 58: // the output of this shader 59: //VTK::Output::Dec 60: 61: // Apple Bug 62: //VTK::PrimID::Dec 63: 64: void main() 65: { 66: // Apple Bug 67: //VTK::PrimID::Impl 68: 69: //VTK::Clip::Impl 70: 71: vec3 ambientColor; 72: vec3 diffuseColor; 73: float opacity; 74: vec3 specularColor; 75: float specularPower; 76: ambientColor = ambientColorUniform; 77: diffuseColor = diffuseColorUniform; 78: opacity = opacityUniform; 79: specularColor = specularColorUniform; 80: specularPower = specularPowerUniform; 81: vec4 texColor = texture2D(texture1, tcoordVCVSOutput.st); 82: diffuseColor = texColor.rgb; 83: opacity = opacity*texColor.a; 84: if (OverridesColor) { 85: ambientColor = ambientColorUniform; 86: diffuseColor = diffuseColorUniform; } 87: 88: 89: // VC position of this fragment 90: vec4 vertexVC = vertexVCVSOutput; 91: 92: // Generate the normal if we are not passed in one 93: vec3 fdx = normalize(vec3(dFdx(vertexVC.x),dFdx(vertexVC.y),dFdx(vertexVC.z))); 94: vec3 fdy = normalize(vec3(dFdy(vertexVC.x),dFdy(vertexVC.y),dFdy(vertexVC.z))); 95: vec3 normalVCVSOutput = normalize(cross(fdx,fdy)); 96: if (cameraParallel == 1 && normalVCVSOutput.z < 0.0) { normalVCVSOutput = -1.0*normalVCVSOutput; } 97: if (cameraParallel == 0 && dot(normalVCVSOutput,vertexVC.xyz) > 0.0) { normalVCVSOutput = -1.0*normalVCVSOutput; } 98: 99: vec3 diffuse = vec3(0,0,0); 100: vec3 specular = vec3(0,0,0); 101: for (int lightNum = 0; lightNum < numberOfLights; lightNum++) 102: { 103: float df = max(0.0, dot(normalVCVSOutput, -lightDirectionVC[lightNum])); 104: diffuse += ((df) * lightColor[lightNum]); 105: if (dot(normalVCVSOutput, lightDirectionVC[lightNum]) < 0.0) 106: { 107: float sf = pow( max(0.0, dot(lightHalfAngleVC[lightNum],normalVCVSOutput)), specularPower); 108: specular += ((sf) * lightColor[lightNum]); 109: } 110: } 111: diffuse = diffuse * diffuseColor; 112: specular = specular * specularColor; 113: gl_FragData[0] = vec4(ambientColor + diffuse + specular, opacity); //VTK::Light::Impl 114: 115: //VTK::TCoord::Impl 116: 117: if (gl_FragData[0].a <= 0.0) 118: { 119: discard; 120: } 121: 122: //VTK::DepthPeeling::Impl 123: 124: //VTK::Picking::Impl 125: 126: } 127: ERROR: In /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, line 370 vtkShaderProgram (0x4d4dbfe0): 0:2(12): error: extension `GL_EXT_gpu_shader4' unsupported in fragment shader APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11) Was it to be expected? If so, is there any chance at all to run PV 5.0.0 in batch with MESA support on a CPU cluster? If so, which MESA version is required/recommended and what are the compile options to pass? Thank you very much in advance for any answer. Frank Albina -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Thu Dec 10 09:18:44 2015 From: ken.martin at kitware.com (Ken Martin) Date: Thu, 10 Dec 2015 09:18:44 -0500 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> Message-ID: Thanks Frank, This is an area we are actively working to cleanup right now. Both in catching it more gracefully and in providing better messages to help people understand what the next step should be. I believe if you are in an Intel based system that using their new SWR backend for mesa ( http://openswr.org/ ) might give the best software rendering performance. I think it requires a more recent version of Mesa, we suggest Mesa 10.6.5 or later for VTK. Other people on this list are more familiar with the specifics of setting up SWR and Mesa on a cluster but I wanted to at least give you a quick response to let you know we are working on it :-) Thanks Ken On Thu, Dec 10, 2015 at 8:47 AM, Albina, Frank < frank.albina at sauber-motorsport.com> wrote: > Hi all! > > > > First of all, thanks for all the effort spent on porting the rendering > engine to support the OpenGL2 backend by default on PV 5.0.0. Early tests > with the binary from the download page shows a massive improvement over the > PV 4.1 to 4.3 versions in terms of rendering time. I have repeated the test > over a few different GPUs and got the same results. > > > > Which brought me to thinking that similar performance improvements could > be also achieved when performing software rendering with the MESA > libraries. I downloaded the PV sources for the 5.0.0-RC1 release yesterday > and compiled it with MESA and MPI support. MPI version is Intel 5.0.1 and > MESA version is 10.5.5. The MESA libraries are compiled using: > > > > ./configure --enable-64-bit --enable-texture-float --enable-osmesa > --disable-egl --disable-xorg --disable-xvmc --disable-opencl --disable-glx > --disable-dri --disable-va --disable-shared-glapi --enable-gallium-llvm=no > --with-gnu-ld --with-osmesa-bits=8 --disable-vdpau > --enable-dependency-tracking --with-gallium-drivers=?? > --with-dri-drivers=?? --with-egl-platforms=?? > > > > Which corresponds to a ?classic? compilation without LLVM support. Believe > it or not, this was found to run faster on our CPU cluster than with the > LLVM drivers. > > > > After linking PV 5.0.0 against the MESA libs with the OpenGL2 backend, I > started running a simple benchmark to check possible performance benefits > and here is the error output I got: > > > > GL_Version: 2.1 Mesa 10.5.5 > > Warning: In > /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, > line 549 > > vtkOSOpenGLRenderWindow (0x3c0eef60): VTK is designed to work with OpenGL > version 3.2 but it appears it has been given a context that does not > support 3.2. VTK will run in a compatibility mode designed to work with > OpenGL 2.1 but some features may not work. > > > > ERROR: In > /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, > line 369 > > vtkShaderProgram (0x4d4dbfe0): 1: #version 120 > > 2: #extension GL_EXT_gpu_shader4 : require > > 3: #define highp > > 4: #define mediump > > 5: #define lowp > > 6: > > 7: > /*========================================================================= > > 8: > > 9: Program: Visualization Toolkit > > 10: Module: vtkPolyDataFS.glsl > > 11: > > 12: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen > > 13: All rights reserved. > > 14: See Copyright.txt or http://www.kitware.com/Copyright.htm for > details. > > 15: > > 16: This software is distributed WITHOUT ANY WARRANTY; without even > > 17: the implied warranty of MERCHANTABILITY or FITNESS FOR A > PARTICULAR > > 18: PURPOSE. See the above copyright notice for more information. > > 19: > > 20: > =========================================================================*/ > > 21: // Template for the polydata mappers fragment shader > > 22: > > 23: uniform int PrimitiveIDOffset; > > 24: > > 25: // VC position of this fragment > > 26: varying vec4 vertexVCVSOutput; > > 27: > > 28: // optional color passed in from the vertex shader, vertexColor > > 29: uniform bool OverridesColor; > > 30: uniform float opacityUniform; // the fragment opacity > > 31: uniform vec3 ambientColorUniform; // intensity weighted color > > 32: uniform vec3 diffuseColorUniform; // intensity weighted color > > 33: uniform vec3 specularColorUniform; // intensity weighted color > > 34: uniform float specularPowerUniform; > > 35: > > 36: > > 37: // optional surface normal declaration > > 38: uniform int cameraParallel; > > 39: > > 40: // extra lighting parameters > > 41: uniform int numberOfLights; > > 42: uniform vec3 lightColor[6]; > > 43: uniform vec3 lightDirectionVC[6]; // normalized > > 44: uniform vec3 lightHalfAngleVC[6]; // normalized > > 45: > > 46: // Texture coordinates > > 47: varying vec2 tcoordVCVSOutput; uniform sampler2D texture1; > > 48: > > 49: // picking support > > 50: //VTK::Picking::Dec > > 51: > > 52: // Depth Peeling Support > > 53: //VTK::DepthPeeling::Dec > > 54: > > 55: // clipping plane vars > > 56: //VTK::Clip::Dec > > 57: > > 58: // the output of this shader > > 59: //VTK::Output::Dec > > 60: > > 61: // Apple Bug > > 62: //VTK::PrimID::Dec > > 63: > > 64: void main() > > 65: { > > 66: // Apple Bug > > 67: //VTK::PrimID::Impl > > 68: > > 69: //VTK::Clip::Impl > > 70: > > 71: vec3 ambientColor; > > 72: vec3 diffuseColor; > > 73: float opacity; > > 74: vec3 specularColor; > > 75: float specularPower; > > 76: ambientColor = ambientColorUniform; > > 77: diffuseColor = diffuseColorUniform; > > 78: opacity = opacityUniform; > > 79: specularColor = specularColorUniform; > > 80: specularPower = specularPowerUniform; > > 81: vec4 texColor = texture2D(texture1, tcoordVCVSOutput.st); > > 82: diffuseColor = texColor.rgb; > > 83: opacity = opacity*texColor.a; > > 84: if (OverridesColor) { > > 85: ambientColor = ambientColorUniform; > > 86: diffuseColor = diffuseColorUniform; } > > 87: > > 88: > > 89: // VC position of this fragment > > 90: vec4 vertexVC = vertexVCVSOutput; > > 91: > > 92: // Generate the normal if we are not passed in one > > 93: vec3 fdx = > normalize(vec3(dFdx(vertexVC.x),dFdx(vertexVC.y),dFdx(vertexVC.z))); > > 94: vec3 fdy = > normalize(vec3(dFdy(vertexVC.x),dFdy(vertexVC.y),dFdy(vertexVC.z))); > > 95: vec3 normalVCVSOutput = normalize(cross(fdx,fdy)); > > 96: if (cameraParallel == 1 && normalVCVSOutput.z < 0.0) { > normalVCVSOutput = -1.0*normalVCVSOutput; } > > 97: if (cameraParallel == 0 && dot(normalVCVSOutput,vertexVC.xyz) > 0.0) > { normalVCVSOutput = -1.0*normalVCVSOutput; } > > 98: > > 99: vec3 diffuse = vec3(0,0,0); > > 100: vec3 specular = vec3(0,0,0); > > 101: for (int lightNum = 0; lightNum < numberOfLights; lightNum++) > > 102: { > > 103: float df = max(0.0, dot(normalVCVSOutput, > -lightDirectionVC[lightNum])); > > 104: diffuse += ((df) * lightColor[lightNum]); > > 105: if (dot(normalVCVSOutput, lightDirectionVC[lightNum]) < 0.0) > > 106: { > > 107: float sf = pow( max(0.0, > dot(lightHalfAngleVC[lightNum],normalVCVSOutput)), specularPower); > > 108: specular += ((sf) * lightColor[lightNum]); > > 109: } > > 110: } > > 111: diffuse = diffuse * diffuseColor; > > 112: specular = specular * specularColor; > > 113: gl_FragData[0] = vec4(ambientColor + diffuse + specular, opacity); > //VTK::Light::Impl > > 114: > > 115: //VTK::TCoord::Impl > > 116: > > 117: if (gl_FragData[0].a <= 0.0) > > 118: { > > 119: discard; > > 120: } > > 121: > > 122: //VTK::DepthPeeling::Impl > > 123: > > 124: //VTK::Picking::Impl > > 125: > > 126: } > > 127: > > > > > > ERROR: In > /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, > line 370 > > vtkShaderProgram (0x4d4dbfe0): 0:2(12): error: extension > `GL_EXT_gpu_shader4' unsupported in fragment shader > > > > > > APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11) > > > > Was it to be expected? If so, is there any chance at all to run PV 5.0.0 > in batch with MESA support on a CPU cluster? If so, which MESA version is > required/recommended and what are the compile options to pass? > > > Thank you very much in advance for any answer. > > > > *Frank Albina * > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Thu Dec 10 09:29:27 2015 From: ken.martin at kitware.com (Ken Martin) Date: Thu, 10 Dec 2015 09:29:27 -0500 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: References: <20151208185800.GB23288@megas.khq.kitware.com> Message-ID: Maybe vtkRenderingOpenGLConfigure.h ? That header is configured from a .in file for both the old and new backend. We could define VTK_OPENGL2 in that header and applications could include it as needed. That header appears to get installed. The only issue I see is that if someone built VTK with no rendering then that header file might not exist. Does that work? If so I can put the VTK_OPENGL2 definition in there. On Wed, Dec 9, 2015 at 12:43 PM, Marcus D. Hanwell < marcus.hanwell at kitware.com> wrote: > vtkConfigure.h is definitely not the right place for this, and we > worked pretty hard to move things out of it that didn't need to be > there. It will cause almost all classes to recompile, and nothing in > common is even aware of rendering backends. There is a configured > header in the modules that record some settings (such as Cocoa, > Carbon, X11, etc as far as I remember) that would be more appropriate. > > I haven't looked at the code in a while, adding something to configure > it in seems reasonable. It is something we originally hoped could be > decided at link time, and it has since become something that can only > really be decided at compile time (which backend to use). With that in > mind, you could simply define something in vtkRenderingCore's > configured header stating which backend it was compiled with. > > Marcus > > On Wed, Dec 9, 2015 at 12:00 PM, Shawn Waldon > wrote: > > There *is* a global VTK configuration header. vtkConfigure.h has many of > > these definitions and is included in vtkObjectBase.h (so pretty much > > everywhere). But you may be right that this should go somewhere in the > > rendering code rather than in there. I am not sure that vtkRenderWindow > is > > the best location for it, but I am not as familiar with the code that > uses > > the compiler definition. Does everywhere that #ifdefs VTK_OPENGL2 > include > > vtkRenderWindow.h? Or would we have to pull in that header just for that > > macro? > > > > Shawn > > > > On Wed, Dec 9, 2015 at 11:54 AM, Tim Thirion > > wrote: > >> > >> Yes, that was my original question. :) Is the vtkRenderWindow the best > >> place for this? I'm happy to add it. > >> > >> On Wed, Dec 9, 2015 at 11:12 AM, Joachim Pouderoux > >> wrote: > >>> > >>> BTW, I took a look but I do not see any way for a third party VTK or PV > >>> application that would not use CMake machinery (and use > VTK_OPENGL_BACKEND) > >>> to know if the VTK it uses is based on OpenGL backend 1 or 2. > >>> VTK_OPENGL2 is a compiler definition provided to build VTK or PV but, > as > >>> there is no global VTK configuration header, shouldn't we add a > function in > >>> vtkRenderWindow to return the version of the backend it is based on? > >>> > >>> Joachim Pouderoux > >>> > >>> PhD, Technical Expert > >>> Kitware SAS > >>> > >>> > >>> 2015-12-08 19:58 GMT+01:00 Ben Boeckel : > >>>> > >>>> On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote: > >>>> > I'm looking to provide run-time identification of the current OpenGL > >>>> > backend in use. Some questions: > >>>> > > >>>> > 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is there > a > >>>> > particular reason we have both? > >>>> > >>>> VTK used to have both. VTKGL2 should be migrated to VTK_OPENGL2 (as > VTK > >>>> did). > >>>> > >>>> > 2. Is there an ideal place to define such a constant? Perhaps on the > >>>> > render > >>>> > window? > >>>> > >>>> The About dialog has a list of information already (versions of > Python, > >>>> matplotlib, numpy, Qt, etc.). > >>>> > >>>> --Ben > >>>> _______________________________________________ > >>>> Powered by www.kitware.com > >>>> > >>>> Visit other Kitware open-source projects at > >>>> http://www.kitware.com/opensource/opensource.html > >>>> > >>>> Please keep messages on-topic and check the ParaView Wiki at: > >>>> http://paraview.org/Wiki/ParaView > >>>> > >>>> Search the list archives at: http://markmail.org/search/?q=ParaView > >>>> > >>>> Follow this link to subscribe/unsubscribe: > >>>> http://public.kitware.com/mailman/listinfo/paraview > >>> > >>> > >> > >> > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: > >> http://paraview.org/Wiki/ParaView > >> > >> Search the list archives at: http://markmail.org/search/?q=ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview > >> > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Thu Dec 10 09:39:30 2015 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Thu, 10 Dec 2015 15:39:30 +0100 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: References: <20151208185800.GB23288@megas.khq.kitware.com> Message-ID: vtkRenderingOpenGLConfigure.h seems indeed the right place. I propose to also add a VTK_OPENGL1 - let's get prepared for the future. And we could also add #define VTK_OPENGL_BACKEND_VERSION [1|2] J. 2015-12-10 15:29 GMT+01:00 Ken Martin : > Maybe vtkRenderingOpenGLConfigure.h ? > > That header is configured from a .in file for both the old and new > backend. We could define VTK_OPENGL2 in that header and applications could > include it as needed. That header appears to get installed. The only issue > I see is that if someone built VTK with no rendering then that header file > might not exist. > > Does that work? If so I can put the VTK_OPENGL2 definition in there. > > > On Wed, Dec 9, 2015 at 12:43 PM, Marcus D. Hanwell < > marcus.hanwell at kitware.com> wrote: > >> vtkConfigure.h is definitely not the right place for this, and we >> worked pretty hard to move things out of it that didn't need to be >> there. It will cause almost all classes to recompile, and nothing in >> common is even aware of rendering backends. There is a configured >> header in the modules that record some settings (such as Cocoa, >> Carbon, X11, etc as far as I remember) that would be more appropriate. >> >> I haven't looked at the code in a while, adding something to configure >> it in seems reasonable. It is something we originally hoped could be >> decided at link time, and it has since become something that can only >> really be decided at compile time (which backend to use). With that in >> mind, you could simply define something in vtkRenderingCore's >> configured header stating which backend it was compiled with. >> >> Marcus >> >> On Wed, Dec 9, 2015 at 12:00 PM, Shawn Waldon >> wrote: >> > There *is* a global VTK configuration header. vtkConfigure.h has many >> of >> > these definitions and is included in vtkObjectBase.h (so pretty much >> > everywhere). But you may be right that this should go somewhere in the >> > rendering code rather than in there. I am not sure that >> vtkRenderWindow is >> > the best location for it, but I am not as familiar with the code that >> uses >> > the compiler definition. Does everywhere that #ifdefs VTK_OPENGL2 >> include >> > vtkRenderWindow.h? Or would we have to pull in that header just for >> that >> > macro? >> > >> > Shawn >> > >> > On Wed, Dec 9, 2015 at 11:54 AM, Tim Thirion >> > wrote: >> >> >> >> Yes, that was my original question. :) Is the vtkRenderWindow the best >> >> place for this? I'm happy to add it. >> >> >> >> On Wed, Dec 9, 2015 at 11:12 AM, Joachim Pouderoux >> >> wrote: >> >>> >> >>> BTW, I took a look but I do not see any way for a third party VTK or >> PV >> >>> application that would not use CMake machinery (and use >> VTK_OPENGL_BACKEND) >> >>> to know if the VTK it uses is based on OpenGL backend 1 or 2. >> >>> VTK_OPENGL2 is a compiler definition provided to build VTK or PV but, >> as >> >>> there is no global VTK configuration header, shouldn't we add a >> function in >> >>> vtkRenderWindow to return the version of the backend it is based on? >> >>> >> >>> Joachim Pouderoux >> >>> >> >>> PhD, Technical Expert >> >>> Kitware SAS >> >>> >> >>> >> >>> 2015-12-08 19:58 GMT+01:00 Ben Boeckel : >> >>>> >> >>>> On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote: >> >>>> > I'm looking to provide run-time identification of the current >> OpenGL >> >>>> > backend in use. Some questions: >> >>>> > >> >>>> > 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is >> there a >> >>>> > particular reason we have both? >> >>>> >> >>>> VTK used to have both. VTKGL2 should be migrated to VTK_OPENGL2 (as >> VTK >> >>>> did). >> >>>> >> >>>> > 2. Is there an ideal place to define such a constant? Perhaps on >> the >> >>>> > render >> >>>> > window? >> >>>> >> >>>> The About dialog has a list of information already (versions of >> Python, >> >>>> matplotlib, numpy, Qt, etc.). >> >>>> >> >>>> --Ben >> >>>> _______________________________________________ >> >>>> Powered by www.kitware.com >> >>>> >> >>>> Visit other Kitware open-source projects at >> >>>> http://www.kitware.com/opensource/opensource.html >> >>>> >> >>>> Please keep messages on-topic and check the ParaView Wiki at: >> >>>> http://paraview.org/Wiki/ParaView >> >>>> >> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >> >>>> >> >>>> Follow this link to subscribe/unsubscribe: >> >>>> http://public.kitware.com/mailman/listinfo/paraview >> >>> >> >>> >> >> >> >> >> >> _______________________________________________ >> >> Powered by www.kitware.com >> >> >> >> Visit other Kitware open-source projects at >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> >> http://paraview.org/Wiki/ParaView >> >> >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > > -- > Ken Martin PhD > Chairman & CFO > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > 518 371 3971 > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Thu Dec 10 09:39:53 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 10 Dec 2015 09:39:53 -0500 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: References: <20151208185800.GB23288@megas.khq.kitware.com> Message-ID: <20151210143953.GB15763@megas.khq.kitware.com> On Thu, Dec 10, 2015 at 09:29:27 -0500, Ken Martin wrote: > Maybe vtkRenderingOpenGLConfigure.h ? > > That header is configured from a .in file for both the old and new backend. > We could define VTK_OPENGL2 in that header and applications could include > it as needed. That header appears to get installed. The only issue I see > is that if someone built VTK with no rendering then that header file might > not exist. The library to link to doesn't either for that matter? > Does that work? If so I can put the VTK_OPENGL2 definition in there. It looks like a good location to me. --Ben From marcus.hanwell at kitware.com Thu Dec 10 09:47:48 2015 From: marcus.hanwell at kitware.com (Marcus D. Hanwell) Date: Thu, 10 Dec 2015 09:47:48 -0500 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: References: <20151208185800.GB23288@megas.khq.kitware.com> Message-ID: Yes, and if the header doesn't exist nor does any backend, so that seems reasonable too. On Thu, Dec 10, 2015 at 9:29 AM, Ken Martin wrote: > Maybe vtkRenderingOpenGLConfigure.h ? > > That header is configured from a .in file for both the old and new backend. > We could define VTK_OPENGL2 in that header and applications could include it > as needed. That header appears to get installed. The only issue I see is > that if someone built VTK with no rendering then that header file might not > exist. > > Does that work? If so I can put the VTK_OPENGL2 definition in there. > > > On Wed, Dec 9, 2015 at 12:43 PM, Marcus D. Hanwell > wrote: >> >> vtkConfigure.h is definitely not the right place for this, and we >> worked pretty hard to move things out of it that didn't need to be >> there. It will cause almost all classes to recompile, and nothing in >> common is even aware of rendering backends. There is a configured >> header in the modules that record some settings (such as Cocoa, >> Carbon, X11, etc as far as I remember) that would be more appropriate. >> >> I haven't looked at the code in a while, adding something to configure >> it in seems reasonable. It is something we originally hoped could be >> decided at link time, and it has since become something that can only >> really be decided at compile time (which backend to use). With that in >> mind, you could simply define something in vtkRenderingCore's >> configured header stating which backend it was compiled with. >> >> Marcus >> >> On Wed, Dec 9, 2015 at 12:00 PM, Shawn Waldon >> wrote: >> > There *is* a global VTK configuration header. vtkConfigure.h has many >> > of >> > these definitions and is included in vtkObjectBase.h (so pretty much >> > everywhere). But you may be right that this should go somewhere in the >> > rendering code rather than in there. I am not sure that vtkRenderWindow >> > is >> > the best location for it, but I am not as familiar with the code that >> > uses >> > the compiler definition. Does everywhere that #ifdefs VTK_OPENGL2 >> > include >> > vtkRenderWindow.h? Or would we have to pull in that header just for >> > that >> > macro? >> > >> > Shawn >> > >> > On Wed, Dec 9, 2015 at 11:54 AM, Tim Thirion >> > wrote: >> >> >> >> Yes, that was my original question. :) Is the vtkRenderWindow the best >> >> place for this? I'm happy to add it. >> >> >> >> On Wed, Dec 9, 2015 at 11:12 AM, Joachim Pouderoux >> >> wrote: >> >>> >> >>> BTW, I took a look but I do not see any way for a third party VTK or >> >>> PV >> >>> application that would not use CMake machinery (and use >> >>> VTK_OPENGL_BACKEND) >> >>> to know if the VTK it uses is based on OpenGL backend 1 or 2. >> >>> VTK_OPENGL2 is a compiler definition provided to build VTK or PV but, >> >>> as >> >>> there is no global VTK configuration header, shouldn't we add a >> >>> function in >> >>> vtkRenderWindow to return the version of the backend it is based on? >> >>> >> >>> Joachim Pouderoux >> >>> >> >>> PhD, Technical Expert >> >>> Kitware SAS >> >>> >> >>> >> >>> 2015-12-08 19:58 GMT+01:00 Ben Boeckel : >> >>>> >> >>>> On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote: >> >>>> > I'm looking to provide run-time identification of the current >> >>>> > OpenGL >> >>>> > backend in use. Some questions: >> >>>> > >> >>>> > 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is there >> >>>> > a >> >>>> > particular reason we have both? >> >>>> >> >>>> VTK used to have both. VTKGL2 should be migrated to VTK_OPENGL2 (as >> >>>> VTK >> >>>> did). >> >>>> >> >>>> > 2. Is there an ideal place to define such a constant? Perhaps on >> >>>> > the >> >>>> > render >> >>>> > window? >> >>>> >> >>>> The About dialog has a list of information already (versions of >> >>>> Python, >> >>>> matplotlib, numpy, Qt, etc.). >> >>>> >> >>>> --Ben >> >>>> _______________________________________________ >> >>>> Powered by www.kitware.com >> >>>> >> >>>> Visit other Kitware open-source projects at >> >>>> http://www.kitware.com/opensource/opensource.html >> >>>> >> >>>> Please keep messages on-topic and check the ParaView Wiki at: >> >>>> http://paraview.org/Wiki/ParaView >> >>>> >> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >> >>>> >> >>>> Follow this link to subscribe/unsubscribe: >> >>>> http://public.kitware.com/mailman/listinfo/paraview >> >>> >> >>> >> >> >> >> >> >> _______________________________________________ >> >> Powered by www.kitware.com >> >> >> >> Visit other Kitware open-source projects at >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> Please keep messages on-topic and check the ParaView Wiki at: >> >> http://paraview.org/Wiki/ParaView >> >> >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > Ken Martin PhD > Chairman & CFO > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > 518 371 3971 > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. From aashish.chaudhary at kitware.com Thu Dec 10 09:55:29 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Thu, 10 Dec 2015 09:55:29 -0500 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> Message-ID: Hi Frank, In addition to what Ken said, If you switch to 10.6.5 make sure you have set in your build and runtime. export MESA_GL_VERSION_OVERRIDE=3.2. - Aashish On Thu, Dec 10, 2015 at 9:18 AM, Ken Martin wrote: > Thanks Frank, > > This is an area we are actively working to cleanup right now. Both in > catching it more gracefully and in providing better messages to help people > understand what the next step should be. I believe if you are in an Intel > based system that using their new SWR backend for mesa ( > http://openswr.org/ ) might give the best software rendering performance. > I think it requires a more recent version of Mesa, we suggest Mesa 10.6.5 > or later for VTK. Other people on this list are more familiar with the > specifics of setting up SWR and Mesa on a cluster but I wanted to at least > give you a quick response to let you know we are working on it :-) > > Thanks > Ken > > > > > > On Thu, Dec 10, 2015 at 8:47 AM, Albina, Frank < > frank.albina at sauber-motorsport.com> wrote: > >> Hi all! >> >> >> >> First of all, thanks for all the effort spent on porting the rendering >> engine to support the OpenGL2 backend by default on PV 5.0.0. Early tests >> with the binary from the download page shows a massive improvement over the >> PV 4.1 to 4.3 versions in terms of rendering time. I have repeated the test >> over a few different GPUs and got the same results. >> >> >> >> Which brought me to thinking that similar performance improvements could >> be also achieved when performing software rendering with the MESA >> libraries. I downloaded the PV sources for the 5.0.0-RC1 release yesterday >> and compiled it with MESA and MPI support. MPI version is Intel 5.0.1 and >> MESA version is 10.5.5. The MESA libraries are compiled using: >> >> >> >> ./configure --enable-64-bit --enable-texture-float --enable-osmesa >> --disable-egl --disable-xorg --disable-xvmc --disable-opencl --disable-glx >> --disable-dri --disable-va --disable-shared-glapi --enable-gallium-llvm=no >> --with-gnu-ld --with-osmesa-bits=8 --disable-vdpau >> --enable-dependency-tracking --with-gallium-drivers=?? >> --with-dri-drivers=?? --with-egl-platforms=?? >> >> >> >> Which corresponds to a ?classic? compilation without LLVM support. >> Believe it or not, this was found to run faster on our CPU cluster than >> with the LLVM drivers. >> >> >> >> After linking PV 5.0.0 against the MESA libs with the OpenGL2 backend, I >> started running a simple benchmark to check possible performance benefits >> and here is the error output I got: >> >> >> >> GL_Version: 2.1 Mesa 10.5.5 >> >> Warning: In >> /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, >> line 549 >> >> vtkOSOpenGLRenderWindow (0x3c0eef60): VTK is designed to work with OpenGL >> version 3.2 but it appears it has been given a context that does not >> support 3.2. VTK will run in a compatibility mode designed to work with >> OpenGL 2.1 but some features may not work. >> >> >> >> ERROR: In >> /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, >> line 369 >> >> vtkShaderProgram (0x4d4dbfe0): 1: #version 120 >> >> 2: #extension GL_EXT_gpu_shader4 : require >> >> 3: #define highp >> >> 4: #define mediump >> >> 5: #define lowp >> >> 6: >> >> 7: >> /*========================================================================= >> >> 8: >> >> 9: Program: Visualization Toolkit >> >> 10: Module: vtkPolyDataFS.glsl >> >> 11: >> >> 12: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen >> >> 13: All rights reserved. >> >> 14: See Copyright.txt or http://www.kitware.com/Copyright.htm for >> details. >> >> 15: >> >> 16: This software is distributed WITHOUT ANY WARRANTY; without even >> >> 17: the implied warranty of MERCHANTABILITY or FITNESS FOR A >> PARTICULAR >> >> 18: PURPOSE. See the above copyright notice for more information. >> >> 19: >> >> 20: >> =========================================================================*/ >> >> 21: // Template for the polydata mappers fragment shader >> >> 22: >> >> 23: uniform int PrimitiveIDOffset; >> >> 24: >> >> 25: // VC position of this fragment >> >> 26: varying vec4 vertexVCVSOutput; >> >> 27: >> >> 28: // optional color passed in from the vertex shader, vertexColor >> >> 29: uniform bool OverridesColor; >> >> 30: uniform float opacityUniform; // the fragment opacity >> >> 31: uniform vec3 ambientColorUniform; // intensity weighted color >> >> 32: uniform vec3 diffuseColorUniform; // intensity weighted color >> >> 33: uniform vec3 specularColorUniform; // intensity weighted color >> >> 34: uniform float specularPowerUniform; >> >> 35: >> >> 36: >> >> 37: // optional surface normal declaration >> >> 38: uniform int cameraParallel; >> >> 39: >> >> 40: // extra lighting parameters >> >> 41: uniform int numberOfLights; >> >> 42: uniform vec3 lightColor[6]; >> >> 43: uniform vec3 lightDirectionVC[6]; // normalized >> >> 44: uniform vec3 lightHalfAngleVC[6]; // normalized >> >> 45: >> >> 46: // Texture coordinates >> >> 47: varying vec2 tcoordVCVSOutput; uniform sampler2D texture1; >> >> 48: >> >> 49: // picking support >> >> 50: //VTK::Picking::Dec >> >> 51: >> >> 52: // Depth Peeling Support >> >> 53: //VTK::DepthPeeling::Dec >> >> 54: >> >> 55: // clipping plane vars >> >> 56: //VTK::Clip::Dec >> >> 57: >> >> 58: // the output of this shader >> >> 59: //VTK::Output::Dec >> >> 60: >> >> 61: // Apple Bug >> >> 62: //VTK::PrimID::Dec >> >> 63: >> >> 64: void main() >> >> 65: { >> >> 66: // Apple Bug >> >> 67: //VTK::PrimID::Impl >> >> 68: >> >> 69: //VTK::Clip::Impl >> >> 70: >> >> 71: vec3 ambientColor; >> >> 72: vec3 diffuseColor; >> >> 73: float opacity; >> >> 74: vec3 specularColor; >> >> 75: float specularPower; >> >> 76: ambientColor = ambientColorUniform; >> >> 77: diffuseColor = diffuseColorUniform; >> >> 78: opacity = opacityUniform; >> >> 79: specularColor = specularColorUniform; >> >> 80: specularPower = specularPowerUniform; >> >> 81: vec4 texColor = texture2D(texture1, tcoordVCVSOutput.st); >> >> 82: diffuseColor = texColor.rgb; >> >> 83: opacity = opacity*texColor.a; >> >> 84: if (OverridesColor) { >> >> 85: ambientColor = ambientColorUniform; >> >> 86: diffuseColor = diffuseColorUniform; } >> >> 87: >> >> 88: >> >> 89: // VC position of this fragment >> >> 90: vec4 vertexVC = vertexVCVSOutput; >> >> 91: >> >> 92: // Generate the normal if we are not passed in one >> >> 93: vec3 fdx = >> normalize(vec3(dFdx(vertexVC.x),dFdx(vertexVC.y),dFdx(vertexVC.z))); >> >> 94: vec3 fdy = >> normalize(vec3(dFdy(vertexVC.x),dFdy(vertexVC.y),dFdy(vertexVC.z))); >> >> 95: vec3 normalVCVSOutput = normalize(cross(fdx,fdy)); >> >> 96: if (cameraParallel == 1 && normalVCVSOutput.z < 0.0) { >> normalVCVSOutput = -1.0*normalVCVSOutput; } >> >> 97: if (cameraParallel == 0 && dot(normalVCVSOutput,vertexVC.xyz) > >> 0.0) { normalVCVSOutput = -1.0*normalVCVSOutput; } >> >> 98: >> >> 99: vec3 diffuse = vec3(0,0,0); >> >> 100: vec3 specular = vec3(0,0,0); >> >> 101: for (int lightNum = 0; lightNum < numberOfLights; lightNum++) >> >> 102: { >> >> 103: float df = max(0.0, dot(normalVCVSOutput, >> -lightDirectionVC[lightNum])); >> >> 104: diffuse += ((df) * lightColor[lightNum]); >> >> 105: if (dot(normalVCVSOutput, lightDirectionVC[lightNum]) < 0.0) >> >> 106: { >> >> 107: float sf = pow( max(0.0, >> dot(lightHalfAngleVC[lightNum],normalVCVSOutput)), specularPower); >> >> 108: specular += ((sf) * lightColor[lightNum]); >> >> 109: } >> >> 110: } >> >> 111: diffuse = diffuse * diffuseColor; >> >> 112: specular = specular * specularColor; >> >> 113: gl_FragData[0] = vec4(ambientColor + diffuse + specular, >> opacity); //VTK::Light::Impl >> >> 114: >> >> 115: //VTK::TCoord::Impl >> >> 116: >> >> 117: if (gl_FragData[0].a <= 0.0) >> >> 118: { >> >> 119: discard; >> >> 120: } >> >> 121: >> >> 122: //VTK::DepthPeeling::Impl >> >> 123: >> >> 124: //VTK::Picking::Impl >> >> 125: >> >> 126: } >> >> 127: >> >> >> >> >> >> ERROR: In >> /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, >> line 370 >> >> vtkShaderProgram (0x4d4dbfe0): 0:2(12): error: extension >> `GL_EXT_gpu_shader4' unsupported in fragment shader >> >> >> >> >> >> APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal >> 11) >> >> >> >> Was it to be expected? If so, is there any chance at all to run PV 5.0.0 >> in batch with MESA support on a CPU cluster? If so, which MESA version is >> required/recommended and what are the compile options to pass? >> >> >> Thank you very much in advance for any answer. >> >> >> >> *Frank Albina * >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- > Ken Martin PhD > Chairman & CFO > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > 518 371 3971 > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank.albina at sauber-motorsport.com Thu Dec 10 10:03:02 2015 From: frank.albina at sauber-motorsport.com (Albina, Frank) Date: Thu, 10 Dec 2015 16:03:02 +0100 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> Message-ID: <589CEB614006334D93C1A48C1B1964C9027CEAC01DDA@srvmes03.spe-ch-md9.net> Dear Aashish & Ken! Thank you very much for your swift replies. I had read from the Kitware blog that OpenSWR would bring additional performance but is still in ?alpha? stage, therefore I have been concentrating on ?standard? MESA first. I was missing the bit of information requiring to set the MESA_GL_VERSION_OVERRIDE. I will therefore arrange to compile a newer MESA version and re-compile PV-5.0.0-rc1 and will let you know the outcome. If everything runs smoothly, I should be able to give you feedback on what the results of my test benchmarks are. Cheers, Fran,. From: Aashish Chaudhary [mailto:aashish.chaudhary at kitware.com] Sent: Donnerstag, 10. Dezember 2015 15:55 To: Ken Martin Cc: Albina, Frank; paraview at paraview.org Subject: Re: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 Hi Frank, In addition to what Ken said, If you switch to 10.6.5 make sure you have set in your build and runtime. export MESA_GL_VERSION_OVERRIDE=3.2. - Aashish On Thu, Dec 10, 2015 at 9:18 AM, Ken Martin > wrote: Thanks Frank, This is an area we are actively working to cleanup right now. Both in catching it more gracefully and in providing better messages to help people understand what the next step should be. I believe if you are in an Intel based system that using their new SWR backend for mesa ( http://openswr.org/ ) might give the best software rendering performance. I think it requires a more recent version of Mesa, we suggest Mesa 10.6.5 or later for VTK. Other people on this list are more familiar with the specifics of setting up SWR and Mesa on a cluster but I wanted to at least give you a quick response to let you know we are working on it :-) Thanks Ken On Thu, Dec 10, 2015 at 8:47 AM, Albina, Frank > wrote: Hi all! First of all, thanks for all the effort spent on porting the rendering engine to support the OpenGL2 backend by default on PV 5.0.0. Early tests with the binary from the download page shows a massive improvement over the PV 4.1 to 4.3 versions in terms of rendering time. I have repeated the test over a few different GPUs and got the same results. Which brought me to thinking that similar performance improvements could be also achieved when performing software rendering with the MESA libraries. I downloaded the PV sources for the 5.0.0-RC1 release yesterday and compiled it with MESA and MPI support. MPI version is Intel 5.0.1 and MESA version is 10.5.5. The MESA libraries are compiled using: ./configure --enable-64-bit --enable-texture-float --enable-osmesa --disable-egl --disable-xorg --disable-xvmc --disable-opencl --disable-glx --disable-dri --disable-va --disable-shared-glapi --enable-gallium-llvm=no --with-gnu-ld --with-osmesa-bits=8 --disable-vdpau --enable-dependency-tracking --with-gallium-drivers=?? --with-dri-drivers=?? --with-egl-platforms=?? Which corresponds to a ?classic? compilation without LLVM support. Believe it or not, this was found to run faster on our CPU cluster than with the LLVM drivers. After linking PV 5.0.0 against the MESA libs with the OpenGL2 backend, I started running a simple benchmark to check possible performance benefits and here is the error output I got: GL_Version: 2.1 Mesa 10.5.5 Warning: In /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 549 vtkOSOpenGLRenderWindow (0x3c0eef60): VTK is designed to work with OpenGL version 3.2 but it appears it has been given a context that does not support 3.2. VTK will run in a compatibility mode designed to work with OpenGL 2.1 but some features may not work. ERROR: In /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, line 369 vtkShaderProgram (0x4d4dbfe0): 1: #version 120 2: #extension GL_EXT_gpu_shader4 : require 3: #define highp 4: #define mediump 5: #define lowp 6: 7: /*========================================================================= 8: 9: Program: Visualization Toolkit 10: Module: vtkPolyDataFS.glsl 11: 12: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen 13: All rights reserved. 14: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. 15: 16: This software is distributed WITHOUT ANY WARRANTY; without even 17: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 18: PURPOSE. See the above copyright notice for more information. 19: 20: =========================================================================*/ 21: // Template for the polydata mappers fragment shader 22: 23: uniform int PrimitiveIDOffset; 24: 25: // VC position of this fragment 26: varying vec4 vertexVCVSOutput; 27: 28: // optional color passed in from the vertex shader, vertexColor 29: uniform bool OverridesColor; 30: uniform float opacityUniform; // the fragment opacity 31: uniform vec3 ambientColorUniform; // intensity weighted color 32: uniform vec3 diffuseColorUniform; // intensity weighted color 33: uniform vec3 specularColorUniform; // intensity weighted color 34: uniform float specularPowerUniform; 35: 36: 37: // optional surface normal declaration 38: uniform int cameraParallel; 39: 40: // extra lighting parameters 41: uniform int numberOfLights; 42: uniform vec3 lightColor[6]; 43: uniform vec3 lightDirectionVC[6]; // normalized 44: uniform vec3 lightHalfAngleVC[6]; // normalized 45: 46: // Texture coordinates 47: varying vec2 tcoordVCVSOutput; uniform sampler2D texture1; 48: 49: // picking support 50: //VTK::Picking::Dec 51: 52: // Depth Peeling Support 53: //VTK::DepthPeeling::Dec 54: 55: // clipping plane vars 56: //VTK::Clip::Dec 57: 58: // the output of this shader 59: //VTK::Output::Dec 60: 61: // Apple Bug 62: //VTK::PrimID::Dec 63: 64: void main() 65: { 66: // Apple Bug 67: //VTK::PrimID::Impl 68: 69: //VTK::Clip::Impl 70: 71: vec3 ambientColor; 72: vec3 diffuseColor; 73: float opacity; 74: vec3 specularColor; 75: float specularPower; 76: ambientColor = ambientColorUniform; 77: diffuseColor = diffuseColorUniform; 78: opacity = opacityUniform; 79: specularColor = specularColorUniform; 80: specularPower = specularPowerUniform; 81: vec4 texColor = texture2D(texture1, tcoordVCVSOutput.st); 82: diffuseColor = texColor.rgb; 83: opacity = opacity*texColor.a; 84: if (OverridesColor) { 85: ambientColor = ambientColorUniform; 86: diffuseColor = diffuseColorUniform; } 87: 88: 89: // VC position of this fragment 90: vec4 vertexVC = vertexVCVSOutput; 91: 92: // Generate the normal if we are not passed in one 93: vec3 fdx = normalize(vec3(dFdx(vertexVC.x),dFdx(vertexVC.y),dFdx(vertexVC.z))); 94: vec3 fdy = normalize(vec3(dFdy(vertexVC.x),dFdy(vertexVC.y),dFdy(vertexVC.z))); 95: vec3 normalVCVSOutput = normalize(cross(fdx,fdy)); 96: if (cameraParallel == 1 && normalVCVSOutput.z < 0.0) { normalVCVSOutput = -1.0*normalVCVSOutput; } 97: if (cameraParallel == 0 && dot(normalVCVSOutput,vertexVC.xyz) > 0.0) { normalVCVSOutput = -1.0*normalVCVSOutput; } 98: 99: vec3 diffuse = vec3(0,0,0); 100: vec3 specular = vec3(0,0,0); 101: for (int lightNum = 0; lightNum < numberOfLights; lightNum++) 102: { 103: float df = max(0.0, dot(normalVCVSOutput, -lightDirectionVC[lightNum])); 104: diffuse += ((df) * lightColor[lightNum]); 105: if (dot(normalVCVSOutput, lightDirectionVC[lightNum]) < 0.0) 106: { 107: float sf = pow( max(0.0, dot(lightHalfAngleVC[lightNum],normalVCVSOutput)), specularPower); 108: specular += ((sf) * lightColor[lightNum]); 109: } 110: } 111: diffuse = diffuse * diffuseColor; 112: specular = specular * specularColor; 113: gl_FragData[0] = vec4(ambientColor + diffuse + specular, opacity); //VTK::Light::Impl 114: 115: //VTK::TCoord::Impl 116: 117: if (gl_FragData[0].a <= 0.0) 118: { 119: discard; 120: } 121: 122: //VTK::DepthPeeling::Impl 123: 124: //VTK::Picking::Impl 125: 126: } 127: ERROR: In /panfs/srvpan01/code/repo/build/paraview-5.0.0-rc1/src/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, line 370 vtkShaderProgram (0x4d4dbfe0): 0:2(12): error: extension `GL_EXT_gpu_shader4' unsupported in fragment shader APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11) Was it to be expected? If so, is there any chance at all to run PV 5.0.0 in batch with MESA support on a CPU cluster? If so, which MESA version is required/recommended and what are the compile options to pass? Thank you very much in advance for any answer. Frank Albina _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Dec 10 10:08:14 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 10 Dec 2015 10:08:14 -0500 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: References: <20151208185800.GB23288@megas.khq.kitware.com> Message-ID: And it should appear in a wrapped class so that we can get it at runtime from python. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Dec 10, 2015 at 9:47 AM, Marcus D. Hanwell < marcus.hanwell at kitware.com> wrote: > Yes, and if the header doesn't exist nor does any backend, so that > seems reasonable too. > > On Thu, Dec 10, 2015 at 9:29 AM, Ken Martin > wrote: > > Maybe vtkRenderingOpenGLConfigure.h ? > > > > That header is configured from a .in file for both the old and new > backend. > > We could define VTK_OPENGL2 in that header and applications could > include it > > as needed. That header appears to get installed. The only issue I see is > > that if someone built VTK with no rendering then that header file might > not > > exist. > > > > Does that work? If so I can put the VTK_OPENGL2 definition in there. > > > > > > On Wed, Dec 9, 2015 at 12:43 PM, Marcus D. Hanwell > > wrote: > >> > >> vtkConfigure.h is definitely not the right place for this, and we > >> worked pretty hard to move things out of it that didn't need to be > >> there. It will cause almost all classes to recompile, and nothing in > >> common is even aware of rendering backends. There is a configured > >> header in the modules that record some settings (such as Cocoa, > >> Carbon, X11, etc as far as I remember) that would be more appropriate. > >> > >> I haven't looked at the code in a while, adding something to configure > >> it in seems reasonable. It is something we originally hoped could be > >> decided at link time, and it has since become something that can only > >> really be decided at compile time (which backend to use). With that in > >> mind, you could simply define something in vtkRenderingCore's > >> configured header stating which backend it was compiled with. > >> > >> Marcus > >> > >> On Wed, Dec 9, 2015 at 12:00 PM, Shawn Waldon > > >> wrote: > >> > There *is* a global VTK configuration header. vtkConfigure.h has many > >> > of > >> > these definitions and is included in vtkObjectBase.h (so pretty much > >> > everywhere). But you may be right that this should go somewhere in > the > >> > rendering code rather than in there. I am not sure that > vtkRenderWindow > >> > is > >> > the best location for it, but I am not as familiar with the code that > >> > uses > >> > the compiler definition. Does everywhere that #ifdefs VTK_OPENGL2 > >> > include > >> > vtkRenderWindow.h? Or would we have to pull in that header just for > >> > that > >> > macro? > >> > > >> > Shawn > >> > > >> > On Wed, Dec 9, 2015 at 11:54 AM, Tim Thirion > > >> > wrote: > >> >> > >> >> Yes, that was my original question. :) Is the vtkRenderWindow the > best > >> >> place for this? I'm happy to add it. > >> >> > >> >> On Wed, Dec 9, 2015 at 11:12 AM, Joachim Pouderoux > >> >> wrote: > >> >>> > >> >>> BTW, I took a look but I do not see any way for a third party VTK or > >> >>> PV > >> >>> application that would not use CMake machinery (and use > >> >>> VTK_OPENGL_BACKEND) > >> >>> to know if the VTK it uses is based on OpenGL backend 1 or 2. > >> >>> VTK_OPENGL2 is a compiler definition provided to build VTK or PV > but, > >> >>> as > >> >>> there is no global VTK configuration header, shouldn't we add a > >> >>> function in > >> >>> vtkRenderWindow to return the version of the backend it is based on? > >> >>> > >> >>> Joachim Pouderoux > >> >>> > >> >>> PhD, Technical Expert > >> >>> Kitware SAS > >> >>> > >> >>> > >> >>> 2015-12-08 19:58 GMT+01:00 Ben Boeckel : > >> >>>> > >> >>>> On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote: > >> >>>> > I'm looking to provide run-time identification of the current > >> >>>> > OpenGL > >> >>>> > backend in use. Some questions: > >> >>>> > > >> >>>> > 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is > there > >> >>>> > a > >> >>>> > particular reason we have both? > >> >>>> > >> >>>> VTK used to have both. VTKGL2 should be migrated to VTK_OPENGL2 (as > >> >>>> VTK > >> >>>> did). > >> >>>> > >> >>>> > 2. Is there an ideal place to define such a constant? Perhaps on > >> >>>> > the > >> >>>> > render > >> >>>> > window? > >> >>>> > >> >>>> The About dialog has a list of information already (versions of > >> >>>> Python, > >> >>>> matplotlib, numpy, Qt, etc.). > >> >>>> > >> >>>> --Ben > >> >>>> _______________________________________________ > >> >>>> Powered by www.kitware.com > >> >>>> > >> >>>> Visit other Kitware open-source projects at > >> >>>> http://www.kitware.com/opensource/opensource.html > >> >>>> > >> >>>> Please keep messages on-topic and check the ParaView Wiki at: > >> >>>> http://paraview.org/Wiki/ParaView > >> >>>> > >> >>>> Search the list archives at: > http://markmail.org/search/?q=ParaView > >> >>>> > >> >>>> Follow this link to subscribe/unsubscribe: > >> >>>> http://public.kitware.com/mailman/listinfo/paraview > >> >>> > >> >>> > >> >> > >> >> > >> >> _______________________________________________ > >> >> Powered by www.kitware.com > >> >> > >> >> Visit other Kitware open-source projects at > >> >> http://www.kitware.com/opensource/opensource.html > >> >> > >> >> Please keep messages on-topic and check the ParaView Wiki at: > >> >> http://paraview.org/Wiki/ParaView > >> >> > >> >> Search the list archives at: http://markmail.org/search/?q=ParaView > >> >> > >> >> Follow this link to subscribe/unsubscribe: > >> >> http://public.kitware.com/mailman/listinfo/paraview > >> >> > >> > > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > Search the list archives at: http://markmail.org/search/?q=ParaView > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: > >> http://paraview.org/Wiki/ParaView > >> > >> Search the list archives at: http://markmail.org/search/?q=ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > > > -- > > Ken Martin PhD > > Chairman & CFO > > Kitware Inc. > > 28 Corporate Drive > > Clifton Park NY 12065 > > 518 371 3971 > > > > This communication, including all attachments, contains confidential and > > legally privileged information, and it is intended only for the use of > the > > addressee. Access to this email by anyone else is unauthorized. If you > are > > not the intended recipient, any disclosure, copying, distribution or any > > action taken in reliance on it is prohibited and may be unlawful. If you > > received this communication in error please notify us immediately and > > destroy the original message. Thank you. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Thu Dec 10 10:37:27 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 10 Dec 2015 10:37:27 -0500 Subject: [Paraview] OpenGL Backend Identification In-Reply-To: References: <20151208185800.GB23288@megas.khq.kitware.com> Message-ID: <20151210153727.GA20850@megas.khq.kitware.com> On Thu, Dec 10, 2015 at 10:08:14 -0500, David E DeMarle wrote: > And it should appear in a wrapped class so that we can get it at runtime > from python. In that case, there should probably be an enum in RenderingCore: enum vtkRenderingBackend { ... }; class vtkRenderingSomething { static vtkRenderingBackend getRenderingBackend(); }; --Ben From ben.boeckel at kitware.com Thu Dec 10 11:06:46 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 10 Dec 2015 11:06:46 -0500 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> Message-ID: <20151210160646.GA4939@megas.khq.kitware.com> On Thu, Dec 10, 2015 at 09:18:44 -0500, Ken Martin wrote: > people on this list are more familiar with the specifics of setting up SWR > and Mesa on a cluster but I wanted to at least give you a quick response to > let you know we are working on it :-) The binaries built by our buildbots (and uploaded to the website) have SWR available using prebuilt mesa binaries. If you have AVX CPU extensions available, passing: --mesa-swr-avx should enable it. There's also --mesa-swr-avx2 if you have AVX2 extensions available. --Ben From frank.albina at sauber-motorsport.com Thu Dec 10 11:20:35 2015 From: frank.albina at sauber-motorsport.com (Albina, Frank) Date: Thu, 10 Dec 2015 17:20:35 +0100 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: <20151210160646.GA4939@megas.khq.kitware.com> References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> <20151210160646.GA4939@megas.khq.kitware.com> Message-ID: <589CEB614006334D93C1A48C1B1964C9027CEAC01DE4@srvmes03.spe-ch-md9.net> Dear Ben! Thank you for the reply. My idea was to run PV-5.0.0-RC1 in parallel on our cluster, therefore the need to recompile as the binaries do not usually ship with this feature and I guess that you do not necessarily know either which parallel communication library is going to be used on the end user's compute platform. If the binaries ship with SWR using prebuilt mesa binaries, is there any documentation on how to build the mesa binaries with SWR support? I might eventually figure it out by myself (or not) but I would be grateful for any hints. Cheers, Frank. -----Original Message----- From: Ben Boeckel [mailto:ben.boeckel at kitware.com] Sent: Donnerstag, 10. Dezember 2015 17:07 To: Ken Martin Cc: Albina, Frank; paraview at paraview.org Subject: Re: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 On Thu, Dec 10, 2015 at 09:18:44 -0500, Ken Martin wrote: > people on this list are more familiar with the specifics of setting up > SWR and Mesa on a cluster but I wanted to at least give you a quick > response to let you know we are working on it :-) The binaries built by our buildbots (and uploaded to the website) have SWR available using prebuilt mesa binaries. If you have AVX CPU extensions available, passing: --mesa-swr-avx should enable it. There's also --mesa-swr-avx2 if you have AVX2 extensions available. --Ben From ben.boeckel at kitware.com Thu Dec 10 11:44:43 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 10 Dec 2015 11:44:43 -0500 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: <589CEB614006334D93C1A48C1B1964C9027CEAC01DE4@srvmes03.spe-ch-md9.net> References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> <20151210160646.GA4939@megas.khq.kitware.com> <589CEB614006334D93C1A48C1B1964C9027CEAC01DE4@srvmes03.spe-ch-md9.net> Message-ID: <20151210164443.GA21619@megas.khq.kitware.com> On Thu, Dec 10, 2015 at 17:20:35 +0100, Albina, Frank wrote: > Thank you for the reply. My idea was to run PV-5.0.0-RC1 in parallel on our cluster, > therefore the need to recompile as the binaries do not usually ship with this feature > and I guess that you do not necessarily know either which parallel communication > library is going to be used on the end user's compute platform. > > If the binaries ship with SWR using prebuilt mesa binaries, is there any documentation > on how to build the mesa binaries with SWR support? I might eventually figure it out by > myself (or not) but I would be grateful for any hints. Here's the relevant subset of the Dockerfile Utkarsh used: #---------------------------------------------------------------------------------------------- WORKDIR /opt/tools/src/openswr-mesa RUN git clone https://github.com/OpenSWR/openswr-mesa.git src-avx2 --depth 1 -b 11.0-openswr WORKDIR /opt/tools/src/openswr-mesa/src-avx2 RUN scons build=release texture_float=yes swr_arch=core-avx2 libgl-xlib WORKDIR /opt/tools/mesa-swr-avx2 RUN cp /opt/tools/src/openswr-mesa/src-avx2/build/linux-x86_64/gallium/targets/libgl-xlib/libGL.so.1.5 . && \ ln -s libGL.so.1 libGL.so && \ ln -s libGL.so.1.5 libGL.so.1 #---------------------------------------------------------------------------------------------- WORKDIR /opt/tools/src/openswr-mesa RUN git clone https://github.com/OpenSWR/openswr-mesa.git src-avx --depth 1 -b 11.0-openswr WORKDIR /opt/tools/src/openswr-mesa/src-avx RUN scons build=release texture_float=yes swr_arch=avx libgl-xlib WORKDIR /opt/tools/mesa-swr-avx RUN cp /opt/tools/src/openswr-mesa/src-avx/build/linux-x86_64/gallium/targets/libgl-xlib/libGL.so.1.5 . && \ ln -s libGL.so.1 libGL.so && \ ln -s libGL.so.1.5 libGL.so.1 --Ben From frank.albina at sauber-motorsport.com Thu Dec 10 12:04:57 2015 From: frank.albina at sauber-motorsport.com (Albina, Frank) Date: Thu, 10 Dec 2015 18:04:57 +0100 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: <20151210164443.GA21619@megas.khq.kitware.com> References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> <20151210160646.GA4939@megas.khq.kitware.com> <589CEB614006334D93C1A48C1B1964C9027CEAC01DE4@srvmes03.spe-ch-md9.net> <20151210164443.GA21619@megas.khq.kitware.com> Message-ID: <589CEB614006334D93C1A48C1B1964C9027CEAC01DEB@srvmes03.spe-ch-md9.net> Hi Ben! Thank you very much for the information. I will try to work my way into getting PV 5.0 compiled with OpenSWR-Mesa & MPI. Best regards, ? Frank Albina -----Original Message----- From: Ben Boeckel [mailto:ben.boeckel at kitware.com] Sent: Donnerstag, 10. Dezember 2015 17:45 To: Albina, Frank Cc: Ken Martin; paraview at paraview.org Subject: Re: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 On Thu, Dec 10, 2015 at 17:20:35 +0100, Albina, Frank wrote: > Thank you for the reply. My idea was to run PV-5.0.0-RC1 in parallel > on our cluster, therefore the need to recompile as the binaries do not > usually ship with this feature and I guess that you do not > necessarily know either which parallel communication library is going to be used on the end user's compute platform. > > If the binaries ship with SWR using prebuilt mesa binaries, is there > any documentation on how to build the mesa binaries with SWR support? > I might eventually figure it out by myself (or not) but I would be grateful for any hints. Here's the relevant subset of the Dockerfile Utkarsh used: #---------------------------------------------------------------------------------------------- WORKDIR /opt/tools/src/openswr-mesa RUN git clone https://github.com/OpenSWR/openswr-mesa.git src-avx2 --depth 1 -b 11.0-openswr WORKDIR /opt/tools/src/openswr-mesa/src-avx2 RUN scons build=release texture_float=yes swr_arch=core-avx2 libgl-xlib WORKDIR /opt/tools/mesa-swr-avx2 RUN cp /opt/tools/src/openswr-mesa/src-avx2/build/linux-x86_64/gallium/targets/libgl-xlib/libGL.so.1.5 . && \ ln -s libGL.so.1 libGL.so && \ ln -s libGL.so.1.5 libGL.so.1 #---------------------------------------------------------------------------------------------- WORKDIR /opt/tools/src/openswr-mesa RUN git clone https://github.com/OpenSWR/openswr-mesa.git src-avx --depth 1 -b 11.0-openswr WORKDIR /opt/tools/src/openswr-mesa/src-avx RUN scons build=release texture_float=yes swr_arch=avx libgl-xlib WORKDIR /opt/tools/mesa-swr-avx RUN cp /opt/tools/src/openswr-mesa/src-avx/build/linux-x86_64/gallium/targets/libgl-xlib/libGL.so.1.5 . && \ ln -s libGL.so.1 libGL.so && \ ln -s libGL.so.1.5 libGL.so.1 --Ben From utkarsh.ayachit at kitware.com Thu Dec 10 12:19:27 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 10 Dec 2015 12:19:27 -0500 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> Message-ID: > ./configure --enable-64-bit --enable-texture-float --enable-osmesa > --disable-egl --disable-xorg --disable-xvmc --disable-opencl --disable-glx > --disable-dri --disable-va --disable-shared-glapi --enable-gallium-llvm=no > --with-gnu-ld --with-osmesa-bits=8 --disable-vdpau > --enable-dependency-tracking --with-gallium-drivers=?? --with-dri-drivers=?? > --with-egl-platforms=?? Frank, One thing I noticed is that you're not using LLVM. Using the new rendering backend without LLVM is not recommended at all. It will be painfully slow since the new rendering backend no longer uses fixed pipeline and it has to process GLSL code. You should stick with llvmpipe. I used the following for OSMesa build with Mesa 11.0.4. Hope that helps. You still need the MESA_GL_VERSION_OVERRIDE flag that Aashish mentioned. ./configure --disable-xvmc --disable-glx --disable-dri --with-dri-drivers= --with-gallium-drivers=swrast --enable-texture-float --disable-egl --with-egl-platforms= --enable-gallium-osmesa --enable-gallium-llvm=yes --prefix=/opt/apps/mesa-11.0.4/llvm-osmesa From keinepostnurmuell at gmail.com Fri Dec 11 07:50:03 2015 From: keinepostnurmuell at gmail.com (no name) Date: Fri, 11 Dec 2015 13:50:03 +0100 Subject: [Paraview] A little help with understanding how the pipeline works please Message-ID: Hello I made a long pipeline to work through some of my files and I don't understand what I am missing here, when writing the input for the pipeline to a macro from paraview.simple import * inputfile = FindSource('FILE*') # create a new 'Threshold' threshold1 = Threshold(Input=inputfile) threshold1.Scalars = ['POINTS', 'dataZ'] threshold1.ThresholdRange = [-0.98, 0.98] This produces an empty object in the pipe (Information window, Number of Cells: 0 and so on ...) under Paraview 4.4 on Win10 (x64). I can then just click on the little eye icon to get values under Information. I would not mind clicking that icon, but I need more filters in my pipeline and they alle are empty after this one (or maybe at all, the threshold is my first filter in a row of 25). Thanks Richard From dave.demarle at kitware.com Fri Dec 11 08:08:30 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 11 Dec 2015 08:08:30 -0500 Subject: [Paraview] A little help with understanding how the pipeline works please In-Reply-To: References: Message-ID: The pipeline is lazily evaluated and won't produce anything until you tell it to flow. In the GUI, the "Apply" button typically does this. From python, you can do the same with threshold1.UpdatePipeline(). Call Show() and Render() to update and display the result at the same time like "Apply" does. On Dec 11, 2015 7:50 AM, "no name" wrote: > Hello > > I made a long pipeline to work through some of my files and I don't > understand what I am missing here, when writing the input for the > pipeline to a macro > > from paraview.simple import * > inputfile = FindSource('FILE*') > > # create a new 'Threshold' > threshold1 = Threshold(Input=inputfile) > threshold1.Scalars = ['POINTS', 'dataZ'] > threshold1.ThresholdRange = [-0.98, 0.98] > > This produces an empty object in the pipe (Information window, Number > of Cells: 0 and so on ...) under Paraview 4.4 on Win10 (x64). I can > then just click on the little eye icon to get values under > Information. I would not mind clicking that icon, but I need more > filters in my pipeline and they alle are empty after this one (or > maybe at all, the threshold is my first filter in a row of 25). > > Thanks > Richard > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From keinepostnurmuell at gmail.com Fri Dec 11 08:20:20 2015 From: keinepostnurmuell at gmail.com (no name) Date: Fri, 11 Dec 2015 14:20:20 +0100 Subject: [Paraview] A little help with understanding how the pipeline works please In-Reply-To: References: Message-ID: The Update.Pipeline() thing worked perfectly as you suggested. But now I get an error I cant' read any information form: RROR: In C:\bbd\b51c3c7f\source-paraview\ParaViewCore\ServerManager\Core\vtkSMEnumerationDomain.cxx, line 75 vtkSMFieldDataDomain (00000000610CD930): Invalid idx: 0 But everything seems to look fine ... But I feel very uncomfortable about ignoring it :( The information I read in comes from multiple INP files. Thanks Richard On 11 December 2015 at 14:17, no name wrote: > Hello David > > Thanks for that. I will try it. I have a completely different problem > that comes from a paraview bug (I think), and I want to write it to > the mail list, if it is not mentioned in a bug tracker already, but I > am not sure on how to name it correctly. > > The thing is, I want to export an animation with paraview, and this > animation breaks at some point, resulting for example in a label of a > axis in a spreadsheetview that goes 10 pixels right, while an object > in the renderview disappears completely. I can also not bring it back, > when I walk through the scenes by hand later on. I would like to issue > a bug report, but I am not sure if this bug really is coming from the > export animation or something else. Can you help me with that? > > Thanks > Richard > > On 11 December 2015 at 14:08, David E DeMarle wrote: >> The pipeline is lazily evaluated and won't produce anything until you tell >> it to flow. In the GUI, the "Apply" button typically does this. From >> python, you can do the same with threshold1.UpdatePipeline(). Call Show() >> and Render() to update and display the result at the same time like "Apply" >> does. >> >> On Dec 11, 2015 7:50 AM, "no name" wrote: >>> >>> Hello >>> >>> I made a long pipeline to work through some of my files and I don't >>> understand what I am missing here, when writing the input for the >>> pipeline to a macro >>> >>> from paraview.simple import * >>> inputfile = FindSource('FILE*') >>> >>> # create a new 'Threshold' >>> threshold1 = Threshold(Input=inputfile) >>> threshold1.Scalars = ['POINTS', 'dataZ'] >>> threshold1.ThresholdRange = [-0.98, 0.98] >>> >>> This produces an empty object in the pipe (Information window, Number >>> of Cells: 0 and so on ...) under Paraview 4.4 on Win10 (x64). I can >>> then just click on the little eye icon to get values under >>> Information. I would not mind clicking that icon, but I need more >>> filters in my pipeline and they alle are empty after this one (or >>> maybe at all, the threshold is my first filter in a row of 25). >>> >>> Thanks >>> Richard >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview From keinepostnurmuell at gmail.com Fri Dec 11 08:25:49 2015 From: keinepostnurmuell at gmail.com (no name) Date: Fri, 11 Dec 2015 14:25:49 +0100 Subject: [Paraview] Export animation breaks paraview after some files Message-ID: What I do: Open multiple INP files, run them through a pipeline. Export them as PNG (same error when I do it as a OVG...) via Save Animation. How does it look: Right now I have a renderview on the left side and a spreadsheetview on the right side. Usually after about 30-110 steps the label of the y axis of the spread sheet view goes 10 pixels to the right or so and the renderview object disappears completely. Lets say I exported 10 PNGs and after the 8th its broken. When I then go back in the paraview main window after the animation made the renderview go south and click for example on the 5th input file, I also don't see anything in the render view. Even if I try to load a new INP in that renderview I stell don't see anything. Using paraview 4.4 on Win10 x64 I did not attach images, as I don't know if that comes through the mailing list :( Thanks for your help Richard From cory.quammen at kitware.com Fri Dec 11 09:14:28 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 11 Dec 2015 09:14:28 -0500 Subject: [Paraview] Export animation breaks paraview after some files In-Reply-To: References: Message-ID: Hi Richard, Could you try this with ParaView 5.0 Release Candidate 1 (RC1) and report whether you see the same thing? Thanks, Cory On Fri, Dec 11, 2015 at 8:25 AM, no name wrote: > What I do: > > Open multiple INP files, run them through a pipeline. > Export them as PNG (same error when I do it as a OVG...) via Save > Animation. > > How does it look: > Right now I have a renderview on the left side and a spreadsheetview > on the right side. Usually after about 30-110 steps the label of the y > axis of the spread sheet view goes 10 pixels to the right or so and > the renderview object disappears completely. Lets say I exported 10 > PNGs and after the 8th its broken. > > When I then go back in the paraview main window after the animation > made the renderview go south and click for example on the 5th input > file, I also don't see anything in the render view. Even if I try to > load a new INP in that renderview I stell don't see anything. > > Using paraview 4.4 on Win10 x64 > > I did not attach images, as I don't know if that comes through the > mailing list :( > > Thanks for your help > Richard > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tossin at gmail.com Fri Dec 11 14:16:30 2015 From: tossin at gmail.com (Evan Kao) Date: Fri, 11 Dec 2015 11:16:30 -0800 Subject: [Paraview] Do the GetCellEdgeNeighbors / GetCellNeighbors methods in vtkPolyData not work for polygons? Message-ID: Hi all, I've been playing around with the GetCellEdgeNeighbors and GetCellNeighbors methods in the vtkPolyData class and testing them on a cylinder source in Paraview 4.3.1, which generates a surface made of vtkQuads for the sides and vtkPolygons for caps. I've applied the Clean filter to the cylinder since the caps generate duplicate points. [image: Inline image 1] Within a programmable filter, I've tested the following script: import numpy as np in1 = self.GetPolyDataInput() surface = self.GetOutput() surface.DeepCopy(in1) surface.BuildCells() surface.BuildLinks() cellId = 0 # a vtkQuad cellPtIds = vtk.vtkIdList() surface.GetCellPoints(cellId, cellPtIds) cellPtIds = [cellPtIds.GetId(i) for i in xrange(cellPtIds.GetNumberOfIds())] cellPtIds = np.array(cellPtIds).astype(np.int64) cellEdges = [[id0, id1] for id0, id1 in zip(cellPtIds[:-1], cellPtIds[1:])] cellEdges.append( [cellPtIds[-1], cellPtIds[0]] ) edgeId = 0 # or 1,2,3 edge = cellEdges[edgeId] edgeIdList = vtk.vtkIdList() for i in xrange(2): edgeIdList.InsertNextId(edge[i]) singleCellEdgeNeighborIds = vtk.vtkIdList() #surface.GetCellEdgeNeighbors(cellId, edge[0], edge[1], singleCellEdgeNeighborIds) surface.GetCellNeighbors(cellId, edgeIdList, singleCellEdgeNeighborIds) If the edge neighbor cell is a vtkQuad, the script works. But if the edge neighbor cell corresponds to one of the caps, Paraview will crash. Is there a way to get this to work? Thanks, Evan Kao -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 34858 bytes Desc: not available URL: From tossin at gmail.com Fri Dec 11 14:27:14 2015 From: tossin at gmail.com (Evan Kao) Date: Fri, 11 Dec 2015 11:27:14 -0800 Subject: [Paraview] Do the GetCellEdgeNeighbors / GetCellNeighbors methods in vtkPolyData not work for polygons? In-Reply-To: References: Message-ID: Hey all, It seems the issue might be something else other than the the neighbor cell type. After applying the Triangulate Filter, the GetCellNeighbors method still results in the same behavior: For cell neighbors on the side of the cylinder, the scripts works, but for cell neighbors that make up the cap, Paraview crashes. So now I have no idea what's happening. - Evan On Fri, Dec 11, 2015 at 11:16 AM, Evan Kao wrote: > Hi all, > > I've been playing around with the GetCellEdgeNeighbors and > GetCellNeighbors methods in the vtkPolyData class and testing them on a > cylinder source in Paraview 4.3.1, which generates a surface made of > vtkQuads for the sides and vtkPolygons for caps. I've applied the Clean > filter to the cylinder since the caps generate duplicate points. > > [image: Inline image 1] > > Within a programmable filter, I've tested the following script: > > import numpy as np > > in1 = self.GetPolyDataInput() > surface = self.GetOutput() > surface.DeepCopy(in1) > surface.BuildCells() > surface.BuildLinks() > > cellId = 0 # a vtkQuad > cellPtIds = vtk.vtkIdList() > surface.GetCellPoints(cellId, cellPtIds) > cellPtIds = [cellPtIds.GetId(i) for i in > xrange(cellPtIds.GetNumberOfIds())] > cellPtIds = np.array(cellPtIds).astype(np.int64) > cellEdges = [[id0, id1] for id0, id1 in zip(cellPtIds[:-1], cellPtIds[1:])] > cellEdges.append( [cellPtIds[-1], cellPtIds[0]] ) > > edgeId = 0 # or 1,2,3 > edge = cellEdges[edgeId] > > edgeIdList = vtk.vtkIdList() > for i in xrange(2): > edgeIdList.InsertNextId(edge[i]) > singleCellEdgeNeighborIds = vtk.vtkIdList() > #surface.GetCellEdgeNeighbors(cellId, edge[0], edge[1], > singleCellEdgeNeighborIds) > surface.GetCellNeighbors(cellId, edgeIdList, singleCellEdgeNeighborIds) > > If the edge neighbor cell is a vtkQuad, the script works. But if the edge > neighbor cell corresponds to one of the caps, Paraview will crash. Is > there a way to get this to work? > > Thanks, > Evan Kao > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 34858 bytes Desc: not available URL: From dkxls23 at gmail.com Sat Dec 12 13:11:01 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Sat, 12 Dec 2015 20:11:01 +0200 Subject: [Paraview] rpath error when compiling ParaView 5.0 In-Reply-To: <20151207163835.GA3080@megas.khq.kitware.com> References: <566332BD.2080008@gmail.com> <20151207163835.GA3080@megas.khq.kitware.com> Message-ID: <566C6335.2050609@gmail.com> Thanks for your reply! On 12/07/2015 06:38 PM, Ben Boeckel wrote: > On Sat, Dec 05, 2015 at 20:53:49 +0200, Armin Wehrfritz wrote: >> I'm building ParaView (version 5.0 RC1) for openSUSE Tumbleweed (using >> gcc 5.2.1) and get an error related to rpath (see below). I cannot say >> much more about this, since don't really understand what's going wrong here. >> >> Does anybody have some hints how to solve this? > > Are you giving any rpath-related settings to CMake? What is the > configure line? No, not that I would be aware of. Here my configure line: cmake \ -DCMAKE_BUILD_TYPE=Release \ -DCMAKE_INSTALL_PREFIX:PATH=/opt/paraview/5.0 \ -DCMAKE_CXX_COMPILER:STRING='mpicxx' \ -DCMAKE_C_COMPILER:STRING='mpicc' \ -DBUILD_SHARED_LIBS:BOOL=ON \ -DBUILD_DOCUMENTATION:BOOL=ON \ -DBUILD_EXAMPLES:BOOL=ON \ -DBUILD_TESTING:BOOL=OFF \ -DPARAVIEW_BUILD_QT_GUI:BOOL=ON \ -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=ON \ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON \ -DPARAVIEW_USE_MPI:BOOL=ON \ -DVTK_WRAP_PYTHON:BOOL=ON \ -DVTK_WRAP_PYTHON_SIP:BOOL=ON \ -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF \ -DVTK_USE_SYSTEM_EXPAT:BOOL=ON \ -DVTK_USE_SYSTEM_FREETYPE:BOOL=ON \ -DVTK_USE_SYSTEM_JPEG:BOOL=ON \ -DVTK_USE_SYSTEM_PNG:BOOL=ON \ -DVTK_USE_SYSTEM_TIFF:BOOL=ON \ -DVTK_USE_SYSTEM_ZLIB:BOOL=ON \ -DVTK_USE_SYSTEM_ZOPE:BOOL=ON \ -DVTK_USE_SYSTEM_TWISTED:BOOL=ON \ ../ >> Please let me know if you need more information. > > What version of CMake are you using? I'm using CMake 3.3.2. I can send the CMakeCache.txt file if that helps to track this down. -Armin From f_magician at mac.com Sun Dec 13 09:07:52 2015 From: f_magician at mac.com (Magician) Date: Sun, 13 Dec 2015 23:07:52 +0900 Subject: [Paraview] dataset_adapter with tensors Message-ID: Hi all, I'm trying to add 3x3 tensor data to vtkPolyData with Python. The version of ParaView is 5.0.0 RC1 and 4.4.0. The smallest example is here: > import vtk > import numpy as np > from paraview.vtk.numpy_interface.dataset_adapter import numpyTovtkDataArray as da > from paraview.vtk.numpy_interface.dataset_adapter import vtkDataArrayToVTKArray as va > > m0 = np.array(( > (0, 1, 2, 3, 4, 5, 6, 7, 8), > )) > > d = vtk.vtkPolyData() > d.GetPointData().AddArray(da(m0, 'data')) > > m1 = [] > for i in range(9): > m1.append(d.GetPointData().GetArray('data').GetValue(i)) > print(m1) > > m2 = va(d.GetPointData().GetArray('data')) > print(m2) m1 is good, but m2 is transposed. Is this a bug of vtkDataArrayToVTKArray? Magician From david.larsson at sth.kth.se Mon Dec 14 07:20:28 2015 From: david.larsson at sth.kth.se (David Larsson) Date: Mon, 14 Dec 2015 12:20:28 +0000 Subject: [Paraview] streamfunction Message-ID: <049c8d1a859842db87515dc5df655dc8@exdb01.ug.kth.se> Dear Paraview users, Has anyone ever calculated the so called stream function (grad^2 (stream function) = -vorticity, set up as a Poisson equation) in paraview? I seem to find old posts in the mail list regarding a streamfunction filter, but I might be wrong (since I can't find any in recent versions). Computing vorticity is quite straight forward, but has anyone continued into streamfunction visualization? Or is the only way going through e.g. a programmable filter? Thanks for your help, /David -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Dec 14 10:38:15 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 14 Dec 2015 10:38:15 -0500 Subject: [Paraview] Export animation breaks paraview after some files In-Reply-To: References: Message-ID: Richard, Can you specify what system you are running? Usually the most informative way to see what is going on is to run it through a debugger like gdb and lldb. This should at least get you a stack trace which will help us identify where it is failing. If you are on Windows, there may be a dialog that pops up with some information. You could try running from the command line with the -dr option, e.g. paraview -dr This will disable any options or settings that may be causing problems. If ParaView runs with that option, then the solution is likely to be to clear your settings files. HTH, Cory On Mon, Dec 14, 2015 at 3:41 AM, no name wrote: > Hi Cory > > Thanks for the help, but unfortunately Paraview 5.0 RC1 wont run on my > system at all, it crashes on startup :( Do you know where I can find > some logs, maybe I can get it working? > > Thanks > Richard > > On 11 December 2015 at 15:14, Cory Quammen > wrote: > > Hi Richard, > > > > Could you try this with ParaView 5.0 Release Candidate 1 (RC1) and report > > whether you see the same thing? > > > > Thanks, > > Cory > > > > On Fri, Dec 11, 2015 at 8:25 AM, no name > > wrote: > >> > >> What I do: > >> > >> Open multiple INP files, run them through a pipeline. > >> Export them as PNG (same error when I do it as a OVG...) via Save > >> Animation. > >> > >> How does it look: > >> Right now I have a renderview on the left side and a spreadsheetview > >> on the right side. Usually after about 30-110 steps the label of the y > >> axis of the spread sheet view goes 10 pixels to the right or so and > >> the renderview object disappears completely. Lets say I exported 10 > >> PNGs and after the 8th its broken. > >> > >> When I then go back in the paraview main window after the animation > >> made the renderview go south and click for example on the 5th input > >> file, I also don't see anything in the render view. Even if I try to > >> load a new INP in that renderview I stell don't see anything. > >> > >> Using paraview 4.4 on Win10 x64 > >> > >> I did not attach images, as I don't know if that comes through the > >> mailing list :( > >> > >> Thanks for your help > >> Richard > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: > >> http://paraview.org/Wiki/ParaView > >> > >> Search the list archives at: http://markmail.org/search/?q=ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > > > -- > > Cory Quammen > > R&D Engineer > > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Dec 14 13:27:08 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 14 Dec 2015 13:27:08 -0500 Subject: [Paraview] Can't set custom range value too small In-Reply-To: <56683698.4070500@mail.ru> References: <56683698.4070500@mail.ru> Message-ID: Hi Gena, Thanks for reporting the issue. It has also been reported on the bug tracker [1]. Thanks, Cory [1] http://www.paraview.org/Bug/view.php?id=15875 On Wed, Dec 9, 2015 at 9:11 AM, Gena Bug wrote: > Hi! > > Tried PV rc1 (5.0.0-RC1-20-g58e9aa1 64-bit) and found that I can't set > range value (maximum) if it less than 1e-16 in Color Map Editor (Rescale to > custom range). Yes, it's not a very good value, however, minimum can be set > to less values. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fcueto at gmail.com Mon Dec 14 14:02:48 2015 From: fcueto at gmail.com (Fernando G. del Cueto) Date: Mon, 14 Dec 2015 13:02:48 -0600 Subject: [Paraview] Axes labels Message-ID: Hi all, I'm having the hardest time finding a way of displaying labels in axes in Paraview 4.4. I'm attaching a screenshot of a view where I loaded a bunch of points, and after enabling the "Edit Axes Grid" I see the grid, but no labels. I even tried adding special markers, etc. and nothing. I've spent hours trying to find a way of enabling these (and I've worked with Paraview a year ago, so I know it shouldn't be this hard!) and I'm finally suspecting it may be a bug, drawing problem or conflict with video drivers, because it shouldn't be this hard! I've also tried creating a new source Axes, and again, it shows some box, but no labels at all. Any help or ideas?? Fernando -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: screen3.png Type: image/png Size: 109830 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Mon Dec 14 14:08:24 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 14 Dec 2015 14:08:24 -0500 Subject: [Paraview] Axes labels In-Reply-To: References: Message-ID: That's weird. Try running ParaView with "-dr" command line argument, any difference? Utkarsh On Mon, Dec 14, 2015 at 2:02 PM, Fernando G. del Cueto wrote: > Hi all, > > I'm having the hardest time finding a way of displaying labels in axes in > Paraview 4.4. > > I'm attaching a screenshot of a view where I loaded a bunch of points, and > after enabling the "Edit Axes Grid" I see the grid, but no labels. I even > tried adding special markers, etc. and nothing. I've spent hours trying to > find a way of enabling these (and I've worked with Paraview a year ago, so I > know it shouldn't be this hard!) and I'm finally suspecting it may be a bug, > drawing problem or conflict with video drivers, because it shouldn't be this > hard! > > I've also tried creating a new source Axes, and again, it shows some box, > but no labels at all. > > Any help or ideas?? > > Fernando > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From fcueto at gmail.com Mon Dec 14 14:20:06 2015 From: fcueto at gmail.com (Fernando G. del Cueto) Date: Mon, 14 Dec 2015 13:20:06 -0600 Subject: [Paraview] Axes labels In-Reply-To: References: Message-ID: Hi Utkarsh, No, it didn't seem to make a difference :-( By the way, is there a way of getting the command line options? I tried --help, -h and didn't get anything. Fernando On Mon, Dec 14, 2015 at 1:08 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > That's weird. Try running ParaView with "-dr" command line argument, > any difference? > > Utkarsh > > On Mon, Dec 14, 2015 at 2:02 PM, Fernando G. del Cueto > wrote: > > Hi all, > > > > I'm having the hardest time finding a way of displaying labels in axes in > > Paraview 4.4. > > > > I'm attaching a screenshot of a view where I loaded a bunch of points, > and > > after enabling the "Edit Axes Grid" I see the grid, but no labels. I even > > tried adding special markers, etc. and nothing. I've spent hours trying > to > > find a way of enabling these (and I've worked with Paraview a year ago, > so I > > know it shouldn't be this hard!) and I'm finally suspecting it may be a > bug, > > drawing problem or conflict with video drivers, because it shouldn't be > this > > hard! > > > > I've also tried creating a new source Axes, and again, it shows some box, > > but no labels at all. > > > > Any help or ideas?? > > > > Fernando > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Dec 14 14:28:21 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 14 Dec 2015 14:28:21 -0500 Subject: [Paraview] Axes labels In-Reply-To: References: Message-ID: > By the way, is there a way of getting the command line options? I tried > --help, -h and didn't get anything. -h should do the trick, but on Windows getting output on the terminal is always weird -- someone more familiar than me with Windows can elaborate. So to be clear, if you run paraview as a follows, then create the "Wavelet" source, hit "Apply" and then show the Axes Grid, you still see no labels? > paraview -dr Utkarsh From fcueto at gmail.com Mon Dec 14 14:34:39 2015 From: fcueto at gmail.com (Fernando G. del Cueto) Date: Mon, 14 Dec 2015 13:34:39 -0600 Subject: [Paraview] Axes labels In-Reply-To: References: Message-ID: Hi Utkarsh, In wavelet2.png I show the results of your instructions. In wavelet3.png I went further and went into the "Edit Axes Grid" and enabled "Show grid" As you can see, no labels!! By the way, thanks a lot for trying to help! Fernando On Mon, Dec 14, 2015 at 1:28 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > > By the way, is there a way of getting the command line options? I tried > > --help, -h and didn't get anything. > > -h should do the trick, but on Windows getting output on the terminal > is always weird -- someone more familiar than me with Windows can > elaborate. > > So to be clear, if you run paraview as a follows, then create the > "Wavelet" source, hit "Apply" and then show the Axes Grid, you still > see no labels? > > > paraview -dr > > Utkarsh > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wavelet2.png Type: image/png Size: 75203 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wavelet3.png Type: image/png Size: 77607 bytes Desc: not available URL: From cory.quammen at kitware.com Mon Dec 14 14:36:26 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 14 Dec 2015 14:36:26 -0500 Subject: [Paraview] Axes labels In-Reply-To: References: Message-ID: I can confirm that -h is not recognized on ParaView on Windows (ParaView tries to open a file named '-h'). --h flashes what looks like the Output window in ParaView, but it closes immediately. Cory On Mon, Dec 14, 2015 at 2:28 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > > By the way, is there a way of getting the command line options? I tried > > --help, -h and didn't get anything. > > -h should do the trick, but on Windows getting output on the terminal > is always weird -- someone more familiar than me with Windows can > elaborate. > > So to be clear, if you run paraview as a follows, then create the > "Wavelet" source, hit "Apply" and then show the Axes Grid, you still > see no labels? > > > paraview -dr > > Utkarsh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Dec 14 14:39:04 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 14 Dec 2015 19:39:04 +0000 Subject: [Paraview] [EXTERNAL] Re: Axes labels In-Reply-To: References: Message-ID: <28232748a10c468db1f3b874c65a6c23@ES01AMSNLNT.srn.sandia.gov> Windows help is weird because ParaView is broken (regarding the command line help on Windows). You can see this by running ParaView from a Command Prompt. ParaView creates a new window, writes the output there, then immediately closes the window. I created the command line help on Linux. Here it is: linuxBlade$ ./paraview --help --connect-id=opt Set the ID of the server and client to make sure they match. 0 is reserved to imply none specified. --cslog=opt ClientServerStream log file. --data=opt Load the specified data. To specify file series replace the numeral with a '.' eg. my0.vtk, my1.vtk...myN.vtk becomes my..vtk --data-directory=opt Set the data directory where test-case data are. --disable-registry -dr Do not use registry when running ParaView (for testing). --enable-bt Enable stack trace signal handler. --enable-streaming EXPERIMENTAL: When specified, view-based streaming is enabled for certain views and representation types. --exit Exit application when testing is done. Use for testing. --help /? Displays available command line arguments. --hostname=opt Override the hostname to be used to connect to this process. By default, the hostname is determined using appropriate system calls. --multi-servers Allow client to connect to several pvserver --print-monitors Print detected monitors and exit (Windows only). --script=opt Set a python script to be evaluated on startup. --server=opt -s=opt Set the name of the server resource to connect with when the client starts. --server-url=opt -url=opt Set the server-url to connect with when the client starts. --server (-s) option supersedes this option, hence one should only use one of the two options. --state=opt Load the specified statefile (.pvsm). --stereo Tell the application to enable stereo rendering --stereo-type=opt Specify the stereo type. This valid only when --stereo is specified. Possible values are "Crystal Eyes", "Red-Blue", "Interlaced", "Dresden", "Anaglyph", "Checkerboard","SplitViewportHorizontal" --test-baseline=opt Add test baseline. Can be used multiple times to specify multiple baselines for multiple tests, in order. --test-directory=opt Set the temporary directory where test-case output will be stored. --test-master (For testing) When present, tests master configuration. --test-plugin=opt Specify the name of the plugin to load for testing --test-plugin-path=opt Specify the path where more plugins can be found.This is typically used when testing plugins. --test-script=opt Add test script. Can be used multiple times to specify multiple tests. --test-slave (For testing) When present, tests slave configuration. --test-threshold=opt Add test image threshold. Can be used multiple times to specify multiple image thresholds for multiple tests in order. --tile-image-prefix=opt Set the temporary directory with file name prefix for tile display image dump. --use-cuda-interop -cudaiop When specified, piston classes will use cuda interop for direct rendering --version -V Give the version number and exit. I will write up a bug report. Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit Sent: Monday, December 14, 2015 12:28 PM To: Fernando G. del Cueto Cc: ParaView Subject: [EXTERNAL] Re: [Paraview] Axes labels > By the way, is there a way of getting the command line options? I > tried --help, -h and didn't get anything. -h should do the trick, but on Windows getting output on the terminal is always weird -- someone more familiar than me with Windows can elaborate. So to be clear, if you run paraview as a follows, then create the "Wavelet" source, hit "Apply" and then show the Axes Grid, you still see no labels? > paraview -dr Utkarsh _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From wascott at sandia.gov Mon Dec 14 14:51:31 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 14 Dec 2015 19:51:31 +0000 Subject: [Paraview] [EXTERNAL] Re: Axes labels In-Reply-To: <28232748a10c468db1f3b874c65a6c23@ES01AMSNLNT.srn.sandia.gov> References: <28232748a10c468db1f3b874c65a6c23@ES01AMSNLNT.srn.sandia.gov> Message-ID: <60f67fc6b4f941f18fa71ba75a37559d@ES01AMSNLNT.srn.sandia.gov> http://www.paraview.org/Bug/view.php?id=15880 Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Monday, December 14, 2015 12:39 PM To: Utkarsh Ayachit; Fernando G. del Cueto Cc: ParaView Subject: Re: [Paraview] [EXTERNAL] Re: Axes labels Windows help is weird because ParaView is broken (regarding the command line help on Windows). You can see this by running ParaView from a Command Prompt. ParaView creates a new window, writes the output there, then immediately closes the window. I created the command line help on Linux. Here it is: linuxBlade$ ./paraview --help --connect-id=opt Set the ID of the server and client to make sure they match. 0 is reserved to imply none specified. --cslog=opt ClientServerStream log file. --data=opt Load the specified data. To specify file series replace the numeral with a '.' eg. my0.vtk, my1.vtk...myN.vtk becomes my..vtk --data-directory=opt Set the data directory where test-case data are. --disable-registry -dr Do not use registry when running ParaView (for testing). --enable-bt Enable stack trace signal handler. --enable-streaming EXPERIMENTAL: When specified, view-based streaming is enabled for certain views and representation types. --exit Exit application when testing is done. Use for testing. --help /? Displays available command line arguments. --hostname=opt Override the hostname to be used to connect to this process. By default, the hostname is determined using appropriate system calls. --multi-servers Allow client to connect to several pvserver --print-monitors Print detected monitors and exit (Windows only). --script=opt Set a python script to be evaluated on startup. --server=opt -s=opt Set the name of the server resource to connect with when the client starts. --server-url=opt -url=opt Set the server-url to connect with when the client starts. --server (-s) option supersedes this option, hence one should only use one of the two options. --state=opt Load the specified statefile (.pvsm). --stereo Tell the application to enable stereo rendering --stereo-type=opt Specify the stereo type. This valid only when --stereo is specified. Possible values are "Crystal Eyes", "Red-Blue", "Interlaced", "Dresden", "Anaglyph", "Checkerboard","SplitViewportHorizontal" --test-baseline=opt Add test baseline. Can be used multiple times to specify multiple baselines for multiple tests, in order. --test-directory=opt Set the temporary directory where test-case output will be stored. --test-master (For testing) When present, tests master configuration. --test-plugin=opt Specify the name of the plugin to load for testing --test-plugin-path=opt Specify the path where more plugins can be found.This is typically used when testing plugins. --test-script=opt Add test script. Can be used multiple times to specify multiple tests. --test-slave (For testing) When present, tests slave configuration. --test-threshold=opt Add test image threshold. Can be used multiple times to specify multiple image thresholds for multiple tests in order. --tile-image-prefix=opt Set the temporary directory with file name prefix for tile display image dump. --use-cuda-interop -cudaiop When specified, piston classes will use cuda interop for direct rendering --version -V Give the version number and exit. I will write up a bug report. Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit Sent: Monday, December 14, 2015 12:28 PM To: Fernando G. del Cueto Cc: ParaView Subject: [EXTERNAL] Re: [Paraview] Axes labels > By the way, is there a way of getting the command line options? I > tried --help, -h and didn't get anything. -h should do the trick, but on Windows getting output on the terminal is always weird -- someone more familiar than me with Windows can elaborate. So to be clear, if you run paraview as a follows, then create the "Wavelet" source, hit "Apply" and then show the Axes Grid, you still see no labels? > paraview -dr Utkarsh _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Mon Dec 14 14:52:08 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 14 Dec 2015 14:52:08 -0500 Subject: [Paraview] Axes labels In-Reply-To: References: Message-ID: Mind downloading the 5.0.0-RC1 and see if the labels show up? 5.0 uses a different OpenGL context. Let's see if that circumvents this issue. 5.0 also show OpenGL information in the About dialog. So it will be useful to post that information too. I am leaning towards this being some driver issue esp. since I have not encountered this issue before. Utkarsh On Mon, Dec 14, 2015 at 2:34 PM, Fernando G. del Cueto wrote: > Hi Utkarsh, > > In wavelet2.png I show the results of your instructions. > > In wavelet3.png I went further and went into the "Edit Axes Grid" and > enabled "Show grid" > > As you can see, no labels!! By the way, thanks a lot for trying to help! > > Fernando > > > > > On Mon, Dec 14, 2015 at 1:28 PM, Utkarsh Ayachit > wrote: >> >> > By the way, is there a way of getting the command line options? I tried >> > --help, -h and didn't get anything. >> >> -h should do the trick, but on Windows getting output on the terminal >> is always weird -- someone more familiar than me with Windows can >> elaborate. >> >> So to be clear, if you run paraview as a follows, then create the >> "Wavelet" source, hit "Apply" and then show the Axes Grid, you still >> see no labels? >> >> > paraview -dr >> >> Utkarsh > > From fcueto at gmail.com Mon Dec 14 14:58:44 2015 From: fcueto at gmail.com (Fernando G. del Cueto) Date: Mon, 14 Dec 2015 13:58:44 -0600 Subject: [Paraview] Axes labels In-Reply-To: References: Message-ID: Actually, that was my first attempt. I downloaded the last 5.x version last week but it crashes when I run it, right after showing the splash screen (both with 32bit and 64bit versions). That's why I defaulted back to 4.4 :-/ Fernando On Mon, Dec 14, 2015 at 1:52 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Mind downloading the 5.0.0-RC1 and see if the labels show up? 5.0 uses > a different OpenGL context. Let's see if that circumvents this issue. > 5.0 also show OpenGL information in the About dialog. So it will be > useful to post that information too. I am leaning towards this being > some driver issue esp. since I have not encountered this issue before. > > Utkarsh > > On Mon, Dec 14, 2015 at 2:34 PM, Fernando G. del Cueto > wrote: > > Hi Utkarsh, > > > > In wavelet2.png I show the results of your instructions. > > > > In wavelet3.png I went further and went into the "Edit Axes Grid" and > > enabled "Show grid" > > > > As you can see, no labels!! By the way, thanks a lot for trying to help! > > > > Fernando > > > > > > > > > > On Mon, Dec 14, 2015 at 1:28 PM, Utkarsh Ayachit > > wrote: > >> > >> > By the way, is there a way of getting the command line options? I > tried > >> > --help, -h and didn't get anything. > >> > >> -h should do the trick, but on Windows getting output on the terminal > >> is always weird -- someone more familiar than me with Windows can > >> elaborate. > >> > >> So to be clear, if you run paraview as a follows, then create the > >> "Wavelet" source, hit "Apply" and then show the Axes Grid, you still > >> see no labels? > >> > >> > paraview -dr > >> > >> Utkarsh > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Dec 14 17:05:21 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 14 Dec 2015 17:05:21 -0500 Subject: [Paraview] Axes labels In-Reply-To: References: Message-ID: Ah in that case I do think you're OpenGL drivers are quite old and they may indeed be having issues rendering the labels. The 5.0.0-RC2 binaries will be available this week. This build will show a dialog box with information about the OpenGL drivers before it fails. Let's see what that shows and we can know for sure if the drivers are too old. Utkarsh On Mon, Dec 14, 2015 at 2:58 PM, Fernando G. del Cueto wrote: > Actually, that was my first attempt. I downloaded the last 5.x version last > week but it crashes when I run it, right after showing the splash screen > (both with 32bit and 64bit versions). That's why I defaulted back to 4.4 > :-/ > > Fernando > > > On Mon, Dec 14, 2015 at 1:52 PM, Utkarsh Ayachit > wrote: >> >> Mind downloading the 5.0.0-RC1 and see if the labels show up? 5.0 uses >> a different OpenGL context. Let's see if that circumvents this issue. >> 5.0 also show OpenGL information in the About dialog. So it will be >> useful to post that information too. I am leaning towards this being >> some driver issue esp. since I have not encountered this issue before. >> >> Utkarsh >> >> On Mon, Dec 14, 2015 at 2:34 PM, Fernando G. del Cueto >> wrote: >> > Hi Utkarsh, >> > >> > In wavelet2.png I show the results of your instructions. >> > >> > In wavelet3.png I went further and went into the "Edit Axes Grid" and >> > enabled "Show grid" >> > >> > As you can see, no labels!! By the way, thanks a lot for trying to >> > help! >> > >> > Fernando >> > >> > >> > >> > >> > On Mon, Dec 14, 2015 at 1:28 PM, Utkarsh Ayachit >> > wrote: >> >> >> >> > By the way, is there a way of getting the command line options? I >> >> > tried >> >> > --help, -h and didn't get anything. >> >> >> >> -h should do the trick, but on Windows getting output on the terminal >> >> is always weird -- someone more familiar than me with Windows can >> >> elaborate. >> >> >> >> So to be clear, if you run paraview as a follows, then create the >> >> "Wavelet" source, hit "Apply" and then show the Axes Grid, you still >> >> see no labels? >> >> >> >> > paraview -dr >> >> >> >> Utkarsh >> > >> > > > From mexas at bris.ac.uk Tue Dec 15 06:20:14 2015 From: mexas at bris.ac.uk (Anton Shterenlikht) Date: Tue, 15 Dec 2015 03:20:14 -0800 (PST) Subject: [Paraview] reading input directly from memory? Message-ID: <201512151120.tBFBKDdB011862@mech-as222.men.bris.ac.uk> Is there a facility in paraview to read input data directly from memory? I'm thinking of a situation where some program is run on N cores. Before it exits, while its data is still in memory, Paraview is started on the same N cores and reads data created by the first program from memory. Then the program exits. I guess something like this can be written from scratch, but I wonder if there is any existing facility in paraview to facilitate this. Thanks Anton From dkxls23 at gmail.com Tue Dec 15 06:48:46 2015 From: dkxls23 at gmail.com (dkxls23 at gmail.com) Date: Tue, 15 Dec 2015 11:48:46 +0000 Subject: [Paraview] reading input directly from memory? In-Reply-To: <201512151120.tBFBKDdB011862@mech-as222.men.bris.ac.uk> References: <201512151120.tBFBKDdB011862@mech-as222.men.bris.ac.uk> Message-ID: I guess what you are aiming at is "in situ analysis": http://www.paraview.org/in-situ/ ParaView's Catalyst framework should give you a good starting point. -Armin On Tue Dec 15 13:20:14 2015 GMT+0200, Anton Shterenlikht wrote: > Is there a facility in paraview to read input > data directly from memory? I'm thinking of a situation > where some program is run on N cores. Before it exits, > while its data is still in memory, Paraview is started on > the same N cores and reads data created by the first program > from memory. Then the program exits. > > I guess something like this can be written from > scratch, but I wonder if there is any existing > facility in paraview to facilitate this. > > Thanks > > Anton > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Sent from my Jolla From mexas at bris.ac.uk Tue Dec 15 06:58:05 2015 From: mexas at bris.ac.uk (Anton Shterenlikht) Date: Tue, 15 Dec 2015 03:58:05 -0800 (PST) Subject: [Paraview] reading input directly from memory? In-Reply-To: Message-ID: <201512151158.tBFBw45U011995@mech-as222.men.bris.ac.uk> >From dkxls23 at gmail.com Tue Dec 15 11:54:43 2015 > >I guess what you are aiming at is "in situ analysis": >http://www.paraview.org/in-situ/ > >ParaView's Catalyst framework should give you a good starting point. > >-Armin At first glance, yes, this is what I'm after. I'll read the manuals, but briefly, is this just paraview functionality via library calls? Anton From utkarsh.ayachit at kitware.com Tue Dec 15 09:37:53 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 15 Dec 2015 09:37:53 -0500 Subject: [Paraview] ANN: ParaView 5.0.0-RC2 now available for download Message-ID: Folks, ParaView 5.0.0-RC2 is now available for download[1]. Checkout the release notes on the Kitware blog [2]. As always, we look forward to your feedback [3]. Also stay tuned to the Kitware Blog [4] for upcoming features and enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much more! - The ParaView team [1] http://www.paraview.org/download/ [2] http://kitware.com/blog/home/post/998 [3] http://paraview.uservoice.com [4] http://www.kitware.com/blog/ From keinepostnurmuell at gmail.com Tue Dec 15 09:39:14 2015 From: keinepostnurmuell at gmail.com (no name) Date: Tue, 15 Dec 2015 15:39:14 +0100 Subject: [Paraview] Some Filter with a programmable Filter combined Message-ID: Hello, I want to import the output of an already applied Filter in my paraview programmable filter. I load an INP file, use GradientOfUnstructuredDataSet1 on it with output name "grad". Now I want to apply a Programmable Filter on that GradientOfUnstructuredDataSet1 and get it's values. I can access them in the console by: print grad.PointData.GetArray('dataX').GetRange() print grad.PointData.GetArray('dataY').GetRange() print grad.PointData.GetArray('dataZ').GetRange() But in the Programmable filter I failed. I tried to fetch the data with something similar to: data = input(0,1) and so, but failed. How do I adress this data best? I can get it Working in the console, but not in the filter itself :( Thanks Richard From utkarsh.ayachit at kitware.com Tue Dec 15 09:46:50 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 15 Dec 2015 09:46:50 -0500 Subject: [Paraview] Some Filter with a programmable Filter combined In-Reply-To: References: Message-ID: I believe you're looking for: data =inputs[0] and not "input(0, 1)". I'd also recommend reading the Chapter 13 from the ParaView Guide (http://www.paraview.org/paraview-guide/). It covers this in detail. Utkarsh On Tue, Dec 15, 2015 at 9:39 AM, no name wrote: > Hello, I want to import the output of an already applied Filter in my > paraview programmable filter. > > I load an INP file, use GradientOfUnstructuredDataSet1 on it with > output name "grad". > > Now I want to apply a Programmable Filter on that > GradientOfUnstructuredDataSet1 and get it's values. > > I can access them in the console by: > > print grad.PointData.GetArray('dataX').GetRange() > print grad.PointData.GetArray('dataY').GetRange() > print grad.PointData.GetArray('dataZ').GetRange() > > But in the Programmable filter I failed. I tried to fetch the data > with something similar to: > > data = input(0,1) and so, but failed. > > How do I adress this data best? I can get it Working in the console, > but not in the filter itself :( > > Thanks > Richard > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Tue Dec 15 11:27:26 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 15 Dec 2015 11:27:26 -0500 Subject: [Paraview] ParaView Environment Variables In-Reply-To: References: <5620138A.9060407@indiana.edu> Message-ID: This page [1] is now accessible from here [2]. [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/EnvironmentVariables.html [2] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/index.html On Thu, Dec 10, 2015 at 3:51 AM, Joachim Pouderoux wrote: > This is a good idea and for information Utkarsh started to write this > documentation in > Utilities/Doxygen/pages/EnvironmentVariables.md > > For now it is just in a merge request (and it is not complete) but no doubt > if will be in master very soon! > > https://gitlab.kitware.com/paraview/paraview/merge_requests/511 > > Joachim > > Joachim Pouderoux > > PhD, Technical Expert > Kitware SAS > > > 2015-10-19 19:31 GMT+02:00 Cory Quammen : >> >> Hi Bill, >> >> This is a good project. Perhaps we can include a version of your man page >> in the user's guide when it is finished? >> >> I know about some of these environment variables: >> >> - PARAVIEW_DATA_ROOT - used to point ParaView to a testing data >> repository. This is really only used when ParaView's tests are run and >> likely isn't useful to users. >> >> - PV_NO_OFFSCREEN_SCREENSHOTS - just what it sounds like. If set, >> offscreen rendering will not be used for generating screenshots, even if the >> ParaView settings say that offscreen rendering should be used for generating >> screenshots. >> >> - VTK_AUTOLOAD_PATH - users shouldn't need to set this. From the >> vtkObjectFactory documentation: "The first time CreateInstance is called, >> all dll's or shared libraries in the environment variable VTK_AUTOLOAD_PATH >> are loaded into the current process." >> >> - VTK_RENDERER - this looks like a historical way to choose which render >> window to instantiate. It doesn't look like it is used anymore. >> >> - PV_DEBUG_LEAKS_VIEW - enables a window that shows the number of >> instances of all VTK classes. Useful for debugging, not really useful for >> users. >> >> -PV_DEBUG_TEST - I don't see this in the ParaView source anywhere >> >> - PV_SETTINGS_DEBUG - turns on debugging message related to loading >> ParaView's settings files, e.g., where it looked for the settings file. >> >> - PV_PLUGIN_DEBUG - print debugging output having to do with where >> ParaView looks for plugins. >> >> - PV_PLUGIN_PATH - adds search path for plugins >> >> - VTK_MATPLOTLIB_DEBUG - Enable verbose debugging output during >> initialization of matplotlib. >> >> Hope that helps, >> Cory >> >> On Thu, Oct 15, 2015 at 4:58 PM, Bill Sherman >> wrote: >>> >>> Hello all, >>> >>> Perhaps an odd question -- I'm wondering what important environment >>> variables are associated with ParaView, and in some cases what they >>> do. >>> >>> I ask because for an installation of ParaView on an HPC system, I >>> am creating a traditional man-page. And one of the traditional >>> sections of man pages for applications is "ENVIRONMENT VARIABLES". >>> >>> I happened to find that NERSC had previously done a similar thing, >>> but based on the command line arguments as well as the environment >>> variables it gives no longer in existence, it would seem that this >>> is from a rather old version of ParaView, so I'm basically starting >>> from scratch. >>> >>> Searching through the source for "getenv", I found several refernces >>> to environment variables, and I'd like to get advice on what should/ >>> should not be included. >>> >>> So there are a couple of categories the environment variables can >>> be classified as. >>> >>> 1) ParaView specific variables: >>> - PV_ICET_WINDOW_BORDERS >>> - PARAVIEW_DATA_ROOT >>> - PV_NO_OFFSCREEN_SCREENSHOTS >>> >>> So I know what the first of those does, and I had an assumption of >>> what the second one (PARAVIEW_DATA_ROOT) does -- but I couldn't find >>> a way to make it have an effect! And I can half-guess what the third >>> one does -- explanations welcome. >>> >>> >>> 2) VTK related variables: >>> - VTK_AUTOLOAD_PATH >>> - VTK_RENDERER >>> >>> And I don't really know what either of them do. >>> >>> >>> 3) Generic environment variables that ParaView accesses: >>> - DISPLAY >>> - HOME >>> - HOSTNAME >>> - LOGNAME >>> - PATH >>> - LD_LIBRARY_PATH >>> - PWD (VTK/Utilities/KWSys/vtksys/SystemTools.cxx) >>> - PYTHONPATH >>> - TCL_LIBRARY (vtkTclUtil.cxx) >>> - TK_LIBRARY (vtkTclUtil.cxx) >>> - R_HOME (vtkRInterface.cxx) >>> - COLUMNS (VTK/Utilities/KWSys/vtksys/SystemTools.cxx) >>> - APPDATA -- for MS-Windows only? >>> - COMMON_APPDATA -- for MS-Windows only? >>> >>> So I don't know that I'd need to include those as part of a ParaView >>> man-page. >>> >>> >>> 4) Other variables that are probably just for internal testing: >>> - PV_DEBUG_LEAKS_VIEW >>> - PV_DEBUG_TEST >>> - PV_SETTINGS_DEBUG >>> - PV_PLUGIN_DEBUG >>> - PV_PLUGIN_PATH >>> - DASHBOARD_TEST_FROM_CTEST >>> - DART_TEST_FROM_DART >>> - VERBOSE_TESTING (Exodus) >>> - VERY_VERBOSE_TESTING (Exodus) >>> - FLIP_CAM_MANIP (Interactor Style Unicam) >>> - VTK_MATPLOTLIB_DEBUG (vtkMatplotlibMathTextUtilities.cxx) >>> - QT_MAC_NO_NATIVE_MENUBAR >>> (ThirdParty/QtTesting/vtkqttesting/pqTestUtility.cxx) >>> >>> Again, probably wouldn't include these in a man-page, unless they are >>> something the end-user could possibly want to affect. >>> >>> >>> Happy to share the man-page when I'm done. >>> >>> Thanks, >>> Bill >>> >>> -- >>> Bill Sherman >>> Sr. Technology Advisor >>> Advanced Visualization Lab >>> Pervasive Technology Inst >>> Indiana University >>> shermanw at indiana.edu >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > From archaerolog at mail.ru Tue Dec 15 13:52:32 2015 From: archaerolog at mail.ru (Gena Bug) Date: Tue, 15 Dec 2015 21:52:32 +0300 Subject: [Paraview] ANN: ParaView 5.0.0-RC2 now available for download In-Reply-To: References: Message-ID: <56706170.8060608@mail.ru> Hi! New release always warn me about using PointGaussian representation for cell data: Warning: In /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ClientServerCore/Rendering/vtkPointGaussianRepresentation.cxx, line 269 vtkPointGaussianRepresentation (0x1e70b190): Using cell data in PointGaussian representation Because all our data are stored in cells (pvd->pvtu->vtu) it's a little bit annoying to see this all the time. On 15.12.2015 17:37, Utkarsh Ayachit wrote: > Folks, > > ParaView 5.0.0-RC2 is now available for download[1]. Checkout the release > notes on the Kitware blog [2]. > > As always, we look forward to your feedback [3]. > > Also stay tuned to the Kitware Blog [4] for upcoming features and > enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much > more! > > - The ParaView team > > [1] http://www.paraview.org/download/ > [2] http://kitware.com/blog/home/post/998 > [3] http://paraview.uservoice.com > [4] http://www.kitware.com/blog/ > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From scott.wittenburg at kitware.com Tue Dec 15 15:47:19 2015 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Tue, 15 Dec 2015 13:47:19 -0700 Subject: [Paraview] ANN: ParaView 5.0.0-RC2 now available for download In-Reply-To: <56706170.8060608@mail.ru> References: <56706170.8060608@mail.ru> Message-ID: Thanks for pointing this out. We're looking into a fix now and should hopefully have something out soon. Cheers, Scott On Tue, Dec 15, 2015 at 11:52 AM, Gena Bug wrote: > Hi! > > New release always warn me about using PointGaussian representation for > cell data: > > Warning: In > /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ClientServerCore/Rendering/vtkPointGaussianRepresentation.cxx, > line 269 > vtkPointGaussianRepresentation (0x1e70b190): Using cell data in > PointGaussian representation > > Because all our data are stored in cells (pvd->pvtu->vtu) it's a little > bit annoying to see this all the time. > > > On 15.12.2015 17:37, Utkarsh Ayachit wrote: > >> Folks, >> >> ParaView 5.0.0-RC2 is now available for download[1]. Checkout the release >> notes on the Kitware blog [2]. >> >> As always, we look forward to your feedback [3]. >> >> Also stay tuned to the Kitware Blog [4] for upcoming features and >> enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much >> more! >> >> - The ParaView team >> >> [1] http://www.paraview.org/download/ >> [2] http://kitware.com/blog/home/post/998 >> [3] http://paraview.uservoice.com >> [4] http://www.kitware.com/blog/ >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Dec 15 16:57:51 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 15 Dec 2015 21:57:51 +0000 Subject: [Paraview] [EXTERNAL] Re: ANN: ParaView 5.0.0-RC2 now available for download In-Reply-To: References: <56706170.8060608@mail.ru> Message-ID: Scott/Utkarsh, I just replicated this, and posted a bug. We really need it fixed for 5.0 ? it shows up all the time with something as simple as Whipple Shield! http://www.paraview.org/Bug/view.php?id=15881 Thanks for reporting. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott Wittenburg Sent: Tuesday, December 15, 2015 1:47 PM To: Gena Bug Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] ANN: ParaView 5.0.0-RC2 now available for download Thanks for pointing this out. We're looking into a fix now and should hopefully have something out soon. Cheers, Scott On Tue, Dec 15, 2015 at 11:52 AM, Gena Bug > wrote: Hi! New release always warn me about using PointGaussian representation for cell data: Warning: In /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ClientServerCore/Rendering/vtkPointGaussianRepresentation.cxx, line 269 vtkPointGaussianRepresentation (0x1e70b190): Using cell data in PointGaussian representation Because all our data are stored in cells (pvd->pvtu->vtu) it's a little bit annoying to see this all the time. On 15.12.2015 17:37, Utkarsh Ayachit wrote: Folks, ParaView 5.0.0-RC2 is now available for download[1]. Checkout the release notes on the Kitware blog [2]. As always, we look forward to your feedback [3]. Also stay tuned to the Kitware Blog [4] for upcoming features and enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much more! - The ParaView team [1] http://www.paraview.org/download/ [2] http://kitware.com/blog/home/post/998 [3] http://paraview.uservoice.com [4] http://www.kitware.com/blog/ _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From viktor.sip at centrum.cz Tue Dec 15 16:54:36 2015 From: viktor.sip at centrum.cz (Viktor Sip) Date: Tue, 15 Dec 2015 22:54:36 +0100 Subject: [Paraview] Filter cell type from PolyData VTK file Message-ID: <56708C1C.6040408@centrum.cz> Dear all, is there a way to filter and show only a specific cell type? In my application I am exporting a PolyData VTK file containing some Polys and Lines. When imported into Paraview, both Polys and Lines are shown, and I did not find a simple way to show only Polys. What I can do is to export additional CellData array with a number specifying cell type and then apply Treshold in Paraview. However that seems redundant, as the type is already stored in the file somewhere. So my question is, is there a direct way? Simplified example of the exported VTK file is attached. Kind regards, Viktor -------------- next part -------------- 1 0 0 0 1 0 1 1 0 0 1 2 3 0 1 1 2 0 2 2 4 6 From utkarsh.ayachit at kitware.com Tue Dec 15 17:17:53 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 15 Dec 2015 17:17:53 -0500 Subject: [Paraview] Filter cell type from PolyData VTK file In-Reply-To: <56708C1C.6040408@centrum.cz> References: <56708C1C.6040408@centrum.cz> Message-ID: Nothing that I am aware of. You could potentially write a filter that coverts the cell type to an cell data attribute and then you could threshold by that -- but that's not much different than what you're already doing. Utkarsh On Tue, Dec 15, 2015 at 4:54 PM, Viktor Sip wrote: > Dear all, > > is there a way to filter and show only a specific cell type? > > In my application I am exporting a PolyData VTK file containing some Polys > and Lines. When imported into Paraview, both Polys and Lines are shown, and > I did not find a simple way to show only Polys. > What I can do is to export additional CellData array with a number > specifying cell type and then apply Treshold in Paraview. However that seems > redundant, as the type is already stored in the file somewhere. > So my question is, is there a direct way? > > Simplified example of the exported VTK file is attached. > > Kind regards, > Viktor > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From david.larsson at sth.kth.se Tue Dec 15 17:22:53 2015 From: david.larsson at sth.kth.se (David Larsson) Date: Tue, 15 Dec 2015 22:22:53 +0000 Subject: [Paraview] Access point/cell data as Python variable Message-ID: <1450218173628.82915@sth.kth.se> Dear all, I am working with imported temporal velocity fields (from pvd/vtu) files. Does anyone know how I in pvpython can access point or cell data as a specified variable (array)? I easily find out how to load data into paraview using the Python tracer ('solutoinpvd = PVDReader(FielName='myfile.pvd')) but can't seem to know how to access the velocity field in pvpython after that. I want the point or cell data loaded in specified variables in order to modify e.g. the velocity or calculated vorticity field through scripting (as an example, set all values >0 to a given value), but I can't seem to find these variables (or set variables to them). Thanks for the help. /David -------------- next part -------------- An HTML attachment was scrubbed... URL: From samuelkey at bresnan.net Tue Dec 15 17:47:00 2015 From: samuelkey at bresnan.net (Samuel Key) Date: Tue, 15 Dec 2015 15:47:00 -0700 Subject: [Paraview] Filter cell type from PolyData VTK file In-Reply-To: <56708C1C.6040408@centrum.cz> References: <56708C1C.6040408@centrum.cz> Message-ID: <56709864.8070605@bresnan.net> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test-frame.pvd Type: text/xml Size: 403 bytes Desc: not available URL: From viktor.sip at centrum.cz Wed Dec 16 02:56:39 2015 From: viktor.sip at centrum.cz (=?utf-8?q?Viktor_Sip?=) Date: Wed, 16 Dec 2015 08:56:39 +0100 Subject: [Paraview] =?utf-8?q?Filter_cell_type_from_PolyData_VTK_file?= In-Reply-To: <56709864.8070605@bresnan.net> References: <56708C1C.6040408@centrum.cz> <56709864.8070605@bresnan.net> Message-ID: <20151216085639.F838CBD2@centrum.cz> Thanks for the helpful tips. First approach has the disadvantage that I need to specify the underlying points in each of the separate files, which leads again to some redundancy. But good to know. EnSight format looks promising though, I didn't know about it before. Thanks again, Viktor ______________________________________________________________ > Od: Samuel Key > Komu: > Datum: 15.12.2015 23:47 > P?edm?t: Re: [Paraview] Filter cell type from PolyData VTK file > >Victor, > > > >Off the top of my head, I can think of three different ways to do this: > > > >(1) Put each cell-type in a separate *.vtp file. You can then load each cell-type separately or you can load them with a *.pvd meta-file (sample attached) as "one object" and use the Extract Block filter to display any number and combination of cell-types. > > > >(2) You can use the EnSight format for your results. This format has a Part-construct that allows mixed-cell objects and that can be used to organize your cells any way you like, for example, by cell-type, by material, by sub-assemblies, ... Again, the Extract Block filter can be used to display any number and combination of 'Parts.' > > > >(3) When you write the *.vtp file assign each cell its vtk-cell-type number as data, and then use the Threshold filter applied to the cell's cell-type value. > > > >There are probably other ways as well. > > > >Hope this helps. > > > >Sam Key > > > > > > > > > >On 12/15/2015 2:54 PM, Viktor Sip wrote: > > > >Dear all, > > > >is there a way to filter and show only a specific cell type? > > > >In my application I am exporting a PolyData VTK file containing some Polys and Lines. When imported into Paraview, both Polys and Lines are shown, and I did not find a simple way to show only Polys. > >What I can do is to export additional CellData array with a number specifying cell type and then apply Treshold in Paraview. However that seems redundant, as the type is already stored in the file somewhere. > >So my question is, is there a direct way? > > > >Simplified example of the exported VTK file is attached. > > > >Kind regards, > >Viktor > > > > > > > >_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview > > > > >---------- > >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > >Search the list archives at: http://markmail.org/search/?q=ParaView > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview > From axkibe at gmail.com Wed Dec 16 06:01:27 2015 From: axkibe at gmail.com (Axel Kittenberger) Date: Wed, 16 Dec 2015 12:01:27 +0100 Subject: [Paraview] Volume Rendering with NumberOfScalarComponents > 1 Message-ID: Hello, the Python VTK script below gives results, like a expect. Now I'm trying to reproduce it in Paraview and I fail. I get rather confused as soon I give it a source with more than one scalar component. Paraview creates one color map; I would expect 3 color maps, 1 for every component. What ever I do effective opacity is always 1. That is I see a black cube with it's surface the images of the data on its surface (so far correct), however no effective volume rendering -- I selected Volume, "Ray Cast Only" which should be vtkFixedPointVolumeRayCastMapper as far I understood. I tried creating 3 readers with the different scalar components extracted first, but doesn't give correct rendering -- neither in VTK nor in paraview, since multiple renderer seem to compete which gets to draw a pixel instead of composing them together like a red transparent + a green transparent should give a yellow transparent impression. How can I achieve the same result with Paraview? Kind regards, Axel -------------------------- #!/usr/bin/env python import vtk # Create the standard renderer, render window and interactor ren = vtk.vtkRenderer( ) renWin = vtk.vtkRenderWindow( ) renWin.AddRenderer( ren ) iren = vtk.vtkRenderWindowInteractor( ) iren.SetRenderWindow( renWin ) reader = vtk.vtkImageReader2( ) reader.SetFileName( "./data.raw" ); reader.SetDataScalarTypeToUnsignedChar( ); reader.SetNumberOfScalarComponents( 3 ); reader.SetFileDimensionality( 3 ); reader.SetDataExtent( 0, 261, 0, 511, 0, 21 ); reader.SetDataSpacing( 1, 1, 3.5 ); # Create transfer mapping scalar value to opacity opacityTransferFunction = vtk.vtkPiecewiseFunction( ) opacityTransferFunction.AddPoint( 0, 0.0 ) opacityTransferFunction.AddPoint( 20, 0.0 ) opacityTransferFunction.AddPoint( 40, 0.1 ) opacityTransferFunction.AddPoint( 255, 0.1 ) # Create transfer mapping scalar value to color colorRedTransferFunction = vtk.vtkColorTransferFunction( ) colorRedTransferFunction.AddRGBPoint( 0.0, 0.2, 0.0, 0.0 ) colorRedTransferFunction.AddRGBPoint( 255.0, 1.0, 0.0, 0.0 ) colorGreenTransferFunction = vtk.vtkColorTransferFunction( ) colorGreenTransferFunction.AddRGBPoint( 0.0, 0.0, 0.2, 0.0 ) colorGreenTransferFunction.AddRGBPoint( 255.0, 0.0, 1.0, 0.0 ) colorBlueTransferFunction = vtk.vtkColorTransferFunction( ) colorBlueTransferFunction.AddRGBPoint( 0.0, 0.0, 0.0, 0.0 ) colorBlueTransferFunction.AddRGBPoint( 255.0, 0.0, 0.0, 1.0 ) volumeProperty = vtk.vtkVolumeProperty( ) volumeProperty.SetColor( 0, colorRedTransferFunction ) volumeProperty.SetColor( 1, colorGreenTransferFunction ) volumeProperty.SetColor( 2, colorBlueTransferFunction ) volumeProperty.SetScalarOpacity( 0, opacityTransferFunction ) volumeProperty.SetScalarOpacity( 1, opacityTransferFunction ) volumeProperty.SetScalarOpacity( 2, opacityTransferFunction ) volumeProperty.SetInterpolationTypeToLinear( ) volumeMapper = vtk.vtkFixedPointVolumeRayCastMapper( ) volumeMapper.SetInputConnection( reader.GetOutputPort( ) ) volumeMapper.SetNumberOfThreads( 1 ) volume = vtk.vtkVolume( ) volume.SetMapper( volumeMapper ) volume.SetProperty( volumeProperty ) ren.AddVolume( volume ) ren.SetBackground( 1, 1, 1 ) renWin.SetSize( 600, 600 ) def CheckAbort( obj, event ): if obj.GetEventPending( ) != 0: obj.SetAbortRender( 1 ) renWin.AddObserver( "AbortCheckEvent", CheckAbort ) iren.Initialize( ) renWin.Render( ) iren.Start( ) -------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Dec 16 10:18:55 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 16 Dec 2015 09:18:55 -0600 Subject: [Paraview] Volume Rendering with NumberOfScalarComponents > 1 In-Reply-To: References: Message-ID: <908959F8-C53F-46A3-97B1-BE827D2DB8BC@kitware.com> Axel We were just discussing this few days ago. Do you have to use paraview gui? Or paraview python will work? There might be a way in pv python route. Thanks Sent from my iPhone > On Dec 16, 2015, at 5:01 AM, Axel Kittenberger wrote: > > Hello, > > the Python VTK script below gives results, like a expect. Now I'm trying to reproduce it in Paraview and I fail. > > I get rather confused as soon I give it a source with more than one scalar component. > Paraview creates one color map; I would expect 3 color maps, 1 for every component. > What ever I do effective opacity is always 1. That is I see a black cube with it's surface the images > of the data on its surface (so far correct), however no effective volume rendering -- I selected Volume, "Ray Cast Only" > which should be vtkFixedPointVolumeRayCastMapper as far I understood. > > I tried creating 3 readers with the different scalar components extracted first, but doesn't give > correct rendering -- neither in VTK nor in paraview, since multiple renderer seem to compete which gets to > draw a pixel instead of composing them together > like a red transparent + a green transparent should give a yellow transparent impression. > > How can I achieve the same result with Paraview? > > Kind regards, Axel > > -------------------------- > #!/usr/bin/env python > > import vtk > > # Create the standard renderer, render window and interactor > ren = vtk.vtkRenderer( ) > renWin = vtk.vtkRenderWindow( ) > renWin.AddRenderer( ren ) > iren = vtk.vtkRenderWindowInteractor( ) > iren.SetRenderWindow( renWin ) > > reader = vtk.vtkImageReader2( ) > reader.SetFileName( "./data.raw" ); > reader.SetDataScalarTypeToUnsignedChar( ); > reader.SetNumberOfScalarComponents( 3 ); > reader.SetFileDimensionality( 3 ); > reader.SetDataExtent( 0, 261, 0, 511, 0, 21 ); > reader.SetDataSpacing( 1, 1, 3.5 ); > > # Create transfer mapping scalar value to opacity > opacityTransferFunction = vtk.vtkPiecewiseFunction( ) > opacityTransferFunction.AddPoint( 0, 0.0 ) > opacityTransferFunction.AddPoint( 20, 0.0 ) > opacityTransferFunction.AddPoint( 40, 0.1 ) > opacityTransferFunction.AddPoint( 255, 0.1 ) > > # Create transfer mapping scalar value to color > > colorRedTransferFunction = vtk.vtkColorTransferFunction( ) > colorRedTransferFunction.AddRGBPoint( 0.0, 0.2, 0.0, 0.0 ) > colorRedTransferFunction.AddRGBPoint( 255.0, 1.0, 0.0, 0.0 ) > > colorGreenTransferFunction = vtk.vtkColorTransferFunction( ) > colorGreenTransferFunction.AddRGBPoint( 0.0, 0.0, 0.2, 0.0 ) > colorGreenTransferFunction.AddRGBPoint( 255.0, 0.0, 1.0, 0.0 ) > > colorBlueTransferFunction = vtk.vtkColorTransferFunction( ) > colorBlueTransferFunction.AddRGBPoint( 0.0, 0.0, 0.0, 0.0 ) > colorBlueTransferFunction.AddRGBPoint( 255.0, 0.0, 0.0, 1.0 ) > > volumeProperty = vtk.vtkVolumeProperty( ) > volumeProperty.SetColor( 0, colorRedTransferFunction ) > volumeProperty.SetColor( 1, colorGreenTransferFunction ) > volumeProperty.SetColor( 2, colorBlueTransferFunction ) > > volumeProperty.SetScalarOpacity( 0, opacityTransferFunction ) > volumeProperty.SetScalarOpacity( 1, opacityTransferFunction ) > volumeProperty.SetScalarOpacity( 2, opacityTransferFunction ) > volumeProperty.SetInterpolationTypeToLinear( ) > > volumeMapper = vtk.vtkFixedPointVolumeRayCastMapper( ) > volumeMapper.SetInputConnection( reader.GetOutputPort( ) ) > volumeMapper.SetNumberOfThreads( 1 ) > > volume = vtk.vtkVolume( ) > volume.SetMapper( volumeMapper ) > volume.SetProperty( volumeProperty ) > > ren.AddVolume( volume ) > ren.SetBackground( 1, 1, 1 ) > renWin.SetSize( 600, 600 ) > > def CheckAbort( obj, event ): > if obj.GetEventPending( ) != 0: > obj.SetAbortRender( 1 ) > > renWin.AddObserver( "AbortCheckEvent", CheckAbort ) > > iren.Initialize( ) > renWin.Render( ) > iren.Start( ) > -------------------------- > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From lyon at fnal.gov Wed Dec 16 11:39:37 2015 From: lyon at fnal.gov (Adam Lyon) Date: Wed, 16 Dec 2015 10:39:37 -0600 Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of ParaView In-Reply-To: References: <3b80307dd0184a7081060df719e33861@MAIL06V-CAS04.fnal.gov> <39f822d31fde44f480e4a52108b21e0d@MAIL06V-CAS04.fnal.gov> <198e09ec4d914afab6645f4e9b37e5bf@MAIL03V-CAS01.fnal.gov> <9661715ca38f44ddacde89a22785e882@MAIL04V-CAS03.fnal.gov> <5BBB77AF-80DE-44B6-A78B-744C4AE89866@kitware.com> Message-ID: Hi Ken and Utkarsh, Checking back in with this issue... I still find that interaction with the g-2 ring in ParaView v5rc2 is very slow compared to v4.4. It looks like you all have a solution in mind. I'm happy to build from master to try it if the solution is there. Thanks again and Happy Holidays!!! I really appreciate you all looking at this problem. -- Adam *------* *Adam L. Lyon* *Scientist; Associate Division Head for Systems for Scientific Applications* Scientific Computing Division & Muon g-2 Experiment Fermi National Accelerator Laboratory 630 840 5522 office www.fnal.gov lyon at fnal.gov Connect with us! Newsletter | Facebook | Twitter On Fri, Nov 20, 2015 at 1:48 PM, Ken Martin wrote: > You could maybe have an actor per LOD and then swap actors in and out. > > Actor owns the property, backface property, and texture. Changes to those > objects can cause VBO/IBO rebuilds (switching from surface to wireframe, > adding a texture map, flat versus phong shading, edge visibility, line > width, etc.) The old backend only looked at the actor's property which is > sort of broken. > > For example in the old backend: create two properties, one set to > wireframe, one set to surface. Then create an actor and mapper set to use > display lists. Switching between the two properties will cause an actor > mtime change, but the properties themselves would still have low mtimes I > believe. In that case the old backend will end up stuck in one > representation because it only looks at the property mtime not actor. > > To make the VBO/IBO rebuild safely (but less often than currently) I think > the solution is to check the mtimes as is done currently, if those are > modified then collect up the parameters that require a VBO or IBO rebuild > and compare them to a stored value from the last build. If different force > a rebuild. That is the best solution IMO just takes some time. I sort of > wanted to do that anyhow but now I can say you forced me into it :-) > > Thanks > Ken > > > > > On Fri, Nov 20, 2015 at 1:57 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> > I did notice PV is forcing the actor to be modified every time the LOD >> > changes (which is a lot). Modifying the actor causes the VBO/IBOs to >> rebuild >> > so it would be better not to do that unless you really need to and in >> this >> > case I'm not sure why it is being done. Specifically I think it is in >> > vtkPVLODActor::Modified where it calls this->Device->Modified() . The >> LOD >> > actor is being modified as a result of calling SetEnableLOD constantly >> > flipping between true and false. That is not the cause of this issue >> but it >> > is something I noticed that will be a pain for large datasets. >> >> Ken, currently, there's no way around it. vtkPVLODActor works by >> changing the mapper on the internal vtkActor aka Device when LOD mode >> is toggled. That will indeed change the Device's MTime even if we stop >> calling this->Device->Modiied() in the vtkPVLODActor::Modified(). The >> question is why are VBO/IBOs rebuild if actor MTime changes? VBOs >> would be data dependent right? Most of data-dependent properties are >> on the Mapper, not the actor. Shouldn't the code that re-creates >> VBO/IBOs only depend on Mapper's MTime? >> >> Utkarsh >> > > > > -- > Ken Martin PhD > Chairman & CFO > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > 518 371 3971 > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Wed Dec 16 12:47:38 2015 From: ken.martin at kitware.com (Ken Martin) Date: Wed, 16 Dec 2015 12:47:38 -0500 Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of ParaView In-Reply-To: References: <3b80307dd0184a7081060df719e33861@MAIL06V-CAS04.fnal.gov> <39f822d31fde44f480e4a52108b21e0d@MAIL06V-CAS04.fnal.gov> <198e09ec4d914afab6645f4e9b37e5bf@MAIL03V-CAS01.fnal.gov> <9661715ca38f44ddacde89a22785e882@MAIL04V-CAS03.fnal.gov> <5BBB77AF-80DE-44B6-A78B-744C4AE89866@kitware.com> Message-ID: I don't really have a solution planned for that case. The data size is trivially small but it falls into the slow path because each block of data may or may not have normals or colors or tcoords. The nature of the blocks is heterogeneous. So you end up with 4000 mappers each rendering 10 triangles. Currently there are two paths for rendering multiblock data. 1) every block has the same properties (normals, tcoords, triangles) In that case we use a fast path, the actual values of course may be different, but if one block has texture coordinates then all of them will. 2) blocks can be different, meaning that one block may be triangles with normals while the next could be lines with texture coordinates. In that case we fall back on just giving each block its own mapper. That is the slow path. What would benefit your case is a third path (or a better slow path) where the blocks can be different, but we combine the ones that are the same so that hopefully we end up with maybe 4 or 5 mappers each with 1000 or so triangles. Implementing that is not trivial though so I don't think anyone has plans for it yet. Another approach would be to look at what is generating your data and try to determine why some blocks have normals while others do not. because if you can get the blocks to be homogeneous then you will get the fast path. Thanks Ken On Wed, Dec 16, 2015 at 11:39 AM, Adam Lyon wrote: > Hi Ken and Utkarsh, Checking back in with this issue... I still find that > interaction with the g-2 ring in ParaView v5rc2 is very slow compared to > v4.4. It looks like you all have a solution in mind. I'm happy to build > from master to try it if the solution is there. Thanks again and Happy > Holidays!!! I really appreciate you all looking at this problem. -- Adam > > *------* > > *Adam L. Lyon* > *Scientist; Associate Division Head for Systems for Scientific > Applications* > > Scientific Computing Division & Muon g-2 Experiment > Fermi National Accelerator Laboratory > 630 840 5522 office > www.fnal.gov > lyon at fnal.gov > > Connect with us! > Newsletter | Facebook > | Twitter > > > On Fri, Nov 20, 2015 at 1:48 PM, Ken Martin > wrote: > >> You could maybe have an actor per LOD and then swap actors in and out. >> >> Actor owns the property, backface property, and texture. Changes to those >> objects can cause VBO/IBO rebuilds (switching from surface to wireframe, >> adding a texture map, flat versus phong shading, edge visibility, line >> width, etc.) The old backend only looked at the actor's property which is >> sort of broken. >> >> For example in the old backend: create two properties, one set to >> wireframe, one set to surface. Then create an actor and mapper set to use >> display lists. Switching between the two properties will cause an actor >> mtime change, but the properties themselves would still have low mtimes I >> believe. In that case the old backend will end up stuck in one >> representation because it only looks at the property mtime not actor. >> >> To make the VBO/IBO rebuild safely (but less often than currently) I >> think the solution is to check the mtimes as is done currently, if those >> are modified then collect up the parameters that require a VBO or IBO >> rebuild and compare them to a stored value from the last build. If >> different force a rebuild. That is the best solution IMO just takes some >> time. I sort of wanted to do that anyhow but now I can say you forced me >> into it :-) >> >> Thanks >> Ken >> >> >> >> >> On Fri, Nov 20, 2015 at 1:57 PM, Utkarsh Ayachit < >> utkarsh.ayachit at kitware.com> wrote: >> >>> > I did notice PV is forcing the actor to be modified every time the LOD >>> > changes (which is a lot). Modifying the actor causes the VBO/IBOs to >>> rebuild >>> > so it would be better not to do that unless you really need to and in >>> this >>> > case I'm not sure why it is being done. Specifically I think it is in >>> > vtkPVLODActor::Modified where it calls this->Device->Modified() . The >>> LOD >>> > actor is being modified as a result of calling SetEnableLOD constantly >>> > flipping between true and false. That is not the cause of this issue >>> but it >>> > is something I noticed that will be a pain for large datasets. >>> >>> Ken, currently, there's no way around it. vtkPVLODActor works by >>> changing the mapper on the internal vtkActor aka Device when LOD mode >>> is toggled. That will indeed change the Device's MTime even if we stop >>> calling this->Device->Modiied() in the vtkPVLODActor::Modified(). The >>> question is why are VBO/IBOs rebuild if actor MTime changes? VBOs >>> would be data dependent right? Most of data-dependent properties are >>> on the Mapper, not the actor. Shouldn't the code that re-creates >>> VBO/IBOs only depend on Mapper's MTime? >>> >>> Utkarsh >>> >> >> >> >> -- >> Ken Martin PhD >> Chairman & CFO >> Kitware Inc. >> 28 Corporate Drive >> Clifton Park NY 12065 >> 518 371 3971 >> >> This communication, including all attachments, contains confidential and >> legally privileged information, and it is intended only for the use of the >> addressee. Access to this email by anyone else is unauthorized. If you are >> not the intended recipient, any disclosure, copying, distribution or any >> action taken in reliance on it is prohibited and may be unlawful. If you >> received this communication in error please notify us immediately and >> destroy the original message. Thank you. >> > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lyon at fnal.gov Wed Dec 16 14:22:09 2015 From: lyon at fnal.gov (Adam Lyon) Date: Wed, 16 Dec 2015 13:22:09 -0600 Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of ParaView In-Reply-To: References: <3b80307dd0184a7081060df719e33861@MAIL06V-CAS04.fnal.gov> <39f822d31fde44f480e4a52108b21e0d@MAIL06V-CAS04.fnal.gov> <198e09ec4d914afab6645f4e9b37e5bf@MAIL03V-CAS01.fnal.gov> <9661715ca38f44ddacde89a22785e882@MAIL04V-CAS03.fnal.gov> <5BBB77AF-80DE-44B6-A78B-744C4AE89866@kitware.com> Message-ID: Hi Ken - thanks for your reply. It's looking like the last approach - I figure out why I'm getting different blocks - is the way to go. It's already clear that not all of the blocks have colors. Some of the blocks are created by vtk sources (e.g. VtkConeSource) and others are created by hand (me setting points and cells). The latter won't have normals. Maybe some of the former do. I'll look into this. I'm curious as to why I didn't have any of these problems in v4.4 -- or is this two path multiblock rendering code all new for v5? Thanks again!! -- Adam *------* *Adam L. Lyon* *Scientist; Associate Division Head for Systems for Scientific Applications* Scientific Computing Division & Muon g-2 Experiment Fermi National Accelerator Laboratory 630 840 5522 office www.fnal.gov lyon at fnal.gov Connect with us! Newsletter | Facebook | Twitter On Wed, Dec 16, 2015 at 11:47 AM, Ken Martin wrote: > I don't really have a solution planned for that case. The data size is > trivially small but it falls into the slow path because each block of data > may or may not have normals or colors or tcoords. The nature of the blocks > is heterogeneous. So you end up with 4000 mappers each rendering 10 > triangles. Currently there are two paths for rendering multiblock data. > > 1) every block has the same properties (normals, tcoords, triangles) In > that case we use a fast path, the actual values of course may be different, > but if one block has texture coordinates then all of them will. > > 2) blocks can be different, meaning that one block may be triangles with > normals while the next could be lines with texture coordinates. In that > case we fall back on just giving each block its own mapper. That is the > slow path. > > What would benefit your case is a third path (or a better slow path) where > the blocks can be different, but we combine the ones that are the same so > that hopefully we end up with maybe 4 or 5 mappers each with 1000 or so > triangles. Implementing that is not trivial though so I don't think anyone > has plans for it yet. > > Another approach would be to look at what is generating your data and try > to determine why some blocks have normals while others do not. because if > you can get the blocks to be homogeneous then you will get the fast path. > > Thanks > Ken > > > > > > > > On Wed, Dec 16, 2015 at 11:39 AM, Adam Lyon wrote: > >> Hi Ken and Utkarsh, Checking back in with this issue... I still find that >> interaction with the g-2 ring in ParaView v5rc2 is very slow compared to >> v4.4. It looks like you all have a solution in mind. I'm happy to build >> from master to try it if the solution is there. Thanks again and Happy >> Holidays!!! I really appreciate you all looking at this problem. -- Adam >> >> *------* >> >> *Adam L. Lyon* >> *Scientist; Associate Division Head for Systems for Scientific >> Applications* >> >> Scientific Computing Division & Muon g-2 Experiment >> Fermi National Accelerator Laboratory >> 630 840 5522 office >> www.fnal.gov >> lyon at fnal.gov >> >> Connect with us! >> Newsletter | Facebook >> | Twitter >> >> >> On Fri, Nov 20, 2015 at 1:48 PM, Ken Martin >> wrote: >> >>> You could maybe have an actor per LOD and then swap actors in and out. >>> >>> Actor owns the property, backface property, and texture. Changes to >>> those objects can cause VBO/IBO rebuilds (switching from surface to >>> wireframe, adding a texture map, flat versus phong shading, edge >>> visibility, line width, etc.) The old backend only looked at the actor's >>> property which is sort of broken. >>> >>> For example in the old backend: create two properties, one set to >>> wireframe, one set to surface. Then create an actor and mapper set to use >>> display lists. Switching between the two properties will cause an actor >>> mtime change, but the properties themselves would still have low mtimes I >>> believe. In that case the old backend will end up stuck in one >>> representation because it only looks at the property mtime not actor. >>> >>> To make the VBO/IBO rebuild safely (but less often than currently) I >>> think the solution is to check the mtimes as is done currently, if those >>> are modified then collect up the parameters that require a VBO or IBO >>> rebuild and compare them to a stored value from the last build. If >>> different force a rebuild. That is the best solution IMO just takes some >>> time. I sort of wanted to do that anyhow but now I can say you forced me >>> into it :-) >>> >>> Thanks >>> Ken >>> >>> >>> >>> >>> On Fri, Nov 20, 2015 at 1:57 PM, Utkarsh Ayachit < >>> utkarsh.ayachit at kitware.com> wrote: >>> >>>> > I did notice PV is forcing the actor to be modified every time the LOD >>>> > changes (which is a lot). Modifying the actor causes the VBO/IBOs to >>>> rebuild >>>> > so it would be better not to do that unless you really need to and in >>>> this >>>> > case I'm not sure why it is being done. Specifically I think it is in >>>> > vtkPVLODActor::Modified where it calls this->Device->Modified() . The >>>> LOD >>>> > actor is being modified as a result of calling SetEnableLOD constantly >>>> > flipping between true and false. That is not the cause of this issue >>>> but it >>>> > is something I noticed that will be a pain for large datasets. >>>> >>>> Ken, currently, there's no way around it. vtkPVLODActor works by >>>> changing the mapper on the internal vtkActor aka Device when LOD mode >>>> is toggled. That will indeed change the Device's MTime even if we stop >>>> calling this->Device->Modiied() in the vtkPVLODActor::Modified(). The >>>> question is why are VBO/IBOs rebuild if actor MTime changes? VBOs >>>> would be data dependent right? Most of data-dependent properties are >>>> on the Mapper, not the actor. Shouldn't the code that re-creates >>>> VBO/IBOs only depend on Mapper's MTime? >>>> >>>> Utkarsh >>>> >>> >>> >>> >>> -- >>> Ken Martin PhD >>> Chairman & CFO >>> Kitware Inc. >>> 28 Corporate Drive >>> Clifton Park NY 12065 >>> 518 371 3971 >>> >>> This communication, including all attachments, contains confidential and >>> legally privileged information, and it is intended only for the use of the >>> addressee. Access to this email by anyone else is unauthorized. If you are >>> not the intended recipient, any disclosure, copying, distribution or any >>> action taken in reliance on it is prohibited and may be unlawful. If you >>> received this communication in error please notify us immediately and >>> destroy the original message. Thank you. >>> >> >> > > > -- > Ken Martin PhD > Chairman & CFO > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > 518 371 3971 > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Wed Dec 16 14:46:10 2015 From: ken.martin at kitware.com (Ken Martin) Date: Wed, 16 Dec 2015 14:46:10 -0500 Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of ParaView In-Reply-To: References: <3b80307dd0184a7081060df719e33861@MAIL06V-CAS04.fnal.gov> <39f822d31fde44f480e4a52108b21e0d@MAIL06V-CAS04.fnal.gov> <198e09ec4d914afab6645f4e9b37e5bf@MAIL03V-CAS01.fnal.gov> <9661715ca38f44ddacde89a22785e882@MAIL04V-CAS03.fnal.gov> <5BBB77AF-80DE-44B6-A78B-744C4AE89866@kitware.com> Message-ID: This code is all new hence the change. On the plus side if you moved from 4000 blocks of 10 triangles each to 4000 blocks of 10000 triangles each the rendering performance would probably not slow down. The overhead is all in starting and stopping each of those 4000 mappers. The old backend wrote everything out into a displaylist and the OpenGL driver handled optimizing it and dealing with any inconsistencies. The new backend has to build vertex buffer objects and we currently only collapse all the blocks together into one VBO if the VBO structure is the same for every block. Thanks Ken On Wed, Dec 16, 2015 at 2:22 PM, Adam Lyon wrote: > Hi Ken - thanks for your reply. It's looking like the last approach - I > figure out why I'm getting different blocks - is the way to go. It's > already clear that not all of the blocks have colors. Some of the blocks > are created by vtk sources (e.g. VtkConeSource) and others are created by > hand (me setting points and cells). The latter won't have normals. Maybe > some of the former do. I'll look into this. > > I'm curious as to why I didn't have any of these problems in v4.4 -- or is > this two path multiblock rendering code all new for v5? Thanks again!! -- > Adam > > *------* > > *Adam L. Lyon* > *Scientist; Associate Division Head for Systems for Scientific > Applications* > > Scientific Computing Division & Muon g-2 Experiment > Fermi National Accelerator Laboratory > 630 840 5522 office > www.fnal.gov > lyon at fnal.gov > > Connect with us! > Newsletter | Facebook > | Twitter > > > On Wed, Dec 16, 2015 at 11:47 AM, Ken Martin > wrote: > >> I don't really have a solution planned for that case. The data size is >> trivially small but it falls into the slow path because each block of data >> may or may not have normals or colors or tcoords. The nature of the blocks >> is heterogeneous. So you end up with 4000 mappers each rendering 10 >> triangles. Currently there are two paths for rendering multiblock data. >> >> 1) every block has the same properties (normals, tcoords, triangles) In >> that case we use a fast path, the actual values of course may be different, >> but if one block has texture coordinates then all of them will. >> >> 2) blocks can be different, meaning that one block may be triangles with >> normals while the next could be lines with texture coordinates. In that >> case we fall back on just giving each block its own mapper. That is the >> slow path. >> >> What would benefit your case is a third path (or a better slow path) >> where the blocks can be different, but we combine the ones that are the >> same so that hopefully we end up with maybe 4 or 5 mappers each with 1000 >> or so triangles. Implementing that is not trivial though so I don't think >> anyone has plans for it yet. >> >> Another approach would be to look at what is generating your data and try >> to determine why some blocks have normals while others do not. because if >> you can get the blocks to be homogeneous then you will get the fast path. >> >> Thanks >> Ken >> >> >> >> >> >> >> >> On Wed, Dec 16, 2015 at 11:39 AM, Adam Lyon wrote: >> >>> Hi Ken and Utkarsh, Checking back in with this issue... I still find >>> that interaction with the g-2 ring in ParaView v5rc2 is very slow compared >>> to v4.4. It looks like you all have a solution in mind. I'm happy to build >>> from master to try it if the solution is there. Thanks again and Happy >>> Holidays!!! I really appreciate you all looking at this problem. -- Adam >>> >>> *------* >>> >>> *Adam L. Lyon* >>> *Scientist; Associate Division Head for Systems for Scientific >>> Applications* >>> >>> Scientific Computing Division & Muon g-2 Experiment >>> Fermi National Accelerator Laboratory >>> 630 840 5522 office >>> www.fnal.gov >>> lyon at fnal.gov >>> >>> Connect with us! >>> Newsletter | Facebook >>> | Twitter >>> >>> >>> On Fri, Nov 20, 2015 at 1:48 PM, Ken Martin >>> wrote: >>> >>>> You could maybe have an actor per LOD and then swap actors in and out. >>>> >>>> Actor owns the property, backface property, and texture. Changes to >>>> those objects can cause VBO/IBO rebuilds (switching from surface to >>>> wireframe, adding a texture map, flat versus phong shading, edge >>>> visibility, line width, etc.) The old backend only looked at the actor's >>>> property which is sort of broken. >>>> >>>> For example in the old backend: create two properties, one set to >>>> wireframe, one set to surface. Then create an actor and mapper set to use >>>> display lists. Switching between the two properties will cause an actor >>>> mtime change, but the properties themselves would still have low mtimes I >>>> believe. In that case the old backend will end up stuck in one >>>> representation because it only looks at the property mtime not actor. >>>> >>>> To make the VBO/IBO rebuild safely (but less often than currently) I >>>> think the solution is to check the mtimes as is done currently, if those >>>> are modified then collect up the parameters that require a VBO or IBO >>>> rebuild and compare them to a stored value from the last build. If >>>> different force a rebuild. That is the best solution IMO just takes some >>>> time. I sort of wanted to do that anyhow but now I can say you forced me >>>> into it :-) >>>> >>>> Thanks >>>> Ken >>>> >>>> >>>> >>>> >>>> On Fri, Nov 20, 2015 at 1:57 PM, Utkarsh Ayachit < >>>> utkarsh.ayachit at kitware.com> wrote: >>>> >>>>> > I did notice PV is forcing the actor to be modified every time the >>>>> LOD >>>>> > changes (which is a lot). Modifying the actor causes the VBO/IBOs to >>>>> rebuild >>>>> > so it would be better not to do that unless you really need to and >>>>> in this >>>>> > case I'm not sure why it is being done. Specifically I think it is in >>>>> > vtkPVLODActor::Modified where it calls this->Device->Modified() . >>>>> The LOD >>>>> > actor is being modified as a result of calling SetEnableLOD >>>>> constantly >>>>> > flipping between true and false. That is not the cause of this issue >>>>> but it >>>>> > is something I noticed that will be a pain for large datasets. >>>>> >>>>> Ken, currently, there's no way around it. vtkPVLODActor works by >>>>> changing the mapper on the internal vtkActor aka Device when LOD mode >>>>> is toggled. That will indeed change the Device's MTime even if we stop >>>>> calling this->Device->Modiied() in the vtkPVLODActor::Modified(). The >>>>> question is why are VBO/IBOs rebuild if actor MTime changes? VBOs >>>>> would be data dependent right? Most of data-dependent properties are >>>>> on the Mapper, not the actor. Shouldn't the code that re-creates >>>>> VBO/IBOs only depend on Mapper's MTime? >>>>> >>>>> Utkarsh >>>>> >>>> >>>> >>>> >>>> -- >>>> Ken Martin PhD >>>> Chairman & CFO >>>> Kitware Inc. >>>> 28 Corporate Drive >>>> Clifton Park NY 12065 >>>> 518 371 3971 >>>> >>>> This communication, including all attachments, contains confidential >>>> and legally privileged information, and it is intended only for the use of >>>> the addressee. Access to this email by anyone else is unauthorized. If you >>>> are not the intended recipient, any disclosure, copying, distribution or >>>> any action taken in reliance on it is prohibited and may be unlawful. If >>>> you received this communication in error please notify us immediately and >>>> destroy the original message. Thank you. >>>> >>> >>> >> >> >> -- >> Ken Martin PhD >> Chairman & CFO >> Kitware Inc. >> 28 Corporate Drive >> Clifton Park NY 12065 >> 518 371 3971 >> >> This communication, including all attachments, contains confidential and >> legally privileged information, and it is intended only for the use of the >> addressee. Access to this email by anyone else is unauthorized. If you are >> not the intended recipient, any disclosure, copying, distribution or any >> action taken in reliance on it is prohibited and may be unlawful. If you >> received this communication in error please notify us immediately and >> destroy the original message. Thank you. >> > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fcueto at gmail.com Wed Dec 16 15:12:06 2015 From: fcueto at gmail.com (Fernando G. del Cueto) Date: Wed, 16 Dec 2015 14:12:06 -0600 Subject: [Paraview] Paraview 5.0.0RC2 crashes at launch Message-ID: Sadly it still crashes immediately after showing the splash screen without much information. I tried the -dr argument in the command line, but without success either. Any idea of what could be wrong? I also have issues displaying axes labels on Paraview 4.4. I suspect some video driver problem, maybe? Fernando -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error5.0RC2.png Type: image/png Size: 92808 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Wed Dec 16 16:20:57 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 16 Dec 2015 16:20:57 -0500 Subject: [Paraview] Any objections to dropping 32 bit WIndows binaries? Message-ID: Folks, I am trying to see if there are any objections to dropping 32 bit Windows binaries for the 5.0 release. We'll still distribute the 64 bit Windows binaries. Thanks Utkarsh From utkarsh.ayachit at kitware.com Wed Dec 16 16:31:44 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 16 Dec 2015 16:31:44 -0500 Subject: [Paraview] Paraview 5.0.0RC2 crashes at launch In-Reply-To: References: Message-ID: The issue is indeed that your OpenGL drivers are old. We're working on something that will catch this and report it in a more graceful way. Utkarsh On Wed, Dec 16, 2015 at 3:12 PM, Fernando G. del Cueto wrote: > Sadly it still crashes immediately after showing the splash screen without > much information. > > I tried the -dr argument in the command line, but without success either. > > Any idea of what could be wrong? I also have issues displaying axes labels > on Paraview 4.4. I suspect some video driver problem, maybe? > > Fernando > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From ben.boeckel at kitware.com Wed Dec 16 16:38:50 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 16 Dec 2015 16:38:50 -0500 Subject: [Paraview] Differences between OpenGL and OpenGL2 versions of ParaView In-Reply-To: References: <9661715ca38f44ddacde89a22785e882@MAIL04V-CAS03.fnal.gov> <5BBB77AF-80DE-44B6-A78B-744C4AE89866@kitware.com> Message-ID: <20151216213850.GA18404@megas.khq.kitware.com> On Wed, Dec 16, 2015 at 13:22:09 -0600, Adam Lyon wrote: > I'm curious as to why I didn't have any of these problems in v4.4 -- or is > this two path multiblock rendering code all new for v5? Thanks again!! -- 4.4 defaults to the OpenGL1 backend (glBegin/glEnd); 5.0 is using the OpenGL2 backend (shaders and VBOs). --Ben From dave.demarle at kitware.com Wed Dec 16 20:23:01 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 16 Dec 2015 20:23:01 -0500 Subject: [Paraview] Access point/cell data as Python variable In-Reply-To: <1450218173628.82915@sth.kth.se> References: <1450218173628.82915@sth.kth.se> Message-ID: It isn't easy to get the the values, because the client only accesses proxies for the filters and data objects, which often exist on remote distributed memory parallel machines. Three strategies: 1) write a python programmable filter. That runs in parallel on remote machines and has access to the actual data. 2) use servermanager.Fetch to copy the data to the client 3) if you are never going to run in parallel, you can use proxy.GetClientSideObject() Personally I recommend #1. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Dec 15, 2015 at 5:22 PM, David Larsson wrote: > Dear all, > > > I am working with imported temporal velocity fields (from pvd/vtu) files. > > > Does anyone know how I in pvpython can access point or cell data as a > specified variable (array)? > I easily find out how to load data into paraview using the Python tracer > ('solutoinpvd = PVDReader(FielName='myfile.pvd')) but can't seem to know > how to access the velocity field in pvpython after that. > > > I want the point or cell data loaded in specified variables in order > to modify e.g. the velocity or calculated vorticity field through scripting > (as an example, set all values >0 to a given value), but I can't seem to > find these variables (or set variables to them). > > > Thanks for the help. > > > /David > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Dec 16 20:29:34 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 16 Dec 2015 20:29:34 -0500 Subject: [Paraview] Filter cell type from PolyData VTK file In-Reply-To: <20151216085639.F838CBD2@centrum.cz> References: <56708C1C.6040408@centrum.cz> <56709864.8070605@bresnan.net> <20151216085639.F838CBD2@centrum.cz> Message-ID: Last time this came up to my knowledge was: http://markmail.org/thread/pbghkrm2zbubkj54 od = self.GetOutput() od.ShallowCopy(self.GetInput()) cta = vtk.vtkIntArray() cta.SetName("cell types") cta.SetNumberOfComponents(1) cta.SetNumberOfTuples(od.GetNumberOfCells()) od.GetCellData().AddArray(cta) for x in xrange(0,od.GetNumberOfCells()): cta.SetValue(x,od.GetCell(x).GetCellType()) Which does what you originally suggested. There are probably shorter incantations now in the numpy based python calculator. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Dec 16, 2015 at 2:56 AM, Viktor Sip wrote: > Thanks for the helpful tips. > First approach has the disadvantage that I need to specify the underlying > points in each of the separate files, which leads again to some redundancy. > But good to know. > EnSight format looks promising though, I didn't know about it before. > > Thanks again, > Viktor > > ______________________________________________________________ > > Od: Samuel Key > > Komu: > > Datum: 15.12.2015 23:47 > > P?edm?t: Re: [Paraview] Filter cell type from PolyData VTK file > > > >Victor, > > > > > > > >Off the top of my head, I can think of three different ways to do this: > > > > > > > >(1) Put each cell-type in a separate *.vtp file. You can then load each > cell-type separately or you can load them with a *.pvd meta-file (sample > attached) as "one object" and use the Extract Block filter to display any > number and combination of cell-types. > > > > > > > >(2) You can use the EnSight format for your results. This format has a > Part-construct that allows mixed-cell objects and that can be used to > organize your cells any way you like, for example, by cell-type, by > material, by sub-assemblies, ... Again, the Extract Block filter can be > used to display any number and combination of 'Parts.' > > > > > > > >(3) When you write the *.vtp file assign each cell its vtk-cell-type > number as data, and then use the Threshold filter applied to the cell's > cell-type value. > > > > > > > >There are probably other ways as well. > > > > > > > >Hope this helps. > > > > > > > >Sam Key > > > > > > > > > > > > > > > > > > > >On 12/15/2015 2:54 PM, Viktor Sip wrote: > > > > > > > >Dear all, > > > > > > > >is there a way to filter and show only a specific cell type? > > > > > > > >In my application I am exporting a PolyData VTK file containing some > Polys and Lines. When imported into Paraview, both Polys and Lines are > shown, and I did not find a simple way to show only Polys. > > > >What I can do is to export additional CellData array with a number > specifying cell type and then apply Treshold in Paraview. However that > seems redundant, as the type is already stored in the file somewhere. > > > >So my question is, is there a direct way? > > > > > > > >Simplified example of the exported VTK file is attached. > > > > > > > >Kind regards, > > > >Viktor > > > > > > > > > > > > > > > >_______________________________________________ Powered by > www.kitware.com Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html Please keep messages > on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > Search the list archives at: http://markmail.org/search/?q=ParaView > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > > >---------- > > > >_______________________________________________ > >Powered by www.kitware.com > > > >Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > >Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > >Search the list archives at: http://markmail.org/search/?q=ParaView > > > >Follow this link to subscribe/unsubscribe: > >http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Dec 16 20:46:46 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 16 Dec 2015 20:46:46 -0500 Subject: [Paraview] reading input directly from memory? In-Reply-To: <201512151158.tBFBw45U011995@mech-as222.men.bris.ac.uk> References: <201512151158.tBFBw45U011995@mech-as222.men.bris.ac.uk> Message-ID: On Tue, Dec 15, 2015 at 6:58 AM, Anton Shterenlikht wrote: > At first glance, yes, this is what I'm after. > I'll read the manuals, but briefly, is this just > paraview functionality via library calls? > Roughly yes. A "full" catalyst installation is just ParaView's Servermanager. Include and link to that to write an adaptor which populates vtk data structures from the simulation's (ideally zero copy). Link them together and you are in business. 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 axkibe at gmail.com Thu Dec 17 04:19:42 2015 From: axkibe at gmail.com (Axel Kittenberger) Date: Thu, 17 Dec 2015 10:19:42 +0100 Subject: [Paraview] Volume Rendering with NumberOfScalarComponents > 1 In-Reply-To: <908959F8-C53F-46A3-97B1-BE827D2DB8BC@kitware.com> References: <908959F8-C53F-46A3-97B1-BE827D2DB8BC@kitware.com> Message-ID: > Do you have to use paraview gui? No, the task on hand is already accomplished so no rush. I merely used the occasion to further teach myself a bit about scientific visualization software and the alternatives. I wonder, is it possible to have the volume data as HSV? That is the "value" is natural the intensity and equals the alpha value and a second "label" array the gives Hue and Saturation? That would feel more natural to me than having a Red/Green/Blue volume data and having it to code back RGB using 1:1 colorTransfers. - Axel On Wed, Dec 16, 2015 at 4:18 PM, Aashish Chaudhary < aashish.chaudhary at kitware.com> wrote: > Axel > > We were just discussing this few days ago. Do you have to use paraview > gui? Or paraview python will work? There might be a way in pv python route. > > Thanks > > Sent from my iPhone > > > On Dec 16, 2015, at 5:01 AM, Axel Kittenberger wrote: > > > > Hello, > > > > the Python VTK script below gives results, like a expect. Now I'm trying > to reproduce it in Paraview and I fail. > > > > I get rather confused as soon I give it a source with more than one > scalar component. > > Paraview creates one color map; I would expect 3 color maps, 1 for every > component. > > What ever I do effective opacity is always 1. That is I see a black cube > with it's surface the images > > of the data on its surface (so far correct), however no effective volume > rendering -- I selected Volume, "Ray Cast Only" > > which should be vtkFixedPointVolumeRayCastMapper as far I understood. > > > > I tried creating 3 readers with the different scalar components > extracted first, but doesn't give > > correct rendering -- neither in VTK nor in paraview, since multiple > renderer seem to compete which gets to > > draw a pixel instead of composing them together > > like a red transparent + a green transparent should give a yellow > transparent impression. > > > > How can I achieve the same result with Paraview? > > > > Kind regards, Axel > > > > -------------------------- > > #!/usr/bin/env python > > > > import vtk > > > > # Create the standard renderer, render window and interactor > > ren = vtk.vtkRenderer( ) > > renWin = vtk.vtkRenderWindow( ) > > renWin.AddRenderer( ren ) > > iren = vtk.vtkRenderWindowInteractor( ) > > iren.SetRenderWindow( renWin ) > > > > reader = vtk.vtkImageReader2( ) > > reader.SetFileName( "./data.raw" ); > > reader.SetDataScalarTypeToUnsignedChar( ); > > reader.SetNumberOfScalarComponents( 3 ); > > reader.SetFileDimensionality( 3 ); > > reader.SetDataExtent( 0, 261, 0, 511, 0, 21 ); > > reader.SetDataSpacing( 1, 1, 3.5 ); > > > > # Create transfer mapping scalar value to opacity > > opacityTransferFunction = vtk.vtkPiecewiseFunction( ) > > opacityTransferFunction.AddPoint( 0, 0.0 ) > > opacityTransferFunction.AddPoint( 20, 0.0 ) > > opacityTransferFunction.AddPoint( 40, 0.1 ) > > opacityTransferFunction.AddPoint( 255, 0.1 ) > > > > # Create transfer mapping scalar value to color > > > > colorRedTransferFunction = vtk.vtkColorTransferFunction( ) > > colorRedTransferFunction.AddRGBPoint( 0.0, 0.2, 0.0, 0.0 ) > > colorRedTransferFunction.AddRGBPoint( 255.0, 1.0, 0.0, 0.0 ) > > > > colorGreenTransferFunction = vtk.vtkColorTransferFunction( ) > > colorGreenTransferFunction.AddRGBPoint( 0.0, 0.0, 0.2, 0.0 ) > > colorGreenTransferFunction.AddRGBPoint( 255.0, 0.0, 1.0, 0.0 ) > > > > colorBlueTransferFunction = vtk.vtkColorTransferFunction( ) > > colorBlueTransferFunction.AddRGBPoint( 0.0, 0.0, 0.0, 0.0 ) > > colorBlueTransferFunction.AddRGBPoint( 255.0, 0.0, 0.0, 1.0 ) > > > > volumeProperty = vtk.vtkVolumeProperty( ) > > volumeProperty.SetColor( 0, colorRedTransferFunction ) > > volumeProperty.SetColor( 1, colorGreenTransferFunction ) > > volumeProperty.SetColor( 2, colorBlueTransferFunction ) > > > > volumeProperty.SetScalarOpacity( 0, opacityTransferFunction ) > > volumeProperty.SetScalarOpacity( 1, opacityTransferFunction ) > > volumeProperty.SetScalarOpacity( 2, opacityTransferFunction ) > > volumeProperty.SetInterpolationTypeToLinear( ) > > > > volumeMapper = vtk.vtkFixedPointVolumeRayCastMapper( ) > > volumeMapper.SetInputConnection( reader.GetOutputPort( ) ) > > volumeMapper.SetNumberOfThreads( 1 ) > > > > volume = vtk.vtkVolume( ) > > volume.SetMapper( volumeMapper ) > > volume.SetProperty( volumeProperty ) > > > > ren.AddVolume( volume ) > > ren.SetBackground( 1, 1, 1 ) > > renWin.SetSize( 600, 600 ) > > > > def CheckAbort( obj, event ): > > if obj.GetEventPending( ) != 0: > > obj.SetAbortRender( 1 ) > > > > renWin.AddObserver( "AbortCheckEvent", CheckAbort ) > > > > iren.Initialize( ) > > renWin.Render( ) > > iren.Start( ) > > -------------------------- > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xzhao99 at gmail.com Thu Dec 17 12:39:35 2015 From: xzhao99 at gmail.com (Xujun Zhao) Date: Thu, 17 Dec 2015 11:39:35 -0600 Subject: [Paraview] Fwd: File format and visualization of bead-spring model in Paraview In-Reply-To: References: Message-ID: Hi all, I am dealing with polymer chains which are represented by bead-spring models. I currently output csv files for the position of the beads and visualize them with "Table to points" and Glyph. But I am not very clear how to visualize the springs that connect the beads. Can anyone give me some hints about the relative file format and visualization of the bead-spring models? Thank you very much. Best, Xujun -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Dec 17 13:05:06 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 17 Dec 2015 13:05:06 -0500 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: <589CEB614006334D93C1A48C1B1964C9027CEAC0201B@srvmes03.spe-ch-md9.net> References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC0201B@srvmes03.spe-ch-md9.net> Message-ID: Frank, First of all, thanks for all your exhausting testing, it's greatly appreciated! * OSMesa and MESA_GL_VERSION_OVERRIDE Communicating with the Mesa team, we learnt that MESA_GL_VERSION_OVERRIDE is a bad idea since it doesnt' really create the specified OpenGL context. Thus if anything tries to use features from the specific OpenGL version, the rendering would crash and burn. Working with Brian Paul from the Mesa team, Ken recently pushed a fix to VTK (after the RC2) that uses new OSMesa API to create the correct OpenGL context. This new OSMesa API will appear in Mesa 11.2, however. Earlier version can be patched using the "alpha" patch that Brian provided us (attached). * Classic v/s llvm Your observation is indeed correct. llvmpipe is the way to go for software rendering. On my builds, classic mesa was painstakingly slow for rendering even small geometries. * Issues with LIC Another correct observation. There are a few regressions in the new implementation for SurfaceLIC. Realistically, we may not be able to address these before the 5.0 release. If you're using SurfaceLIC heavily, I'd suggest building ParaView 5.0 with the older OpenGL backend (or sticking with 4.4) for the interim. * OSMesa + SWR While currently I am not sure openswr+osmesa builds are possible, I wouldn't be surprised if that on the roadmap. I am going to try to contact the OpenSWR team to see if they have any thoughts on that. Utkarsh -------------- next part -------------- A non-text attachment was scrubbed... Name: mesa.patch Type: text/x-patch Size: 11012 bytes Desc: not available URL: From leonardopessanha74 at gmail.com Thu Dec 17 13:10:01 2015 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Thu, 17 Dec 2015 16:10:01 -0200 Subject: [Paraview] Saving Interpolated Data Message-ID: Hi, I have a dataset with 30 timesteps, after applying some temporal filters and try to save my data, it will only save the 30 timesteps. I would like to interpolate my data and save it interpolated. It is possible to do that? Thanks in advance, Leonardo Pessanha, COPPE-UFRJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkxls23 at gmail.com Thu Dec 17 17:12:25 2015 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Fri, 18 Dec 2015 00:12:25 +0200 Subject: [Paraview] rpath error when compiling ParaView 5.0 In-Reply-To: <566C6335.2050609@gmail.com> References: <566332BD.2080008@gmail.com> <20151207163835.GA3080@megas.khq.kitware.com> <566C6335.2050609@gmail.com> Message-ID: <56733349.4020606@gmail.com> Hi, as a follow up, I found that the error is related to this option: PARAVIEW_INSTALL_DEVELOPMENT_FILES For some reason I had it switched on and by switching it off, I can avoid the rpath error. Though I don't know why. I should probably note that for older build environments (cmake 3.0.2/ gcc 4.8.3) this error does not appear. -Armin On 12/12/2015 08:11 PM, Armin Wehrfritz wrote: > Thanks for your reply! > > On 12/07/2015 06:38 PM, Ben Boeckel wrote: >> On Sat, Dec 05, 2015 at 20:53:49 +0200, Armin Wehrfritz wrote: >>> I'm building ParaView (version 5.0 RC1) for openSUSE Tumbleweed (using >>> gcc 5.2.1) and get an error related to rpath (see below). I cannot say >>> much more about this, since don't really understand what's going >>> wrong here. >>> >>> Does anybody have some hints how to solve this? >> >> Are you giving any rpath-related settings to CMake? What is the >> configure line? > No, not that I would be aware of. Here my configure line: > > cmake \ > -DCMAKE_BUILD_TYPE=Release \ > -DCMAKE_INSTALL_PREFIX:PATH=/opt/paraview/5.0 \ > -DCMAKE_CXX_COMPILER:STRING='mpicxx' \ > -DCMAKE_C_COMPILER:STRING='mpicc' \ > -DBUILD_SHARED_LIBS:BOOL=ON \ > -DBUILD_DOCUMENTATION:BOOL=ON \ > -DBUILD_EXAMPLES:BOOL=ON \ > -DBUILD_TESTING:BOOL=OFF \ > -DPARAVIEW_BUILD_QT_GUI:BOOL=ON \ > -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=ON \ > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \ > -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON \ > -DPARAVIEW_USE_MPI:BOOL=ON \ > -DVTK_WRAP_PYTHON:BOOL=ON \ > -DVTK_WRAP_PYTHON_SIP:BOOL=ON \ > -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF \ > -DVTK_USE_SYSTEM_EXPAT:BOOL=ON \ > -DVTK_USE_SYSTEM_FREETYPE:BOOL=ON \ > -DVTK_USE_SYSTEM_JPEG:BOOL=ON \ > -DVTK_USE_SYSTEM_PNG:BOOL=ON \ > -DVTK_USE_SYSTEM_TIFF:BOOL=ON \ > -DVTK_USE_SYSTEM_ZLIB:BOOL=ON \ > -DVTK_USE_SYSTEM_ZOPE:BOOL=ON \ > -DVTK_USE_SYSTEM_TWISTED:BOOL=ON \ > ../ > >>> Please let me know if you need more information. >> >> What version of CMake are you using? > I'm using CMake 3.3.2. > > I can send the CMakeCache.txt file if that helps to track this down. > > -Armin > From frank.albina at sauber-motorsport.com Fri Dec 18 02:52:05 2015 From: frank.albina at sauber-motorsport.com (Albina, Frank) Date: Fri, 18 Dec 2015 08:52:05 +0100 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC0201B@srvmes03.spe-ch-md9.net> Message-ID: <589CEB614006334D93C1A48C1B1964C9027CEAC0202F@srvmes03.spe-ch-md9.net> Dear Utkarsh! Thank you very much for your swift reply and for sending the patch to the MESA libraries. I will apply it asap. Also, thank you for liaising with the OpenSWR team in order to check if they support or plan supporting OSMESA. It is of interest for us, since any gain in reducing rendering times during post-processing of our simulations has a substantial impact in the longer term on the number of simulations we can perform (i.e. less time spent in post-processing means that there are more resources left for running simulations). Concerning the surfaceLIC, we are using it primarily on GPUs but it would have been great to have the possibility to switch to software rendering under ParaView 5.0.0. This was also motivated by the fact that the software has made a good step in reducing rendering times. To underline this, below is a summary of the rendering times in seconds for generating 60 pressure-contours images on the same compute cluster: Paraview 3.8.1 Paraview 4.3.1 Paraview 5.0.0-rc2 Intel MPI 5.0.1.035 Intel MPI 5.0.1.035 Intel MPI 5.0.1.035 MESA v10.5.5 MESA v10.5.5 llvm-MESA-11.0.7 Cores python v2.7.8 python v2.7.8 python v2.7.10 1 339.32 502.49 320.29 2 177.62 276.19 86.43 4 95.91 142.94 50.64 8 57.17 87.47 33.71 16 34.91 50.49 26.12 32 22.51 32.44 17.36 Basically, I can't wait to get my hands on the new ParaView release. On my side I will continue today to perform additional tests which are part of the way we use ParaView on our compute cluster. I'll keep you posted on that . Talk to you soon. Frank. -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Donnerstag, 17. Dezember 2015 19:05 To: Albina, Frank Cc: paraview at paraview.org Subject: Re: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 Frank, First of all, thanks for all your exhausting testing, it's greatly appreciated! * OSMesa and MESA_GL_VERSION_OVERRIDE Communicating with the Mesa team, we learnt that MESA_GL_VERSION_OVERRIDE is a bad idea since it doesnt' really create the specified OpenGL context. Thus if anything tries to use features from the specific OpenGL version, the rendering would crash and burn. Working with Brian Paul from the Mesa team, Ken recently pushed a fix to VTK (after the RC2) that uses new OSMesa API to create the correct OpenGL context. This new OSMesa API will appear in Mesa 11.2, however. Earlier version can be patched using the "alpha" patch that Brian provided us (attached). * Classic v/s llvm Your observation is indeed correct. llvmpipe is the way to go for software rendering. On my builds, classic mesa was painstakingly slow for rendering even small geometries. * Issues with LIC Another correct observation. There are a few regressions in the new implementation for SurfaceLIC. Realistically, we may not be able to address these before the 5.0 release. If you're using SurfaceLIC heavily, I'd suggest building ParaView 5.0 with the older OpenGL backend (or sticking with 4.4) for the interim. * OSMesa + SWR While currently I am not sure openswr+osmesa builds are possible, I wouldn't be surprised if that on the roadmap. I am going to try to contact the OpenSWR team to see if they have any thoughts on that. Utkarsh From nico.schloemer at gmail.com Fri Dec 18 05:49:45 2015 From: nico.schloemer at gmail.com (=?UTF-8?Q?Nico_Schl=C3=B6mer?=) Date: Fri, 18 Dec 2015 10:49:45 +0000 Subject: [Paraview] XDMF wrong format? Message-ID: Hi everyone, I'm creating XDMF files with VTK's XdmfWriter, and while the contents of the file look alright to me (representing two tetrahedra), ParaView 5.0RC1 will only show two triangles. Not sure where this is going wrong. The file is attached. Any hints? Cheers, Nico -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test.xmf Type: audio/x-xmf Size: 570 bytes Desc: not available URL: From D.J.Baker at soton.ac.uk Fri Dec 18 05:54:50 2015 From: D.J.Baker at soton.ac.uk (Baker D.J.) Date: Fri, 18 Dec 2015 10:54:50 +0000 Subject: [Paraview] Building paraview with piston -- enabling GPGPU support Message-ID: <9230853A36E499458AF5EAD38C13DCD5219CCC3D@SRV00048.soton.ac.uk> Hello, I am trying to integrate GPGPU support in paraview v4.4.0. With that in mind I have enabled "PARAVIEW_USE_PISTON" in the cmake configurator, and downloaded the Piston source code. The software that I'm using is... Paraview 4.4.0 Piston 0.4 Cuda toolkit 7.5.18 The make fails when compiling vtkPistonConverters.cu, and I cannot make any progress to resolve my issues. In addition to a load of warnings I see the following types of errors: piston/choose_container.h(42): error: namespace "thrust::detail" has no member "default_device_space_tag" VTK/Accelerators/Piston/vtkPistonConverters.cu(93): error: expected a type specifier (a couple) VTK/Accelerators/Piston/vtkPistonConverters.cu(36): error: too few arguments for class template "piston::vtk_image3d" (several times) I'm not a C/C++ programmer and so this is a show stopper for me. I've tried downloading the current VTK source, however that does not help. Could anyone please advise on the source of these errors or alternatively advise which combination of paraview/piston/cuda give a working solution. Best regards, David. -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank.albina at sauber-motorsport.com Fri Dec 18 08:30:34 2015 From: frank.albina at sauber-motorsport.com (Albina, Frank) Date: Fri, 18 Dec 2015 14:30:34 +0100 Subject: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel Message-ID: <589CEB614006334D93C1A48C1B1964C9027CEAC0204E@srvmes03.spe-ch-md9.net> Dear all! I recompiled Paraview-v5.0.0-rc2 from scratch using OpenMPI v1.6.5 and GCC v4.7.2 on my workstation. The QT & Python versions are the default system versions and are resp. 4.8.4 & 2.7.3. After successful compilation and installation, I start 8 parallel pvserver instances with: mpirun -np 8 pvserver -sp=7436 Then, I start paraview and connect to the server running on the same machine. After connection is established, paraview fails with a segmentation fault. Waiting for client... Connection URL: cs://ws334:7436 Accepting connection(s): ws334:7436 Client connected. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 809 vtkSocketCommunicator (0x2b7a600): Could not receive tag. 1 ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. [...] ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. -------------------------------------------------------------------------- mpirun noticed that process rank 0 with PID 13964 on node ws334 exited on signal 11 (Segmentation fault). -------------------------------------------------------------------------- I have included hereafter how Paraview was compiled: cmake $sourceDir \ -DBUILD_SHARED_LIBS:BOOL=ON\ -DBUILD_TESTING:BOOL=OFF\ -DBUILD_DOCUMENTATION:BOOL=ON\ -DCMAKE_BUILD_TYPE:STRING=Release\ -DPARAVIEW_ENABLE_CATALYST:BOOL=ON\ -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ -DPARAVIEW_USE_MPI:BOOL=ON\ -DPARAVIEW_USE_UNIFIED_BINDINGS:BOOL=ON\ -DPARAVIEW_ENABLE_WEB:BOOL=ON\ -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF\ -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE\ -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ -DVTK_USE_OFFSCREEN:BOOL=OFF\ -DVTK_USE_X:BOOL=ON\ -DVTK_USE_QT=ON\ -DVTK_USE_DISPLAY=ON\ -DVTK_USE_GUI_SUPPORT:BOOL=ON\ -DPARAVIEW_BUILD_QT_GUI:BOOL=ON\ -DCMAKE_INSTALL_PREFIX:PATH=$installDir\ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON\ -DPYTHON_ENABLE_MODULE_MPIPython:BOOL=ON\ -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake\ -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2\ -DPYTHON_INCLUDE_DIR:FILEPATH=/usr/include/python2.7\ -DPYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.7.so\ -DPYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so\ -DVTK_RENDERING_BACKEND:STRING=OpenGL2\ -DModule_vtkRenderingLICOpenGL2:BOOL=ON I must have missed something since I guess that Paraview using parallel servers should run, even when there is only one GPU available. Any hints would be greatly appreciated. Best regards, Frank Albina -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 18 09:07:34 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 18 Dec 2015 09:07:34 -0500 Subject: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel In-Reply-To: <589CEB614006334D93C1A48C1B1964C9027CEAC0204E@srvmes03.spe-ch-md9.net> References: <589CEB614006334D93C1A48C1B1964C9027CEAC0204E@srvmes03.spe-ch-md9.net> Message-ID: Hi Frank, Since you said you recompiled ParaView, I suspect that maybe you forgot to update the submodules ParaView uses. In the ParaView source tree, run git status If VTK is listed, it may say there are new commits available for VTK. To update VTK, run git submodule update This has been an issue a few folks have encountered in the past. Also, double-check that your ParaView client and server are truly from the same build. HTH, Cory On Fri, Dec 18, 2015 at 8:30 AM, Albina, Frank < frank.albina at sauber-motorsport.com> wrote: > Dear all! > > > > I recompiled Paraview-v5.0.0-rc2 from scratch using OpenMPI v1.6.5 and GCC > v4.7.2 on my workstation. > > The QT & Python versions are the default system versions and are resp. > 4.8.4 & 2.7.3. > > > > After successful compilation and installation, I start 8 parallel pvserver > instances with: > > mpirun ?np 8 pvserver ?sp=7436 > > > > Then, I start paraview and connect to the server running on the same > machine. After connection is established, paraview fails with a > segmentation fault. > > > > Waiting for client... > > Connection URL: cs://ws334:7436 > > Accepting connection(s): ws334:7436 > > Client connected. > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Parallel/Core/vtkSocketCommunicator.cxx, > line 809 > > vtkSocketCommunicator (0x2b7a600): Could not receive tag. 1 > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > [?] > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > -------------------------------------------------------------------------- > > mpirun noticed that process rank 0 with PID 13964 on node ws334 exited on > signal 11 (Segmentation fault). > > -------------------------------------------------------------------------- > > > > I have included hereafter how Paraview was compiled: > > cmake $sourceDir \ > > -DBUILD_SHARED_LIBS:BOOL=ON\ > > -DBUILD_TESTING:BOOL=OFF\ > > -DBUILD_DOCUMENTATION:BOOL=ON\ > > -DCMAKE_BUILD_TYPE:STRING=Release\ > > -DPARAVIEW_ENABLE_CATALYST:BOOL=ON\ > > -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ > > -DPARAVIEW_USE_MPI:BOOL=ON\ > > -DPARAVIEW_USE_UNIFIED_BINDINGS:BOOL=ON\ > > -DPARAVIEW_ENABLE_WEB:BOOL=ON\ > > -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF\ > > -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE\ > > -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ > > -DVTK_USE_OFFSCREEN:BOOL=OFF\ > > -DVTK_USE_X:BOOL=ON\ > > -DVTK_USE_QT=ON\ > > -DVTK_USE_DISPLAY=ON\ > > -DVTK_USE_GUI_SUPPORT:BOOL=ON\ > > -DPARAVIEW_BUILD_QT_GUI:BOOL=ON\ > > -DCMAKE_INSTALL_PREFIX:PATH=$installDir\ > > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON\ > > -DPYTHON_ENABLE_MODULE_MPIPython:BOOL=ON\ > > -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake\ > > -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2\ > > -DPYTHON_INCLUDE_DIR:FILEPATH=/usr/include/python2.7\ > > -DPYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.7.so\ > > -DPYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so\ > > -DVTK_RENDERING_BACKEND:STRING=OpenGL2\ > > -DModule_vtkRenderingLICOpenGL2:BOOL=ON > > > > I must have missed something since I guess that Paraview using parallel > servers should run, even when there is only one GPU available. Any hints > would be greatly appreciated. > > > > Best regards, > > > > *Frank Albina * > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank.albina at sauber-motorsport.com Fri Dec 18 09:15:24 2015 From: frank.albina at sauber-motorsport.com (Albina, Frank) Date: Fri, 18 Dec 2015 15:15:24 +0100 Subject: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC0204E@srvmes03.spe-ch-md9.net> Message-ID: <589CEB614006334D93C1A48C1B1964C9027CEAC02058@srvmes03.spe-ch-md9.net> Hi Cory! I have compiled the source code from the Paraview v5.0.0-RC2 source files that I downloaded earlier this week from http://www.paraview.org/download/. No GIT repository there and none to be found in the top-level directory of the source files. Paraview client & server are from the same build, since I am starting both server and client from the same command line on the (Linux) workstation, hence I am using the same environement. HTH, Frank. From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Freitag, 18. Dezember 2015 15:08 To: Albina, Frank Cc: paraview at paraview.org Subject: Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel Hi Frank, Since you said you recompiled ParaView, I suspect that maybe you forgot to update the submodules ParaView uses. In the ParaView source tree, run git status If VTK is listed, it may say there are new commits available for VTK. To update VTK, run git submodule update This has been an issue a few folks have encountered in the past. Also, double-check that your ParaView client and server are truly from the same build. HTH, Cory On Fri, Dec 18, 2015 at 8:30 AM, Albina, Frank > wrote: Dear all! I recompiled Paraview-v5.0.0-rc2 from scratch using OpenMPI v1.6.5 and GCC v4.7.2 on my workstation. The QT & Python versions are the default system versions and are resp. 4.8.4 & 2.7.3. After successful compilation and installation, I start 8 parallel pvserver instances with: mpirun ?np 8 pvserver ?sp=7436 Then, I start paraview and connect to the server running on the same machine. After connection is established, paraview fails with a segmentation fault. Waiting for client... Connection URL: cs://ws334:7436 Accepting connection(s): ws334:7436 Client connected. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 809 vtkSocketCommunicator (0x2b7a600): Could not receive tag. 1 ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. [?] ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. -------------------------------------------------------------------------- mpirun noticed that process rank 0 with PID 13964 on node ws334 exited on signal 11 (Segmentation fault). -------------------------------------------------------------------------- I have included hereafter how Paraview was compiled: cmake $sourceDir \ -DBUILD_SHARED_LIBS:BOOL=ON\ -DBUILD_TESTING:BOOL=OFF\ -DBUILD_DOCUMENTATION:BOOL=ON\ -DCMAKE_BUILD_TYPE:STRING=Release\ -DPARAVIEW_ENABLE_CATALYST:BOOL=ON\ -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ -DPARAVIEW_USE_MPI:BOOL=ON\ -DPARAVIEW_USE_UNIFIED_BINDINGS:BOOL=ON\ -DPARAVIEW_ENABLE_WEB:BOOL=ON\ -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF\ -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE\ -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ -DVTK_USE_OFFSCREEN:BOOL=OFF\ -DVTK_USE_X:BOOL=ON\ -DVTK_USE_QT=ON\ -DVTK_USE_DISPLAY=ON\ -DVTK_USE_GUI_SUPPORT:BOOL=ON\ -DPARAVIEW_BUILD_QT_GUI:BOOL=ON\ -DCMAKE_INSTALL_PREFIX:PATH=$installDir\ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON\ -DPYTHON_ENABLE_MODULE_MPIPython:BOOL=ON\ -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake\ -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2\ -DPYTHON_INCLUDE_DIR:FILEPATH=/usr/include/python2.7\ -DPYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.7.so\ -DPYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so\ -DVTK_RENDERING_BACKEND:STRING=OpenGL2\ -DModule_vtkRenderingLICOpenGL2:BOOL=ON I must have missed something since I guess that Paraview using parallel servers should run, even when there is only one GPU available. Any hints would be greatly appreciated. Best regards, Frank Albina _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 18 09:38:59 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 18 Dec 2015 09:38:59 -0500 Subject: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel In-Reply-To: <589CEB614006334D93C1A48C1B1964C9027CEAC02058@srvmes03.spe-ch-md9.net> References: <589CEB614006334D93C1A48C1B1964C9027CEAC0204E@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC02058@srvmes03.spe-ch-md9.net> Message-ID: Frank, Thanks for the info on where you got the code. Maybe there's a problem with the source packaging? I'll try out that download and see if I can reproduce the problem. Thanks, Cory On Fri, Dec 18, 2015 at 9:15 AM, Albina, Frank < frank.albina at sauber-motorsport.com> wrote: > Hi Cory! > > > > I have compiled the source code from the Paraview v5.0.0-RC2 source files > that I downloaded earlier this week from http://www.paraview.org/download/. > > No GIT repository there and none to be found in the top-level directory of > the source files. > > > > Paraview client & server are from the same build, since I am starting both > server and client from the same command line on the (Linux) workstation, > hence I am using the same environement. > > > > HTH, > > > Frank. > > > > *From:* Cory Quammen [mailto:cory.quammen at kitware.com] > *Sent:* Freitag, 18. Dezember 2015 15:08 > *To:* Albina, Frank > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend > failing to start in parallel > > > > Hi Frank, > > > > Since you said you recompiled ParaView, I suspect that maybe you forgot to > update the submodules ParaView uses. In the ParaView source tree, run > > > > git status > > > > If VTK is listed, it may say there are new commits available for VTK. To > update VTK, run > > > > git submodule update > > > > This has been an issue a few folks have encountered in the past. > > > > Also, double-check that your ParaView client and server are truly from the > same build. > > > > HTH, > > Cory > > > > On Fri, Dec 18, 2015 at 8:30 AM, Albina, Frank < > frank.albina at sauber-motorsport.com> wrote: > > Dear all! > > > > I recompiled Paraview-v5.0.0-rc2 from scratch using OpenMPI v1.6.5 and GCC > v4.7.2 on my workstation. > > The QT & Python versions are the default system versions and are resp. > 4.8.4 & 2.7.3. > > > > After successful compilation and installation, I start 8 parallel pvserver > instances with: > > mpirun ?np 8 pvserver ?sp=7436 > > > > Then, I start paraview and connect to the server running on the same > machine. After connection is established, paraview fails with a > segmentation fault. > > > > Waiting for client... > > Connection URL: cs://ws334:7436 > > Accepting connection(s): ws334:7436 > > Client connected. > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Parallel/Core/vtkSocketCommunicator.cxx, > line 809 > > vtkSocketCommunicator (0x2b7a600): Could not receive tag. 1 > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > [?] > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > -------------------------------------------------------------------------- > > mpirun noticed that process rank 0 with PID 13964 on node ws334 exited on > signal 11 (Segmentation fault). > > -------------------------------------------------------------------------- > > > > I have included hereafter how Paraview was compiled: > > cmake $sourceDir \ > > -DBUILD_SHARED_LIBS:BOOL=ON\ > > -DBUILD_TESTING:BOOL=OFF\ > > -DBUILD_DOCUMENTATION:BOOL=ON\ > > -DCMAKE_BUILD_TYPE:STRING=Release\ > > -DPARAVIEW_ENABLE_CATALYST:BOOL=ON\ > > -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ > > -DPARAVIEW_USE_MPI:BOOL=ON\ > > -DPARAVIEW_USE_UNIFIED_BINDINGS:BOOL=ON\ > > -DPARAVIEW_ENABLE_WEB:BOOL=ON\ > > -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF\ > > -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE\ > > -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ > > -DVTK_USE_OFFSCREEN:BOOL=OFF\ > > -DVTK_USE_X:BOOL=ON\ > > -DVTK_USE_QT=ON\ > > -DVTK_USE_DISPLAY=ON\ > > -DVTK_USE_GUI_SUPPORT:BOOL=ON\ > > -DPARAVIEW_BUILD_QT_GUI:BOOL=ON\ > > -DCMAKE_INSTALL_PREFIX:PATH=$installDir\ > > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON\ > > -DPYTHON_ENABLE_MODULE_MPIPython:BOOL=ON\ > > -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake\ > > -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2\ > > -DPYTHON_INCLUDE_DIR:FILEPATH=/usr/include/python2.7\ > > -DPYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.7.so\ > > -DPYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so\ > > -DVTK_RENDERING_BACKEND:STRING=OpenGL2\ > > -DModule_vtkRenderingLICOpenGL2:BOOL=ON > > > > I must have missed something since I guess that Paraview using parallel > servers should run, even when there is only one GPU available. Any hints > would be greatly appreciated. > > > > Best regards, > > > > *Frank Albina * > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank.albina at sauber-motorsport.com Fri Dec 18 10:00:22 2015 From: frank.albina at sauber-motorsport.com (Albina, Frank) Date: Fri, 18 Dec 2015 16:00:22 +0100 Subject: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC0204E@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC02058@srvmes03.spe-ch-md9.net> Message-ID: <589CEB614006334D93C1A48C1B1964C9027CEAC02061@srvmes03.spe-ch-md9.net> Hi Cory! Thank you very much for that. As said earlier in another post, I am very keen to see PV v5.0.0 release so I am happy to help and report issues before the new version gets unleashed. Cheers, Frank. From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Freitag, 18. Dezember 2015 15:39 To: Albina, Frank Cc: paraview at paraview.org Subject: Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel Frank, Thanks for the info on where you got the code. Maybe there's a problem with the source packaging? I'll try out that download and see if I can reproduce the problem. Thanks, Cory On Fri, Dec 18, 2015 at 9:15 AM, Albina, Frank > wrote: Hi Cory! I have compiled the source code from the Paraview v5.0.0-RC2 source files that I downloaded earlier this week from http://www.paraview.org/download/. No GIT repository there and none to be found in the top-level directory of the source files. Paraview client & server are from the same build, since I am starting both server and client from the same command line on the (Linux) workstation, hence I am using the same environement. HTH, Frank. From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Freitag, 18. Dezember 2015 15:08 To: Albina, Frank Cc: paraview at paraview.org Subject: Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel Hi Frank, Since you said you recompiled ParaView, I suspect that maybe you forgot to update the submodules ParaView uses. In the ParaView source tree, run git status If VTK is listed, it may say there are new commits available for VTK. To update VTK, run git submodule update This has been an issue a few folks have encountered in the past. Also, double-check that your ParaView client and server are truly from the same build. HTH, Cory On Fri, Dec 18, 2015 at 8:30 AM, Albina, Frank > wrote: Dear all! I recompiled Paraview-v5.0.0-rc2 from scratch using OpenMPI v1.6.5 and GCC v4.7.2 on my workstation. The QT & Python versions are the default system versions and are resp. 4.8.4 & 2.7.3. After successful compilation and installation, I start 8 parallel pvserver instances with: mpirun ?np 8 pvserver ?sp=7436 Then, I start paraview and connect to the server running on the same machine. After connection is established, paraview fails with a segmentation fault. Waiting for client... Connection URL: cs://ws334:7436 Accepting connection(s): ws334:7436 Client connected. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 809 vtkSocketCommunicator (0x2b7a600): Could not receive tag. 1 ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. [?] ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. ERROR: In /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. -------------------------------------------------------------------------- mpirun noticed that process rank 0 with PID 13964 on node ws334 exited on signal 11 (Segmentation fault). -------------------------------------------------------------------------- I have included hereafter how Paraview was compiled: cmake $sourceDir \ -DBUILD_SHARED_LIBS:BOOL=ON\ -DBUILD_TESTING:BOOL=OFF\ -DBUILD_DOCUMENTATION:BOOL=ON\ -DCMAKE_BUILD_TYPE:STRING=Release\ -DPARAVIEW_ENABLE_CATALYST:BOOL=ON\ -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ -DPARAVIEW_USE_MPI:BOOL=ON\ -DPARAVIEW_USE_UNIFIED_BINDINGS:BOOL=ON\ -DPARAVIEW_ENABLE_WEB:BOOL=ON\ -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF\ -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE\ -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ -DVTK_USE_OFFSCREEN:BOOL=OFF\ -DVTK_USE_X:BOOL=ON\ -DVTK_USE_QT=ON\ -DVTK_USE_DISPLAY=ON\ -DVTK_USE_GUI_SUPPORT:BOOL=ON\ -DPARAVIEW_BUILD_QT_GUI:BOOL=ON\ -DCMAKE_INSTALL_PREFIX:PATH=$installDir\ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON\ -DPYTHON_ENABLE_MODULE_MPIPython:BOOL=ON\ -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake\ -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2\ -DPYTHON_INCLUDE_DIR:FILEPATH=/usr/include/python2.7\ -DPYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.7.so\ -DPYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so\ -DVTK_RENDERING_BACKEND:STRING=OpenGL2\ -DModule_vtkRenderingLICOpenGL2:BOOL=ON I must have missed something since I guess that Paraview using parallel servers should run, even when there is only one GPU available. Any hints would be greatly appreciated. Best regards, Frank Albina _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen R&D Engineer Kitware, Inc. -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 18 10:02:09 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 18 Dec 2015 10:02:09 -0500 Subject: [Paraview] Selecting a point in Python In-Reply-To: <9c2561ccdb6e4849b424e20638aa6c08@ES01AMSNLNT.srn.sandia.gov> References: <9c2561ccdb6e4849b424e20638aa6c08@ES01AMSNLNT.srn.sandia.gov> Message-ID: HI Alan, Selections are indeed possible in Python, though as you have found they are not recorded in traces. You should be able to do something like this to select one or more points: can = GetActiveSource() # Extract the desired block first extractBlock = ExtractBlock(Input=can) extractBlock.BlockIndices = [2] # Now extract point 1764 pointID = 1764 pointIDs = [0, pointID] # process number, point ID selection = paraview.simple.IDSelectionSource(ContainingCells=0, FieldType = "POINT", IDs = pointIDs) plotSelectionOverTime1 = PlotSelectionOverTime(Input=can, Selection=selection) qcv = CreateView('QuartileChartView') d = Show(plotSelectionOverTime1, qcv) I hope this helps, Cory On Wed, Dec 9, 2015 at 7:29 PM, Scott, W Alan wrote: > I am trying to create a python script that will create a plot selection > over time. Here is what I am trying to do: > > ? Read in the can.exo. All vars on. Apply > > ? Select point on can. (This is the line that does not record in > the Trace Recorder, and I need). > > ? Plot selection over time (I can?t get here without the previous > step). > > > > How is a selection done in Python? > > > > Thanks, > > > > Alan > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Fri Dec 18 10:09:22 2015 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Fri, 18 Dec 2015 15:09:22 +0000 Subject: [Paraview] Coloring Exodus Nodesets in Programmable Filter Message-ID: All, I have a user who wants to programmatically color nodesets. I assume the PF is the ticket here. I can find the nodesets in the PF, but I don't understand how to color them. It seems this might be a display parameter rather than a nodeset parameter, but I'm unsure how to access the active RenderView from within the PF. I note that changing individual nset colors in the Multi-block Inspector is not recorded in a Trace, so that was no help. I saw an idea to setting element colors using SetScalars, but that doesn't seem to exist for the nodesets and frankly, I never understood how that worked. Ideas? Thanks Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 18 10:13:04 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 18 Dec 2015 10:13:04 -0500 Subject: [Paraview] Selecting a point in Python In-Reply-To: References: <9c2561ccdb6e4849b424e20638aa6c08@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, Oops, clicked 'Send' too fast. You don't really need the extract block part. Try this instead: can = GetActiveSource() pointID = 1764 pointIDs = [0, pointID] # process, id selection = IDSelectionSource(ContainingCells=0, FieldType = "POINT", IDs = pointIDs) plotSelectionOverTime1 = PlotSelectionOverTime(Input=extract, Selection=selection) qcv = CreateView('QuartileChartView') d = Show(plotSelectionOverTime1, qcv) Thanks, Cory On Fri, Dec 18, 2015 at 10:02 AM, Cory Quammen wrote: > HI Alan, > > Selections are indeed possible in Python, though as you have found they > are not recorded in traces. > > You should be able to do something like this to select one or more points: > > can = GetActiveSource() > > > # Extract the desired block first > > extractBlock = ExtractBlock(Input=can) > > extractBlock.BlockIndices = [2] > > > # Now extract point 1764 > > pointID = 1764 > > pointIDs = [0, pointID] # process number, point ID > > selection = paraview.simple.IDSelectionSource(ContainingCells=0, FieldType > = "POINT", IDs = pointIDs) > plotSelectionOverTime1 = PlotSelectionOverTime(Input=can, > Selection=selection) > > qcv = CreateView('QuartileChartView') > > d = Show(plotSelectionOverTime1, qcv) > > > I hope this helps, > > Cory > > > > On Wed, Dec 9, 2015 at 7:29 PM, Scott, W Alan wrote: > >> I am trying to create a python script that will create a plot selection >> over time. Here is what I am trying to do: >> >> ? Read in the can.exo. All vars on. Apply >> >> ? Select point on can. (This is the line that does not record in >> the Trace Recorder, and I need). >> >> ? Plot selection over time (I can?t get here without the >> previous step). >> >> >> >> How is a selection done in Python? >> >> >> >> Thanks, >> >> >> >> Alan >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.held at ni.com Fri Dec 18 10:41:12 2015 From: ben.held at ni.com (Ben Held) Date: Fri, 18 Dec 2015 15:41:12 +0000 Subject: [Paraview] Accessing plane properties (origin) for a custom filter including a slice filter Message-ID: I'm trying to create a customer filter that involves a slice filter. For simplicity, assume that's the only content in the custom filter. Why doesn't the properties step in the custom filter wizard allow me to expose parameters for the plane used in the slice? Thanks, Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Fri Dec 18 10:59:49 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 18 Dec 2015 10:59:49 -0500 Subject: [Paraview] Building paraview with piston -- enabling GPGPU support In-Reply-To: <9230853A36E499458AF5EAD38C13DCD5219CCC3D@SRV00048.soton.ac.uk> References: <9230853A36E499458AF5EAD38C13DCD5219CCC3D@SRV00048.soton.ac.uk> Message-ID: What you are seeing is that piston has evolved since the we wrote the vtk module that interfaces to it. I think the same is true of thrust evolving since piston 0.4. So, in order to make it work without modifying the code, you will need to use older versions. Instead of doing that, I recommend you look into vtk-m project instead. This is the successor to the since deprecated PISTON and DAX projects. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Dec 18, 2015 at 5:54 AM, Baker D.J. wrote: > Hello, > > > > I am trying to integrate GPGPU support in paraview v4.4.0. With that in > mind I have enabled ?PARAVIEW_USE_PISTON? in the cmake configurator, and > downloaded the Piston source code. The software that I?m using is? > > > > Paraview 4.4.0 > > Piston 0.4 > > Cuda toolkit 7.5.18 > > > > The make fails when compiling vtkPistonConverters.cu, and I cannot make > any progress to resolve my issues. In addition to a load of warnings I see > the following types of errors: > > > > piston/choose_container.h(42): error: namespace "thrust::detail" has no > member "default_device_space_tag" > > > > VTK/Accelerators/Piston/vtkPistonConverters.cu(93): error: expected a type > specifier (a couple) > > > > VTK/Accelerators/Piston/vtkPistonConverters.cu(36): error: too few > arguments for class template "piston::vtk_image3d" (several times) > > > > I?m not a C/C++ programmer and so this is a show stopper for me. I?ve > tried downloading the current VTK source, however that does not help. Could > anyone please advise on the source of these errors or alternatively advise > which combination of paraview/piston/cuda give a working solution. > > > > Best regards, > > > > David. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Fri Dec 18 11:40:01 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Fri, 18 Dec 2015 11:40:01 -0500 Subject: [Paraview] CFP - Eurographics 2016 Symposium on Parallel Graphics and Visualization (EGPGV 2016) Message-ID: [We aplogize if you receive multiple copies of this message.] Eurographics 2016 Symposium on Parallel Graphics and Visualization (EGPGV 2016) =============================================================================== June 6-7, 2016, Groningen, the Netherlands Co-located with EuroVis 2016 www.egpgv.org Call for Papers ================ The importance of parallel computing is increasing rapidly with the ubiquitous availability of multi-core CPUs, GPUs, and cluster systems. Computationally demanding and data-intensive applications in graphics and visualization are strongly affected by this trend and require novel efficient parallel solutions. The aim of this symposium is to foster the exchange of experiences and knowledge exploiting and defining new trends in parallel graphics and visualization. The proceedings of the EGPGV Symposium will be published in the Eurographics Proceedings Series and in the Eurographics Digital Library. Best papers from the EGPGV symposium will be invited to submit an extended journal version to IEEE Transactions on Visualization and Computer Graphics. Focusing on parallel computing, the symposium seeks papers on graphics and visualization techniques, data structures, algorithms, and systems for: - large-data - clusters - (multi-)GPU computing, and heterogeneous, hybrid architectures - out-of-core - hybrid distributed and shared memory architectures - grid and cloud environments In particular the symposium topics include: - computationally and data intensive rendering - scientific visualization (volume rendering, flow and tensor visualization) - information visualization and visual analytics - simulations for virtual environments (physics-based animation, collision detection, acoustics) - mesh processing, level-of-detail, and geometric methods - visual computing (image- and video-based rendering, image processing and exploitation, segmentation) - scheduling, memory management and data coherence - large and high resolution displays, virtual environments - scientific, engineering, and industrial applications Important Dates ================= Paper Submission: February 19, 2016 Author Notification: April 1, 2016 Camera-Ready papers: April 15, 2016 Symposium: June 6-7, 2016 Submission instructions ======================== You are invited to submit original and unpublished research works. Full papers are expected to be eight to ten (8-10) pages in length, with the final length appropriate to the contribution of the paper. Submissions are to be formatted along the Eurographics paper publication guidelines. We expect that the submissions will clearly discuss the novel and significant contributions as well as related work in the field. Authors must highlight how their contributions differ and advance the state of the art in parallel graphics and visualization. The full paper and all supplementary material must be submitted via the PCS online system. Additional submission details will be announced shortly on egpgv.org. Symposium Chair ================= Alexandru Telea, University of Groningen, the Netherlands Program Chairs =============== Wes Bethel, Lawrence Berkeley National Laboratory, USA Enrico Gobbetti, CRS4, Italy Program Committee ================== To be announced soon on the event's website (egpgv.org) -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Dec 18 12:57:11 2015 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 18 Dec 2015 17:57:11 +0000 Subject: [Paraview] [EXTERNAL] Re: Selecting a point in Python In-Reply-To: References: <9c2561ccdb6e4849b424e20638aa6c08@ES01AMSNLNT.srn.sandia.gov> Message-ID: <7338242de5284e7ebecd60efa6901864@ES01AMSNLNT.srn.sandia.gov> Excellent! Thanks. One more question ? is it possible to select the cell or point with a maximum value, as opposed to a hard coded cell or point? Alan From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Friday, December 18, 2015 8:02 AM To: Scott, W Alan Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] Selecting a point in Python HI Alan, Selections are indeed possible in Python, though as you have found they are not recorded in traces. You should be able to do something like this to select one or more points: can = GetActiveSource() # Extract the desired block first extractBlock = ExtractBlock(Input=can) extractBlock.BlockIndices = [2] # Now extract point 1764 pointID = 1764 pointIDs = [0, pointID] # process number, point ID selection = paraview.simple.IDSelectionSource(ContainingCells=0, FieldType = "POINT", IDs = pointIDs) plotSelectionOverTime1 = PlotSelectionOverTime(Input=can, Selection=selection) qcv = CreateView('QuartileChartView') d = Show(plotSelectionOverTime1, qcv) I hope this helps, Cory On Wed, Dec 9, 2015 at 7:29 PM, Scott, W Alan > wrote: I am trying to create a python script that will create a plot selection over time. Here is what I am trying to do: ? Read in the can.exo. All vars on. Apply ? Select point on can. (This is the line that does not record in the Trace Recorder, and I need). ? Plot selection over time (I can?t get here without the previous step). How is a selection done in Python? Thanks, Alan _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 18 14:19:34 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 18 Dec 2015 14:19:34 -0500 Subject: [Paraview] [EXTERNAL] Re: Selecting a point in Python In-Reply-To: <7338242de5284e7ebecd60efa6901864@ES01AMSNLNT.srn.sandia.gov> References: <9c2561ccdb6e4849b424e20638aa6c08@ES01AMSNLNT.srn.sandia.gov> <7338242de5284e7ebecd60efa6901864@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, Scrap what I said earlier. There is a simpler way. For selecting a point by ID, try: query = 'id == 1234' can = GetActiveSource() s = SelectPoints(query) plotSelectionOverTime = PlotSelectionOverTime(Input=can, Selection=s) view = CreateView('QuartileChartView') Show(plotSelectionOverTime, view) For selecting a point with the maximum value, change the query variable to: query = 'DISPL[0] == max(DISPL[0])' Thanks, Cory On Fri, Dec 18, 2015 at 12:57 PM, Scott, W Alan wrote: > Excellent! Thanks. > > > > One more question ? is it possible to select the cell or point with a > maximum value, as opposed to a hard coded cell or point? > > > > Alan > > > > *From:* Cory Quammen [mailto:cory.quammen at kitware.com] > *Sent:* Friday, December 18, 2015 8:02 AM > *To:* Scott, W Alan > *Cc:* paraview at paraview.org > *Subject:* [EXTERNAL] Re: [Paraview] Selecting a point in Python > > > > HI Alan, > > > > Selections are indeed possible in Python, though as you have found they > are not recorded in traces. > > > > You should be able to do something like this to select one or more points: > > > > can = GetActiveSource() > > > > # Extract the desired block first > > extractBlock = ExtractBlock(Input=can) > > extractBlock.BlockIndices = [2] > > > > # Now extract point 1764 > > pointID = 1764 > > pointIDs = [0, pointID] # process number, point ID > > selection = paraview.simple.IDSelectionSource(ContainingCells=0, FieldType > = "POINT", IDs = pointIDs) > > plotSelectionOverTime1 = PlotSelectionOverTime(Input=can, > Selection=selection) > > qcv = CreateView('QuartileChartView') > > d = Show(plotSelectionOverTime1, qcv) > > > > > > I hope this helps, > > Cory > > > > > > On Wed, Dec 9, 2015 at 7:29 PM, Scott, W Alan wrote: > > I am trying to create a python script that will create a plot selection > over time. Here is what I am trying to do: > > ? Read in the can.exo. All vars on. Apply > > ? Select point on can. (This is the line that does not record in > the Trace Recorder, and I need). > > ? Plot selection over time (I can?t get here without the previous > step). > > > > How is a selection done in Python? > > > > Thanks, > > > > Alan > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Fri Dec 18 14:52:27 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 18 Dec 2015 14:52:27 -0500 Subject: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel In-Reply-To: <589CEB614006334D93C1A48C1B1964C9027CEAC02061@srvmes03.spe-ch-md9.net> References: <589CEB614006334D93C1A48C1B1964C9027CEAC0204E@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC02058@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC02061@srvmes03.spe-ch-md9.net> Message-ID: Hi Frank, The official binaries of 5.0.0-RC1 on Mac work fine for me the way you tried. Everything works fine on the master branch as well However, when I build the same configuration as you for the 5.0.0-RC2 tar file on the downloads page of www.paraview.org on a Mac, I get a similar error and a crash in the client. Partial stack trace from the client: 0 org.python.python 0x0000000109b6a1b6 PyObject_Call + 23 1 org.python.python 0x0000000109be8e83 PyEval_CallObjectWithKeywords + 165 2 libvtkClientServer-pv5.0.1.dylib 0x000000010715c253 CommandFunctionCallback(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 3971 3 libvtkClientServer-pv5.0.1.dylib 0x000000010714600b vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 155 4 libvtkClientServer-pv5.0.1.dylib 0x000000010714493b vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 331 5 libvtkClientServer-pv5.0.1.dylib 0x0000000107143c45 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 741 6 libvtkClientServer-pv5.0.1.dylib 0x000000010714392d vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 45 7 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3c744 vtkSIProperty::ProcessMessage(vtkClientServerStream&) + 52 8 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3bf8e vtkSIVectorPropertyTemplate::Push(int*, int) + 654 9 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3ba1f vtkSIVectorPropertyTemplate::ReadXMLAttributes(vtkSIProxy*, vtkPVXMLElement*) + 271 10 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3eeb6 vtkSIProxy::ReadXMLProperty(vtkPVXMLElement*) + 742 11 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3e9ed vtkSIProxy::ReadXMLAttributes(vtkPVXMLElement*) + 797 12 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3e346 vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) + 2086 13 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3ce01 vtkSIProxy::Push(paraview_protobuf::Message*) + 33 14 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e248ec vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) + 2220 15 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e24ba6 vtkPVSessionCore::PushState(paraview_protobuf::Message*) + 262 16 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e220f6 vtkPVSessionBase::PushState(paraview_protobuf::Message*) + 38 17 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d2630a vtkSMSessionClient::PushState(paraview_protobuf::Message*) + 426 18 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d0040c vtkSMProxy::CreateVTKObjects() + 1276 19 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d42aab vtkSMSettingsProxy::CreateVTKObjects() + 27 20 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106cffa61 vtkSMProxy::UpdateVTKObjects() + 33 21 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106ceccc5 vtkSMParaViewPipelineController::PostInitializeProxy(vtkSMProxy*) + 517 22 libvtkPVServerManagerRendering-pv5.0.1.dylib 0x0000000109e288b3 vtkSMParaViewPipelineControllerWithRendering::PostInitializeProxy(vtkSMProxy*) + 51 23 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106cec898 vtkSMParaViewPipelineController::UpdateSettingsProxies(vtkSMSession*) + 296 24 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106ce9d74 vtkSMParaViewPipelineController::InitializeSession(vtkSMSession*) + 452 25 libvtkpqCore-pv5.0.1.dylib 0x0000000106688e5c pqServerManagerModel::onConnectionCreated(long long) + 636 On the server, I get ERROR: In /Users/cory.quammen/src/ParaView-v5.0.0-RC2-source/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 809 vtkSocketCommunicator (0x7fbc2a4e8930): Could not receive tag. 1 I'll check around to see what might be up with the source code packaging. Thanks for the report, Cory On Fri, Dec 18, 2015 at 10:00 AM, Albina, Frank < frank.albina at sauber-motorsport.com> wrote: > Hi Cory! > > Thank you very much for that. > > As said earlier in another post, I am very keen to see PV v5.0.0 release > so I am happy to help and report issues before the new version gets > unleashed. > > Cheers, > > Frank. > > *From:* Cory Quammen [mailto:cory.quammen at kitware.com] > *Sent:* Freitag, 18. Dezember 2015 15:39 > > *To:* Albina, Frank > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend > failing to start in parallel > > > > Frank, > > > > Thanks for the info on where you got the code. Maybe there's a problem > with the source packaging? I'll try out that download and see if I can > reproduce the problem. > > > > Thanks, > > Cory > > > > On Fri, Dec 18, 2015 at 9:15 AM, Albina, Frank < > frank.albina at sauber-motorsport.com> wrote: > > Hi Cory! > > > > I have compiled the source code from the Paraview v5.0.0-RC2 source files > that I downloaded earlier this week from http://www.paraview.org/download/. > > No GIT repository there and none to be found in the top-level directory of > the source files. > > > > Paraview client & server are from the same build, since I am starting both > server and client from the same command line on the (Linux) workstation, > hence I am using the same environement. > > > > HTH, > > > Frank. > > > > *From:* Cory Quammen [mailto:cory.quammen at kitware.com] > *Sent:* Freitag, 18. Dezember 2015 15:08 > *To:* Albina, Frank > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend > failing to start in parallel > > > > Hi Frank, > > > > Since you said you recompiled ParaView, I suspect that maybe you forgot to > update the submodules ParaView uses. In the ParaView source tree, run > > > > git status > > > > If VTK is listed, it may say there are new commits available for VTK. To > update VTK, run > > > > git submodule update > > > > This has been an issue a few folks have encountered in the past. > > > > Also, double-check that your ParaView client and server are truly from the > same build. > > > > HTH, > > Cory > > > > On Fri, Dec 18, 2015 at 8:30 AM, Albina, Frank < > frank.albina at sauber-motorsport.com> wrote: > > Dear all! > > > > I recompiled Paraview-v5.0.0-rc2 from scratch using OpenMPI v1.6.5 and GCC > v4.7.2 on my workstation. > > The QT & Python versions are the default system versions and are resp. > 4.8.4 & 2.7.3. > > > > After successful compilation and installation, I start 8 parallel pvserver > instances with: > > mpirun ?np 8 pvserver ?sp=7436 > > > > Then, I start paraview and connect to the server running on the same > machine. After connection is established, paraview fails with a > segmentation fault. > > > > Waiting for client... > > Connection URL: cs://ws334:7436 > > Accepting connection(s): ws334:7436 > > Client connected. > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Parallel/Core/vtkSocketCommunicator.cxx, > line 809 > > vtkSocketCommunicator (0x2b7a600): Could not receive tag. 1 > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > [?] > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > ERROR: In > /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, > line 572 > > vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. > > > > -------------------------------------------------------------------------- > > mpirun noticed that process rank 0 with PID 13964 on node ws334 exited on > signal 11 (Segmentation fault). > > -------------------------------------------------------------------------- > > > > I have included hereafter how Paraview was compiled: > > cmake $sourceDir \ > > -DBUILD_SHARED_LIBS:BOOL=ON\ > > -DBUILD_TESTING:BOOL=OFF\ > > -DBUILD_DOCUMENTATION:BOOL=ON\ > > -DCMAKE_BUILD_TYPE:STRING=Release\ > > -DPARAVIEW_ENABLE_CATALYST:BOOL=ON\ > > -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ > > -DPARAVIEW_USE_MPI:BOOL=ON\ > > -DPARAVIEW_USE_UNIFIED_BINDINGS:BOOL=ON\ > > -DPARAVIEW_ENABLE_WEB:BOOL=ON\ > > -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF\ > > -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE\ > > -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ > > -DVTK_USE_OFFSCREEN:BOOL=OFF\ > > -DVTK_USE_X:BOOL=ON\ > > -DVTK_USE_QT=ON\ > > -DVTK_USE_DISPLAY=ON\ > > -DVTK_USE_GUI_SUPPORT:BOOL=ON\ > > -DPARAVIEW_BUILD_QT_GUI:BOOL=ON\ > > -DCMAKE_INSTALL_PREFIX:PATH=$installDir\ > > -DPARAVIEW_ENABLE_PYTHON:BOOL=ON\ > > -DPYTHON_ENABLE_MODULE_MPIPython:BOOL=ON\ > > -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake\ > > -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2\ > > -DPYTHON_INCLUDE_DIR:FILEPATH=/usr/include/python2.7\ > > -DPYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.7.so\ > > -DPYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so\ > > -DVTK_RENDERING_BACKEND:STRING=OpenGL2\ > > -DModule_vtkRenderingLICOpenGL2:BOOL=ON > > > > I must have missed something since I guess that Paraview using parallel > servers should run, even when there is only one GPU available. Any hints > would be greatly appreciated. > > > > Best regards, > > > > *Frank Albina * > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > > Cory Quammen > R&D Engineer > Kitware, Inc. > > > > > > -- > > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From orion at cora.nwra.com Fri Dec 18 18:27:20 2015 From: orion at cora.nwra.com (Orion Poplawski) Date: Fri, 18 Dec 2015 16:27:20 -0700 Subject: [Paraview] rpath error when compiling ParaView 5.0 In-Reply-To: <56733349.4020606@gmail.com> References: <566332BD.2080008@gmail.com> <20151207163835.GA3080@megas.khq.kitware.com> <566C6335.2050609@gmail.com> <56733349.4020606@gmail.com> Message-ID: <56749658.2050307@cora.nwra.com> On 12/17/2015 03:12 PM, Armin Wehrfritz wrote: > Hi, > > as a follow up, I found that the error is related to this option: > PARAVIEW_INSTALL_DEVELOPMENT_FILES > > For some reason I had it switched on and by switching it off, I can > avoid the rpath error. Though I don't know why. > > I should probably note that for older build environments (cmake 3.0.2/ > gcc 4.8.3) this error does not appear. > > -Armin FWIW - Fedora builds of paraview enable this and I haven't seen any rpath issues. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion at nwra.com Boulder, CO 80301 http://www.nwra.com From cory.quammen at kitware.com Sat Dec 19 00:42:30 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Sat, 19 Dec 2015 00:42:30 -0500 Subject: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC0204E@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC02058@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC02061@srvmes03.spe-ch-md9.net> Message-ID: Frank, It does indeed look like there was a problem with the source code packaging. A fix has been merged into the packaging script: https://gitlab.kitware.com/paraview/paraview/merge_requests/541 Thanks for helping us find it by pointing out the problem. We'll get an updated tar file posted sometime soon. Cory On Fri, Dec 18, 2015 at 2:52 PM, Cory Quammen wrote: > Hi Frank, > > The official binaries of 5.0.0-RC1 on Mac work fine for me the way you > tried. Everything works fine on the master branch as well > > However, when I build the same configuration as you for the 5.0.0-RC2 tar > file on the downloads page of www.paraview.org on a Mac, I get a similar > error and a crash in the client. Partial stack trace from the client: > > 0 org.python.python 0x0000000109b6a1b6 PyObject_Call + 23 > 1 org.python.python 0x0000000109be8e83 > PyEval_CallObjectWithKeywords + 165 > 2 libvtkClientServer-pv5.0.1.dylib 0x000000010715c253 > CommandFunctionCallback(vtkClientServerInterpreter*, vtkObjectBase*, char > const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 3971 > 3 libvtkClientServer-pv5.0.1.dylib 0x000000010714600b > vtkClientServerInterpreter::CallCommandFunction(char const*, > vtkObjectBase*, char const*, vtkClientServerStream const&, > vtkClientServerStream&) + 155 > 4 libvtkClientServer-pv5.0.1.dylib 0x000000010714493b > vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream > const&, int) + 331 > 5 libvtkClientServer-pv5.0.1.dylib 0x0000000107143c45 > vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, > int) + 741 > 6 libvtkClientServer-pv5.0.1.dylib 0x000000010714392d > vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 45 > 7 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3c744 > vtkSIProperty::ProcessMessage(vtkClientServerStream&) + 52 > 8 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3bf8e > vtkSIVectorPropertyTemplate::Push(int*, int) + 654 > 9 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3ba1f > vtkSIVectorPropertyTemplate::ReadXMLAttributes(vtkSIProxy*, > vtkPVXMLElement*) + 271 > 10 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3eeb6 > vtkSIProxy::ReadXMLProperty(vtkPVXMLElement*) + 742 > 11 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3e9ed > vtkSIProxy::ReadXMLAttributes(vtkPVXMLElement*) + 797 > 12 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3e346 > vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) + 2086 > 13 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3ce01 > vtkSIProxy::Push(paraview_protobuf::Message*) + 33 > 14 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e248ec > vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) + 2220 > 15 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e24ba6 > vtkPVSessionCore::PushState(paraview_protobuf::Message*) + 262 > 16 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e220f6 > vtkPVSessionBase::PushState(paraview_protobuf::Message*) + 38 > 17 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d2630a > vtkSMSessionClient::PushState(paraview_protobuf::Message*) + 426 > 18 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d0040c > vtkSMProxy::CreateVTKObjects() + 1276 > 19 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d42aab > vtkSMSettingsProxy::CreateVTKObjects() + 27 > 20 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106cffa61 > vtkSMProxy::UpdateVTKObjects() + 33 > 21 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106ceccc5 > vtkSMParaViewPipelineController::PostInitializeProxy(vtkSMProxy*) + 517 > 22 libvtkPVServerManagerRendering-pv5.0.1.dylib 0x0000000109e288b3 > vtkSMParaViewPipelineControllerWithRendering::PostInitializeProxy(vtkSMProxy*) > + 51 > 23 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106cec898 > vtkSMParaViewPipelineController::UpdateSettingsProxies(vtkSMSession*) + 296 > 24 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106ce9d74 > vtkSMParaViewPipelineController::InitializeSession(vtkSMSession*) + 452 > 25 libvtkpqCore-pv5.0.1.dylib 0x0000000106688e5c > pqServerManagerModel::onConnectionCreated(long long) + 636 > > On the server, I get > > ERROR: In > /Users/cory.quammen/src/ParaView-v5.0.0-RC2-source/VTK/Parallel/Core/vtkSocketCommunicator.cxx, > line 809 > > vtkSocketCommunicator (0x7fbc2a4e8930): Could not receive tag. 1 > > I'll check around to see what might be up with the source code packaging. > > Thanks for the report, > Cory > > On Fri, Dec 18, 2015 at 10:00 AM, Albina, Frank < > frank.albina at sauber-motorsport.com> wrote: > >> Hi Cory! >> >> Thank you very much for that. >> >> As said earlier in another post, I am very keen to see PV v5.0.0 release >> so I am happy to help and report issues before the new version gets >> unleashed. >> >> Cheers, >> >> Frank. >> >> *From:* Cory Quammen [mailto:cory.quammen at kitware.com] >> *Sent:* Freitag, 18. Dezember 2015 15:39 >> >> *To:* Albina, Frank >> *Cc:* paraview at paraview.org >> *Subject:* Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend >> failing to start in parallel >> >> >> >> Frank, >> >> >> >> Thanks for the info on where you got the code. Maybe there's a problem >> with the source packaging? I'll try out that download and see if I can >> reproduce the problem. >> >> >> >> Thanks, >> >> Cory >> >> >> >> On Fri, Dec 18, 2015 at 9:15 AM, Albina, Frank < >> frank.albina at sauber-motorsport.com> wrote: >> >> Hi Cory! >> >> >> >> I have compiled the source code from the Paraview v5.0.0-RC2 source files >> that I downloaded earlier this week from >> http://www.paraview.org/download/. >> No GIT repository there and none to be found in the top-level directory >> of the source files. >> >> >> >> Paraview client & server are from the same build, since I am starting >> both server and client from the same command line on the (Linux) >> workstation, hence I am using the same environement. >> >> >> >> HTH, >> >> >> Frank. >> >> >> >> *From:* Cory Quammen [mailto:cory.quammen at kitware.com] >> *Sent:* Freitag, 18. Dezember 2015 15:08 >> *To:* Albina, Frank >> *Cc:* paraview at paraview.org >> *Subject:* Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend >> failing to start in parallel >> >> >> >> Hi Frank, >> >> >> >> Since you said you recompiled ParaView, I suspect that maybe you forgot >> to update the submodules ParaView uses. In the ParaView source tree, run >> >> >> >> git status >> >> >> >> If VTK is listed, it may say there are new commits available for VTK. To >> update VTK, run >> >> >> >> git submodule update >> >> >> >> This has been an issue a few folks have encountered in the past. >> >> >> >> Also, double-check that your ParaView client and server are truly from >> the same build. >> >> >> >> HTH, >> >> Cory >> >> >> >> On Fri, Dec 18, 2015 at 8:30 AM, Albina, Frank < >> frank.albina at sauber-motorsport.com> wrote: >> >> Dear all! >> >> >> >> I recompiled Paraview-v5.0.0-rc2 from scratch using OpenMPI v1.6.5 and >> GCC v4.7.2 on my workstation. >> >> The QT & Python versions are the default system versions and are resp. >> 4.8.4 & 2.7.3. >> >> >> >> After successful compilation and installation, I start 8 parallel >> pvserver instances with: >> >> mpirun ?np 8 pvserver ?sp=7436 >> >> >> >> Then, I start paraview and connect to the server running on the same >> machine. After connection is established, paraview fails with a >> segmentation fault. >> >> >> >> Waiting for client... >> >> Connection URL: cs://ws334:7436 >> >> Accepting connection(s): ws334:7436 >> >> Client connected. >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >> line 809 >> >> vtkSocketCommunicator (0x2b7a600): Could not receive tag. 1 >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> [?] >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> ERROR: In >> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >> line 572 >> >> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >> >> >> >> -------------------------------------------------------------------------- >> >> mpirun noticed that process rank 0 with PID 13964 on node ws334 exited on >> signal 11 (Segmentation fault). >> >> -------------------------------------------------------------------------- >> >> >> >> I have included hereafter how Paraview was compiled: >> >> cmake $sourceDir \ >> >> -DBUILD_SHARED_LIBS:BOOL=ON\ >> >> -DBUILD_TESTING:BOOL=OFF\ >> >> -DBUILD_DOCUMENTATION:BOOL=ON\ >> >> -DCMAKE_BUILD_TYPE:STRING=Release\ >> >> -DPARAVIEW_ENABLE_CATALYST:BOOL=ON\ >> >> -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ >> >> -DPARAVIEW_USE_MPI:BOOL=ON\ >> >> -DPARAVIEW_USE_UNIFIED_BINDINGS:BOOL=ON\ >> >> -DPARAVIEW_ENABLE_WEB:BOOL=ON\ >> >> -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF\ >> >> -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE\ >> >> -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ >> >> -DVTK_USE_OFFSCREEN:BOOL=OFF\ >> >> -DVTK_USE_X:BOOL=ON\ >> >> -DVTK_USE_QT=ON\ >> >> -DVTK_USE_DISPLAY=ON\ >> >> -DVTK_USE_GUI_SUPPORT:BOOL=ON\ >> >> -DPARAVIEW_BUILD_QT_GUI:BOOL=ON\ >> >> -DCMAKE_INSTALL_PREFIX:PATH=$installDir\ >> >> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON\ >> >> -DPYTHON_ENABLE_MODULE_MPIPython:BOOL=ON\ >> >> -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake\ >> >> -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2\ >> >> -DPYTHON_INCLUDE_DIR:FILEPATH=/usr/include/python2.7\ >> >> -DPYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.7.so\ >> >> -DPYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so\ >> >> -DVTK_RENDERING_BACKEND:STRING=OpenGL2\ >> >> -DModule_vtkRenderingLICOpenGL2:BOOL=ON >> >> >> >> I must have missed something since I guess that Paraview using parallel >> servers should run, even when there is only one GPU available. Any hints >> would be greatly appreciated. >> >> >> >> Best regards, >> >> >> >> *Frank Albina * >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> >> -- >> >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> >> >> >> >> >> -- >> >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikolays at buffalo.edu Sun Dec 20 08:58:22 2015 From: nikolays at buffalo.edu (Nikolay Simakov) Date: Sun, 20 Dec 2015 08:58:22 -0500 Subject: [Paraview] Problem with reading xdmf file Message-ID: <5676B3FE.50901@buffalo.edu> Hello, I am trying to create XDMF file to visualize data from hdf5 output from my program. The coordinates in hdf5 are stored as separate arrays. As first step I'd like to plot the nodes as points. So I made a simple xdmf file which mimics the data layout in my hdf5 file: 0 1 2 3 0.0 0.0 1.0 0.0 1.0 0.0 1.0 0.0 0.0 1.0 1.0 0.0 And when I use xdmf3 reader it paraview-4.4 or 5.0RC2 exit with sigmentation fault. I did try to use GeometryType="X_Y_Z" but it didn't work out too. In case of xdmf reader it did the job but generates following error message was: ERROR: In /home/kitware/Dashboards/buildbot/paraview-debian4dash-linux-shared-release_qt4_superbuild/source-paraview/VTK/IO/Xdmf2/vtkXdmfHeavyData.cxx, line 345 vtkXdmfReader (0x1da35d0): Cannot find DataItem element in geometry xml, no caching possible. Am I missing something? Thanks, Nikolay From denis.cohen at gmail.com Sun Dec 20 09:26:06 2015 From: denis.cohen at gmail.com (denis cohen) Date: Sun, 20 Dec 2015 15:26:06 +0100 Subject: [Paraview] Moving ColorBar in python script Message-ID: Hello, I am writing a script for pvbatch. I'd like to move the ScalrBar that show color legend from its default position (for me in the lower left). How can I do that in the script? Using trace when moving it in the gui does not show anything. Thanks Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Sun Dec 20 21:22:43 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Sun, 20 Dec 2015 21:22:43 -0500 Subject: [Paraview] Export animation breaks paraview after some files In-Reply-To: References: Message-ID: Hmm, no, you shouldn't have to install a runtime package before installing ParaView. Then again, I'm not sure how extensively we are testing Windows 10. Sorry I don't have anything more insightful to share. - Cory On Wed, Dec 16, 2015 at 3:31 AM, no name wrote: > Hi Cory > > Dependency Walker gives me all these files, which cannot be found. I > guess some runtime package has to be installed first maybe? > > API-MS-WIN-CORE-APIQUERY-L1-1-0.DLL > API-MS-WIN-CORE-APPCOMPAT-L1-1-1.DLL > API-MS-WIN-CORE-APPINIT-L1-1-0.DLL > API-MS-WIN-CORE-ATOMS-L1-1-0.DLL > API-MS-WIN-CORE-COM-L1-1-0 > API-MS-WIN-CORE-COM-L1-1-1.DLL > API-MS-WIN-CORE-COM-MIDLPROXYSTUB-L1-1-0.DLL > API-MS-WIN-CORE-COM-PRIVATE-L1-1-0.DLL > API-MS-WIN-CORE-COM-PRIVATE-L1-1-1.DLL > API-MS-WIN-CORE-COMM-L1-1-0.DLL > API-MS-WIN-CORE-CONSOLE-L2-1-0.DLL > API-MS-WIN-CORE-CRT-L1-1-0.DLL > API-MS-WIN-CORE-CRT-L2-1-0.DLL > API-MS-WIN-CORE-DATETIME-L1-1-1.DLL > API-MS-WIN-CORE-DATETIME-L1-1-2.DLL > API-MS-WIN-CORE-DEBUG-L1-1-1.DLL > API-MS-WIN-CORE-DELAYLOAD-L1-1-1.DLL > API-MS-WIN-CORE-ERRORHANDLING-L1-1-1.DLL > API-MS-WIN-CORE-ERRORHANDLING-L1-1-3.DLL > API-MS-WIN-CORE-FIBERS-L1-1-1.DLL > API-MS-WIN-CORE-FIBERS-L2-1-1.DLL > API-MS-WIN-CORE-FILE-L1-2-1.DLL > API-MS-WIN-CORE-FILE-L1-2-2.DLL > API-MS-WIN-CORE-FILE-L2-1-1.DLL > API-MS-WIN-CORE-FILE-L2-1-2.DLL > API-MS-WIN-CORE-HEAP-L1-2-0.DLL > API-MS-WIN-CORE-HEAP-L2-1-0.DLL > API-MS-WIN-CORE-HEAP-OBSOLETE-L1-1-0.DLL > API-MS-WIN-CORE-INTERLOCKED-L1-2-0.DLL > API-MS-WIN-CORE-IO-L1-1-1.DLL > API-MS-WIN-CORE-JOB-L1-1-0.DLL > API-MS-WIN-CORE-JOB-L2-1-0.DLL > API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-1.DLL > API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-3.DLL > API-MS-WIN-CORE-KERNEL32-PRIVATE-L1-1-1.DLL > API-MS-WIN-CORE-KERNEL32-PRIVATE-L1-1-2.DLL > API-MS-WIN-CORE-LIBRARYLOADER-L1-2-0.DLL > API-MS-WIN-CORE-LIBRARYLOADER-L1-2-1.DLL > API-MS-WIN-CORE-LIBRARYLOADER-L2-1-0.DLL > API-MS-WIN-CORE-LOCALIZATION-L1-2-1.DLL > API-MS-WIN-CORE-LOCALIZATION-L1-2-2.DLL > API-MS-WIN-CORE-LOCALIZATION-L2-1-0.DLL > API-MS-WIN-CORE-LOCALIZATION-OBSOLETE-L1-3-0.DLL > API-MS-WIN-CORE-LOCALIZATION-PRIVATE-L1-1-0.DLL > API-MS-WIN-CORE-MEMORY-L1-1-2.DLL > API-MS-WIN-CORE-NAMEDPIPE-L1-2-0.DLL > API-MS-WIN-CORE-NAMEDPIPE-L1-2-1.DLL > API-MS-WIN-CORE-NAMESPACE-L1-1-0.DLL > API-MS-WIN-CORE-NORMALIZATION-L1-1-0.DLL > API-MS-WIN-CORE-PATH-L1-1-0.DLL > API-MS-WIN-CORE-PERFCOUNTERS-L1-1-0.DLL > API-MS-WIN-CORE-PRIVATEPROFILE-L1-1-1.DLL > API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-2-0.DLL > API-MS-WIN-CORE-PROCESSSNAPSHOT-L1-1-0.DLL > API-MS-WIN-CORE-PROCESSTHREADS-L1-1-2.DLL > API-MS-WIN-CORE-PROCESSTHREADS-L1-1-3.DLL > API-MS-WIN-CORE-PROCESSTOPOLOGY-L1-2-0.DLL > API-MS-WIN-CORE-PSAPI-ANSI-L1-1-0.DLL > API-MS-WIN-CORE-PSAPI-L1-1-0.DLL > API-MS-WIN-CORE-PSAPI-OBSOLETE-L1-1-0.DLL > API-MS-WIN-CORE-PSM-KEY-L1-1-0.DLL > API-MS-WIN-CORE-QUIRKS-L1-1-0.DLL > API-MS-WIN-CORE-REALTIME-L1-1-0.DLL > API-MS-WIN-CORE-REGISTRY-L1-1-0.DLL > API-MS-WIN-CORE-REGISTRY-L1-1-1.DLL > API-MS-WIN-CORE-REGISTRY-L2-2-0.DLL > API-MS-WIN-CORE-REGISTRYUSERSPECIFIC-L1-1-0.DLL > API-MS-WIN-CORE-RTLSUPPORT-L1-2-0.DLL > API-MS-WIN-CORE-SHLWAPI-LEGACY-L1-1-0.DLL > API-MS-WIN-CORE-SHLWAPI-OBSOLETE-L1-2-0.DLL > API-MS-WIN-CORE-SIDEBYSIDE-L1-1-0.DLL > API-MS-WIN-CORE-STRING-L2-1-0.DLL > API-MS-WIN-CORE-STRING-L2-1-1.DLL > API-MS-WIN-CORE-STRING-OBSOLETE-L1-1-0.DLL > API-MS-WIN-CORE-STRINGANSI-L1-1-0.DLL > API-MS-WIN-CORE-SYNCH-L1-2-1.DLL > API-MS-WIN-CORE-SYSINFO-L1-2-1.DLL > API-MS-WIN-CORE-SYSINFO-L1-2-3.DLL > API-MS-WIN-CORE-SYSTEMTOPOLOGY-L1-1-0.DLL > API-MS-WIN-CORE-THREADPOOL-L1-2-0.DLL > API-MS-WIN-CORE-THREADPOOL-LEGACY-L1-1-0.DLL > API-MS-WIN-CORE-THREADPOOL-PRIVATE-L1-1-0.DLL > API-MS-WIN-CORE-URL-L1-1-0.DLL > API-MS-WIN-CORE-VERSION-L1-1-0.DLL > API-MS-WIN-CORE-VERSIONANSI-L1-1-0.DLL > API-MS-WIN-CORE-WINDOWSERRORREPORTING-L1-1-0.DLL > API-MS-WIN-CORE-WINRT-ERROR-L1-1-1.DLL > API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL > API-MS-WIN-CORE-WOW64-L1-1-0.DLL > API-MS-WIN-CORE-WOW64-L1-1-1.DLL > API-MS-WIN-CORE-XSTATE-L2-1-0.DLL > API-MS-WIN-DEVICES-CONFIG-L1-1-1.DLL > API-MS-WIN-DEVICES-QUERY-L1-1-1.DLL > API-MS-WIN-EVENTING-CLASSICPROVIDER-L1-1-0.DLL > API-MS-WIN-EVENTING-CONSUMER-L1-1-0.DLL > API-MS-WIN-EVENTING-CONTROLLER-L1-1-0.DLL > API-MS-WIN-EVENTING-OBSOLETE-L1-1-0.DLL > API-MS-WIN-EVENTING-PROVIDER-L1-1-0.DLL > API-MS-WIN-MM-JOYSTICK-L1-1-0.DLL > API-MS-WIN-MM-MISC-L1-1-1.DLL > API-MS-WIN-MM-MME-L1-1-0.DLL > API-MS-WIN-MM-TIME-L1-1-0.DLL > API-MS-WIN-SECURITY-ACTIVEDIRECTORYCLIENT-L1-1-0.DLL > API-MS-WIN-SECURITY-APPCONTAINER-L1-1-0.DLL > API-MS-WIN-SECURITY-AUDIT-L1-1-1.DLL > API-MS-WIN-SECURITY-BASE-L1-2-0.DLL > API-MS-WIN-SECURITY-BASE-PRIVATE-L1-1-1.DLL > API-MS-WIN-SECURITY-GROUPPOLICY-L1-1-0.DLL > API-MS-WIN-SECURITY-LSALOOKUP-L1-1-1.DLL > API-MS-WIN-SECURITY-LSAPOLICY-L1-1-0.DLL > API-MS-WIN-SECURITY-SDDL-L1-1-0.DLL > API-MS-WIN-SERVICE-CORE-L1-1-1.DLL > API-MS-WIN-SERVICE-CORE-L1-1-2.DLL > API-MS-WIN-SERVICE-MANAGEMENT-L1-1-0.DLL > API-MS-WIN-SERVICE-MANAGEMENT-L2-1-0.DLL > API-MS-WIN-SERVICE-PRIVATE-L1-1-0 > API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL > API-MS-WIN-SERVICE-WINSVC-L1-2-0.DLL > API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL > API-MS-WIN-SHELL-SHELLCOM-L1-1-0.DLL > API-MS-WIN-SHELL-SHELLFOLDERS-L1-1-0.DLL > API-MS-WIN-STORAGE-EXPORTS-EXTERNAL-L1-1-0.DLL > API-MS-WIN-STORAGE-EXPORTS-INTERNAL-L1-1-0.DLL > API-MS-WIN-APPMODEL-IDENTITY-L1-2-0.DLL > API-MS-WIN-APPMODEL-RUNTIME-INTERNAL-L1-1-0.DLL > API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL > API-MS-WIN-APPMODEL-RUNTIME-L1-1-1.DLL > API-MS-WIN-APPMODEL-STATE-L1-2-0.DLL > API-MS-WIN-APPMODEL-UNLOCK-L1-1-0.DLL > API-MS-WIN-BASE-UTIL-L1-1-0.DLL > API-MS-WIN-CORE-CALENDAR-L1-1-0.DLL > API-MS-WIN-CORE-COM-L2-1-1.DLL > API-MS-WIN-CORE-DELAYLOAD-L1-1-0.DLL > API-MS-WIN-CORE-FIBERS-L1-1-0.DLL > API-MS-WIN-CORE-IO-L1-1-0.DLL > API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-0.DLL > API-MS-WIN-CORE-LOCALIZATION-L1-1-0.DLL > API-MS-WIN-CORE-LOCALIZATION-OBSOLETE-L1-2-0.DLL > API-MS-WIN-CORE-LOCALREGISTRY-L1-1-0.DLL > API-MS-WIN-CORE-MARSHAL-L1-1-0.DLL > API-MS-WIN-CORE-MISC-L1-1-0.DLL > API-MS-WIN-CORE-PROCESSTOPOLOGY-OBSOLETE-L1-1-0.DLL > API-MS-WIN-CORE-PSM-APPNOTIFY-L1-1-0.DLL > API-MS-WIN-CORE-REALTIME-L1-1-1.DLL > API-MS-WIN-CORE-REGISTRY-PRIVATE-L1-1-0.DLL > API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL > API-MS-WIN-CORE-SYSINFO-L1-2-0.DLL > API-MS-WIN-CORE-TOOLHELP-L1-1-0.DLL > API-MS-WIN-CORE-VERSION-L1-1-1.DLL > API-MS-WIN-CORE-VERSION-PRIVATE-L1-1-0.DLL > API-MS-WIN-CORE-VERSIONANSI-L1-1-1.DLL > API-MS-WIN-CORE-WINRT-ERRORPRIVATE-L1-1-1.DLL > API-MS-WIN-CORE-WINRT-L1-1-0.DLL > API-MS-WIN-CORE-WINRT-PROPERTYSETPRIVATE-L1-1-0.DLL > API-MS-WIN-CORE-WINRT-PROPERTYSETPRIVATE-L1-1-1.DLL > API-MS-WIN-CORE-WINRT-REGISTRATION-L1-1-0.DLL > API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL > API-MS-WIN-COREUI-SECRUNTIME-L1-1-0.DLL > API-MS-WIN-DOWNLEVEL-ADVAPI32-L1-1-0.DLL > API-MS-WIN-DOWNLEVEL-ADVAPI32-L2-1-0.DLL > API-MS-WIN-DOWNLEVEL-NORMALIZ-L1-1-0.DLL > API-MS-WIN-DOWNLEVEL-OLE32-L1-1-0.DLL > API-MS-WIN-DOWNLEVEL-SHELL32-L1-1-0.DLL > API-MS-WIN-DOWNLEVEL-SHLWAPI-L1-1-0.DLL > API-MS-WIN-DOWNLEVEL-SHLWAPI-L2-1-0.DLL > API-MS-WIN-DOWNLEVEL-SHLWAPI-L2-1-1.DLL > API-MS-WIN-DOWNLEVEL-USER32-L1-1-0.DLL > API-MS-WIN-DOWNLEVEL-VERSION-L1-1-0.DLL > API-MS-WIN-DX-D3DKMT-L1-1-0.DLL > API-MS-WIN-EVENTING-LEGACY-L1-1-0.DLL > API-MS-WIN-EVENTLOG-LEGACY-L1-1-0.DLL > API-MS-WIN-GDI-DPIINFO-L1-1-0.DLL > API-MS-WIN-MM-MISC-L2-1-0.DLL > API-MS-WIN-NTUSER-IE-MESSAGE-L1-1-0.DLL > API-MS-WIN-NTUSER-SYSPARAMS-L1-1-0.DLL > API-MS-WIN-OLE32-IE-L1-1-0.DLL > API-MS-WIN-POWER-BASE-L1-1-0.DLL > API-MS-WIN-POWER-SETTING-L1-1-0.DLL > API-MS-WIN-RTCORE-NTUSER-CLIPBOARD-L1-1-0.DLL > API-MS-WIN-RTCORE-NTUSER-PRIVATE-L1-1-0.DLL > API-MS-WIN-RTCORE-NTUSER-PRIVATE-L1-1-1.DLL > API-MS-WIN-RTCORE-NTUSER-SYNCH-L1-1-0.DLL > API-MS-WIN-RTCORE-NTUSER-WINDOW-L1-1-0.DLL > API-MS-WIN-RTCORE-NTUSER-WINEVENT-L1-1-0.DLL > API-MS-WIN-SECURITY-ACCESSHLPR-L1-1-0.DLL > API-MS-WIN-SECURITY-ACTIVEDIRECTORYCLIENT-L1-1-1.DLL > API-MS-WIN-SECURITY-BASE-L1-1-0.DLL > API-MS-WIN-SECURITY-CAPABILITY-L1-1-0.DLL > API-MS-WIN-SECURITY-CREDENTIALS-L1-1-0.DLL > API-MS-WIN-SECURITY-CREDENTIALS-L2-1-0.DLL > API-MS-WIN-SECURITY-CRYPTOAPI-L1-1-0.DLL > API-MS-WIN-SECURITY-LSALOOKUP-L1-1-2.DLL > API-MS-WIN-SECURITY-LSALOOKUP-L2-1-1.DLL > API-MS-WIN-SECURITY-PROVIDER-L1-1-0.DLL > API-MS-WIN-SECURITY-SDDLPARSECOND-L1-1-0.DLL > API-MS-WIN-SERVICE-WINSVC-L1-1-0.DLL > API-MS-WIN-SHCORE-COMHELPERS-L1-1-0.DLL > API-MS-WIN-SHCORE-OBSOLETE-L1-1-0.DLL > API-MS-WIN-SHCORE-REGISTRY-L1-1-1.DLL > API-MS-WIN-SHCORE-STREAM-L1-1-0.DLL > API-MS-WIN-SHCORE-STREAM-WINRT-L1-1-0.DLL > API-MS-WIN-SHCORE-SYSINFO-L1-1-0.DLL > API-MS-WIN-SHCORE-THREAD-L1-1-0.DLL > API-MS-WIN-SHCORE-UNICODEANSI-L1-1-0.DLL > API-MS-WIN-SHLWAPI-IE-L1-1-0.DLL > API-MS-WIN-SHLWAPI-WINRT-STORAGE-L1-1-1.DLL > EMCLIENT.DLL > EXT-MS-MF-PAL-L2-1-0.DLL > EXT-MS-ONECORE-APPCHROMEAPI-L1-1-0.DLL > EXT-MS-ONECORE-APPMODEL-VEVENTDISPATCHER-L1-1-0.DLL > EXT-MS-ONECORE-DCOMP-L1-1-0.DLL > EXT-MS-ONECORE-ORIENTATION-L1-1-0.DLL > EXT-MS-ONECORE-PHONEINFO-L1-1-0.DLL > EXT-MS-ONECORE-SHELLCHROMEAPI-L1-1-1.DLL > EXT-MS-WIN-ADVAPI32-EVENTINGCONTROLLER-L1-1-0.DLL > EXT-MS-WIN-ADVAPI32-MSI-L1-1-0.DLL > EXT-MS-WIN-ADVAPI32-NPUSERNAME-L1-1-0.DLL > EXT-MS-WIN-ADVAPI32-NTMARTA-L1-1-0.DLL > EXT-MS-WIN-ADVAPI32-PSM-APP-L1-1-0.DLL > EXT-MS-WIN-ADVAPI32-REGISTRY-L1-1-0.DLL > EXT-MS-WIN-ADVAPI32-SAFER-L1-1-0.DLL > EXT-MS-WIN-APPCOMPAT-APPHELP-L1-1-0.DLL > EXT-MS-WIN-APPMODEL-APPCONTAINERPATH-L1-1-0.DLL > EXT-MS-WIN-APPMODEL-DEPLOYMENT-L1-1-1.DLL > EXT-MS-WIN-APPMODEL-STATE-EXT-L1-2-0.DLL > EXT-MS-WIN-APPMODEL-USERCONTEXT-L1-1-0.DLL > EXT-MS-WIN-APPXDEPLOYMENTCLIENT-APPXDEPLOY-L1-1-0.DLL > EXT-MS-WIN-APPXDEPLOYMENTCLIENT-APPXDEPLOYONECORE-L1-1-0.DLL > EXT-MS-WIN-AUDIOCORE-PAL-L1-1-0.DLL > EXT-MS-WIN-AUTHZ-CONTEXT-L1-1-0.DLL > EXT-MS-WIN-AUTHZ-REMOTE-L1-1-0.DLL > EXT-MS-WIN-COM-CLBCATQ-L1-1-0.DLL > EXT-MS-WIN-COM-COML2-L1-1-1.DLL > EXT-MS-WIN-COM-OLE32-L1-1-1.DLL > EXT-MS-WIN-COM-OLE32-L1-1-3.DLL > EXT-MS-WIN-COM-PSMREGISTER-L1-1-0.DLL > EXT-MS-WIN-COM-SUSPENDRESILIENCY-L1-1-0.DLL > EXT-MS-WIN-CORE-WINRT-REMOTE-L1-1-0.DLL > EXT-MS-WIN-DEVMGMT-POLICY-L1-1-0.DLL > EXT-MS-WIN-DOMAINJOIN-NETJOIN-L1-1-0.DLL > EXT-MS-WIN-DWMAPIDXGI-EXT-L1-1-0.DLL > EXT-MS-WIN-EDPUTIL-POLICY-L1-1-0.DLL > EXT-MS-WIN-FAMILYSAFETY-CHILDACCOUNT-L1-1-0.DLL > EXT-MS-WIN-FECLIENT-ENCRYPTEDFILE-L1-1-0.DLL > EXT-MS-WIN-FIREWALLAPI-WEBPROXY-L1-1-0.DLL > EXT-MS-WIN-GDI-DC-CREATE-L1-1-1.DLL > EXT-MS-WIN-GDI-DC-L1-2-0.DLL > EXT-MS-WIN-GDI-DEVCAPS-L1-1-0.DLL > EXT-MS-WIN-GDI-DRAW-L1-1-1.DLL > EXT-MS-WIN-GDI-DRAW-L1-1-2.DLL > EXT-MS-WIN-GDI-FONT-L1-1-1.DLL > EXT-MS-WIN-GDI-FONT-L1-1-2.DLL > EXT-MS-WIN-GDI-METAFILE-L1-1-1.DLL > EXT-MS-WIN-GDI-PATH-L1-1-0.DLL > EXT-MS-WIN-GDI-RENDER-L1-1-0.DLL > EXT-MS-WIN-GPAPI-GROUPPOLICY-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-APPCOMPAT-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-DATETIME-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-ERRORHANDLING-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-FILE-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-LOCALIZATION-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-PACKAGE-CURRENT-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-PACKAGE-L1-1-1.DLL > EXT-MS-WIN-KERNEL32-QUIRKS-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-QUIRKS-L1-1-1.DLL > EXT-MS-WIN-KERNEL32-REGISTRY-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-SIDEBYSIDE-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-WINDOWSERRORREPORTING-L1-1-0.DLL > EXT-MS-WIN-KERNEL32-WINDOWSERRORREPORTING-L1-1-1.DLL > EXT-MS-WIN-KERNELBASE-PROCESSTHREAD-L1-1-0.DLL > EXT-MS-WIN-MININPUT-INPUTHOST-L1-1-0.DLL > EXT-MS-WIN-MPR-MULTIPLEPROVIDERROUTER-L1-1-0.DLL > EXT-MS-WIN-MRMCORER-ENVIRONMENT-L1-1-0.DLL > EXT-MS-WIN-MRMCORER-RESMANAGER-L1-1-0.DLL > EXT-MS-WIN-NTDSAPI-ACTIVEDIRECTORYCLIENT-L1-1-0.DLL > EXT-MS-WIN-NTDSAPI-ACTIVEDIRECTORYCLIENT-L1-1-1.DLL > EXT-MS-WIN-NTUSER-DC-ACCESS-EXT-L1-1-0.DLL > EXT-MS-WIN-NTUSER-DIALOGBOX-L1-1-1.DLL > EXT-MS-WIN-NTUSER-DIALOGBOX-L1-1-2.DLL > EXT-MS-WIN-NTUSER-DRAW-L1-1-1.DLL > EXT-MS-WIN-NTUSER-DRAW-L1-1-2.DLL > EXT-MS-WIN-NTUSER-GUI-L1-3-0.DLL > EXT-MS-WIN-NTUSER-KEYBOARD-L1-1-1.DLL > EXT-MS-WIN-NTUSER-KEYBOARD-L1-2-0.DLL > EXT-MS-WIN-NTUSER-MENU-L1-1-2.DLL > EXT-MS-WIN-NTUSER-MESSAGE-L1-1-1.DLL > EXT-MS-WIN-NTUSER-MESSAGE-L1-1-2.DLL > EXT-MS-WIN-NTUSER-MISC-L1-3-0.DLL > EXT-MS-WIN-NTUSER-MISC-L1-5-0.DLL > EXT-MS-WIN-NTUSER-MOUSE-L1-1-0.DLL > EXT-MS-WIN-NTUSER-PRIVATE-L1-2-0.DLL > EXT-MS-WIN-NTUSER-RECTANGLE-EXT-L1-1-0.DLL > EXT-MS-WIN-NTUSER-ROTATIONMANAGER-L1-1-0.DLL > EXT-MS-WIN-NTUSER-STRING-L1-1-0.DLL > EXT-MS-WIN-NTUSER-SYNCH-L1-1-0.DLL > EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL > EXT-MS-WIN-NTUSER-WINDOW-L1-1-1.DLL > EXT-MS-WIN-NTUSER-WINDOW-L1-1-3.DLL > EXT-MS-WIN-NTUSER-WINDOWCLASS-L1-1-1.DLL > EXT-MS-WIN-NTUSER-WINDOWSTATION-L1-1-1.DLL > EXT-MS-WIN-OLE32-BINDCTX-L1-1-0.DLL > EXT-MS-WIN-OLE32-IE-EXT-L1-1-0.DLL > EXT-MS-WIN-OLE32-OLEAUTOMATION-L1-1-0.DLL > EXT-MS-WIN-PROFILE-EXTENDER-L1-1-0.DLL > EXT-MS-WIN-PROFILE-LOAD-L1-1-0.DLL > EXT-MS-WIN-PROFILE-USERENV-L1-1-0.DLL > EXT-MS-WIN-PROFILE-USERENV-L1-1-1.DLL > EXT-MS-WIN-RPC-SSL-L1-1-0.DLL > EXT-MS-WIN-RTCORE-GDI-DEVCAPS-L1-1-0.DLL > EXT-MS-WIN-RTCORE-GDI-OBJECT-L1-1-0.DLL > EXT-MS-WIN-RTCORE-GDI-RGN-L1-1-0.DLL > EXT-MS-WIN-RTCORE-GDI-RGN-L1-1-1.DLL > EXT-MS-WIN-RTCORE-MINUSER-PRIVATE-EXT-L1-1-0.DLL > EXT-MS-WIN-RTCORE-NTUSER-CURSOR-L1-1-0.DLL > EXT-MS-WIN-RTCORE-NTUSER-DC-ACCESS-L1-1-0.DLL > EXT-MS-WIN-RTCORE-NTUSER-DPI-L1-1-0.DLL > EXT-MS-WIN-RTCORE-NTUSER-IAM-L1-1-0.DLL > EXT-MS-WIN-RTCORE-NTUSER-INTEGRATION-L1-1-0.DLL > EXT-MS-WIN-RTCORE-NTUSER-SYNCH-EXT-L1-1-0.DLL > EXT-MS-WIN-RTCORE-NTUSER-SYSCOLORS-L1-1-0.DLL > EXT-MS-WIN-RTCORE-NTUSER-SYSPARAMS-L1-1-0.DLL > EXT-MS-WIN-RTCORE-NTUSER-WINDOW-EXT-L1-1-0.DLL > EXT-MS-WIN-SECUR32-TRANSLATENAME-L1-1-0.DLL > EXT-MS-WIN-SECURITY-CAPAUTHZ-L1-1-0.DLL > EXT-MS-WIN-SECURITY-CHAMBERS-L1-1-0.DLL > EXT-MS-WIN-SECURITY-CREDUI-L1-1-0.DLL > EXT-MS-WIN-SECURITY-EFS-L1-1-0.DLL > EXT-MS-WIN-SESSION-USERMGR-L1-1-0.DLL > EXT-MS-WIN-SESSION-USERTOKEN-L1-1-0.DLL > EXT-MS-WIN-SESSION-WINSTA-L1-1-0.DLL > EXT-MS-WIN-SESSION-WTSAPI32-L1-1-0.DLL > EXT-MS-WIN-SETUPAPI-INF-L1-1-0.DLL > EXT-MS-WIN-SHELL-DIRECTORY-L1-1-0.DLL > EXT-MS-WIN-SHELL-PROPSYS-L1-1-0.DLL > EXT-MS-WIN-SHELL-SHELL32-L1-2-0.DLL > EXT-MS-WIN-SHELL-SHLWAPI-L1-1-0.DLL > EXT-MS-WIN-SHELL32-SHELLCOM-L1-1-0.DLL > EXT-MS-WIN-SXS-OLEAUTOMATION-L1-1-0.DLL > EXT-MS-WIN-UI-VIEWMANAGEMENT-L1-1-0.DLL > EXT-MS-WIN-USP10-L1-1-0.DLL > EXT-MS-WIN-WER-UI-L1-1-0.DLL > EXT-MS-WIN-WER-XBOX-L1-1-0.DLL > EXT-MS-WIN-WINRT-STORAGE-L1-1-0.DLL > EXT-MS-WIN-WLAN-ONEXUI-L1-1-0.DLL > IESHIMS.DLL > > Hop that helps a little bit. > > Richard > > On 16 December 2015 at 09:26, no name wrote: > > Hey Cory > > > > I cannot run paraview -dr > > I see the startupscreen, then an output window (with nothing in it) > > and then "Paraview stopped working". I run wind10x64. > > > > Thanks > > Richard > > > > On 14 December 2015 at 16:38, Cory Quammen > wrote: > >> Richard, > >> > >> Can you specify what system you are running? > >> > >> Usually the most informative way to see what is going on is to run it > >> through a debugger like gdb and lldb. This should at least get you a > stack > >> trace which will help us identify where it is failing. If you are on > >> Windows, there may be a dialog that pops up with some information. > >> > >> You could try running from the command line with the -dr option, e.g. > >> > >> paraview -dr > >> > >> This will disable any options or settings that may be causing problems. > If > >> ParaView runs with that option, then the solution is likely to be to > clear > >> your settings files. > >> > >> HTH, > >> Cory > >> > >> On Mon, Dec 14, 2015 at 3:41 AM, no name > >> wrote: > >>> > >>> Hi Cory > >>> > >>> Thanks for the help, but unfortunately Paraview 5.0 RC1 wont run on my > >>> system at all, it crashes on startup :( Do you know where I can find > >>> some logs, maybe I can get it working? > >>> > >>> Thanks > >>> Richard > >>> > >>> On 11 December 2015 at 15:14, Cory Quammen > >>> wrote: > >>> > Hi Richard, > >>> > > >>> > Could you try this with ParaView 5.0 Release Candidate 1 (RC1) and > >>> > report > >>> > whether you see the same thing? > >>> > > >>> > Thanks, > >>> > Cory > >>> > > >>> > On Fri, Dec 11, 2015 at 8:25 AM, no name < > keinepostnurmuell at gmail.com> > >>> > wrote: > >>> >> > >>> >> What I do: > >>> >> > >>> >> Open multiple INP files, run them through a pipeline. > >>> >> Export them as PNG (same error when I do it as a OVG...) via Save > >>> >> Animation. > >>> >> > >>> >> How does it look: > >>> >> Right now I have a renderview on the left side and a spreadsheetview > >>> >> on the right side. Usually after about 30-110 steps the label of > the y > >>> >> axis of the spread sheet view goes 10 pixels to the right or so and > >>> >> the renderview object disappears completely. Lets say I exported 10 > >>> >> PNGs and after the 8th its broken. > >>> >> > >>> >> When I then go back in the paraview main window after the animation > >>> >> made the renderview go south and click for example on the 5th input > >>> >> file, I also don't see anything in the render view. Even if I try to > >>> >> load a new INP in that renderview I stell don't see anything. > >>> >> > >>> >> Using paraview 4.4 on Win10 x64 > >>> >> > >>> >> I did not attach images, as I don't know if that comes through the > >>> >> mailing list :( > >>> >> > >>> >> Thanks for your help > >>> >> Richard > >>> >> _______________________________________________ > >>> >> Powered by www.kitware.com > >>> >> > >>> >> Visit other Kitware open-source projects at > >>> >> http://www.kitware.com/opensource/opensource.html > >>> >> > >>> >> Please keep messages on-topic and check the ParaView Wiki at: > >>> >> http://paraview.org/Wiki/ParaView > >>> >> > >>> >> Search the list archives at: http://markmail.org/search/?q=ParaView > >>> >> > >>> >> Follow this link to subscribe/unsubscribe: > >>> >> http://public.kitware.com/mailman/listinfo/paraview > >>> > > >>> > > >>> > > >>> > > >>> > -- > >>> > Cory Quammen > >>> > R&D Engineer > >>> > Kitware, Inc. > >> > >> > >> > >> > >> -- > >> Cory Quammen > >> R&D Engineer > >> Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wideli at hotmail.com Mon Dec 21 06:49:28 2015 From: wideli at hotmail.com (wide li) Date: Mon, 21 Dec 2015 11:49:28 +0000 Subject: [Paraview] Paraview crash when loading xdmf with HDF5 data Message-ID: Hi there, I am new to paraview. At the moment, I am trying to utilize the xdmf and HDF5 data in paraview. What I have is very strange. When the HDF5 is small, say the number of sampling points in each direction is less that 100, paraview works perfectly. But when the resolution is above this value, the paraview crashes immediately. The same problem occurs when I use the binary executable for mac. So, could anyone give me some hint where to look at this problem? The paraview-5.00-RC1 is compiled and installed on my MAC (EI Capitan). The parameters setup is as follows. The qt4 is installed via macport. The HDF5 and MPICH are compiled and installed without problem. Thanks very much in advance Li BUILD_DOCUMENTATION OFF BUILD_EXAMPLES OFF BUILD_SHARED_LIBS ON BUILD_TESTING ON BUILD_USER_DEFINED_LIBS OFF CMAKE_BUILD_TYPE Debug CTEST_TEST_TIMEOUT 3600 GMVReader_GMVREAD_LIB_DIR /Users/Li/Documents/Source/ParaView/ParaView-v5.0.0-RC1-source/Utilities/VisItBridg/databases/GMV GMVReader_SKIP_DATARANGE_CALCU OFF MACOSX_APP_INSTALL_PREFIX /Applications MPI_C_INCLUDE_PATH /usr/local/include MPI_C_LIBRARIES /usr/local/lib/libmpi.dylib;/usr/local/lib/lib/libpmpi.dylib PARAVIEW_BUILD_QT_GUI ON PARAVIEW_ENABLE_CATALYST ON PARAVIEW_ENABLE_FFMPEG ON PARAVIEW_ENABLE_PYTHON ON PARAVIEW_ENABLE_XDMF3 OFF PARAVIEW_INSTALL_DEVELOPMENT_F OFF PARAVIEW_PLUGIN_LOADER_PATHS PARAVIEW_USE_DAX OFF PARAVIEW_USE_MPI ON PARAVIEW_USE_PISTON OFF PARAVIEW_USE_UNIFIED_BINDINGS OFF PARAVIEW_USE_VISITBRIDGE OFF RMANTREE RMANTREE-NOTFOUND SURFACELIC_PLUGIN_TESTING ON VTK_ANDROID_BUILD OFF VTK_EGL_DEVICE_INDEX 0 VTK_IOS_BUILD OFF VTK_PYTHON_VERSION 2 VTK_QT_VERSION 4 VTK_RENDERING_BACKEND OpenGL VTK_SMP_IMPLEMENTATION_TYPE Sequential VTK_USE_LARGE_DATA ON VTK_USE_SYSTEM_GLEW OFF XDMF_USE_BZIP2 OFF XDMF_USE_GZIP OFF -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Dec 21 08:55:56 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 21 Dec 2015 08:55:56 -0500 Subject: [Paraview] Paraview crash when loading xdmf with HDF5 data In-Reply-To: References: Message-ID: Li, When ParaView crashes, could you share the error that is reported window that comes up? This will provide a stack trace that can help someone on the list debug the error. Thank you, Cory On Mon, Dec 21, 2015 at 6:49 AM, wide li wrote: > Hi there, > > I am new to paraview. > > At the moment, I am trying to utilize the xdmf and HDF5 data in paraview. > What I have is very strange. When the HDF5 is small, say the number of > sampling points in each direction is less that 100, paraview works > perfectly. But when the resolution is above this value, the paraview > crashes immediately. The same problem occurs when I use the binary > executable for mac. > > So, could anyone give me some hint where to look at this problem? > > The paraview-5.00-RC1 is compiled and installed on my MAC (EI Capitan). > The parameters setup is as follows. > The qt4 is installed via macport. The HDF5 and MPICH are compiled and > installed without problem. > > > Thanks very much in advance > > Li > > > > BUILD_DOCUMENTATION > OFF > BUILD_EXAMPLES > OFF > BUILD_SHARED_LIBS > ON > BUILD_TESTING ON > BUILD_USER_DEFINED_LIBS OFF > CMAKE_BUILD_TYPE Debug > CTEST_TEST_TIMEOUT 3600 > GMVReader_GMVREAD_LIB_DIR > /Users/Li/Documents/Source/ParaView/ParaView-v5.0.0-RC1-source/Utilities/VisItBridg/databases/GMV > GMVReader_SKIP_DATARANGE_CALCU > OFF > MACOSX_APP_INSTALL_PREFIX > /Applications > MPI_C_INCLUDE_PATH > /usr/local/include > MPI_C_LIBRARIES > /usr/local/lib/libmpi.dylib;/usr/local/lib/lib/libpmpi.dylib > PARAVIEW_BUILD_QT_GUI > ON > PARAVIEW_ENABLE_CATALYST > ON > PARAVIEW_ENABLE_FFMPEG > ON > PARAVIEW_ENABLE_PYTHON > ON > PARAVIEW_ENABLE_XDMF3 > OFF > PARAVIEW_INSTALL_DEVELOPMENT_F > OFF > PARAVIEW_PLUGIN_LOADER_PATHS > > PARAVIEW_USE_DAX > OFF > PARAVIEW_USE_MPI > ON > PARAVIEW_USE_PISTON > OFF > PARAVIEW_USE_UNIFIED_BINDINGS OFF > PARAVIEW_USE_VISITBRIDGE > OFF > RMANTREE > RMANTREE-NOTFOUND > SURFACELIC_PLUGIN_TESTING > ON > VTK_ANDROID_BUILD > OFF > VTK_EGL_DEVICE_INDEX > 0 > VTK_IOS_BUILD > OFF > VTK_PYTHON_VERSION > 2 > VTK_QT_VERSION > 4 > VTK_RENDERING_BACKEND > OpenGL > VTK_SMP_IMPLEMENTATION_TYPE > Sequential > VTK_USE_LARGE_DATA > ON > VTK_USE_SYSTEM_GLEW > OFF > XDMF_USE_BZIP2 > OFF > XDMF_USE_GZIP OFF > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Mon Dec 21 09:13:13 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 21 Dec 2015 09:13:13 -0500 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC0201B@srvmes03.spe-ch-md9.net> Message-ID: Utkarsh, This is great news! few inline comments: On Thu, Dec 17, 2015 at 1:05 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Frank, > > First of all, thanks for all your exhausting testing, it's greatly > appreciated! > > * OSMesa and MESA_GL_VERSION_OVERRIDE > > Communicating with the Mesa team, we learnt that > MESA_GL_VERSION_OVERRIDE is a bad idea since it doesnt' really create > the specified OpenGL context. Thus if anything tries to use features > from the specific OpenGL version, the rendering would crash and burn. > Working with Brian Paul from the Mesa team, Ken recently pushed a fix > to VTK (after the RC2) that uses new OSMesa API to create the correct > OpenGL context. This new OSMesa API will appear in Mesa 11.2, however. > Earlier version can be patched using the "alpha" patch that Brian > provided us (attached). > Does this patch cleanly applies to all previous version of Mesa or only 11.1 release? I am assuming that this patch existing in their current master? > > * Classic v/s llvm > > Your observation is indeed correct. llvmpipe is the way to go for > software rendering. On my builds, classic mesa was painstakingly slow > for rendering even small geometries. > > * Issues with LIC > > Another correct observation. There are a few regressions in the new > implementation for SurfaceLIC. Realistically, we may not be able to > address these before the 5.0 release. If you're using SurfaceLIC > heavily, I'd suggest building ParaView 5.0 with the older OpenGL > backend (or sticking with 4.4) for the interim. > > * OSMesa + SWR > > While currently I am not sure openswr+osmesa builds are possible, I > wouldn't be surprised if that on the roadmap. I am going to try to > contact the OpenSWR team to see if they have any thoughts on that. > > Utkarsh > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Dec 21 10:03:28 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 21 Dec 2015 10:03:28 -0500 Subject: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend failing to start in parallel In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC0204E@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC02058@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC02061@srvmes03.spe-ch-md9.net> Message-ID: Frank, Upon further review, the source code turns out to be fine. There is likely an issue with the unified python bindings. I've posted a bug report here: http://www.paraview.org/Bug/view.php?id=15896 Cory On Sat, Dec 19, 2015 at 12:42 AM, Cory Quammen wrote: > Frank, > > It does indeed look like there was a problem with the source code > packaging. > > A fix has been merged into the packaging script: > > https://gitlab.kitware.com/paraview/paraview/merge_requests/541 > > Thanks for helping us find it by pointing out the problem. We'll get an > updated tar file posted sometime soon. > > Cory > > On Fri, Dec 18, 2015 at 2:52 PM, Cory Quammen > wrote: > >> Hi Frank, >> >> The official binaries of 5.0.0-RC1 on Mac work fine for me the way you >> tried. Everything works fine on the master branch as well >> >> However, when I build the same configuration as you for the 5.0.0-RC2 tar >> file on the downloads page of www.paraview.org on a Mac, I get a similar >> error and a crash in the client. Partial stack trace from the client: >> >> 0 org.python.python 0x0000000109b6a1b6 PyObject_Call + 23 >> 1 org.python.python 0x0000000109be8e83 >> PyEval_CallObjectWithKeywords + 165 >> 2 libvtkClientServer-pv5.0.1.dylib 0x000000010715c253 >> CommandFunctionCallback(vtkClientServerInterpreter*, vtkObjectBase*, char >> const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 3971 >> 3 libvtkClientServer-pv5.0.1.dylib 0x000000010714600b >> vtkClientServerInterpreter::CallCommandFunction(char const*, >> vtkObjectBase*, char const*, vtkClientServerStream const&, >> vtkClientServerStream&) + 155 >> 4 libvtkClientServer-pv5.0.1.dylib 0x000000010714493b >> vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream >> const&, int) + 331 >> 5 libvtkClientServer-pv5.0.1.dylib 0x0000000107143c45 >> vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, >> int) + 741 >> 6 libvtkClientServer-pv5.0.1.dylib 0x000000010714392d >> vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 45 >> 7 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3c744 >> vtkSIProperty::ProcessMessage(vtkClientServerStream&) + 52 >> 8 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3bf8e >> vtkSIVectorPropertyTemplate::Push(int*, int) + 654 >> 9 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3ba1f >> vtkSIVectorPropertyTemplate::ReadXMLAttributes(vtkSIProxy*, >> vtkPVXMLElement*) + 271 >> 10 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3eeb6 >> vtkSIProxy::ReadXMLProperty(vtkPVXMLElement*) + 742 >> 11 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3e9ed >> vtkSIProxy::ReadXMLAttributes(vtkPVXMLElement*) + 797 >> 12 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3e346 >> vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) + 2086 >> 13 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e3ce01 >> vtkSIProxy::Push(paraview_protobuf::Message*) + 33 >> 14 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e248ec >> vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) + 2220 >> 15 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e24ba6 >> vtkPVSessionCore::PushState(paraview_protobuf::Message*) + 262 >> 16 libvtkPVServerImplementationCore-pv5.0.1.dylib 0x0000000106e220f6 >> vtkPVSessionBase::PushState(paraview_protobuf::Message*) + 38 >> 17 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d2630a >> vtkSMSessionClient::PushState(paraview_protobuf::Message*) + 426 >> 18 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d0040c >> vtkSMProxy::CreateVTKObjects() + 1276 >> 19 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106d42aab >> vtkSMSettingsProxy::CreateVTKObjects() + 27 >> 20 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106cffa61 >> vtkSMProxy::UpdateVTKObjects() + 33 >> 21 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106ceccc5 >> vtkSMParaViewPipelineController::PostInitializeProxy(vtkSMProxy*) + 517 >> 22 libvtkPVServerManagerRendering-pv5.0.1.dylib 0x0000000109e288b3 >> vtkSMParaViewPipelineControllerWithRendering::PostInitializeProxy(vtkSMProxy*) >> + 51 >> 23 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106cec898 >> vtkSMParaViewPipelineController::UpdateSettingsProxies(vtkSMSession*) + 296 >> 24 libvtkPVServerManagerCore-pv5.0.1.dylib 0x0000000106ce9d74 >> vtkSMParaViewPipelineController::InitializeSession(vtkSMSession*) + 452 >> 25 libvtkpqCore-pv5.0.1.dylib 0x0000000106688e5c >> pqServerManagerModel::onConnectionCreated(long long) + 636 >> >> On the server, I get >> >> ERROR: In >> /Users/cory.quammen/src/ParaView-v5.0.0-RC2-source/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >> line 809 >> >> vtkSocketCommunicator (0x7fbc2a4e8930): Could not receive tag. 1 >> >> I'll check around to see what might be up with the source code packaging. >> >> Thanks for the report, >> Cory >> >> On Fri, Dec 18, 2015 at 10:00 AM, Albina, Frank < >> frank.albina at sauber-motorsport.com> wrote: >> >>> Hi Cory! >>> >>> Thank you very much for that. >>> >>> As said earlier in another post, I am very keen to see PV v5.0.0 release >>> so I am happy to help and report issues before the new version gets >>> unleashed. >>> >>> Cheers, >>> >>> Frank. >>> >>> *From:* Cory Quammen [mailto:cory.quammen at kitware.com] >>> *Sent:* Freitag, 18. Dezember 2015 15:39 >>> >>> *To:* Albina, Frank >>> *Cc:* paraview at paraview.org >>> *Subject:* Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend >>> failing to start in parallel >>> >>> >>> >>> Frank, >>> >>> >>> >>> Thanks for the info on where you got the code. Maybe there's a problem >>> with the source packaging? I'll try out that download and see if I can >>> reproduce the problem. >>> >>> >>> >>> Thanks, >>> >>> Cory >>> >>> >>> >>> On Fri, Dec 18, 2015 at 9:15 AM, Albina, Frank < >>> frank.albina at sauber-motorsport.com> wrote: >>> >>> Hi Cory! >>> >>> >>> >>> I have compiled the source code from the Paraview v5.0.0-RC2 source >>> files that I downloaded earlier this week from >>> http://www.paraview.org/download/. >>> No GIT repository there and none to be found in the top-level directory >>> of the source files. >>> >>> >>> >>> Paraview client & server are from the same build, since I am starting >>> both server and client from the same command line on the (Linux) >>> workstation, hence I am using the same environement. >>> >>> >>> >>> HTH, >>> >>> >>> Frank. >>> >>> >>> >>> *From:* Cory Quammen [mailto:cory.quammen at kitware.com] >>> *Sent:* Freitag, 18. Dezember 2015 15:08 >>> *To:* Albina, Frank >>> *Cc:* paraview at paraview.org >>> *Subject:* Re: [Paraview] Paraview v5.0.0-rc2 with OpenGL2 backend >>> failing to start in parallel >>> >>> >>> >>> Hi Frank, >>> >>> >>> >>> Since you said you recompiled ParaView, I suspect that maybe you forgot >>> to update the submodules ParaView uses. In the ParaView source tree, run >>> >>> >>> >>> git status >>> >>> >>> >>> If VTK is listed, it may say there are new commits available for VTK. To >>> update VTK, run >>> >>> >>> >>> git submodule update >>> >>> >>> >>> This has been an issue a few folks have encountered in the past. >>> >>> >>> >>> Also, double-check that your ParaView client and server are truly from >>> the same build. >>> >>> >>> >>> HTH, >>> >>> Cory >>> >>> >>> >>> On Fri, Dec 18, 2015 at 8:30 AM, Albina, Frank < >>> frank.albina at sauber-motorsport.com> wrote: >>> >>> Dear all! >>> >>> >>> >>> I recompiled Paraview-v5.0.0-rc2 from scratch using OpenMPI v1.6.5 and >>> GCC v4.7.2 on my workstation. >>> >>> The QT & Python versions are the default system versions and are resp. >>> 4.8.4 & 2.7.3. >>> >>> >>> >>> After successful compilation and installation, I start 8 parallel >>> pvserver instances with: >>> >>> mpirun ?np 8 pvserver ?sp=7436 >>> >>> >>> >>> Then, I start paraview and connect to the server running on the same >>> machine. After connection is established, paraview fails with a >>> segmentation fault. >>> >>> >>> >>> Waiting for client... >>> >>> Connection URL: cs://ws334:7436 >>> >>> Accepting connection(s): ws334:7436 >>> >>> Client connected. >>> >>> ERROR: In >>> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >>> line 809 >>> >>> vtkSocketCommunicator (0x2b7a600): Could not receive tag. 1 >>> >>> >>> >>> ERROR: In >>> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >>> line 572 >>> >>> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >>> >>> >>> >>> ERROR: In >>> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >>> line 572 >>> >>> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >>> >>> >>> >>> ERROR: In >>> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >>> line 572 >>> >>> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >>> >>> >>> >>> ERROR: In >>> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >>> line 572 >>> >>> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >>> >>> >>> >>> ERROR: In >>> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >>> line 572 >>> >>> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >>> >>> [?] >>> >>> ERROR: In >>> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >>> line 572 >>> >>> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >>> >>> >>> >>> ERROR: In >>> /cfdcode/opensuse12/opt/ParaView/SRC/paraview-5.0.0-rc2/VTK/Common/System/vtkSocket.cxx, >>> line 572 >>> >>> vtkClientSocket (0x293e940): Socket error in call to send. Broken pipe. >>> >>> >>> >>> >>> -------------------------------------------------------------------------- >>> >>> mpirun noticed that process rank 0 with PID 13964 on node ws334 exited >>> on signal 11 (Segmentation fault). >>> >>> >>> -------------------------------------------------------------------------- >>> >>> >>> >>> I have included hereafter how Paraview was compiled: >>> >>> cmake $sourceDir \ >>> >>> -DBUILD_SHARED_LIBS:BOOL=ON\ >>> >>> -DBUILD_TESTING:BOOL=OFF\ >>> >>> -DBUILD_DOCUMENTATION:BOOL=ON\ >>> >>> -DCMAKE_BUILD_TYPE:STRING=Release\ >>> >>> -DPARAVIEW_ENABLE_CATALYST:BOOL=ON\ >>> >>> -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ >>> >>> -DPARAVIEW_USE_MPI:BOOL=ON\ >>> >>> -DPARAVIEW_USE_UNIFIED_BINDINGS:BOOL=ON\ >>> >>> -DPARAVIEW_ENABLE_WEB:BOOL=ON\ >>> >>> -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF\ >>> >>> -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE\ >>> >>> -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ >>> >>> -DVTK_USE_OFFSCREEN:BOOL=OFF\ >>> >>> -DVTK_USE_X:BOOL=ON\ >>> >>> -DVTK_USE_QT=ON\ >>> >>> -DVTK_USE_DISPLAY=ON\ >>> >>> -DVTK_USE_GUI_SUPPORT:BOOL=ON\ >>> >>> -DPARAVIEW_BUILD_QT_GUI:BOOL=ON\ >>> >>> -DCMAKE_INSTALL_PREFIX:PATH=$installDir\ >>> >>> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON\ >>> >>> -DPYTHON_ENABLE_MODULE_MPIPython:BOOL=ON\ >>> >>> -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake\ >>> >>> -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2\ >>> >>> -DPYTHON_INCLUDE_DIR:FILEPATH=/usr/include/python2.7\ >>> >>> -DPYTHON_LIBRARY:FILEPATH=/usr/lib64/libpython2.7.so\ >>> >>> -DPYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so\ >>> >>> -DVTK_RENDERING_BACKEND:STRING=OpenGL2\ >>> >>> -DModule_vtkRenderingLICOpenGL2:BOOL=ON >>> >>> >>> >>> I must have missed something since I guess that Paraview using parallel >>> servers should run, even when there is only one GPU available. Any hints >>> would be greatly appreciated. >>> >>> >>> >>> Best regards, >>> >>> >>> >>> *Frank Albina * >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >>> >>> >>> -- >>> >>> Cory Quammen >>> R&D Engineer >>> Kitware, Inc. >>> >>> >>> >>> >>> >>> -- >>> >>> Cory Quammen >>> R&D Engineer >>> Kitware, Inc. >>> >> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From D.J.Baker at soton.ac.uk Mon Dec 21 11:15:21 2015 From: D.J.Baker at soton.ac.uk (Baker D.J.) Date: Mon, 21 Dec 2015 16:15:21 +0000 Subject: [Paraview] Building paraview with piston -- enabling GPGPU support In-Reply-To: References: <9230853A36E499458AF5EAD38C13DCD5219CCC3D@SRV00048.soton.ac.uk> Message-ID: <9230853A36E499458AF5EAD38C13DCD5219CE6A2@SRV00048.soton.ac.uk> Hello David, Thank you for this advice. I?m currently looking in to the vtk-m project, and I?ll see how I get on. Could you please tell me if it?s possible to integrate vtk-m and paraview in any way? For example using a plugin. Best regards, David. From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Friday, December 18, 2015 4:00 PM To: Baker D.J. Cc: paraview at paraview.org Subject: Re: [Paraview] Building paraview with piston -- enabling GPGPU support What you are seeing is that piston has evolved since the we wrote the vtk module that interfaces to it. I think the same is true of thrust evolving since piston 0.4. So, in order to make it work without modifying the code, you will need to use older versions. Instead of doing that, I recommend you look into vtk-m project instead. This is the successor to the since deprecated PISTON and DAX projects. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Dec 18, 2015 at 5:54 AM, Baker D.J. > wrote: Hello, I am trying to integrate GPGPU support in paraview v4.4.0. With that in mind I have enabled ?PARAVIEW_USE_PISTON? in the cmake configurator, and downloaded the Piston source code. The software that I?m using is? Paraview 4.4.0 Piston 0.4 Cuda toolkit 7.5.18 The make fails when compiling vtkPistonConverters.cu, and I cannot make any progress to resolve my issues. In addition to a load of warnings I see the following types of errors: piston/choose_container.h(42): error: namespace "thrust::detail" has no member "default_device_space_tag" VTK/Accelerators/Piston/vtkPistonConverters.cu(93): error: expected a type specifier (a couple) VTK/Accelerators/Piston/vtkPistonConverters.cu(36): error: too few arguments for class template "piston::vtk_image3d" (several times) I?m not a C/C++ programmer and so this is a show stopper for me. I?ve tried downloading the current VTK source, however that does not help. Could anyone please advise on the source of these errors or alternatively advise which combination of paraview/piston/cuda give a working solution. Best regards, David. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Dec 21 11:33:37 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 21 Dec 2015 11:33:37 -0500 Subject: [Paraview] Any objections to dropping 32 bit WIndows binaries? In-Reply-To: References: Message-ID: Since there were no objections voiced, we'll drop distributing 32-bit Windows binaries for ParaView 5.0. Thanks Utkarsh On Wed, Dec 16, 2015 at 4:20 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Folks, > > I am trying to see if there are any objections to dropping 32 bit > Windows binaries for the 5.0 release. We'll still distribute the 64 > bit Windows binaries. > > Thanks > Utkarsh > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hahnse at ornl.gov Mon Dec 21 15:56:16 2015 From: hahnse at ornl.gov (Hahn, Steven E.) Date: Mon, 21 Dec 2015 20:56:16 +0000 Subject: [Paraview] VTK warning during volume rendering of vtkStructuredGrid on Windows with Nvidia graphics card. Message-ID: I tried viewing the volume representation of a small vtkStructuredGrid file with ParaView v5.0.0-RC2 built with the OpenGL2 rendering backend and get this warning: Warning: In C:\Sources\ParaView-v5.0.0-RC1-source\VTK\Rendering\VolumeOpenGL2\vtkOpenGL ProjectedTetrahedraMapper.cxx, line 251 vtkOpenGLProjectedTetrahedraMapper (00000000061B0AD0): Missing FBO support. The algorithm may produce visual artifacts. Updating the video card (Nvidia Quadro K6000) driver to the latest version (354.56) had no effect. Volume rendering with a different vtkImageData file generated no warnings. Best, Steven Hahn From aashish.chaudhary at kitware.com Mon Dec 21 16:02:05 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 21 Dec 2015 16:02:05 -0500 Subject: [Paraview] VTK warning during volume rendering of vtkStructuredGrid on Windows with Nvidia graphics card. In-Reply-To: References: Message-ID: On Mon, Dec 21, 2015 at 3:56 PM, Hahn, Steven E. wrote: > I tried viewing the volume representation of a small vtkStructuredGrid > file with ParaView v5.0.0-RC2 built with the OpenGL2 rendering backend and > get this warning: > > Warning: In > C:\Sources\ParaView-v5.0.0-RC1-source\VTK\Rendering\VolumeOpenGL2\vtkOpenGL > ProjectedTetrahedraMapper.cxx, line 251 > vtkOpenGLProjectedTetrahedraMapper (00000000061B0AD0): Missing FBO > support. The algorithm may produce visual artifacts. > > Updating the video card (Nvidia Quadro K6000) driver to the latest version > (354.56) had no effect. Volume rendering with a different vtkImageData > file generated no warnings. > They are using different mappers. I am surprised that you are reported missing fbo support. Which windows Platform is this? - Aashish > > Best, > Steven Hahn > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Mon Dec 21 16:03:55 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 21 Dec 2015 16:03:55 -0500 Subject: [Paraview] VTK warning during volume rendering of vtkStructuredGrid on Windows with Nvidia graphics card. In-Reply-To: References: Message-ID: Hi Steven, Also, can you install and run glview ( http://www.realtech-vr.com/glview/download.php) on your system to see if FBO support exists? Thanks, Aashish On Mon, Dec 21, 2015 at 4:02 PM, Aashish Chaudhary < aashish.chaudhary at kitware.com> wrote: > > On Mon, Dec 21, 2015 at 3:56 PM, Hahn, Steven E. wrote: > >> I tried viewing the volume representation of a small vtkStructuredGrid >> file with ParaView v5.0.0-RC2 built with the OpenGL2 rendering backend and >> get this warning: >> >> Warning: In >> >> C:\Sources\ParaView-v5.0.0-RC1-source\VTK\Rendering\VolumeOpenGL2\vtkOpenGL >> ProjectedTetrahedraMapper.cxx, line 251 >> vtkOpenGLProjectedTetrahedraMapper (00000000061B0AD0): Missing FBO >> support. The algorithm may produce visual artifacts. >> >> Updating the video card (Nvidia Quadro K6000) driver to the latest version >> (354.56) had no effect. Volume rendering with a different vtkImageData >> file generated no warnings. >> > > > They are using different mappers. I am surprised that you are reported > missing fbo support. Which windows Platform is this? > > - Aashish > > >> >> Best, >> Steven Hahn >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. * > *| http://www.kitware.com/company/team/chaudhary.html > * > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From hahnse at ornl.gov Mon Dec 21 17:07:16 2015 From: hahnse at ornl.gov (Hahn, Steven E.) Date: Mon, 21 Dec 2015 22:07:16 +0000 Subject: [Paraview] VTK warning during volume rendering of vtkStructuredGrid on Windows with Nvidia graphics card. In-Reply-To: References: , Message-ID: <1450735636346.93209@ornl.gov> Hi Aashish, This machine is running Windows 7. I built Paraview v5.0.0-RC2 with Visual Studio 2015. GLview does list GL_ARB_framebuffer_object as supported. Are there any other specific features in the report that I should check? Best, Steven ________________________________ From: Aashish Chaudhary Sent: Monday, December 21, 2015 4:03 PM To: Hahn, Steven E. Cc: ParaView Subject: Re: [Paraview] VTK warning during volume rendering of vtkStructuredGrid on Windows with Nvidia graphics card. Hi Steven, Also, can you install and run glview (http://www.realtech-vr.com/glview/download.php) on your system to see if FBO support exists? Thanks, Aashish On Mon, Dec 21, 2015 at 4:02 PM, Aashish Chaudhary > wrote: On Mon, Dec 21, 2015 at 3:56 PM, Hahn, Steven E. > wrote: I tried viewing the volume representation of a small vtkStructuredGrid file with ParaView v5.0.0-RC2 built with the OpenGL2 rendering backend and get this warning: Warning: In C:\Sources\ParaView-v5.0.0-RC1-source\VTK\Rendering\VolumeOpenGL2\vtkOpenGL ProjectedTetrahedraMapper.cxx, line 251 vtkOpenGLProjectedTetrahedraMapper (00000000061B0AD0): Missing FBO support. The algorithm may produce visual artifacts. Updating the video card (Nvidia Quadro K6000) driver to the latest version (354.56) had no effect. Volume rendering with a different vtkImageData file generated no warnings. They are using different mappers. I am surprised that you are reported missing fbo support. Which windows Platform is this? - Aashish Best, Steven Hahn _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Mon Dec 21 18:53:46 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 21 Dec 2015 18:53:46 -0500 Subject: [Paraview] VTK warning during volume rendering of vtkStructuredGrid on Windows with Nvidia graphics card. In-Reply-To: <1450735636346.93209@ornl.gov> References: <1450735636346.93209@ornl.gov> Message-ID: This is good, GLview, should have a way to export the output to a file. Can you send that to us as well? If it is too big, send it to me directly. Thanks, aashish On Mon, Dec 21, 2015 at 5:07 PM, Hahn, Steven E. wrote: > Hi Aashish, > > > > This machine is running Windows 7. I built Paraview v5.0.0-RC2 with Visual > Studio 2015. > > > > GLview does list GL_ARB_framebuffer_object as supported. Are there any > other specific features in the report that I should check? > > > > Best, > > Steven > ------------------------------ > *From:* Aashish Chaudhary > *Sent:* Monday, December 21, 2015 4:03 PM > *To:* Hahn, Steven E. > *Cc:* ParaView > *Subject:* Re: [Paraview] VTK warning during volume rendering of > vtkStructuredGrid on Windows with Nvidia graphics card. > > Hi Steven, > > Also, can you install and run glview ( > http://www.realtech-vr.com/glview/download.php) on your system to see if > FBO support exists? > > Thanks, > Aashish > > On Mon, Dec 21, 2015 at 4:02 PM, Aashish Chaudhary < > aashish.chaudhary at kitware.com> wrote: > >> >> On Mon, Dec 21, 2015 at 3:56 PM, Hahn, Steven E. wrote: >> >>> I tried viewing the volume representation of a small vtkStructuredGrid >>> file with ParaView v5.0.0-RC2 built with the OpenGL2 rendering backend >>> and >>> get this warning: >>> >>> Warning: In >>> >>> C:\Sources\ParaView-v5.0.0-RC1-source\VTK\Rendering\VolumeOpenGL2\vtkOpenGL >>> ProjectedTetrahedraMapper.cxx, line 251 >>> vtkOpenGLProjectedTetrahedraMapper (00000000061B0AD0): Missing FBO >>> support. The algorithm may produce visual artifacts. >>> >>> Updating the video card (Nvidia Quadro K6000) driver to the latest >>> version >>> (354.56) had no effect. Volume rendering with a different vtkImageData >>> file generated no warnings. >>> >> >> >> They are using different mappers. I am surprised that you are reported >> missing fbo support. Which windows Platform is this? >> >> - Aashish >> >> >>> >>> Best, >>> Steven Hahn >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> >> -- >> >> >> >> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >> * >> *| http://www.kitware.com/company/team/chaudhary.html >> * >> > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. > * > *| http://www.kitware.com/company/team/chaudhary.html > * > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Dec 22 09:53:51 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 22 Dec 2015 09:53:51 -0500 Subject: [Paraview] Paraview crash when loading xdmf with HDF5 data In-Reply-To: References: Message-ID: Hmm, I wonder how it is rendering anything at all without MESA... Thanks for reporting what solved the problem. I've CC'ed the list in case anyone else runs into a similar problem. Cory On Mon, Dec 21, 2015 at 1:37 PM, wide li wrote: > Hi Cory, > > You are right. I should have done that. > > I guess I found the problem cause the crash. I did not install the MESA > library. The lack of MESA does not fail the compilation of Paraview nor > loading the xdmf file with small HDF5 file, but simply results the crash > the ParaView when loading big data. > > Thanks very much anyway. > > Li > > > > ------------------------------ > Date: Mon, 21 Dec 2015 08:55:56 -0500 > Subject: Re: [Paraview] Paraview crash when loading xdmf with HDF5 data > From: cory.quammen at kitware.com > To: wideli at hotmail.com > CC: paraview at paraview.org > > > Li, > > When ParaView crashes, could you share the error that is reported window > that comes up? This will provide a stack trace that can help someone on the > list debug the error. > > Thank you, > Cory > > On Mon, Dec 21, 2015 at 6:49 AM, wide li wrote: > > Hi there, > > I am new to paraview. > > At the moment, I am trying to utilize the xdmf and HDF5 data in paraview. > What I have is very strange. When the HDF5 is small, say the number of > sampling points in each direction is less that 100, paraview works > perfectly. But when the resolution is above this value, the paraview > crashes immediately. The same problem occurs when I use the binary > executable for mac. > > So, could anyone give me some hint where to look at this problem? > > The paraview-5.00-RC1 is compiled and installed on my MAC (EI Capitan). > The parameters setup is as follows. > The qt4 is installed via macport. The HDF5 and MPICH are compiled and > installed without problem. > > > Thanks very much in advance > > Li > > > > BUILD_DOCUMENTATION > OFF > BUILD_EXAMPLES > OFF > BUILD_SHARED_LIBS > ON > BUILD_TESTING ON > BUILD_USER_DEFINED_LIBS OFF > CMAKE_BUILD_TYPE Debug > CTEST_TEST_TIMEOUT 3600 > GMVReader_GMVREAD_LIB_DIR > /Users/Li/Documents/Source/ParaView/ParaView-v5.0.0-RC1-source/Utilities/VisItBridg/databases/GMV > GMVReader_SKIP_DATARANGE_CALCU > OFF > MACOSX_APP_INSTALL_PREFIX > /Applications > MPI_C_INCLUDE_PATH > /usr/local/include > MPI_C_LIBRARIES > /usr/local/lib/libmpi.dylib;/usr/local/lib/lib/libpmpi.dylib > PARAVIEW_BUILD_QT_GUI > ON > PARAVIEW_ENABLE_CATALYST > ON > PARAVIEW_ENABLE_FFMPEG > ON > PARAVIEW_ENABLE_PYTHON > ON > PARAVIEW_ENABLE_XDMF3 > OFF > PARAVIEW_INSTALL_DEVELOPMENT_F > OFF > PARAVIEW_PLUGIN_LOADER_PATHS > > PARAVIEW_USE_DAX > OFF > PARAVIEW_USE_MPI > ON > PARAVIEW_USE_PISTON > OFF > PARAVIEW_USE_UNIFIED_BINDINGS OFF > PARAVIEW_USE_VISITBRIDGE > OFF > RMANTREE > RMANTREE-NOTFOUND > SURFACELIC_PLUGIN_TESTING > ON > VTK_ANDROID_BUILD > OFF > VTK_EGL_DEVICE_INDEX > 0 > VTK_IOS_BUILD > OFF > VTK_PYTHON_VERSION > 2 > VTK_QT_VERSION > 4 > VTK_RENDERING_BACKEND > OpenGL > VTK_SMP_IMPLEMENTATION_TYPE > Sequential > VTK_USE_LARGE_DATA > ON > VTK_USE_SYSTEM_GLEW > OFF > XDMF_USE_BZIP2 > OFF > XDMF_USE_GZIP OFF > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Dec 22 10:11:45 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 22 Dec 2015 10:11:45 -0500 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC0201B@srvmes03.spe-ch-md9.net> Message-ID: On Mon, Dec 21, 2015 at 9:13 AM, Aashish Chaudhary wrote: > Does this patch cleanly applies to all previous version of Mesa or only 11.1 > release? I am assuming that this patch existing in their current master? Brian says "11.1, 11.0 and maybe earlier releases". From utkarsh.ayachit at kitware.com Tue Dec 22 10:14:09 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 22 Dec 2015 10:14:09 -0500 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: <589CEB614006334D93C1A48C1B1964C9027CEAC0202F@srvmes03.spe-ch-md9.net> References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC0201B@srvmes03.spe-ch-md9.net> <589CEB614006334D93C1A48C1B1964C9027CEAC0202F@srvmes03.spe-ch-md9.net> Message-ID: > Also, thank you for liaising with the OpenSWR team in order to check if they support or plan supporting OSMESA. Frank, I am told that OpenSWR on Github should work with OSMesa. I haven't tried it out myself, will give it a go once I get the a few other issues ironed out. Just wanted to let you know if you wanted to give it another go. Utkarsh From cory.quammen at kitware.com Tue Dec 22 10:14:35 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 22 Dec 2015 10:14:35 -0500 Subject: [Paraview] Export animation breaks paraview after some files In-Reply-To: References: Message-ID: Richard, I updated to Windows 10 and installed ParaView 5.0.0-RC2. It runs without problem. Interestingly, when I run dependency walker, I get the same list of missing DLLs as you, but it runs fine. Could you try removing a couple ParaView settings files under C:\\AppData\Roaming\ParaView The settings files in question are ParaView5.0.0.ini ParaView-UserSettings.json Name these to something else, like ParaView5.0.0.ini.bkp, and try to start ParaView 5.0.0 again from the start menu. I know this isn't your primary question, but I'm concerned 5.0.0 isn't running on your system :-) Thanks, Cory On Sun, Dec 20, 2015 at 9:22 PM, Cory Quammen wrote: > Hmm, no, you shouldn't have to install a runtime package before installing > ParaView. Then again, I'm not sure how extensively we are testing Windows > 10. > > Sorry I don't have anything more insightful to share. > > - Cory > > On Wed, Dec 16, 2015 at 3:31 AM, no name > wrote: > >> Hi Cory >> >> Dependency Walker gives me all these files, which cannot be found. I >> guess some runtime package has to be installed first maybe? >> >> API-MS-WIN-CORE-APIQUERY-L1-1-0.DLL >> API-MS-WIN-CORE-APPCOMPAT-L1-1-1.DLL >> API-MS-WIN-CORE-APPINIT-L1-1-0.DLL >> API-MS-WIN-CORE-ATOMS-L1-1-0.DLL >> API-MS-WIN-CORE-COM-L1-1-0 >> API-MS-WIN-CORE-COM-L1-1-1.DLL >> API-MS-WIN-CORE-COM-MIDLPROXYSTUB-L1-1-0.DLL >> API-MS-WIN-CORE-COM-PRIVATE-L1-1-0.DLL >> API-MS-WIN-CORE-COM-PRIVATE-L1-1-1.DLL >> API-MS-WIN-CORE-COMM-L1-1-0.DLL >> API-MS-WIN-CORE-CONSOLE-L2-1-0.DLL >> API-MS-WIN-CORE-CRT-L1-1-0.DLL >> API-MS-WIN-CORE-CRT-L2-1-0.DLL >> API-MS-WIN-CORE-DATETIME-L1-1-1.DLL >> API-MS-WIN-CORE-DATETIME-L1-1-2.DLL >> API-MS-WIN-CORE-DEBUG-L1-1-1.DLL >> API-MS-WIN-CORE-DELAYLOAD-L1-1-1.DLL >> API-MS-WIN-CORE-ERRORHANDLING-L1-1-1.DLL >> API-MS-WIN-CORE-ERRORHANDLING-L1-1-3.DLL >> API-MS-WIN-CORE-FIBERS-L1-1-1.DLL >> API-MS-WIN-CORE-FIBERS-L2-1-1.DLL >> API-MS-WIN-CORE-FILE-L1-2-1.DLL >> API-MS-WIN-CORE-FILE-L1-2-2.DLL >> API-MS-WIN-CORE-FILE-L2-1-1.DLL >> API-MS-WIN-CORE-FILE-L2-1-2.DLL >> API-MS-WIN-CORE-HEAP-L1-2-0.DLL >> API-MS-WIN-CORE-HEAP-L2-1-0.DLL >> API-MS-WIN-CORE-HEAP-OBSOLETE-L1-1-0.DLL >> API-MS-WIN-CORE-INTERLOCKED-L1-2-0.DLL >> API-MS-WIN-CORE-IO-L1-1-1.DLL >> API-MS-WIN-CORE-JOB-L1-1-0.DLL >> API-MS-WIN-CORE-JOB-L2-1-0.DLL >> API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-1.DLL >> API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-3.DLL >> API-MS-WIN-CORE-KERNEL32-PRIVATE-L1-1-1.DLL >> API-MS-WIN-CORE-KERNEL32-PRIVATE-L1-1-2.DLL >> API-MS-WIN-CORE-LIBRARYLOADER-L1-2-0.DLL >> API-MS-WIN-CORE-LIBRARYLOADER-L1-2-1.DLL >> API-MS-WIN-CORE-LIBRARYLOADER-L2-1-0.DLL >> API-MS-WIN-CORE-LOCALIZATION-L1-2-1.DLL >> API-MS-WIN-CORE-LOCALIZATION-L1-2-2.DLL >> API-MS-WIN-CORE-LOCALIZATION-L2-1-0.DLL >> API-MS-WIN-CORE-LOCALIZATION-OBSOLETE-L1-3-0.DLL >> API-MS-WIN-CORE-LOCALIZATION-PRIVATE-L1-1-0.DLL >> API-MS-WIN-CORE-MEMORY-L1-1-2.DLL >> API-MS-WIN-CORE-NAMEDPIPE-L1-2-0.DLL >> API-MS-WIN-CORE-NAMEDPIPE-L1-2-1.DLL >> API-MS-WIN-CORE-NAMESPACE-L1-1-0.DLL >> API-MS-WIN-CORE-NORMALIZATION-L1-1-0.DLL >> API-MS-WIN-CORE-PATH-L1-1-0.DLL >> API-MS-WIN-CORE-PERFCOUNTERS-L1-1-0.DLL >> API-MS-WIN-CORE-PRIVATEPROFILE-L1-1-1.DLL >> API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-2-0.DLL >> API-MS-WIN-CORE-PROCESSSNAPSHOT-L1-1-0.DLL >> API-MS-WIN-CORE-PROCESSTHREADS-L1-1-2.DLL >> API-MS-WIN-CORE-PROCESSTHREADS-L1-1-3.DLL >> API-MS-WIN-CORE-PROCESSTOPOLOGY-L1-2-0.DLL >> API-MS-WIN-CORE-PSAPI-ANSI-L1-1-0.DLL >> API-MS-WIN-CORE-PSAPI-L1-1-0.DLL >> API-MS-WIN-CORE-PSAPI-OBSOLETE-L1-1-0.DLL >> API-MS-WIN-CORE-PSM-KEY-L1-1-0.DLL >> API-MS-WIN-CORE-QUIRKS-L1-1-0.DLL >> API-MS-WIN-CORE-REALTIME-L1-1-0.DLL >> API-MS-WIN-CORE-REGISTRY-L1-1-0.DLL >> API-MS-WIN-CORE-REGISTRY-L1-1-1.DLL >> API-MS-WIN-CORE-REGISTRY-L2-2-0.DLL >> API-MS-WIN-CORE-REGISTRYUSERSPECIFIC-L1-1-0.DLL >> API-MS-WIN-CORE-RTLSUPPORT-L1-2-0.DLL >> API-MS-WIN-CORE-SHLWAPI-LEGACY-L1-1-0.DLL >> API-MS-WIN-CORE-SHLWAPI-OBSOLETE-L1-2-0.DLL >> API-MS-WIN-CORE-SIDEBYSIDE-L1-1-0.DLL >> API-MS-WIN-CORE-STRING-L2-1-0.DLL >> API-MS-WIN-CORE-STRING-L2-1-1.DLL >> API-MS-WIN-CORE-STRING-OBSOLETE-L1-1-0.DLL >> API-MS-WIN-CORE-STRINGANSI-L1-1-0.DLL >> API-MS-WIN-CORE-SYNCH-L1-2-1.DLL >> API-MS-WIN-CORE-SYSINFO-L1-2-1.DLL >> API-MS-WIN-CORE-SYSINFO-L1-2-3.DLL >> API-MS-WIN-CORE-SYSTEMTOPOLOGY-L1-1-0.DLL >> API-MS-WIN-CORE-THREADPOOL-L1-2-0.DLL >> API-MS-WIN-CORE-THREADPOOL-LEGACY-L1-1-0.DLL >> API-MS-WIN-CORE-THREADPOOL-PRIVATE-L1-1-0.DLL >> API-MS-WIN-CORE-URL-L1-1-0.DLL >> API-MS-WIN-CORE-VERSION-L1-1-0.DLL >> API-MS-WIN-CORE-VERSIONANSI-L1-1-0.DLL >> API-MS-WIN-CORE-WINDOWSERRORREPORTING-L1-1-0.DLL >> API-MS-WIN-CORE-WINRT-ERROR-L1-1-1.DLL >> API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL >> API-MS-WIN-CORE-WOW64-L1-1-0.DLL >> API-MS-WIN-CORE-WOW64-L1-1-1.DLL >> API-MS-WIN-CORE-XSTATE-L2-1-0.DLL >> API-MS-WIN-DEVICES-CONFIG-L1-1-1.DLL >> API-MS-WIN-DEVICES-QUERY-L1-1-1.DLL >> API-MS-WIN-EVENTING-CLASSICPROVIDER-L1-1-0.DLL >> API-MS-WIN-EVENTING-CONSUMER-L1-1-0.DLL >> API-MS-WIN-EVENTING-CONTROLLER-L1-1-0.DLL >> API-MS-WIN-EVENTING-OBSOLETE-L1-1-0.DLL >> API-MS-WIN-EVENTING-PROVIDER-L1-1-0.DLL >> API-MS-WIN-MM-JOYSTICK-L1-1-0.DLL >> API-MS-WIN-MM-MISC-L1-1-1.DLL >> API-MS-WIN-MM-MME-L1-1-0.DLL >> API-MS-WIN-MM-TIME-L1-1-0.DLL >> API-MS-WIN-SECURITY-ACTIVEDIRECTORYCLIENT-L1-1-0.DLL >> API-MS-WIN-SECURITY-APPCONTAINER-L1-1-0.DLL >> API-MS-WIN-SECURITY-AUDIT-L1-1-1.DLL >> API-MS-WIN-SECURITY-BASE-L1-2-0.DLL >> API-MS-WIN-SECURITY-BASE-PRIVATE-L1-1-1.DLL >> API-MS-WIN-SECURITY-GROUPPOLICY-L1-1-0.DLL >> API-MS-WIN-SECURITY-LSALOOKUP-L1-1-1.DLL >> API-MS-WIN-SECURITY-LSAPOLICY-L1-1-0.DLL >> API-MS-WIN-SECURITY-SDDL-L1-1-0.DLL >> API-MS-WIN-SERVICE-CORE-L1-1-1.DLL >> API-MS-WIN-SERVICE-CORE-L1-1-2.DLL >> API-MS-WIN-SERVICE-MANAGEMENT-L1-1-0.DLL >> API-MS-WIN-SERVICE-MANAGEMENT-L2-1-0.DLL >> API-MS-WIN-SERVICE-PRIVATE-L1-1-0 >> API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL >> API-MS-WIN-SERVICE-WINSVC-L1-2-0.DLL >> API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL >> API-MS-WIN-SHELL-SHELLCOM-L1-1-0.DLL >> API-MS-WIN-SHELL-SHELLFOLDERS-L1-1-0.DLL >> API-MS-WIN-STORAGE-EXPORTS-EXTERNAL-L1-1-0.DLL >> API-MS-WIN-STORAGE-EXPORTS-INTERNAL-L1-1-0.DLL >> API-MS-WIN-APPMODEL-IDENTITY-L1-2-0.DLL >> API-MS-WIN-APPMODEL-RUNTIME-INTERNAL-L1-1-0.DLL >> API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL >> API-MS-WIN-APPMODEL-RUNTIME-L1-1-1.DLL >> API-MS-WIN-APPMODEL-STATE-L1-2-0.DLL >> API-MS-WIN-APPMODEL-UNLOCK-L1-1-0.DLL >> API-MS-WIN-BASE-UTIL-L1-1-0.DLL >> API-MS-WIN-CORE-CALENDAR-L1-1-0.DLL >> API-MS-WIN-CORE-COM-L2-1-1.DLL >> API-MS-WIN-CORE-DELAYLOAD-L1-1-0.DLL >> API-MS-WIN-CORE-FIBERS-L1-1-0.DLL >> API-MS-WIN-CORE-IO-L1-1-0.DLL >> API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-0.DLL >> API-MS-WIN-CORE-LOCALIZATION-L1-1-0.DLL >> API-MS-WIN-CORE-LOCALIZATION-OBSOLETE-L1-2-0.DLL >> API-MS-WIN-CORE-LOCALREGISTRY-L1-1-0.DLL >> API-MS-WIN-CORE-MARSHAL-L1-1-0.DLL >> API-MS-WIN-CORE-MISC-L1-1-0.DLL >> API-MS-WIN-CORE-PROCESSTOPOLOGY-OBSOLETE-L1-1-0.DLL >> API-MS-WIN-CORE-PSM-APPNOTIFY-L1-1-0.DLL >> API-MS-WIN-CORE-REALTIME-L1-1-1.DLL >> API-MS-WIN-CORE-REGISTRY-PRIVATE-L1-1-0.DLL >> API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL >> API-MS-WIN-CORE-SYSINFO-L1-2-0.DLL >> API-MS-WIN-CORE-TOOLHELP-L1-1-0.DLL >> API-MS-WIN-CORE-VERSION-L1-1-1.DLL >> API-MS-WIN-CORE-VERSION-PRIVATE-L1-1-0.DLL >> API-MS-WIN-CORE-VERSIONANSI-L1-1-1.DLL >> API-MS-WIN-CORE-WINRT-ERRORPRIVATE-L1-1-1.DLL >> API-MS-WIN-CORE-WINRT-L1-1-0.DLL >> API-MS-WIN-CORE-WINRT-PROPERTYSETPRIVATE-L1-1-0.DLL >> API-MS-WIN-CORE-WINRT-PROPERTYSETPRIVATE-L1-1-1.DLL >> API-MS-WIN-CORE-WINRT-REGISTRATION-L1-1-0.DLL >> API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL >> API-MS-WIN-COREUI-SECRUNTIME-L1-1-0.DLL >> API-MS-WIN-DOWNLEVEL-ADVAPI32-L1-1-0.DLL >> API-MS-WIN-DOWNLEVEL-ADVAPI32-L2-1-0.DLL >> API-MS-WIN-DOWNLEVEL-NORMALIZ-L1-1-0.DLL >> API-MS-WIN-DOWNLEVEL-OLE32-L1-1-0.DLL >> API-MS-WIN-DOWNLEVEL-SHELL32-L1-1-0.DLL >> API-MS-WIN-DOWNLEVEL-SHLWAPI-L1-1-0.DLL >> API-MS-WIN-DOWNLEVEL-SHLWAPI-L2-1-0.DLL >> API-MS-WIN-DOWNLEVEL-SHLWAPI-L2-1-1.DLL >> API-MS-WIN-DOWNLEVEL-USER32-L1-1-0.DLL >> API-MS-WIN-DOWNLEVEL-VERSION-L1-1-0.DLL >> API-MS-WIN-DX-D3DKMT-L1-1-0.DLL >> API-MS-WIN-EVENTING-LEGACY-L1-1-0.DLL >> API-MS-WIN-EVENTLOG-LEGACY-L1-1-0.DLL >> API-MS-WIN-GDI-DPIINFO-L1-1-0.DLL >> API-MS-WIN-MM-MISC-L2-1-0.DLL >> API-MS-WIN-NTUSER-IE-MESSAGE-L1-1-0.DLL >> API-MS-WIN-NTUSER-SYSPARAMS-L1-1-0.DLL >> API-MS-WIN-OLE32-IE-L1-1-0.DLL >> API-MS-WIN-POWER-BASE-L1-1-0.DLL >> API-MS-WIN-POWER-SETTING-L1-1-0.DLL >> API-MS-WIN-RTCORE-NTUSER-CLIPBOARD-L1-1-0.DLL >> API-MS-WIN-RTCORE-NTUSER-PRIVATE-L1-1-0.DLL >> API-MS-WIN-RTCORE-NTUSER-PRIVATE-L1-1-1.DLL >> API-MS-WIN-RTCORE-NTUSER-SYNCH-L1-1-0.DLL >> API-MS-WIN-RTCORE-NTUSER-WINDOW-L1-1-0.DLL >> API-MS-WIN-RTCORE-NTUSER-WINEVENT-L1-1-0.DLL >> API-MS-WIN-SECURITY-ACCESSHLPR-L1-1-0.DLL >> API-MS-WIN-SECURITY-ACTIVEDIRECTORYCLIENT-L1-1-1.DLL >> API-MS-WIN-SECURITY-BASE-L1-1-0.DLL >> API-MS-WIN-SECURITY-CAPABILITY-L1-1-0.DLL >> API-MS-WIN-SECURITY-CREDENTIALS-L1-1-0.DLL >> API-MS-WIN-SECURITY-CREDENTIALS-L2-1-0.DLL >> API-MS-WIN-SECURITY-CRYPTOAPI-L1-1-0.DLL >> API-MS-WIN-SECURITY-LSALOOKUP-L1-1-2.DLL >> API-MS-WIN-SECURITY-LSALOOKUP-L2-1-1.DLL >> API-MS-WIN-SECURITY-PROVIDER-L1-1-0.DLL >> API-MS-WIN-SECURITY-SDDLPARSECOND-L1-1-0.DLL >> API-MS-WIN-SERVICE-WINSVC-L1-1-0.DLL >> API-MS-WIN-SHCORE-COMHELPERS-L1-1-0.DLL >> API-MS-WIN-SHCORE-OBSOLETE-L1-1-0.DLL >> API-MS-WIN-SHCORE-REGISTRY-L1-1-1.DLL >> API-MS-WIN-SHCORE-STREAM-L1-1-0.DLL >> API-MS-WIN-SHCORE-STREAM-WINRT-L1-1-0.DLL >> API-MS-WIN-SHCORE-SYSINFO-L1-1-0.DLL >> API-MS-WIN-SHCORE-THREAD-L1-1-0.DLL >> API-MS-WIN-SHCORE-UNICODEANSI-L1-1-0.DLL >> API-MS-WIN-SHLWAPI-IE-L1-1-0.DLL >> API-MS-WIN-SHLWAPI-WINRT-STORAGE-L1-1-1.DLL >> EMCLIENT.DLL >> EXT-MS-MF-PAL-L2-1-0.DLL >> EXT-MS-ONECORE-APPCHROMEAPI-L1-1-0.DLL >> EXT-MS-ONECORE-APPMODEL-VEVENTDISPATCHER-L1-1-0.DLL >> EXT-MS-ONECORE-DCOMP-L1-1-0.DLL >> EXT-MS-ONECORE-ORIENTATION-L1-1-0.DLL >> EXT-MS-ONECORE-PHONEINFO-L1-1-0.DLL >> EXT-MS-ONECORE-SHELLCHROMEAPI-L1-1-1.DLL >> EXT-MS-WIN-ADVAPI32-EVENTINGCONTROLLER-L1-1-0.DLL >> EXT-MS-WIN-ADVAPI32-MSI-L1-1-0.DLL >> EXT-MS-WIN-ADVAPI32-NPUSERNAME-L1-1-0.DLL >> EXT-MS-WIN-ADVAPI32-NTMARTA-L1-1-0.DLL >> EXT-MS-WIN-ADVAPI32-PSM-APP-L1-1-0.DLL >> EXT-MS-WIN-ADVAPI32-REGISTRY-L1-1-0.DLL >> EXT-MS-WIN-ADVAPI32-SAFER-L1-1-0.DLL >> EXT-MS-WIN-APPCOMPAT-APPHELP-L1-1-0.DLL >> EXT-MS-WIN-APPMODEL-APPCONTAINERPATH-L1-1-0.DLL >> EXT-MS-WIN-APPMODEL-DEPLOYMENT-L1-1-1.DLL >> EXT-MS-WIN-APPMODEL-STATE-EXT-L1-2-0.DLL >> EXT-MS-WIN-APPMODEL-USERCONTEXT-L1-1-0.DLL >> EXT-MS-WIN-APPXDEPLOYMENTCLIENT-APPXDEPLOY-L1-1-0.DLL >> EXT-MS-WIN-APPXDEPLOYMENTCLIENT-APPXDEPLOYONECORE-L1-1-0.DLL >> EXT-MS-WIN-AUDIOCORE-PAL-L1-1-0.DLL >> EXT-MS-WIN-AUTHZ-CONTEXT-L1-1-0.DLL >> EXT-MS-WIN-AUTHZ-REMOTE-L1-1-0.DLL >> EXT-MS-WIN-COM-CLBCATQ-L1-1-0.DLL >> EXT-MS-WIN-COM-COML2-L1-1-1.DLL >> EXT-MS-WIN-COM-OLE32-L1-1-1.DLL >> EXT-MS-WIN-COM-OLE32-L1-1-3.DLL >> EXT-MS-WIN-COM-PSMREGISTER-L1-1-0.DLL >> EXT-MS-WIN-COM-SUSPENDRESILIENCY-L1-1-0.DLL >> EXT-MS-WIN-CORE-WINRT-REMOTE-L1-1-0.DLL >> EXT-MS-WIN-DEVMGMT-POLICY-L1-1-0.DLL >> EXT-MS-WIN-DOMAINJOIN-NETJOIN-L1-1-0.DLL >> EXT-MS-WIN-DWMAPIDXGI-EXT-L1-1-0.DLL >> EXT-MS-WIN-EDPUTIL-POLICY-L1-1-0.DLL >> EXT-MS-WIN-FAMILYSAFETY-CHILDACCOUNT-L1-1-0.DLL >> EXT-MS-WIN-FECLIENT-ENCRYPTEDFILE-L1-1-0.DLL >> EXT-MS-WIN-FIREWALLAPI-WEBPROXY-L1-1-0.DLL >> EXT-MS-WIN-GDI-DC-CREATE-L1-1-1.DLL >> EXT-MS-WIN-GDI-DC-L1-2-0.DLL >> EXT-MS-WIN-GDI-DEVCAPS-L1-1-0.DLL >> EXT-MS-WIN-GDI-DRAW-L1-1-1.DLL >> EXT-MS-WIN-GDI-DRAW-L1-1-2.DLL >> EXT-MS-WIN-GDI-FONT-L1-1-1.DLL >> EXT-MS-WIN-GDI-FONT-L1-1-2.DLL >> EXT-MS-WIN-GDI-METAFILE-L1-1-1.DLL >> EXT-MS-WIN-GDI-PATH-L1-1-0.DLL >> EXT-MS-WIN-GDI-RENDER-L1-1-0.DLL >> EXT-MS-WIN-GPAPI-GROUPPOLICY-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-APPCOMPAT-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-DATETIME-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-ERRORHANDLING-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-FILE-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-LOCALIZATION-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-PACKAGE-CURRENT-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-PACKAGE-L1-1-1.DLL >> EXT-MS-WIN-KERNEL32-QUIRKS-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-QUIRKS-L1-1-1.DLL >> EXT-MS-WIN-KERNEL32-REGISTRY-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-SIDEBYSIDE-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-WINDOWSERRORREPORTING-L1-1-0.DLL >> EXT-MS-WIN-KERNEL32-WINDOWSERRORREPORTING-L1-1-1.DLL >> EXT-MS-WIN-KERNELBASE-PROCESSTHREAD-L1-1-0.DLL >> EXT-MS-WIN-MININPUT-INPUTHOST-L1-1-0.DLL >> EXT-MS-WIN-MPR-MULTIPLEPROVIDERROUTER-L1-1-0.DLL >> EXT-MS-WIN-MRMCORER-ENVIRONMENT-L1-1-0.DLL >> EXT-MS-WIN-MRMCORER-RESMANAGER-L1-1-0.DLL >> EXT-MS-WIN-NTDSAPI-ACTIVEDIRECTORYCLIENT-L1-1-0.DLL >> EXT-MS-WIN-NTDSAPI-ACTIVEDIRECTORYCLIENT-L1-1-1.DLL >> EXT-MS-WIN-NTUSER-DC-ACCESS-EXT-L1-1-0.DLL >> EXT-MS-WIN-NTUSER-DIALOGBOX-L1-1-1.DLL >> EXT-MS-WIN-NTUSER-DIALOGBOX-L1-1-2.DLL >> EXT-MS-WIN-NTUSER-DRAW-L1-1-1.DLL >> EXT-MS-WIN-NTUSER-DRAW-L1-1-2.DLL >> EXT-MS-WIN-NTUSER-GUI-L1-3-0.DLL >> EXT-MS-WIN-NTUSER-KEYBOARD-L1-1-1.DLL >> EXT-MS-WIN-NTUSER-KEYBOARD-L1-2-0.DLL >> EXT-MS-WIN-NTUSER-MENU-L1-1-2.DLL >> EXT-MS-WIN-NTUSER-MESSAGE-L1-1-1.DLL >> EXT-MS-WIN-NTUSER-MESSAGE-L1-1-2.DLL >> EXT-MS-WIN-NTUSER-MISC-L1-3-0.DLL >> EXT-MS-WIN-NTUSER-MISC-L1-5-0.DLL >> EXT-MS-WIN-NTUSER-MOUSE-L1-1-0.DLL >> EXT-MS-WIN-NTUSER-PRIVATE-L1-2-0.DLL >> EXT-MS-WIN-NTUSER-RECTANGLE-EXT-L1-1-0.DLL >> EXT-MS-WIN-NTUSER-ROTATIONMANAGER-L1-1-0.DLL >> EXT-MS-WIN-NTUSER-STRING-L1-1-0.DLL >> EXT-MS-WIN-NTUSER-SYNCH-L1-1-0.DLL >> EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL >> EXT-MS-WIN-NTUSER-WINDOW-L1-1-1.DLL >> EXT-MS-WIN-NTUSER-WINDOW-L1-1-3.DLL >> EXT-MS-WIN-NTUSER-WINDOWCLASS-L1-1-1.DLL >> EXT-MS-WIN-NTUSER-WINDOWSTATION-L1-1-1.DLL >> EXT-MS-WIN-OLE32-BINDCTX-L1-1-0.DLL >> EXT-MS-WIN-OLE32-IE-EXT-L1-1-0.DLL >> EXT-MS-WIN-OLE32-OLEAUTOMATION-L1-1-0.DLL >> EXT-MS-WIN-PROFILE-EXTENDER-L1-1-0.DLL >> EXT-MS-WIN-PROFILE-LOAD-L1-1-0.DLL >> EXT-MS-WIN-PROFILE-USERENV-L1-1-0.DLL >> EXT-MS-WIN-PROFILE-USERENV-L1-1-1.DLL >> EXT-MS-WIN-RPC-SSL-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-GDI-DEVCAPS-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-GDI-OBJECT-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-GDI-RGN-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-GDI-RGN-L1-1-1.DLL >> EXT-MS-WIN-RTCORE-MINUSER-PRIVATE-EXT-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-NTUSER-CURSOR-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-NTUSER-DC-ACCESS-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-NTUSER-DPI-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-NTUSER-IAM-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-NTUSER-INTEGRATION-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-NTUSER-SYNCH-EXT-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-NTUSER-SYSCOLORS-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-NTUSER-SYSPARAMS-L1-1-0.DLL >> EXT-MS-WIN-RTCORE-NTUSER-WINDOW-EXT-L1-1-0.DLL >> EXT-MS-WIN-SECUR32-TRANSLATENAME-L1-1-0.DLL >> EXT-MS-WIN-SECURITY-CAPAUTHZ-L1-1-0.DLL >> EXT-MS-WIN-SECURITY-CHAMBERS-L1-1-0.DLL >> EXT-MS-WIN-SECURITY-CREDUI-L1-1-0.DLL >> EXT-MS-WIN-SECURITY-EFS-L1-1-0.DLL >> EXT-MS-WIN-SESSION-USERMGR-L1-1-0.DLL >> EXT-MS-WIN-SESSION-USERTOKEN-L1-1-0.DLL >> EXT-MS-WIN-SESSION-WINSTA-L1-1-0.DLL >> EXT-MS-WIN-SESSION-WTSAPI32-L1-1-0.DLL >> EXT-MS-WIN-SETUPAPI-INF-L1-1-0.DLL >> EXT-MS-WIN-SHELL-DIRECTORY-L1-1-0.DLL >> EXT-MS-WIN-SHELL-PROPSYS-L1-1-0.DLL >> EXT-MS-WIN-SHELL-SHELL32-L1-2-0.DLL >> EXT-MS-WIN-SHELL-SHLWAPI-L1-1-0.DLL >> EXT-MS-WIN-SHELL32-SHELLCOM-L1-1-0.DLL >> EXT-MS-WIN-SXS-OLEAUTOMATION-L1-1-0.DLL >> EXT-MS-WIN-UI-VIEWMANAGEMENT-L1-1-0.DLL >> EXT-MS-WIN-USP10-L1-1-0.DLL >> EXT-MS-WIN-WER-UI-L1-1-0.DLL >> EXT-MS-WIN-WER-XBOX-L1-1-0.DLL >> EXT-MS-WIN-WINRT-STORAGE-L1-1-0.DLL >> EXT-MS-WIN-WLAN-ONEXUI-L1-1-0.DLL >> IESHIMS.DLL >> >> Hop that helps a little bit. >> >> Richard >> >> On 16 December 2015 at 09:26, no name >> wrote: >> > Hey Cory >> > >> > I cannot run paraview -dr >> > I see the startupscreen, then an output window (with nothing in it) >> > and then "Paraview stopped working". I run wind10x64. >> > >> > Thanks >> > Richard >> > >> > On 14 December 2015 at 16:38, Cory Quammen >> wrote: >> >> Richard, >> >> >> >> Can you specify what system you are running? >> >> >> >> Usually the most informative way to see what is going on is to run it >> >> through a debugger like gdb and lldb. This should at least get you a >> stack >> >> trace which will help us identify where it is failing. If you are on >> >> Windows, there may be a dialog that pops up with some information. >> >> >> >> You could try running from the command line with the -dr option, e.g. >> >> >> >> paraview -dr >> >> >> >> This will disable any options or settings that may be causing >> problems. If >> >> ParaView runs with that option, then the solution is likely to be to >> clear >> >> your settings files. >> >> >> >> HTH, >> >> Cory >> >> >> >> On Mon, Dec 14, 2015 at 3:41 AM, no name >> >> wrote: >> >>> >> >>> Hi Cory >> >>> >> >>> Thanks for the help, but unfortunately Paraview 5.0 RC1 wont run on my >> >>> system at all, it crashes on startup :( Do you know where I can find >> >>> some logs, maybe I can get it working? >> >>> >> >>> Thanks >> >>> Richard >> >>> >> >>> On 11 December 2015 at 15:14, Cory Quammen >> >>> wrote: >> >>> > Hi Richard, >> >>> > >> >>> > Could you try this with ParaView 5.0 Release Candidate 1 (RC1) and >> >>> > report >> >>> > whether you see the same thing? >> >>> > >> >>> > Thanks, >> >>> > Cory >> >>> > >> >>> > On Fri, Dec 11, 2015 at 8:25 AM, no name < >> keinepostnurmuell at gmail.com> >> >>> > wrote: >> >>> >> >> >>> >> What I do: >> >>> >> >> >>> >> Open multiple INP files, run them through a pipeline. >> >>> >> Export them as PNG (same error when I do it as a OVG...) via Save >> >>> >> Animation. >> >>> >> >> >>> >> How does it look: >> >>> >> Right now I have a renderview on the left side and a >> spreadsheetview >> >>> >> on the right side. Usually after about 30-110 steps the label of >> the y >> >>> >> axis of the spread sheet view goes 10 pixels to the right or so and >> >>> >> the renderview object disappears completely. Lets say I exported 10 >> >>> >> PNGs and after the 8th its broken. >> >>> >> >> >>> >> When I then go back in the paraview main window after the animation >> >>> >> made the renderview go south and click for example on the 5th input >> >>> >> file, I also don't see anything in the render view. Even if I try >> to >> >>> >> load a new INP in that renderview I stell don't see anything. >> >>> >> >> >>> >> Using paraview 4.4 on Win10 x64 >> >>> >> >> >>> >> I did not attach images, as I don't know if that comes through the >> >>> >> mailing list :( >> >>> >> >> >>> >> Thanks for your help >> >>> >> Richard >> >>> >> _______________________________________________ >> >>> >> Powered by www.kitware.com >> >>> >> >> >>> >> Visit other Kitware open-source projects at >> >>> >> http://www.kitware.com/opensource/opensource.html >> >>> >> >> >>> >> Please keep messages on-topic and check the ParaView Wiki at: >> >>> >> http://paraview.org/Wiki/ParaView >> >>> >> >> >>> >> Search the list archives at: >> http://markmail.org/search/?q=ParaView >> >>> >> >> >>> >> Follow this link to subscribe/unsubscribe: >> >>> >> http://public.kitware.com/mailman/listinfo/paraview >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > -- >> >>> > Cory Quammen >> >>> > R&D Engineer >> >>> > Kitware, Inc. >> >> >> >> >> >> >> >> >> >> -- >> >> Cory Quammen >> >> R&D Engineer >> >> Kitware, Inc. >> > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Tue Dec 22 10:24:44 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Tue, 22 Dec 2015 10:24:44 -0500 Subject: [Paraview] VTK warning during volume rendering of vtkStructuredGrid on Windows with Nvidia graphics card. In-Reply-To: <1450797708669.18352@ornl.gov> References: <1450735636346.93209@ornl.gov> <1450797708669.18352@ornl.gov> Message-ID: this is very useful.I will push a fix today and will attach a patch too. - Aashish On Tue, Dec 22, 2015 at 10:21 AM, Hahn, Steven E. wrote: > Hi Aashish, > > > > The XML report is attached. > > > > Best, > > Steven > ------------------------------ > *From:* Aashish Chaudhary > *Sent:* Monday, December 21, 2015 6:53 PM > > *To:* Hahn, Steven E. > *Cc:* ParaView > *Subject:* Re: [Paraview] VTK warning during volume rendering of > vtkStructuredGrid on Windows with Nvidia graphics card. > > This is good, GLview, should have a way to export the output to a file. > Can you send that to us as well? If it is too big, send it to me directly. > > Thanks, > aashish > > On Mon, Dec 21, 2015 at 5:07 PM, Hahn, Steven E. wrote: > >> Hi Aashish, >> >> >> >> This machine is running Windows 7. I built Paraview v5.0.0-RC2 with >> Visual Studio 2015. >> >> >> >> GLview does list GL_ARB_framebuffer_object as supported. Are there any >> other specific features in the report that I should check? >> >> >> >> Best, >> >> Steven >> ------------------------------ >> *From:* Aashish Chaudhary >> *Sent:* Monday, December 21, 2015 4:03 PM >> *To:* Hahn, Steven E. >> *Cc:* ParaView >> *Subject:* Re: [Paraview] VTK warning during volume rendering of >> vtkStructuredGrid on Windows with Nvidia graphics card. >> >> Hi Steven, >> >> Also, can you install and run glview ( >> http://www.realtech-vr.com/glview/download.php) on your system to see if >> FBO support exists? >> >> Thanks, >> Aashish >> >> On Mon, Dec 21, 2015 at 4:02 PM, Aashish Chaudhary < >> aashish.chaudhary at kitware.com> wrote: >> >>> >>> On Mon, Dec 21, 2015 at 3:56 PM, Hahn, Steven E. >>> wrote: >>> >>>> I tried viewing the volume representation of a small vtkStructuredGrid >>>> file with ParaView v5.0.0-RC2 built with the OpenGL2 rendering backend >>>> and >>>> get this warning: >>>> >>>> Warning: In >>>> >>>> C:\Sources\ParaView-v5.0.0-RC1-source\VTK\Rendering\VolumeOpenGL2\vtkOpenGL >>>> ProjectedTetrahedraMapper.cxx, line 251 >>>> vtkOpenGLProjectedTetrahedraMapper (00000000061B0AD0): Missing FBO >>>> support. The algorithm may produce visual artifacts. >>>> >>>> Updating the video card (Nvidia Quadro K6000) driver to the latest >>>> version >>>> (354.56) had no effect. Volume rendering with a different vtkImageData >>>> file generated no warnings. >>>> >>> >>> >>> They are using different mappers. I am surprised that you are reported >>> missing fbo support. Which windows Platform is this? >>> >>> - Aashish >>> >>> >>>> >>>> Best, >>>> Steven Hahn >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> >>> -- >>> >>> >>> >>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>> * >>> *| http://www.kitware.com/company/team/chaudhary.html >>> * >>> >> >> >> >> -- >> >> >> >> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >> * >> *| http://www.kitware.com/company/team/chaudhary.html >> * >> > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. > * > *| http://www.kitware.com/company/team/chaudhary.html > * > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank.albina at sauber-motorsport.com Thu Dec 17 11:19:52 2015 From: frank.albina at sauber-motorsport.com (Albina, Frank) Date: Thu, 17 Dec 2015 17:19:52 +0100 Subject: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 In-Reply-To: References: <589CEB614006334D93C1A48C1B1964C9027CEAC01DCD@srvmes03.spe-ch-md9.net> Message-ID: <589CEB614006334D93C1A48C1B1964C9027CEAC0201B@srvmes03.spe-ch-md9.net> Dear Utkarsh! It's now one week since I have written my last email in this thread. I would have liked to have replied earlier, but since then ParaView 5.0.0-RC2 was made available for download and hence, I had to restart all compilations and tests from scratch. The tests I am most interested in are summarized in a few benchmarks that I can pass you if you fancy. Please liaise with me directly if you wish to do so and I might be able upload data and benchmark instructions to the server of your choice. The benchmarks are divided in 2 categories: 1) pressure contours on a generic (and quite outdated) F1 car geometry. 2) surfaceLIC of the flow-field on the surface of the aforementioned F1 car geometry. The expected results are shown in the enclosed pictures 1.jpg for the pressure contours and 2.jpg for the surfaceLIC representation. In order to run ParaView v5.0.0-rc2 using the OpenGL2 backend in batch with Mesa, I had to set: a) MESA_GL_VERSION_OVERRIDE = 3.2 b) MESA_GLSL_VERSION_OVERRIDE = 150 For my tests, I used compiled Mesa v10.6.9 and 11.0.7 which are delivering similar results in terms of performance, therefore I will focus mainly on the latest Mesa v11.0.7 release. I have compiled 2 flavors: 1) the "classic" osmesa: ---------------------------- ./configure --prefix=${installDir} --enable-texture-float --enable-osmesa --disable-egl --disable-xvmc --disable-opencl --disable-glx --disable-dri --disable-va --enable-gallium-llvm=no --with-gnu-ld --with-osmesa-bits=8 --disable-vdpau --enable-dependency-tracking --with-gallium-drivers="" --with-dri-drivers="" --with-egl-platforms="" 2) the "llvm" backend: ----------------------------- ./configure --enable-texture-float --disable-egl --disable-xvmc --disable-opencl --disable-glx --disable-dri --disable-va --enable-gallium-llvm=yes --with-gnu-ld --with-osmesa-bits=8 --disable-vdpau --enable-dependency-tracking --with-gallium-drivers="swrast" --enable-gallium-osmesa --with-dri-drivers="" --with-egl-platforms="" --enable-gallium-llvm --enable-llvm-shared-libs The reason is that I tried both flavors with Mesa-10.5.5 together with Paraview v4.3.1 and found out that the "classic" flavor on the Mesa v10.5.5 release was faster by a substantial amount (up to 40%) compared to the "llvm" flavor. For this reason, I have used Paraview v5.0.0-rc2 with both Mesa libraries, with following options to force building with an OpenGL2 backend and also support for SurfaceLIC. cmake $sourceDir \ -DBUILD_SHARED_LIBS:BOOL=ON\ -DBUILD_TESTING:BOOL=OFF\ -DBUILD_DOCUMENTATION:BOOL=OFF\ -DCMAKE_BUILD_TYPE:STRING=Release\ -DPARAVIEW_ENABLE_CATALYST:BOOL=ON\ -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ -DPARAVIEW_USE_MPI:BOOL=ON\ -DPARAVIEW_USE_UNIFIED_BINDINGS:BOOL=OFF\ -DPARAVIEW_ENABLE_WEB:BOOL=OFF\ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON\ -DVTK_USE_MANGLED_MESA:BOOL=OFF\ -DOPENGL_gl_LIBRARY:FILEPATH=\ -DOPENGL_glu_LIBRARY:FILEPATH=$mesaPath/mesa-11.0.7/lib/libGLU.so\ -DOPENGL_xmesa_INCLUDE_DIR:PATH==$mesaPath/mesa-11.0.7/include\ -DOSMESA_LIBRARY:PATH= $mesaPath/mesa-11.0.7/lib/libOSMesa.so\ -DOSMESA_INCLUDE_PATH:PATH=$mesaPath/generic/mesa-11.0.7/include\ -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=ON\ -DPARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE\ -DPARAVIEW_USE_MPI:BOOL=ON\ -DVTK_USE_OFFSCREEN:BOOL=ON\ -DVTK_USE_X:BOOL=OFF\ -DVTK_USE_QT=OFF\ -DVTK_USE_DISPLAY=ON\ -DVTK_USE_GUI_SUPPORT:BOOL=OFF\ -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF\ -DCMAKE_INSTALL_PREFIX:PATH=$installDir\ -DPARAVIEW_ENABLE_PYTHON:BOOL=ON\ -DPYTHON_ENABLE_MODULE_MPIPython:BOOL=ON\ -DMAKE_CXX_COMPILER:FILEPATH=$gccPath/bin/g++\ -DCMAKE_C_COMPILER:FILEPATH=$gccPath/bin/gcc\ -DCMAKE_Fortran_COMPILER:FILEPATH=$gccPath/bin/gfortran\ -DMPI_COMPILER:FILEPATH=$MPI_HOME/bin/mpicxx\ -DMPI_INCLUDE_PATH:FILEPATH=$MPI_HOME/include\ -DMPI_Fortran_COMPILER:FILEPATH=$MPI_HOME/bin/mpif90\ -DMPI_Fortran_LIBRARIES:FILEPATH=$MPI_HOME/lib/libmpifort.so\ -DMPI_Fortran_INCLUDE_PATH:FILEPATH=$MPI_HOME/include\ -DMPI_LIBRARY:FILEPATH=$MPI_HOME/lib/libmpi.so\ -DMPI_C_LIBRARIES:FILEPATH=$MPI_HOME/lib/libmpi.so\ -DMPI_CXX_LIBRARIES:FILEPATH=$MPI_HOME/lib/libmpicxx.so\ -DPYTHON_LIBRARY:FILEPATH=$PYTHON_HOME/lib/libpython2.7.so\ -DPYTHON_INCLUDE_DIR:PATH=$PYTHON_HOME/include/python2.7\ -DPYTHON_EXECUTABLE:FILEPATH=$PYTHON_HOME/bin/python2.7\ -DVTK_RENDERING_BACKEND:STRING=OpenGL2\ -DModule_vtkRenderingLICOpenGL2:BOOL=ON\ Here is a summary of the tests I have performed for the different benchmarks: 1) Pressure contour benchmark a) Rendering time with the "classic" mesa flavor is much slower that the "llvmpipe" flavor. There is a factor of 3 difference on 1 core, a factor of 6 on 2 cores. The generated images using 1 core are as if lighting went missing (see 3.jpg). In batch and in parallel, when more than one core is involved, it looks like only the bits owned by the master process are displayed (see attached filed 4.jpg). b) Images rendered using the "llvmpipe" flavor are generated correctly. 2) surfaceLIC benchmark Not used using the "classic" mesa flavor, only with the "llvmpipe". I am getting an odd behavior where the benchmark hangs randomly in parallel. Restarting the parallel process by hand usually works but I can get corrupted images. Also, when using more than one core in parallel, one can see clearly which part of the image is processed by which core (see file 5.jpg). This is something I did not recall seeing using PV versions from 4.1 to 4.3. I am wondering if this is an expected behavior? Finally, I have tried compile openswr-mesa-11.0 on my compute platform. After resolving all kind of dependencies, I could not get the libOSMESA.so compiled using swr as driver. Here are my compilation options: ./configure --enable-gallium-osmesa --enable-dependency-tracking --enable-gallium-llvm=yes --enable-llvm-shared-libs --enable-swr-native --enable-sysfs --enable-texture-float --disable-dri --disable-egl --disable-glx --disable-gles1 --disable-gles2 --disable-opencl --disable-vdpau --disable-va --disable-xvmc --with-dri-drivers="" --with-egl-platforms="" --with-gallium-drivers="swr,swrast" --with-gnu-ld --with-osmesa-bits=8 --with-swr-arch="CORE_AVX2" And the compilation finally fails because of unresolved references in the llvm library (v3.7.0): ../../../../src/gallium/drivers/swr/.libs/libmesaswr.a(builder_gen.o):(.data.rel.ro._ZTIN4llvm15InsertValueInstE[_ZTIN4llvm15InsertValueInstE]+0x10): undefined reference to `typeinfo for llvm::Instruction' ../../../../src/gallium/drivers/swr/.libs/libmesaswr.a(builder_gen.o):(.data.rel.ro._ZTIN4llvm17GetElementPtrInstE[_ZTIN4llvm17GetElementPtrInstE]+0x10): undefined reference to `typeinfo for llvm::Instruction' ../../../../src/gallium/drivers/swr/.libs/libmesaswr.a(builder_gen.o):(.data.rel.ro._ZTIN4llvm8ICmpInstE[_ZTIN4llvm8ICmpInstE]+0x10): undefined reference to `typeinfo for llvm::CmpInst' ../../../../src/gallium/drivers/swr/.libs/libmesaswr.a(builder_gen.o):(.data.rel.ro._ZTIN4llvm8FCmpInstE[_ZTIN4llvm8FCmpInstE]+0x10): undefined reference to `typeinfo for llvm::CmpInst' ../../../../src/gallium/drivers/swr/.libs/libmesaswr.a(builder_gen.o):(.data.rel.ro._ZTIN4llvm7PHINodeE[_ZTIN4llvm7PHINodeE]+0x10): undefined reference to `typeinfo for llvm::Instruction' ../../../../src/gallium/drivers/swr/.libs/libmesaswr.a(builder_gen.o):(.data.rel.ro._ZTIN4llvm10SelectInstE[_ZTIN4llvm10SelectInstE]+0x10): undefined reference to `typeinfo for llvm::Instruction' ../../../../src/gallium/drivers/swr/.libs/libmesaswr.a(builder_gen.o):(.data.rel.ro._ZTIN4llvm9VAArgInstE[_ZTIN4llvm9VAArgInstE]+0x10): undefined reference to `typeinfo for llvm::UnaryInstruction' ../../../../src/gallium/drivers/swr/.libs/libmesaswr.a(builder_gen.o):(.data.rel.ro._ZTIN4llvm16ExtractValueInstE[_ZTIN4llvm16ExtractValueInstE]+0x10): undefined reference to `typeinfo for llvm::UnaryInstruction' collect2: error: ld returned 1 exit status As far as I understood, openSWR is meant as a replacement for the libGL.so library, so I am wondering if my intents are doomed to failure because it is not meant to be used as a replacement for libOSMESA.so? Any hints would be much appreciated. Anyway, I am already happy that the new ParaView release is already a good chunk faster the 4.x series and I can' t wait to have to test the final released version. Any comments welcome. Cheers, Frank. -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Donnerstag, 10. Dezember 2015 18:19 To: Albina, Frank Cc: paraview at paraview.org Subject: Re: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5 > ./configure --enable-64-bit --enable-texture-float --enable-osmesa > --disable-egl --disable-xorg --disable-xvmc --disable-opencl > --disable-glx --disable-dri --disable-va --disable-shared-glapi > --enable-gallium-llvm=no --with-gnu-ld --with-osmesa-bits=8 > --disable-vdpau --enable-dependency-tracking --with-gallium-drivers=?? --with-dri-drivers=?? > --with-egl-platforms=?? Frank, One thing I noticed is that you're not using LLVM. Using the new rendering backend without LLVM is not recommended at all. It will be painfully slow since the new rendering backend no longer uses fixed pipeline and it has to process GLSL code. You should stick with llvmpipe. I used the following for OSMesa build with Mesa 11.0.4. Hope that helps. You still need the MESA_GL_VERSION_OVERRIDE flag that Aashish mentioned. ./configure --disable-xvmc --disable-glx --disable-dri --with-dri-drivers= --with-gallium-drivers=swrast --enable-texture-float --disable-egl --with-egl-platforms= --enable-gallium-osmesa --enable-gallium-llvm=yes --prefix=/opt/apps/mesa-11.0.4/llvm-osmesa -------------- next part -------------- A non-text attachment was scrubbed... Name: 1.jpg Type: image/jpeg Size: 181445 bytes Desc: 1.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2.jpg Type: image/jpeg Size: 185539 bytes Desc: 2.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3.jpg Type: image/jpeg Size: 153915 bytes Desc: 3.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 4.jpg Type: image/jpeg Size: 66416 bytes Desc: 4.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 5.jpg Type: image/jpeg Size: 197494 bytes Desc: 5.jpg URL: From cyrcyr123 at gmail.com Wed Dec 23 10:28:21 2015 From: cyrcyr123 at gmail.com (=?gb18030?B?s8Li+ci7?=) Date: Wed, 23 Dec 2015 23:28:21 +0800 Subject: [Paraview] question about integrate function(for Schlieren image) Message-ID: Dear Paraview group? I'm a student who use paraview for openfoam data. Now I'm dealing with a problem about 3D Schlieren image: For 2D Schlieren image, it's easy just to use a partial derivative for the density, for 3D however, may need a integral function that integrate volume derivative data through one direction into a plane. I found that the 'volume rendering' does the similar job, but I need to accumulate the data by the direction instead of accumulating the color. Also, I found a filter called 'integrate variables' yet I don't know how to use it or whether it can integrate all the volume into a plane. Is there any kind of filter that I can use to get the results for the current version? or any suggestions on how I should manage to custom this filter? I would be so pleased if I can have your reply. Best wishes! Yiran Chen Center for Combustion Energy Tsinghua Univerisity -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Dec 23 10:56:35 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 23 Dec 2015 10:56:35 -0500 Subject: [Paraview] ANN: ParaView 5.0.0-RC3 now available for download Message-ID: Folks, ParaView 5.0.0-RC3 is now available for download[1]. Checkout the release notes on the Kitware blog [2]. - The ParaView team [1] http://www.paraview.org/download/ [2] http://kitware.com/blog/home/post/998 From cyndyb at email.arizona.edu Wed Dec 23 12:00:58 2015 From: cyndyb at email.arizona.edu (Hart, Cynthia Joyce - (cyndyb)) Date: Wed, 23 Dec 2015 17:00:58 +0000 Subject: [Paraview] OpenGL issues trying to run in parallel from an iMac (OSX) Message-ID: <204CD21E-0894-4495-A3E1-910BE1F0B419@email.arizona.edu> Hi folks - I?m new to Paraview, and trying to run it in parallel on our Linux based HPC cluster here at the University of Arizona. This is something we can successfully do from Windows, but not, for some odd reason, from a Mac running OS X with Xquartz as the X server. This is the error I get, after the Paraview GUI appears for an instant on my local screen, from the HPC cluster, then it dies: ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 382 vtkXOpenGLRenderWindow (0x4412ee0): Could not find a decent visual ERROR: In /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 382 vtkXOpenGLRenderWindow (0x4412ee0): Could not find a decent visual X Error: BadValue (integer parameter out of range for operation) 2 Extension: 150 (Uknown extension) Minor opcode: 3 (Unknown request) Resource id: 0x22 ERROR: In /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 621 vtkXOpenGLRenderWindow (0x4412ee0): Cannot create GLX context. Aborting. Any ideas what?s going on, here, and how I might fix it? Thanks, Cynthia -------------- next part -------------- An HTML attachment was scrubbed... URL: From lenny at intuitivemachines.com Wed Dec 23 17:33:50 2015 From: lenny at intuitivemachines.com (Leonard Cassady) Date: Wed, 23 Dec 2015 16:33:50 -0600 Subject: [Paraview] Paraview 4.4 Openfoam native reader decomposed read issue Message-ID: Hi, I've recently upgraded to Openfoam 3.0 and installed paraview 4.4. To speed up reading, I'm using pvserver in parallel (with mpirun) and open the openfoam solution with the native openfoam reader as a "decomposed case". I was able to visualize scalar data as expected. I was not able to render the vector velocity data "U". It just doesn't show up as an option for coloring surfaces or to apply filters to. Is this a bug in paraview, or am I doing something wrong? Above is my main question. Below are general questions regarding paraview performance. As you may know, Openfoam creates directories for each processor (say 192) when solving the case in parallel. It requires the user to run the same number of parallel processes (mpirun -np 192 -parallel) as there are processor directories. Does pvserver require the user to also run the same number of processes as there are processor directories? Is pvserver (when run in parallel) smart enough to not open every data file on every process for the native openfoam reader, but to smartly allocate the directories to different instances? (I know that if I open a "reconstructed case" with pvserver running in parallel each instance of pvserver opens the same file and greatly slows the system and overloads ram.) I believe that my computer has good enough graphics processors to handle rendering. Once I load in a data set I can re-orient and re-color and slice very fast. I also believe that I can open and read the data files quickly ( about 230 MB/s read rate for my large files). I believe that the slowest part of my data processing is the step between reading and rendering. It also takes a long time to apply complicated filters like stream lines. How can I speed up this part of my visualization? I have multiple computers and one of them is much faster at analysis and I can't figure out why. -- Leonard Cassady PhD Senior Development Engineer Intuitive Machines Cell: 281-755-2553 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wideli at hotmail.com Wed Dec 23 18:22:20 2015 From: wideli at hotmail.com (wide li) Date: Wed, 23 Dec 2015 23:22:20 +0000 Subject: [Paraview] Xdmf format and the contour plot Message-ID: Hi there, I have a basic question about the contour and stream line plots in ParaView. When I load my Xdmf file to the ParaView, neither of the contour nor streamline filters does function. I wonder WHY it is so and HOW I can solve this problem. At the moment, I really have no clue at all. The ParaView (5.0.0-RC1) is compiled and installed on Mac (El Capitan). In ccmake, I switched on PARAVIEW_BUILD_QT_GUI ON PARAVIEW_ENABLE_CATALYST ON PARAVIEW_ENABLE_FFMPEG ON PARAVIEW_ENABLE_PYTHON ON PARAVIEW_USE_MPI ON VTK_USE_LARGE_DATA ON. Chosen by ParaView itself, all Modules are not activated except, Module_vtkWrappingPythonCore ON. Thanks very much in advance. Li PS. Here is my Xdmf file: ./../DATA/Coords.h5:/X ./../DATA/Coords.h5:/Y ./../DATA/Coords.h5:/Z ./../DATA/Field0.h5:/Br ./../DATA/Field0.h5:/Bt ./../DATA/Field0.h5:/Bp -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.gallagher at gatech.edu Wed Dec 23 18:52:33 2015 From: tim.gallagher at gatech.edu (Tim Gallagher) Date: Wed, 23 Dec 2015 18:52:33 -0500 (EST) Subject: [Paraview] Xdmf format and the contour plot In-Reply-To: Message-ID: <1745549061.20991557.1450914753127.JavaMail.root@mail.gatech.edu> Apply a CellDataToPointData filter after you load your dataset and before you try to use the contour or stream line filters. They both require node-based data but you are providing cell-centered data. Tim ----- Original Message ----- From: "wide li" To: paraview at paraview.org Sent: Wednesday, December 23, 2015 6:22:20 PM Subject: [Paraview] Xdmf format and the contour plot Hi there, I have a basic question about the contour and stream line plots in ParaView. When I load my Xdmf file to the ParaView, neither of the contour nor streamline filters does function. I wonder WHY it is so and HOW I can solve this problem. At the moment, I really have no clue at all. The ParaView (5.0.0-RC1) is compiled and installed on Mac (El Capitan). In ccmake, I switched on PARAVIEW_BUILD_QT_GUI ON PARAVIEW_ENABLE_CATALYST ON PARAVIEW_ENABLE_FFMPEG ON PARAVIEW_ENABLE_PYTHON ON PARAVIEW_USE_MPI ON VTK_USE_LARGE_DATA ON. Chosen by ParaView itself, all Modules are not activated except, Module_vtkWrappingPythonCore ON. Thanks very much in advance. Li PS. Here is my Xdmf file: ./../DATA/Coords.h5:/X ./../DATA/Coords.h5:/Y ./../DATA/Coords.h5:/Z ./../DATA/Field0.h5:/Br ./../DATA/Field0.h5:/Bt ./../DATA/Field0.h5:/Bp _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From wideli at hotmail.com Thu Dec 24 07:30:17 2015 From: wideli at hotmail.com (wide li) Date: Thu, 24 Dec 2015 12:30:17 +0000 Subject: [Paraview] Xdmf format and the contour plot In-Reply-To: <1745549061.20991557.1450914753127.JavaMail.root@mail.gatech.edu> References: , <1745549061.20991557.1450914753127.JavaMail.root@mail.gatech.edu> Message-ID: Hi Tim, Thanks very much for the hint. I have tried both approaches. 1. Amendmenting of my Xdmf and HDF5 files using "Node" data as the input. 2. Applying CellDataToPointData filter first as ParaView reads in "Cell" data. Unfortunately, in either way, I could not have the Contour and Streamline filters working. I wonder do I still miss some key ingredient? Li Date: Wed, 23 Dec 2015 18:52:33 -0500 From: tim.gallagher at gatech.edu To: wideli at hotmail.com CC: paraview at paraview.org Subject: Re: [Paraview] Xdmf format and the contour plot Apply a CellDataToPointData filter after you load your dataset and before you try to use the contour or stream line filters. They both require node-based data but you are providing cell-centered data. Tim From: "wide li" To: paraview at paraview.org Sent: Wednesday, December 23, 2015 6:22:20 PM Subject: [Paraview] Xdmf format and the contour plot Hi there, I have a basic question about the contour and stream line plots in ParaView. When I load my Xdmf file to the ParaView, neither of the contour nor streamline filters does function. I wonder WHY it is so and HOW I can solve this problem. At the moment, I really have no clue at all. The ParaView (5.0.0-RC1) is compiled and installed on Mac (El Capitan). In ccmake, I switched on PARAVIEW_BUILD_QT_GUI ON PARAVIEW_ENABLE_CATALYST ON PARAVIEW_ENABLE_FFMPEG ON PARAVIEW_ENABLE_PYTHON ON PARAVIEW_USE_MPI ON VTK_USE_LARGE_DATA ON. Chosen by ParaView itself, all Modules are not activated except, Module_vtkWrappingPythonCore ON. Thanks very much in advance. Li PS. Here is my Xdmf file: ./../DATA/Coords.h5:/X ./../DATA/Coords.h5:/Y ./../DATA/Coords.h5:/Z ./../DATA/Field0.h5:/Br ./../DATA/Field0.h5:/Bt ./../DATA/Field0.h5:/Bp _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From oshima at eng.niigata-u.ac.jp Fri Dec 25 12:45:50 2015 From: oshima at eng.niigata-u.ac.jp (Takuya OSHIMA) Date: Sat, 26 Dec 2015 02:45:50 +0900 =?iso-2022-jp?B?KBskQkVsNX4bKEIgKBskQkk4PWA7fhsoQikp?= Subject: [Paraview] Paraview 4.4 Openfoam native reader decomposed read issue In-Reply-To: References: Message-ID: <20151226.024550.199955112.oshima@eng.niigata-u.ac.jp> Hi Leonard, I am not using OpenFOAM recently so this is what I can only answer: > Is pvserver (when > run in parallel) smart enough to not open every data file on every process for > the native openfoam reader, but to smartly allocate the directories to > different instances? Yes. For the allocation strategy, see slide 7 of [1]. And if you choose "Reconstructed Case" and if the reader still works as intended, the whole recousructed case should be loaded only by process 0. [1] http://www.opencae.jp/data/OpenSourceCAEWorkshop/200811/slides/OpenSourceCAEWorkshop200811Ohshima2.pdf Takuya OSHIMA, Ph.D. Faculty of Engineering, Niigata University 8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN From: Leonard Cassady Subject: [Paraview] Paraview 4.4 Openfoam native reader decomposed read issue Date: Wed, 23 Dec 2015 16:33:50 -0600 > Hi, ?? > > ? I've recently upgraded to Openfoam 3.0 and installed paraview 4.4.? To speed > up reading, I'm using pvserver in parallel (with mpirun) and open the openfoam > solution with the native openfoam reader as a "decomposed case". ? > ? I was able to visualize scalar data as expected.? I was not able to render > the vector velocity data "U". ? It just doesn't show up as an option for > coloring surfaces or to apply filters to.? Is this a bug in paraview, or am I > doing something wrong?? > > ? Above is my main question.? Below are general questions regarding paraview > performance.? > > ? As you may know, Openfoam creates directories for each processor (say 192) > when solving the case in parallel. It requires the user to run the same number > of parallel processes (mpirun -np 192 -parallel) ?as there > are processor directories.? Does pvserver require the user to also run the > same number of processes as there are processor directories? Is pvserver (when > run in parallel) smart enough to not open every data file on every process for > the native openfoam reader, but to smartly allocate the directories to > different instances? ?(I know that if I open a "reconstructed case" with > pvserver running in parallel each instance of pvserver opens the same file and > greatly slows the system and overloads ram.) ? > > ? ?I believe that my computer has good enough graphics processors to handle > rendering.? Once I load in a data set I can re-orient and re-color and slice > very fast.? I also believe that I can open and read the data files quickly ( > about 230 MB/s read rate for my large files).? I believe that the slowest part > of my data processing is the step between reading and rendering.? It also > takes a long time to apply complicated filters like stream lines.? How can I > speed up this part of my visualization?? I have multiple computers and one of > them is much faster at analysis and I can't figure out why. ? > ?? > > -- > Leonard Cassady PhD > Senior Development Engineer > Intuitive Machines > Cell: 281-755-2553? > From andy.bauer at kitware.com Mon Dec 28 08:16:49 2015 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 28 Dec 2015 08:16:49 -0500 Subject: [Paraview] question about integrate function(for Schlieren image) In-Reply-To: References: Message-ID: Hi, This is a fairly complex algorithm to do in parallel for general data sets. For something like a vtkImageData or vtkRectilinearGrid though it should be manageable. One option would be to use the Resample with Dataset filter to project onto a vtkImageData if you have a vtkUnstructuredGrid or vtkStructuredGrid and then do the integration in one direction. The Integrate Variables filter always integrates over the entire data set. Best, Andy On Wed, Dec 23, 2015 at 10:28 AM, ??? wrote: > Dear Paraview group? > > I'm a student who use paraview for openfoam data. > Now I'm dealing with a problem about 3D Schlieren image: > For 2D Schlieren image, it's easy just to use a partial derivative > for the density, for 3D however, > may need a integral function that integrate volume derivative data through > one direction into a plane. > > I found that the 'volume rendering' does the similar job, but I > need to accumulate the data by the direction > instead of accumulating the color. Also, I found a filter called > 'integrate variables' yet I don't know how to use it or > whether it can integrate all the volume into a plane. > Is there any kind of filter that I can use to get the results for > the current version? or any suggestions on > how I should manage to custom this filter? > > I would be so pleased if I can have your reply. > > Best wishes! > > Yiran Chen > Center for Combustion Energy > Tsinghua Univerisity > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lenny at intuitivemachines.com Mon Dec 28 10:39:58 2015 From: lenny at intuitivemachines.com (Leonard Cassady) Date: Mon, 28 Dec 2015 09:39:58 -0600 Subject: [Paraview] 4.4.0 Native Openfoam decomposed case reader bug Message-ID: Hello, I believe that there is a bug with the openfoam reader for decomposed cases. The reader cannot open all of the "U" files in the decomposed directories. For some reason, not all of the files cause the errors - only one divisible by the number of parallel processes I'm running with pvserver. I get the errors when running 24 processes (on case decomposed into 192 directories): ERROR: In /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, line 6497 vtkOpenFOAMReaderPrivate (0xd0c3d4e0): Error reading line 813 of /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor0/7.38/U: Expected a number, found ( ERROR: In /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, line 6497 vtkOpenFOAMReaderPrivate (0xd0c44920): Error reading line 817 of /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor24/7.38/U: Expected a number, found ( ERROR: In /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, line 6497 vtkOpenFOAMReaderPrivate (0x2738e60): Error reading line 836 of /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor48/7.38/U: Expected a number, found ( ERROR: In /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, line 6497 vtkOpenFOAMReaderPrivate (0x4bc99a0): Error reading line 845 of /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor72/7.38/U: Expected a number, found ( ERROR: In /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, line 6497 vtkOpenFOAMReaderPrivate (0x2738440): Error reading line 820 of /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor96/7.38/U: Expected a number, found ( ERROR: In /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, line 6497 vtkOpenFOAMReaderPrivate (0xd0f954c0): Error reading line 879 of /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor120/7.38/U: Expected a number, found ( ERROR: In /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, line 6497 vtkOpenFOAMReaderPrivate (0xd0c8a900): Error reading line 878 of /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor144/7.38/U: Expected a number, found ( ERROR: In /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, line 6497 vtkOpenFOAMReaderPrivate (0xd0ecfbc0): Error reading line 976 of /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor168/7.38/U: Expected a number, found ( How do I submit a bug? -- Leonard Cassady PhD Senior Development Engineer Intuitive Machines Cell: 281-755-2553 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lenny at intuitivemachines.com Mon Dec 28 11:08:21 2015 From: lenny at intuitivemachines.com (Leonard Cassady) Date: Mon, 28 Dec 2015 10:08:21 -0600 Subject: [Paraview] Paraview 4.4 Openfoam native reader decomposed read issue In-Reply-To: <20151226.024550.199955112.oshima@eng.niigata-u.ac.jp> References: <20151226.024550.199955112.oshima@eng.niigata-u.ac.jp> Message-ID: Takuya, Thank you for your response. I now see how pvserver (when run in parallel) opens up the decomposed data files. To the group, I have sent out another email detailing the bug in native paraview openfoam reader. My case is about 20 million cells and the reconstructed file sizes are 150 MB for scalar data and 500 MB for vector data. I still have questions about data processing. Are filters processed on the client or server? Are complicated filters (such as stream lines that cross boundaries of the parallel (decomposed) solution) faster when pvserver is run in parallel? I have re-compiled paraview 4.4.0 to be mpi-enabled. I have selected the "enable Auto MPI" with 24 processes (same number as my cores). If I open a serial (reconstructed) solution, paraview takes much longer (>10x) to open a case. Paraview is slightly slower when opening a decomposed case with the 24 processes. What should I know to improve the performance of paraview? Thanks, Lenny On Fri, Dec 25, 2015 at 11:45 AM, Takuya OSHIMA wrote: > Hi Leonard, > > I am not using OpenFOAM recently so this is what I can only answer: > > > Is pvserver (when > > run in parallel) smart enough to not open every data file on every > process for > > the native openfoam reader, but to smartly allocate the directories to > > different instances? > > Yes. For the allocation strategy, see slide 7 of [1]. And if you > choose "Reconstructed Case" and if the reader still works as intended, > the whole recousructed case should be loaded only by process 0. > > [1] > http://www.opencae.jp/data/OpenSourceCAEWorkshop/200811/slides/OpenSourceCAEWorkshop200811Ohshima2.pdf > > Takuya OSHIMA, Ph.D. > Faculty of Engineering, Niigata University > 8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN > > From: Leonard Cassady > Subject: [Paraview] Paraview 4.4 Openfoam native reader decomposed read > issue > Date: Wed, 23 Dec 2015 16:33:50 -0600 > > > Hi, > > > > I've recently upgraded to Openfoam 3.0 and installed paraview 4.4. To > speed > > up reading, I'm using pvserver in parallel (with mpirun) and open the > openfoam > > solution with the native openfoam reader as a "decomposed case". > > I was able to visualize scalar data as expected. I was not able to > render > > the vector velocity data "U". It just doesn't show up as an option for > > coloring surfaces or to apply filters to. Is this a bug in paraview, or > am I > > doing something wrong? > > > > Above is my main question. Below are general questions regarding > paraview > > performance. > > > > As you may know, Openfoam creates directories for each processor (say > 192) > > when solving the case in parallel. It requires the user to run the same > number > > of parallel processes (mpirun -np 192 -parallel) as > there > > are processor directories. Does pvserver require the user to also run > the > > same number of processes as there are processor directories? Is pvserver > (when > > run in parallel) smart enough to not open every data file on every > process for > > the native openfoam reader, but to smartly allocate the directories to > > different instances? (I know that if I open a "reconstructed case" with > > pvserver running in parallel each instance of pvserver opens the same > file and > > greatly slows the system and overloads ram.) > > > > I believe that my computer has good enough graphics processors to > handle > > rendering. Once I load in a data set I can re-orient and re-color and > slice > > very fast. I also believe that I can open and read the data files > quickly ( > > about 230 MB/s read rate for my large files). I believe that the > slowest part > > of my data processing is the step between reading and rendering. It also > > takes a long time to apply complicated filters like stream lines. How > can I > > speed up this part of my visualization? I have multiple computers and > one of > > them is much faster at analysis and I can't figure out why. > > > > > > -- > > Leonard Cassady PhD > > Senior Development Engineer > > Intuitive Machines > > Cell: 281-755-2553 > > > -- Leonard Cassady PhD Senior Development Engineer Intuitive Machines Cell: 281-755-2553 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bflandard at gmail.com Mon Dec 28 17:17:18 2015 From: bflandard at gmail.com (Bob Flandard) Date: Mon, 28 Dec 2015 22:17:18 +0000 Subject: [Paraview] Scalar bar ranges jump around Message-ID: Hello, Sorry if this is old news. The colour ranges on the scalar bar should remain equally spaced, but with the transfer function reset mode set to "clamp and update every timestep", they jump about during a time series animation. Attached is a state file that demonstrates the issue (created with PV v5.0 RC3). Please load it and click the play button, or manually click through time steps. Thanks, Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ScalarBarIssue.zip Type: application/zip Size: 17915 bytes Desc: not available URL: From kmorel at sandia.gov Tue Dec 29 12:49:53 2015 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 29 Dec 2015 17:49:53 +0000 Subject: [Paraview] Scalar bar ranges jump around In-Reply-To: References: Message-ID: Bob, I am confused. The "clamp and update every timestep" feature is what turns on the behavior of changing the scale of every timestep. Just turn it off. -Ken Sent from my iPad so blame autocorrect. > On Dec 28, 2015, at 3:17 PM, Bob Flandard wrote: > > Hello, > > Sorry if this is old news. > > The colour ranges on the scalar bar should remain equally spaced, but with the transfer function reset mode set to "clamp and update every timestep", they jump about during a time series animation. > > Attached is a state file that demonstrates the issue (created with PV v5.0 RC3). Please load it and click the play button, or manually click through time steps. > > Thanks, Bob > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From bflandard at gmail.com Tue Dec 29 14:46:20 2015 From: bflandard at gmail.com (Bob Flandard) Date: Tue, 29 Dec 2015 19:46:20 +0000 Subject: [Paraview] Scalar bar ranges jump around In-Reply-To: References: Message-ID: Hello Ken, Maybe you are seeing something different to what I see when playing the different time steps. I see the relative size of each of the discrete colours in the scalar bar, changing in a random way. The ticks don't move and the numbers change appropriately, but the length of each colour is not constant. I've attached an image that shows the scalar bar from three time step of the data set in the state file I posted yesterday. One (t=96) has a good scalar bar and the other two are wrong. Just to clarify, I'm using ParaView 5.0 RC3 64bit on a Windows 7 machine. Thanks for your help, Bob On 29 December 2015 at 17:49, Moreland, Kenneth wrote: > Bob, > > I am confused. The "clamp and update every timestep" feature is what turns > on the behavior of changing the scale of every timestep. Just turn it off. > > -Ken > > Sent from my iPad so blame autocorrect. > > > On Dec 28, 2015, at 3:17 PM, Bob Flandard wrote: > > > > Hello, > > > > Sorry if this is old news. > > > > The colour ranges on the scalar bar should remain equally spaced, but > with the transfer function reset mode set to "clamp and update every > timestep", they jump about during a time series animation. > > > > Attached is a state file that demonstrates the issue (created with PV > v5.0 RC3). Please load it and click the play button, or manually click > through time steps. > > > > Thanks, Bob > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: BadScalarBar.png Type: image/png Size: 55421 bytes Desc: not available URL: From bflandard at gmail.com Tue Dec 29 16:07:47 2015 From: bflandard at gmail.com (Bob Flandard) Date: Tue, 29 Dec 2015 21:07:47 +0000 Subject: [Paraview] Scalar bar ranges jump around In-Reply-To: References: Message-ID: Hello Ken, Maybe you are seeing something different to what I see when playing the different time steps. I see the relative size of each of the discrete colours in the scalar bar, changing in a random way. The ticks don't move and the numbers change appropriately, but the length of each colour is not constant. I've attached an image that shows the scalar bar from three time step of the data set in the state file I posted yesterday. One (t=96) has a good scalar bar and the other two are wrong. Thanks for your help, Bob On 29 December 2015 at 17:49, Moreland, Kenneth wrote: > Bob, > > I am confused. The "clamp and update every timestep" feature is what turns > on the behavior of changing the scale of every timestep. Just turn it off. > > -Ken > > Sent from my iPad so blame autocorrect. > > > On Dec 28, 2015, at 3:17 PM, Bob Flandard wrote: > > > > Hello, > > > > Sorry if this is old news. > > > > The colour ranges on the scalar bar should remain equally spaced, but > with the transfer function reset mode set to "clamp and update every > timestep", they jump about during a time series animation. > > > > Attached is a state file that demonstrates the issue (created with PV > v5.0 RC3). Please load it and click the play button, or manually click > through time steps. > > > > Thanks, Bob > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Dec 29 16:44:09 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 29 Dec 2015 16:44:09 -0500 Subject: [Paraview] Scalar bar ranges jump around In-Reply-To: References: Message-ID: Can you try unchecking the "Automatic Label Format" checkbox on the "Edit Color Legend Parameters" dialog accessible from the "Color Map Editor" panel? I think it's the label formatting that's causing the issue. Utkarsh On Tue, Dec 29, 2015 at 4:07 PM, Bob Flandard wrote: > Hello Ken, > > Maybe you are seeing something different to what I see when playing the > different time steps. I see the relative size of each of the discrete > colours in the scalar bar, changing in a random way. The ticks don't move > and the numbers change appropriately, but the length of each colour is not > constant. I've attached an image that shows the scalar bar from three time > step of the data set in the state file I posted yesterday. One (t=96) has a > good scalar bar and the other two are wrong. > > Thanks for your help, Bob > > On 29 December 2015 at 17:49, Moreland, Kenneth wrote: >> >> Bob, >> >> I am confused. The "clamp and update every timestep" feature is what turns >> on the behavior of changing the scale of every timestep. Just turn it off. >> >> -Ken >> >> Sent from my iPad so blame autocorrect. >> >> > On Dec 28, 2015, at 3:17 PM, Bob Flandard wrote: >> > >> > Hello, >> > >> > Sorry if this is old news. >> > >> > The colour ranges on the scalar bar should remain equally spaced, but >> > with the transfer function reset mode set to "clamp and update every >> > timestep", they jump about during a time series animation. >> > >> > Attached is a state file that demonstrates the issue (created with PV >> > v5.0 RC3). Please load it and click the play button, or manually click >> > through time steps. >> > >> > Thanks, Bob >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From bflandard at gmail.com Tue Dec 29 17:26:35 2015 From: bflandard at gmail.com (Bob Flandard) Date: Tue, 29 Dec 2015 22:26:35 +0000 Subject: [Paraview] Scalar bar ranges jump around In-Reply-To: References: Message-ID: Hello Utkarsh, Thank you for the suggestion. The plot I sent has already implicitly disabled "automatic label format" by only using the "Draw Annotations" and "Automatic Annotation" options, with the options in the "Labels" section unchecked. I tried explicitly unchecking the "Automatic Label Format" as you suggested, but it has no effect in this instance (as expected). Are you able to reproduce the effect from the attached state file? Thanks for your help, Bob On 29 December 2015 at 21:44, Utkarsh Ayachit wrote: > Can you try unchecking the "Automatic Label Format" checkbox on the > "Edit Color Legend Parameters" dialog accessible from the "Color Map > Editor" panel? I think it's the label formatting that's causing the > issue. > > Utkarsh > > On Tue, Dec 29, 2015 at 4:07 PM, Bob Flandard wrote: > > Hello Ken, > > > > Maybe you are seeing something different to what I see when playing the > > different time steps. I see the relative size of each of the discrete > > colours in the scalar bar, changing in a random way. The ticks don't move > > and the numbers change appropriately, but the length of each colour is > not > > constant. I've attached an image that shows the scalar bar from three > time > > step of the data set in the state file I posted yesterday. One (t=96) > has a > > good scalar bar and the other two are wrong. > > > > Thanks for your help, Bob > > > > On 29 December 2015 at 17:49, Moreland, Kenneth > wrote: > >> > >> Bob, > >> > >> I am confused. The "clamp and update every timestep" feature is what > turns > >> on the behavior of changing the scale of every timestep. Just turn it > off. > >> > >> -Ken > >> > >> Sent from my iPad so blame autocorrect. > >> > >> > On Dec 28, 2015, at 3:17 PM, Bob Flandard > wrote: > >> > > >> > Hello, > >> > > >> > Sorry if this is old news. > >> > > >> > The colour ranges on the scalar bar should remain equally spaced, but > >> > with the transfer function reset mode set to "clamp and update every > >> > timestep", they jump about during a time series animation. > >> > > >> > Attached is a state file that demonstrates the issue (created with PV > >> > v5.0 RC3). Please load it and click the play button, or manually click > >> > through time steps. > >> > > >> > Thanks, Bob > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > Search the list archives at: http://markmail.org/search/?q=ParaView > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ScalarBarIssue.zip Type: application/zip Size: 17915 bytes Desc: not available URL: From cory.quammen at kitware.com Tue Dec 29 22:37:47 2015 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 29 Dec 2015 22:37:47 -0500 Subject: [Paraview] 4.4.0 Native Openfoam decomposed case reader bug In-Reply-To: References: Message-ID: Hi Leonard, The ParaView bug tracker is here: http://www.paraview.org/Bug/ It would make it easier to fix the bug if you can provide a perhaps smaller data set that exhibits the bug with your bug report. Thanks, Cory On Mon, Dec 28, 2015 at 10:39 AM, Leonard Cassady < lenny at intuitivemachines.com> wrote: > Hello, > > I believe that there is a bug with the openfoam reader for decomposed > cases. The reader cannot open all of the "U" files in the decomposed > directories. For some reason, not all of the files cause the errors - only > one divisible by the number of parallel processes I'm running with pvserver. > > I get the errors when running 24 processes (on case decomposed into 192 > directories): > > ERROR: In > /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, > line 6497 > > vtkOpenFOAMReaderPrivate (0xd0c3d4e0): Error reading line 813 of > /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor0/7.38/U: > Expected a number, found ( > > > > ERROR: In > /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, > line 6497 > > vtkOpenFOAMReaderPrivate (0xd0c44920): Error reading line 817 of > /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor24/7.38/U: > Expected a number, found ( > > > > ERROR: In > /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, > line 6497 > > vtkOpenFOAMReaderPrivate (0x2738e60): Error reading line 836 of > /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor48/7.38/U: > Expected a number, found ( > > > > ERROR: In > /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, > line 6497 > > vtkOpenFOAMReaderPrivate (0x4bc99a0): Error reading line 845 of > /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor72/7.38/U: > Expected a number, found ( > > > > ERROR: In > /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, > line 6497 > > vtkOpenFOAMReaderPrivate (0x2738440): Error reading line 820 of > /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor96/7.38/U: > Expected a number, found ( > > > > ERROR: In > /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, > line 6497 > > vtkOpenFOAMReaderPrivate (0xd0f954c0): Error reading line 879 of > /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor120/7.38/U: > Expected a number, found ( > > > > ERROR: In > /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, > line 6497 > > vtkOpenFOAMReaderPrivate (0xd0c8a900): Error reading line 878 of > /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor144/7.38/U: > Expected a number, found ( > > > > ERROR: In > /software/OpenFOAM/ThirdParty-3.0.x/ParaView-4.4.0/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, > line 6497 > > vtkOpenFOAMReaderPrivate (0xd0ecfbc0): Error reading line 976 of > /home/lcassady/OpenFOAM/lcassady-3.0.x/run/blowout_LES_10rho2/processor168/7.38/U: > Expected a number, found ( > > > How do I submit a bug? > > -- > Leonard Cassady PhD > Senior Development Engineer > Intuitive Machines > Cell: 281-755-2553 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume.jacquenot at gmail.com Wed Dec 30 09:03:34 2015 From: guillaume.jacquenot at gmail.com (Guillaume Jacquenot) Date: Wed, 30 Dec 2015 15:03:34 +0100 Subject: [Paraview] Use of Python declared variables inside new scripts from ProgrammableSource and/or ProgrammableFilter. Message-ID: I would like to use Python declared variables inside new scripts from ProgrammableSource and/or ProgrammableFilter. Why do I want such a thing? I could simply declared these variables in the code of the script. But what if these variables are to be used by several scripts from ProgrammableSource and/or ProgrammableFilter? Of course, I can serialize variables and pass the serialized data to the scripts, taking special care for float. But, what if I have large data, that are difficult to serialize? So, here is my question: Is there a mechanism to access already defined data inside the scripts of ProgrammableSource and/or ProgrammableFilter? For example, a global scope dict? Do I have to use an external file to store and access data? Below is the example of the Python file I would like to run , where I have defined a 'data' that I want to access inside the script. If I try to directly access 'data', I have a "NameError: global name 'data' is not defined" My data are in fact transformation matrices that will be used to move objects from a ProgrammableFilter. Using the Animation Keyframes are terribly slow. Guillaume Python script: data = .... script=""" instructions to access "data" at run time ... """ scriptRequestInformation=""" ... """ source = ProgrammableSource() source.OutputDataSetType = 'vtkStructuredGrid' source.Script = script source.ScriptRequestInformation = scriptRequestInformation source.PythonPath = '' -------------- next part -------------- An HTML attachment was scrubbed... URL: From christoph.h.woe at gmail.com Wed Dec 30 10:36:26 2015 From: christoph.h.woe at gmail.com (=?windows-1252?Q?Christoph_W=F6lfle?=) Date: Wed, 30 Dec 2015 16:36:26 +0100 Subject: [Paraview] ParaView Nastran Reader Guidelines Message-ID: <60850EB6-80A8-48F5-BC7D-872C80C63D23@gmail.com> Hi all, I am trying to visualize a Nastran model with some basic results from a linear static analysis. Is there any documentation on how to set up appropriate output options in Nastran for ParaView?s Nastran reader? Until now I tried: 1.) Writing the bulk echo and the results to the .f06 -> got ?No data to operate on!? 2.) Writing the bulk echo and the results to standard .pch Punch file -> got the mesh loaded, but not the results 3.) Writing the bulk echo and the results to the .pch as above (loading the model in ParaView first) and the results to an .op2 POST file (default procedure for Patran, Hyperview,...) -> ParaView freezes upon loading the .op2 (the model contains < 1000 grid points, so nothing very big) 4.) Combination of 1.) and 2.) -> again loading the mesh works, but loading the .f06 yields ?No data to operate on!? Could someone please give me a hint on how to load Nastran results? I can absolutely not find any further documentation on this. Best regards, Christoph From ruggiero.guida at gmail.com Wed Dec 30 11:35:15 2015 From: ruggiero.guida at gmail.com (Ruggiero Guida) Date: Wed, 30 Dec 2015 17:35:15 +0100 Subject: [Paraview] ParaviewWeb - Python Script Message-ID: Hi, I use a Python script to run Paraview with predefined settings and automatically load files that are generated by an external application. At the moment I use the '--script' option so that the script is loaded when Paraview is launched. I would like to do something similar with ParaviewWeb. Is this possible? Do I need to modify one of the predefined examples directly to include this feature? Thanks and Happy New Year! Ruggiero -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Dec 30 13:18:27 2015 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 30 Dec 2015 11:18:27 -0700 Subject: [Paraview] ParaviewWeb - Python Script In-Reply-To: References: Message-ID: Hi Ruggiero, It is definitely possible with ParaViewWeb. Either you embedded your initialization code within the Python Script that define the ParaViewWeb server or you can extend the pv_web_visualizer.py one to add a new argument which could be the path to the script you want to run at initialization time and then you make sure you process that arg and run that script before starting the Web server. If you think that feature should be part of the Visualizer application, then you can submit a pull request on our gitlab and assign me as reviewer. Happy new year! Seb On Wed, Dec 30, 2015 at 9:35 AM, Ruggiero Guida wrote: > Hi, > > I use a Python script to run Paraview with predefined settings and > automatically load files that are generated by an external application. At > the moment I use the '--script' option so that the script is loaded when > Paraview is launched. > > I would like to do something similar with ParaviewWeb. Is this possible? > Do I need to modify one of the predefined examples directly to include this > feature? > > Thanks and Happy New Year! > Ruggiero > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruggiero.guida at gmail.com Wed Dec 30 14:24:33 2015 From: ruggiero.guida at gmail.com (Ruggiero Guida) Date: Wed, 30 Dec 2015 20:24:33 +0100 Subject: [Paraview] ParaviewWeb - Python Script In-Reply-To: References: Message-ID: Thanks Sebastian, Sorry for the silly question, but I am not sure how I can run a script on the server once it has been initiated with server.start_webserver(options=args, protocol=_VisualizerServer) I am not very familiar with VTK programming. Thanks Ruggiero On 30 December 2015 at 19:18, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Hi Ruggiero, > > It is definitely possible with ParaViewWeb. Either you embedded your > initialization code within the Python Script that define the ParaViewWeb > server or you can extend the pv_web_visualizer.py one to add a new argument > which could be the path to the script you want to run at initialization > time and then you make sure you process that arg and run that script before > starting the Web server. > > If you think that feature should be part of the Visualizer application, > then you can submit a pull request on our gitlab and assign me as reviewer. > > Happy new year! > > Seb > > On Wed, Dec 30, 2015 at 9:35 AM, Ruggiero Guida > wrote: > >> Hi, >> >> I use a Python script to run Paraview with predefined settings and >> automatically load files that are generated by an external application. At >> the moment I use the '--script' option so that the script is loaded when >> Paraview is launched. >> >> I would like to do something similar with ParaviewWeb. Is this possible? >> Do I need to modify one of the predefined examples directly to include this >> feature? >> >> Thanks and Happy New Year! >> Ruggiero >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Dec 30 15:40:39 2015 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 30 Dec 2015 13:40:39 -0700 Subject: [Paraview] ParaviewWeb - Python Script In-Reply-To: References: Message-ID: It will be ParaView/Python inside .../pv_web_visualizer.py [...] class _VisualizerServer(pv_wamp.PVServerProtocol): @staticmethod def add_arguments(parser): [...] # Add your extra arg here @staticmethod def configure(args): [...] # Extract your arg here def initialize(self): [...] # If script arg has content self.registerVtkWebProtocol(pv_protocols.ParaViewWebStartupRemoteConnection(_VisualizerServer.dsHost, _VisualizerServer.dsPort, _VisualizerServer.rsHost, _VisualizerServer.rsPort, _VisualizerServer.rcPort)) self.registerVtkWebProtocol(pv_protocols.ParaViewWebStartupPluginLoader(_VisualizerServer.plugins)) self.registerVtkWebProtocol(pv_protocols.ParaViewWebFileListing(_VisualizerServer.dataDir, "Home", _VisualizerServer.excludeRegex, _VisualizerServer.groupRegex)) self.registerVtkWebProtocol(pv_protocols.ParaViewWebProxyManager(allowedProxiesFile=_VisualizerServer.proxies, baseDir=_VisualizerServer.dataDir, fileToLoad=_VisualizerServer.fileToLoad, allowUnconfiguredReaders=_VisualizerServer.allReaders)) self.registerVtkWebProtocol(pv_protocols.ParaViewWebColorManager(pathToColorMaps=_VisualizerServer.colorPalette)) self.registerVtkWebProtocol(pv_protocols.ParaViewWebMouseHandler()) self.registerVtkWebProtocol(pv_protocols.ParaViewWebViewPort()) self.registerVtkWebProtocol(pv_protocols.ParaViewWebViewPortImageDelivery()) self.registerVtkWebProtocol(pv_protocols.ParaViewWebViewPortGeometryDelivery()) self.registerVtkWebProtocol(pv_protocols.ParaViewWebTimeHandler()) self.registerVtkWebProtocol(pv_protocols.ParaViewWebSelectionHandler()) self.registerVtkWebProtocol(pv_protocols.ParaViewWebWidgetManager()) self.registerVtkWebProtocol(pv_protocols.ParaViewWebKeyValuePairStore()) self.registerVtkWebProtocol(pv_protocols.ParaViewWebSaveData(baseSavePath=_VisualizerServer.saveDataDir)) # Update authentication key to use self.updateSecret(_VisualizerServer.authKey) # Disable interactor-based render calls simple.GetRenderView().EnableRenderOnInteraction = 0 On Wed, Dec 30, 2015 at 12:24 PM, Ruggiero Guida wrote: > Thanks Sebastian, > > Sorry for the silly question, but I am not sure how I can run a script on > the server once it has been initiated with > > server.start_webserver(options=args, protocol=_VisualizerServer) > > I am not very familiar with VTK programming. > > Thanks > Ruggiero > > > > On 30 December 2015 at 19:18, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> Hi Ruggiero, >> >> It is definitely possible with ParaViewWeb. Either you embedded your >> initialization code within the Python Script that define the ParaViewWeb >> server or you can extend the pv_web_visualizer.py one to add a new argument >> which could be the path to the script you want to run at initialization >> time and then you make sure you process that arg and run that script before >> starting the Web server. >> >> If you think that feature should be part of the Visualizer application, >> then you can submit a pull request on our gitlab and assign me as reviewer. >> >> Happy new year! >> >> Seb >> >> On Wed, Dec 30, 2015 at 9:35 AM, Ruggiero Guida > > wrote: >> >>> Hi, >>> >>> I use a Python script to run Paraview with predefined settings and >>> automatically load files that are generated by an external application. At >>> the moment I use the '--script' option so that the script is loaded when >>> Paraview is launched. >>> >>> I would like to do something similar with ParaviewWeb. Is this possible? >>> Do I need to modify one of the predefined examples directly to include this >>> feature? >>> >>> Thanks and Happy New Year! >>> Ruggiero >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Dec 30 15:42:26 2015 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 30 Dec 2015 13:42:26 -0700 Subject: [Paraview] ParaviewWeb - Python Script In-Reply-To: References: Message-ID: Oops the previous mail was sent before I finished the edit... Sorry... It will be ParaView/Python inside .../pv_web_visualizer.py [...] class _VisualizerServer(pv_wamp.PVServerProtocol): @staticmethod def add_arguments(parser): [...] # Add your extra arg here @staticmethod def configure(args): [...] # Extract your arg here def initialize(self): [...] # If script arg has content the eval the script here.. On Wed, Dec 30, 2015 at 12:24 PM, Ruggiero Guida wrote: > Thanks Sebastian, > > Sorry for the silly question, but I am not sure how I can run a script on > the server once it has been initiated with > > server.start_webserver(options=args, protocol=_VisualizerServer) > > I am not very familiar with VTK programming. > > Thanks > Ruggiero > > > > On 30 December 2015 at 19:18, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> Hi Ruggiero, >> >> It is definitely possible with ParaViewWeb. Either you embedded your >> initialization code within the Python Script that define the ParaViewWeb >> server or you can extend the pv_web_visualizer.py one to add a new argument >> which could be the path to the script you want to run at initialization >> time and then you make sure you process that arg and run that script before >> starting the Web server. >> >> If you think that feature should be part of the Visualizer application, >> then you can submit a pull request on our gitlab and assign me as reviewer. >> >> Happy new year! >> >> Seb >> >> On Wed, Dec 30, 2015 at 9:35 AM, Ruggiero Guida > > wrote: >> >>> Hi, >>> >>> I use a Python script to run Paraview with predefined settings and >>> automatically load files that are generated by an external application. At >>> the moment I use the '--script' option so that the script is loaded when >>> Paraview is launched. >>> >>> I would like to do something similar with ParaviewWeb. Is this possible? >>> Do I need to modify one of the predefined examples directly to include this >>> feature? >>> >>> Thanks and Happy New Year! >>> Ruggiero >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Dec 30 16:53:33 2015 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 30 Dec 2015 16:53:33 -0500 Subject: [Paraview] Scalar bar ranges jump around In-Reply-To: References: Message-ID: Ah, the issue seems to be with "Automatic Annotations". Cory, can you check this out when you get the chance? I am not entirely sure how automatic annotations should work here, if at all. Utkarsh On Tue, Dec 29, 2015 at 5:26 PM, Bob Flandard wrote: > Hello Utkarsh, > > Thank you for the suggestion. The plot I sent has already implicitly > disabled "automatic label format" by only using the "Draw Annotations" and > "Automatic Annotation" options, with the options in the "Labels" section > unchecked. I tried explicitly unchecking the "Automatic Label Format" as you > suggested, but it has no effect in this instance (as expected). > > Are you able to reproduce the effect from the attached state file? > > Thanks for your help, Bob > > > > On 29 December 2015 at 21:44, Utkarsh Ayachit > wrote: >> >> Can you try unchecking the "Automatic Label Format" checkbox on the >> "Edit Color Legend Parameters" dialog accessible from the "Color Map >> Editor" panel? I think it's the label formatting that's causing the >> issue. >> >> Utkarsh >> >> On Tue, Dec 29, 2015 at 4:07 PM, Bob Flandard wrote: >> > Hello Ken, >> > >> > Maybe you are seeing something different to what I see when playing the >> > different time steps. I see the relative size of each of the discrete >> > colours in the scalar bar, changing in a random way. The ticks don't >> > move >> > and the numbers change appropriately, but the length of each colour is >> > not >> > constant. I've attached an image that shows the scalar bar from three >> > time >> > step of the data set in the state file I posted yesterday. One (t=96) >> > has a >> > good scalar bar and the other two are wrong. >> > >> > Thanks for your help, Bob >> > >> > On 29 December 2015 at 17:49, Moreland, Kenneth >> > wrote: >> >> >> >> Bob, >> >> >> >> I am confused. The "clamp and update every timestep" feature is what >> >> turns >> >> on the behavior of changing the scale of every timestep. Just turn it >> >> off. >> >> >> >> -Ken >> >> >> >> Sent from my iPad so blame autocorrect. >> >> >> >> > On Dec 28, 2015, at 3:17 PM, Bob Flandard >> >> > wrote: >> >> > >> >> > Hello, >> >> > >> >> > Sorry if this is old news. >> >> > >> >> > The colour ranges on the scalar bar should remain equally spaced, but >> >> > with the transfer function reset mode set to "clamp and update every >> >> > timestep", they jump about during a time series animation. >> >> > >> >> > Attached is a state file that demonstrates the issue (created with PV >> >> > v5.0 RC3). Please load it and click the play button, or manually >> >> > click >> >> > through time steps. >> >> > >> >> > Thanks, Bob >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Please keep messages on-topic and check the ParaView Wiki at: >> >> > http://paraview.org/Wiki/ParaView >> >> > >> >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > > > From n_maftoon at yahoo.com Wed Dec 30 16:57:33 2015 From: n_maftoon at yahoo.com (Nima Maftoon) Date: Wed, 30 Dec 2015 21:57:33 +0000 (UTC) Subject: [Paraview] Visualizing complex vibration modes References: <218221950.4166291.1451512653571.JavaMail.yahoo.ref@mail.yahoo.com> Message-ID: <218221950.4166291.1451512653571.JavaMail.yahoo@mail.yahoo.com> Hello all, I am trying to visualize complex vibration modes with Paraview. Unlike in a real mode, points in a complex mode have different phases. Please see previous discussions on this subject:http://www.salome-platform.org/forum/forum_10/587894859http://www.paraview.org/pipermail/paraview/2011-December/023538.html The Paraview version included in Salome has a macro for modal visualization. I've put that macro and a MED file containing both real and imaginary parts of the mode shapes and another two other MED files for separate real and imaginary parts in the following shared folder. http://1drv.ms/1TqggEK The real mode animation in the mode macro is based on applying ExtractSurface(), ScaleVector(), WarpByVector() in cascade and animating the ScaleVector using a sinusoidal interpolation in a CompositeKeyFrame. However for a complex mode two components should drive the WrapByVector filter. I describe my thoughts, which didn't solve the problem, below: If the complex mode shape is a+jb, the animated mode shape should have a form like a cos(wt)+b cos(wt+pi/2). w is only for visualization and can be 2pi, 1, etc. t can come from the animation time. I learned about GetAnimationTime () that can be accessed inside a PythonAnimationCue (). Another way of getting the time is through CompositeKeyFrame for real and imaginary parts where "Phase" for one of them should be set to pi/2 (it is not clear to me whether the phase should be defined as deg or rad for CompositeKeyFrame). I guess at least one of my problem is that I don't know how to access data of the imaginary and real fields in the complex file or data of the two separate reader sources and do math operation on them to make a new field out of them and feed it to a wrap filter. Any thoughts would be appreciated.Nima -------------- next part -------------- An HTML attachment was scrubbed... URL: From bflandard at gmail.com Wed Dec 30 17:39:04 2015 From: bflandard at gmail.com (Bob Flandard) Date: Wed, 30 Dec 2015 22:39:04 +0000 Subject: [Paraview] Scalar bar ranges jump around In-Reply-To: References: Message-ID: Hello Utkarsh and Cory, This issue is not exclusive to "Automatic Annotations". It also exists with the default "Labels" type annotations with or without the "Automatic Label Format" selected. Thanks for investigating, Bob On 30 December 2015 at 21:53, Utkarsh Ayachit wrote: > Ah, the issue seems to be with "Automatic Annotations". Cory, can you > check this out when you get the chance? I am not entirely sure how > automatic annotations should work here, if at all. > > Utkarsh > > On Tue, Dec 29, 2015 at 5:26 PM, Bob Flandard wrote: > > Hello Utkarsh, > > > > Thank you for the suggestion. The plot I sent has already implicitly > > disabled "automatic label format" by only using the "Draw Annotations" > and > > "Automatic Annotation" options, with the options in the "Labels" section > > unchecked. I tried explicitly unchecking the "Automatic Label Format" as > you > > suggested, but it has no effect in this instance (as expected). > > > > Are you able to reproduce the effect from the attached state file? > > > > Thanks for your help, Bob > > > > > > > > On 29 December 2015 at 21:44, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> > > wrote: > >> > >> Can you try unchecking the "Automatic Label Format" checkbox on the > >> "Edit Color Legend Parameters" dialog accessible from the "Color Map > >> Editor" panel? I think it's the label formatting that's causing the > >> issue. > >> > >> Utkarsh > >> > >> On Tue, Dec 29, 2015 at 4:07 PM, Bob Flandard > wrote: > >> > Hello Ken, > >> > > >> > Maybe you are seeing something different to what I see when playing > the > >> > different time steps. I see the relative size of each of the discrete > >> > colours in the scalar bar, changing in a random way. The ticks don't > >> > move > >> > and the numbers change appropriately, but the length of each colour is > >> > not > >> > constant. I've attached an image that shows the scalar bar from three > >> > time > >> > step of the data set in the state file I posted yesterday. One (t=96) > >> > has a > >> > good scalar bar and the other two are wrong. > >> > > >> > Thanks for your help, Bob > >> > > >> > On 29 December 2015 at 17:49, Moreland, Kenneth > >> > wrote: > >> >> > >> >> Bob, > >> >> > >> >> I am confused. The "clamp and update every timestep" feature is what > >> >> turns > >> >> on the behavior of changing the scale of every timestep. Just turn it > >> >> off. > >> >> > >> >> -Ken > >> >> > >> >> Sent from my iPad so blame autocorrect. > >> >> > >> >> > On Dec 28, 2015, at 3:17 PM, Bob Flandard > >> >> > wrote: > >> >> > > >> >> > Hello, > >> >> > > >> >> > Sorry if this is old news. > >> >> > > >> >> > The colour ranges on the scalar bar should remain equally spaced, > but > >> >> > with the transfer function reset mode set to "clamp and update > every > >> >> > timestep", they jump about during a time series animation. > >> >> > > >> >> > Attached is a state file that demonstrates the issue (created with > PV > >> >> > v5.0 RC3). Please load it and click the play button, or manually > >> >> > click > >> >> > through time steps. > >> >> > > >> >> > Thanks, Bob > >> >> > > >> >> > _______________________________________________ > >> >> > Powered by www.kitware.com > >> >> > > >> >> > Visit other Kitware open-source projects at > >> >> > http://www.kitware.com/opensource/opensource.html > >> >> > > >> >> > Please keep messages on-topic and check the ParaView Wiki at: > >> >> > http://paraview.org/Wiki/ParaView > >> >> > > >> >> > Search the list archives at: > http://markmail.org/search/?q=ParaView > >> >> > > >> >> > Follow this link to subscribe/unsubscribe: > >> >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > >> > > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Please keep messages on-topic and check the ParaView Wiki at: > >> > http://paraview.org/Wiki/ParaView > >> > > >> > Search the list archives at: http://markmail.org/search/?q=ParaView > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview > >> > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrewh0 at uw.edu Thu Dec 31 15:06:58 2015 From: andrewh0 at uw.edu (Andrew Ho) Date: Thu, 31 Dec 2015 13:06:58 -0700 Subject: [Paraview] Xdmf reader subsets? Message-ID: I am trying to read an Xdmf subset into Paraview 4.4, but I get the assertion (debug build): *vtkXdmfHeavyData.cxx:293: vtkDataObject *vtkXdmfHeavyData::ReadUniformData(xdm**f2::XdmfGrid *, int): Assertion `xmfGrid->IsUniform() && "Input must be a uniform xdmf grid."' failed.* I dug through the backtrace, and it seems that *vtkXdmfHeavyData::ReadData(XdmfGrid* xmfGrid, int blockId)* is incorrectly forwarding the Subset grid to the vtkXdmfHeavyData::ReadUniformData function. Here's a self-contained XDMF file to test with: 0 1 2 3 4 5 6 7 8 0. 0. 0. 1. 0. 0. 0. 1. 0. 1. 0. 0. 2. 0. 0. 1. 1. 0. 2. 0. 0. 3. 0. 0. 2. 1. 0. 0 2 /Xdmf/Domain/Grid[1] I'm relatively confident that this should be a valid XDMF file, but I'm not positive since I wrote this by hand and the documentation for subsets is relatively sparse. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ckitsaki at gmail.com Sat Dec 5 03:49:01 2015 From: ckitsaki at gmail.com (Chara Kitsaki) Date: Sat, 05 Dec 2015 08:49:01 -0000 Subject: [Paraview] Electric field plot Message-ID: Hi, I would like to create a plot of the electric field vs y_coordinate. I created a .sif file (attached) which computes the electric field using the ElmerFEM software and I exported all the results into a .vtu file (attached). All I have done is to use the filter PlotOverLine but what I get as a plot is the electric field vs the arc_length. Thanks in advance, Chara -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: case128520.vtu Type: application/octet-stream Size: 4179745 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: strips_flat.sif Type: application/octet-stream Size: 1587 bytes Desc: not available URL: From hahnse at ornl.gov Tue Dec 22 10:21:51 2015 From: hahnse at ornl.gov (Hahn, Steven E.) Date: Tue, 22 Dec 2015 15:21:51 -0000 Subject: [Paraview] VTK warning during volume rendering of vtkStructuredGrid on Windows with Nvidia graphics card. In-Reply-To: References: <1450735636346.93209@ornl.gov>, Message-ID: <1450797708669.18352@ornl.gov> Hi Aashish, The XML report is attached. Best, Steven ________________________________ From: Aashish Chaudhary Sent: Monday, December 21, 2015 6:53 PM To: Hahn, Steven E. Cc: ParaView Subject: Re: [Paraview] VTK warning during volume rendering of vtkStructuredGrid on Windows with Nvidia graphics card. This is good, GLview, should have a way to export the output to a file. Can you send that to us as well? If it is too big, send it to me directly. Thanks, aashish On Mon, Dec 21, 2015 at 5:07 PM, Hahn, Steven E. > wrote: Hi Aashish, This machine is running Windows 7. I built Paraview v5.0.0-RC2 with Visual Studio 2015. GLview does list GL_ARB_framebuffer_object as supported. Are there any other specific features in the report that I should check? Best, Steven ________________________________ From: Aashish Chaudhary > Sent: Monday, December 21, 2015 4:03 PM To: Hahn, Steven E. Cc: ParaView Subject: Re: [Paraview] VTK warning during volume rendering of vtkStructuredGrid on Windows with Nvidia graphics card. Hi Steven, Also, can you install and run glview (http://www.realtech-vr.com/glview/download.php) on your system to see if FBO support exists? Thanks, Aashish On Mon, Dec 21, 2015 at 4:02 PM, Aashish Chaudhary > wrote: On Mon, Dec 21, 2015 at 3:56 PM, Hahn, Steven E. > wrote: I tried viewing the volume representation of a small vtkStructuredGrid file with ParaView v5.0.0-RC2 built with the OpenGL2 rendering backend and get this warning: Warning: In C:\Sources\ParaView-v5.0.0-RC1-source\VTK\Rendering\VolumeOpenGL2\vtkOpenGL ProjectedTetrahedraMapper.cxx, line 251 vtkOpenGLProjectedTetrahedraMapper (00000000061B0AD0): Missing FBO support. The algorithm may produce visual artifacts. Updating the video card (Nvidia Quadro K6000) driver to the latest version (354.56) had no effect. Volume rendering with a different vtkImageData file generated no warnings. They are using different mappers. I am surprised that you are reported missing fbo support. Which windows Platform is this? - Aashish Best, Steven Hahn _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: glview-Quadro K6000_PCIe_SSE2-11.XML Type: text/xml Size: 443967 bytes Desc: glview-Quadro K6000_PCIe_SSE2-11.XML URL: From thomas.oliveira at gmail.com Mon Dec 28 16:50:45 2015 From: thomas.oliveira at gmail.com (Thomas Oliveira) Date: Mon, 28 Dec 2015 21:50:45 -0000 Subject: [Paraview] Two images selected on pipeline, just one shown Message-ID: Dear all, I am trying to visualize two images simultaneously in Paraview 4.4.0 64-bit, but without sucess. For the first image (figure image1.png attached), I loaded a raw file, visualized it as "volume" and set the color map to get a very low opacity. It represents the solid phase in a porous object. For the second image (figure image2.png attached), I loaded the results of a simulation, applied the "Stream Tracer" filter on the velocity field, and applied the "Tube" filter on top of it. It represents the streamlines of the flow inside the porous object shown in the first image. If I turn the eyeball on for both items on the pipeline browser, just the first image is visible. Is this the expected behaviour? I thought that both images could be seen at the same time. --------------- Detailed experiment with the user interface: - turn both eyeballs off, turn on eyeball of first image => image is rendered - turn both eyeballs off, turn on eyeball of second image => image is rendered - turn both eyeballs off, turn on eyeball of first image, then of second image => just first image is rendered (figure together.png attached) - turn both eyeballs off, turn on eyeball of second image, then turn on eyeball of first image => nothing is rendered (figure none.png attached) - turn both eyeballs off, turn on eyeball of second image, then turn on eyeball of first image, then press Reset button => just first image is rendered (figure together.png attached) --------------- Best regards, and a happy 2016! Thomas Oliveira -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image1.png Type: image/png Size: 408308 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image2.png Type: image/png Size: 467087 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: none.png Type: image/png Size: 239582 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: together.png Type: image/png Size: 420622 bytes Desc: not available URL: