From cory.quammen at kitware.com Mon Aug 1 11:22:23 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 1 Aug 2016 11:22:23 -0400 Subject: [Paraview-developers] time-dependent output in programmable source In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F684366AEA2@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F68436698D2@MBX211.d.ethz.ch> <0EB9B6375711A04B820E6B6F5CCA9F684366AEA2@MBX211.d.ethz.ch> Message-ID: Jean, I have filed a bug report here: http://www.paraview.org/Bug/view.php?id=16804 Best, Cory On Wed, Jul 27, 2016 at 11:12 AM, Favre Jean wrote: > Thanks Cory > > the first tip was useful. > > and the second tip too. Indeed, if I cut-&-paste my RequestInformation code and my RequestData code directly into an empty ProgrammableSource object, my production code (similar to the small demonstrator I provided) works fine. > > There is something wrong in loading a full session through the python console as you have clearly confirmed. Sometimes though (actually often), a simple tweak is not enough. Yes, all the timestep info appears. But then it crashes on 'Play". Can you open a bug using the demonstrator I provided? > > ----------------- > Jean > -- Cory Quammen R&D Engineer Kitware, Inc. From mathieu.westphal at kitware.com Mon Aug 1 11:27:40 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Mon, 1 Aug 2016 17:27:40 +0200 Subject: [Paraview-developers] Moving around ui files in ParaView Message-ID: Hello I've moved an .ui file and associated class from Components to ApplicationComponents and modified it a bit in a branch. Compiling my branch from an empty directory works perfectly, but compiling it from up to date build directory would fail like this : error: 'class pqSpreadSheetViewDecorator::pqInternal' has no member named 'ExportVisibleColumns' As if the ui file had not been updated. We have already tracked the problem to the fact the build/Qt/Components still contains the old ui_*.h file. Removing it manually fix the problem. but it shows that there may be a problem with the include order, Is there any reason for the include directory of the current source and build directory for not being included before all other include directories ? Is there a work around for this issue ? Because in it's current state, if my branch get merged, anyone compiling master from an existing build directory will encounter the ame bug. Mathieu Westphal -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Aug 1 11:42:57 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 1 Aug 2016 11:42:57 -0400 Subject: [Paraview-developers] Moving around ui files in ParaView In-Reply-To: References: Message-ID: Mathieu, On Mon, Aug 1, 2016 at 11:27 AM, Mathieu Westphal wrote: > Hello > > I've moved an .ui file and associated class from Components to > ApplicationComponents and modified it a bit in a branch. > > Compiling my branch from an empty directory works perfectly, but compiling > it from up to date build directory would fail like this : > > error: 'class pqSpreadSheetViewDecorator::pqInternal' has no member named > 'ExportVisibleColumns' > > As if the ui file had not been updated. We have already tracked the problem > to the fact the build/Qt/Components still contains the old ui_*.h file. Ah yes, I've been bitten by that before. It was maddening. > Removing it manually fix the problem. but it shows that there may be a > problem with the include order, > Is there any reason for the include directory of the current source and > build directory for not being included before all other include directories > ? I don't think there is a reason not to. I'm guess it just hasn't been a big enough issue to make the necessary changes to the CMakeLists.txt files to ensure that the current directory is the first directory to search. It should be possible to insert the current directory in the front of the list in the 'vtk_module_library' function in VTK/CMake/vtkModuleMacros.cmake where 'include_directories' is called.include > Is there a work around for this issue ? > Because in it's current state, if my branch get merged, anyone compiling > master from an existing build directory will encounter the ame bug. Good point. I don't think the build bots start from a clean directory. We probably haven't encountered this scenario since we started using the buildbots, so I'm not sure how it would be handled. > Mathieu Westphal > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen R&D Engineer Kitware, Inc. From joachim.pouderoux at kitware.com Mon Aug 1 11:44:02 2016 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Mon, 1 Aug 2016 17:44:02 +0200 Subject: [Paraview-developers] Moving around ui files in ParaView In-Reply-To: References: Message-ID: The workaround would be to add those source and bin directory using the BEFORE option of the cmake function include_directories(). However, not sure yet where it should be done and there might be a better fix. *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2016-08-01 17:27 GMT+02:00 Mathieu Westphal : > Hello > > I've moved an .ui file and associated class from Components to > ApplicationComponents and modified it a bit in a branch. > > Compiling my branch from an empty directory works perfectly, but compiling > it from up to date build directory would fail like this : > > error: 'class pqSpreadSheetViewDecorator::pqInternal' has no member named 'ExportVisibleColumns' > > As if the ui file had not been updated. We have already tracked the problem to the fact the build/Qt/Components still contains the old ui_*.h file. > > Removing it manually fix the problem. but it shows that there may be a problem with the include order, > Is there any reason for the include directory of the current source and build directory for not being included before all other include directories ? > Is there a work around for this issue ? > Because in it's current state, if my branch get merged, anyone compiling master from an existing build directory will encounter the ame bug. > > Mathieu Westphal > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Mon Aug 1 11:46:48 2016 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Mon, 1 Aug 2016 17:46:48 +0200 Subject: [Paraview-developers] Moving around ui files in ParaView In-Reply-To: References: Message-ID: I would propose (not tested yet) to change vtkModuleMacros.cmake:191 include_directories(${${vtk-module}_INCLUDE_DIRS}) by include_directories(*BEFORE* ${${vtk-module}_INCLUDE_DIRS}) What do you think? *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2016-08-01 17:44 GMT+02:00 Joachim Pouderoux : > The workaround would be to add those source and bin directory using the > BEFORE option of the cmake function include_directories(). > However, not sure yet where it should be done and there might be a better > fix. > > *Joachim Pouderoux*, PhD > > *Technical Expert - Scientific Computing Team* > *Kitware SAS * > > > 2016-08-01 17:27 GMT+02:00 Mathieu Westphal > : > >> Hello >> >> I've moved an .ui file and associated class from Components to >> ApplicationComponents and modified it a bit in a branch. >> >> Compiling my branch from an empty directory works perfectly, but >> compiling it from up to date build directory would fail like this : >> >> error: 'class pqSpreadSheetViewDecorator::pqInternal' has no member named 'ExportVisibleColumns' >> >> As if the ui file had not been updated. We have already tracked the problem to the fact the build/Qt/Components still contains the old ui_*.h file. >> >> Removing it manually fix the problem. but it shows that there may be a problem with the include order, >> Is there any reason for the include directory of the current source and build directory for not being included before all other include directories ? >> Is there a work around for this issue ? >> Because in it's current state, if my branch get merged, anyone compiling master from an existing build directory will encounter the ame bug. >> >> Mathieu Westphal >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Tue Aug 2 05:06:39 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 2 Aug 2016 11:06:39 +0200 Subject: [Paraview-developers] Moving around ui files in ParaView In-Reply-To: References: Message-ID: Joachim proposition indeed fix the problem. I've created a Merge Request with this fix, it does not seem to cause any problems during paraview or any vtk based applpication compilation, feel free to review it. https://gitlab.kitware.com/vtk/vtk/merge_requests/1763 Mathieu Westphal On Mon, Aug 1, 2016 at 5:46 PM, Joachim Pouderoux < joachim.pouderoux at kitware.com> wrote: > I would propose (not tested yet) to change vtkModuleMacros.cmake:191 > > include_directories(${${vtk-module}_INCLUDE_DIRS}) > > by > > include_directories(*BEFORE* ${${vtk-module}_INCLUDE_DIRS}) > > What do you think? > > > *Joachim Pouderoux*, PhD > > *Technical Expert - Scientific Computing Team* > *Kitware SAS * > > > 2016-08-01 17:44 GMT+02:00 Joachim Pouderoux < > joachim.pouderoux at kitware.com>: > >> The workaround would be to add those source and bin directory using the >> BEFORE option of the cmake function include_directories(). >> However, not sure yet where it should be done and there might be a better >> fix. >> >> *Joachim Pouderoux*, PhD >> >> *Technical Expert - Scientific Computing Team* >> *Kitware SAS * >> >> >> 2016-08-01 17:27 GMT+02:00 Mathieu Westphal > >: >> >>> Hello >>> >>> I've moved an .ui file and associated class from Components to >>> ApplicationComponents and modified it a bit in a branch. >>> >>> Compiling my branch from an empty directory works perfectly, but >>> compiling it from up to date build directory would fail like this : >>> >>> error: 'class pqSpreadSheetViewDecorator::pqInternal' has no member named 'ExportVisibleColumns' >>> >>> As if the ui file had not been updated. We have already tracked the problem to the fact the build/Qt/Components still contains the old ui_*.h file. >>> >>> Removing it manually fix the problem. but it shows that there may be a problem with the include order, >>> Is there any reason for the include directory of the current source and build directory for not being included before all other include directories ? >>> Is there a work around for this issue ? >>> Because in it's current state, if my branch get merged, anyone compiling master from an existing build directory will encounter the ame bug. >>> >>> Mathieu Westphal >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Aug 2 11:42:50 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 2 Aug 2016 11:42:50 -0400 Subject: [Paraview-developers] Deadline Extended: ISAV2016: Call for Participation -- August 22, 2016 Message-ID: ** Paper deadline extended to Aug 22, 2016 *** ----------------------------------------------------------------- Call for Participation: ISAV 2016 ========================= ISAV2016: In Situ Infrastructures for Enabling Extreme-Scale Analysis and Visualization In cooperation with SIGHPC and held in conjunction with SC16: The International Conference on High Performance Computing, Networking, Storage and Analysis, Salt Lake City, Utah, U.S.A. Full-day Sunday November 13th, 2016 ISAV 2016 Web Site: http://vis.lbl.gov/Events/ISAV-2016/ Workshop Theme ------------------------ The considerable interest in the HPC community regarding in situ analysis and visualization is due to several factors. First is an I/O cost savings, where data is analyzed/visualized while being generated, without first storing to a file system. Second is the potential for increased accuracy, where fine temporal sampling of transient analysis might expose some complex behavior missed in coarse temporal sampling. Third is the ability to use all available resources, CPU?s and accelerators, in the computation of analysis products. The workshop brings together researchers, developers and practitioners from industry, academia, and government laboratories developing, applying, and deploying in situ methods in extreme-scale, high performance computing. The goal is to present research findings, lessons learned, and insights related to developing and applying in situ methods and infrastructure across a range of science and engineering applications in HPC environments; to discuss topics like opportunities presented by new architectures, existing infrastructure needs, requirements, and gaps, and experiences to foster and enable in situ analysis and visualization; to serve as a ?center of gravity? for researchers, practitioners, and users/consumers of in situ methods and infrastructure in the HPC space. Participation/Call for Papers and Oral Presentations --------------------------------------------------------------------- We invite two types of submissions to ISAV 2016: (1) short, 4-page papers that present research results, that identify opportunities or challenges, and that present case studies/best practices for in situ methods/infrastructure in the areas of data management, analysis and visualization; (2) lightning presentation submission, consisting of a 1- or 2-page submission, for a brief oral presentation at the workshop. Short papers will appear in the workshop proceedings and will be invited to give an oral presentation of 15 to 20 minutes; lightning round submissions that are invited to present at the workshop will have author names and titles included as part of the proceedings. Submissions of both types are welcome that fall within one or more areas of interest, as follows: Areas of interest for ISAV, include, but are not limited to: In situ infrastructures * Current Systems: production quality, research prototypes * Opportunities * Gaps System resources, hardware, and emerging architectures * Enabling Hardware * Hardware and architectures that provide opportunities for In situ processing, such as burst buffers, staging computations on I/O nodes, sharing cores within a node for both simulation and in situ processing Methods/algorithms/applications/Case studies * Best practices * Analysis: feature detection, statistical methods, temporal methods, geometric methods * Visualization: information visualization, scientific visualization, time- varying methods * Data reduction/compression * Examples/case studies of solving a specific science challenge with in situ methods/infrastructure. Simulation * Integration:data modeling, software-engineering * Resilience: error detection, fault recovery * Workflows for supporting complex in situ processing pipelines Requirements * Preserve important elements * Significantly reduce the data size * Flexibility for post-processing exploration Review Process ---------------------- All submissions will undergo a peer-review process consisting of three reviews by experts in the field, and evaluated according to relevance to the workshop theme, technical soundness, creativity, originality, and impactfulness of method/results. Lightning round submissions will be evaluated primarily for relevance to the workshop. Submission Process ---------------------------- Authors are invited to submit papers of at most 4 pages in PDF format, excluding references, and lightning presentations of at most 2 pages in PDF format, excluding references. Papers should be formatted in the ACM Proceedings Style (templates available at https://www.acm.org/publications/proceedings-template) and submitted via EasyChair (https://easychair.org/conferences/?conf=isav2016). No changes to the margins, spacing, or font sizes as specified by the style file are allowed. Papers must be self-contained and provide the technical substance required for the program committee to evaluate their contributions. Submitted papers must be original work that has not appeared in and is not under consideration for another conference or a journal. See the ACM Prior Publication Policy for more details. Papers can be submitted at https://easychair.org/conferences/?conf=isav2016. Publication in proceedings, presentation at the workshop --------------------------------------------------------------------------- All paper submissions that receive favorable reviews will be included as part of the workshop proceedings, which will be published through SIGHPC along with other SC16 workshop proceedings in the ACM Digital Library and IEEE Xplore. Lightning round submissions will not be included as part of the proceedings. Subject to the constraints of workshop length, some subset of the accepted publications will be invited to give a brief oral presentation at the workshop. The exact number of such presentations and their length will be determined after the review process has been completed. Timeline/Important Dates ----------------------------------- 22 August 2016 Paper submission deadline 15 September 2016 Author notification 30 September 2016 Camera ready copy due 15 October 2016 Final program posted to ISAV web page 13 November 2016 ISAV 2016 workshop at SC16 From mathieu.westphal at kitware.com Wed Aug 3 09:19:42 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 3 Aug 2016 15:19:42 +0200 Subject: [Paraview-developers] Example Custom Applications Message-ID: Hello Example Custom Applications seems to be quite out of date, showing warnings and segfault. Shouldn't them be tested somehow ? Regards Mathieu Westphal -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 3 09:21:33 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Aug 2016 09:21:33 -0400 Subject: [Paraview-developers] Example Custom Applications In-Reply-To: References: Message-ID: > Shouldn't them be tested somehow ? +1. It should be possible to add tests easily for those. Feel free! From mathieu.westphal at kitware.com Wed Aug 3 09:22:04 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 3 Aug 2016 15:22:04 +0200 Subject: [Paraview-developers] Example Custom Applications In-Reply-To: References: Message-ID: Well first we would need to fix them :) Mathieu Westphal On Wed, Aug 3, 2016 at 3:21 PM, Utkarsh Ayachit wrote: > > Shouldn't them be tested somehow ? > > +1. It should be possible to add tests easily for those. Feel free! > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 3 09:23:58 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 3 Aug 2016 09:23:58 -0400 Subject: [Paraview-developers] Example Custom Applications In-Reply-To: References: Message-ID: > Well first we would need to fix them :) I assumed as much :). From dave.demarle at kitware.com Wed Aug 3 10:18:44 2016 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 3 Aug 2016 10:18:44 -0400 Subject: [Paraview-developers] Visualization field data at Gauss Points In-Reply-To: References: Message-ID: http://www.vtk.org/Wiki/images/7/78/VTK-Quadrature-Point-Design-Doc.pdf Seems we can interpolate onto the points, but I am not aware of anything in-built that interpolates from them. For that your approach seems reasonable as would a splatting technique. I might suggest apply a resample filter to get the interpolated values back onto the original unstructured mesh. In either case the interpolation will be pretty simplistic. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Sun, Jul 31, 2016 at 5:38 PM, sumeet kumar wrote: > I have a unstructured mesh with different types of elements like (quads, > hexahedrons, tets etc). I have also gauss points associated with these > elements and there are field data ( like stress, strain ) associated with > gauss points only while displacements, velocity are associated with nodes. > The nodal data can be easily be visualized and interpolated in para-view. > > Is there any way in paraview, to visualize data located at gauss points > and interpolate it accordingly within the element and over nearby connected > elements? > > I have the with me the location of all gauss points, the entire > unstructured mesh (comprising of nodes and element). I also have the > information about collection of gauss points belonging to the element. > > Since I do not had a solution for this. What am I currently doing is > generating a Delaunchy3D mesh from the gauss points and then visualizing > the field data in paraview. > > Best > Sumeet > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetsinha.in/ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Aug 4 10:52:05 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 4 Aug 2016 10:52:05 -0400 Subject: [Paraview-developers] Changes coming to ParaView's color legend Message-ID: Hi folks, There are a number of issues with ParaView's current color legend. Here are a few: http://www.paraview.org/Bug/view.php?id=15875 http://www.paraview.org/Bug/view.php?id=16000 http://www.paraview.org/Bug/view.php?id=15379 http://www.paraview.org/Bug/view.php?id=15074 http://www.paraview.org/Bug/view.php?id=15864 http://www.paraview.org/Bug/view.php?id=15862 http://www.paraview.org/Bug/view.php?id=15851 http://www.paraview.org/Bug/view.php?id=15637 http://www.paraview.org/Bug/view.php?id=15319 http://www.paraview.org/Bug/view.php?id=14980 http://www.paraview.org/Bug/view.php?id=15049 http://www.paraview.org/Bug/view.php?id=14146 You get the idea... To address most of these issues and to make future fixes hopefully more straightforward, I have been working on a new implementation of ParaView's color legend. Key improvements in the implementation include: - numerous bug fixes - ability to specify precisely the values to label - improved automatic "human-readable" values for the tick labels - font size controls that offer precise control over font properties. Size can be arbtitrary, for exampld - precise control over the color bar thickness - uses VTK's charts API, so making future improvements to the scalar bar is easier than in the current implementation While the color legend will look similar to the current color legend, you will likely see some differences once this change lands in master. Any baseline image used by testing infrastructure for ParaView or ParaView-based applications with a color legend will probably need to be updated. Note that these changes are in ParaView only and do not affect the scalar bars in VTK. I plan to put together a blog post on the Kitware web site showing off the new color legend in the near future. In the mean time, please let me know if you have any questions or concerns. Thanks, Cory -- Cory Quammen R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Thu Aug 4 11:58:04 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 4 Aug 2016 11:58:04 -0400 Subject: [Paraview-developers] Changes coming to ParaView's color legend In-Reply-To: References: Message-ID: For a small preview of how the new implementation compares to the current one, please see the attached screenshots of the current and new color legend. The files ending in "Current.png" are from ParaView 5.1, while files ending in "New.png" are from the new color legend not yet in ParaView. - Cory On Thu, Aug 4, 2016 at 10:52 AM, Cory Quammen wrote: > Hi folks, > > There are a number of issues with ParaView's current color legend. > Here are a few: > > http://www.paraview.org/Bug/view.php?id=15875 > http://www.paraview.org/Bug/view.php?id=16000 > http://www.paraview.org/Bug/view.php?id=15379 > http://www.paraview.org/Bug/view.php?id=15074 > http://www.paraview.org/Bug/view.php?id=15864 > http://www.paraview.org/Bug/view.php?id=15862 > http://www.paraview.org/Bug/view.php?id=15851 > http://www.paraview.org/Bug/view.php?id=15637 > http://www.paraview.org/Bug/view.php?id=15319 > http://www.paraview.org/Bug/view.php?id=14980 > http://www.paraview.org/Bug/view.php?id=15049 > http://www.paraview.org/Bug/view.php?id=14146 > > You get the idea... > > To address most of these issues and to make future fixes hopefully > more straightforward, I have been working on a new implementation of > ParaView's color legend. Key improvements in the implementation > include: > > - numerous bug fixes > - ability to specify precisely the values to label > - improved automatic "human-readable" values for the tick labels > - font size controls that offer precise control over font properties. > Size can be arbtitrary, for exampld > - precise control over the color bar thickness > - uses VTK's charts API, so making future improvements to the scalar > bar is easier than in the current implementation > > While the color legend will look similar to the current color legend, > you will likely see some differences once this change lands in master. > Any baseline image used by testing infrastructure for ParaView or > ParaView-based applications with a color legend will probably need to > be updated. > > Note that these changes are in ParaView only and do not affect the > scalar bars in VTK. > > I plan to put together a blog post on the Kitware web site showing off > the new color legend in the near future. In the mean time, please let > me know if you have any questions or concerns. > > Thanks, > Cory > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- A non-text attachment was scrubbed... Name: Default-Current.png Type: image/png Size: 7031 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Default-New.png Type: image/png Size: 7434 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Tall-Current.png Type: image/png Size: 9319 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Tall-New.png Type: image/png Size: 12481 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Annotations-Current.png Type: image/png Size: 8411 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Annotations-New.png Type: image/png Size: 10978 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Horizontal-CustomTicks-New.png Type: image/png Size: 5103 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Indexed-Current.png Type: image/png Size: 5327 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Indexed-New.png Type: image/png Size: 7276 bytes Desc: not available URL: From mathieu.westphal at kitware.com Fri Aug 5 03:55:12 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 5 Aug 2016 09:55:12 +0200 Subject: [Paraview-developers] Changes coming to ParaView's color legend In-Reply-To: References: Message-ID: That looks good ! Good luck with baseline generation ! Regards, Mathieu Westphal On Thu, Aug 4, 2016 at 5:58 PM, Cory Quammen wrote: > For a small preview of how the new implementation compares to the > current one, please see the attached screenshots of the current and > new color legend. The files ending in "Current.png" are from ParaView > 5.1, while files ending in "New.png" are from the new color legend not > yet in ParaView. > > - Cory > > On Thu, Aug 4, 2016 at 10:52 AM, Cory Quammen > wrote: > > Hi folks, > > > > There are a number of issues with ParaView's current color legend. > > Here are a few: > > > > http://www.paraview.org/Bug/view.php?id=15875 > > http://www.paraview.org/Bug/view.php?id=16000 > > http://www.paraview.org/Bug/view.php?id=15379 > > http://www.paraview.org/Bug/view.php?id=15074 > > http://www.paraview.org/Bug/view.php?id=15864 > > http://www.paraview.org/Bug/view.php?id=15862 > > http://www.paraview.org/Bug/view.php?id=15851 > > http://www.paraview.org/Bug/view.php?id=15637 > > http://www.paraview.org/Bug/view.php?id=15319 > > http://www.paraview.org/Bug/view.php?id=14980 > > http://www.paraview.org/Bug/view.php?id=15049 > > http://www.paraview.org/Bug/view.php?id=14146 > > > > You get the idea... > > > > To address most of these issues and to make future fixes hopefully > > more straightforward, I have been working on a new implementation of > > ParaView's color legend. Key improvements in the implementation > > include: > > > > - numerous bug fixes > > - ability to specify precisely the values to label > > - improved automatic "human-readable" values for the tick labels > > - font size controls that offer precise control over font properties. > > Size can be arbtitrary, for exampld > > - precise control over the color bar thickness > > - uses VTK's charts API, so making future improvements to the scalar > > bar is easier than in the current implementation > > > > While the color legend will look similar to the current color legend, > > you will likely see some differences once this change lands in master. > > Any baseline image used by testing infrastructure for ParaView or > > ParaView-based applications with a color legend will probably need to > > be updated. > > > > Note that these changes are in ParaView only and do not affect the > > scalar bars in VTK. > > > > I plan to put together a blog post on the Kitware web site showing off > > the new color legend in the near future. In the mean time, please let > > me know if you have any questions or concerns. > > > > Thanks, > > Cory > > > > > > -- > > Cory Quammen > > R&D Engineer > > Kitware, Inc. > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Fri Aug 5 10:40:39 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 5 Aug 2016 14:40:39 +0000 Subject: [Paraview-developers] Changes coming to ParaView's color legend Message-ID: <020bd7cfd7e14f33baec8f98afde106d@ES08AMSNLNT.srn.sandia.gov> Cory, These color bars look nice, particularly the tick placement. If it is not trouble, can you make one minor change? Can you make the new color bar a little bit thinner? I think it makes the bar look a bit more slick. -Ken -----Original Message----- From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Cory Quammen Sent: Thursday, August 4, 2016 9:58 AM To: ParaView Developers Subject: [EXTERNAL] Re: [Paraview-developers] Changes coming to ParaView's color legend For a small preview of how the new implementation compares to the current one, please see the attached screenshots of the current and new color legend. The files ending in "Current.png" are from ParaView 5.1, while files ending in "New.png" are from the new color legend not yet in ParaView. - Cory On Thu, Aug 4, 2016 at 10:52 AM, Cory Quammen wrote: > Hi folks, > > There are a number of issues with ParaView's current color legend. > Here are a few: > > http://www.paraview.org/Bug/view.php?id=15875 > http://www.paraview.org/Bug/view.php?id=16000 > http://www.paraview.org/Bug/view.php?id=15379 > http://www.paraview.org/Bug/view.php?id=15074 > http://www.paraview.org/Bug/view.php?id=15864 > http://www.paraview.org/Bug/view.php?id=15862 > http://www.paraview.org/Bug/view.php?id=15851 > http://www.paraview.org/Bug/view.php?id=15637 > http://www.paraview.org/Bug/view.php?id=15319 > http://www.paraview.org/Bug/view.php?id=14980 > http://www.paraview.org/Bug/view.php?id=15049 > http://www.paraview.org/Bug/view.php?id=14146 > > You get the idea... > > To address most of these issues and to make future fixes hopefully > more straightforward, I have been working on a new implementation of > ParaView's color legend. Key improvements in the implementation > include: > > - numerous bug fixes > - ability to specify precisely the values to label > - improved automatic "human-readable" values for the tick labels > - font size controls that offer precise control over font properties. > Size can be arbtitrary, for exampld > - precise control over the color bar thickness > - uses VTK's charts API, so making future improvements to the scalar > bar is easier than in the current implementation > > While the color legend will look similar to the current color legend, > you will likely see some differences once this change lands in master. > Any baseline image used by testing infrastructure for ParaView or > ParaView-based applications with a color legend will probably need to > be updated. > > Note that these changes are in ParaView only and do not affect the > scalar bars in VTK. > > I plan to put together a blog post on the Kitware web site showing off > the new color legend in the near future. In the mean time, please let > me know if you have any questions or concerns. > > Thanks, > Cory > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. -- Cory Quammen R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Fri Aug 5 16:23:42 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 5 Aug 2016 16:23:42 -0400 Subject: [Paraview-developers] Moving around ui files in ParaView In-Reply-To: References: Message-ID: Mathieu's merge request has been merged into VTK master, so one should not run into this particular problem any more. Thanks, Mathieu! Cory On Tue, Aug 2, 2016 at 5:06 AM, Mathieu Westphal wrote: > Joachim proposition indeed fix the problem. > > I've created a Merge Request with this fix, it does not seem to cause any > problems during paraview or any vtk based applpication compilation, feel > free to review it. > https://gitlab.kitware.com/vtk/vtk/merge_requests/1763 > > Mathieu Westphal > > On Mon, Aug 1, 2016 at 5:46 PM, Joachim Pouderoux > wrote: >> >> I would propose (not tested yet) to change vtkModuleMacros.cmake:191 >> >> include_directories(${${vtk-module}_INCLUDE_DIRS}) >> >> by >> >> include_directories(BEFORE ${${vtk-module}_INCLUDE_DIRS}) >> >> What do you think? >> >> >> Joachim Pouderoux, PhD >> >> Technical Expert - Scientific Computing Team >> Kitware SAS >> >> >> 2016-08-01 17:44 GMT+02:00 Joachim Pouderoux >> : >>> >>> The workaround would be to add those source and bin directory using the >>> BEFORE option of the cmake function include_directories(). >>> However, not sure yet where it should be done and there might be a better >>> fix. >>> >>> Joachim Pouderoux, PhD >>> >>> Technical Expert - Scientific Computing Team >>> Kitware SAS >>> >>> >>> 2016-08-01 17:27 GMT+02:00 Mathieu Westphal >>> : >>>> >>>> Hello >>>> >>>> I've moved an .ui file and associated class from Components to >>>> ApplicationComponents and modified it a bit in a branch. >>>> >>>> Compiling my branch from an empty directory works perfectly, but >>>> compiling it from up to date build directory would fail like this : >>>> >>>> error: 'class pqSpreadSheetViewDecorator::pqInternal' has no member >>>> named 'ExportVisibleColumns' >>>> >>>> As if the ui file had not been updated. We have already tracked the >>>> problem to the fact the build/Qt/Components still contains the old ui_*.h >>>> file. >>>> >>>> Removing it manually fix the problem. but it shows that there may be a >>>> problem with the include order, >>>> Is there any reason for the include directory of the current source and >>>> build directory for not being included before all other include directories >>>> ? >>>> Is there a work around for this issue ? >>>> Because in it's current state, if my branch get merged, anyone compiling >>>> master from an existing build directory will encounter the ame bug. >>>> >>>> Mathieu Westphal >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Search the list archives at: >>>> http://markmail.org/search/?q=Paraview-developers >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>> >>> >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Fri Aug 5 16:29:17 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 5 Aug 2016 16:29:17 -0400 Subject: [Paraview-developers] Changes coming to ParaView's color legend In-Reply-To: <020bd7cfd7e14f33baec8f98afde106d@ES08AMSNLNT.srn.sandia.gov> References: <020bd7cfd7e14f33baec8f98afde106d@ES08AMSNLNT.srn.sandia.gov> Message-ID: > If it is not trouble, can you make one minor change? Can you make the new color bar a little bit thinner? I think it makes the bar look a bit more slick. Ken, Yes, it is very easy to change the default color bar thickness. Attached is an image with two thinner scalar bars. Which do you prefer? Thanks for the suggestion, Cory > > -----Original Message----- > From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Cory Quammen > Sent: Thursday, August 4, 2016 9:58 AM > To: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Changes coming to ParaView's color legend > > For a small preview of how the new implementation compares to the current one, please see the attached screenshots of the current and new color legend. The files ending in "Current.png" are from ParaView 5.1, while files ending in "New.png" are from the new color legend not yet in ParaView. > > - Cory > > On Thu, Aug 4, 2016 at 10:52 AM, Cory Quammen wrote: >> Hi folks, >> >> There are a number of issues with ParaView's current color legend. >> Here are a few: >> >> http://www.paraview.org/Bug/view.php?id=15875 >> http://www.paraview.org/Bug/view.php?id=16000 >> http://www.paraview.org/Bug/view.php?id=15379 >> http://www.paraview.org/Bug/view.php?id=15074 >> http://www.paraview.org/Bug/view.php?id=15864 >> http://www.paraview.org/Bug/view.php?id=15862 >> http://www.paraview.org/Bug/view.php?id=15851 >> http://www.paraview.org/Bug/view.php?id=15637 >> http://www.paraview.org/Bug/view.php?id=15319 >> http://www.paraview.org/Bug/view.php?id=14980 >> http://www.paraview.org/Bug/view.php?id=15049 >> http://www.paraview.org/Bug/view.php?id=14146 >> >> You get the idea... >> >> To address most of these issues and to make future fixes hopefully >> more straightforward, I have been working on a new implementation of >> ParaView's color legend. Key improvements in the implementation >> include: >> >> - numerous bug fixes >> - ability to specify precisely the values to label >> - improved automatic "human-readable" values for the tick labels >> - font size controls that offer precise control over font properties. >> Size can be arbtitrary, for exampld >> - precise control over the color bar thickness >> - uses VTK's charts API, so making future improvements to the scalar >> bar is easier than in the current implementation >> >> While the color legend will look similar to the current color legend, >> you will likely see some differences once this change lands in master. >> Any baseline image used by testing infrastructure for ParaView or >> ParaView-based applications with a color legend will probably need to >> be updated. >> >> Note that these changes are in ParaView only and do not affect the >> scalar bars in VTK. >> >> I plan to put together a blog post on the Kitware web site showing off >> the new color legend in the near future. In the mean time, please let >> me know if you have any questions or concerns. >> >> Thanks, >> Cory >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- A non-text attachment was scrubbed... Name: 15vs10Thickness.png Type: image/png Size: 14106 bytes Desc: not available URL: From kmorel at sandia.gov Fri Aug 5 16:58:10 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 5 Aug 2016 20:58:10 +0000 Subject: [Paraview-developers] Changes coming to ParaView's color legend Message-ID: <0cd9e1410a5f4d0e8aea1e7bf21268b9@ES08AMSNLNT.srn.sandia.gov> I personally like the thinner one (on the right). Does anyone else have an opinion? -Ken -----Original Message----- From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Friday, August 5, 2016 2:29 PM To: Moreland, Kenneth Cc: ParaView Developers Subject: [EXTERNAL] Re: [Paraview-developers] Changes coming to ParaView's color legend > If it is not trouble, can you make one minor change? Can you make the new color bar a little bit thinner? I think it makes the bar look a bit more slick. Ken, Yes, it is very easy to change the default color bar thickness. Attached is an image with two thinner scalar bars. Which do you prefer? Thanks for the suggestion, Cory > > -----Original Message----- > From: Paraview-developers > [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Cory > Quammen > Sent: Thursday, August 4, 2016 9:58 AM > To: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Changes coming to > ParaView's color legend > > For a small preview of how the new implementation compares to the current one, please see the attached screenshots of the current and new color legend. The files ending in "Current.png" are from ParaView 5.1, while files ending in "New.png" are from the new color legend not yet in ParaView. > > - Cory > > On Thu, Aug 4, 2016 at 10:52 AM, Cory Quammen wrote: >> Hi folks, >> >> There are a number of issues with ParaView's current color legend. >> Here are a few: >> >> http://www.paraview.org/Bug/view.php?id=15875 >> http://www.paraview.org/Bug/view.php?id=16000 >> http://www.paraview.org/Bug/view.php?id=15379 >> http://www.paraview.org/Bug/view.php?id=15074 >> http://www.paraview.org/Bug/view.php?id=15864 >> http://www.paraview.org/Bug/view.php?id=15862 >> http://www.paraview.org/Bug/view.php?id=15851 >> http://www.paraview.org/Bug/view.php?id=15637 >> http://www.paraview.org/Bug/view.php?id=15319 >> http://www.paraview.org/Bug/view.php?id=14980 >> http://www.paraview.org/Bug/view.php?id=15049 >> http://www.paraview.org/Bug/view.php?id=14146 >> >> You get the idea... >> >> To address most of these issues and to make future fixes hopefully >> more straightforward, I have been working on a new implementation of >> ParaView's color legend. Key improvements in the implementation >> include: >> >> - numerous bug fixes >> - ability to specify precisely the values to label >> - improved automatic "human-readable" values for the tick labels >> - font size controls that offer precise control over font properties. >> Size can be arbtitrary, for exampld >> - precise control over the color bar thickness >> - uses VTK's charts API, so making future improvements to the scalar >> bar is easier than in the current implementation >> >> While the color legend will look similar to the current color legend, >> you will likely see some differences once this change lands in master. >> Any baseline image used by testing infrastructure for ParaView or >> ParaView-based applications with a color legend will probably need to >> be updated. >> >> Note that these changes are in ParaView only and do not affect the >> scalar bars in VTK. >> >> I plan to put together a blog post on the Kitware web site showing >> off the new color legend in the near future. In the mean time, please >> let me know if you have any questions or concerns. >> >> Thanks, >> Cory >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. -- Cory Quammen R&D Engineer Kitware, Inc. From andy.bauer at kitware.com Fri Aug 5 17:04:26 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 5 Aug 2016 17:04:26 -0400 Subject: [Paraview-developers] Changes coming to ParaView's color legend In-Reply-To: <0cd9e1410a5f4d0e8aea1e7bf21268b9@ES08AMSNLNT.srn.sandia.gov> References: <0cd9e1410a5f4d0e8aea1e7bf21268b9@ES08AMSNLNT.srn.sandia.gov> Message-ID: I'm having a tough time judging between the two without my normal context (i.e. having some geometry in the images). Also, having the same lookup table bounds and increments would make it easier for me to compare. I'm not as visually imaginative as Ken to fill in the rest of the details on my own :) On Fri, Aug 5, 2016 at 4:58 PM, Moreland, Kenneth wrote: > I personally like the thinner one (on the right). Does anyone else have an > opinion? > > -Ken > > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: Friday, August 5, 2016 2:29 PM > To: Moreland, Kenneth > Cc: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Changes coming to ParaView's > color legend > > > If it is not trouble, can you make one minor change? Can you make the > new color bar a little bit thinner? I think it makes the bar look a bit > more slick. > > Ken, > > Yes, it is very easy to change the default color bar thickness. > Attached is an image with two thinner scalar bars. Which do you prefer? > > Thanks for the suggestion, > Cory > > > > > -----Original Message----- > > From: Paraview-developers > > [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Cory > > Quammen > > Sent: Thursday, August 4, 2016 9:58 AM > > To: ParaView Developers > > Subject: [EXTERNAL] Re: [Paraview-developers] Changes coming to > > ParaView's color legend > > > > For a small preview of how the new implementation compares to the > current one, please see the attached screenshots of the current and new > color legend. The files ending in "Current.png" are from ParaView 5.1, > while files ending in "New.png" are from the new color legend not yet in > ParaView. > > > > - Cory > > > > On Thu, Aug 4, 2016 at 10:52 AM, Cory Quammen > wrote: > >> Hi folks, > >> > >> There are a number of issues with ParaView's current color legend. > >> Here are a few: > >> > >> http://www.paraview.org/Bug/view.php?id=15875 > >> http://www.paraview.org/Bug/view.php?id=16000 > >> http://www.paraview.org/Bug/view.php?id=15379 > >> http://www.paraview.org/Bug/view.php?id=15074 > >> http://www.paraview.org/Bug/view.php?id=15864 > >> http://www.paraview.org/Bug/view.php?id=15862 > >> http://www.paraview.org/Bug/view.php?id=15851 > >> http://www.paraview.org/Bug/view.php?id=15637 > >> http://www.paraview.org/Bug/view.php?id=15319 > >> http://www.paraview.org/Bug/view.php?id=14980 > >> http://www.paraview.org/Bug/view.php?id=15049 > >> http://www.paraview.org/Bug/view.php?id=14146 > >> > >> You get the idea... > >> > >> To address most of these issues and to make future fixes hopefully > >> more straightforward, I have been working on a new implementation of > >> ParaView's color legend. Key improvements in the implementation > >> include: > >> > >> - numerous bug fixes > >> - ability to specify precisely the values to label > >> - improved automatic "human-readable" values for the tick labels > >> - font size controls that offer precise control over font properties. > >> Size can be arbtitrary, for exampld > >> - precise control over the color bar thickness > >> - uses VTK's charts API, so making future improvements to the scalar > >> bar is easier than in the current implementation > >> > >> While the color legend will look similar to the current color legend, > >> you will likely see some differences once this change lands in master. > >> Any baseline image used by testing infrastructure for ParaView or > >> ParaView-based applications with a color legend will probably need to > >> be updated. > >> > >> Note that these changes are in ParaView only and do not affect the > >> scalar bars in VTK. > >> > >> I plan to put together a blog post on the Kitware web site showing > >> off the new color legend in the near future. In the mean time, please > >> let me know if you have any questions or concerns. > >> > >> Thanks, > >> Cory > >> > >> > >> -- > >> Cory Quammen > >> R&D Engineer > >> Kitware, Inc. > > > > > > > > -- > > Cory Quammen > > R&D Engineer > > Kitware, Inc. > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Aug 9 10:10:56 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 9 Aug 2016 10:10:56 -0400 Subject: [Paraview-developers] Dashboards Message-ID: Folks, The dashboards have gotten to a bit of a messy state in the past few days. Can we focus our efforts on cleaning things up on the dashboards before adding new features please. Thanks! From mathieu.westphal at kitware.com Tue Aug 9 11:10:25 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 9 Aug 2016 17:10:25 +0200 Subject: [Paraview-developers] [vtk-developers] Dashboards In-Reply-To: References: Message-ID: As far as i know, valgrind defect are not tracked by the dashboards, only vtk leaks, is it not ? Mathieu Westphal On Tue, Aug 9, 2016 at 5:08 PM, Bill Lorensen wrote: > And do not forget the valgrind defects... > > > On Tue, Aug 9, 2016 at 10:10 AM, Utkarsh Ayachit > wrote: > > Folks, > > > > The dashboards have gotten to a bit of a messy state in the past few > > days. Can we focus our efforts on cleaning things up on the dashboards > > before adding new features please. > > > > Thanks! > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > > > Search the list archives at: http://markmail.org/search/?q= > vtk-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/vtk-developers > > > > > > -- > Unpaid intern in BillsBasement at noware dot com > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sumeet.kumar507 at gmail.com Wed Aug 10 02:58:59 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Tue, 9 Aug 2016 23:58:59 -0700 Subject: [Paraview-developers] Selective sending of Field data to Paraview VCR based on user request Message-ID: Hello all, I have a unstructured mesh with many fields like Displacements, velocity, Stresses, Strains, Material no.. etc either on nodes or on cell. Currently, I associate all the field data arrays with my unstructured mesh and send it to ParaView for visualization and it works great.. But, now, since I have many field data and the mesh can be also very large. Sending all data at once would be very *slow and in-efficient.* What I want is the following: - I want that based on user request I should send attach that field data only. For example in the ParaView, if the User selects Displacements to Visualize, I should some how know that and only send displacements and similarly. - Also, I want that the user should be able to see all the different field data options I have, so that he can select and ask for as it is done normally . - I also, want that if the user selects a filter like, *wrap by vector *with displacements and chooses to see stress, ParaView should generate requests for *displacements and stresses so that I can send them.* I would be really thankfull, if someone could answer my queries. Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomasblome at startmail.com Wed Aug 10 07:54:50 2016 From: thomasblome at startmail.com (thomasblome at startmail.com) Date: Wed, 10 Aug 2016 13:54:50 +0200 Subject: [Paraview-developers] Paraview build in VS Message-ID: I?m trying to build paraview from source, therefore using: * Windows 7 * Visual Studio 2010 * Qt 4.8.7 * Python 2.7.8 * msmpi 7 * paraview source, version 5.1.0 In CMake I can choose different options to specify what functionality to include into the build process. I tried different combinations, like setting BUILD_EXAMPLES or PARAVIEW_USE_MPI, respectively. Now I have got following questions: 1. When I set BUILD_SHARED_LIBS and PARAVIEW_ENABLE_PYTHON as well (besides others, but I know those two cause the problem), configuring and generating the project with CMake is successful, but compiling in VS fails; it keeps freezing right after starting the compilation. Did anybody experience the same problem and how did you solve it? (By the way, if I switch off BUILD_SHARED_LIBS it works, but I don?t want a static build of paraview). 2. By using the combination BUILD_EXAMPLES, BUILD_TESTING, PARAVIEW_BUILD_QT_GUI, PARAVIEW_ENABLE_CATALYST, PARAVIEW_ENABLE_PYTHON and PARAVIEW_USE_MPI the same problem as described in 1.) occurs, but that is more or less what I need to use catalyst to perform in-situ analysis of my FEM simulation. (Incidentally, if I switch off BUILD_TESTING in the above combination it works, but I need CTest to test the catalyst examples as described here . Does anybody now how to fix that problem? 3. As shown at GitHub , some examples have been updated to work properly in paraview 4.4. Is my version of paraview (5.1.0) unsuitable for the catalyst examples? Is that the reason why VS is always hanging up for particular variable settings in CMake and which version of paraview is most suitable to get the catalyst examples going? I'd appreciate any help! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 7F53DEC77F67D0E0.asc Type: application/pgp-keys Size: 3082 bytes Desc: OpenPGP public keys URL: From mathieu.westphal at kitware.com Wed Aug 10 10:17:16 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 10 Aug 2016 16:17:16 +0200 Subject: [Paraview-developers] RenderView management python segfault In-Reply-To: References: Message-ID: Hello All I'm experiencing a systematic segfault with the following code in pvpython : from paraview.simple import * import gc v=CreateRenderView() Render(v) w=CreateRenderView() Render(w) Delete(v) del v gc.collect() # not absolutelly necessary, the destructor will be called eventually, but this ensure the bug to happen at the next call. Render(w) [xcb] Unknown sequence number while appending request [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pvpython: xcb_io.c:161: append_pending_request: Assertion `!xcb_xlib_unknown_seq_number' failed. Aborted (core dumped) Basically, * Creating and rendering a first view, * then Creating and rendering a second render view, * then destroying the first view, will put the second in a unstable state that will lead to a segfault. Does not reproduce in paraview, pvpython only. I've added a bug in paraview bugtracker : http://www.paraview.org/Bug/view.php?id=16767 If you have any idea why does it happen and how to correct it it would be great ! Mathieu Westphal On Fri, Jul 1, 2016 at 5:19 PM, Mathieu Westphal < mathieu.westphal at kitware.com> wrote: > Hello > > I'm experiencing a systematic segfault with the following code in pvpython > : > > from paraview.simple import * > import gc > > v=CreateRenderView() > Render(v) > w=CreateRenderView() > Render(w) > > Delete(v) > del v > gc.collect() # not absolutally necessary, the destructor will be called > eventually > > Render(w) > > > [xcb] Unknown sequence number while appending request > [xcb] Most likely this is a multi-threaded client and XInitThreads has not > been called > [xcb] Aborting, sorry about that. > pvpython: xcb_io.c:161: append_pending_request: Assertion > `!xcb_xlib_unknown_seq_number' failed. > Aborted (core dumped) > > Basically, Creating and rendering a first view, then Creating and > rendering a second render view, then destroying the first view, will put > the second in a unstable state that will lead to a segfault. > Does not reproduce in paraview. > > I've added a bug in paraview bugtracker : > http://www.paraview.org/Bug/view.php?id=16767 > > If you have any idea why does it happen and how to correct it it would be > great ! > > Mathieu Westphal > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bugRender.py Type: text/x-python Size: 144 bytes Desc: not available URL: From ben.boeckel at kitware.com Wed Aug 10 10:39:23 2016 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 10 Aug 2016 10:39:23 -0400 Subject: [Paraview-developers] [ANN] Buildbot updates In-Reply-To: <20151119192947.GA11791@megas.khq.kitware.com> References: <20151119192947.GA11791@megas.khq.kitware.com> Message-ID: <20160810143923.GB14268@megas.kitware.com> On Thu, Nov 19, 2015 at 14:29:47 -0500, Ben Boeckel wrote: > A more disruptive change that has been discussed a bit would be to make > the --oneshot argument the default and instead switching around to using > --continuous instead to have "rebuild on push" behavior. So by default, > every push would need another "Do: test" to trigger a build. This would > help reduce the amount of clutter on the buildbots. I've made this change and would plan on deploying it this week. Commands already given are still using the old behavior. --Ben From cory.quammen at kitware.com Wed Aug 10 11:24:47 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 10 Aug 2016 11:24:47 -0400 Subject: [Paraview-developers] Selective sending of Field data to Paraview VCR based on user request In-Reply-To: References: Message-ID: Sumeet, Could you clarify what you mean by "sending data to ParaView"? Thanks, Cory On Wed, Aug 10, 2016 at 2:58 AM, sumeet kumar wrote: > Hello all, > > I have a unstructured mesh with many fields like Displacements, velocity, > Stresses, Strains, Material no.. etc either on nodes or on cell. Currently, > I associate all the field data arrays with my unstructured mesh and send it > to ParaView for visualization and it works great.. > > But, now, since I have many field data and the mesh can be also very > large. Sending all data at once would be very *slow and in-efficient.* > > What I want is the following: > > - I want that based on user request I should send attach that field > data only. For example in the ParaView, if the User selects Displacements > to Visualize, I should some how know that and only send displacements and > similarly. > - Also, I want that the user should be able to see all the different > field data options I have, so that he can select and ask for as it is done > normally . > - I also, want that if the user selects a filter like, *wrap by vector > *with displacements and chooses to see stress, ParaView should > generate requests for *displacements and stresses so that I can send > them.* > > I would be really thankfull, if someone could answer my queries. > > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetsinha.in/ > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Wed Aug 10 11:37:25 2016 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 10 Aug 2016 11:37:25 -0400 Subject: [Paraview-developers] Mantis -> Gitlab issue migration Message-ID: <20160810153725.GA12991@megas.kitware.com> Hi, I'm planning on doing the Mantis -> Gitlab issue migration on Friday morning. In order to do this, it is planned to take down Gitlab for about 2 hours to prevent any issues from being created which would cause off-by-one problems with the issue number preservation. Mantis will be made read-only tomorrow so that a snapshot of the existing issue state can be properly made. The plan is to have it complete by 9 AM EDT (13:00 UTC). Thanks, --Ben From bastien.jacquet at kitware.com Thu Aug 11 07:12:06 2016 From: bastien.jacquet at kitware.com (Bastien Jacquet) Date: Thu, 11 Aug 2016 13:12:06 +0200 Subject: [Paraview-developers] Failed Superbuild in Debug mode Message-ID: Hello dear Paraview developers, I tried to build a fresh Veloview (it's a custom Paraview) using the superbuild (similar to Paraview's). It goes well in Release or RelWithDebInfo. It fails in Debug. It is complaining about python27_d.lib not being found. I solved this by setting the CMAKE python debug lib to python.lib. The next failure is about qtmain_win.lib, it complains with the following error: error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doen't match value '2' in VeloView_main.obj error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doen't match value 'MD_DynamicDebug' Notice that VeloView uses pythonqt too. Is it a know problem? Is there a workaround for compiling the superbuild in Debug without using the system installed python/qt libs? Should the superbuild ship python and qt debug libs too? Best, Bastien -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Aug 11 09:55:05 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 11 Aug 2016 09:55:05 -0400 Subject: [Paraview-developers] Failed Superbuild in Debug mode In-Reply-To: References: Message-ID: Bastien, > Is it a know problem? To my knowledge, superbuild is only intended to build release builds intended for packaging or installation. For development and debugging, developers usually build ParaView by itself. I recommend doing the same unless you really need the superbuild for something. There are certain advantages to doing so, e.g., the superbuild system isn't quite as smart as CMake when it comes to rebuilding only the parts of ParaView that are needed when you make source code changes. HTH, Cory -- Cory Quammen R&D Engineer Kitware, Inc. From mathieu.westphal at kitware.com Thu Aug 11 10:00:04 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Thu, 11 Aug 2016 16:00:04 +0200 Subject: [Paraview-developers] Making paraView dev life easier with custom app Message-ID: Hello All If you are working on a Custom Application based on ParaView and you do not *always* want to use pqPipelineBrowserWidget/pqPropertiesPanel/pqTabbedMultiViewWidget, you are definitelly concerned by this mail. I am drafting up MRs allowing dev to - use pqTabbedMultiViewWidget-independant view, - helping show data without using ApplyBehavior and pqPropertiesPanel - Creating a correctly configured pqPipelineBrowser after the initialization of the application In case you want to give inputs and reviews, please feel free to take a look : https://gitlab.kitware.com/paraview/paraview/merge_requests/936 (Ready For review/critics) https://gitlab.kitware.com/paraview/paraview/merge_requests/937 (Still on developpement) Regards, Mathieu Westphal -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Fri Aug 12 07:58:29 2016 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 12 Aug 2016 07:58:29 -0400 Subject: [Paraview-developers] Mantis -> Gitlab issue migration In-Reply-To: <20160810153725.GA12991@megas.kitware.com> References: <20160810153725.GA12991@megas.kitware.com> Message-ID: <20160812115829.GC10731@megas.kitware.com> On Wed, Aug 10, 2016 at 11:37:25 -0400, Ben Boeckel wrote: > I'm planning on doing the Mantis -> Gitlab issue migration on Friday > morning. In order to do this, it is planned to take down Gitlab for > about 2 hours to prevent any issues from being created which would cause > off-by-one problems with the issue number preservation. Mantis will be > made read-only tomorrow so that a snapshot of the existing issue state > can be properly made. The plan is to have it complete by 9 AM EDT (13:00 > UTC). The import is complete; gitlab.kitware.com should be accessible again soon. --Ben From sumeet.kumar507 at gmail.com Fri Aug 12 11:44:16 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Fri, 12 Aug 2016 08:44:16 -0700 Subject: [Paraview-developers] Sending only the user/client requested field data to Paraview Message-ID: Hello all, I have a unstructured mesh with many fields like Displacements, velocity, Stresses, Strains, Material no.. etc either on nodes or on cell. Currently, I associate all the field data arrays with my unstructured mesh and send it to ParaView for visualization and it works great.. But, now, since I have many field data and the mesh can be also very large. Sending all data at once would be very *slow and in-efficient.* What I want is the following: - I want that based on user request I should send attach that field data only. For example in the ParaView, if the User selects Displacements to Visualize, I should some how know that and only send displacements and similarly. - Also, I want that the user should be able to see all the different field data options I have, so that he can select and ask for as it is done normally . - I also, want that if the user selects a filter like, *wrap by vector *with displacements and chooses to see stress, ParaView should generate requests for *displacements and stresses so that I can send them.* Currently I am doing this from my reader. Node_Mesh->GetPointData()->AddArray(Generalized_Displacements); Node_Mesh->GetPointData()->AddArray(Node_Tag); Node_Mesh->GetCellData()->AddArray(Element_Tag); Node_Mesh->GetCellData()->AddArray(Material_Tag); Node_Mesh->GetPointData()->AddArray(Elastic_Strain); Node_Mesh->GetPointData()->AddArray(Plastic_Strain); Node_Mesh->GetPointData()->AddArray(Stress); Which means I am sending all field data *Generalized_Displacemnts , Node_Tag, Element_Tag, Material_tag, Elastic_Strain ........ * Now suppose, in Paraview, user selects field_data *Generalized Displacements *.to visualize. [image: Inline image 2] Currently, I am sending all the field data associated with that mesh as stated above. In order to be efficient, I want to send only *Generalized_Displacements* in the next time step. But at the same time, I want that the user should be able to see all the field datasets, so that if he changes his mind and select other field dataset to visualize, I would get a request and send the same data. In other words, I want to respond to the events when (the choice of field data to visualize is changed), so that i can send that field data only. But, The user should be able to view other field data options available, so that they can change the request what they want to visualize a particular field data . Basically, I want to respond to this event as shown above. -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 46611 bytes Desc: not available URL: From cory.quammen at kitware.com Fri Aug 12 11:50:28 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 12 Aug 2016 11:50:28 -0400 Subject: [Paraview-developers] Selective sending of Field data to Paraview VCR based on user request In-Reply-To: References: Message-ID: Sumeet, Please include the list with your reply so that others may participate in the conversation. It is possible at the reader level to specify which arrays are loaded through the reader properties panel. See the VTU and Exodus II file readers in ParaView, for example. However, any unloaded arrays will not be displayed in the Color By combobox. At present, I do not believe it is possible to do what you are asking without some significant source code changes within ParaView. For example, support for consumers to request subsets of data arrays from producers, like your reader, would need to be added. That's a fairly heavy lift. Your best bet for now is probably to support selecting which arrays are loaded by your reader. See the xml description for XMLUnstructuredGridReaderCore in paraview/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml for an example of how to set this up. HTH, Cory On Wed, Aug 10, 2016 at 1:05 PM, sumeet kumar wrote: > Hey Cory, > > Currently I am doing this from my reader. > > Node_Mesh->GetPointData()->AddArray(Generalized_Displacements); > Node_Mesh->GetPointData()->AddArray(Node_Tag); > Node_Mesh->GetCellData()->AddArray(Element_Tag); > Node_Mesh->GetCellData()->AddArray(Material_Tag); > Node_Mesh->GetPointData()->AddArray(Elastic_Strain); > Node_Mesh->GetPointData()->AddArray(Plastic_Strain); > Node_Mesh->GetPointData()->AddArray(Stress); > Which means I am sending all field data > *Generalized_Displacemnts , Node_Tag, Element_Tag, Material_tag, > Elastic_Strain ........ * > Now suppose, in Paraview, user selects field_data *Generalized > Displacements *.to visualize. > > Currently, I am sending all the field data associated with that mesh as > stated above. In order to be efficient, I want to send only > *Generalized_Displacements* in the next time step. > But at the same time, I want that the user should be able to see all the > field datasets, so that if he changes his mind and select other field > dataset to visualize, I would get a request and send the same data. > > In other words, I want to respond to the events when (the choice of field > data to visualize is changed), so that i can send that field data only. > But, The user should be able to view other field data options, so that > they can change the request what they want to visualize. > Basically, I want to respond to this event as shown below > > [image: Inline image 2] > > > Sumeet > > > On Wed, Aug 10, 2016 at 8:24 AM, Cory Quammen > wrote: > >> Sumeet, >> >> Could you clarify what you mean by "sending data to ParaView"? >> >> Thanks, >> Cory >> >> On Wed, Aug 10, 2016 at 2:58 AM, sumeet kumar >> wrote: >> >>> Hello all, >>> >>> I have a unstructured mesh with many fields like Displacements, >>> velocity, Stresses, Strains, Material no.. etc either on nodes or on cell. >>> Currently, I associate all the field data arrays with my unstructured mesh >>> and send it to ParaView for visualization and it works great.. >>> >>> But, now, since I have many field data and the mesh can be also very >>> large. Sending all data at once would be very *slow and in-efficient.* >>> >>> What I want is the following: >>> >>> - I want that based on user request I should send attach that field >>> data only. For example in the ParaView, if the User selects Displacements >>> to Visualize, I should some how know that and only send displacements and >>> similarly. >>> - Also, I want that the user should be able to see all the different >>> field data options I have, so that he can select and ask for as it is done >>> normally . >>> - I also, want that if the user selects a filter like, *wrap by >>> vector *with displacements and chooses to see stress, ParaView >>> should generate requests for *displacements and stresses so that I >>> can send them.* >>> >>> I would be really thankfull, if someone could answer my queries. >>> >>> >>> Sumeet Kumar Sinha >>> Graduate Student >>> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >>> Website : http://www.sumeetsinha.in/ >>> >> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> > > > > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetsinha.in/ > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 46611 bytes Desc: not available URL: From sumeet.kumar507 at gmail.com Fri Aug 12 11:54:04 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Fri, 12 Aug 2016 08:54:04 -0700 Subject: [Paraview-developers] Reading multiple files in parallel Message-ID: Hello all, I have a number of files which contains information about pieces of unstructured mesh. For example :- t_2.h5.01.feioutput t_2.h5.03.feioutput t_2.h5.04.feioutput t_2.h5.05.feioutput t_2.h5.06.feioutput t_2.h5.07.feioutput t_2.h5.08.feioutput t_2.h5.09.feioutput t_2.h5.feioutput My reader can read each file individually but I want to read them all in parallel so that I can visualize the whole model. I looked at the http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the steps for unstructured mesh. When I try to set the number of pieces in Request Information function as this vtkInformation* Node_Mesh = outVec->GetInformationObject(0); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); I get the following error error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of ?vtkStreamingDemandDrivenPipeline? Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); Also, it would be highly appreciated if anyone could show/(send me link) me to a sample example. Regards Sumeet -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sumeet.kumar507 at gmail.com Sat Aug 13 02:48:12 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Fri, 12 Aug 2016 23:48:12 -0700 Subject: [Paraview-developers] Selective sending of Field data to Paraview VCR based on user request In-Reply-To: References: Message-ID: Thank you Cory, Yeah, the only best option seems available is to support selecting which arrays are loaded by the reader. But, I just want to let you know that I think VISIT's *avtvisit FileFormat* supports this. Sumeet On Fri, Aug 12, 2016 at 8:50 AM, Cory Quammen wrote: > Sumeet, > > Please include the list with your reply so that others may participate in > the conversation. > > It is possible at the reader level to specify which arrays are loaded > through the reader properties panel. See the VTU and Exodus II file readers > in ParaView, for example. However, any unloaded arrays will not be > displayed in the Color By combobox. > > At present, I do not believe it is possible to do what you are asking > without some significant source code changes within ParaView. For example, > support for consumers to request subsets of data arrays from producers, > like your reader, would need to be added. That's a fairly heavy lift. > > Your best bet for now is probably to support selecting which arrays are > loaded by your reader. See the xml description for > XMLUnstructuredGridReaderCore in > > paraview/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml > > for an example of how to set this up. > > HTH, > Cory > > > On Wed, Aug 10, 2016 at 1:05 PM, sumeet kumar > wrote: > >> Hey Cory, >> >> Currently I am doing this from my reader. >> >> Node_Mesh->GetPointData()->AddArray(Generalized_Displacements); >> Node_Mesh->GetPointData()->AddArray(Node_Tag); >> Node_Mesh->GetCellData()->AddArray(Element_Tag); >> Node_Mesh->GetCellData()->AddArray(Material_Tag); >> Node_Mesh->GetPointData()->AddArray(Elastic_Strain); >> Node_Mesh->GetPointData()->AddArray(Plastic_Strain); >> Node_Mesh->GetPointData()->AddArray(Stress); >> Which means I am sending all field data >> *Generalized_Displacemnts , Node_Tag, Element_Tag, Material_tag, >> Elastic_Strain ........ * >> Now suppose, in Paraview, user selects field_data *Generalized >> Displacements *.to visualize. >> >> Currently, I am sending all the field data associated with that mesh as >> stated above. In order to be efficient, I want to send only >> *Generalized_Displacements* in the next time step. >> But at the same time, I want that the user should be able to see all the >> field datasets, so that if he changes his mind and select other field >> dataset to visualize, I would get a request and send the same data. >> >> In other words, I want to respond to the events when (the choice of field >> data to visualize is changed), so that i can send that field data only. >> But, The user should be able to view other field data options, so that >> they can change the request what they want to visualize. >> Basically, I want to respond to this event as shown below >> >> [image: Inline image 2] >> >> >> Sumeet >> >> >> On Wed, Aug 10, 2016 at 8:24 AM, Cory Quammen >> wrote: >> >>> Sumeet, >>> >>> Could you clarify what you mean by "sending data to ParaView"? >>> >>> Thanks, >>> Cory >>> >>> On Wed, Aug 10, 2016 at 2:58 AM, sumeet kumar >> > wrote: >>> >>>> Hello all, >>>> >>>> I have a unstructured mesh with many fields like Displacements, >>>> velocity, Stresses, Strains, Material no.. etc either on nodes or on cell. >>>> Currently, I associate all the field data arrays with my unstructured mesh >>>> and send it to ParaView for visualization and it works great.. >>>> >>>> But, now, since I have many field data and the mesh can be also very >>>> large. Sending all data at once would be very *slow and in-efficient.* >>>> >>>> What I want is the following: >>>> >>>> - I want that based on user request I should send attach that field >>>> data only. For example in the ParaView, if the User selects Displacements >>>> to Visualize, I should some how know that and only send displacements and >>>> similarly. >>>> - Also, I want that the user should be able to see all the >>>> different field data options I have, so that he can select and ask for as >>>> it is done normally . >>>> - I also, want that if the user selects a filter like, *wrap by >>>> vector *with displacements and chooses to see stress, ParaView >>>> should generate requests for *displacements and stresses so that I >>>> can send them.* >>>> >>>> I would be really thankfull, if someone could answer my queries. >>>> >>>> >>>> Sumeet Kumar Sinha >>>> Graduate Student >>>> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >>>> Website : http://www.sumeetsinha.in/ >>>> >>> >>> >>> >>> -- >>> Cory Quammen >>> R&D Engineer >>> Kitware, Inc. >>> >> >> >> >> -- >> >> Sumeet Kumar Sinha >> Graduate Student >> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >> Website : http://www.sumeetsinha.in/ >> > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 46611 bytes Desc: not available URL: From sumeet.kumar507 at gmail.com Mon Aug 15 14:57:58 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Mon, 15 Aug 2016 11:57:58 -0700 Subject: [Paraview-developers] Reading multiple files in parallel Message-ID: Hello all, I have a number of files which contains information about pieces of unstructured mesh. For example :- t_2.h5.01.feioutput t_2.h5.03.feioutput t_2.h5.04.feioutput t_2.h5.05.feioutput t_2.h5.06.feioutput t_2.h5.07.feioutput t_2.h5.08.feioutput t_2.h5.09.feioutput t_2.h5.feioutput My reader can read each file individually but I want to read them all in parallel so that I can visualize the whole model. I looked at the http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the steps for unstructured mesh. When I try to set the number of pieces in Request Information function as this vtkInformation* Node_Mesh = outVec->GetInformationObject(0); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); I get the following error error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of ? vtkStreamingDemandDrivenPipeline? Node_Mesh->Set(vtkStreamingDemandDrivenPipeli ne::MAXIMUM_NUMBER_OF_PIECES(), 10); Also, it would be highly appreciated if anyone could show/(send me link) me to a sample example. Regards -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Mon Aug 15 15:57:01 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 15 Aug 2016 19:57:01 +0000 Subject: [Paraview-developers] Reading multiple files in parallel Message-ID: <6e279cec48a8454abc07633b9ac79c5a@ES08AMSNLNT.srn.sandia.gov> I think the key you are looking for is vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), which you want to set to 1 to signify that you can provide multiple pieces. You might want to look at vtkmXMLPUnstructuredGridDataReader for an example. If I remember correctly, this has recently been changed in VTK. It used to be that you would give the number of pieces you supported, but that functionality was not useful in practice and consequently readers reported that they could produce any number of pieces in order to be useful. Thus, the behavior was change to allow readers simply to report whether or not they support multiple pieces. Berk can probably provide more information. -Ken From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of sumeet kumar Sent: Monday, August 15, 2016 12:58 PM To: ParaView Developers Subject: [EXTERNAL] [Paraview-developers] Reading multiple files in parallel Hello all, I have a number of files which contains information about pieces of unstructured mesh. For example :- t_2.h5.01.feioutput t_2.h5.03.feioutput t_2.h5.04.feioutput t_2.h5.05.feioutput t_2.h5.06.feioutput t_2.h5.07.feioutput t_2.h5.08.feioutput t_2.h5.09.feioutput t_2.h5.feioutput My reader can read each file individually but I want to read them all in parallel so that I can visualize the whole model. I looked at the http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the steps for unstructured mesh. When I try to set the number of pieces in Request Information function as this vtkInformation* Node_Mesh = outVec->GetInformationObject(0); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); I get the following error error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of ?vtkStreamingDemandDrivenPipeline? Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); Also, it would be highly appreciated if anyone could show/(send me link) me to a sample example. Regards -- [Image removed by sender.] Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: ~WRD000.jpg URL: From sumeet.kumar507 at gmail.com Mon Aug 15 17:52:19 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Mon, 15 Aug 2016 14:52:19 -0700 Subject: [Paraview-developers] Reading multiple files in parallel In-Reply-To: <6e279cec48a8454abc07633b9ac79c5a@ES08AMSNLNT.srn.sandia.gov> References: <6e279cec48a8454abc07633b9ac79c5a@ES08AMSNLNT.srn.sandia.gov> Message-ID: Thanks Kenneth, for you help. I get the vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), set 1 part. But, what to do next. How can i get the piece no, so that i can update the data for it. vtkmXMLPUnstructuredGridDataReader is not doing me a great help. Sumeet On Mon, Aug 15, 2016 at 12:57 PM, Moreland, Kenneth wrote: > I think the key you are looking for is vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), > which you want to set to 1 to signify that you can provide multiple pieces. > You might want to look at vtkmXMLPUnstructuredGridDataReader for an > example. > > > > If I remember correctly, this has recently been changed in VTK. It used to > be that you would give the number of pieces you supported, but that > functionality was not useful in practice and consequently readers reported > that they could produce any number of pieces in order to be useful. Thus, > the behavior was change to allow readers simply to report whether or not > they support multiple pieces. Berk can probably provide more information. > > > > -Ken > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] *On Behalf Of *sumeet kumar > *Sent:* Monday, August 15, 2016 12:58 PM > *To:* ParaView Developers > *Subject:* [EXTERNAL] [Paraview-developers] Reading multiple files in > parallel > > > > Hello all, > > I have a number of files which contains information about pieces of > unstructured mesh. For example :- > > t_2.h5.01.feioutput > t_2.h5.03.feioutput > t_2.h5.04.feioutput > t_2.h5.05.feioutput > t_2.h5.06.feioutput > t_2.h5.07.feioutput > t_2.h5.08.feioutput > t_2.h5.09.feioutput > t_2.h5.feioutput > > My reader can read each file individually but I want to read them all in > parallel so that I can visualize the whole model. I looked at the > http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the > steps for unstructured mesh. > > When I try to set the number of pieces in Request Information function as > this > > vtkInformation* Node_Mesh = outVec->GetInformationObject(0); > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::MAXIMUM_NUMBER_OF_PIECES(), 10); > > > > I get the following error > > error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of ? > vtkStreamingDemandDrivenPipeline? > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::MAXIMUM_NUMBER_OF_PIECES(), 10); > > > > Also, it would be highly appreciated if anyone could show/(send me link) > me to a sample example. > > Regards > > -- > > [image: Image removed by sender.] > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Aug 15 18:37:17 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 15 Aug 2016 22:37:17 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Changes coming to ParaView's color legend In-Reply-To: <0cd9e1410a5f4d0e8aea1e7bf21268b9@ES08AMSNLNT.srn.sandia.gov> References: <0cd9e1410a5f4d0e8aea1e7bf21268b9@ES08AMSNLNT.srn.sandia.gov> Message-ID: Sorry for taking so long to add feedback. I have been on vacation. I also like the thinner one, the one on the right. Alan -----Original Message----- From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Moreland, Kenneth Sent: Friday, August 05, 2016 2:58 PM To: Cory Quammen Cc: ParaView Developers Subject: [EXTERNAL] Re: [Paraview-developers] Changes coming to ParaView's color legend I personally like the thinner one (on the right). Does anyone else have an opinion? -Ken -----Original Message----- From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Friday, August 5, 2016 2:29 PM To: Moreland, Kenneth Cc: ParaView Developers Subject: [EXTERNAL] Re: [Paraview-developers] Changes coming to ParaView's color legend > If it is not trouble, can you make one minor change? Can you make the new color bar a little bit thinner? I think it makes the bar look a bit more slick. Ken, Yes, it is very easy to change the default color bar thickness. Attached is an image with two thinner scalar bars. Which do you prefer? Thanks for the suggestion, Cory > > -----Original Message----- > From: Paraview-developers > [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Cory > Quammen > Sent: Thursday, August 4, 2016 9:58 AM > To: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Changes coming to > ParaView's color legend > > For a small preview of how the new implementation compares to the current one, please see the attached screenshots of the current and new color legend. The files ending in "Current.png" are from ParaView 5.1, while files ending in "New.png" are from the new color legend not yet in ParaView. > > - Cory > > On Thu, Aug 4, 2016 at 10:52 AM, Cory Quammen wrote: >> Hi folks, >> >> There are a number of issues with ParaView's current color legend. >> Here are a few: >> >> http://www.paraview.org/Bug/view.php?id=15875 >> http://www.paraview.org/Bug/view.php?id=16000 >> http://www.paraview.org/Bug/view.php?id=15379 >> http://www.paraview.org/Bug/view.php?id=15074 >> http://www.paraview.org/Bug/view.php?id=15864 >> http://www.paraview.org/Bug/view.php?id=15862 >> http://www.paraview.org/Bug/view.php?id=15851 >> http://www.paraview.org/Bug/view.php?id=15637 >> http://www.paraview.org/Bug/view.php?id=15319 >> http://www.paraview.org/Bug/view.php?id=14980 >> http://www.paraview.org/Bug/view.php?id=15049 >> http://www.paraview.org/Bug/view.php?id=14146 >> >> You get the idea... >> >> To address most of these issues and to make future fixes hopefully >> more straightforward, I have been working on a new implementation of >> ParaView's color legend. Key improvements in the implementation >> include: >> >> - numerous bug fixes >> - ability to specify precisely the values to label >> - improved automatic "human-readable" values for the tick labels >> - font size controls that offer precise control over font properties. >> Size can be arbtitrary, for exampld >> - precise control over the color bar thickness >> - uses VTK's charts API, so making future improvements to the scalar >> bar is easier than in the current implementation >> >> While the color legend will look similar to the current color legend, >> you will likely see some differences once this change lands in master. >> Any baseline image used by testing infrastructure for ParaView or >> ParaView-based applications with a color legend will probably need to >> be updated. >> >> Note that these changes are in ParaView only and do not affect the >> scalar bars in VTK. >> >> I plan to put together a blog post on the Kitware web site showing >> off the new color legend in the near future. In the mean time, please >> let me know if you have any questions or concerns. >> >> Thanks, >> Cory >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. -- Cory Quammen R&D Engineer Kitware, Inc. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers From kmorel at sandia.gov Mon Aug 15 18:58:06 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 15 Aug 2016 22:58:06 +0000 Subject: [Paraview-developers] Reading multiple files in parallel Message-ID: <21adba1164ba43539fbec057479b83a9@ES08AMSNLNT.srn.sandia.gov> During the RequestData pass of the pipeline, you should be able to get the keys vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER() and vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES() from the output information object that comes from downstream. This will tell you how many pieces the pipeline expects and which piece is expected to be read. Generally the number of pieces requested will not match exactly the number of files that you have. This means you will have to adjust by either reading more than 1 file at a time or sometimes reading nothing and returning an empty object. -Ken From: sumeet kumar [mailto:sumeet.kumar507 at gmail.com] Sent: Monday, August 15, 2016 3:52 PM To: Moreland, Kenneth Cc: ParaView Developers Subject: [EXTERNAL] Re: [Paraview-developers] Reading multiple files in parallel Thanks Kenneth, for you help. I get the vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), set 1 part. But, what to do next. How can i get the piece no, so that i can update the data for it. vtkmXMLPUnstructuredGridDataReader is not doing me a great help. Sumeet On Mon, Aug 15, 2016 at 12:57 PM, Moreland, Kenneth > wrote: I think the key you are looking for is vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), which you want to set to 1 to signify that you can provide multiple pieces. You might want to look at vtkmXMLPUnstructuredGridDataReader for an example. If I remember correctly, this has recently been changed in VTK. It used to be that you would give the number of pieces you supported, but that functionality was not useful in practice and consequently readers reported that they could produce any number of pieces in order to be useful. Thus, the behavior was change to allow readers simply to report whether or not they support multiple pieces. Berk can probably provide more information. -Ken From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of sumeet kumar Sent: Monday, August 15, 2016 12:58 PM To: ParaView Developers > Subject: [EXTERNAL] [Paraview-developers] Reading multiple files in parallel Hello all, I have a number of files which contains information about pieces of unstructured mesh. For example :- t_2.h5.01.feioutput t_2.h5.03.feioutput t_2.h5.04.feioutput t_2.h5.05.feioutput t_2.h5.06.feioutput t_2.h5.07.feioutput t_2.h5.08.feioutput t_2.h5.09.feioutput t_2.h5.feioutput My reader can read each file individually but I want to read them all in parallel so that I can visualize the whole model. I looked at the http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the steps for unstructured mesh. When I try to set the number of pieces in Request Information function as this vtkInformation* Node_Mesh = outVec->GetInformationObject(0); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); I get the following error error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of ?vtkStreamingDemandDrivenPipeline? Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); Also, it would be highly appreciated if anyone could show/(send me link) me to a sample example. Regards -- Error! Filename not specified. Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -- [Image removed by sender.] Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 407 bytes Desc: image001.jpg URL: From sumeet.kumar507 at gmail.com Mon Aug 15 19:38:48 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Mon, 15 Aug 2016 16:38:48 -0700 Subject: [Paraview-developers] Reading multiple files in parallel In-Reply-To: <21adba1164ba43539fbec057479b83a9@ES08AMSNLNT.srn.sandia.gov> References: <21adba1164ba43539fbec057479b83a9@ES08AMSNLNT.srn.sandia.gov> Message-ID: Hey Ken, I am sorry that I am asking you a lot of stupid questions. But I am stuck here. I followed what you said, But I don't see the piece number getting updated. And also when would that stop being updated...etc. Here is my code int pvESSI::RequestInformation( vtkInformation *request, vtkInformationVector **vtkNotUsed(inVec), vtkInformationVector* outVec){ this->Initialize(); vtkInformation* Node_Mesh = outVec->GetInformationObject(0); double Time_range[2]={Time[0],Time[Number_Of_Time_Steps-1]}; Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_STEPS(),Time, this->Number_Of_Time_Steps); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_RANGE(),Time_range,2); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(),EXTENT,6); int num_of_piec = 10; Node_Mesh->Set(CAN_HANDLE_PIECE_REQUEST(), 1); return 1; } int pvESSI::RequestData(vtkInformation *vtkNotUsed(request),vtkInformationVector **vtkNotUsed(inputVector), vtkInformationVector *outputVector){ vtkInformation *Node_Mesh = outputVector->GetInformationObject(0); // outInfo->Print(std::cout); piece_no = Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER()); num_of_pieces = Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES()); cout << "Piece_No " << piece_no << endl; cout << "Number_of_Pieces " << piece_no << endl; Step_Initializer(Piece_No); // makes the file and variables ready for that piece this->Node_Mesh_Current_Time = Time_Map.find( Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()))->second; if (!Whether_Node_Mesh_Build){ this->Get_Node_Mesh(UGrid_Node_Mesh); UGrid_Current_Node_Mesh->ShallowCopy(UGrid_Node_Mesh); } Build_Node_Attributes(UGrid_Current_Node_Mesh, this->Node_Mesh_Current_Time ); Build_Stress_Field_At_Nodes(UGrid_Current_Node_Mesh, this->Node_Mesh_Current_Time); // get the ouptut pointer to paraview vtkUnstructuredGrid *Output_Node_Mesh = vtkUnstructuredGrid::SafeDownCast(Node_Mesh->Get(vtkDataObject::DATA_OBJECT())); Output_Node_Mesh->ShallowCopy(UGrid_Current_Node_Mesh); return 1; } When I run this code, The *Piece_no* and *Number_of_Pieces* both remain 0. Sumeet On Mon, Aug 15, 2016 at 3:58 PM, Moreland, Kenneth wrote: > During the RequestData pass of the pipeline, you should be able to get the > keys vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER() and > vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES() from the > output information object that comes from downstream. This will tell you > how many pieces the pipeline expects and which piece is expected to be read. > > > > Generally the number of pieces requested will not match exactly the number > of files that you have. This means you will have to adjust by either > reading more than 1 file at a time or sometimes reading nothing and > returning an empty object. > > > > -Ken > > > > *From:* sumeet kumar [mailto:sumeet.kumar507 at gmail.com] > *Sent:* Monday, August 15, 2016 3:52 PM > *To:* Moreland, Kenneth > *Cc:* ParaView Developers > *Subject:* [EXTERNAL] Re: [Paraview-developers] Reading multiple files in > parallel > > > > Thanks Kenneth, for you help. > > I get the vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), set 1 part. > > But, what to do next. > > How can i get the piece no, so that i can update the data for it. > > vtkmXMLPUnstructuredGridDataReader is not doing me a great help. > > Sumeet > > > > On Mon, Aug 15, 2016 at 12:57 PM, Moreland, Kenneth > wrote: > > I think the key you are looking for is vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), > which you want to set to 1 to signify that you can provide multiple pieces. > You might want to look at vtkmXMLPUnstructuredGridDataReader for an > example. > > > > If I remember correctly, this has recently been changed in VTK. It used to > be that you would give the number of pieces you supported, but that > functionality was not useful in practice and consequently readers reported > that they could produce any number of pieces in order to be useful. Thus, > the behavior was change to allow readers simply to report whether or not > they support multiple pieces. Berk can probably provide more information. > > > > -Ken > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] *On Behalf Of *sumeet kumar > *Sent:* Monday, August 15, 2016 12:58 PM > *To:* ParaView Developers > *Subject:* [EXTERNAL] [Paraview-developers] Reading multiple files in > parallel > > > > Hello all, > > I have a number of files which contains information about pieces of > unstructured mesh. For example :- > > t_2.h5.01.feioutput > t_2.h5.03.feioutput > t_2.h5.04.feioutput > t_2.h5.05.feioutput > t_2.h5.06.feioutput > t_2.h5.07.feioutput > t_2.h5.08.feioutput > t_2.h5.09.feioutput > t_2.h5.feioutput > > My reader can read each file individually but I want to read them all in > parallel so that I can visualize the whole model. I looked at the > http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the > steps for unstructured mesh. > > When I try to set the number of pieces in Request Information function as > this > > vtkInformation* Node_Mesh = outVec->GetInformationObject(0); > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::MAXIMUM_NUMBER_OF_PIECES(), 10); > > > > I get the following error > > error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of ? > vtkStreamingDemandDrivenPipeline? > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::MAXIMUM_NUMBER_OF_PIECES(), 10); > > > > Also, it would be highly appreciated if anyone could show/(send me link) > me to a sample example. > > Regards > > -- > > *Error! Filename not specified.* > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > > > > > -- > > [image: Image removed by sender.] > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 407 bytes Desc: not available URL: From kmorel at sandia.gov Tue Aug 16 11:03:50 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 16 Aug 2016 15:03:50 +0000 Subject: [Paraview-developers] Reading multiple files in parallel In-Reply-To: References: <21adba1164ba43539fbec057479b83a9@ES08AMSNLNT.srn.sandia.gov>, Message-ID: <1CB5ABB4-3C98-4899-ADFF-1B52B585FEF0@sandia.gov> Are you running ParaView in MPI parallel mode? If not, it might not set the number of pieces. Also, I don't think you need to set WHOLE_EXTENT. That is for structured type of data. -Ken Sent from my iPad so blame autocorrect. On Aug 15, 2016, at 5:38 PM, sumeet kumar > wrote: Hey Ken, I am sorry that I am asking you a lot of stupid questions. But I am stuck here. I followed what you said, But I don't see the piece number getting updated. And also when would that stop being updated...etc. Here is my code int pvESSI::RequestInformation( vtkInformation *request, vtkInformationVector **vtkNotUsed(inVec), vtkInformationVector* outVec){ this->Initialize(); vtkInformation* Node_Mesh = outVec->GetInformationObject(0); double Time_range[2]={Time[0],Time[Number_Of_Time_Steps-1]}; Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_STEPS(),Time, this->Number_Of_Time_Steps); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_RANGE(),Time_range,2); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(),EXTENT,6); int num_of_piec = 10; Node_Mesh->Set(CAN_HANDLE_PIECE_REQUEST(), 1); return 1; } int pvESSI::RequestData(vtkInformation *vtkNotUsed(request),vtkInformationVector **vtkNotUsed(inputVector), vtkInformationVector *outputVector){ vtkInformation *Node_Mesh = outputVector->GetInformationObject(0); // outInfo->Print(std::cout); piece_no = Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER()); num_of_pieces = Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES()); cout << "Piece_No " << piece_no << endl; cout << "Number_of_Pieces " << piece_no << endl; Step_Initializer(Piece_No); // makes the file and variables ready for that piece this->Node_Mesh_Current_Time = Time_Map.find( Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()))->second; if (!Whether_Node_Mesh_Build){ this->Get_Node_Mesh(UGrid_Node_Mesh); UGrid_Current_Node_Mesh->ShallowCopy(UGrid_Node_Mesh); } Build_Node_Attributes(UGrid_Current_Node_Mesh, this->Node_Mesh_Current_Time ); Build_Stress_Field_At_Nodes(UGrid_Current_Node_Mesh, this->Node_Mesh_Current_Time); // get the ouptut pointer to paraview vtkUnstructuredGrid *Output_Node_Mesh = vtkUnstructuredGrid::SafeDownCast(Node_Mesh->Get(vtkDataObject::DATA_OBJECT())); Output_Node_Mesh->ShallowCopy(UGrid_Current_Node_Mesh); return 1; } When I run this code, The Piece_no and Number_of_Pieces both remain 0. Sumeet On Mon, Aug 15, 2016 at 3:58 PM, Moreland, Kenneth > wrote: During the RequestData pass of the pipeline, you should be able to get the keys vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER() and vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES() from the output information object that comes from downstream. This will tell you how many pieces the pipeline expects and which piece is expected to be read. Generally the number of pieces requested will not match exactly the number of files that you have. This means you will have to adjust by either reading more than 1 file at a time or sometimes reading nothing and returning an empty object. -Ken From: sumeet kumar [mailto:sumeet.kumar507 at gmail.com] Sent: Monday, August 15, 2016 3:52 PM To: Moreland, Kenneth > Cc: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Reading multiple files in parallel Thanks Kenneth, for you help. I get the vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), set 1 part. But, what to do next. How can i get the piece no, so that i can update the data for it. vtkmXMLPUnstructuredGridDataReader is not doing me a great help. Sumeet On Mon, Aug 15, 2016 at 12:57 PM, Moreland, Kenneth > wrote: I think the key you are looking for is vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), which you want to set to 1 to signify that you can provide multiple pieces. You might want to look at vtkmXMLPUnstructuredGridDataReader for an example. If I remember correctly, this has recently been changed in VTK. It used to be that you would give the number of pieces you supported, but that functionality was not useful in practice and consequently readers reported that they could produce any number of pieces in order to be useful. Thus, the behavior was change to allow readers simply to report whether or not they support multiple pieces. Berk can probably provide more information. -Ken From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of sumeet kumar Sent: Monday, August 15, 2016 12:58 PM To: ParaView Developers > Subject: [EXTERNAL] [Paraview-developers] Reading multiple files in parallel Hello all, I have a number of files which contains information about pieces of unstructured mesh. For example :- t_2.h5.01.feioutput t_2.h5.03.feioutput t_2.h5.04.feioutput t_2.h5.05.feioutput t_2.h5.06.feioutput t_2.h5.07.feioutput t_2.h5.08.feioutput t_2.h5.09.feioutput t_2.h5.feioutput My reader can read each file individually but I want to read them all in parallel so that I can visualize the whole model. I looked at the http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the steps for unstructured mesh. When I try to set the number of pieces in Request Information function as this vtkInformation* Node_Mesh = outVec->GetInformationObject(0); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); I get the following error error: 'MAXIMUM_NUMBER_OF_PIECES' is not a member of 'vtkStreamingDemandDrivenPipeline' Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); Also, it would be highly appreciated if anyone could show/(send me link) me to a sample example. Regards -- Error! Filename not specified. Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -- Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -- [http://faculty.engineering.ucdavis.edu/ceetemplate/wp-content/uploads/2013/06/CEE75percent500w.jpg] Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 407 bytes Desc: image001.jpg URL: From sumeet.kumar507 at gmail.com Tue Aug 16 17:07:57 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Tue, 16 Aug 2016 14:07:57 -0700 Subject: [Paraview-developers] Reading multiple files in parallel In-Reply-To: <1CB5ABB4-3C98-4899-ADFF-1B52B585FEF0@sandia.gov> References: <21adba1164ba43539fbec057479b83a9@ES08AMSNLNT.srn.sandia.gov> <1CB5ABB4-3C98-4899-ADFF-1B52B585FEF0@sandia.gov> Message-ID: I compiled ParaView with MPI enabled and as you said and now I can get UPDATE_NUMBER_OF_PIECES() and UPDATE_NUMBER_OF_PIECES() keys. But, as you said in your previous mail that the number of piece requests will not match with the number of files. So, how can I now what is the range of piece requests that will be generated. For example, if I have 8 files and the user runs para-view on 4 processes. The optimal way is to read two files per processes. But my question will how can i know that the user is running on 4 nodes only. Is there any key ??/ for that. Thanks Sumeet On Tue, Aug 16, 2016 at 8:03 AM, Moreland, Kenneth wrote: > Are you running ParaView in MPI parallel mode? If not, it might not set > the number of pieces. > > Also, I don't think you need to set WHOLE_EXTENT. That is for structured > type of data. > > -Ken > > Sent from my iPad so blame autocorrect. > > On Aug 15, 2016, at 5:38 PM, sumeet kumar > wrote: > > Hey Ken, > > I am sorry that I am asking you a lot of stupid questions. But I am stuck > here. I followed what you said, But I don't see the piece number getting > updated. And also when would that stop being updated...etc. Here is my code > > int pvESSI::RequestInformation( vtkInformation *request, > vtkInformationVector **vtkNotUsed(inVec), vtkInformationVector* outVec){ > > this->Initialize(); > > vtkInformation* Node_Mesh = outVec->GetInformationObject(0); > > double Time_range[2]={Time[0],Time[Number_Of_Time_Steps-1]}; > > Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_STEPS(),Time, > this->Number_Of_Time_Steps); > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::TIME_RANGE(),Time_range,2); > > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::WHOLE_EXTENT(),EXTENT,6); > > int num_of_piec = 10; > Node_Mesh->Set(CAN_HANDLE_PIECE_REQUEST(), 1); > > return 1; > } > > int pvESSI::RequestData(vtkInformation *vtkNotUsed(request),vtkInformationVector > **vtkNotUsed(inputVector), vtkInformationVector *outputVector){ > > vtkInformation *Node_Mesh = outputVector->GetInformationObject(0); > // outInfo->Print(std::cout); > > piece_no = Node_Mesh->Get(vtkStreamingDemandDrivenPipeli > ne::UPDATE_PIECE_NUMBER()); > num_of_pieces = Node_Mesh->Get(vtkStreamingDemandDrivenPipeli > ne::UPDATE_NUMBER_OF_PIECES()); > cout << "Piece_No " << piece_no << endl; > cout << "Number_of_Pieces " << piece_no << endl; > > Step_Initializer(Piece_No); // makes the file and variables > ready for that piece > > this->Node_Mesh_Current_Time = Time_Map.find( Node_Mesh->Get( > vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()))->second; > > if (!Whether_Node_Mesh_Build){ > this->Get_Node_Mesh(UGrid_Node_Mesh); > UGrid_Current_Node_Mesh->ShallowCopy(UGrid_Node_Mesh); > } > > Build_Node_Attributes(UGrid_Current_Node_Mesh, > this->Node_Mesh_Current_Time ); > Build_Stress_Field_At_Nodes(UGrid_Current_Node_Mesh, > this->Node_Mesh_Current_Time); > > // get the ouptut pointer to paraview > vtkUnstructuredGrid *Output_Node_Mesh = vtkUnstructuredGrid:: > SafeDownCast(Node_Mesh->Get(vtkDataObject::DATA_OBJECT())); > > Output_Node_Mesh->ShallowCopy(UGrid_Current_Node_Mesh); > return 1; > } > > When I run this code, The * Piece_no* and *Number_of_Pieces* both remain > 0. > > > Sumeet > > On Mon, Aug 15, 2016 at 3:58 PM, Moreland, Kenneth > wrote: > >> During the RequestData pass of the pipeline, you should be able to get >> the keys vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER() and >> vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES() from the >> output information object that comes from downstream. This will tell you >> how many pieces the pipeline expects and which piece is expected to be read. >> >> >> >> Generally the number of pieces requested will not match exactly the >> number of files that you have. This means you will have to adjust by either >> reading more than 1 file at a time or sometimes reading nothing and >> returning an empty object. >> >> >> >> -Ken >> >> >> >> *From:* sumeet kumar [mailto:sumeet.kumar507 at gmail.com] >> *Sent:* Monday, August 15, 2016 3:52 PM >> *To:* Moreland, Kenneth >> *Cc:* ParaView Developers >> *Subject:* [EXTERNAL] Re: [Paraview-developers] Reading multiple files >> in parallel >> >> >> >> Thanks Kenneth, for you help. >> >> I get the vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), set 1 part. >> >> But, what to do next. >> >> How can i get the piece no, so that i can update the data for it. >> >> vtkmXMLPUnstructuredGridDataReader is not doing me a great help. >> >> Sumeet >> >> >> >> On Mon, Aug 15, 2016 at 12:57 PM, Moreland, Kenneth >> wrote: >> >> I think the key you are looking for is vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), >> which you want to set to 1 to signify that you can provide multiple pieces. >> You might want to look at vtkmXMLPUnstructuredGridDataReader for an >> example. >> >> >> >> If I remember correctly, this has recently been changed in VTK. It used >> to be that you would give the number of pieces you supported, but that >> functionality was not useful in practice and consequently readers reported >> that they could produce any number of pieces in order to be useful. Thus, >> the behavior was change to allow readers simply to report whether or not >> they support multiple pieces. Berk can probably provide more information. >> >> >> >> -Ken >> >> >> >> *From:* Paraview-developers [mailto:paraview-developers-bo >> unces at paraview.org] *On Behalf Of *sumeet kumar >> *Sent:* Monday, August 15, 2016 12:58 PM >> *To:* ParaView Developers >> *Subject:* [EXTERNAL] [Paraview-developers] Reading multiple files in >> parallel >> >> >> >> Hello all, >> >> I have a number of files which contains information about pieces of >> unstructured mesh. For example :- >> >> t_2.h5.01.feioutput >> t_2.h5.03.feioutput >> t_2.h5.04.feioutput >> t_2.h5.05.feioutput >> t_2.h5.06.feioutput >> t_2.h5.07.feioutput >> t_2.h5.08.feioutput >> t_2.h5.09.feioutput >> t_2.h5.feioutput >> >> My reader can read each file individually but I want to read them all in >> parallel so that I can visualize the whole model. I looked at the >> http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the >> steps for unstructured mesh. >> >> When I try to set the number of pieces in Request Information function as >> this >> >> vtkInformation* Node_Mesh = outVec->GetInformationObject(0); >> Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), >> 10); >> >> >> >> I get the following error >> >> error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of >> ?vtkStreamingDemandDrivenPipeline? >> Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), >> 10); >> >> >> >> Also, it would be highly appreciated if anyone could show/(send me link) >> me to a sample example. >> >> Regards >> >> -- >> >> *Error! Filename not specified.* >> >> Sumeet Kumar Sinha >> >> Graduate Student >> >> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >> >> Website : http://www.sumeetksinha.com/ >> >> >> >> >> -- >> >> >> >> Sumeet Kumar Sinha >> >> Graduate Student >> >> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >> >> Website : http://www.sumeetksinha.com/ >> > > > > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetksinha.com/ > > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Tue Aug 16 17:28:44 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 16 Aug 2016 21:28:44 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Reading multiple files in parallel In-Reply-To: References: <21adba1164ba43539fbec057479b83a9@ES08AMSNLNT.srn.sandia.gov> <1CB5ABB4-3C98-4899-ADFF-1B52B585FEF0@sandia.gov> Message-ID: <8cfaf89310314c8695b2daaa7380998b@ES08AMSNLNT.srn.sandia.gov> ParaView will set the UPDATE_NUMBER_OF_PIECES to the number of processes and UPDATE_PIECE_NUMBER to the rank. -Ken From: sumeet kumar [mailto:sumeet.kumar507 at gmail.com] Sent: Tuesday, August 16, 2016 3:08 PM To: Moreland, Kenneth ; Sumeet Kumar Sinha Cc: ParaView Developers Subject: [EXTERNAL] Re: [Paraview-developers] Reading multiple files in parallel I compiled ParaView with MPI enabled and as you said and now I can get UPDATE_NUMBER_OF_PIECES() and UPDATE_NUMBER_OF_PIECES() keys. But, as you said in your previous mail that the number of piece requests will not match with the number of files. So, how can I now what is the range of piece requests that will be generated. For example, if I have 8 files and the user runs para-view on 4 processes. The optimal way is to read two files per processes. But my question will how can i know that the user is running on 4 nodes only. Is there any key ??/ for that. Thanks Sumeet On Tue, Aug 16, 2016 at 8:03 AM, Moreland, Kenneth > wrote: Are you running ParaView in MPI parallel mode? If not, it might not set the number of pieces. Also, I don't think you need to set WHOLE_EXTENT. That is for structured type of data. -Ken Sent from my iPad so blame autocorrect. On Aug 15, 2016, at 5:38 PM, sumeet kumar > wrote: Hey Ken, I am sorry that I am asking you a lot of stupid questions. But I am stuck here. I followed what you said, But I don't see the piece number getting updated. And also when would that stop being updated...etc. Here is my code int pvESSI::RequestInformation( vtkInformation *request, vtkInformationVector **vtkNotUsed(inVec), vtkInformationVector* outVec){ this->Initialize(); vtkInformation* Node_Mesh = outVec->GetInformationObject(0); double Time_range[2]={Time[0],Time[Number_Of_Time_Steps-1]}; Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_STEPS(),Time, this->Number_Of_Time_Steps); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_RANGE(),Time_range,2); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(),EXTENT,6); int num_of_piec = 10; Node_Mesh->Set(CAN_HANDLE_PIECE_REQUEST(), 1); return 1; } int pvESSI::RequestData(vtkInformation *vtkNotUsed(request),vtkInformationVector **vtkNotUsed(inputVector), vtkInformationVector *outputVector){ vtkInformation *Node_Mesh = outputVector->GetInformationObject(0); // outInfo->Print(std::cout); piece_no = Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER()); num_of_pieces = Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES()); cout << "Piece_No " << piece_no << endl; cout << "Number_of_Pieces " << piece_no << endl; Step_Initializer(Piece_No); // makes the file and variables ready for that piece this->Node_Mesh_Current_Time = Time_Map.find( Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()))->second; if (!Whether_Node_Mesh_Build){ this->Get_Node_Mesh(UGrid_Node_Mesh); UGrid_Current_Node_Mesh->ShallowCopy(UGrid_Node_Mesh); } Build_Node_Attributes(UGrid_Current_Node_Mesh, this->Node_Mesh_Current_Time ); Build_Stress_Field_At_Nodes(UGrid_Current_Node_Mesh, this->Node_Mesh_Current_Time); // get the ouptut pointer to paraview vtkUnstructuredGrid *Output_Node_Mesh = vtkUnstructuredGrid::SafeDownCast(Node_Mesh->Get(vtkDataObject::DATA_OBJECT())); Output_Node_Mesh->ShallowCopy(UGrid_Current_Node_Mesh); return 1; } When I run this code, The Piece_no and Number_of_Pieces both remain 0. Sumeet On Mon, Aug 15, 2016 at 3:58 PM, Moreland, Kenneth > wrote: During the RequestData pass of the pipeline, you should be able to get the keys vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER() and vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES() from the output information object that comes from downstream. This will tell you how many pieces the pipeline expects and which piece is expected to be read. Generally the number of pieces requested will not match exactly the number of files that you have. This means you will have to adjust by either reading more than 1 file at a time or sometimes reading nothing and returning an empty object. -Ken From: sumeet kumar [mailto:sumeet.kumar507 at gmail.com] Sent: Monday, August 15, 2016 3:52 PM To: Moreland, Kenneth > Cc: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Reading multiple files in parallel Thanks Kenneth, for you help. I get the vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), set 1 part. But, what to do next. How can i get the piece no, so that i can update the data for it. vtkmXMLPUnstructuredGridDataReader is not doing me a great help. Sumeet On Mon, Aug 15, 2016 at 12:57 PM, Moreland, Kenneth > wrote: I think the key you are looking for is vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), which you want to set to 1 to signify that you can provide multiple pieces. You might want to look at vtkmXMLPUnstructuredGridDataReader for an example. If I remember correctly, this has recently been changed in VTK. It used to be that you would give the number of pieces you supported, but that functionality was not useful in practice and consequently readers reported that they could produce any number of pieces in order to be useful. Thus, the behavior was change to allow readers simply to report whether or not they support multiple pieces. Berk can probably provide more information. -Ken From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of sumeet kumar Sent: Monday, August 15, 2016 12:58 PM To: ParaView Developers > Subject: [EXTERNAL] [Paraview-developers] Reading multiple files in parallel Hello all, I have a number of files which contains information about pieces of unstructured mesh. For example :- t_2.h5.01.feioutput t_2.h5.03.feioutput t_2.h5.04.feioutput t_2.h5.05.feioutput t_2.h5.06.feioutput t_2.h5.07.feioutput t_2.h5.08.feioutput t_2.h5.09.feioutput t_2.h5.feioutput My reader can read each file individually but I want to read them all in parallel so that I can visualize the whole model. I looked at the http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the steps for unstructured mesh. When I try to set the number of pieces in Request Information function as this vtkInformation* Node_Mesh = outVec->GetInformationObject(0); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); I get the following error error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of ?vtkStreamingDemandDrivenPipeline? Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); Also, it would be highly appreciated if anyone could show/(send me link) me to a sample example. Regards -- Error! Filename not specified. Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -- Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -- [Image removed by sender.] Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -- [Image removed by sender.] Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 407 bytes Desc: image001.jpg URL: From sumeet.kumar507 at gmail.com Tue Aug 16 18:10:42 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Tue, 16 Aug 2016 15:10:42 -0700 Subject: [Paraview-developers] [EXTERNAL] Re: Reading multiple files in parallel In-Reply-To: <8cfaf89310314c8695b2daaa7380998b@ES08AMSNLNT.srn.sandia.gov> References: <21adba1164ba43539fbec057479b83a9@ES08AMSNLNT.srn.sandia.gov> <1CB5ABB4-3C98-4899-ADFF-1B52B585FEF0@sandia.gov> <8cfaf89310314c8695b2daaa7380998b@ES08AMSNLNT.srn.sandia.gov> Message-ID: Thanks Kenneth, I can get the Number_Of_Processes from the UPDATE_NUMBER_OF_PIECES key. I can read more than one file per request in ParaView on separate VTKDATA_OBJECT (let say array). I searched on Internet, But, couldn't find how to send an array of VTKDATA_OBJECTS to a single output port. Currently , I do this vtkInformation *Node_Mesh = outputVector->GetInformationObject(0); ..... this->Get_Node_Mesh(UGrid_Node_Mesh); UGrid_Current_Node_Mesh->ShallowCopy(UGrid_Node_Mesh); ...... vtkUnstructuredGrid *Output_Node_Mesh = vtkUnstructuredGrid::SafeDownCast(Node_Mesh->Get(vtkDataObject::DATA_OBJECT())); Output_Node_Mesh->ShallowCopy(UGrid_Current_Node_Mesh); is there any way I can send separate mesh ( VTKDATA_OBJECTS) at once in paraview on the same output port. Thanks Sumeet On Tue, Aug 16, 2016 at 2:28 PM, Moreland, Kenneth wrote: > ParaView will set the UPDATE_NUMBER_OF_PIECES to the number of processes > and UPDATE_PIECE_NUMBER to the rank. > > > > -Ken > > > > *From:* sumeet kumar [mailto:sumeet.kumar507 at gmail.com] > *Sent:* Tuesday, August 16, 2016 3:08 PM > *To:* Moreland, Kenneth ; Sumeet Kumar Sinha < > skssinha at ucdavis.edu> > > *Cc:* ParaView Developers > *Subject:* [EXTERNAL] Re: [Paraview-developers] Reading multiple files in > parallel > > > > I compiled ParaView with MPI enabled and as you said and now I can get > UPDATE_NUMBER_OF_PIECES() and UPDATE_NUMBER_OF_PIECES() keys. > > But, as you said in your previous mail that the number of piece requests > will not match with the number of files. So, how can I now what is the > range of piece requests that will be generated. > > For example, if I have 8 files and the user runs para-view on 4 > processes. The optimal way is to read two files per processes. > > But my question will how can i know that the user is running on 4 nodes > only. Is there any key ??/ for that. > > Thanks > > Sumeet > > > > > > On Tue, Aug 16, 2016 at 8:03 AM, Moreland, Kenneth > wrote: > > Are you running ParaView in MPI parallel mode? If not, it might not set > the number of pieces. > > > > Also, I don't think you need to set WHOLE_EXTENT. That is for structured > type of data. > > > > -Ken > > > > Sent from my iPad so blame autocorrect. > > > On Aug 15, 2016, at 5:38 PM, sumeet kumar > wrote: > > Hey Ken, > > I am sorry that I am asking you a lot of stupid questions. But I am stuck > here. I followed what you said, But I don't see the piece number getting > updated. And also when would that stop being updated...etc. Here is my code > > int pvESSI::RequestInformation( vtkInformation *request, > vtkInformationVector **vtkNotUsed(inVec), vtkInformationVector* outVec){ > > this->Initialize(); > > vtkInformation* Node_Mesh = outVec->GetInformationObject(0); > > double Time_range[2]={Time[0],Time[Number_Of_Time_Steps-1]}; > > Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_STEPS(),Time, > this->Number_Of_Time_Steps); > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::TIME_RANGE(),Time_range,2); > > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::WHOLE_EXTENT(),EXTENT,6); > > int num_of_piec = 10; > Node_Mesh->Set(CAN_HANDLE_PIECE_REQUEST(), 1); > > return 1; > } > > int pvESSI::RequestData(vtkInformation *vtkNotUsed(request),vtkInformationVector > **vtkNotUsed(inputVector), vtkInformationVector *outputVector){ > > vtkInformation *Node_Mesh = outputVector->GetInformationObject(0); > // outInfo->Print(std::cout); > > piece_no = Node_Mesh->Get(vtkStreamingDemandDrivenPipeli > ne::UPDATE_PIECE_NUMBER()); > num_of_pieces = Node_Mesh->Get(vtkStreamingDemandDrivenPipeli > ne::UPDATE_NUMBER_OF_PIECES()); > cout << "Piece_No " << piece_no << endl; > cout << "Number_of_Pieces " << piece_no << endl; > > Step_Initializer(Piece_No); // makes the file and variables > ready for that piece > > this->Node_Mesh_Current_Time = Time_Map.find( Node_Mesh->Get( > vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()))->second; > > if (!Whether_Node_Mesh_Build){ > this->Get_Node_Mesh(UGrid_Node_Mesh); > UGrid_Current_Node_Mesh->ShallowCopy(UGrid_Node_Mesh); > } > > Build_Node_Attributes(UGrid_Current_Node_Mesh, > this->Node_Mesh_Current_Time ); > Build_Stress_Field_At_Nodes(UGrid_Current_Node_Mesh, > this->Node_Mesh_Current_Time); > > // get the ouptut pointer to paraview > vtkUnstructuredGrid *Output_Node_Mesh = vtkUnstructuredGrid:: > SafeDownCast(Node_Mesh->Get(vtkDataObject::DATA_OBJECT())); > > Output_Node_Mesh->ShallowCopy(UGrid_Current_Node_Mesh); > return 1; > } > > When I run this code, The *Piece_no* and *Number_of_Pieces* both remain 0. > > Sumeet > > > > On Mon, Aug 15, 2016 at 3:58 PM, Moreland, Kenneth > wrote: > > During the RequestData pass of the pipeline, you should be able to get the > keys vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER() and > vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES() from the > output information object that comes from downstream. This will tell you > how many pieces the pipeline expects and which piece is expected to be read. > > > > Generally the number of pieces requested will not match exactly the number > of files that you have. This means you will have to adjust by either > reading more than 1 file at a time or sometimes reading nothing and > returning an empty object. > > > > -Ken > > > > *From:* sumeet kumar [mailto:sumeet.kumar507 at gmail.com] > *Sent:* Monday, August 15, 2016 3:52 PM > *To:* Moreland, Kenneth > *Cc:* ParaView Developers > *Subject:* [EXTERNAL] Re: [Paraview-developers] Reading multiple files in > parallel > > > > Thanks Kenneth, for you help. > > I get the vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), set 1 part. > > But, what to do next. > > How can i get the piece no, so that i can update the data for it. > > vtkmXMLPUnstructuredGridDataReader is not doing me a great help. > > Sumeet > > > > On Mon, Aug 15, 2016 at 12:57 PM, Moreland, Kenneth > wrote: > > I think the key you are looking for is vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), > which you want to set to 1 to signify that you can provide multiple pieces. > You might want to look at vtkmXMLPUnstructuredGridDataReader for an > example. > > > > If I remember correctly, this has recently been changed in VTK. It used to > be that you would give the number of pieces you supported, but that > functionality was not useful in practice and consequently readers reported > that they could produce any number of pieces in order to be useful. Thus, > the behavior was change to allow readers simply to report whether or not > they support multiple pieces. Berk can probably provide more information. > > > > -Ken > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] *On Behalf Of *sumeet kumar > *Sent:* Monday, August 15, 2016 12:58 PM > *To:* ParaView Developers > *Subject:* [EXTERNAL] [Paraview-developers] Reading multiple files in > parallel > > > > Hello all, > > I have a number of files which contains information about pieces of > unstructured mesh. For example :- > > t_2.h5.01.feioutput > t_2.h5.03.feioutput > t_2.h5.04.feioutput > t_2.h5.05.feioutput > t_2.h5.06.feioutput > t_2.h5.07.feioutput > t_2.h5.08.feioutput > t_2.h5.09.feioutput > t_2.h5.feioutput > > My reader can read each file individually but I want to read them all in > parallel so that I can visualize the whole model. I looked at the > http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the > steps for unstructured mesh. > > When I try to set the number of pieces in Request Information function as > this > > vtkInformation* Node_Mesh = outVec->GetInformationObject(0); > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::MAXIMUM_NUMBER_OF_PIECES(), 10); > > > > I get the following error > > error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of ? > vtkStreamingDemandDrivenPipeline? > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::MAXIMUM_NUMBER_OF_PIECES(), 10); > > > > Also, it would be highly appreciated if anyone could show/(send me link) > me to a sample example. > > Regards > > -- > > *Error! Filename not specified.* > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > > > > > -- > > > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > > > > > -- > > [image: Image removed by sender.] > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > > > > > -- > > [image: Image removed by sender.] > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 407 bytes Desc: not available URL: From kmorel at sandia.gov Tue Aug 16 19:22:30 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 16 Aug 2016 23:22:30 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Reading multiple files in parallel In-Reply-To: References: <21adba1164ba43539fbec057479b83a9@ES08AMSNLNT.srn.sandia.gov> <1CB5ABB4-3C98-4899-ADFF-1B52B585FEF0@sandia.gov> <8cfaf89310314c8695b2daaa7380998b@ES08AMSNLNT.srn.sandia.gov> Message-ID: <787bd13be4c3446c8625f6b0d16ebbfe@ES08AMSNLNT.srn.sandia.gov> The easiest solution is to use vtkAppendFilter to combine the data objects into a single data object. -Ken From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of sumeet kumar Sent: Tuesday, August 16, 2016 4:11 PM To: Moreland, Kenneth Cc: ParaView Developers ; Sumeet Kumar Sinha Subject: Re: [Paraview-developers] [EXTERNAL] Re: Reading multiple files in parallel Thanks Kenneth, I can get the Number_Of_Processes from the UPDATE_NUMBER_OF_PIECES key. I can read more than one file per request in ParaView on separate VTKDATA_OBJECT (let say array). I searched on Internet, But, couldn't find how to send an array of VTKDATA_OBJECTS to a single output port. Currently , I do this vtkInformation *Node_Mesh = outputVector->GetInformationObject(0); ..... this->Get_Node_Mesh(UGrid_Node_Mesh); UGrid_Current_Node_Mesh->ShallowCopy(UGrid_Node_Mesh); ...... vtkUnstructuredGrid *Output_Node_Mesh = vtkUnstructuredGrid::SafeDownCast(Node_Mesh->Get(vtkDataObject::DATA_OBJECT())); Output_Node_Mesh->ShallowCopy(UGrid_Current_Node_Mesh); is there any way I can send separate mesh ( VTKDATA_OBJECTS) at once in paraview on the same output port. Thanks Sumeet On Tue, Aug 16, 2016 at 2:28 PM, Moreland, Kenneth > wrote: ParaView will set the UPDATE_NUMBER_OF_PIECES to the number of processes and UPDATE_PIECE_NUMBER to the rank. -Ken From: sumeet kumar [mailto:sumeet.kumar507 at gmail.com] Sent: Tuesday, August 16, 2016 3:08 PM To: Moreland, Kenneth >; Sumeet Kumar Sinha > Cc: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Reading multiple files in parallel I compiled ParaView with MPI enabled and as you said and now I can get UPDATE_NUMBER_OF_PIECES() and UPDATE_NUMBER_OF_PIECES() keys. But, as you said in your previous mail that the number of piece requests will not match with the number of files. So, how can I now what is the range of piece requests that will be generated. For example, if I have 8 files and the user runs para-view on 4 processes. The optimal way is to read two files per processes. But my question will how can i know that the user is running on 4 nodes only. Is there any key ??/ for that. Thanks Sumeet On Tue, Aug 16, 2016 at 8:03 AM, Moreland, Kenneth > wrote: Are you running ParaView in MPI parallel mode? If not, it might not set the number of pieces. Also, I don't think you need to set WHOLE_EXTENT. That is for structured type of data. -Ken Sent from my iPad so blame autocorrect. On Aug 15, 2016, at 5:38 PM, sumeet kumar > wrote: Hey Ken, I am sorry that I am asking you a lot of stupid questions. But I am stuck here. I followed what you said, But I don't see the piece number getting updated. And also when would that stop being updated...etc. Here is my code int pvESSI::RequestInformation( vtkInformation *request, vtkInformationVector **vtkNotUsed(inVec), vtkInformationVector* outVec){ this->Initialize(); vtkInformation* Node_Mesh = outVec->GetInformationObject(0); double Time_range[2]={Time[0],Time[Number_Of_Time_Steps-1]}; Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_STEPS(),Time, this->Number_Of_Time_Steps); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_RANGE(),Time_range,2); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(),EXTENT,6); int num_of_piec = 10; Node_Mesh->Set(CAN_HANDLE_PIECE_REQUEST(), 1); return 1; } int pvESSI::RequestData(vtkInformation *vtkNotUsed(request),vtkInformationVector **vtkNotUsed(inputVector), vtkInformationVector *outputVector){ vtkInformation *Node_Mesh = outputVector->GetInformationObject(0); // outInfo->Print(std::cout); piece_no = Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER()); num_of_pieces = Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES()); cout << "Piece_No " << piece_no << endl; cout << "Number_of_Pieces " << piece_no << endl; Step_Initializer(Piece_No); // makes the file and variables ready for that piece this->Node_Mesh_Current_Time = Time_Map.find( Node_Mesh->Get(vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()))->second; if (!Whether_Node_Mesh_Build){ this->Get_Node_Mesh(UGrid_Node_Mesh); UGrid_Current_Node_Mesh->ShallowCopy(UGrid_Node_Mesh); } Build_Node_Attributes(UGrid_Current_Node_Mesh, this->Node_Mesh_Current_Time ); Build_Stress_Field_At_Nodes(UGrid_Current_Node_Mesh, this->Node_Mesh_Current_Time); // get the ouptut pointer to paraview vtkUnstructuredGrid *Output_Node_Mesh = vtkUnstructuredGrid::SafeDownCast(Node_Mesh->Get(vtkDataObject::DATA_OBJECT())); Output_Node_Mesh->ShallowCopy(UGrid_Current_Node_Mesh); return 1; } When I run this code, The Piece_no and Number_of_Pieces both remain 0. Sumeet On Mon, Aug 15, 2016 at 3:58 PM, Moreland, Kenneth > wrote: During the RequestData pass of the pipeline, you should be able to get the keys vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER() and vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES() from the output information object that comes from downstream. This will tell you how many pieces the pipeline expects and which piece is expected to be read. Generally the number of pieces requested will not match exactly the number of files that you have. This means you will have to adjust by either reading more than 1 file at a time or sometimes reading nothing and returning an empty object. -Ken From: sumeet kumar [mailto:sumeet.kumar507 at gmail.com] Sent: Monday, August 15, 2016 3:52 PM To: Moreland, Kenneth > Cc: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Reading multiple files in parallel Thanks Kenneth, for you help. I get the vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), set 1 part. But, what to do next. How can i get the piece no, so that i can update the data for it. vtkmXMLPUnstructuredGridDataReader is not doing me a great help. Sumeet On Mon, Aug 15, 2016 at 12:57 PM, Moreland, Kenneth > wrote: I think the key you are looking for is vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), which you want to set to 1 to signify that you can provide multiple pieces. You might want to look at vtkmXMLPUnstructuredGridDataReader for an example. If I remember correctly, this has recently been changed in VTK. It used to be that you would give the number of pieces you supported, but that functionality was not useful in practice and consequently readers reported that they could produce any number of pieces in order to be useful. Thus, the behavior was change to allow readers simply to report whether or not they support multiple pieces. Berk can probably provide more information. -Ken From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of sumeet kumar Sent: Monday, August 15, 2016 12:58 PM To: ParaView Developers > Subject: [EXTERNAL] [Paraview-developers] Reading multiple files in parallel Hello all, I have a number of files which contains information about pieces of unstructured mesh. For example :- t_2.h5.01.feioutput t_2.h5.03.feioutput t_2.h5.04.feioutput t_2.h5.05.feioutput t_2.h5.06.feioutput t_2.h5.07.feioutput t_2.h5.08.feioutput t_2.h5.09.feioutput t_2.h5.feioutput My reader can read each file individually but I want to read them all in parallel so that I can visualize the whole model. I looked at the http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the steps for unstructured mesh. When I try to set the number of pieces in Request Information function as this vtkInformation* Node_Mesh = outVec->GetInformationObject(0); Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); I get the following error error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of ?vtkStreamingDemandDrivenPipeline? Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::MAXIMUM_NUMBER_OF_PIECES(), 10); Also, it would be highly appreciated if anyone could show/(send me link) me to a sample example. Regards -- Error! Filename not specified. Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -- Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -- [Image removed by sender.] Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -- [Image removed by sender.] Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -- [http://faculty.engineering.ucdavis.edu/ceetemplate/wp-content/uploads/2013/06/CEE75percent500w.jpg] Sumeet Kumar Sinha Graduate Student Phone: (+1) 5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 407 bytes Desc: image001.jpg URL: From utkarsh.ayachit at kitware.com Wed Aug 17 11:40:08 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 17 Aug 2016 11:40:08 -0400 Subject: [Paraview-developers] Making paraView dev life easier with custom app In-Reply-To: References: Message-ID: > - helping show data without using ApplyBehavior and pqPropertiesPanel I think the easiest solution for this would be simply make pqApplyBehaviour independent of pqPropertiesPanel. The code may need some restructuring, but essentially, there are two things that are happening here: 1. do tasks on applying a single filter/source 2. do tasks after all sources/fitlers are applied. Adding API on the class to provide access to these two functions in a pqPropertiesPanel independent way may be the way to go. From sumeet.kumar507 at gmail.com Wed Aug 17 13:02:44 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Wed, 17 Aug 2016 10:02:44 -0700 Subject: [Paraview-developers] [EXTERNAL] Re: Reading multiple files in parallel In-Reply-To: <787bd13be4c3446c8625f6b0d16ebbfe@ES08AMSNLNT.srn.sandia.gov> References: <21adba1164ba43539fbec057479b83a9@ES08AMSNLNT.srn.sandia.gov> <1CB5ABB4-3C98-4899-ADFF-1B52B585FEF0@sandia.gov> <8cfaf89310314c8695b2daaa7380998b@ES08AMSNLNT.srn.sandia.gov> <787bd13be4c3446c8625f6b0d16ebbfe@ES08AMSNLNT.srn.sandia.gov> Message-ID: Thank You a lot Kenneth, It worked finally :) Regards Sumeet On Tue, Aug 16, 2016 at 4:22 PM, Moreland, Kenneth wrote: > The easiest solution is to use vtkAppendFilter to combine the data objects > into a single data object. > > > > -Ken > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] *On Behalf Of *sumeet kumar > *Sent:* Tuesday, August 16, 2016 4:11 PM > *To:* Moreland, Kenneth > *Cc:* ParaView Developers ; Sumeet > Kumar Sinha > *Subject:* Re: [Paraview-developers] [EXTERNAL] Re: Reading multiple > files in parallel > > > > Thanks Kenneth, > > I can get the Number_Of_Processes from the UPDATE_NUMBER_OF_PIECES key. > > I can read more than one file per request in ParaView on separate > VTKDATA_OBJECT (let say array). > > I searched on Internet, But, couldn't find how to send an array of > VTKDATA_OBJECTS to a single output port. > > Currently , I do this > > vtkInformation *Node_Mesh = outputVector->GetInformationObject(0); > > ..... > > > this->Get_Node_Mesh(UGrid_Node_Mesh); > UGrid_Current_Node_Mesh->ShallowCopy(UGrid_Node_Mesh); > > > ...... > > > vtkUnstructuredGrid *Output_Node_Mesh = vtkUnstructuredGrid:: > SafeDownCast(Node_Mesh->Get(vtkDataObject::DATA_OBJECT())); > > Output_Node_Mesh->ShallowCopy(UGrid_Current_Node_Mesh); > > is there any way I can send separate mesh ( VTKDATA_OBJECTS) at once in > paraview on the same output port. > > Thanks > > Sumeet > > > > > > On Tue, Aug 16, 2016 at 2:28 PM, Moreland, Kenneth > wrote: > > ParaView will set the UPDATE_NUMBER_OF_PIECES to the number of processes > and UPDATE_PIECE_NUMBER to the rank. > > > > -Ken > > > > *From:* sumeet kumar [mailto:sumeet.kumar507 at gmail.com] > *Sent:* Tuesday, August 16, 2016 3:08 PM > *To:* Moreland, Kenneth ; Sumeet Kumar Sinha < > skssinha at ucdavis.edu> > > > *Cc:* ParaView Developers > *Subject:* [EXTERNAL] Re: [Paraview-developers] Reading multiple files in > parallel > > > > I compiled ParaView with MPI enabled and as you said and now I can get > UPDATE_NUMBER_OF_PIECES() and UPDATE_NUMBER_OF_PIECES() keys. > > But, as you said in your previous mail that the number of piece requests > will not match with the number of files. So, how can I now what is the > range of piece requests that will be generated. > > For example, if I have 8 files and the user runs para-view on 4 > processes. The optimal way is to read two files per processes. > > But my question will how can i know that the user is running on 4 nodes > only. Is there any key ??/ for that. > > Thanks > > Sumeet > > > > > > On Tue, Aug 16, 2016 at 8:03 AM, Moreland, Kenneth > wrote: > > Are you running ParaView in MPI parallel mode? If not, it might not set > the number of pieces. > > > > Also, I don't think you need to set WHOLE_EXTENT. That is for structured > type of data. > > > > -Ken > > > > Sent from my iPad so blame autocorrect. > > > On Aug 15, 2016, at 5:38 PM, sumeet kumar > wrote: > > Hey Ken, > > I am sorry that I am asking you a lot of stupid questions. But I am stuck > here. I followed what you said, But I don't see the piece number getting > updated. And also when would that stop being updated...etc. Here is my code > > int pvESSI::RequestInformation( vtkInformation *request, > vtkInformationVector **vtkNotUsed(inVec), vtkInformationVector* outVec){ > > this->Initialize(); > > vtkInformation* Node_Mesh = outVec->GetInformationObject(0); > > double Time_range[2]={Time[0],Time[Number_Of_Time_Steps-1]}; > > Node_Mesh->Set(vtkStreamingDemandDrivenPipeline::TIME_STEPS(),Time, > this->Number_Of_Time_Steps); > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::TIME_RANGE(),Time_range,2); > > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::WHOLE_EXTENT(),EXTENT,6); > > int num_of_piec = 10; > Node_Mesh->Set(CAN_HANDLE_PIECE_REQUEST(), 1); > > return 1; > } > > int pvESSI::RequestData(vtkInformation *vtkNotUsed(request),vtkInformationVector > **vtkNotUsed(inputVector), vtkInformationVector *outputVector){ > > vtkInformation *Node_Mesh = outputVector->GetInformationObject(0); > // outInfo->Print(std::cout); > > piece_no = Node_Mesh->Get(vtkStreamingDemandDrivenPipeli > ne::UPDATE_PIECE_NUMBER()); > num_of_pieces = Node_Mesh->Get(vtkStreamingDemandDrivenPipeli > ne::UPDATE_NUMBER_OF_PIECES()); > cout << "Piece_No " << piece_no << endl; > cout << "Number_of_Pieces " << piece_no << endl; > > Step_Initializer(Piece_No); // makes the file and variables > ready for that piece > > this->Node_Mesh_Current_Time = Time_Map.find( Node_Mesh->Get( > vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()))->second; > > if (!Whether_Node_Mesh_Build){ > this->Get_Node_Mesh(UGrid_Node_Mesh); > UGrid_Current_Node_Mesh->ShallowCopy(UGrid_Node_Mesh); > } > > Build_Node_Attributes(UGrid_Current_Node_Mesh, > this->Node_Mesh_Current_Time ); > Build_Stress_Field_At_Nodes(UGrid_Current_Node_Mesh, > this->Node_Mesh_Current_Time); > > // get the ouptut pointer to paraview > vtkUnstructuredGrid *Output_Node_Mesh = vtkUnstructuredGrid:: > SafeDownCast(Node_Mesh->Get(vtkDataObject::DATA_OBJECT())); > > Output_Node_Mesh->ShallowCopy(UGrid_Current_Node_Mesh); > return 1; > } > > When I run this code, The *Piece_no* and *Number_of_Pieces* both remain 0. > > Sumeet > > > > On Mon, Aug 15, 2016 at 3:58 PM, Moreland, Kenneth > wrote: > > During the RequestData pass of the pipeline, you should be able to get the > keys vtkStreamingDemandDrivenPipeline::UPDATE_PIECE_NUMBER() and > vtkStreamingDemandDrivenPipeline::UPDATE_NUMBER_OF_PIECES() from the > output information object that comes from downstream. This will tell you > how many pieces the pipeline expects and which piece is expected to be read. > > > > Generally the number of pieces requested will not match exactly the number > of files that you have. This means you will have to adjust by either > reading more than 1 file at a time or sometimes reading nothing and > returning an empty object. > > > > -Ken > > > > *From:* sumeet kumar [mailto:sumeet.kumar507 at gmail.com] > *Sent:* Monday, August 15, 2016 3:52 PM > *To:* Moreland, Kenneth > *Cc:* ParaView Developers > *Subject:* [EXTERNAL] Re: [Paraview-developers] Reading multiple files in > parallel > > > > Thanks Kenneth, for you help. > > I get the vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), set 1 part. > > But, what to do next. > > How can i get the piece no, so that i can update the data for it. > > vtkmXMLPUnstructuredGridDataReader is not doing me a great help. > > Sumeet > > > > On Mon, Aug 15, 2016 at 12:57 PM, Moreland, Kenneth > wrote: > > I think the key you are looking for is vtkAlgorithm::CAN_HANDLE_PIECE_REQUEST(), > which you want to set to 1 to signify that you can provide multiple pieces. > You might want to look at vtkmXMLPUnstructuredGridDataReader for an > example. > > > > If I remember correctly, this has recently been changed in VTK. It used to > be that you would give the number of pieces you supported, but that > functionality was not useful in practice and consequently readers reported > that they could produce any number of pieces in order to be useful. Thus, > the behavior was change to allow readers simply to report whether or not > they support multiple pieces. Berk can probably provide more information. > > > > -Ken > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] *On Behalf Of *sumeet kumar > *Sent:* Monday, August 15, 2016 12:58 PM > *To:* ParaView Developers > *Subject:* [EXTERNAL] [Paraview-developers] Reading multiple files in > parallel > > > > Hello all, > > I have a number of files which contains information about pieces of > unstructured mesh. For example :- > > t_2.h5.01.feioutput > t_2.h5.03.feioutput > t_2.h5.04.feioutput > t_2.h5.05.feioutput > t_2.h5.06.feioutput > t_2.h5.07.feioutput > t_2.h5.08.feioutput > t_2.h5.09.feioutput > t_2.h5.feioutput > > My reader can read each file individually but I want to read them all in > parallel so that I can visualize the whole model. I looked at the > http://www.paraview.org/Wiki/Writing_ParaView_Readers and followed the > steps for unstructured mesh. > > When I try to set the number of pieces in Request Information function as > this > > vtkInformation* Node_Mesh = outVec->GetInformationObject(0); > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::MAXIMUM_NUMBER_OF_PIECES(), 10); > > > > I get the following error > > error: ?MAXIMUM_NUMBER_OF_PIECES? is not a member of ? > vtkStreamingDemandDrivenPipeline? > Node_Mesh->Set(vtkStreamingDemandDrivenPipeli > ne::MAXIMUM_NUMBER_OF_PIECES(), 10); > > > > Also, it would be highly appreciated if anyone could show/(send me link) > me to a sample example. > > Regards > > -- > > *Error! Filename not specified.* > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > > > > > -- > > > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > > > > > -- > > [image: Image removed by sender.] > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > > > > > -- > > [image: Image removed by sender.] > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > > > > > -- > > > > Sumeet Kumar Sinha > > Graduate Student > > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > > Website : http://www.sumeetksinha.com/ > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 407 bytes Desc: not available URL: From Axel.Gerstenberger at Rolls-Royce.com Thu Aug 18 10:29:44 2016 From: Axel.Gerstenberger at Rolls-Royce.com (Gerstenberger, Axel) Date: Thu, 18 Aug 2016 14:29:44 +0000 Subject: [Paraview-developers] addrofthis to give Python the address of a vtkObject Message-ID: <7BA6875C23078842B4E4B47B0D95450D92003207@GBDOXPR-MBX002.Rolls-Royce.Local> Dear developers, When looking through the source code of Paraview (from which we learn all the time for our own code), I found that to get the address of a vtkObject for Python interaction you use code like this: // Set self to point to this char addrofthis[1024]; sprintf(addrofthis, "%p", somepointer); char *aplus = addrofthis; if ((addrofthis[0] == '0') && ((addrofthis[1] == 'x') || addrofthis[1] == 'X')) { aplus += 2; //skip over "0x" } return std::string(aplus); However, sometimes you use aplus for referencing the address (e.g. in vtkPythonAnnotationFilter), but sometimes you use directly addrofthis, but still execute the part to compute aplus. This happens for example in vtkPythonView.cxx, line 142 ff. Since the first version is used a lot, is the second version in vtkPythonView.cxx a bug or does it serve a different purpose? Also, this code snippet appears to be copied to quite a few places, but it is crucial for vtk Python interaction. Maybe a little static method in VTK could be created for that? Thanks, Axel -- Dr. Axel Gerstenberger Aero Methods and Design Systems Engineering (ET-DSE) Rolls-Royce Deutschland Ltd & Co KG Eschenweg 11, Dahlewitz, 15827 Blankenfelde-Mahlow, Germany Tel: +49(0)33708-6-3101 E-Mail: axel.gerstenberger at rolls-royce.com Absence pending: 14.06.2016 Rolls-Royce Deutschland Ltd & Co KG Sitz/Registered Office: Blankenfelde-Mahlow, Deutschland, Registergericht/Court of Register: Amtsgericht Potsdam, HRA 2731 P, Pers?nlich haftende Gesellschafterin/General Partner: Rolls-Royce General Partner Limited, Sitz/Registered Office: Derby, United Kingdom, Register: Registry of Companies Wales and England, 4066556, Directors/Gesch?ftsf?hrer: Paul O?Neil, Alastair McIntosh, Nicole Fehr, Dr. Holger Cartsburg Confidentiality Notice: This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. The data contained in, or attached to, this e-mail, may contain confidential information. If you have received it in error you should notify the sender immediately by reply e-mail, delete the message from your system and contact +44 (0) 3301235850 (Security Operations Centre) if you need assistance. Please do not copy it for any purpose, or disclose its contents to any other person. An e-mail response to this address may be subject to interception or monitoring for operational reasons or for lawful business practices. (c) 2016 Rolls-Royce plc Registered office: 62 Buckingham Gate, London SW1E 6AT Company number: 1003142. Registered in England. From cory.quammen at kitware.com Thu Aug 18 11:59:09 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 18 Aug 2016 11:59:09 -0400 Subject: [Paraview-developers] addrofthis to give Python the address of a vtkObject In-Reply-To: <7BA6875C23078842B4E4B47B0D95450D92003207@GBDOXPR-MBX002.Rolls-Royce.Local> References: <7BA6875C23078842B4E4B47B0D95450D92003207@GBDOXPR-MBX002.Rolls-Royce.Local> Message-ID: HI Axel, > When looking through the source code of Paraview (from which we learn all the time for our own code), I found that to get the address of a vtkObject for Python interaction you use code like this: > > // Set self to point to this > char addrofthis[1024]; > sprintf(addrofthis, "%p", somepointer); > char *aplus = addrofthis; > if ((addrofthis[0] == '0') && ((addrofthis[1] == 'x') || addrofthis[1] == 'X')) > { > aplus += 2; //skip over "0x" > } > return std::string(aplus); > > However, sometimes you use aplus for referencing the address (e.g. in vtkPythonAnnotationFilter), but sometimes you use directly addrofthis, but still execute the part to compute aplus. This happens for example in vtkPythonView.cxx, line 142 ff. > > Since the first version is used a lot, is the second version in vtkPythonView.cxx a bug or does it serve a different purpose? Hmm, you are right, that is different from other examples where the object address is passed to Python, and is not intended. It seems to work, though, or at least it did when I wrote the code. My hunch is that the Python wrapping handles either case of passing "0xffffffff" or "ffffffff" to the constructor to create a Python object from an existing VTK object, but I don't know the Python wrapping facilities well enough to verify that. Perhaps Python wrapping guru David Gobbi can answer affirmatively. > Also, this code snippet appears to be copied to quite a few places, but it is crucial for vtk Python interaction. Maybe a little static method in VTK could be created for that? If the wrappers in fact do not handle both address formats, then yes it would make sense to have a static member function that would do this, probably in vtkPythonUtils. Thanks, Cory > Thanks, > Axel > > > -- > Dr. Axel Gerstenberger > Aero Methods and Design Systems Engineering (ET-DSE) > > Rolls-Royce Deutschland Ltd & Co KG > Eschenweg 11, Dahlewitz, 15827 Blankenfelde-Mahlow, Germany > > Tel: +49(0)33708-6-3101 > E-Mail: axel.gerstenberger at rolls-royce.com > > Absence pending: 14.06.2016 > > Rolls-Royce Deutschland Ltd & Co KG Sitz/Registered Office: Blankenfelde-Mahlow, Deutschland, Registergericht/Court of Register: Amtsgericht Potsdam, HRA 2731 P, Pers?nlich haftende Gesellschafterin/General Partner: Rolls-Royce General Partner Limited, Sitz/Registered Office: Derby, United Kingdom, Register: Registry of Companies Wales and England, 4066556, Directors/Gesch?ftsf?hrer: Paul O?Neil, Alastair McIntosh, Nicole Fehr, Dr. Holger Cartsburg Confidentiality Notice: This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. > The data contained in, or attached to, this e-mail, may contain confidential information. If you have received it in error you should notify the sender immediately by reply e-mail, delete the message from your system and contact +44 (0) 3301235850 (Security Operations Centre) if you need assistance. Please do not copy it for any purpose, or disclose its contents to any other person. > > An e-mail response to this address may be subject to interception or monitoring for operational reasons or for lawful business practices. > > (c) 2016 Rolls-Royce plc > > Registered office: 62 Buckingham Gate, London SW1E 6AT Company number: 1003142. Registered in England. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers -- Cory Quammen R&D Engineer Kitware, Inc. From Axel.Gerstenberger at Rolls-Royce.com Thu Aug 18 12:11:45 2016 From: Axel.Gerstenberger at Rolls-Royce.com (Gerstenberger, Axel) Date: Thu, 18 Aug 2016 16:11:45 +0000 Subject: [Paraview-developers] addrofthis to give Python the address of a vtkObject In-Reply-To: References: <7BA6875C23078842B4E4B47B0D95450D92003207@GBDOXPR-MBX002.Rolls-Royce.Local> Message-ID: <7BA6875C23078842B4E4B47B0D95450D920032E7@GBDOXPR-MBX002.Rolls-Royce.Local> Hi Cory, Just to confirm: We use both variants at various places (maybe copied from different sources) and also for us either version seems to work. But I have some parallel crashes in our python code that I try to understand and I stumbled of this address issue and wanted to make sure that this is not the reason for that. A statement from a wrapper expert (or a static method that encodes the advice) would make us more confident that we use the right version. Regards, Axel -----Original Message----- From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Thursday, August 18, 2016 5:59 PM To: Gerstenberger, Axel Cc: ParaView Developers Subject: Re: [Paraview-developers] addrofthis to give Python the address of a vtkObject HI Axel, > When looking through the source code of Paraview (from which we learn all the time for our own code), I found that to get the address of a vtkObject for Python interaction you use code like this: > > // Set self to point to this > char addrofthis[1024]; > sprintf(addrofthis, "%p", somepointer); > char *aplus = addrofthis; > if ((addrofthis[0] == '0') && ((addrofthis[1] == 'x') || addrofthis[1] == 'X')) > { > aplus += 2; //skip over "0x" > } > return std::string(aplus); > > However, sometimes you use aplus for referencing the address (e.g. in vtkPythonAnnotationFilter), but sometimes you use directly addrofthis, but still execute the part to compute aplus. This happens for example in vtkPythonView.cxx, line 142 ff. > > Since the first version is used a lot, is the second version in vtkPythonView.cxx a bug or does it serve a different purpose? Hmm, you are right, that is different from other examples where the object address is passed to Python, and is not intended. It seems to work, though, or at least it did when I wrote the code. My hunch is that the Python wrapping handles either case of passing "0xffffffff" or "ffffffff" to the constructor to create a Python object from an existing VTK object, but I don't know the Python wrapping facilities well enough to verify that. Perhaps Python wrapping guru David Gobbi can answer affirmatively. > Also, this code snippet appears to be copied to quite a few places, but it is crucial for vtk Python interaction. Maybe a little static method in VTK could be created for that? If the wrappers in fact do not handle both address formats, then yes it would make sense to have a static member function that would do this, probably in vtkPythonUtils. Thanks, Cory > Thanks, > Axel > > > -- > Dr. Axel Gerstenberger > Aero Methods and Design Systems Engineering (ET-DSE) > > Rolls-Royce Deutschland Ltd & Co KG > Eschenweg 11, Dahlewitz, 15827 Blankenfelde-Mahlow, Germany > > Tel: +49(0)33708-6-3101 > E-Mail: axel.gerstenberger at rolls-royce.com > > Absence pending: 14.06.2016 > > Rolls-Royce Deutschland Ltd & Co KG Sitz/Registered Office: Blankenfelde-Mahlow, Deutschland, Registergericht/Court of Register: Amtsgericht Potsdam, HRA 2731 P, Pers?nlich haftende Gesellschafterin/General Partner: Rolls-Royce General Partner Limited, Sitz/Registered Office: Derby, United Kingdom, Register: Registry of Companies Wales and England, 4066556, Directors/Gesch?ftsf?hrer: Paul O?Neil, Alastair McIntosh, Nicole Fehr, Dr. Holger Cartsburg Confidentiality Notice: This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. > The data contained in, or attached to, this e-mail, may contain confidential information. If you have received it in error you should notify the sender immediately by reply e-mail, delete the message from your system and contact +44 (0) 3301235850 (Security Operations Centre) if you need assistance. Please do not copy it for any purpose, or disclose its contents to any other person. > > An e-mail response to this address may be subject to interception or monitoring for operational reasons or for lawful business practices. > > (c) 2016 Rolls-Royce plc > > Registered office: 62 Buckingham Gate, London SW1E 6AT Company number: 1003142. Registered in England. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers -- Cory Quammen R&D Engineer Kitware, Inc. Rolls-Royce Deutschland Ltd & Co KG Sitz/Registered Office: Blankenfelde-Mahlow, Deutschland, Registergericht/Court of Register: Amtsgericht Potsdam, HRA 2731 P, Pers?nlich haftende Gesellschafterin/General Partner: Rolls-Royce General Partner Limited, Sitz/Registered Office: Derby, United Kingdom, Register: Registry of Companies Wales and England, 4066556, Directors/Gesch?ftsf?hrer: Paul O?Neil, Alastair McIntosh, Nicole Fehr, Dr. Holger Cartsburg Confidentiality Notice: This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. The data contained in, or attached to, this e-mail, may contain confidential information. If you have received it in error you should notify the sender immediately by reply e-mail, delete the message from your system and contact +44 (0) 3301235850 (Security Operations Centre) if you need assistance. Please do not copy it for any purpose, or disclose its contents to any other person. An e-mail response to this address may be subject to interception or monitoring for operational reasons or for lawful business practices. (c) 2016 Rolls-Royce plc Registered office: 62 Buckingham Gate, London SW1E 6AT Company number: 1003142. Registered in England. From cory.quammen at kitware.com Thu Aug 18 14:50:37 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 18 Aug 2016 14:50:37 -0400 Subject: [Paraview-developers] addrofthis to give Python the address of a vtkObject In-Reply-To: <7BA6875C23078842B4E4B47B0D95450D920032E7@GBDOXPR-MBX002.Rolls-Royce.Local> References: <7BA6875C23078842B4E4B47B0D95450D92003207@GBDOXPR-MBX002.Rolls-Royce.Local> <7BA6875C23078842B4E4B47B0D95450D920032E7@GBDOXPR-MBX002.Rolls-Royce.Local> Message-ID: Axel, I modified the Python Annotation filter so that it does not cut off the leading "0x", and it worked fine, so I think you can do either. If you couldn't leave the leading "0x", I would expect consistent and spectacular crashes when you do so. HTH, Cory On Thu, Aug 18, 2016 at 12:11 PM, Gerstenberger, Axel wrote: > Hi Cory, > > Just to confirm: We use both variants at various places (maybe copied from different sources) and also for us either version seems to work. > But I have some parallel crashes in our python code that I try to understand and I stumbled of this address issue and wanted to make sure that this is not the reason for that. > > A statement from a wrapper expert (or a static method that encodes the advice) would make us more confident that we use the right version. > > Regards, > Axel > > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: Thursday, August 18, 2016 5:59 PM > To: Gerstenberger, Axel > Cc: ParaView Developers > Subject: Re: [Paraview-developers] addrofthis to give Python the address of a vtkObject > > HI Axel, > >> When looking through the source code of Paraview (from which we learn all the time for our own code), I found that to get the address of a vtkObject for Python interaction you use code like this: >> >> // Set self to point to this >> char addrofthis[1024]; >> sprintf(addrofthis, "%p", somepointer); >> char *aplus = addrofthis; >> if ((addrofthis[0] == '0') && ((addrofthis[1] == 'x') || addrofthis[1] == 'X')) >> { >> aplus += 2; //skip over "0x" >> } >> return std::string(aplus); >> >> However, sometimes you use aplus for referencing the address (e.g. in vtkPythonAnnotationFilter), but sometimes you use directly addrofthis, but still execute the part to compute aplus. This happens for example in vtkPythonView.cxx, line 142 ff. >> >> Since the first version is used a lot, is the second version in vtkPythonView.cxx a bug or does it serve a different purpose? > > Hmm, you are right, that is different from other examples where the > object address is passed to Python, and is not intended. It seems to > work, though, or at least it did when I wrote the code. > > My hunch is that the Python wrapping handles either case of passing > "0xffffffff" or "ffffffff" to the constructor to create a Python > object from an existing VTK object, but I don't know the Python > wrapping facilities well enough to verify that. Perhaps Python > wrapping guru David Gobbi can answer affirmatively. > >> Also, this code snippet appears to be copied to quite a few places, but it is crucial for vtk Python interaction. Maybe a little static method in VTK could be created for that? > > If the wrappers in fact do not handle both address formats, then yes > it would make sense to have a static member function that would do > this, probably in vtkPythonUtils. > > Thanks, > Cory > >> Thanks, >> Axel >> >> >> -- >> Dr. Axel Gerstenberger >> Aero Methods and Design Systems Engineering (ET-DSE) >> >> Rolls-Royce Deutschland Ltd & Co KG >> Eschenweg 11, Dahlewitz, 15827 Blankenfelde-Mahlow, Germany >> >> Tel: +49(0)33708-6-3101 >> E-Mail: axel.gerstenberger at rolls-royce.com >> >> Absence pending: 14.06.2016 >> >> Rolls-Royce Deutschland Ltd & Co KG Sitz/Registered Office: Blankenfelde-Mahlow, Deutschland, Registergericht/Court of Register: Amtsgericht Potsdam, HRA 2731 P, Pers?nlich haftende Gesellschafterin/General Partner: Rolls-Royce General Partner Limited, Sitz/Registered Office: Derby, United Kingdom, Register: Registry of Companies Wales and England, 4066556, Directors/Gesch?ftsf?hrer: Paul O?Neil, Alastair McIntosh, Nicole Fehr, Dr. Holger Cartsburg Confidentiality Notice: This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. >> The data contained in, or attached to, this e-mail, may contain confidential information. If you have received it in error you should notify the sender immediately by reply e-mail, delete the message from your system and contact +44 (0) 3301235850 (Security Operations Centre) if you need assistance. Please do not copy it for any purpose, or disclose its contents to any other person. >> >> An e-mail response to this address may be subject to interception or monitoring for operational reasons or for lawful business practices. >> >> (c) 2016 Rolls-Royce plc >> >> Registered office: 62 Buckingham Gate, London SW1E 6AT Company number: 1003142. Registered in England. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > Rolls-Royce Deutschland Ltd & Co KG Sitz/Registered Office: Blankenfelde-Mahlow, Deutschland, Registergericht/Court of Register: Amtsgericht Potsdam, HRA 2731 P, Pers?nlich haftende Gesellschafterin/General Partner: Rolls-Royce General Partner Limited, Sitz/Registered Office: Derby, United Kingdom, Register: Registry of Companies Wales and England, 4066556, Directors/Gesch?ftsf?hrer: Paul O?Neil, Alastair McIntosh, Nicole Fehr, Dr. Holger Cartsburg Confidentiality Notice: This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. > The data contained in, or attached to, this e-mail, may contain confidential information. If you have received it in error you should notify the sender immediately by reply e-mail, delete the message from your system and contact +44 (0) 3301235850 (Security Operations Centre) if you need assistance. Please do not copy it for any purpose, or disclose its contents to any other person. > > An e-mail response to this address may be subject to interception or monitoring for operational reasons or for lawful business practices. > > (c) 2016 Rolls-Royce plc > > Registered office: 62 Buckingham Gate, London SW1E 6AT Company number: 1003142. Registered in England. -- Cory Quammen R&D Engineer Kitware, Inc. From wascott at sandia.gov Thu Aug 18 20:20:03 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 19 Aug 2016 00:20:03 +0000 Subject: [Paraview-developers] Trello Message-ID: <14332f20ea7b4499ac450908a3259841@ES01AMSNLNT.srn.sandia.gov> Utkarsh, I just added a bug/feature request to the new tracker. As I was trying to figure out what priority to make it, I was really aware of Trello. It helps immensely to be able to prioritize bugs by looking at Trello an trying to balance priorities for the next release. Guess I'm trying to say that I really like this functionality, and hope we don't lose it. Also, until things are automated, should I be adding bugs to Trello also? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Fri Aug 19 00:46:19 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Fri, 19 Aug 2016 10:16:19 +0530 Subject: [Paraview-developers] build problem with paraview superbuild 5.1.2 Message-ID: Hi, I am trying to build paraview using the superbuild (on git cloned version) I enabled the modules : mpi, paraview, python, qt4 and zlib (everything is set to be build on the fly and no system installed libraries will be used) I am using C++11 compiler (GNU 4.9.2) in RHEL6 After I run make following generating it using cmake, I eneded up with errors in the "paraview" module. I tried the same setup for paraview superbuild 5.0.1 and it worked perfectly. Any clue what is missing from my side? Thanks, Chiranjib -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Fri Aug 19 04:05:40 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 19 Aug 2016 10:05:40 +0200 Subject: [Paraview-developers] Glyph3D Representation Move to plugin. Message-ID: Hello I would like to move the Glyph3D Representation to a Plugin. We had several user complain about that, one (new user) can often get mixed up between Glyph3D Representation and Glyph Filter. I already have a MR ready for review, i you would like to manage this differently eg : keeping the representation class in ParaView or using a cmake var instead, please do so. https://gitlab.kitware.com/paraview/paraview/merge_requests/953#note_154612 Regards. Mathieu Westphal -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Aug 19 10:01:46 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 19 Aug 2016 10:01:46 -0400 Subject: [Paraview-developers] Trello In-Reply-To: <14332f20ea7b4499ac450908a3259841@ES01AMSNLNT.srn.sandia.gov> References: <14332f20ea7b4499ac450908a3259841@ES01AMSNLNT.srn.sandia.gov> Message-ID: > I just added a bug/feature request to the new tracker. As I was trying to > figure out what priority to make it, I was really aware of Trello. It helps > immensely to be able to prioritize bugs by looking at Trello an trying to > balance priorities for the next release. Guess I?m trying to say that I > really like this functionality, and hope we don?t lose it. Roger that. BTW, have see this: https://gitlab.kitware.com/paraview/paraview/issues?scope=all&sort=priority&state=opened&utf8=%E2%9C%93&milestone_title=5.2&label-name= You can view issues for a milestone sorted by priority. That'll probably give you a better sorted view for a specific milestone. > Also, until things are automated, should I be adding bugs to Trello also? To avoid confusion, let's not use the private Trello anymore. I will migrate the sorting information from the trello over to Gitlab labels over this weekend. Does that work? Utkarsh From cory.quammen at kitware.com Fri Aug 19 10:16:44 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 19 Aug 2016 10:16:44 -0400 Subject: [Paraview-developers] build problem with paraview superbuild 5.1.2 In-Reply-To: References: Message-ID: Chirangjib, Could you post the errors that you encounter? Thanks, Cory On Fri, Aug 19, 2016 at 12:46 AM, Chiranjib Sur wrote: > Hi, > I am trying to build paraview using the superbuild (on git cloned version) > > I enabled the modules : mpi, paraview, python, qt4 and zlib (everything is > set to be build on the fly and no system installed libraries will be used) > > I am using C++11 compiler (GNU 4.9.2) in RHEL6 > > After I run make following generating it using cmake, I eneded up with > errors in the "paraview" module. > > I tried the same setup for paraview superbuild 5.0.1 and it worked > perfectly. > > > Any clue what is missing from my side? > > Thanks, > Chiranjib > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen R&D Engineer Kitware, Inc. From utkarsh.ayachit at kitware.com Fri Aug 19 14:57:17 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 19 Aug 2016 14:57:17 -0400 Subject: [Paraview-developers] [Paraview] PythonQt plugin build error In-Reply-To: References: Message-ID: Replace it by pqRenderViewBase::widget() [1]. [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqView.html#ae44839f94fd03cd4ef28640366df3f17 On Thu, Aug 18, 2016 at 7:52 PM, ????? ???????? wrote: > Hi, > > I have a problem with PythonQt plugin building: > > > > c:\users\buildsystem\desktop\paraview-build\plugins\pythonqtplugin\pqPluginDecorators.h(129): > error C2039: 'getWidget': is not a member of 'pqRenderViewBase' > > c:\users\buildsystem\desktop\paraview-src\qt\core\pqRenderViewBase.h(43): > note: see declaration of 'pqRenderViewBase' > > > > I guess getWidget method from wrapped_methods.txt, should I remove it? > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From wascott at sandia.gov Fri Aug 19 15:21:05 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 19 Aug 2016 19:21:05 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Trello In-Reply-To: References: <14332f20ea7b4499ac450908a3259841@ES01AMSNLNT.srn.sandia.gov> Message-ID: <4739b195224c47efb7c12293411dd75b@ES01AMSNLNT.srn.sandia.gov> Specific milestones - good enough. Regarding trello, sounds good. Al -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Friday, August 19, 2016 8:02 AM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Trello > I just added a bug/feature request to the new tracker. As I was trying to > figure out what priority to make it, I was really aware of Trello. It > helps immensely to be able to prioritize bugs by looking at Trello an > trying to balance priorities for the next release. Guess I?m trying > to say that I really like this functionality, and hope we don?t lose it. Roger that. BTW, have see this: https://gitlab.kitware.com/paraview/paraview/issues?scope=all&sort=priority&state=opened&utf8=%E2%9C%93&milestone_title=5.2&label-name= You can view issues for a milestone sorted by priority. That'll probably give you a better sorted view for a specific milestone. > Also, until things are automated, should I be adding bugs to Trello also? To avoid confusion, let's not use the private Trello anymore. I will migrate the sorting information from the trello over to Gitlab labels over this weekend. Does that work? Utkarsh From utkarsh.ayachit at kitware.com Sat Aug 20 09:28:42 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 20 Aug 2016 09:28:42 -0400 Subject: [Paraview-developers] Updates to ParaVIew development workflow Message-ID: Folks, Now that we have started using Gitlab for both code review and issue tracking, it's time to review our development workflow. Following discussions with several people involved with ParaView development and release process, we now have a proposal for an updated development workflow. I've updated the docs and created a merge request here: https://gitlab.kitware.com/paraview/paraview/merge_requests/959 Suggestions, comments, revisions are welcome. Thanks, Utkarsh From utkarsh.ayachit at kitware.com Sat Aug 20 11:03:10 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sat, 20 Aug 2016 11:03:10 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Trello In-Reply-To: <4739b195224c47efb7c12293411dd75b@ES01AMSNLNT.srn.sandia.gov> References: <14332f20ea7b4499ac450908a3259841@ES01AMSNLNT.srn.sandia.gov> <4739b195224c47efb7c12293411dd75b@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, I've migrated all states from Trello as labels on Gitlab issues for the open issues. The mapping between the Trello list names and priority labels is as under: Must have ==> priority:required Really should have ==> priority:important Should have ==> priority:nice-to-have Nice-to-have ==> priority:moonshot A full list of issues for the 5.2 milestone can be found using any of the following: 1. https://gitlab.kitware.com/paraview/paraview/milestones/4 2. https://gitlab.kitware.com/paraview/paraview/issues?scope=all&sort=priority&state=opened&utf8=%E2%9C%93&milestone_title=5.2&label-name= I am leaving the Trello board around for reference, but otherwise everyone should treat the board as obsolete and read only. Utkarsh On Fri, Aug 19, 2016 at 3:21 PM, Scott, W Alan wrote: > Specific milestones - good enough. > > Regarding trello, sounds good. > > Al > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, August 19, 2016 8:02 AM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Trello > >> I just added a bug/feature request to the new tracker. As I was trying to >> figure out what priority to make it, I was really aware of Trello. It >> helps immensely to be able to prioritize bugs by looking at Trello an >> trying to balance priorities for the next release. Guess I?m trying >> to say that I really like this functionality, and hope we don?t lose it. > > Roger that. BTW, have see this: > https://gitlab.kitware.com/paraview/paraview/issues?scope=all&sort=priority&state=opened&utf8=%E2%9C%93&milestone_title=5.2&label-name= > > You can view issues for a milestone sorted by priority. That'll probably give you a better sorted view for a specific milestone. > >> Also, until things are automated, should I be adding bugs to Trello also? > > To avoid confusion, let's not use the private Trello anymore. I will migrate the sorting information from the trello over to Gitlab labels over this weekend. Does that work? > > Utkarsh From thomasblome at startmail.com Sun Aug 21 04:10:14 2016 From: thomasblome at startmail.com (thomasblome at startmail.com) Date: Sun, 21 Aug 2016 10:10:14 +0200 Subject: [Paraview-developers] vtkRenderingFreeType error Message-ID: <5d3c970444825d1455d71db7c9921eaa.startmail@www.startmail.com> Hi, I'm trying to build paraview from source. For this I'm using: Windows 10 Visual Studio 2015 CMake 3.6.1 paraview 5.1.2 Qt 5.7 msmpi 7.1 I downloaded the source code of paraview from http://www.paraview.org/download/ and generated the project in CMake. Every time I switch on BUILD_EXAMPLES, I get the following error messages in VS: Error?? ?LNK2001?? ?unresolved external symbol "void __cdecl vtkRenderingFreeType_AutoInit_Construct(void)" (?vtkRenderingFreeType_AutoInit_Construct@@YAXXZ) [C:\Kitware\ParaView-v5.1.0\bin\Examples\All\Plugins\Autostart\Autostart.vcxproj]?? ?ParaViewExamples?? ?C:\Kitware\ParaView-v5.1.0\bin\Autostart_Plugin.obj?? ?1??? Error?? ?LNK2019?? ?unresolved external symbol "void __cdecl vtkRenderingFreeType_AutoInit_Construct(void)" (?vtkRenderingFreeType_AutoInit_Construct@@YAXXZ) referenced in function "public: __cdecl vtkRenderingCore_AutoInit::vtkRenderingCore_AutoInit(void)" (??0vtkRenderingCore_AutoInit@@QEAA at XZ) [C:\Kitware\ParaView-v5.1.0\bin\Examples\All\Plugins\Autostart\Autostart.vcxproj]?? ?ParaViewExamples?? ?C:\Kitware\ParaView-v5.1.0\bin\pqMyApplicationStarterImplementation.obj?? ?1??? I found the same problem already mentioned here: http://public.kitware.com/pipermail/paraview-developers/2015-November/004094.html, so I added the command "target_link_libraries(paraview LINK_PRIVATE vtkRenderingFreeType)" to the CMake file located in C:\Kitware\ParaView-v5.1.2\Applications\ParaView - right after the "build_paraview_client()" macro, but I keep running into the same error. I also tried the build on another system (windows 7, Visual Studio 2010, Qt 4.8.7), but to no avail. By the way, I wonder why the ParaviewExamples project in VS doesn't contain neither source nor header files. Is that project properly generated by CMake? Thanks in advance! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 7F53DEC77F67D0E0.asc Type: application/pgp-keys Size: 3082 bytes Desc: OpenPGP public keys URL: From sur.chiranjib at gmail.com Mon Aug 22 02:39:29 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Mon, 22 Aug 2016 12:09:29 +0530 Subject: [Paraview-developers] build problem with paraview superbuild 5.1.2 In-Reply-To: References: Message-ID: Hi Cory, I could figure out the build error. Once the "Makefile" is is generated, I was trying to build using the multi-core option of make (e.g -j) When I used to build like this ($make -k -j16) the build was NOT successful. However, when I tried without "-j" option ($make -k) I ended up with successful build. If this is the "requirement" to build PV from superbuild, I recommend that the wiki page should contain this small information. Chiranjib On Fri, Aug 19, 2016 at 7:46 PM, Cory Quammen wrote: > Chirangjib, > > Could you post the errors that you encounter? > > Thanks, > Cory > > On Fri, Aug 19, 2016 at 12:46 AM, Chiranjib Sur > wrote: > > Hi, > > I am trying to build paraview using the superbuild (on git cloned > version) > > > > I enabled the modules : mpi, paraview, python, qt4 and zlib (everything > is > > set to be build on the fly and no system installed libraries will be > used) > > > > I am using C++11 compiler (GNU 4.9.2) in RHEL6 > > > > After I run make following generating it using cmake, I eneded up with > > errors in the "paraview" module. > > > > I tried the same setup for paraview superbuild 5.0.1 and it worked > > perfectly. > > > > > > Any clue what is missing from my side? > > > > Thanks, > > Chiranjib > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Mon Aug 22 02:43:02 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Mon, 22 Aug 2016 12:13:02 +0530 Subject: [Paraview-developers] ParaView 5.1.2 binary crash - stack trace attached Message-ID: All, I downloaded the Linux binary from the website and while trying to run the executable, I get a seg fault. Cory suggested me to post the stack trace. Here is the trace attached. Any clue? I am trying to run it in a RHEL6.6 system with qt4.8.6 and python-2.7.9 Thanks, Chiranjib -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- #0 0x0000000000000000 in ?? () #1 0x00002aaaaf7bcfb2 in vtkOpenGLRenderWindow::CreateHardwareOffScreenBuffers(int, int, bool) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingOpenGL2-pv5.1.so.1 #2 0x00002aaaaf7bd37c in vtkOpenGLRenderWindow::CreateHardwareOffScreenWindow(int, int) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingOpenGL2-pv5.1.so.1 #3 0x00002aaaaf84e945 in vtkXOpenGLRenderWindow::CreateOffScreenWindow(int, int) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingOpenGL2-pv5.1.so.1 #4 0x00002aaaaf7bb6b0 in vtkOpenGLRenderWindow::SupportsOpenGL() () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingOpenGL2-pv5.1.so.1 #5 0x00002aaab6c6bb3e in vtkPVDisplayInformation::SupportsOpenGLLocally() () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVClientServerCoreRendering-pv5.1.so.1 #6 0x00002aaab6c6bb84 in vtkPVDisplayInformation::CopyFromObject(vtkObject*) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVClientServerCoreRendering-pv5.1.so.1 #7 0x00002aaaad5fd92b in vtkPVSessionCore::GatherInformationInternal(vtkPVInformation*, unsigned int) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVServerImplementationCore-pv5.1.so.1 #8 0x00002aaaad5fda92 in vtkPVSessionCore::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVServerImplementationCore-pv5.1.so.1 #9 0x00002aaaaab6c4a2 in pqDefaultViewBehavior::onServerCreation(pqServer*) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkpqApplicationComponents-pv5.1.so.1 #10 0x00002aaab490a8ca in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libQtCore.so.4 #11 0x00002aaaab9e8e32 in pqServerManagerModel::serverAdded(pqServer*) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkpqCore-pv5.1.so.1 #12 0x00002aaaab9baa41 in pqServerManagerModel::onConnectionCreated(long long) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkpqCore-pv5.1.so.1 #13 0x00002aaab490a8ca in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libQtCore.so.4 #14 0x00002aaaab9ea022 in pqServerManagerObserver::connectionCreated(long long) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkpqCore-pv5.1.so.1 #15 0x00002aaaab9ea199 in pqServerManagerObserver::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)---Type to continue, or q to quit--- () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkpqCore-pv5.1.so.1 #16 0x00002aaab490a8ca in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libQtCore.so.4 #17 0x00002aaaae084a87 in vtkQtConnection::EmitExecute(vtkObject*, unsigned long, void*, void*, vtkCommand*) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkGUISupportQt-pv5.1.so.1 #18 0x00002aaaae07159c in vtkQtConnection::DoCallback(vtkObject*, unsigned long, void*, void*) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkGUISupportQt-pv5.1.so.1 #19 0x00002aaab4fbe799 in vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkCommonCore-pv5.1.so.1 #20 0x00002aaab5070db0 in vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkCommonCore-pv5.1.so.1 #21 0x00002aaaadbbbab0 in vtkProcessModule::RegisterSession(vtkSession*) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVClientServerCoreCore-pv5.1.so.1 #22 0x00002aaaad3293a3 in vtkSMSession::ConnectToSelf() () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVServerManagerCore-pv5.1.so.1 #23 0x00002aaaab987f40 in pqObjectBuilder::createServer(pqServerResource const&) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkpqCore-pv5.1.so.1 #24 0x00002aaaaab39652 in pqAlwaysConnectedBehavior::serverCheck() () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkpqApplicationComponents-pv5.1.so.1 #25 0x00002aaaaab39788 in pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior(QObject*) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkpqApplicationComponents-pv5.1.so.1 #26 0x00002aaaaab93a78 in pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) () from /home/csur/Utils/ParaView-5.1.2-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkpqApplicationComponents-pv5.1.so.1 #27 0x0000000000409eb4 in ParaViewMainWindow::ParaViewMainWindow() () #28 0x0000000000408306 in pqparaviewInitializer::Initialize(int, char**) () #29 0x0000000000407fda From david.lonie at kitware.com Mon Aug 22 09:38:02 2016 From: david.lonie at kitware.com (David Lonie) Date: Mon, 22 Aug 2016 09:38:02 -0400 Subject: [Paraview-developers] link error building examples on MSVC (was: vtkRenderingFreeType error) Message-ID: (Just updating the subject so the MSVC folks will see this -- the problem is not related to freetype, so I want to make sure the right eyes see it :) ). On Sun, Aug 21, 2016 at 4:10 AM, wrote: > Hi, > > I'm trying to build paraview from source. For this I'm using: > > Windows 10 > Visual Studio 2015 > CMake 3.6.1 > paraview 5.1.2 > Qt 5.7 > msmpi 7.1 > > I downloaded the source code of paraview from > http://www.paraview.org/download/ and generated the project in CMake. > Every time I switch on BUILD_EXAMPLES, I get the following error messages in > VS: > > Error LNK2001 unresolved external symbol "void __cdecl > vtkRenderingFreeType_AutoInit_Construct(void)" > (?vtkRenderingFreeType_AutoInit_Construct@@YAXXZ) > [C:\Kitware\ParaView-v5.1.0\bin\Examples\All\Plugins\Autostart\Autostart.vcxproj] > ParaViewExamples C:\Kitware\ParaView-v5.1.0\bin\Autostart_Plugin.obj 1 > > Error LNK2019 unresolved external symbol "void __cdecl > vtkRenderingFreeType_AutoInit_Construct(void)" > (?vtkRenderingFreeType_AutoInit_Construct@@YAXXZ) referenced in function > "public: __cdecl vtkRenderingCore_AutoInit::vtkRenderingCore_AutoInit(void)" > (??0vtkRenderingCore_AutoInit@@QEAA at XZ) > [C:\Kitware\ParaView-v5.1.0\bin\Examples\All\Plugins\Autostart\Autostart.vcxproj] > ParaViewExamples > C:\Kitware\ParaView-v5.1.0\bin\pqMyApplicationStarterImplementation.obj 1 > > I found the same problem already mentioned here: > http://public.kitware.com/pipermail/paraview-developers/2015-November/004094.html, > so I added the command "target_link_libraries(paraview LINK_PRIVATE > vtkRenderingFreeType)" to the CMake file located in > C:\Kitware\ParaView-v5.1.2\Applications\ParaView - right after the > "build_paraview_client()" macro, but I keep running into the same error. > > I also tried the build on another system (windows 7, Visual Studio 2010, Qt > 4.8.7), but to no avail. > By the way, I wonder why the ParaviewExamples project in VS doesn't contain > neither source nor header files. Is that project properly generated by > CMake? > > Thanks in advance! > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Mon Aug 22 15:14:34 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 22 Aug 2016 15:14:34 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Trello In-Reply-To: References: <14332f20ea7b4499ac450908a3259841@ES01AMSNLNT.srn.sandia.gov> <4739b195224c47efb7c12293411dd75b@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, Cory just brought his to my attention: latest Gitlab release has support for issue boards!: https://www.youtube.com/watch?time_continue=137&v=UWsJ8tkHAa8 This is perfect for us and timing couldn't be better. I'll see if & when can we update our Gitlab instance to the latest version. Utkarsh On Sat, Aug 20, 2016 at 11:03 AM, Utkarsh Ayachit wrote: > Alan, > > I've migrated all states from Trello as labels on Gitlab issues for > the open issues. The mapping between the Trello list names and > priority labels is as under: > > Must have ==> priority:required > Really should have ==> priority:important > Should have ==> priority:nice-to-have > Nice-to-have ==> priority:moonshot > > A full list of issues for the 5.2 milestone can be found using any of > the following: > 1. https://gitlab.kitware.com/paraview/paraview/milestones/4 > 2. https://gitlab.kitware.com/paraview/paraview/issues?scope=all&sort=priority&state=opened&utf8=%E2%9C%93&milestone_title=5.2&label-name= > > I am leaving the Trello board around for reference, but otherwise > everyone should treat the board as obsolete and read only. > > Utkarsh > > On Fri, Aug 19, 2016 at 3:21 PM, Scott, W Alan wrote: >> Specific milestones - good enough. >> >> Regarding trello, sounds good. >> >> Al >> >> -----Original Message----- >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Sent: Friday, August 19, 2016 8:02 AM >> To: Scott, W Alan >> Cc: paraview-developers at paraview.org >> Subject: [EXTERNAL] Re: [Paraview-developers] Trello >> >>> I just added a bug/feature request to the new tracker. As I was trying to >>> figure out what priority to make it, I was really aware of Trello. It >>> helps immensely to be able to prioritize bugs by looking at Trello an >>> trying to balance priorities for the next release. Guess I?m trying >>> to say that I really like this functionality, and hope we don?t lose it. >> >> Roger that. BTW, have see this: >> https://gitlab.kitware.com/paraview/paraview/issues?scope=all&sort=priority&state=opened&utf8=%E2%9C%93&milestone_title=5.2&label-name= >> >> You can view issues for a milestone sorted by priority. That'll probably give you a better sorted view for a specific milestone. >> >>> Also, until things are automated, should I be adding bugs to Trello also? >> >> To avoid confusion, let's not use the private Trello anymore. I will migrate the sorting information from the trello over to Gitlab labels over this weekend. Does that work? >> >> Utkarsh From wascott at sandia.gov Mon Aug 22 19:35:49 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 22 Aug 2016 23:35:49 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Trello In-Reply-To: References: <14332f20ea7b4499ac450908a3259841@ES01AMSNLNT.srn.sandia.gov> <4739b195224c47efb7c12293411dd75b@ES01AMSNLNT.srn.sandia.gov> Message-ID: <03b792b1735c4d13b51bb16c829ab215@ES01AMSNLNT.srn.sandia.gov> Sounds good. Alan -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Saturday, August 20, 2016 9:03 AM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: Re: [EXTERNAL] Re: [Paraview-developers] Trello Alan, I've migrated all states from Trello as labels on Gitlab issues for the open issues. The mapping between the Trello list names and priority labels is as under: Must have ==> priority:required Really should have ==> priority:important Should have ==> priority:nice-to-have Nice-to-have ==> priority:moonshot A full list of issues for the 5.2 milestone can be found using any of the following: 1. https://gitlab.kitware.com/paraview/paraview/milestones/4 2. https://gitlab.kitware.com/paraview/paraview/issues?scope=all&sort=priority&state=opened&utf8=%E2%9C%93&milestone_title=5.2&label-name= I am leaving the Trello board around for reference, but otherwise everyone should treat the board as obsolete and read only. Utkarsh On Fri, Aug 19, 2016 at 3:21 PM, Scott, W Alan wrote: > Specific milestones - good enough. > > Regarding trello, sounds good. > > Al > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, August 19, 2016 8:02 AM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Trello > >> I just added a bug/feature request to the new tracker. As I was trying to >> figure out what priority to make it, I was really aware of Trello. >> It helps immensely to be able to prioritize bugs by looking at Trello >> an trying to balance priorities for the next release. Guess I?m >> trying to say that I really like this functionality, and hope we don?t lose it. > > Roger that. BTW, have see this: > https://gitlab.kitware.com/paraview/paraview/issues?scope=all&sort=pri > ority&state=opened&utf8=%E2%9C%93&milestone_title=5.2&label-name= > > You can view issues for a milestone sorted by priority. That'll probably give you a better sorted view for a specific milestone. > >> Also, until things are automated, should I be adding bugs to Trello also? > > To avoid confusion, let's not use the private Trello anymore. I will migrate the sorting information from the trello over to Gitlab labels over this weekend. Does that work? > > Utkarsh From wascott at sandia.gov Mon Aug 22 20:14:45 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 23 Aug 2016 00:14:45 +0000 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: Message-ID: Being a bit slow here ... I see that we are checking in these docs - great! But, where are they, and how can I see them? Thanks, Alan -----Original Message----- From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Utkarsh Ayachit Sent: Saturday, August 20, 2016 7:29 AM To: ParaView Developers Subject: [EXTERNAL] [Paraview-developers] Updates to ParaVIew development workflow Folks, Now that we have started using Gitlab for both code review and issue tracking, it's time to review our development workflow. Following discussions with several people involved with ParaView development and release process, we now have a proposal for an updated development workflow. I've updated the docs and created a merge request here: https://gitlab.kitware.com/paraview/paraview/merge_requests/959 Suggestions, comments, revisions are welcome. Thanks, Utkarsh _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers From utkarsh.ayachit at kitware.com Tue Aug 23 08:20:58 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 23 Aug 2016 08:20:58 -0400 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: Message-ID: Alan, Once these changes land, these will be accessible from the Gitlab ParaView landing page: https://gitlab.kitware.com/paraview/paraview There's link for CONTRIBUTING.md which should take you to the pages that were updated. Also, when reporting a new issue, Gitlab automatically shows a link to this file as "contributing guidelines" next to the "Submit" button for a new issue. Utkarsh On Mon, Aug 22, 2016 at 8:14 PM, Scott, W Alan wrote: > Being a bit slow here ... I see that we are checking in these docs - great! But, where are they, and how can I see them? > > Thanks, > > Alan > > -----Original Message----- > From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Utkarsh Ayachit > Sent: Saturday, August 20, 2016 7:29 AM > To: ParaView Developers > Subject: [EXTERNAL] [Paraview-developers] Updates to ParaVIew development workflow > > Folks, > > Now that we have started using Gitlab for both code review and issue tracking, it's time to review our development workflow. > > Following discussions with several people involved with ParaView development and release process, we now have a proposal for an updated development workflow. I've updated the docs and created a merge request here: > > https://gitlab.kitware.com/paraview/paraview/merge_requests/959 > > Suggestions, comments, revisions are welcome. > > Thanks, > Utkarsh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers From mathieu.westphal at kitware.com Tue Aug 23 09:42:45 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 23 Aug 2016 15:42:45 +0200 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: Message-ID: I clicked on one of the link in the intruction by mistake and realized most of them are gitlab 404 error, I supose it's a bug ? Mathieu Westphal On Tue, Aug 23, 2016 at 2:20 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Alan, > > Once these changes land, these will be accessible from the Gitlab > ParaView landing page: > > https://gitlab.kitware.com/paraview/paraview > > There's link for CONTRIBUTING.md which should take you to the pages > that were updated. > > Also, when reporting a new issue, Gitlab automatically shows a link to > this file as "contributing guidelines" next to the "Submit" button for > a new issue. > > Utkarsh > > On Mon, Aug 22, 2016 at 8:14 PM, Scott, W Alan wrote: > > Being a bit slow here ... I see that we are checking in these docs - > great! But, where are they, and how can I see them? > > > > Thanks, > > > > Alan > > > > -----Original Message----- > > From: Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] On Behalf Of Utkarsh Ayachit > > Sent: Saturday, August 20, 2016 7:29 AM > > To: ParaView Developers > > Subject: [EXTERNAL] [Paraview-developers] Updates to ParaVIew > development workflow > > > > Folks, > > > > Now that we have started using Gitlab for both code review and issue > tracking, it's time to review our development workflow. > > > > Following discussions with several people involved with ParaView > development and release process, we now have a proposal for an updated > development workflow. I've updated the docs and created a merge request > here: > > > > https://gitlab.kitware.com/paraview/paraview/merge_requests/959 > > > > Suggestions, comments, revisions are welcome. > > > > Thanks, > > Utkarsh > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Tue Aug 23 09:43:01 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 23 Aug 2016 15:43:01 +0200 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: Message-ID: I clicked on one of the link in the introduction by mistake and realized most of them are gitlab 404 error, I supose it's a bug ? Mathieu Westphal On Tue, Aug 23, 2016 at 3:42 PM, Mathieu Westphal < mathieu.westphal at kitware.com> wrote: > I clicked on one of the link in the intruction by mistake and realized > most of them are gitlab 404 error, I supose it's a bug ? > > Mathieu Westphal > > On Tue, Aug 23, 2016 at 2:20 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Alan, >> >> Once these changes land, these will be accessible from the Gitlab >> ParaView landing page: >> >> https://gitlab.kitware.com/paraview/paraview >> >> There's link for CONTRIBUTING.md which should take you to the pages >> that were updated. >> >> Also, when reporting a new issue, Gitlab automatically shows a link to >> this file as "contributing guidelines" next to the "Submit" button for >> a new issue. >> >> Utkarsh >> >> On Mon, Aug 22, 2016 at 8:14 PM, Scott, W Alan >> wrote: >> > Being a bit slow here ... I see that we are checking in these docs - >> great! But, where are they, and how can I see them? >> > >> > Thanks, >> > >> > Alan >> > >> > -----Original Message----- >> > From: Paraview-developers [mailto:paraview-developers-bo >> unces at paraview.org] On Behalf Of Utkarsh Ayachit >> > Sent: Saturday, August 20, 2016 7:29 AM >> > To: ParaView Developers >> > Subject: [EXTERNAL] [Paraview-developers] Updates to ParaVIew >> development workflow >> > >> > Folks, >> > >> > Now that we have started using Gitlab for both code review and issue >> tracking, it's time to review our development workflow. >> > >> > Following discussions with several people involved with ParaView >> development and release process, we now have a proposal for an updated >> development workflow. I've updated the docs and created a merge request >> here: >> > >> > https://gitlab.kitware.com/paraview/paraview/merge_requests/959 >> > >> > Suggestions, comments, revisions are welcome. >> > >> > Thanks, >> > Utkarsh >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> > >> > Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Aug 23 09:47:11 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 23 Aug 2016 09:47:11 -0400 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: Message-ID: Can you be a bit more specific? Not sure which link you clicked or from where :). On Tue, Aug 23, 2016 at 9:43 AM, Mathieu Westphal wrote: > I clicked on one of the link in the introduction by mistake and realized > most of them are gitlab 404 error, I supose it's a bug ? > > Mathieu Westphal > > On Tue, Aug 23, 2016 at 3:42 PM, Mathieu Westphal > wrote: >> >> I clicked on one of the link in the intruction by mistake and realized >> most of them are gitlab 404 error, I supose it's a bug ? >> >> Mathieu Westphal >> >> On Tue, Aug 23, 2016 at 2:20 PM, Utkarsh Ayachit >> wrote: >>> >>> Alan, >>> >>> Once these changes land, these will be accessible from the Gitlab >>> ParaView landing page: >>> >>> https://gitlab.kitware.com/paraview/paraview >>> >>> There's link for CONTRIBUTING.md which should take you to the pages >>> that were updated. >>> >>> Also, when reporting a new issue, Gitlab automatically shows a link to >>> this file as "contributing guidelines" next to the "Submit" button for >>> a new issue. >>> >>> Utkarsh >>> >>> On Mon, Aug 22, 2016 at 8:14 PM, Scott, W Alan >>> wrote: >>> > Being a bit slow here ... I see that we are checking in these docs - >>> > great! But, where are they, and how can I see them? >>> > >>> > Thanks, >>> > >>> > Alan >>> > >>> > -----Original Message----- >>> > From: Paraview-developers >>> > [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Utkarsh >>> > Ayachit >>> > Sent: Saturday, August 20, 2016 7:29 AM >>> > To: ParaView Developers >>> > Subject: [EXTERNAL] [Paraview-developers] Updates to ParaVIew >>> > development workflow >>> > >>> > Folks, >>> > >>> > Now that we have started using Gitlab for both code review and issue >>> > tracking, it's time to review our development workflow. >>> > >>> > Following discussions with several people involved with ParaView >>> > development and release process, we now have a proposal for an updated >>> > development workflow. I've updated the docs and created a merge request >>> > here: >>> > >>> > https://gitlab.kitware.com/paraview/paraview/merge_requests/959 >>> > >>> > Suggestions, comments, revisions are welcome. >>> > >>> > Thanks, >>> > Utkarsh >>> > _______________________________________________ >>> > Powered by www.kitware.com >>> > >>> > Visit other Kitware open-source projects at >>> > http://www.kitware.com/opensource/opensource.html >>> > >>> > Search the list archives at: >>> > http://markmail.org/search/?q=Paraview-developers >>> > >>> > Follow this link to subscribe/unsubscribe: >>> > http://public.kitware.com/mailman/listinfo/paraview-developers >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > From sumeet.kumar507 at gmail.com Tue Aug 23 09:47:37 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Tue, 23 Aug 2016 06:47:37 -0700 Subject: [Paraview-developers] Parallel mesh reading Message-ID: Hello all, Let's have a very large mesh in GB's/TB's that too in one file. How can I read that file in parallel with any arbitrary number of processors. How can I divide my mesh in N independent pieces? that each processor would read. Is there any instructions for doing such kind of think in para-view. Is reading multiple files in parallel more efficient or reading one file in parallel more efficient in para-view. In either of these how I should design my output to be most efficient to be read by ParaView in Parallel. Sumeet -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Aug 23 09:50:26 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 23 Aug 2016 09:50:26 -0400 Subject: [Paraview-developers] Parallel mesh reading In-Reply-To: References: Message-ID: What kind of grid is it? It's much easier to read in topologically regular grids in parallel than unstructured grids. On Tue, Aug 23, 2016 at 9:47 AM, sumeet kumar wrote: > Hello all, > > Let's have a very large mesh in GB's/TB's that too in one file. How can I > read that file in parallel with any arbitrary number of processors. > > How can I divide my mesh in N independent pieces? that each processor > would read. Is there any instructions for doing such kind of think in > para-view. > > Is reading multiple files in parallel more efficient or reading one file > in parallel more efficient in para-view. In either of these how I should > design my output to be most efficient to be read by ParaView in Parallel. > > > Sumeet > > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetksinha.com/ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sumeet.kumar507 at gmail.com Tue Aug 23 09:51:51 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Tue, 23 Aug 2016 06:51:51 -0700 Subject: [Paraview-developers] Parallel mesh reading In-Reply-To: References: Message-ID: I have unstructured grids On Tue, Aug 23, 2016 at 6:50 AM, Andy Bauer wrote: > What kind of grid is it? It's much easier to read in topologically regular > grids in parallel than unstructured grids. > > On Tue, Aug 23, 2016 at 9:47 AM, sumeet kumar > wrote: > >> Hello all, >> >> Let's have a very large mesh in GB's/TB's that too in one file. How can I >> read that file in parallel with any arbitrary number of processors. >> >> How can I divide my mesh in N independent pieces? that each processor >> would read. Is there any instructions for doing such kind of think in >> para-view. >> >> Is reading multiple files in parallel more efficient or reading one file >> in parallel more efficient in para-view. In either of these how I should >> design my output to be most efficient to be read by ParaView in Parallel. >> >> >> Sumeet >> >> -- >> >> Sumeet Kumar Sinha >> Graduate Student >> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >> Website : http://www.sumeetksinha.com/ >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Aug 23 09:58:10 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 23 Aug 2016 09:58:10 -0400 Subject: [Paraview-developers] Parallel mesh reading In-Reply-To: References: Message-ID: The difficulty in parallel with unstructured grids is that it's tough to determine which cells need which points so for unstructured grids that are stored in a single file, all points often time are either read in on process 0 and broadcast out or each process reads in all points. Neither of these methods scale well. The advantage of multiple files here is that in each file the points are just the ones that are needed by the cells in that file. You could do a similar thing with blocks of points and cells in a single file. The main point here is that you need to think about an algorithm that has each process read in only (or nearly only) the points it needs in order to read in the cells in gets assigned. Also, consider whether or not you want your reader to be able to read in ghost cells as well. It's not a requirement for parallel readers but certain filter work better with ghost cells. On Tue, Aug 23, 2016 at 9:51 AM, sumeet kumar wrote: > I have unstructured grids > > On Tue, Aug 23, 2016 at 6:50 AM, Andy Bauer > wrote: > >> What kind of grid is it? It's much easier to read in topologically >> regular grids in parallel than unstructured grids. >> >> On Tue, Aug 23, 2016 at 9:47 AM, sumeet kumar >> wrote: >> >>> Hello all, >>> >>> Let's have a very large mesh in GB's/TB's that too in one file. How can >>> I read that file in parallel with any arbitrary number of processors. >>> >>> How can I divide my mesh in N independent pieces? that each processor >>> would read. Is there any instructions for doing such kind of think in >>> para-view. >>> >>> Is reading multiple files in parallel more efficient or reading one file >>> in parallel more efficient in para-view. In either of these how I should >>> design my output to be most efficient to be read by ParaView in Parallel. >>> >>> >>> Sumeet >>> >>> -- >>> >>> Sumeet Kumar Sinha >>> Graduate Student >>> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >>> Website : http://www.sumeetksinha.com/ >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: http://markmail.org/search/?q= >>> Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >>> >> > > > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetksinha.com/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Tue Aug 23 10:01:50 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Tue, 23 Aug 2016 16:01:50 +0200 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: Message-ID: Ho sorry, all the links here are wrong, there may be others. Introduction ParaView is an open-source, multi-platform data analysis and visualization application based on Visualization Toolkit (VTK) . The first public release was announced in October 2002. Since then, the project has grown through collaborative efforts between Kitware Inc. , Sandia National Laboratories , Los Alamos National Laboratory , Army Research Laboratory , and various other government and commercial institutions, and acedemic partners." Mathieu Westphal On Tue, Aug 23, 2016 at 3:47 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Can you be a bit more specific? Not sure which link you clicked or > from where :). > > On Tue, Aug 23, 2016 at 9:43 AM, Mathieu Westphal > wrote: > > I clicked on one of the link in the introduction by mistake and realized > > most of them are gitlab 404 error, I supose it's a bug ? > > > > Mathieu Westphal > > > > On Tue, Aug 23, 2016 at 3:42 PM, Mathieu Westphal > > wrote: > >> > >> I clicked on one of the link in the intruction by mistake and realized > >> most of them are gitlab 404 error, I supose it's a bug ? > >> > >> Mathieu Westphal > >> > >> On Tue, Aug 23, 2016 at 2:20 PM, Utkarsh Ayachit > >> wrote: > >>> > >>> Alan, > >>> > >>> Once these changes land, these will be accessible from the Gitlab > >>> ParaView landing page: > >>> > >>> https://gitlab.kitware.com/paraview/paraview > >>> > >>> There's link for CONTRIBUTING.md which should take you to the pages > >>> that were updated. > >>> > >>> Also, when reporting a new issue, Gitlab automatically shows a link to > >>> this file as "contributing guidelines" next to the "Submit" button for > >>> a new issue. > >>> > >>> Utkarsh > >>> > >>> On Mon, Aug 22, 2016 at 8:14 PM, Scott, W Alan > >>> wrote: > >>> > Being a bit slow here ... I see that we are checking in these docs - > >>> > great! But, where are they, and how can I see them? > >>> > > >>> > Thanks, > >>> > > >>> > Alan > >>> > > >>> > -----Original Message----- > >>> > From: Paraview-developers > >>> > [mailto:paraview-developers-bounces at paraview.org] On Behalf Of > Utkarsh > >>> > Ayachit > >>> > Sent: Saturday, August 20, 2016 7:29 AM > >>> > To: ParaView Developers > >>> > Subject: [EXTERNAL] [Paraview-developers] Updates to ParaVIew > >>> > development workflow > >>> > > >>> > Folks, > >>> > > >>> > Now that we have started using Gitlab for both code review and issue > >>> > tracking, it's time to review our development workflow. > >>> > > >>> > Following discussions with several people involved with ParaView > >>> > development and release process, we now have a proposal for an > updated > >>> > development workflow. I've updated the docs and created a merge > request > >>> > here: > >>> > > >>> > https://gitlab.kitware.com/paraview/paraview/merge_requests/959 > >>> > > >>> > Suggestions, comments, revisions are welcome. > >>> > > >>> > Thanks, > >>> > Utkarsh > >>> > _______________________________________________ > >>> > Powered by www.kitware.com > >>> > > >>> > Visit other Kitware open-source projects at > >>> > http://www.kitware.com/opensource/opensource.html > >>> > > >>> > Search the list archives at: > >>> > http://markmail.org/search/?q=Paraview-developers > >>> > > >>> > Follow this link to subscribe/unsubscribe: > >>> > http://public.kitware.com/mailman/listinfo/paraview-developers > >>> _______________________________________________ > >>> Powered by www.kitware.com > >>> > >>> Visit other Kitware open-source projects at > >>> http://www.kitware.com/opensource/opensource.html > >>> > >>> Search the list archives at: > >>> http://markmail.org/search/?q=Paraview-developers > >>> > >>> Follow this link to subscribe/unsubscribe: > >>> http://public.kitware.com/mailman/listinfo/paraview-developers > >> > >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sumeet.kumar507 at gmail.com Tue Aug 23 10:21:23 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Tue, 23 Aug 2016 07:21:23 -0700 Subject: [Paraview-developers] Parallel mesh reading In-Reply-To: References: Message-ID: Thank You Andy, for a quick reply. Thanks Sumeet On Tue, Aug 23, 2016 at 6:58 AM, Andy Bauer wrote: > The difficulty in parallel with unstructured grids is that it's tough to > determine which cells need which points so for unstructured grids that are > stored in a single file, all points often time are either read in on > process 0 and broadcast out or each process reads in all points. Neither of > these methods scale well. The advantage of multiple files here is that in > each file the points are just the ones that are needed by the cells in that > file. You could do a similar thing with blocks of points and cells in a > single file. The main point here is that you need to think about an > algorithm that has each process read in only (or nearly only) the points it > needs in order to read in the cells in gets assigned. Also, consider > whether or not you want your reader to be able to read in ghost cells as > well. It's not a requirement for parallel readers but certain filter work > better with ghost cells. > > On Tue, Aug 23, 2016 at 9:51 AM, sumeet kumar > wrote: > >> I have unstructured grids >> >> On Tue, Aug 23, 2016 at 6:50 AM, Andy Bauer >> wrote: >> >>> What kind of grid is it? It's much easier to read in topologically >>> regular grids in parallel than unstructured grids. >>> >>> On Tue, Aug 23, 2016 at 9:47 AM, sumeet kumar >> > wrote: >>> >>>> Hello all, >>>> >>>> Let's have a very large mesh in GB's/TB's that too in one file. How can >>>> I read that file in parallel with any arbitrary number of processors. >>>> >>>> How can I divide my mesh in N independent pieces? that each processor >>>> would read. Is there any instructions for doing such kind of think in >>>> para-view. >>>> >>>> Is reading multiple files in parallel more efficient or reading one >>>> file in parallel more efficient in para-view. In either of these how I >>>> should design my output to be most efficient to be read by ParaView in >>>> Parallel. >>>> >>>> >>>> Sumeet >>>> >>>> -- >>>> >>>> Sumeet Kumar Sinha >>>> Graduate Student >>>> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >>>> Website : http://www.sumeetksinha.com/ >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Search the list archives at: http://markmail.org/search/?q= >>>> Paraview-developers >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>> >>>> >>> >> >> >> -- >> >> Sumeet Kumar Sinha >> Graduate Student >> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >> Website : http://www.sumeetksinha.com/ >> > > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Aug 23 12:33:44 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 23 Aug 2016 12:33:44 -0400 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: Message-ID: Seems like links in the README.md are not the way Gitlab want them to be. Someone wants to take a stab at fixing those? On Tue, Aug 23, 2016 at 10:01 AM, Mathieu Westphal wrote: > Ho sorry, all the links here are wrong, there may be others. > > Introduction > > ParaView is an open-source, multi-platform data analysis and visualization > application based on Visualization Toolkit (VTK). > > The first public release was announced in October 2002. Since then, the > project has grown through collaborative efforts between Kitware Inc., Sandia > National Laboratories, Los Alamos National Laboratory, Army Research > Laboratory, and various other government and commercial institutions, and > acedemic partners." > > > Mathieu Westphal > > On Tue, Aug 23, 2016 at 3:47 PM, Utkarsh Ayachit > wrote: >> >> Can you be a bit more specific? Not sure which link you clicked or >> from where :). >> >> On Tue, Aug 23, 2016 at 9:43 AM, Mathieu Westphal >> wrote: >> > I clicked on one of the link in the introduction by mistake and realized >> > most of them are gitlab 404 error, I supose it's a bug ? >> > >> > Mathieu Westphal >> > >> > On Tue, Aug 23, 2016 at 3:42 PM, Mathieu Westphal >> > wrote: >> >> >> >> I clicked on one of the link in the intruction by mistake and realized >> >> most of them are gitlab 404 error, I supose it's a bug ? >> >> >> >> Mathieu Westphal >> >> >> >> On Tue, Aug 23, 2016 at 2:20 PM, Utkarsh Ayachit >> >> wrote: >> >>> >> >>> Alan, >> >>> >> >>> Once these changes land, these will be accessible from the Gitlab >> >>> ParaView landing page: >> >>> >> >>> https://gitlab.kitware.com/paraview/paraview >> >>> >> >>> There's link for CONTRIBUTING.md which should take you to the pages >> >>> that were updated. >> >>> >> >>> Also, when reporting a new issue, Gitlab automatically shows a link to >> >>> this file as "contributing guidelines" next to the "Submit" button for >> >>> a new issue. >> >>> >> >>> Utkarsh >> >>> >> >>> On Mon, Aug 22, 2016 at 8:14 PM, Scott, W Alan >> >>> wrote: >> >>> > Being a bit slow here ... I see that we are checking in these docs - >> >>> > great! But, where are they, and how can I see them? >> >>> > >> >>> > Thanks, >> >>> > >> >>> > Alan >> >>> > >> >>> > -----Original Message----- >> >>> > From: Paraview-developers >> >>> > [mailto:paraview-developers-bounces at paraview.org] On Behalf Of >> >>> > Utkarsh >> >>> > Ayachit >> >>> > Sent: Saturday, August 20, 2016 7:29 AM >> >>> > To: ParaView Developers >> >>> > Subject: [EXTERNAL] [Paraview-developers] Updates to ParaVIew >> >>> > development workflow >> >>> > >> >>> > Folks, >> >>> > >> >>> > Now that we have started using Gitlab for both code review and issue >> >>> > tracking, it's time to review our development workflow. >> >>> > >> >>> > Following discussions with several people involved with ParaView >> >>> > development and release process, we now have a proposal for an >> >>> > updated >> >>> > development workflow. I've updated the docs and created a merge >> >>> > request >> >>> > here: >> >>> > >> >>> > https://gitlab.kitware.com/paraview/paraview/merge_requests/959 >> >>> > >> >>> > Suggestions, comments, revisions are welcome. >> >>> > >> >>> > Thanks, >> >>> > Utkarsh >> >>> > _______________________________________________ >> >>> > Powered by www.kitware.com >> >>> > >> >>> > Visit other Kitware open-source projects at >> >>> > http://www.kitware.com/opensource/opensource.html >> >>> > >> >>> > Search the list archives at: >> >>> > http://markmail.org/search/?q=Paraview-developers >> >>> > >> >>> > Follow this link to subscribe/unsubscribe: >> >>> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >>> _______________________________________________ >> >>> Powered by www.kitware.com >> >>> >> >>> Visit other Kitware open-source projects at >> >>> http://www.kitware.com/opensource/opensource.html >> >>> >> >>> Search the list archives at: >> >>> http://markmail.org/search/?q=Paraview-developers >> >>> >> >>> Follow this link to subscribe/unsubscribe: >> >>> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> >> >> >> > > > From wascott at sandia.gov Tue Aug 23 20:40:26 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 24 Aug 2016 00:40:26 +0000 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: Message-ID: <4cb6ff7d5c4e4dd787e39c567b8a30ae@ES01AMSNLNT.srn.sandia.gov> I tried the link below, and did find Contributing. Nice. I suspect that the majority to vast majority of people who pull master are read only. Shouldn't we have a section that gives trivial directions on how to pull a fresh developer's tree? Or, should people just use the contributing page? If so, shouldn't we clarify somehow? "Get ParaView source, and optionally contribute"? Alan -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Tuesday, August 23, 2016 6:21 AM To: Scott, W Alan Cc: ParaView Developers Subject: Re: [EXTERNAL] [Paraview-developers] Updates to ParaVIew development workflow Alan, Once these changes land, these will be accessible from the Gitlab ParaView landing page: https://gitlab.kitware.com/paraview/paraview There's link for CONTRIBUTING.md which should take you to the pages that were updated. Also, when reporting a new issue, Gitlab automatically shows a link to this file as "contributing guidelines" next to the "Submit" button for a new issue. Utkarsh On Mon, Aug 22, 2016 at 8:14 PM, Scott, W Alan wrote: > Being a bit slow here ... I see that we are checking in these docs - great! But, where are they, and how can I see them? > > Thanks, > > Alan > > -----Original Message----- > From: Paraview-developers > [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Utkarsh > Ayachit > Sent: Saturday, August 20, 2016 7:29 AM > To: ParaView Developers > Subject: [EXTERNAL] [Paraview-developers] Updates to ParaVIew > development workflow > > Folks, > > Now that we have started using Gitlab for both code review and issue tracking, it's time to review our development workflow. > > Following discussions with several people involved with ParaView development and release process, we now have a proposal for an updated development workflow. I've updated the docs and created a merge request here: > > https://gitlab.kitware.com/paraview/paraview/merge_requests/959 > > Suggestions, comments, revisions are welcome. > > Thanks, > Utkarsh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers From utkarsh.ayachit at kitware.com Tue Aug 23 21:13:23 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 23 Aug 2016 21:13:23 -0400 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: Message-ID: > Seems like links in the README.md are not the way Gitlab want them to > be. Someone wants to take a stab at fixing those? Here's an MR that fixes the links in README.md: https://gitlab.kitware.com/paraview/paraview/merge_requests/969 From utkarsh.ayachit at kitware.com Tue Aug 23 21:14:54 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 23 Aug 2016 21:14:54 -0400 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: <4cb6ff7d5c4e4dd787e39c567b8a30ae@ES01AMSNLNT.srn.sandia.gov> References: <4cb6ff7d5c4e4dd787e39c567b8a30ae@ES01AMSNLNT.srn.sandia.gov> Message-ID: > I suspect that the majority to vast majority of people who pull master are read only. Shouldn't we have a section that gives trivial directions on how to pull a fresh developer's tree? Or, should people just use the contributing page? If so, shouldn't we clarify somehow? "Get ParaView source, and optionally contribute"? Yes. No objection there. We should migrate "download & build" from Wiki to such pages. From utkarsh.ayachit at kitware.com Wed Aug 24 09:09:04 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Aug 2016 09:09:04 -0400 Subject: [Paraview-developers] Changing ParaView default CMake variable values Message-ID: Folks, I wanted to propose changing the defaults for the following CMake variables in ParaView: VTK_RENDERING_BACKEND = OpenGL2 (currently OpenGL1) VTK_ENABLE_KITS = ON (currently OFF) The former will use the new rendering backend. The latter will build fewer libraries since multiple VTK modules gets built as a single kit library. Thoughts? Any other suggestions? Utkarsh From m.schlottke-lakemper at aia.rwth-aachen.de Wed Aug 24 09:36:40 2016 From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael) Date: Wed, 24 Aug 2016 13:36:40 +0000 Subject: [Paraview-developers] Changing ParaView default CMake variable values In-Reply-To: References: Message-ID: <4E94C901-98F5-4B8C-8CDF-88D7CE868A92@aia.rwth-aachen.de> Hi Utkarsh, Especially with the first change (rendering backend upgraded to OpenGL2) I suspect that some users might have builds fail because of missing dependencies on older systems (at least I expect it for some of our systems). Is there somewhere a list of library prerequisites that will change with this switch? I only know of http://www.paraview.org/Wiki/ParaView:Build_And_Install and there no OpenGL dependencies are listed explicitly. Regards, Michael -- Michael Schlottke-Lakemper Institute of Aerodynamics and Chair of Fluid Mechanics RWTH Aachen University W?llnerstra?e 5a 52062 Aachen Germany Phone: +49 (241) 80 95188 Fax: +49 (241) 80 92257 Mail: m.schlottke-lakemper at aia.rwth-aachen.de Web: http://www.aia.rwth-aachen.de On 24 Aug 2016, at 15:09 , Utkarsh Ayachit > wrote: Folks, I wanted to propose changing the defaults for the following CMake variables in ParaView: VTK_RENDERING_BACKEND = OpenGL2 (currently OpenGL1) VTK_ENABLE_KITS = ON (currently OFF) The former will use the new rendering backend. The latter will build fewer libraries since multiple VTK modules gets built as a single kit library. Thoughts? Any other suggestions? Utkarsh _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Wed Aug 24 09:50:39 2016 From: ken.martin at kitware.com (Ken Martin) Date: Wed, 24 Aug 2016 09:50:39 -0400 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: <4cb6ff7d5c4e4dd787e39c567b8a30ae@ES01AMSNLNT.srn.sandia.gov> References: <4cb6ff7d5c4e4dd787e39c567b8a30ae@ES01AMSNLNT.srn.sandia.gov> Message-ID: I see a lot of tags mentioned in that document. Will those be pull down options? If not, are developers expected to memorize them? I am good with pull downs picking the right choice but my memory is iffy :-) On Tue, Aug 23, 2016 at 8:40 PM, Scott, W Alan wrote: > I tried the link below, and did find Contributing. Nice. > > I suspect that the majority to vast majority of people who pull master are > read only. Shouldn't we have a section that gives trivial directions on > how to pull a fresh developer's tree? Or, should people just use the > contributing page? If so, shouldn't we clarify somehow? "Get ParaView > source, and optionally contribute"? > > Alan > > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Tuesday, August 23, 2016 6:21 AM > To: Scott, W Alan > Cc: ParaView Developers > Subject: Re: [EXTERNAL] [Paraview-developers] Updates to ParaVIew > development workflow > > Alan, > > Once these changes land, these will be accessible from the Gitlab ParaView > landing page: > > https://gitlab.kitware.com/paraview/paraview > > There's link for CONTRIBUTING.md which should take you to the pages that > were updated. > > Also, when reporting a new issue, Gitlab automatically shows a link to > this file as "contributing guidelines" next to the "Submit" button for a > new issue. > > Utkarsh > > On Mon, Aug 22, 2016 at 8:14 PM, Scott, W Alan wrote: > > Being a bit slow here ... I see that we are checking in these docs - > great! But, where are they, and how can I see them? > > > > Thanks, > > > > Alan > > > > -----Original Message----- > > From: Paraview-developers > > [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Utkarsh > > Ayachit > > Sent: Saturday, August 20, 2016 7:29 AM > > To: ParaView Developers > > Subject: [EXTERNAL] [Paraview-developers] Updates to ParaVIew > > development workflow > > > > Folks, > > > > Now that we have started using Gitlab for both code review and issue > tracking, it's time to review our development workflow. > > > > Following discussions with several people involved with ParaView > development and release process, we now have a proposal for an updated > development workflow. I've updated the docs and created a merge request > here: > > > > https://gitlab.kitware.com/paraview/paraview/merge_requests/959 > > > > Suggestions, comments, revisions are welcome. > > > > Thanks, > > Utkarsh > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 24 09:59:17 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Aug 2016 09:59:17 -0400 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: <4cb6ff7d5c4e4dd787e39c567b8a30ae@ES01AMSNLNT.srn.sandia.gov> Message-ID: On Wed, Aug 24, 2016 at 9:50 AM, Ken Martin wrote: > I see a lot of tags mentioned in that document. Will those be pull down > options? If not, are developers expected to memorize them? I am good with > pull downs picking the right choice but my memory is iffy :-) Yes, when you click on "Edit" next to "Labels" for any issue, a drop down pops up. BTW, the workflow may be a lot easier come Friday. We're updated to Gitlab 8.11 which now supports what it calls "Issue Boards" (https://youtu.be/UWsJ8tkHAa8) which make adding removing labels for transitioning from one state to another as easy as moving the issue around. From utkarsh.ayachit at kitware.com Wed Aug 24 09:59:57 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 24 Aug 2016 09:59:57 -0400 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: <4cb6ff7d5c4e4dd787e39c567b8a30ae@ES01AMSNLNT.srn.sandia.gov> Message-ID: read: "we're *updating* to Gitlabl 8.11" On Wed, Aug 24, 2016 at 9:59 AM, Utkarsh Ayachit wrote: > On Wed, Aug 24, 2016 at 9:50 AM, Ken Martin wrote: >> I see a lot of tags mentioned in that document. Will those be pull down >> options? If not, are developers expected to memorize them? I am good with >> pull downs picking the right choice but my memory is iffy :-) > > Yes, when you click on "Edit" next to "Labels" for any issue, a drop > down pops up. BTW, the workflow may be a lot easier come Friday. We're > updated to Gitlab 8.11 which now supports what it calls "Issue Boards" > (https://youtu.be/UWsJ8tkHAa8) which make adding removing labels for > transitioning from one state to another as easy as moving the issue > around. From ken.martin at kitware.com Wed Aug 24 10:03:17 2016 From: ken.martin at kitware.com (Ken Martin) Date: Wed, 24 Aug 2016 10:03:17 -0400 Subject: [Paraview-developers] [EXTERNAL] Updates to ParaVIew development workflow In-Reply-To: References: <4cb6ff7d5c4e4dd787e39c567b8a30ae@ES01AMSNLNT.srn.sandia.gov> Message-ID: Ohh that looks really nice! I like it! On Wed, Aug 24, 2016 at 9:59 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > read: "we're *updating* to Gitlabl 8.11" > > On Wed, Aug 24, 2016 at 9:59 AM, Utkarsh Ayachit > wrote: > > On Wed, Aug 24, 2016 at 9:50 AM, Ken Martin > wrote: > >> I see a lot of tags mentioned in that document. Will those be pull down > >> options? If not, are developers expected to memorize them? I am good > with > >> pull downs picking the right choice but my memory is iffy :-) > > > > Yes, when you click on "Edit" next to "Labels" for any issue, a drop > > down pops up. BTW, the workflow may be a lot easier come Friday. We're > > updated to Gitlab 8.11 which now supports what it calls "Issue Boards" > > (https://youtu.be/UWsJ8tkHAa8) which make adding removing labels for > > transitioning from one state to another as easy as moving the issue > > around. > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Wed Aug 24 10:19:11 2016 From: ken.martin at kitware.com (Ken Martin) Date: Wed, 24 Aug 2016 10:19:11 -0400 Subject: [Paraview-developers] Changing ParaView default CMake variable values In-Reply-To: <4E94C901-98F5-4B8C-8CDF-88D7CE868A92@aia.rwth-aachen.de> References: <4E94C901-98F5-4B8C-8CDF-88D7CE868A92@aia.rwth-aachen.de> Message-ID: I have a OpenGL2 document I try to keep up to date here https://docs.google.com/document/d/1ojY_20mQbRyCfmgxe-LuPKi82x3XwPlU_KfFLeJoBvo/edit#heading=h.a92mikls63mw I could probably be expanded some. The section on compatibility is currently as follows: The new OpenGL2 backend typically requires OpenGL 3.2. Most hardware from 2010 or later should support OpenGL 3.2. For Linux systems that lack hardware support for OpenGL3.2, Mesa version 10.5.5 and later has been shown to work with VTK. OS Mesa requires version 11.2. Apple Mac Pro with AMD Graphics Chips - there is/was a bug in some ATI drivers that causes picking and cell coloring to fail as of March 19th 2015. We have coded a workaround for the bug but it does impact performance significantly on Apple systems with AMD hardware. We have worked with Apple to fix the bug in El Capitan for most AMD cards they use. Windows remote desktop only supports OpenGL version 1.4, the new backend will not work with this. Other options like VNC and nomachine should work. Windows computers that DO NOT have an NVidia or AMD GPU will rely on their Intel GPU if present. Desktop and laptop Intel CPUs from IvyBridge (early 2012) or later should be fine as long as your drivers are up to date. Most Intel Xeon CPUs lack a GPU and some workstation CPUs (6 cores or more) do as well. In those cases you would need a dedicated GPU. On Wed, Aug 24, 2016 at 9:36 AM, Schlottke-Lakemper, Michael < m.schlottke-lakemper at aia.rwth-aachen.de> wrote: > Hi Utkarsh, > > Especially with the first change (rendering backend upgraded to OpenGL2) I > suspect that some users might have builds fail because of missing > dependencies on older systems (at least I expect it for some of our > systems). Is there somewhere a list of library prerequisites that will > change with this switch? I only know of http://www.paraview.org/ > Wiki/ParaView:Build_And_Install and there no OpenGL dependencies are > listed explicitly. > > Regards, > > Michael > > > -- > Michael Schlottke-Lakemper > > Institute of Aerodynamics and Chair of Fluid Mechanics > RWTH Aachen University > W?llnerstra?e 5a > 52062 Aachen > Germany > > Phone: +49 (241) 80 95188 > Fax: +49 (241) 80 92257 > Mail: m.schlottke-lakemper at aia.rwth-aachen.de > Web: http://www.aia.rwth-aachen.de > > On 24 Aug 2016, at 15:09 , Utkarsh Ayachit > wrote: > > Folks, > > I wanted to propose changing the defaults for the following CMake > variables in ParaView: > > VTK_RENDERING_BACKEND = OpenGL2 (currently OpenGL1) > VTK_ENABLE_KITS = ON (currently OFF) > > The former will use the new rendering backend. The latter will build > fewer libraries since multiple VTK modules gets built as a single kit > library. > > Thoughts? Any other suggestions? > > Utkarsh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Aug 25 14:29:10 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 25 Aug 2016 14:29:10 -0400 Subject: [Paraview-developers] GitLab upgrade today, August 25, at 5:15PM EST Message-ID: Dear developers, gitlab.kitware.com will be upgraded this evening at 5:15pm to enable new features. Access may be briefly limited. Sorry for the short notice. Thanks, Cory -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matthew.Czech at pfizer.com Thu Aug 25 16:21:56 2016 From: Matthew.Czech at pfizer.com (Czech, Matthew) Date: Thu, 25 Aug 2016 20:21:56 +0000 Subject: [Paraview-developers] Create programmable source via python shell Message-ID: Hello, Is it possible to create a programmable source via the python shell? Any information on this is much appreciated. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Aug 25 21:12:51 2016 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 25 Aug 2016 21:12:51 -0400 Subject: [Paraview-developers] Create programmable source via python shell In-Reply-To: References: Message-ID: Sure is. Here is a minimal example. from paraview.simple import * programmableSource1 = ProgrammableSource() programmableSource1.Script = 'print "Hello World"' programmableSource1.UpdatePipeline() In general, try Tools->Start Trace, make a source or anything really, Tools->Stop Trace to see how to do things. good luck David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Aug 25, 2016 at 4:21 PM, Czech, Matthew wrote: > Hello, > > Is it possible to create a programmable source via the python shell? Any > information on this is much appreciated. > > Thanks, > Matt > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.Murphy at lasp.colorado.edu Thu Aug 25 21:27:43 2016 From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy) Date: Fri, 26 Aug 2016 01:27:43 +0000 Subject: [Paraview-developers] Create programmable source via python shell In-Reply-To: References: Message-ID: <9B206401-E850-4A78-B8FC-3EE43D0A72AC@lasp.colorado.edu> I was just about to ask a very similar question, but I was wondering how to create a source in pvpython without using the programmable source. I have a larger script that I would like to generate the source, but I am having trouble figuring out how to get my vtkStructuredGrid data into a source that can be visualized on a pipeline. Any suggestions for this use case? Thanks, Josh From: Paraview-developers on behalf of David E DeMarle Date: Thursday, August 25, 2016 at 7:12 PM To: "Czech, Matthew" Cc: "paraview-developers at paraview.org" Subject: Re: [Paraview-developers] Create programmable source via python shell Sure is. Here is a minimal example. from paraview.simple import * programmableSource1 = ProgrammableSource() programmableSource1.Script = 'print "Hello World"' programmableSource1.UpdatePipeline() In general, try Tools->Start Trace, make a source or anything really, Tools->Stop Trace to see how to do things. good luck David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Aug 25, 2016 at 4:21 PM, Czech, Matthew > wrote: Hello, Is it possible to create a programmable source via the python shell? Any information on this is much appreciated. Thanks, Matt _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Fri Aug 26 07:15:21 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 26 Aug 2016 13:15:21 +0200 Subject: [Paraview-developers] ParaQ documentation Message-ID: Hello Could we take down ParaQ Documentation ? I don't think it is still used by anyone, yet it always shows up first in google searches, wich can be cumbersome for developpers and problematic for new developpers. https://www.google.fr/search?btnG=1&pws=0&q=vtkPVRenderView&gws_rd=cr&ei=riTAV8PFEcT-af2vu_AB Regards Mathieu Westphal -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.lonie at kitware.com Fri Aug 26 09:51:32 2016 From: david.lonie at kitware.com (David Lonie) Date: Fri, 26 Aug 2016 09:51:32 -0400 Subject: [Paraview-developers] Create programmable source via python shell In-Reply-To: <9B206401-E850-4A78-B8FC-3EE43D0A72AC@lasp.colorado.edu> References: <9B206401-E850-4A78-B8FC-3EE43D0A72AC@lasp.colorado.edu> Message-ID: On Thu, Aug 25, 2016 at 9:27 PM, Joshua Murphy wrote: > I was just about to ask a very similar question, but I was wondering how to > create a source in pvpython without using the programmable source. I have a > larger script that I would like to generate the source, but I am having > trouble figuring out how to get my vtkStructuredGrid data into a source that > can be visualized on a pipeline. Any suggestions for this use case? If you've already got a data object you want to use in a pipeline, check out vtkTrivialProducer: http://www.vtk.org/doc/nightly/html/classvtkTrivialProducer.html HTH, Dave From david.lonie at kitware.com Fri Aug 26 09:52:23 2016 From: david.lonie at kitware.com (David Lonie) Date: Fri, 26 Aug 2016 09:52:23 -0400 Subject: [Paraview-developers] Create programmable source via python shell In-Reply-To: References: <9B206401-E850-4A78-B8FC-3EE43D0A72AC@lasp.colorado.edu> Message-ID: On Fri, Aug 26, 2016 at 9:51 AM, David Lonie wrote: > On Thu, Aug 25, 2016 at 9:27 PM, Joshua Murphy > wrote: >> I was just about to ask a very similar question, but I was wondering how to >> create a source in pvpython without using the programmable source. I have a >> larger script that I would like to generate the source, but I am having >> trouble figuring out how to get my vtkStructuredGrid data into a source that >> can be visualized on a pipeline. Any suggestions for this use case? > > If you've already got a data object you want to use in a pipeline, > check out vtkTrivialProducer: > > http://www.vtk.org/doc/nightly/html/classvtkTrivialProducer.html Actually, I'm not sure if this is VTK only or if it'd work in ParaView, too... From thomasblome at startmail.com Sat Aug 27 12:46:48 2016 From: thomasblome at startmail.com (thomasblome at startmail.com) Date: Sat, 27 Aug 2016 18:46:48 +0200 Subject: [Paraview-developers] cmake error configuring catalyst project Message-ID: <54a417a8e29114d0e57681fcc2cb76ce.startmail@www.startmail.com> Hi, I downloaded the latest Catalyst edition (5.1.2) to build it on my Windows 10 system. In CMake I use default settings, but it starts complaining while configuring, displaying following error message: ? CMake Error at VTK/CMake/vtkModuleTop.cmake:59 (message): No such module "vtkGUISupportQt" needed by "vtkPVVTKExtensionsRendering" Call Stack (most recent call first): VTK/CMake/vtkModuleTop.cmake:75 (vtk_module_check) VTK/CMake/vtkModuleTop.cmake:75 (vtk_module_check) VTK/CMake/vtkModuleTop.cmake:82 (vtk_module_check) VTK/CMakeLists.txt:543 (include) Does anybody know how to fix that? Kind regards, Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 7F53DEC77F67D0E0.asc Type: application/pgp-keys Size: 3082 bytes Desc: OpenPGP public keys URL: From andy.bauer at kitware.com Sun Aug 28 07:06:42 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Sun, 28 Aug 2016 07:06:42 -0400 Subject: [Paraview-developers] cmake error configuring catalyst project In-Reply-To: <54a417a8e29114d0e57681fcc2cb76ce.startmail@www.startmail.com> References: <54a417a8e29114d0e57681fcc2cb76ce.startmail@www.startmail.com> Message-ID: Did you try the build directions at http://www.paraview.org/Wiki/Build_Directions? You'll want to use the cmake.sh script instead of the default CMake settings. On Sat, Aug 27, 2016 at 12:46 PM, wrote: > Hi, > > I downloaded the latest Catalyst edition (5.1.2) to build it on my Windows > 10 system. > In CMake I use default settings, but it starts complaining while > configuring, displaying following error message: > > > CMake Error at VTK/CMake/vtkModuleTop.cmake:59 (message): > No such module "vtkGUISupportQt" needed by "vtkPVVTKExtensionsRendering" > Call Stack (most recent call first): > VTK/CMake/vtkModuleTop.cmake:75 (vtk_module_check) > VTK/CMake/vtkModuleTop.cmake:75 (vtk_module_check) > VTK/CMake/vtkModuleTop.cmake:82 (vtk_module_check) > VTK/CMakeLists.txt:543 (include) > > Does anybody know how to fix that? > > Kind regards, > Thomas > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.schlottke-lakemper at aia.rwth-aachen.de Mon Aug 29 11:36:09 2016 From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael) Date: Mon, 29 Aug 2016 15:36:09 +0000 Subject: [Paraview-developers] Changing ParaView default CMake variable values In-Reply-To: References: <4E94C901-98F5-4B8C-8CDF-88D7CE868A92@aia.rwth-aachen.de> Message-ID: <54F21FDB-6F3E-4653-8DB4-DD8A40741971@aia.rwth-aachen.de> Hi Ken, Thanks for your reply. This is going to be an issue for us (as expected), as a quick check reveals that we use an older Version of OS Mesa on our cluster (of course, this can and will be changed eventually). Do you know if there an easy way to check if my hardware/Linux distro supports OpenGL 3.2 (we are using openSUSE)? Yours Michael On 24 Aug 2016, at 16:19 , Ken Martin > wrote: I have a OpenGL2 document I try to keep up to date here https://docs.google.com/document/d/1ojY_20mQbRyCfmgxe-LuPKi82x3XwPlU_KfFLeJoBvo/edit#heading=h.a92mikls63mw I could probably be expanded some. The section on compatibility is currently as follows: The new OpenGL2 backend typically requires OpenGL 3.2. Most hardware from 2010 or later should support OpenGL 3.2. For Linux systems that lack hardware support for OpenGL3.2, Mesa version 10.5.5 and later has been shown to work with VTK. OS Mesa requires version 11.2. Apple Mac Pro with AMD Graphics Chips - there is/was a bug in some ATI drivers that causes picking and cell coloring to fail as of March 19th 2015. We have coded a workaround for the bug but it does impact performance significantly on Apple systems with AMD hardware. We have worked with Apple to fix the bug in El Capitan for most AMD cards they use. Windows remote desktop only supports OpenGL version 1.4, the new backend will not work with this. Other options like VNC and nomachine should work. Windows computers that DO NOT have an NVidia or AMD GPU will rely on their Intel GPU if present. Desktop and laptop Intel CPUs from IvyBridge (early 2012) or later should be fine as long as your drivers are up to date. Most Intel Xeon CPUs lack a GPU and some workstation CPUs (6 cores or more) do as well. In those cases you would need a dedicated GPU. On Wed, Aug 24, 2016 at 9:36 AM, Schlottke-Lakemper, Michael > wrote: Hi Utkarsh, Especially with the first change (rendering backend upgraded to OpenGL2) I suspect that some users might have builds fail because of missing dependencies on older systems (at least I expect it for some of our systems). Is there somewhere a list of library prerequisites that will change with this switch? I only know of http://www.paraview.org/Wiki/ParaView:Build_And_Install and there no OpenGL dependencies are listed explicitly. Regards, Michael -- Michael Schlottke-Lakemper Institute of Aerodynamics and Chair of Fluid Mechanics RWTH Aachen University W?llnerstra?e 5a 52062 Aachen Germany Phone: +49 (241) 80 95188 Fax: +49 (241) 80 92257 Mail: m.schlottke-lakemper at aia.rwth-aachen.de Web: http://www.aia.rwth-aachen.de On 24 Aug 2016, at 15:09 , Utkarsh Ayachit > wrote: Folks, I wanted to propose changing the defaults for the following CMake variables in ParaView: VTK_RENDERING_BACKEND = OpenGL2 (currently OpenGL1) VTK_ENABLE_KITS = ON (currently OFF) The former will use the new rendering backend. The latter will build fewer libraries since multiple VTK modules gets built as a single kit library. Thoughts? Any other suggestions? Utkarsh _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Tue Aug 30 09:00:13 2016 From: ken.martin at kitware.com (Ken Martin) Date: Tue, 30 Aug 2016 09:00:13 -0400 Subject: [Paraview-developers] Changing ParaView default CMake variable values In-Reply-To: <54F21FDB-6F3E-4653-8DB4-DD8A40741971@aia.rwth-aachen.de> References: <4E94C901-98F5-4B8C-8CDF-88D7CE868A92@aia.rwth-aachen.de> <54F21FDB-6F3E-4653-8DB4-DD8A40741971@aia.rwth-aachen.de> Message-ID: It is a little tricky as I think the answer is a combination of your hardware and your software. I'm not the best Linux person around so maybe someone else has a better answer. From a live system point of view I believe glxinfo will report the GL_VERSION your system supports. So anything 3.2 or later should be good for your default OpenGL. OSMesa is I think a bit different as I do not think glxinfo picks that up. I have seen good results with the nvidia linux drivers on hardware from the past 5 years. One other gotcha that has bitten us, is that there is an SGI patent that impacts Mesa's support for floating point textures. So some distros ship a version of Mesa that does not include floating point textures. This can cause issues depending on what you are rendering. Hope that helps Ken On Mon, Aug 29, 2016 at 11:36 AM, Schlottke-Lakemper, Michael < m.schlottke-lakemper at aia.rwth-aachen.de> wrote: > Hi Ken, > > Thanks for your reply. This is going to be an issue for us (as expected), > as a quick check reveals that we use an older Version of OS Mesa on our > cluster (of course, this can and will be changed eventually). Do you know > if there an easy way to check if my hardware/Linux distro supports OpenGL > 3.2 (we are using openSUSE)? > > Yours > > Michael > > On 24 Aug 2016, at 16:19 , Ken Martin wrote: > > I have a OpenGL2 document I try to keep up to date here > > https://docs.google.com/document/d/1ojY_20mQbRyCfmgxe- > LuPKi82x3XwPlU_KfFLeJoBvo/edit#heading=h.a92mikls63mw > > I could probably be expanded some. The section on compatibility is > currently as follows: > > > The new OpenGL2 backend typically requires OpenGL 3.2. Most hardware from > 2010 or later should support OpenGL 3.2. For Linux systems that lack > hardware support for OpenGL3.2, Mesa version 10.5.5 and later has been > shown to work with VTK. OS Mesa requires version 11.2. > > Apple Mac Pro with AMD Graphics Chips - there is/was a bug in some ATI > drivers that causes picking and cell coloring to fail as of March 19th > 2015. We have coded a workaround for the bug but it does impact performance > significantly on Apple systems with AMD hardware. We have worked with Apple > to fix the bug in El Capitan for most AMD cards they use. > > Windows remote desktop only supports OpenGL version 1.4, the new backend > will not work with this. Other options like VNC and nomachine should work. > > Windows computers that DO NOT have an NVidia or AMD GPU will rely on their > Intel GPU if present. Desktop and laptop Intel CPUs from IvyBridge (early > 2012) or later should be fine as long as your drivers are up to date. Most > Intel Xeon CPUs lack a GPU and some workstation CPUs (6 cores or more) do > as well. In those cases you would need a dedicated GPU. > > > On Wed, Aug 24, 2016 at 9:36 AM, Schlottke-Lakemper, Michael < > m.schlottke-lakemper at aia.rwth-aachen.de> wrote: > >> Hi Utkarsh, >> >> Especially with the first change (rendering backend upgraded to OpenGL2) >> I suspect that some users might have builds fail because of missing >> dependencies on older systems (at least I expect it for some of our >> systems). Is there somewhere a list of library prerequisites that will >> change with this switch? I only know of http://www.paraview.org/Wik >> i/ParaView:Build_And_Install and there no OpenGL dependencies are listed >> explicitly. >> >> Regards, >> >> Michael >> >> >> -- >> Michael Schlottke-Lakemper >> >> Institute of Aerodynamics and Chair of Fluid Mechanics >> RWTH Aachen University >> W?llnerstra?e 5a >> 52062 Aachen >> Germany >> >> Phone: +49 (241) 80 95188 >> Fax: +49 (241) 80 92257 >> Mail: m.schlottke-lakemper at aia.rwth-aachen.de >> Web: http://www.aia.rwth-aachen.de >> >> On 24 Aug 2016, at 15:09 , Utkarsh Ayachit >> wrote: >> >> Folks, >> >> I wanted to propose changing the defaults for the following CMake >> variables in ParaView: >> >> VTK_RENDERING_BACKEND = OpenGL2 (currently OpenGL1) >> VTK_ENABLE_KITS = ON (currently OFF) >> >> The former will use the new rendering backend. The latter will build >> fewer libraries since multiple VTK modules gets built as a single kit >> library. >> >> Thoughts? Any other suggestions? >> >> Utkarsh >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > > > -- > Ken Martin PhD > Chairman & CFO > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > 518 371 3971 > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.schlottke-lakemper at aia.rwth-aachen.de Wed Aug 31 15:06:46 2016 From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael) Date: Wed, 31 Aug 2016 19:06:46 +0000 Subject: [Paraview-developers] Changing ParaView default CMake variable values In-Reply-To: References: <4E94C901-98F5-4B8C-8CDF-88D7CE868A92@aia.rwth-aachen.de> <54F21FDB-6F3E-4653-8DB4-DD8A40741971@aia.rwth-aachen.de> Message-ID: <4148BC4B-4D01-4BCE-B56F-6162E40ECF66@aia.rwth-aachen.de> Thanks for the hint! ?glxinfo | grep -i version? did the trick for me. Regards, Michael P.S.: Unfortunately, for our cluster OpenGL 3.0 seems to be the norm, so I guess I will have to explicitly disable the new backend starting with 5.2.0? On 30 Aug 2016, at 15:00 , Ken Martin > wrote: It is a little tricky as I think the answer is a combination of your hardware and your software. I'm not the best Linux person around so maybe someone else has a better answer. From a live system point of view I believe glxinfo will report the GL_VERSION your system supports. So anything 3.2 or later should be good for your default OpenGL. OSMesa is I think a bit different as I do not think glxinfo picks that up. I have seen good results with the nvidia linux drivers on hardware from the past 5 years. One other gotcha that has bitten us, is that there is an SGI patent that impacts Mesa's support for floating point textures. So some distros ship a version of Mesa that does not include floating point textures. This can cause issues depending on what you are rendering. Hope that helps Ken On Mon, Aug 29, 2016 at 11:36 AM, Schlottke-Lakemper, Michael > wrote: Hi Ken, Thanks for your reply. This is going to be an issue for us (as expected), as a quick check reveals that we use an older Version of OS Mesa on our cluster (of course, this can and will be changed eventually). Do you know if there an easy way to check if my hardware/Linux distro supports OpenGL 3.2 (we are using openSUSE)? Yours Michael On 24 Aug 2016, at 16:19 , Ken Martin > wrote: I have a OpenGL2 document I try to keep up to date here https://docs.google.com/document/d/1ojY_20mQbRyCfmgxe-LuPKi82x3XwPlU_KfFLeJoBvo/edit#heading=h.a92mikls63mw I could probably be expanded some. The section on compatibility is currently as follows: The new OpenGL2 backend typically requires OpenGL 3.2. Most hardware from 2010 or later should support OpenGL 3.2. For Linux systems that lack hardware support for OpenGL3.2, Mesa version 10.5.5 and later has been shown to work with VTK. OS Mesa requires version 11.2. Apple Mac Pro with AMD Graphics Chips - there is/was a bug in some ATI drivers that causes picking and cell coloring to fail as of March 19th 2015. We have coded a workaround for the bug but it does impact performance significantly on Apple systems with AMD hardware. We have worked with Apple to fix the bug in El Capitan for most AMD cards they use. Windows remote desktop only supports OpenGL version 1.4, the new backend will not work with this. Other options like VNC and nomachine should work. Windows computers that DO NOT have an NVidia or AMD GPU will rely on their Intel GPU if present. Desktop and laptop Intel CPUs from IvyBridge (early 2012) or later should be fine as long as your drivers are up to date. Most Intel Xeon CPUs lack a GPU and some workstation CPUs (6 cores or more) do as well. In those cases you would need a dedicated GPU. On Wed, Aug 24, 2016 at 9:36 AM, Schlottke-Lakemper, Michael > wrote: Hi Utkarsh, Especially with the first change (rendering backend upgraded to OpenGL2) I suspect that some users might have builds fail because of missing dependencies on older systems (at least I expect it for some of our systems). Is there somewhere a list of library prerequisites that will change with this switch? I only know of http://www.paraview.org/Wiki/ParaView:Build_And_Install and there no OpenGL dependencies are listed explicitly. Regards, Michael -- Michael Schlottke-Lakemper Institute of Aerodynamics and Chair of Fluid Mechanics RWTH Aachen University W?llnerstra?e 5a 52062 Aachen Germany Phone: +49 (241) 80 95188 Fax: +49 (241) 80 92257 Mail: m.schlottke-lakemper at aia.rwth-aachen.de Web: http://www.aia.rwth-aachen.de On 24 Aug 2016, at 15:09 , Utkarsh Ayachit > wrote: Folks, I wanted to propose changing the defaults for the following CMake variables in ParaView: VTK_RENDERING_BACKEND = OpenGL2 (currently OpenGL1) VTK_ENABLE_KITS = ON (currently OFF) The former will use the new rendering backend. The latter will build fewer libraries since multiple VTK modules gets built as a single kit library. Thoughts? Any other suggestions? Utkarsh _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Aug 31 19:34:06 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 31 Aug 2016 23:34:06 +0000 Subject: [Paraview-developers] Master build errors probably in vtkSMCoreUtilities.cxx Message-ID: <88dcde83b3ae4f9bb35d00e6b25afc45@ES01AMSNLNT.srn.sandia.gov> Utkarsh, Here are some build errors. Help? This is on a cluster build Alan [ 11%] Building CXX object ParaViewCore/ServerManager/Core/CMakeFiles/vtkPVServerManagerCore.dir/vtkSMCoreUtilities.cxx.o /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx(181): error: more than one instance of overloaded function "std::abs" matches the argument list: function "std::abs(double)" function "std::abs(float)" function "std::abs(long double)" argument types are: (int) EquivSizeIntT delta = std::abs(irange[1] - irange[0]); ^ detected during instantiation of "bool ::AdjustTRange(T *, EquivSizeIntT) [with T=float, EquivSizeIntT=int]" at line 216 /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx(181): error: more than one instance of overloaded function "std::abs" matches the argument list: function "std::abs(double)" function "std::abs(float)" function "std::abs(long double)" argument types are: (long long) EquivSizeIntT delta = std::abs(irange[1] - irange[0]); ^ detected during instantiation of "bool ::AdjustTRange(T *, EquivSizeIntT) [with T=double, EquivSizeIntT=signed long long]" at line 226 compilation aborted for /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx (code 2) gmake[2]: *** [ParaViewCore/ServerManager/Core/CMakeFiles/vtkPVServerManagerCore.dir/vtkSMCoreUtilities.cxx.o] Error 2 Here's a git log of the file: commit fe2cf0b0c89f79076219df7c7ea211e38ad89ae0 Author: Shawn Waldon Date: Fri Aug 26 11:57:42 2016 -0400 Update the tiny range delta to work when passing in doubles The delta worked well for floats, but when passing in doubles we needed a larger delta so that the difference would be noticable when the numbers were later downcase to float for display. commit 450a1545e2a777e83568e7a975df1212306a7133 Author: Robert Maynard Date: Fri Apr 15 14:06:35 2016 -0400 Fix strict aliasing warnings in vtkSMCoreUtilities AdjustRange commit 604cbe44c15ce547a631508a30ad744b6984c402 Author: Robert Maynard Date: Wed Apr 13 17:35:35 2016 -0400 vtkSMCoreUtilities now adjusts ranges properly when min~=max. Previously when min and max where very close to being equal but also very small numbers they would not offset from each other sufficiently. commit 3154b783090e58ee277d96a8d893d01ff9b796b1 Author: Brad King Date: Thu Aug 20 13:25:43 2015 -0400 Remove use of include and vtksys_ios::*stringstream Use the following commands to switch to standard header and namespace: git grep -l vtksys/ios | xargs sed -i 's|vtksys/ios/sstream|sstream|' git grep -l vtksys_ios:: | xargs sed -i 's|vtksys_ios::|std::|g' commit a9cb582ed5647f4b34cefc907013a14677924b5c Author: Utkarsh Ayachit Date: Tue Jun 30 22:44:10 2015 -0400 Consolidate code to adjust empty range. When resetting lut ranges, we need to avoid setting null range. This consolidates that code in vtkSMCoreUtilities. vtkSMPVRepresentationProxy and vtkSMTransferFunctionManager now use this new static method in vtkSMCoreUtilities, called AdjustRange(). -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Aug 31 21:00:23 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 1 Sep 2016 01:00:23 +0000 Subject: [Paraview-developers] [EXTERNAL] Master build errors probably in vtkSMCoreUtilities.cxx In-Reply-To: <88dcde83b3ae4f9bb35d00e6b25afc45@ES01AMSNLNT.srn.sandia.gov> References: <88dcde83b3ae4f9bb35d00e6b25afc45@ES01AMSNLNT.srn.sandia.gov> Message-ID: <57079bc76d714feda5e5cc7b915598bb@ES01AMSNLNT.srn.sandia.gov> And, client side builds on the LAN: [ 35%] Building CXX object ParaViewCore/ServerManager/Core/CMakeFiles/vtkPVServerManagerCore.dir/vtkSMCoreUtilities.cxx.o /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx: In function ?bool::AdjustTRange(T*, EquivSizeIntT) [with T = float, EquivSizeIntT = int]?: /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx:216: instantiated from here /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx:181: error: call of overloaded ?abs(int)? is ambiguous /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:94: note: candidates are: double std::abs(double) /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:98: note: float std::abs(float) /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:102: note: long double std::abs(long double) /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx: In function ?bool::AdjustTRange(T*, EquivSizeIntT) [with T = double, EquivSizeIntT = long long int]?: /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx:226: instantiated from here /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx:181: error: call of overloaded ?abs(long long int)? is ambiguous /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:94: note: candidates are: double std::abs(double) /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:98: note: float std::abs(float) /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:102: note: long double std::abs(long double) gmake[2]: *** [ParaViewCore/ServerManager/Core/CMakeFiles/vtkPVServerManagerCore.dir/vtkSMCoreUtilities.cxx.o] Error 1 gmake[1]: *** [ParaViewCore/ServerManager/Core/CMakeFiles/vtkPVServerManagerCore.dir/all] Error 2 Alan From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Wednesday, August 31, 2016 5:34 PM To: paraview-developers at paraview.org Subject: [EXTERNAL] [Paraview-developers] Master build errors probably in vtkSMCoreUtilities.cxx Utkarsh, Here are some build errors. Help? This is on a cluster build Alan [ 11%] Building CXX object ParaViewCore/ServerManager/Core/CMakeFiles/vtkPVServerManagerCore.dir/vtkSMCoreUtilities.cxx.o /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx(181): error: more than one instance of overloaded function "std::abs" matches the argument list: function "std::abs(double)" function "std::abs(float)" function "std::abs(long double)" argument types are: (int) EquivSizeIntT delta = std::abs(irange[1] - irange[0]); ^ detected during instantiation of "bool ::AdjustTRange(T *, EquivSizeIntT) [with T=float, EquivSizeIntT=int]" at line 216 /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx(181): error: more than one instance of overloaded function "std::abs" matches the argument list: function "std::abs(double)" function "std::abs(float)" function "std::abs(long double)" argument types are: (long long) EquivSizeIntT delta = std::abs(irange[1] - irange[0]); ^ detected during instantiation of "bool ::AdjustTRange(T *, EquivSizeIntT) [with T=double, EquivSizeIntT=signed long long]" at line 226 compilation aborted for /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx (code 2) gmake[2]: *** [ParaViewCore/ServerManager/Core/CMakeFiles/vtkPVServerManagerCore.dir/vtkSMCoreUtilities.cxx.o] Error 2 Here's a git log of the file: commit fe2cf0b0c89f79076219df7c7ea211e38ad89ae0 Author: Shawn Waldon > Date: Fri Aug 26 11:57:42 2016 -0400 Update the tiny range delta to work when passing in doubles The delta worked well for floats, but when passing in doubles we needed a larger delta so that the difference would be noticable when the numbers were later downcase to float for display. commit 450a1545e2a777e83568e7a975df1212306a7133 Author: Robert Maynard > Date: Fri Apr 15 14:06:35 2016 -0400 Fix strict aliasing warnings in vtkSMCoreUtilities AdjustRange commit 604cbe44c15ce547a631508a30ad744b6984c402 Author: Robert Maynard > Date: Wed Apr 13 17:35:35 2016 -0400 vtkSMCoreUtilities now adjusts ranges properly when min~=max. Previously when min and max where very close to being equal but also very small numbers they would not offset from each other sufficiently. commit 3154b783090e58ee277d96a8d893d01ff9b796b1 Author: Brad King > Date: Thu Aug 20 13:25:43 2015 -0400 Remove use of include and vtksys_ios::*stringstream Use the following commands to switch to standard header and namespace: git grep -l vtksys/ios | xargs sed -i 's|vtksys/ios/sstream|sstream|' git grep -l vtksys_ios:: | xargs sed -i 's|vtksys_ios::|std::|g' commit a9cb582ed5647f4b34cefc907013a14677924b5c Author: Utkarsh Ayachit > Date: Tue Jun 30 22:44:10 2015 -0400 Consolidate code to adjust empty range. When resetting lut ranges, we need to avoid setting null range. This consolidates that code in vtkSMCoreUtilities. vtkSMPVRepresentationProxy and vtkSMTransferFunctionManager now use this new static method in vtkSMCoreUtilities, called AdjustRange(). -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 31 23:30:15 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 31 Aug 2016 23:30:15 -0400 Subject: [Paraview-developers] [EXTERNAL] Master build errors probably in vtkSMCoreUtilities.cxx In-Reply-To: <57079bc76d714feda5e5cc7b915598bb@ES01AMSNLNT.srn.sandia.gov> References: <88dcde83b3ae4f9bb35d00e6b25afc45@ES01AMSNLNT.srn.sandia.gov> <57079bc76d714feda5e5cc7b915598bb@ES01AMSNLNT.srn.sandia.gov> Message-ID: Wow! You're fast! This was merged in just earlier today! Shawn, can you take a look please? Thanks. Utkarsh On Wed, Aug 31, 2016 at 9:00 PM, Scott, W Alan wrote: > And, client side builds on the LAN: > > > > [ 35%] Building CXX object ParaViewCore/ServerManager/Core/CMakeFiles/ > vtkPVServerManagerCore.dir/vtkSMCoreUtilities.cxx.o > > /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ > ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx: In function > ?bool::AdjustTRange(T*, EquivSizeIntT) [with T = float, > EquivSizeIntT = int]?: > > /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ > ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx:216: > instantiated from here > > /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ > ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx:181: error: call > of overloaded ?abs(int)? is ambiguous > > /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:94: > note: candidates are: double std::abs(double) > > /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:98: > note: float std::abs(float) > > /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:102: > note: long double std::abs(long double) > > /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ > ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx: In function > ?bool::AdjustTRange(T*, EquivSizeIntT) [with T = double, > EquivSizeIntT = long long int]?: > > /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ > ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx:226: > instantiated from here > > /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ > ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx:181: error: call > of overloaded ?abs(long long int)? is ambiguous > > /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:94: > note: candidates are: double std::abs(double) > > /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:98: > note: float std::abs(float) > > /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/cmath:102: > note: long double std::abs(long double) > > gmake[2]: *** [ParaViewCore/ServerManager/Core/CMakeFiles/ > vtkPVServerManagerCore.dir/vtkSMCoreUtilities.cxx.o] Error 1 > > gmake[1]: *** [ParaViewCore/ServerManager/Core/CMakeFiles/ > vtkPVServerManagerCore.dir/all] Error 2 > > > > > > Alan > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] *On Behalf Of *Scott, W Alan > *Sent:* Wednesday, August 31, 2016 5:34 PM > *To:* paraview-developers at paraview.org > *Subject:* [EXTERNAL] [Paraview-developers] Master build errors probably > in vtkSMCoreUtilities.cxx > > > > Utkarsh, > > Here are some build errors. Help? This is on a cluster build > > > > Alan > > > > [ 11%] Building CXX object ParaViewCore/ServerManager/Core/CMakeFiles/ > vtkPVServerManagerCore.dir/vtkSMCoreUtilities.cxx.o > > /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ > ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx(181): error: more > than one instance of overloaded function "std::abs" matches the argument > list: > > function "std::abs(double)" > > function "std::abs(float)" > > function "std::abs(long double)" > > argument types are: (int) > > EquivSizeIntT delta = std::abs(irange[1] - irange[0]); > > ^ > > detected during instantiation of "bool ::AdjustTRange(T > *, EquivSizeIntT) [with T=float, EquivSizeIntT=int]" at line 216 > > > > /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/ > ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx(181): error: more > than one instance of overloaded function "std::abs" matches the argument > list: > > function "std::abs(double)" > > function "std::abs(float)" > > function "std::abs(long double)" > > argument types are: (long long) > > EquivSizeIntT delta = std::abs(irange[1] - irange[0]); > > ^ > > detected during instantiation of "bool ::AdjustTRange(T > *, EquivSizeIntT) [with T=double, EquivSizeIntT=signed long long]" at line > 226 > > > > compilation aborted for /projects/viz/paraview/src/ > ParaView/5.2.0-junk/ParaView5/ParaViewCore/ServerManager/Core/vtkSMCoreUtilities.cxx > (code 2) > > gmake[2]: *** [ParaViewCore/ServerManager/Core/CMakeFiles/ > vtkPVServerManagerCore.dir/vtkSMCoreUtilities.cxx.o] Error 2 > > > > > > > > > > > > Here?s a git log of the file: > > > > commit fe2cf0b0c89f79076219df7c7ea211e38ad89ae0 > > Author: Shawn Waldon > > Date: Fri Aug 26 11:57:42 2016 -0400 > > > > Update the tiny range delta to work when passing in doubles > > > > The delta worked well for floats, but when passing in doubles we > needed a > > larger delta so that the difference would be noticable when the numbers > > were later downcase to float for display. > > > > commit 450a1545e2a777e83568e7a975df1212306a7133 > > Author: Robert Maynard > > Date: Fri Apr 15 14:06:35 2016 -0400 > > > > Fix strict aliasing warnings in vtkSMCoreUtilities AdjustRange > > > > commit 604cbe44c15ce547a631508a30ad744b6984c402 > > Author: Robert Maynard > > Date: Wed Apr 13 17:35:35 2016 -0400 > > > > vtkSMCoreUtilities now adjusts ranges properly when min~=max. > > > > Previously when min and max where very close to being equal but also > very > > small numbers they would not offset from each other sufficiently. > > > > commit 3154b783090e58ee277d96a8d893d01ff9b796b1 > > Author: Brad King > > Date: Thu Aug 20 13:25:43 2015 -0400 > > > > Remove use of include and > vtksys_ios::*stringstream > > > > Use the following commands to switch to standard header and namespace: > > > > git grep -l vtksys/ios | xargs sed -i 's|vtksys/ios/sstream|sstream|' > > git grep -l vtksys_ios:: | xargs sed -i 's|vtksys_ios::|std::|g' > > > > commit a9cb582ed5647f4b34cefc907013a14677924b5c > > Author: Utkarsh Ayachit > > Date: Tue Jun 30 22:44:10 2015 -0400 > > > > Consolidate code to adjust empty range. > > > > When resetting lut ranges, we need to avoid setting null range. This > > consolidates that code in vtkSMCoreUtilities. > vtkSMPVRepresentationProxy > > and vtkSMTransferFunctionManager now use this new static method in > > vtkSMCoreUtilities, called AdjustRange(). > > > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 31 23:33:39 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 31 Aug 2016 23:33:39 -0400 Subject: [Paraview-developers] Changing ParaView package structure Message-ID: Folks, We've been investigating cleaning up ParaView's package structure on various platforms to be more standard and consistent with other apps. Here's what we have so far for Linux [1] and Windows [2] [1] https://gitlab.kitware.com/paraview/paraview/issues/16870 [2] https://gitlab.kitware.com/paraview/paraview/issues/16872 Any thoughts, suggestions, objections are welcome. This is not necessarily targeted for 5.2 release, but at least wanted to get the ball rolling. Thanks as always, Utkarsh -------------- next part -------------- An HTML attachment was scrubbed... URL: