We are anticipating a June release date for Pointwise Version 17.1 R3. Although this is a minor update, it includes several new features in addition to bug fixes.
We began the practice of adding new features to minor releases (those that increment the “R” number) after the release of V17.0. (Pat Baker's post on Another Fine Mesh about our release process provides more background on how we get software out the door.) Prior to V17.0, minor releases were strictly maintenance – bug fixes only. We maintained this separation of our maintenance and new development code branches in the hope of keeping the maintenance branch as robust as possible. The unintended downside of this plan was that customers needing features, especially relatively small ones, had to wait for the next major release for the release.
We don't unnecessarily warehouse features anymore. Part of our development planning is choosing which features to move from the new development code branch to the maintenance code branch in time for a minor release.
Here are some of those features we are making available in V17.1 R3 and beyond.
You will be able to set the number of cutting plane increments and the coordinate extents of the cutting planes in the Examine command (see an example in Figure 1). Prior to this addition, the cutting plane locations were computed as 2 per cent increments of the coordinate extents of the selected volume grids. Now, you will have significantly more flexibility.
As shown in Figure 2, the new scan plane controls are
Support for the Kestrel CFD solver has been added to Pointwise in cooperation with the Kestrel development team. AVMesh V1.0 format (aka rev 0) is currently supported with plans to extend that to V1.1 (aka rev 1) when that new specification is published. Kestrel is one of the CFD solvers being developed under the auspices of the U.S. Government's CREATE program.
The existing interface to Exodus II, the popular Department of Energy file format for finite element data, has been updated. (Exodus-II is available on SourceForge In addition to upgrading support to the latest version of the libraries, baffle inflation and T-Rex cell recombination were added.
For those of you who write templates and macros using the Glyph scripting language, an optional parameter has been added to the closestPoint and intersectRay methods in the pw::Database class that returns a Boolean value indicating whether or not a surface was found.
And Pointwise's version number is now displayed in its window's title bar.
New feature development continues for releases beyond V17.1 R3. Some of these features are complete, whereas others are still in-work.
Of course, many other features are in various stages of planning.
In terms of major new capabilities, our longer term development efforts are focused on three areas. As mentioned previously in The Connector and other forums, our work on merging overset grid assembly (OGA) with meshing will soon be delivered for use by all our customers. This contracted effort, funded by the U.S. Air Force at AEDC, was completed this past month, thereby freeing the development effort to move from research to production. This new capability includes the ability to set up grids for hole-cutting, spawn either PEGASUS or Suggar++ to cut the holes, and visualize the results, including identification of fringe and orphan points. Also included are some techniques for grid remediation to fix problems identified by the hole-cutter.
Continuing work on T-Rex (anisotropic tetrahedral extrusion, the advancing layer technique for hybrid meshing with boundary layer resolution) will focus on improving cell quality, increasing the height of the extruded layers, and adding more automation and efficiency to the process.
In what may be the most impactful of our longer term development efforts, we are extending Pointwise's support for grid types to include meshes with mixed cell types. For example, currently a volume grid in Pointwise has either all structured hexes or all tetrahedral or uniform layers of prisms. In the future, we'll be able to maintain a single volume grid containing all of those cell types and more. We are targeting capabilities like these:
All our development efforts, of course, rely on feedback and direction from the Pointwise Advisory Team, a select group of customers and partners who review our development plans before we start writing code. Their feedback was critical to the features in V17.1 R3 and will continue to be vital as we continue forward.
You'll receive a special issue of The Connector when V17.1 R3 is released. As always, to be certain you're using the latest version of Pointwise, you can check the download page on our website.