Certainly one can apply a variation of the Pareto Principle to mesh generation: 80 percent of your mesh is generated using only 20 percent of the software's functionality. That's because the essential steps in mesh generation are basically the same, no matter what type of mesh you're generating:
However, that leaves a lot of the mesh generator's functionality unexplored. That's a shame because in Pointwise there are a lot of very powerful commands that you might not be aware of that can really speed you along with your meshing. So with that introduction, here is a list of some very helpful commands about which many users are not aware:
Five years ago the computer science and cognitive science communities deemed the use of rainbow color maps for display of scalar field data to be harmful [Reference 1]. More specifically, rainbow color maps are said to be “confusing, obscuring, and actively misleading.” Coincidentally, at this month's AIAA Aerospace Sciences meeting the invited paper by the University of Utah's Mike Kirby re-iterated that conclusion [Reference 2]. What should you use instead?
Fortunately, Pointwise's Examine command for visualizing mesh quality metrics provides five choices for color bars (aka ramps) (see Figure 1), including the ability to reverse each of them. Unfortunately, not many people know about this capability.
Figure 2, Figure 3, Figure 4, Figure 5, and Figure 6 illustrate the differences between Pointwise's five color bars: Spectrum, Full Spectrum, Modern, Red Blue, and Grayscale, respectively. A quick comparison reveals why Grayscale might address the concerns cited in Reference 1 in the respect that relative values are easier to discern. But regardless of which you prefer, they're all available to you.
You might not think there's anything special about deleting things. But there's a big difference between the Delete (Del) and Delete Special (Ctrl+Del) commands. For example, when you select a block and press Delete, the block is deleted. However, its parent entities (domains and connectors) remain. If you want to delete an entity and its parents, press Delete Special instead. This applies to all topological entities from models and quilts, to blocks and domains.
Undo (Ctrl+Z) in the Edit menu not only is very powerful but it's a favorite of users. The reason should be obvious: Undo lets you recover from mistakes or unexpected results. People in the field of user interface design like to say that Undo gives users the freedom to explore the software's functionality without fear, because they can try a command and easily Undo if they don't like what it did. [Reference 3]
Depending on how error-prone or conservative you are, you can set the number of Undo levels in Pointwise as high as 20 (see Figure 8). The default value for number of Undo levels is five. The number of levels is simply the number of commands that can be undone relative to the grid's current state.
What's important to keep in mind is how Undo works in Pointwise. Undo is implemented as a state machine rather than by reversible commands. That means Pointwise has to store the changes between successive states – in other words, the differences between the grid at each undo level. Furthermore, the differences are stored in memory; they are not rolled off to disk.
Therefore, imagine the effect on your memory usage for any command that changes a block's interior grid points, such as running the Solve command. Obviously, your block will always contain the volume grid, but now the Undo stack also contains the previous version of the volume grid. That's two copies of your volume grid. You can see how that will start consuming a lot of memory.
The flexibility of retaining 20 undo levels has to be weighed against the negative impact of increasing memory usage. In fact, you might consider reducing the number of undo levels to only one to have the best of both worlds – the ability to recover while minimizing memory usage.
You can change the number of undo levels in the Edit, Preferences command in the Miscellaneous frame (see Figure 9).
There are many instances in which a command on the toolbar behaves differently than the same command in the menus. Intersect is one such command. Keep in mind that, in general, Intersect computes the intersection of all the entities in one set (Group A) with all the entities in another set (Group B). Let's assume you want to intersect two entities. If you select them and use Create, Intersect from the menu, the command assumes those two entities comprise Group A and it waits for you to select Group B.
The faster way to intersect the two entities is to select them both and press the Intersect button on the toolbar. The toolbar implementation of Intersect computes the intersection of each selected entity with all other selected entities without opening the command panel. You can see how intersecting two or more entities with the menu bar (see Figure 11) is much faster.
The challenges of dealing with CAD data are well documented. One of the most problematic aspects of working with CAD data involves handling the gaps and overlaps caused by tolerance and data translation issues. Pointwise offers two suites of tools for handling this: fault tolerant meshing and solid meshing. In the former, the mesh is “healed” over the CAD gaps primarily by using the Merge command. In the latter, the CAD geometry is assembled into a watertight solid model that's mesh-ready.
For those of you unfamiliar with solid modeling, a solid is simply a topological entity in which surface geometry is knitted together like a quilt, resulting in an object that is watertight, hence the name solid model. In Pointwise, models can be open (like half an aircraft split down its centerline) or closed (like a flange or other mechanical part).
Assembling models can be performed interactively through a process of selecting various CAD surfaces and setting a tolerance but that can often involve a bit of trial and error, depending on the CAD data's source and your familiarity with it.
But in cases in which you are familiar with the CAD data, you can have the model assembled automatically during CAD import. As an example, consider the mechanical part shown in Figure 12. By default, the CAD data is imported without any attempt to assemble the solid model. In Figure 12, the result is more than 60 disconnected surfaces (shown by colors).
Many users miss that models can be assembled for you automatically during import. After you select the CAD file to import, you'll see a panel with several import options (see Figure 13). One of these options is Model Assembly Tolerance and as long as you set it to a positive number, the code will attempt to assemble solid model(s) for you automatically. (Of course, this is why it's important to understand your CAD data, so that the tolerance is set correctly.)
For the mechanical part shown above, a single, watertight solid model is assembled automatically, as seen in Figure 14.
Almost everyone uses the Print to File (Ctrl+P) command to capture the Display window image and save it to a PNG, BMP, or TIFF image file. But few know that the companion Print to File Setup (Ctrl+Shift+P) command lets you customize how the image is saved.
As you can see from Figure 15, the Colors frame gives you control over the image's foreground and background colors. For example, suppose you have set a preference for a two-color gradient background, but you don't want that included in your images. You can set the background color to black, white or other choices via the Background radio buttons. (Figure 18 was made by using the Black Background option to remove the gradient background seen in Figure 17.)
The really interesting controls are in the Advanced frame, where you can create an image file at a higher resolution than what you see on the screen. For example, assume you need to produce an image for a print publication that will be printed at 300 dpi and needs to be 4 inches wide by 2.5 inches high. Once you enter those parameters in the panel, the Display window shows a cropping guide for your use in positioning the image. The table at the top of the panel lists the parameters of the image file to be created (see Figure 16).
Even when CAD data is imported accurately and correctly, it can still pose many challenges to mesh generation. One such challenge is the inclusion of excessive detail. These details (small holes, for example) complicate mesh generation while adding nothing to the analysis. Therefore, a goal for meshing would be to remove unnecessary detail.
Consider the CAD geometry for a simplified engine block shown in Figure 17. [Reference 4]
Assuming you don't need to include the extruded lettering in the mesh, it can be removed easily using the Untrim command. You're probably familiar with the two commands used to create trimmed surfaces – Trim by Surfaces and Trim by Curves. But Untrim is the one you want to use here. Untrim simply removes trimming curves from a surface. This differs from simply deleting the trimming part. For example, in Figure 17, if you just deleted the surfaces that comprise the raised lettering, the endplate of the engine block would still have three holes, cutouts for each of the letters (see Figure 18, left). Instead, you want to untrim the endplate by removing the curves that define the shapes of the letters, leaving the endplate untrimmed (see Figure 18, right).
To accomplish this, you select the endplate's quilt (without digressing too much, a quilt is similar to a trimmed surface) and press Edit, Untrim. You see the quilt's trimming curves highlighted. Select those curves and press Untrim.
Here's one last powerful but lesser-used command: Zoom to Selection (Shift+F2). If you want to get a close look at one particular entity, the easiest way to see it up close and personal is to click it and use Zoom to Selection in the View menu. The selected entity (or entities) will be positioned to fill the Display window.
The best way to learn more about the breadth of functionality that Pointwise has to offer is to attend one of our training courses. We have a course coming up at the Pointwise User Group Meeting 2013 in March. Come join us and see what you've been missing.
3rd Quarter of 2017
2nd Quarter of 2017
May 2017, Special Edition
1st Quarter of 2017
December 2016, Special Edition
4th Quarter of 2016
September 2016, Special Edition
3rd Quarter of 2016
2nd Quarter of 2016
1st Quarter of 2016
February 2016, Special Edition
November / December 2015
September 2015, Special Edition
September / October 2015
July / August 2015
June 2015, Special Edition
May 2015, Special Edition
May / June 2015
March / April 2015
February 2015, Special Edition
January / February 2015
November / December 2014
September / October 2014
August 2014, Special Edition
July / August 2014
May / June 2014
April 2014, Special Edition
March / April 2014
January / February 2014
November / December 2013
September 2013, Special Edition
September / October 2013
July / August 2013
June 2013, Special Edition
May / June 2013
March / April 2013
February 2013, Special Edition
January / February 2013
December 2012, Special Edition
November / December 2012
September / October 2012
August 2012, Special Edition
July / August 2012
May / June 2012
March / April 2012
March 2012, Special Edition
January / February 2012
November / December 2011
September / October 2011
July / August 2011
May / June 2011
March / April 2011
January / February 2011