[Paraview] Status of reload button?
Dear ParaView crew, congratulations on your 4.1 release, I am looking forward to give it and its new features a try. Sadly, once more I am missing the long awaited (5 years [1]), highly demanded (203 votes on uservoice [2]), but still back locked [3] reload button. Can you give an official statement whether this is planned for the near future? Is there a technical or other reason that makes this button so difficult to implement? How about a fund raising campaign to get some money for its development? I am sure there are plenty of bugged users willing to sponsor the reload button. Love your work, Christoph [1] http://paraview.org/Bug/view.php?id=7306 [2] http://paraview.uservoice.com/ [3] http://paraview.org/Bug/view.php?id=12100 -- Une science n'était vraiment développée que quand elle pouvait utiliser les mathématiques.(Paul Lafargue) ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] plot HDF5 with time using XDMF
Hello everyone, I am new to ParaView, and so far I was able to use it without much trouble. But I have hit a dead end, I have looked online for example, but unfortunately it did not help me. I have managed to create XMF file that gives me a 3d plot, but I can't figure out how to couple the time data with the coordinates. MY GOAL IS TO BE ABLE TO PLOT THE DATA CHRONOLOGICALLY the HDF5 file has 3 datasets for X Y Z, 1 for amplitude, and 1 for time. All are of the same hierarchy. Use the following code: ?xml version=1.0 ? !DOCTYPE Xdmf SYSTEM Xdmf.dtd [] Xdmf Version=2.0 Domain Grid Name=mesh3 GridType=Uniform Topology TopologyType=Polyvertex Dimensions=4 / Geometry GeometryType=X_Y_Z DataItem Dimensions=1 1 4 NumberType=Float Precision=4 Format=HDF test3.h5:/X /DataItem DataItem Dimensions=1 1 4 NumberType=Float Precision=4 Format=HDF test3.h5:/Y /DataItem DataItem Dimensions=1 1 4 NumberType=Float Precision=4 Format=HDF test3.h5:/Z /DataItem /Geometry Attribute Name=Pressure AttributeType=Scalar Center=Node DataItem Dimensions=1 1 4 NumberType=Float Precision=4 Format=HDF test3.h5:/MVSPCIe/Pressure /DataItem /Attribute Time TimeType=List DataItem Dimensions=4 NumberType=Float Precision=4 Format=XML test3.h5:/time /DataItem /Time /Grid /Domain /Xdmf Where and how should I put my time data in this schema for Paraview to be able to see it? Does anybody have an idea? Please help... Have a nice day, Ramiz Does anybody have an idea __ Fraunhofer-Institut für Produktionstechnologie IPT Ramiz Azadaliyev Steinbachstraße 17 52074 Aachen ramiz.azadali...@ipt.fraunhofer.de http://www.ipt.fraunhofer.de __ ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] How to display normals, INPUT from a VTK file in Paraview ?
Hi, I am a new user of Paraview. I am facing a problem I cannot solve and I have not found any relevant practice on the internet (guide user, mailing, ...)... I want to visualise my mesh with normals specified IN MY VTK FILE (and NOT the Normals Glyphs calculated by the software) (I have these normals calculations in another code and I do not want to change that). I am importing a mesh in Paraview from a VTK file. The VTK file contains the following elements: # vtk DataFile Version 2.0 hydrodynamic vtk mesh for paraview vizu ASCII DATASET POLYDATA POINTS 458 float x0 y0 z0 (points coordinates) ... ... ... ... POLYGONS 465 2325 4 n1 n2 n3 n4 (points IDs) 4 ... ... ... ... .. CELL_DATA 465 NORMALS cell_normals float ... ... ... (normals coordinates) A 'cell_normals' array appears in 'Information'; I am able to color the surface (each cell) of the mesh according to the values of the cell_normals array (Magnitude, X, Y or Z) but nothing more. This gives me information on the normals orientation but I have no visual on the vectors. How is it possible de visualise these normals (displayed as vectors) on Paraview without calculating them with the software? What is the correct pratice ? I need to know if they are well oriented, I also need some visual on the mesh I am studying. Thanks a lot, Best regards. -- Vincent ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Status of reload button?
There was a talk about that feature in the mailing list with a work around here: http://paraview.markmail.org/thread/riu2by4yof2m4e5s#query:+page:1+mid:7dg2jctve32oijwe+state:results But some reader do have some optimized internal caching which will prevent this trick to work. But maybe, for the reader that you are interested in, that might be good enough... Seb On Tue, Jan 14, 2014 at 12:59 AM, Christoph Grüninger christoph.gruenin...@iws.uni-stuttgart.de wrote: Dear ParaView crew, congratulations on your 4.1 release, I am looking forward to give it and its new features a try. Sadly, once more I am missing the long awaited (5 years [1]), highly demanded (203 votes on uservoice [2]), but still back locked [3] reload button. Can you give an official statement whether this is planned for the near future? Is there a technical or other reason that makes this button so difficult to implement? How about a fund raising campaign to get some money for its development? I am sure there are plenty of bugged users willing to sponsor the reload button. Love your work, Christoph [1] http://paraview.org/Bug/view.php?id=7306 [2] http://paraview.uservoice.com/ [3] http://paraview.org/Bug/view.php?id=12100 -- Une science n'était vraiment développée que quand elle pouvait utiliser les mathématiques.(Paul Lafargue) ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] ParaView 4.1.0 (UNCLASSIFIED)
Classification: UNCLASSIFIED Caveats: NONE I'm seeing some weirdness with the color map editor. If I choose the color map editor option, a separate window pops up as expected. But when I move my cursor from the main window over to the color map pop-up window, the color map window disappears. If I move my cursor back to the main window, the color map pop-up reappears. If I drag the main GUI window over to so that the edges of the main GUI window and the color map popup window are touching, then the color map editor window does not disappear. I'm using the Linux_64 prebuilt binary on a RHEL5 Linux system running KDE 3.5.4. Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Building 120 Cube 315 Aberdeen Proving Ground, MD Phone: 410-278-6266 -Original Message- From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Utkarsh Ayachit Sent: Monday, January 13, 2014 12:25 PM To: ParaView Cc: ParaView Developers Subject: [Paraview] ANN: ParaView 4.1.0 is available for download Folks, ParaView 4.1.0 is now available for download (http://paraview.org/paraview/resources/software.php http://paraview.org/paraview/resources/software.php ). With over 170 issues resolved, this release includes several bug fixes and feature enhancements. For a detailed list of issues resolved, refer to the change log (http://paraview.org/Bug/changelog_page.php http://paraview.org/Bug/changelog_page.php ). Some of the notable enhancements in this release are as follows: Redesigned Color Map Editor panel This release introduces a completely designed panel for editing color and opacity transfer functions for scalar coloring. The panel, which is now a dockable widget, instead of a popup dialog, makes it easier to edit transfer functions as well as edit labels and annotations on the color legend or scalar bar. This also makes it easier to access some of the functionality introduced in the previous version of ParaView, such as categorical colors. It is now easier to edit transfer functions when using log scaling as the transfer function editor view now switches to log space. https://lh3.googleusercontent.com/KT5sVRI8U1GjtliypOEgy3REYvVsZl6YihSYcKJ1c GP_0mPIpDvs4tutNRCD-dh22l_aCXV7FjCobEi0DsnSIMvifFMZqr3vYrw0HZPxOJIIwbh963WvR p_acg Enhancements to Find Data dialog Find Data dialog, introduced several versions ago, has quickly become of the main mechanisms for creating new selections. However, until now, if the user created selection using some other mechanism, such as selecting cells in the 3D view, the Find Data dialog could not be used to inspect that selection. One had to use what was called the Selection Inspector. That has now been changed. Find Data dialog has been updated to always show the active selection, no matter how it was created. Selection Inspector panel has been removed. Selection Inspector was primarily used to control how selections are labelled, their font properties, etc. One can affect these directly from the Find Data dialog or the new Selection Display Inspector which is dockable panel specially designed for picking selection labels, label properties, or showing the selection frustum for frustum based selections. https://lh3.googleusercontent.com/32EfgOk8F9VyKJJi2AuPaqR1TukxdEHY5uCgQHxTd AJ2EduZTFJR9nmjdMBlLRjKbNXn7fkHl3GL23mG6FywA2unhn7uiyDbPvoKeIA-uE9SLs0GPD_cx 4_tJA Enhancements for interactions with Plots Inspired by plots in matplotlib, individual axes in line and bar charts can now be zoomed by right-clicking and dragging along the x- or y- axis. Of course, one can still drag diagonally to scale both axes as before. Also the the user interactions for making new selections in line chart view have been cleaned up to be more consistent with the render view. Support for Python-based views This release adds mechanisms to enable Python developers to integrate views that use libraries such as matplotlib for rendering. This will make it possible to take ParaView's charting capabilities even further. More details on how to create such views can be found on Kitware blog (http://www.kitware.com/blog/home/post/588 http://www.kitware.com/blog/home/post/588 ). ParaView Catalyst: Zero-Copy infrastructure for transferring data A set of experimental interfaces have been added for reusing simulation memory in portions of a Catalyst pipeline. A vtkMappedDataArray subclass may be used for attribute/coordinate arrays, and vtkMappedUnstructuredGrid is used for dataset topologies. More information can be found at http://www.paraview.org/Wiki/CoProcessing#Experimental:_Reusing_simulation_m emory http://www.paraview.org/Wiki/CoProcessing#Experimental:_Reusing_simulation_ memory . ParaView Catalyst: Editions Several new editions of ParaView Catalyst are now available for download and are routinely built and tested. These editions are: Base minimal set of dependencies needed for Catalyst Base-Python Base with
Re: [Paraview] [EXTERNAL] Re: Status of reload button?
Seb/ Christoph, I may be wrong, and there may be ways to get around it (such as the discussion in the mailing list below), but I believe that this feature has to be done on a reader by reader basis. If so, it isn't a trivial amount of work. Further, there are readers that do have this feature - such as the Exodus reader. Alan From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Sebastien Jourdain Sent: Tuesday, January 14, 2014 9:46 AM To: Christoph Grüninger Cc: paraview@paraview.org Subject: [EXTERNAL] Re: [Paraview] Status of reload button? There was a talk about that feature in the mailing list with a work around here: http://paraview.markmail.org/thread/riu2by4yof2m4e5s#query:+page:1+mid:7dg2jctve32oijwe+state:results But some reader do have some optimized internal caching which will prevent this trick to work. But maybe, for the reader that you are interested in, that might be good enough... Seb On Tue, Jan 14, 2014 at 12:59 AM, Christoph Grüninger christoph.gruenin...@iws.uni-stuttgart.demailto:christoph.gruenin...@iws.uni-stuttgart.de wrote: Dear ParaView crew, congratulations on your 4.1 release, I am looking forward to give it and its new features a try. Sadly, once more I am missing the long awaited (5 years [1]), highly demanded (203 votes on uservoice [2]), but still back locked [3] reload button. Can you give an official statement whether this is planned for the near future? Is there a technical or other reason that makes this button so difficult to implement? How about a fund raising campaign to get some money for its development? I am sure there are plenty of bugged users willing to sponsor the reload button. Love your work, Christoph [1] http://paraview.org/Bug/view.php?id=7306 [2] http://paraview.uservoice.com/ [3] http://paraview.org/Bug/view.php?id=12100 -- Une science n'était vraiment développée que quand elle pouvait utiliser les mathématiques.(Paul Lafargue) ___ Powered by www.kitware.comhttp://www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView 4.1.0 (UNCLASSIFIED)
Rick, Can you try running ParaView with -dr command line option and see if the problem persists? Utkarsh On Tue, Jan 14, 2014 at 12:31 PM, Angelini, Richard C (Rick) CIV USARMY ARL (US) richard.c.angelini@mail.mil wrote: Classification: UNCLASSIFIED Caveats: NONE I'm seeing some weirdness with the color map editor. If I choose the color map editor option, a separate window pops up as expected. But when I move my cursor from the main window over to the color map pop-up window, the color map window disappears. If I move my cursor back to the main window, the color map pop-up reappears. If I drag the main GUI window over to so that the edges of the main GUI window and the color map popup window are touching, then the color map editor window does not disappear. I'm using the Linux_64 prebuilt binary on a RHEL5 Linux system running KDE 3.5.4. Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Building 120 Cube 315 Aberdeen Proving Ground, MD Phone: 410-278-6266 -Original Message- From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Utkarsh Ayachit Sent: Monday, January 13, 2014 12:25 PM To: ParaView Cc: ParaView Developers Subject: [Paraview] ANN: ParaView 4.1.0 is available for download Folks, ParaView 4.1.0 is now available for download (http://paraview.org/paraview/resources/software.php http://paraview.org/paraview/resources/software.php ). With over 170 issues resolved, this release includes several bug fixes and feature enhancements. For a detailed list of issues resolved, refer to the change log (http://paraview.org/Bug/changelog_page.php http://paraview.org/Bug/changelog_page.php ). Some of the notable enhancements in this release are as follows: Redesigned Color Map Editor panel This release introduces a completely designed panel for editing color and opacity transfer functions for scalar coloring. The panel, which is now a dockable widget, instead of a popup dialog, makes it easier to edit transfer functions as well as edit labels and annotations on the color legend or scalar bar. This also makes it easier to access some of the functionality introduced in the previous version of ParaView, such as categorical colors. It is now easier to edit transfer functions when using log scaling as the transfer function editor view now switches to log space. https://lh3.googleusercontent.com/KT5sVRI8U1GjtliypOEgy3REYvVsZl6YihSYcKJ1c GP_0mPIpDvs4tutNRCD-dh22l_aCXV7FjCobEi0DsnSIMvifFMZqr3vYrw0HZPxOJIIwbh963WvR p_acg Enhancements to Find Data dialog Find Data dialog, introduced several versions ago, has quickly become of the main mechanisms for creating new selections. However, until now, if the user created selection using some other mechanism, such as selecting cells in the 3D view, the Find Data dialog could not be used to inspect that selection. One had to use what was called the Selection Inspector. That has now been changed. Find Data dialog has been updated to always show the active selection, no matter how it was created. Selection Inspector panel has been removed. Selection Inspector was primarily used to control how selections are labelled, their font properties, etc. One can affect these directly from the Find Data dialog or the new Selection Display Inspector which is dockable panel specially designed for picking selection labels, label properties, or showing the selection frustum for frustum based selections. https://lh3.googleusercontent.com/32EfgOk8F9VyKJJi2AuPaqR1TukxdEHY5uCgQHxTd AJ2EduZTFJR9nmjdMBlLRjKbNXn7fkHl3GL23mG6FywA2unhn7uiyDbPvoKeIA-uE9SLs0GPD_cx 4_tJA Enhancements for interactions with Plots Inspired by plots in matplotlib, individual axes in line and bar charts can now be zoomed by right-clicking and dragging along the x- or y- axis. Of course, one can still drag diagonally to scale both axes as before. Also the the user interactions for making new selections in line chart view have been cleaned up to be more consistent with the render view. Support for Python-based views This release adds mechanisms to enable Python developers to integrate views that use libraries such as matplotlib for rendering. This will make it possible to take ParaView's charting capabilities even further. More details on how to create such views can be found on Kitware blog (http://www.kitware.com/blog/home/post/588 http://www.kitware.com/blog/home/post/588 ). ParaView Catalyst: Zero-Copy infrastructure for transferring data A set of experimental interfaces have been added for reusing simulation memory in portions of a Catalyst pipeline. A vtkMappedDataArray subclass may be used for attribute/coordinate arrays, and vtkMappedUnstructuredGrid is used for dataset topologies. More information can be found at http://www.paraview.org/Wiki/CoProcessing#Experimental:_Reusing_simulation_m emory
[Paraview] Paraview 4.1 fails fetching image
Hello, I just try to compile Paraview 4.1 and it fails due to a wrong MD5 hash - do I do something wrong or is this a bug? Here is the relevant output of the compilation process: -- Fetching http://www.vtk.org/files/ExternalData/MD5/c3a85b21946b6eb8675ac73e166eafd7; -- [download 3% complete] -- [download 7% complete] -- [download 10% complete] -- [download 14% complete] -- [download 17% complete] -- [download 21% complete] -- [download 24% complete] -- [download 28% complete] -- [download 32% complete] -- [download 35% complete] -- [download 39% complete] -- [download 40% complete] -- [download 43% complete] -- [download 47% complete] -- [download 50% complete] -- [download 54% complete] -- [download 58% complete] -- [download 61% complete] -- [download 65% complete] -- [download 68% complete] -- [download 72% complete] -- [download 75% complete] -- [download 79% complete] -- [download 80% complete] -- [download 84% complete] -- [download 87% complete] -- [download 91% complete] -- [download 94% complete] -- [download 100% complete] CMake Error at /home/matse/Downloads/paraview/src/ParaView-v4.1.0/VTK/CMake/ExternalData.cmake:735 (message): Object MD5=c3a85b21946b6eb8675ac73e166eafd7 not found at: http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.downloadchecksum=c3a85b21946b6eb8675ac73e166eafd7algorithm=MD5 (wrong hash MD5=d91764a02837e039d507e571fe58663a) http://www.vtk.org/files/ExternalData/MD5/c3a85b21946b6eb8675ac73e166eafd7 (wrong hash MD5=d91764a02837e039d507e571fe58663a) Call Stack (most recent call first): /home/matse/Downloads/paraview/src/ParaView-v4.1.0/VTK/CMake/ExternalData.cmake:757 (_ExternalData_download_object) VTK/CMakeFiles/VTKData.dir/build.make:1721: recipe for target 'ExternalData/VTK/Testing/Data/usa_image.jpg.md5-stamp' failed make[2]: *** [ExternalData/VTK/Testing/Data/usa_image.jpg.md5-stamp] Error 1 CMakeFiles/Makefile2:2469: recipe for target 'VTK/CMakeFiles/VTKData.dir/all' failed I hope anybody can fix this. Greetings Mathias ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] [EXTERNAL] Re: Status of reload button?
Hi Alan, I agree and what you are stating is what I was trying to say in my e-mail. Just that for some of them the trick that I mentioned could work… Seb On Tue, Jan 14, 2014 at 10:53 AM, Scott, W Alan wasc...@sandia.gov wrote: Seb/ Christoph, I may be wrong, and there may be ways to get around it (such as the discussion in the mailing list below), but I believe that this feature has to be done on a reader by reader basis. If so, it isn’t a trivial amount of work. Further, there are readers that do have this feature – such as the Exodus reader. Alan *From:* ParaView [mailto:paraview-boun...@paraview.org] *On Behalf Of *Sebastien Jourdain *Sent:* Tuesday, January 14, 2014 9:46 AM *To:* Christoph Grüninger *Cc:* paraview@paraview.org *Subject:* [EXTERNAL] Re: [Paraview] Status of reload button? There was a talk about that feature in the mailing list with a work around here: http://paraview.markmail.org/thread/riu2by4yof2m4e5s#query:+page:1+mid:7dg2jctve32oijwe+state:results But some reader do have some optimized internal caching which will prevent this trick to work. But maybe, for the reader that you are interested in, that might be good enough... Seb On Tue, Jan 14, 2014 at 12:59 AM, Christoph Grüninger christoph.gruenin...@iws.uni-stuttgart.de wrote: Dear ParaView crew, congratulations on your 4.1 release, I am looking forward to give it and its new features a try. Sadly, once more I am missing the long awaited (5 years [1]), highly demanded (203 votes on uservoice [2]), but still back locked [3] reload button. Can you give an official statement whether this is planned for the near future? Is there a technical or other reason that makes this button so difficult to implement? How about a fund raising campaign to get some money for its development? I am sure there are plenty of bugged users willing to sponsor the reload button. Love your work, Christoph [1] http://paraview.org/Bug/view.php?id=7306 [2] http://paraview.uservoice.com/ [3] http://paraview.org/Bug/view.php?id=12100 -- Une science n'était vraiment développée que quand elle pouvait utiliser les mathématiques.(Paul Lafargue) ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView 4.1.0 (UNCLASSIFIED)
Classification: UNCLASSIFIED Caveats: NONE If I run with the -dr flag, the color map window shows up inside of the main GUI (on the right hand side of the GL window) and works correctly. If I drag the color map editor tool outside of the main gui, I get the same behavior of the window disappearing if the cursor is outside of the main GL window. Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Building 120 Cube 315 Aberdeen Proving Ground, MD Phone: 410-278-6266 -Original Message- From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] Sent: Tuesday, January 14, 2014 1:26 PM To: Angelini, Richard C (Rick) CIV USARMY ARL (US) Cc: ParaView Subject: Re: ParaView 4.1.0 (UNCLASSIFIED) Rick, Can you try running ParaView with -dr command line option and see if the problem persists? Utkarsh On Tue, Jan 14, 2014 at 12:31 PM, Angelini, Richard C (Rick) CIV USARMY ARL (US) richard.c.angelini@mail.mil wrote: Classification: UNCLASSIFIED Caveats: NONE I'm seeing some weirdness with the color map editor. If I choose the color map editor option, a separate window pops up as expected. But when I move my cursor from the main window over to the color map pop-up window, the color map window disappears. If I move my cursor back to the main window, the color map pop-up reappears. If I drag the main GUI window over to so that the edges of the main GUI window and the color map popup window are touching, then the color map editor window does not disappear. I'm using the Linux_64 prebuilt binary on a RHEL5 Linux system running KDE 3.5.4. Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Building 120 Cube 315 Aberdeen Proving Ground, MD Phone: 410-278-6266 -Original Message- From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Utkarsh Ayachit Sent: Monday, January 13, 2014 12:25 PM To: ParaView Cc: ParaView Developers Subject: [Paraview] ANN: ParaView 4.1.0 is available for download Folks, ParaView 4.1.0 is now available for download (http://paraview.org/paraview/resources/software.php http://paraview.org/paraview/resources/software.php ). With over 170 issues resolved, this release includes several bug fixes and feature enhancements. For a detailed list of issues resolved, refer to the change log (http://paraview.org/Bug/changelog_page.php http://paraview.org/Bug/changelog_page.php ). Some of the notable enhancements in this release are as follows: Redesigned Color Map Editor panel This release introduces a completely designed panel for editing color and opacity transfer functions for scalar coloring. The panel, which is now a dockable widget, instead of a popup dialog, makes it easier to edit transfer functions as well as edit labels and annotations on the color legend or scalar bar. This also makes it easier to access some of the functionality introduced in the previous version of ParaView, such as categorical colors. It is now easier to edit transfer functions when using log scaling as the transfer function editor view now switches to log space. https://lh3.googleusercontent.com/KT5sVRI8U1GjtliypOEgy3REYvVsZl6YihSYcKJ1c GP_0mPIpDvs4tutNRCD-dh22l_aCXV7FjCobEi0DsnSIMvifFMZqr3vYrw0HZPxOJIIwbh963WvR https://lh3.googleusercontent.com/KT5sVRI8U1GjtliypOEgy3REYvVsZl6YihSYcKJ1c GP_0mPIpDvs4tutNRCD-dh22l_aCXV7FjCobEi0DsnSIMvifFMZqr3vYrw0HZPxOJIIwbh963WvR p_acg Enhancements to Find Data dialog Find Data dialog, introduced several versions ago, has quickly become of the main mechanisms for creating new selections. However, until now, if the user created selection using some other mechanism, such as selecting cells in the 3D view, the Find Data dialog could not be used to inspect that selection. One had to use what was called the Selection Inspector. That has now been changed. Find Data dialog has been updated to always show the active selection, no matter how it was created. Selection Inspector panel has been removed. Selection Inspector was primarily used to control how selections are labelled, their font properties, etc. One can affect these directly from the Find Data dialog or the new Selection Display Inspector which is dockable panel specially designed for picking selection labels, label
Re: [Paraview] ParaView 4.1.0 (UNCLASSIFIED)
I suspect that has something to do with KDE/X Windowing system. I wonder if anyone else on this list has seen this problem. Utkarsh On Tue, Jan 14, 2014 at 1:53 PM, Angelini, Richard C (Rick) CIV USARMY ARL (US) richard.c.angelini@mail.mil wrote: Classification: UNCLASSIFIED Caveats: NONE If I run with the -dr flag, the color map window shows up inside of the main GUI (on the right hand side of the GL window) and works correctly. If I drag the color map editor tool outside of the main gui, I get the same behavior of the window disappearing if the cursor is outside of the main GL window. Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Building 120 Cube 315 Aberdeen Proving Ground, MD Phone: 410-278-6266 -Original Message- From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] Sent: Tuesday, January 14, 2014 1:26 PM To: Angelini, Richard C (Rick) CIV USARMY ARL (US) Cc: ParaView Subject: Re: ParaView 4.1.0 (UNCLASSIFIED) Rick, Can you try running ParaView with -dr command line option and see if the problem persists? Utkarsh On Tue, Jan 14, 2014 at 12:31 PM, Angelini, Richard C (Rick) CIV USARMY ARL (US) richard.c.angelini@mail.mil wrote: Classification: UNCLASSIFIED Caveats: NONE I'm seeing some weirdness with the color map editor. If I choose the color map editor option, a separate window pops up as expected. But when I move my cursor from the main window over to the color map pop-up window, the color map window disappears. If I move my cursor back to the main window, the color map pop-up reappears. If I drag the main GUI window over to so that the edges of the main GUI window and the color map popup window are touching, then the color map editor window does not disappear. I'm using the Linux_64 prebuilt binary on a RHEL5 Linux system running KDE 3.5.4. Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Building 120 Cube 315 Aberdeen Proving Ground, MD Phone: 410-278-6266 -Original Message- From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Utkarsh Ayachit Sent: Monday, January 13, 2014 12:25 PM To: ParaView Cc: ParaView Developers Subject: [Paraview] ANN: ParaView 4.1.0 is available for download Folks, ParaView 4.1.0 is now available for download (http://paraview.org/paraview/resources/software.php http://paraview.org/paraview/resources/software.php ). With over 170 issues resolved, this release includes several bug fixes and feature enhancements. For a detailed list of issues resolved, refer to the change log (http://paraview.org/Bug/changelog_page.php http://paraview.org/Bug/changelog_page.php ). Some of the notable enhancements in this release are as follows: Redesigned Color Map Editor panel This release introduces a completely designed panel for editing color and opacity transfer functions for scalar coloring. The panel, which is now a dockable widget, instead of a popup dialog, makes it easier to edit transfer functions as well as edit labels and annotations on the color legend or scalar bar. This also makes it easier to access some of the functionality introduced in the previous version of ParaView, such as categorical colors. It is now easier to edit transfer functions when using log scaling as the transfer function editor view now switches to log space. https://lh3.googleusercontent.com/KT5sVRI8U1GjtliypOEgy3REYvVsZl6YihSYcKJ1c GP_0mPIpDvs4tutNRCD-dh22l_aCXV7FjCobEi0DsnSIMvifFMZqr3vYrw0HZPxOJIIwbh963WvR https://lh3.googleusercontent.com/KT5sVRI8U1GjtliypOEgy3REYvVsZl6YihSYcKJ1c GP_0mPIpDvs4tutNRCD-dh22l_aCXV7FjCobEi0DsnSIMvifFMZqr3vYrw0HZPxOJIIwbh963WvR p_acg Enhancements to Find Data dialog Find Data dialog, introduced several versions ago, has quickly become of the main mechanisms for creating new selections. However, until now, if the user created selection using some other mechanism, such as selecting cells in the 3D view, the Find Data dialog could not be used to inspect that selection. One had to use what was called the Selection Inspector. That has now been changed. Find Data dialog has been updated to always show the active selection, no matter how it was created. Selection Inspector panel has been removed. Selection Inspector was primarily used to control how selections are labelled, their font properties, etc. One can affect these
Re: [Paraview] Paraview 4.1 fails fetching image
Mathias, The testing data server can be a bit flaky. You can just do a make again. Alternatively, you can disable testing by turning off BUILD_TESTING cmake flag and those data files won't be downloaded. Utkarsh On Tue, Jan 14, 2014 at 1:34 PM, Mathias Anselmann mathias.anselm...@gmail.com wrote: Hello, I just try to compile Paraview 4.1 and it fails due to a wrong MD5 hash - do I do something wrong or is this a bug? Here is the relevant output of the compilation process: -- Fetching http://www.vtk.org/files/ExternalData/MD5/c3a85b21946b6eb8675ac73e166eafd7 -- [download 3% complete] -- [download 7% complete] -- [download 10% complete] -- [download 14% complete] -- [download 17% complete] -- [download 21% complete] -- [download 24% complete] -- [download 28% complete] -- [download 32% complete] -- [download 35% complete] -- [download 39% complete] -- [download 40% complete] -- [download 43% complete] -- [download 47% complete] -- [download 50% complete] -- [download 54% complete] -- [download 58% complete] -- [download 61% complete] -- [download 65% complete] -- [download 68% complete] -- [download 72% complete] -- [download 75% complete] -- [download 79% complete] -- [download 80% complete] -- [download 84% complete] -- [download 87% complete] -- [download 91% complete] -- [download 94% complete] -- [download 100% complete] CMake Error at /home/matse/Downloads/paraview/src/ParaView-v4.1.0/VTK/CMake/ExternalData.cmake:735 (message): Object MD5=c3a85b21946b6eb8675ac73e166eafd7 not found at: http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.downloadchecksum=c3a85b21946b6eb8675ac73e166eafd7algorithm=MD5 (wrong hash MD5=d91764a02837e039d507e571fe58663a) http://www.vtk.org/files/ExternalData/MD5/c3a85b21946b6eb8675ac73e166eafd7 (wrong hash MD5=d91764a02837e039d507e571fe58663a) Call Stack (most recent call first): /home/matse/Downloads/paraview/src/ParaView-v4.1.0/VTK/CMake/ExternalData.cmake:757 (_ExternalData_download_object) VTK/CMakeFiles/VTKData.dir/build.make:1721: recipe for target 'ExternalData/VTK/Testing/Data/usa_image.jpg.md5-stamp' failed make[2]: *** [ExternalData/VTK/Testing/Data/usa_image.jpg.md5-stamp] Error 1 CMakeFiles/Makefile2:2469: recipe for target 'VTK/CMakeFiles/VTKData.dir/all' failed I hope anybody can fix this. Greetings Mathias ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] ParticleTracer particle lifetime
Hello, I am continuing my ongoing quest to do something like this http://earth.nullschool.net/#current/wind/isobaric/1000hPa/orthographic=267.73,5.54,350 or this http://www.youtube.com/watch?v=xusdWPuWAoU in Paraview using ***time dependent velocity vectors***. While the LIC plugin is very cool, it does something different. I followed the previous suggestion and tried to use the streamline filter: http://paraview.org/Wiki/ParaView/Custom_Filters Unfortunately that is not quite right either. The problem with the streamline filter is that it treats each timestep as completely independent and regenerates the streamlines whenever the velocity field changes. (This is the correct behavior: streamlines are defined by the *instantaneous* flow.) What we see in those videos are truly particle trajectories. In particular: - particles are seeded randomly (in space and time) - they leave a decaying trail (sometimes called a streaklet) - the particles disappear after a short lifetime This is the combination of ingredients I need to reproduce in paraview. The best candidate is clearly the ParticleTracer filter. However, I have hit a serious problem: it doesn't appear that this filter is able to make the particles die after a temporal lifetime. Compare the v 3.3 documentation http://paraview.org/OnlineHelpCurrent/ParticleTracer.html with the current documentation http://paraview.org/Wiki/ParaView/Users_Guide/List_of_filters#ParticleTracer In the old version, there was an option called Termination Time that is missing from the new version. Without such an option, the particles will never disappear, the domain will get more and more crowded, and the computational expense will grow with time. Let me know if you have any suggestions or if you know how to re-enable this Termination Time option. Thanks a lot, Ryan ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParticleTracer particle lifetime
Hi Ryan, When I look at these movies carefully, it looks like they are using streaklines that are seeded for a short burst. It looks like they pick a number of seeds each time step and start a streakline from each and keep them active for a few time steps. Then those streaklines seem to be killed eventually. It also appears as if they are playing with transparency depending on the age of the streakline. Am I right? -berk On Tue, Jan 14, 2014 at 2:20 PM, Ryan Abernathey ryan.abernat...@gmail.com wrote: Hello, I am continuing my ongoing quest to do something like this http://earth.nullschool.net/#current/wind/isobaric/1000hPa/orthographic=267.73,5.54,350 or this http://www.youtube.com/watch?v=xusdWPuWAoU in Paraview using ***time dependent velocity vectors***. While the LIC plugin is very cool, it does something different. I followed the previous suggestion and tried to use the streamline filter: http://paraview.org/Wiki/ParaView/Custom_Filters Unfortunately that is not quite right either. The problem with the streamline filter is that it treats each timestep as completely independent and regenerates the streamlines whenever the velocity field changes. (This is the correct behavior: streamlines are defined by the *instantaneous* flow.) What we see in those videos are truly particle trajectories. In particular: - particles are seeded randomly (in space and time) - they leave a decaying trail (sometimes called a streaklet) - the particles disappear after a short lifetime This is the combination of ingredients I need to reproduce in paraview. The best candidate is clearly the ParticleTracer filter. However, I have hit a serious problem: it doesn't appear that this filter is able to make the particles die after a temporal lifetime. Compare the v 3.3 documentation http://paraview.org/OnlineHelpCurrent/ParticleTracer.html with the current documentation http://paraview.org/Wiki/ParaView/Users_Guide/List_of_filters#ParticleTracer In the old version, there was an option called Termination Time that is missing from the new version. Without such an option, the particles will never disappear, the domain will get more and more crowded, and the computational expense will grow with time. Let me know if you have any suggestions or if you know how to re-enable this Termination Time option. Thanks a lot, Ryan ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParticleTracer particle lifetime
Hi Ryan, The following thread might be useful in trying to get pathlines/streaklines to work in paraview. http://paraview.markmail.org/search/?q=Dan%20Lipsa#query:Dan%20Lipsa+page:1+mid:lr6wjdwan2ixidlg+state:results Dan On Tue, Jan 14, 2014 at 2:20 PM, Ryan Abernathey ryan.abernat...@gmail.comwrote: Hello, I am continuing my ongoing quest to do something like this http://earth.nullschool.net/#current/wind/isobaric/1000hPa/orthographic=267.73,5.54,350 or this http://www.youtube.com/watch?v=xusdWPuWAoU in Paraview using ***time dependent velocity vectors***. While the LIC plugin is very cool, it does something different. I followed the previous suggestion and tried to use the streamline filter: http://paraview.org/Wiki/ParaView/Custom_Filters Unfortunately that is not quite right either. The problem with the streamline filter is that it treats each timestep as completely independent and regenerates the streamlines whenever the velocity field changes. (This is the correct behavior: streamlines are defined by the *instantaneous* flow.) What we see in those videos are truly particle trajectories. In particular: - particles are seeded randomly (in space and time) - they leave a decaying trail (sometimes called a streaklet) - the particles disappear after a short lifetime This is the combination of ingredients I need to reproduce in paraview. The best candidate is clearly the ParticleTracer filter. However, I have hit a serious problem: it doesn't appear that this filter is able to make the particles die after a temporal lifetime. Compare the v 3.3 documentation http://paraview.org/OnlineHelpCurrent/ParticleTracer.html with the current documentation http://paraview.org/Wiki/ParaView/Users_Guide/List_of_filters#ParticleTracer In the old version, there was an option called Termination Time that is missing from the new version. Without such an option, the particles will never disappear, the domain will get more and more crowded, and the computational expense will grow with time. Let me know if you have any suggestions or if you know how to re-enable this Termination Time option. Thanks a lot, Ryan ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParticleTracer particle lifetime
Berk, That might be the correct interpretation for the first video, which I think uses a steady (i.e. not time-dependent) flow field. For steady flows, streamlines, streaklines, and trajectories are all identical. But if you look at the second video, I think you can see that they are plotting Lagrangian trajectories. My velocity data is time-dependent, so I think I need the trajectories. -Ryan On Tue, Jan 14, 2014 at 2:47 PM, Berk Geveci berk.gev...@kitware.comwrote: Hi Ryan, When I look at these movies carefully, it looks like they are using streaklines that are seeded for a short burst. It looks like they pick a number of seeds each time step and start a streakline from each and keep them active for a few time steps. Then those streaklines seem to be killed eventually. It also appears as if they are playing with transparency depending on the age of the streakline. Am I right? -berk On Tue, Jan 14, 2014 at 2:20 PM, Ryan Abernathey ryan.abernat...@gmail.com wrote: Hello, I am continuing my ongoing quest to do something like this http://earth.nullschool.net/#current/wind/isobaric/1000hPa/orthographic=267.73,5.54,350 or this http://www.youtube.com/watch?v=xusdWPuWAoU in Paraview using ***time dependent velocity vectors***. While the LIC plugin is very cool, it does something different. I followed the previous suggestion and tried to use the streamline filter: http://paraview.org/Wiki/ParaView/Custom_Filters Unfortunately that is not quite right either. The problem with the streamline filter is that it treats each timestep as completely independent and regenerates the streamlines whenever the velocity field changes. (This is the correct behavior: streamlines are defined by the *instantaneous* flow.) What we see in those videos are truly particle trajectories. In particular: - particles are seeded randomly (in space and time) - they leave a decaying trail (sometimes called a streaklet) - the particles disappear after a short lifetime This is the combination of ingredients I need to reproduce in paraview. The best candidate is clearly the ParticleTracer filter. However, I have hit a serious problem: it doesn't appear that this filter is able to make the particles die after a temporal lifetime. Compare the v 3.3 documentation http://paraview.org/OnlineHelpCurrent/ParticleTracer.html with the current documentation http://paraview.org/Wiki/ParaView/Users_Guide/List_of_filters#ParticleTracer In the old version, there was an option called Termination Time that is missing from the new version. Without such an option, the particles will never disappear, the domain will get more and more crowded, and the computational expense will grow with time. Let me know if you have any suggestions or if you know how to re-enable this Termination Time option. Thanks a lot, Ryan ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParticleTracer particle lifetime
I got it. I think that the correct way of doing this would be: 1. Seed particles 2. Integrate 1 time step 3. Kill particles that are older that threshold 4. Connect particles to generate streaklets 5. If time step % n == 0, update seed source randomly 6. Go to 1 if time step left Does this make sense? -berk On Tue, Jan 14, 2014 at 3:17 PM, Ryan Abernathey ryan.abernat...@gmail.com wrote: Berk, That might be the correct interpretation for the first video, which I think uses a steady (i.e. not time-dependent) flow field. For steady flows, streamlines, streaklines, and trajectories are all identical. But if you look at the second video, I think you can see that they are plotting Lagrangian trajectories. My velocity data is time-dependent, so I think I need the trajectories. -Ryan On Tue, Jan 14, 2014 at 2:47 PM, Berk Geveci berk.gev...@kitware.com wrote: Hi Ryan, When I look at these movies carefully, it looks like they are using streaklines that are seeded for a short burst. It looks like they pick a number of seeds each time step and start a streakline from each and keep them active for a few time steps. Then those streaklines seem to be killed eventually. It also appears as if they are playing with transparency depending on the age of the streakline. Am I right? -berk On Tue, Jan 14, 2014 at 2:20 PM, Ryan Abernathey ryan.abernat...@gmail.com wrote: Hello, I am continuing my ongoing quest to do something like this http://earth.nullschool.net/#current/wind/isobaric/1000hPa/orthographic=267.73,5.54,350 or this http://www.youtube.com/watch?v=xusdWPuWAoU in Paraview using ***time dependent velocity vectors***. While the LIC plugin is very cool, it does something different. I followed the previous suggestion and tried to use the streamline filter: http://paraview.org/Wiki/ParaView/Custom_Filters Unfortunately that is not quite right either. The problem with the streamline filter is that it treats each timestep as completely independent and regenerates the streamlines whenever the velocity field changes. (This is the correct behavior: streamlines are defined by the *instantaneous* flow.) What we see in those videos are truly particle trajectories. In particular: - particles are seeded randomly (in space and time) - they leave a decaying trail (sometimes called a streaklet) - the particles disappear after a short lifetime This is the combination of ingredients I need to reproduce in paraview. The best candidate is clearly the ParticleTracer filter. However, I have hit a serious problem: it doesn't appear that this filter is able to make the particles die after a temporal lifetime. Compare the v 3.3 documentation http://paraview.org/OnlineHelpCurrent/ParticleTracer.html with the current documentation http://paraview.org/Wiki/ParaView/Users_Guide/List_of_filters#ParticleTracer In the old version, there was an option called Termination Time that is missing from the new version. Without such an option, the particles will never disappear, the domain will get more and more crowded, and the computational expense will grow with time. Let me know if you have any suggestions or if you know how to re-enable this Termination Time option. Thanks a lot, Ryan ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParticleTracer particle lifetime
Yes, that sounds very sensible! Of course, the difficult part (for me, a relative noob) is to actually implement those steps in terms of a Paraview pipeline. Or would you recommend creating a new custom filter? Unfortunately experimentation has been difficult because of the slowness / instability of the ParticleTracer filter. Even with a very modest number of particles (~10), I experience crippling delays when advancing timesteps. Perhaps pre-generating the trajectories is the answer. Thanks a lot for your suggestions. -Ryan On Tue, Jan 14, 2014 at 3:32 PM, Berk Geveci berk.gev...@kitware.comwrote: I got it. I think that the correct way of doing this would be: 1. Seed particles 2. Integrate 1 time step 3. Kill particles that are older that threshold 4. Connect particles to generate streaklets 5. If time step % n == 0, update seed source randomly 6. Go to 1 if time step left Does this make sense? -berk On Tue, Jan 14, 2014 at 3:17 PM, Ryan Abernathey ryan.abernat...@gmail.com wrote: Berk, That might be the correct interpretation for the first video, which I think uses a steady (i.e. not time-dependent) flow field. For steady flows, streamlines, streaklines, and trajectories are all identical. But if you look at the second video, I think you can see that they are plotting Lagrangian trajectories. My velocity data is time-dependent, so I think I need the trajectories. -Ryan On Tue, Jan 14, 2014 at 2:47 PM, Berk Geveci berk.gev...@kitware.com wrote: Hi Ryan, When I look at these movies carefully, it looks like they are using streaklines that are seeded for a short burst. It looks like they pick a number of seeds each time step and start a streakline from each and keep them active for a few time steps. Then those streaklines seem to be killed eventually. It also appears as if they are playing with transparency depending on the age of the streakline. Am I right? -berk On Tue, Jan 14, 2014 at 2:20 PM, Ryan Abernathey ryan.abernat...@gmail.com wrote: Hello, I am continuing my ongoing quest to do something like this http://earth.nullschool.net/#current/wind/isobaric/1000hPa/orthographic=267.73,5.54,350 or this http://www.youtube.com/watch?v=xusdWPuWAoU in Paraview using ***time dependent velocity vectors***. While the LIC plugin is very cool, it does something different. I followed the previous suggestion and tried to use the streamline filter: http://paraview.org/Wiki/ParaView/Custom_Filters Unfortunately that is not quite right either. The problem with the streamline filter is that it treats each timestep as completely independent and regenerates the streamlines whenever the velocity field changes. (This is the correct behavior: streamlines are defined by the *instantaneous* flow.) What we see in those videos are truly particle trajectories. In particular: - particles are seeded randomly (in space and time) - they leave a decaying trail (sometimes called a streaklet) - the particles disappear after a short lifetime This is the combination of ingredients I need to reproduce in paraview. The best candidate is clearly the ParticleTracer filter. However, I have hit a serious problem: it doesn't appear that this filter is able to make the particles die after a temporal lifetime. Compare the v 3.3 documentation http://paraview.org/OnlineHelpCurrent/ParticleTracer.html with the current documentation http://paraview.org/Wiki/ParaView/Users_Guide/List_of_filters#ParticleTracer In the old version, there was an option called Termination Time that is missing from the new version. Without such an option, the particles will never disappear, the domain will get more and more crowded, and the computational expense will grow with time. Let me know if you have any suggestions or if you know how to re-enable this Termination Time option. Thanks a lot, Ryan ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] color using side set ID
Hello Paraview people, I'm sure this is something simple that I'm missing, but my google-fu and RTFM-fu is failing me. I have Exodus meshes which include Side Sets. In paraview 3.14.1, I was able to look at these side sets as they would show up in the generic list of Sets after loading the mesh as Unnamed set ID: X. Then selecting these and de-selecting all Blocks, and coloring by ObjectID would color the various side sets. In paraview 3.98/4.0, this Sets panel has gone away. If I click on the Information tab, I can still see that Paraview recognizes my sets as Side Sets, but all statistics are NA, and I cannot for the life of me figure out how to view these. I assume this capability has not gone away, and that I'm doing something wrong, so any suggestions would be helpful. Thanks, Ethan --- Ethan Coon Research Scientist Computational Earth Sciences -- EES-16 Los Alamos National Laboratory 505-665-8289 http://www.ldeo.columbia.edu/~ecoon/ --- ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Status of reload button?
Hi Scott, thanks for your clarification. I wasn't aware of the fact, that the reload button has to be written for every reader. Now I see that it will be a lot of work to get the reload button. On the other hand, reader by reader this feature could be implemented. I am using the VTK reader and will try Sebastien's work around. Thanks so far. This won't cover the numerious wishes for the reload button but alleviate my pain. I am still wondering why Kitware / the ParaView devs do not communicate the reasons better. I know users switching to VisIt only due to its reload button. Please update your statements on uservoice and the bug tracker. Otherwise people might think you don't listen. Thanks for the answers, Christoph ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParticleTracer particle lifetime
Hi Ryan, (4) and (5) won't work out of box and need some thinking. (3) can be implemented by applying Threshold after the particle tracer. I am not aware of any particular issues - other than general slowness but not as bad as you describe - with the particle tracer. Do you have some data that I can experiment with? Note that if you jump around in time, the particle filter can be very slow specially with time dependent data. It has to regenerate the particle paths for all of the times in between if you do that, which means loading a lot of data from disk. It should be relatively fast when animating forward in time. -berk On Tue, Jan 14, 2014 at 3:51 PM, Ryan Abernathey ryan.abernat...@gmail.com wrote: Yes, that sounds very sensible! Of course, the difficult part (for me, a relative noob) is to actually implement those steps in terms of a Paraview pipeline. Or would you recommend creating a new custom filter? Unfortunately experimentation has been difficult because of the slowness / instability of the ParticleTracer filter. Even with a very modest number of particles (~10), I experience crippling delays when advancing timesteps. Perhaps pre-generating the trajectories is the answer. Thanks a lot for your suggestions. -Ryan On Tue, Jan 14, 2014 at 3:32 PM, Berk Geveci berk.gev...@kitware.com wrote: I got it. I think that the correct way of doing this would be: 1. Seed particles 2. Integrate 1 time step 3. Kill particles that are older that threshold 4. Connect particles to generate streaklets 5. If time step % n == 0, update seed source randomly 6. Go to 1 if time step left Does this make sense? -berk On Tue, Jan 14, 2014 at 3:17 PM, Ryan Abernathey ryan.abernat...@gmail.com wrote: Berk, That might be the correct interpretation for the first video, which I think uses a steady (i.e. not time-dependent) flow field. For steady flows, streamlines, streaklines, and trajectories are all identical. But if you look at the second video, I think you can see that they are plotting Lagrangian trajectories. My velocity data is time-dependent, so I think I need the trajectories. -Ryan On Tue, Jan 14, 2014 at 2:47 PM, Berk Geveci berk.gev...@kitware.com wrote: Hi Ryan, When I look at these movies carefully, it looks like they are using streaklines that are seeded for a short burst. It looks like they pick a number of seeds each time step and start a streakline from each and keep them active for a few time steps. Then those streaklines seem to be killed eventually. It also appears as if they are playing with transparency depending on the age of the streakline. Am I right? -berk On Tue, Jan 14, 2014 at 2:20 PM, Ryan Abernathey ryan.abernat...@gmail.com wrote: Hello, I am continuing my ongoing quest to do something like this http://earth.nullschool.net/#current/wind/isobaric/1000hPa/orthographic=267.73,5.54,350 or this http://www.youtube.com/watch?v=xusdWPuWAoU in Paraview using ***time dependent velocity vectors***. While the LIC plugin is very cool, it does something different. I followed the previous suggestion and tried to use the streamline filter: http://paraview.org/Wiki/ParaView/Custom_Filters Unfortunately that is not quite right either. The problem with the streamline filter is that it treats each timestep as completely independent and regenerates the streamlines whenever the velocity field changes. (This is the correct behavior: streamlines are defined by the *instantaneous* flow.) What we see in those videos are truly particle trajectories. In particular: - particles are seeded randomly (in space and time) - they leave a decaying trail (sometimes called a streaklet) - the particles disappear after a short lifetime This is the combination of ingredients I need to reproduce in paraview. The best candidate is clearly the ParticleTracer filter. However, I have hit a serious problem: it doesn't appear that this filter is able to make the particles die after a temporal lifetime. Compare the v 3.3 documentation http://paraview.org/OnlineHelpCurrent/ParticleTracer.html with the current documentation http://paraview.org/Wiki/ParaView/Users_Guide/List_of_filters#ParticleTracer In the old version, there was an option called Termination Time that is missing from the new version. Without such an option, the particles will never disappear, the domain will get more and more crowded, and the computational expense will grow with time. Let me know if you have any suggestions or if you know how to re-enable this Termination Time option. Thanks a lot, Ryan ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
Re: [Paraview] ParticleTracer particle lifetime
Note that if you jump around in time, the particle filter can be very slow specially with time dependent data. It has to regenerate the particle paths for all of the times in between if you do that, which means loading a lot of data from disk. It should be relatively fast when animating forward in time. Berk It used to work just fine jumping around in time - and I implemented it that way so that one could do just that - setting up animations to look just right often requires that kind of playing (and I’m quite upset that it isn’t possible now). Since you chaps messed around with it, it’s awful, and implementing the time steps as a recursive call is really dreadful. Debugging the particle tracer now means stack traces of many thousands of lines. Just my grumpy 2c. JB ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] [EXTERNAL] Client/Server connection problems
Okay, I figured it out, although I'm still confused. Resolution add -connect_id to both cluster and desktop. The cluster reverse connecting was handshaking with an appended connect_id. I had initially tried not using a connect_id, but it errors out saying it's required. The desktop doesn't have one, unless I add it in on the command line run. Any idea why the server is requiring one? Also is there a way to add in the connect_id through the GUI as opposed to through the command line? Thanks, From: Fabian, Nathan Fabian ndfa...@sandia.govmailto:ndfa...@sandia.gov Date: Monday, January 13, 2014 5:42 PM To: Utkarsh Ayachit utkarsh.ayac...@kitware.commailto:utkarsh.ayac...@kitware.com, Scott, W Alan wasc...@sandia.govmailto:wasc...@sandia.gov Cc: paraview@paraview.orgmailto:paraview@paraview.org paraview@paraview.orgmailto:paraview@paraview.org Subject: Re: [Paraview] [EXTERNAL] Client/Server connection problems Thanks for the tip. I'll try this out and let you know how it goes. From: Utkarsh Ayachit utkarsh.ayac...@kitware.commailto:utkarsh.ayac...@kitware.com Date: Saturday, January 11, 2014 7:43 AM To: Scott, W Alan wasc...@sandia.govmailto:wasc...@sandia.gov Cc: Nathan Fabian ndfa...@sandia.govmailto:ndfa...@sandia.gov, paraview@paraview.orgmailto:paraview@paraview.org paraview@paraview.orgmailto:paraview@paraview.org Subject: Re: [Paraview] [EXTERNAL] Client/Server connection problems Nathan, First, let me clarify what is checked, since what Alan said isn't entirely correct. What comprises the handshake? The handshake is a string of the following form: paraview.MajorNumber.MinorNumber If a connect-id is specified then the handshake becomes: paraview.MajorNumber.MinorNumber.connect_id.ConnectId The client and the root-server node exchange these strings. If either side concludes that they don't match, the connection is terminated. To debug, you can put a cout in vtkTCPNetworkAccessManager::ConnectToRemove(), or vtkTCPNetworkAccessManager::ParaViewHandshake() call on both(or either) sides to print the relevant string. How is the MajorNumber/MinorNumber determined? = First, it's hardcoded in the top level CMakeLists.txt. Any time a version number changes, this is manually updated. So on git/master, this will change when we changed from 4.0.1 to 4.1.0-RC1. Thus, even before the official release the version number has changed. This could explain why two builds from git master may not always work with each other. Secondly, if the source repository is a git repository (nothing to do with whether it has access to the Internet), then the version is determined by using the git command git describe. By making sure we tag the repository when the CMakeLists.txt change happens, we ensure that git describe results in version numbers of the form MajorNumber.MinorNumber-FOO-BAR. We can ignore FOO/BAR for now. These are extra annotations that us determine exactly what source version you're using, esp when doing git/master builds. The thing to note is that the handshake only uses the MajorNumber and MinorNumber. So even if your git/master checkouts are from slightly different points in history, they can work together (unless of course, the two checkout happened to be across a version number change). Hope that clarifies things. Putting a cout in vtkTCPNetworkAccessManager and comparing the handshake strings would be a good start to debug this. Utkarsh On Fri, Jan 10, 2014 at 7:00 PM, Scott, W Alan wasc...@sandia.govmailto:wasc...@sandia.gov wrote: Then no, that isn't the issue. One more thing to try - and I don't completely know how to do it. (i.e., ask Kitware). I believe that they now look at not just ParaView version numbers, but also git checkin tags or whatever it is called. If the two trees are basically the same, and ANYONE touched the tree between pulls, that is your problem. This has been an issue for me when one of the two (client or server) is behind a firewall, but the other can connect back to Kitware and find that git tag. Make sure the source trees are exactly the same. Alan -Original Message- From: Fabian, Nathan Sent: Friday, January 10, 2014 4:57 PM To: Scott, W Alan; paraview@paraview.orgmailto:paraview@paraview.org Subject: Re: [EXTERNAL] [Paraview] Client/Server connection problems That sounded promising, but it doesn't appear to have worked. I deleted everything under .config/ParaView and .config/Kitware on both machines, still getting the same error. On 1/10/14 4:45 PM, Scott, W Alan wasc...@sandia.govmailto:wasc...@sandia.gov wrote: Delete your configuration files. Corrupt configuration files sometimes cause this. Surprisingly, on one client of mine, the first connect works, the configuration file gets written, and you never get another successful connect using that configuration file. I haven't chased this down yes, hoping it goes away with the
Re: [Paraview] [EXTERNAL] Client/Server connection problems
You compiled it in? '-DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON ' From: Fabian, Nathan Sent: Tuesday, January 14, 2014 5:41 PM To: Fabian, Nathan; Utkarsh Ayachit; Scott, W Alan Cc: paraview@paraview.org Subject: Re: [Paraview] [EXTERNAL] Client/Server connection problems Okay, I figured it out, although I'm still confused. Resolution add -connect_id to both cluster and desktop. The cluster reverse connecting was handshaking with an appended connect_id. I had initially tried not using a connect_id, but it errors out saying it's required. The desktop doesn't have one, unless I add it in on the command line run. Any idea why the server is requiring one? Also is there a way to add in the connect_id through the GUI as opposed to through the command line? Thanks, From: Fabian, Nathan Fabian ndfa...@sandia.govmailto:ndfa...@sandia.gov Date: Monday, January 13, 2014 5:42 PM To: Utkarsh Ayachit utkarsh.ayac...@kitware.commailto:utkarsh.ayac...@kitware.com, Scott, W Alan wasc...@sandia.govmailto:wasc...@sandia.gov Cc: paraview@paraview.orgmailto:paraview@paraview.org paraview@paraview.orgmailto:paraview@paraview.org Subject: Re: [Paraview] [EXTERNAL] Client/Server connection problems Thanks for the tip. I'll try this out and let you know how it goes. From: Utkarsh Ayachit utkarsh.ayac...@kitware.commailto:utkarsh.ayac...@kitware.com Date: Saturday, January 11, 2014 7:43 AM To: Scott, W Alan wasc...@sandia.govmailto:wasc...@sandia.gov Cc: Nathan Fabian ndfa...@sandia.govmailto:ndfa...@sandia.gov, paraview@paraview.orgmailto:paraview@paraview.org paraview@paraview.orgmailto:paraview@paraview.org Subject: Re: [Paraview] [EXTERNAL] Client/Server connection problems Nathan, First, let me clarify what is checked, since what Alan said isn't entirely correct. What comprises the handshake? The handshake is a string of the following form: paraview.MajorNumber.MinorNumber If a connect-id is specified then the handshake becomes: paraview.MajorNumber.MinorNumber.connect_id.ConnectId The client and the root-server node exchange these strings. If either side concludes that they don't match, the connection is terminated. To debug, you can put a cout in vtkTCPNetworkAccessManager::ConnectToRemove(), or vtkTCPNetworkAccessManager::ParaViewHandshake() call on both(or either) sides to print the relevant string. How is the MajorNumber/MinorNumber determined? = First, it's hardcoded in the top level CMakeLists.txt. Any time a version number changes, this is manually updated. So on git/master, this will change when we changed from 4.0.1 to 4.1.0-RC1. Thus, even before the official release the version number has changed. This could explain why two builds from git master may not always work with each other. Secondly, if the source repository is a git repository (nothing to do with whether it has access to the Internet), then the version is determined by using the git command git describe. By making sure we tag the repository when the CMakeLists.txt change happens, we ensure that git describe results in version numbers of the form MajorNumber.MinorNumber-FOO-BAR. We can ignore FOO/BAR for now. These are extra annotations that us determine exactly what source version you're using, esp when doing git/master builds. The thing to note is that the handshake only uses the MajorNumber and MinorNumber. So even if your git/master checkouts are from slightly different points in history, they can work together (unless of course, the two checkout happened to be across a version number change). Hope that clarifies things. Putting a cout in vtkTCPNetworkAccessManager and comparing the handshake strings would be a good start to debug this. Utkarsh On Fri, Jan 10, 2014 at 7:00 PM, Scott, W Alan wasc...@sandia.govmailto:wasc...@sandia.gov wrote: Then no, that isn't the issue. One more thing to try - and I don't completely know how to do it. (i.e., ask Kitware). I believe that they now look at not just ParaView version numbers, but also git checkin tags or whatever it is called. If the two trees are basically the same, and ANYONE touched the tree between pulls, that is your problem. This has been an issue for me when one of the two (client or server) is behind a firewall, but the other can connect back to Kitware and find that git tag. Make sure the source trees are exactly the same. Alan -Original Message- From: Fabian, Nathan Sent: Friday, January 10, 2014 4:57 PM To: Scott, W Alan; paraview@paraview.orgmailto:paraview@paraview.org Subject: Re: [EXTERNAL] [Paraview] Client/Server connection problems That sounded promising, but it doesn't appear to have worked. I deleted everything under .config/ParaView and .config/Kitware on both machines, still getting the same error. On 1/10/14 4:45 PM, Scott, W Alan wasc...@sandia.govmailto:wasc...@sandia.gov wrote: Delete your configuration files. Corrupt
Re: [Paraview] color using side set ID
Ethan, The properties panel has changed to move some of the less often used properties to the advanced mode. Refer to http://www.kitware.com/blog/home/post/491 for details. The Sets selection is still present, just is advanced by default. Either search for Sets by typing the same text in the Search box at the top of the panel or switch to advanced mode to see it. Utkarsh On Tue, Jan 14, 2014 at 4:01 PM, Coon, Ethan ec...@lanl.gov wrote: Hello Paraview people, I'm sure this is something simple that I'm missing, but my google-fu and RTFM-fu is failing me. I have Exodus meshes which include Side Sets. In paraview 3.14.1, I was able to look at these side sets as they would show up in the generic list of Sets after loading the mesh as Unnamed set ID: X. Then selecting these and de-selecting all Blocks, and coloring by ObjectID would color the various side sets. In paraview 3.98/4.0, this Sets panel has gone away. If I click on the Information tab, I can still see that Paraview recognizes my sets as Side Sets, but all statistics are NA, and I cannot for the life of me figure out how to view these. I assume this capability has not gone away, and that I'm doing something wrong, so any suggestions would be helpful. Thanks, Ethan --- Ethan Coon Research Scientist Computational Earth Sciences -- EES-16 Los Alamos National Laboratory 505-665-8289 http://www.ldeo.columbia.edu/~ecoon/ --- ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
