[Paraview] Diagrams displayed on sections in 3D
My question is related to a typical problem occurring in postprocessing of finite element results for shell elements. Usually one would like to display sectional forces as diagrams, but plotted directly onto the 3D shell model, as in https://ibb.co/irp2v5. I can imagine that it should be feasible to create a paraview filter that can do the following: - create a plane as in the clip/cut filter - select the component to display (membrane force x/y/magnitude, moments, shear force etc) - scale the diagram appropriately Similar functionality would be useful for beam/truss results, visualizing forces along the elements. I'm quite sure that I'm not the first one with such a demand. Does anyone know of a paraview plugin that would accomplish this? Thanks and best regards Matthias -- Ingénieur civil EPFL/SIA / Dr ès sciences EPFL Geomod SA Ch. des Epinettes 32 1007 Lausanne 079 7657226 ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Clever way to identify a ring of element?
Hello Dennis, To apply the slice filter to a doughnut polygon creates line segments obtained by intersecting it with section planes. And then to apply the connectivity filter to the result gives curve rings consisting of consecutive line segments and each of rings is assigned a RegionId. You can try the attached Status file with ParaView 5.4. Unfortunately these elements belonging to the rings are in Cartesian coordinate system. So, you need to convert the elements' coordinates from Cartesian (x,y,z) to Cylindrical (r,\theta,z). At that time, the following code would be helpful to compute a barycenter and a mean radius of individual rings: https://github.com/vmtk/vmtk/blob/master/vtkVmtk/ComputationalGeometry/vtkvmtkBoundaryReferenceSystems.cxx Thanks, yoshimi 2017-06-16 1:58 GMT+09:00 Dennis Conklin : > All, > > > > Imagine I have a model of a doughnut. I want to identify rings in the > model. A ring is a set of elements in an r, z, theta coordinate system > which has the same radius and z_coordinate and only differs in the angular > coordinate. Of course, since trig functions are used in calculating the > radius, we are not guaranteed that the radius will be absolutely identical > for each element in the ring. > > > > Is there a clever (as in fast and easy) way to sort out elements belonging > to individual rings and perhaps assign something like a ring number to them > so that a threshold could be used to examine individual rings. I’m hoping > there is some clever vtk stuff that I’m not familiar with that would help > with this. > > > > Thanks for any thoughts > > > > Dennis > > > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > rings.tar.gz Description: GNU Zip compressed data ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Dropping Qt 4 support from ParaView 5.5 onwards
Great! Our official release binaries will indeed use Qt 5.9, but we probably want to keep the required min version for building ParaVeiw at 5.6 for reasons Dave mentioned. Utkarsh On Thu, Jun 8, 2017 at 7:22 AM, David E DeMarle wrote: > +1 for dropping 4 > > Regarding 5.9 what distros/versions is it not yet readily available on? If > nothing major, then +1 as well. > > On Jun 8, 2017 2:43 AM, "MicK7" wrote: > > +1 for qt 5.9 > > And thanks for the great job on 5.4 release. > > Mickael PHILIT > > > On 06/06/2017 18:44, Michael Jackson wrote: >> >> +1. >> Also I would vote to jump all the way to Qt 5.9 since it is a LTS release >> and you can stabilize on Qt 5.9 for the next 3 years at least where as Qt >> 5.6 is only supported in a security bug fix from here on for another 2 >> years. I don't think Qt is going to add support for newer operating systems >> so if something breaks on newer releases of macOS or Windows Qt made it >> sound like they would not fix Qt 5.6 >> > > > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > 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
Re: [Paraview] MPI-Error during using "Programmable Filter"...
Stefan, I am a little confused on how test your state file. Is the attached state bad or good? I don't get any errors even when I run in parallel with 2 pvservers. Utkarsh On Mon, Jun 19, 2017 at 8:34 AM, Stefan Melber wrote: > Hi, > > > Update: found the reason of the mpi-error - maybe a PV-bug: > > If i use this formula in a programmable filter > > v_bad = min((1., max((-1., tmp2 > > > then paraview crashes in parallel. If i use the same but written out in > > if (tmp2 > -1.): > > if (tmp2 > 1.): > > v = 1. > > else: > > v = tmp2 > > else: > > v = -1. > > the result for v is the same, however paraview does not crash. > > Further more, the results of v_bad and v in parallel differ, in serial mode > they are the same. Find attached a short restart file, which demonstrates > the effect. > > Stefan > > Hi, > > > i have used a programmable filter (find it below) to calculate the > lambda2-criterion from gradients of velocity. In serial mode this works fine > - running it in parallel an error message comes up. Any idea what does it > mean and whats wrong with the filter? > > Best regards, > >Stefan > > > > > Executing with: 0 > Executing with: 0 > Executing with: 0 > Executing with: 0 > Executing with: 0 > Executing with: 0 > Executing with: 0 > Executing with: 0 > > 2385958 > 2406377 > 2220610 > 2292001 > 2144431 > 2331490 > 2061524 > 2344595 > Traceback (most recent call last): > File "", line 22, in > File "", line 76, in RequestData > File > "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", > line 358, in max > return _global_func(MaxImpl(), array, axis, controller) > File > "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", > line 199, in _global_func > max_dims, size = _reduce_dims(res, comm) > File > "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", > line 168, in _reduce_dims > comm.Allreduce([dims, mpitype], [max_dims, mpitype], MPI.MAX) > File "MPI/Comm.pyx", line 715, in mpi4py.MPI.Comm.Allreduce > (/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0/VTK/ThirdParty/mpi4py/vtkmpi4py/src/mpi4py.MPI.c:99224) > mpi4py.MPI.Exception: MPI_ERR_OTHER: known error not in list > Traceback (most recent call last): > File "", line 22, in > Traceback (most recent call last): > File "", line 76, in RequestData > File "", line 22, in > File "", line 76, in RequestData > File > "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", > line 358, in max > File > "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", > line 358, in max > return _global_func(MaxImpl(), array, axis, controller) > File > "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", > line 199, in _global_func > max_dims, size = _reduce_dims(res, comm) > return _global_func(MaxImpl(), array, axis, controller) > File > "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", > line 199, in _global_func > File > "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", > line 168, in _reduce_dims > max_dims, size = _reduce_dims(res, comm) > comm.Allreduce([dims, mpitype], [max_dims, mpitype], MPI.MAX) > File "MPI/Comm.pyx", line 715, in mpi4py.MPI.Comm.Allreduce > (/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0/VTK/ThirdParty/mpi4py/vtkmpi4py/src/mpi4py.MPI.c:99224) > File > "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", > line 168, in _reduce_dims > mpi4py.MPI.Exception: MPI_ERR_OTHER: known error not in list > comm.Allreduce([dims, mpitype], [max_dims, mpitype], MPI.MAX) > File "MPI/Comm.pyx", line 715, in mpi4py.MPI.Comm.Allreduce > (/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0/VTK/ThirdParty/mpi4py/vtkmpi4py/src/mpi4py.MPI.c:99224) > mpi4py.MPI.Exception: MPI_ERR_OTHER: known error not in list > > > > > > > > > grad = inputs[0].PointData["Gradients"] > > npoints = len(grad) > > print npoints > > data = [] > > for i in range(npoints): > > # Gradients > > dvx = grad[i,:][0] > > dvy = grad[i,:][1] > > dvz = grad[i,:][2] > > # Symmetrical part of flow tensor -> S > > s0 = dvx[0] > > s1 = 0.5 * (dvx[1] + dvy[0]) > > s2 = 0.5 * (dvx[2] + dvz[0]) > > s3 = 0.5 * (dvy[0] + dvx[1]) > > s4 = dvy[1]; > > s5 = 0.5 * (dvy[2] + dvz[1]) > > s6 = 0.5 * (dvz[0] + dvx[2]) > > s7 = 0.5 * (dvz[1] + dvy[2]) > > s8 = dvz[2] > > # Antisymmetrical part of flow tensor -> Omega > > Omega0 = 0.0 > > Omega1 = 0.5 * (dvx[1] - dvy[0]) > > Omega2 = 0.5 * (dvx[2] - dvz[0]) > > Omega3 = 0.5 * (dvy[0] - dvx[1]) > > Omega4 =
Re: [Paraview] Coloring isocontour by the coordinates outputted from a Transform filter and some other questions
Hello Cory, I've been playing around a little bit more and followed your suggestion with using the calculator to "expose" the transformed coordinates. However, my understanding is that this Calculator will duplicate the memory usage for that coordinate and be an additional step in the filtering process, slowing it down. I have to use the Calculator filter to expose all 3 coordinates before using a threshold to filter for only a subset region that I want to plt, which results in a filtering chain as follows: ExposeX (Calculator) -> ExposeY (Calculator) -> ExposeZ (Calculator) -> ThresholdX (Threshold) -> ThresholdY (Threshold) -> ThresholdZ (Threshold). This is 6 filters, which is very slow with my data set (>29M nodes in a rectlinear grid). Is there a way to speed this up? Thanks, Shuhao On 2017-06-07 03:29 PM, Cory Quammen wrote: Shuhao, Welcome to ParaView! On Sun, Jun 4, 2017 at 6:33 PM, Shuhao Wu wrote: Hello all, Is there a way to color an isocontour via the coordinates outputted from a Transform filter? I'm using the Transform filter to "normalize" my coordinate systems and I want to display the isocontour colored by the normalized Y coordinates. Do I have to create yet another Calculator filter to recalculate the normalized Y value that is already calculated by the Transform filter? There is currently no direct way to color surfaces by coordinate value. You can, however, add a Calculator after the Transform filter and simply set the expression to coordsY - no recomputation of the normalization is needed. This will copy your normalized Y coordinate values to a new array named "Result", and you can then color the isosurface by "Result". "Result" is just the default name - you can change it however you wish. Also: is there a way to turn off one axis on the axis grid (so turn off the Y axis display and leave only X and Z)? Click the Edit button next to the Axes Grid option. Click the gear icon in the top right of the dialog that appears. Under Face Properties, click on the "Faces to Render" combo box. Turn off the sides you do not wish to see by selecting them in the combo box. What about changing the interval on the axis itself (instead of incrementing by 100 as it chooses, increment by 250). In the same dialog described above, check the "X Axis Use Custom Labels", and you can specify exactly the labels you want. There is no property to directly change the increment. Best, Cory I'm pretty new to Paraview (coming from Tecplot). Please bear with me as I likely will have more question. Thanks, Shuhao ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView 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
Re: [Paraview] MPI-Error during using "Programmable Filter"...
Hi Utkarsh, the state file is the one with errors. I got a long list of differences between v_bad and v in the window, where i have started the pvservers with mpi like -0.149121856689 0.485999450684 -0.158555145264 0.47960144043 -0.17734588623 0.457775421143 -0.149189071655 0.476917114258 -0.241045379639 0.370332946777 -0.177021789551 0.414346313477 -0.333812713623 0.232836074829 -0.237988204956 0.299920196533 -0.446063957214 0.0598551177979 -0.324894866943 0.146606750488 -0.566599311829 -0.131107559204 -0.42886264801 -0.0301560974121 Running it in serial no differences between v_bad and v occur. I tried the same binaries of 5.4 from the webpage ... same error. Best regards, Stefan Stefan, I am a little confused on how test your state file. Is the attached state bad or good? I don't get any errors even when I run in parallel with 2 pvservers. Utkarsh On Mon, Jun 19, 2017 at 8:34 AM, Stefan Melber wrote: Hi, Update: found the reason of the mpi-error - maybe a PV-bug: If i use this formula in a programmable filter v_bad = min((1., max((-1., tmp2 then paraview crashes in parallel. If i use the same but written out in if (tmp2 > -1.): if (tmp2 > 1.): v = 1. else: v = tmp2 else: v = -1. the result for v is the same, however paraview does not crash. Further more, the results of v_bad and v in parallel differ, in serial mode they are the same. Find attached a short restart file, which demonstrates the effect. Stefan Hi, i have used a programmable filter (find it below) to calculate the lambda2-criterion from gradients of velocity. In serial mode this works fine - running it in parallel an error message comes up. Any idea what does it mean and whats wrong with the filter? Best regards, Stefan Executing with: 0 Executing with: 0 Executing with: 0 Executing with: 0 Executing with: 0 Executing with: 0 Executing with: 0 Executing with: 0 2385958 2406377 2220610 2292001 2144431 2331490 2061524 2344595 Traceback (most recent call last): File "", line 22, in File "", line 76, in RequestData File "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", line 358, in max return _global_func(MaxImpl(), array, axis, controller) File "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", line 199, in _global_func max_dims, size = _reduce_dims(res, comm) File "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", line 168, in _reduce_dims comm.Allreduce([dims, mpitype], [max_dims, mpitype], MPI.MAX) File "MPI/Comm.pyx", line 715, in mpi4py.MPI.Comm.Allreduce (/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0/VTK/ThirdParty/mpi4py/vtkmpi4py/src/mpi4py.MPI.c:99224) mpi4py.MPI.Exception: MPI_ERR_OTHER: known error not in list Traceback (most recent call last): File "", line 22, in Traceback (most recent call last): File "", line 76, in RequestData File "", line 22, in File "", line 76, in RequestData File "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", line 358, in max File "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", line 358, in max return _global_func(MaxImpl(), array, axis, controller) File "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", line 199, in _global_func max_dims, size = _reduce_dims(res, comm) return _global_func(MaxImpl(), array, axis, controller) File "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", line 199, in _global_func File "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", line 168, in _reduce_dims max_dims, size = _reduce_dims(res, comm) comm.Allreduce([dims, mpitype], [max_dims, mpitype], MPI.MAX) File "MPI/Comm.pyx", line 715, in mpi4py.MPI.Comm.Allreduce (/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0/VTK/ThirdParty/mpi4py/vtkmpi4py/src/mpi4py.MPI.c:99224) File "/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0.bin/lib/site-packages/vtk/numpy_interface/algorithms.py", line 168, in _reduce_dims mpi4py.MPI.Exception: MPI_ERR_OTHER: known error not in list comm.Allreduce([dims, mpitype], [max_dims, mpitype], MPI.MAX) File "MPI/Comm.pyx", line 715, in mpi4py.MPI.Comm.Allreduce (/opt/PARAVIEW_5_4_0_OpenGL2/ParaView-v5.4.0/VTK/ThirdParty/mpi4py/vtkmpi4py/src/mpi4py.MPI.c:99224) mpi4py.MPI.Exception: MPI_ERR_OTHER: known error not in list grad = inputs[0].PointData["Gradients"] npoints = len(grad) print npoints data = [] for i in range(npoints): # Gradients dvx = grad[i,:][0] dvy = grad[i,:][1] dvz = grad[i,:][2] # Symmetrical part of flow tensor -> S
