Rndtble Logo 5IMR Panel Discussion Notes

Panel Discussion
5th International Meshing Roundtable `96.
October 10, 1996. Pittsburgh.

Index

Panel Makeup
Contact information and panelists' web pages
Discussion notes
First prepared question - technical issues
Audience questions
Second prepared question - cultural issues
More audience questions
Links back

Panelists

Paul Chew, Cornell University
Norimasa Chiba, Hitachi, Ltd., Mechanical Engineering Research Lab
Samuel Key, Sandia National Laboratories
David Marcum, Mississippi State University
Renato Perucchio, University of Rochester
Moderator: Scott Mitchell, Sandia National Laboratories

Contact Information

Paul Chew
721 Rhodes Hall
Cornell University
Ithaca, NY 14853
Phone: (607)255-9217
FAX: (607)255-4428
E-mail:
chew@cs.cornell.edu
URL: http://www.cs.cornell.edu/home/chew/chew.html

Norimasa Chiba
Center for CAE
Mechanical Engineering Research Laboratory, Hitachi, Ltd.
502 Kandatsu, Tsuchiura, Ibaraki 300, Japan
Phone: 0298-32-4111(x6850)
FAX: 0298-31-8961
E-mail: chibax@merl.hitachi.co.jp

Sam Key
Sandia National Laboratories
P.O. Box 5800
MS 0443
Albuquerque, NM 87185-0443
Phone: (505) 845-0875
FAX: (505) 844-9297
E-mail: swkey@sandia.gov

Dave Marcum
NSF Research Center for Computational Field Simulation
Mechanical Engineering Department
Mail Stop 9552, 210 Carpenter Building
Mississippi State University
Mississippi Sate, MS 39762
Phone: (601) 325-7310 or (601) 325-2423 (at ERC -- usually here in summer)
FAX: (601) 325-7223
E-mail: marcum@erc.msstate.edu
URL: http://www.msstate.edu/Dept/ME/FACULTY/marcum.html

Renato Perucchio
Dept. Mechanical Engineering
University of Rochester
Rochester, NY 14627
Phone: (716) 275-4069
E-mail: rlp@me.rochester.edu
URL: http://www.me.rochester.edu:8080/perucchio.html

Scott Mitchell
Sandia National Laboratories
P.O. Box 5800
MS 0441
Albuquerque, NM 87185-0443
Phone: (505) 845-7594
FAX: (505) 844-9297
E-mail: samitch@sandia.gov
URL: http://endo.sandia.gov/~samitch/


Prepared Q1: What are the key technical issues facing mesh generation today in your research/application area?

Paul Chew:

There are many application challenges to computational geometry. This was an easy question for me to prepare for because its almost the same as the question considered in the recent CG (Computational Geometry) Impact task force report
(postscript).
Open Questions (proving something about):
· Heuristics for point-set triangulations
· Surface representation
· Volume Mesh Generation
· Hexehedral meshes
· Advancing Front
· Mesh Generation & CAD systems
· Mesh Partitioning
· Multigrid for Unstructured Meshes
· Robustness
· Automatic Remeshing

Norimasa Chiba:

Tetrahedral Mesh
· Mesh Density control
· high quality perfect automation, embedded in analysis programs (for people who desire not to worry about meshing)
Hexehedral Mesh
· Automatization level
· mesh quality good enough to compete with mapped mesh (for mesh-conscious people)

Sam Key:

Title: Where meshing is going in the future.

The situation for a software developer guy at Sandia: On one side is massively parallel computing (9000 Intel P6 CPUs running at 200MHz), on the other side is management wanting 5x106 elements. The sides move together, squashing the developer between two walls.

The way the solution process is now: First we build the problem on a front end machine, then we roll in domain decomposition tools and break the problem into subdomains. The subdomains are then doled out onto individual processors of the MP machine. As MP machine gets bigger, the front end machine must encompass it (memory). This paradigm will break down.

The way the process will/should become: The front end machine will create subdomains, plus a boundary mesh (only) with meshing instructions for filling in the interior for each subdomain. These are doled out to the MP machine's CPUs. This small data set is expanded on the MP to a full mesh. Fully automated blind meshing that must take place if we're going to have big analysis and quality simulations.

David Marcum:

Geometry Clean-up/Repair
· Takes significant user input & time
· For meshing, an approximate geometry may be adequate
· Don't expect the CAD world to change for meshers. We must deal with Geometry Clean-up/Repair on the meshing side.
· + overlaps - trim surfaces can be automatic
· + gaps - we only need an approximation to the undefined regions. Small surface patches can create new problems
· + Multiple surfaces - group together to eliminate interior edges
· Carpeting - difficult to automate
· Global map -

Automation -
· Infinite loop quite possible
· Automate by tuning the tools to particular application areas
· Speed of generator can minimize user dissatisfaction with having to provide input.

Adaptation/Anisotropic Elements
· General anisotropic adaptation must be aligned. If not may angles will destroy solver performance
· Required for large 3D problems (CFD - Anisotropy will not be feasible in foreseeable future for high resolution meshes
· very application dependent
· Feature detection and tilting tied to physics - resolution tied to solver accuracy
· local regeneration for dynamic problems.

Polyhedral elements
· 100% hex mesh not reasonable for cases with complex geometry and varying element size
· mixed element grids provide the most suitable elements for local topology / geometry
· How do you generate polyhedral elements?
· Driven by solvers. Reduce CPU & memory?

Renato Perucchio:

Solid model Reconstruction of geometry.
The Meshing community commonly assumes that the starting point is a solid model with well defined bounding surfaces. This is not the case for many medical applications. Sometimes just cross-sectional data, or pixel data.

Biomechanical applications involve anisotropy, incompressibility, - all the "bad stuff" which requires hexahedral finite element modeling. How does one derive, in a semi-automatic fashion, a mesh?

I want an integrated adaptive computational system like the following: 0) Finite element modeling starts with some form of solid modeling kernel, able to take medical data and produce some sort of solid model. 1) Paradigm: Mesh generation, then analysis, then verification of the results. If the system finds that the mesh was not good enough, then the system goes back to 0), the Geometric/solid modeling kernel, or to 1), the mesh generation step. The challenge is constructing geometry, and being able to reconstruct geometry, out of which you can derive other meshes and other analysis.

Audience questions:

Q. Dennis Vasilopoulos: (People laugh as he takes the floor, recalling his long speech at last year's Roundtable.) Last year the hottest subject was all-hex mesh generation: "How many of us can see the light at the end of the tunnel?" This year, is all-hex mesh generation still the hot item on the market? If it is, how many of us today see light at the end of the tunnel? Do we have to make any short cuts?

A: Renato Perucchio: You have to define the solid you want to apply hex meshing to. If you're looking for something that is capable of handling all possible solids, then - at present - the problem has no solution and may very well be mathematically intractable.

But for vertical applications within a specific problem domain, the all-hex meshing problem has solutions. In a complete sense, I don't see a future for fully automatic procedures in hexahedral meshing. We won't be able to operate without interactive tools.

Sam Key: Preference is all-hex mesh. The computation mechanics community is trying to make Hexehedral in solid mechanics, which can relieve the pressure.

Q. Incompressible Elements - use full hex and Lagrangian to get internal freedom. Need to pay attention to high steps, too.

Q. I think in one year there will be automatic hex meshers. We'll have number of tools (for specific domains) that put together will solve the general problem. As tools progress, people are more satisfied with what they get. All-hex meshing is less of an issue this year.

Q.Ted Blacker: At what cost can we come up with a semi-automatic mesher, and cease to want a completely automated mesher.

Q. Scott Canann: Is hex meshing the number one topic, or is dealing with geometry problems? Hexes will always be problem, but is it the number one problem?

Q. Joe Walsh - The real issue is producing a mesh that produces quality (analysis) results. In the past one had to go with a hex mesh to get quality analysis results. Limiting factor - geometry mesh (need to clean up). Get efficient error estimation adaptivity going along with it.

Reza Taghavi: Mesh generation is an intermediate step to design, where the computer proposes a solution.

Sam Key: Do you mean high quality mesh generation will take place in background?

Reza Taghavi:. Yes, either in the CAD tool or the analysis tool. Use partial method.

Harley Wattrick: Consider the design process and where meshing fits into it. Hardware suppliers can make a rapid prototype and test it faster then we can mesh it. The CAD problem is a quality issue, if the paradigm is to create the geometry and document it, then the quality issue belongs to the person creating the geometry. Fitting the meshing problem into the whole design thing is a major problem today. How do we get it (information) to go from the meshing environment to product design environment.

Ted Blacker: Re: Sam's large models. Mesh generation will have smaller memory requirements then (on each subdomain v.s. entire domain at once).

Randy Lober: The typical (non-labs) user is not generating meshes of size on the order that Sam suggested.

Comments: What's the feasibility of and need for large meshes like Sam proposes?

In Sam's introductory paradigm, parallel mesh generation is reduced to creating subdomains.

Editorial comment: Seems to be a consensus this year that Hex meshing is very problem domain dependent.

Prepared Q2. What are the key cultural issues facing mesh generation today in your research/ application area?

Paul Chew:

Cultural issue - Is what we (Computational Geometry researchers) do useful in practice?

Chiba:

Some issues exist, not very big ones. Due to demands of production.

Sam Key:

Cultural Nourishment - I'm assuming that people in this room are a fair cross section of people working in meshing. I don't see enough "fire in the gut". Because of this I'm not confident this community will solve the problem. You don't realize your importance and what a huge impact you can have if you are successful (at automating, all-hex meshing).

Dave Marcum? Mark Shephard?:

Theoretical vs. applied - many good ideas from the math community get over-looked. We don't understand what they are trying to say. The reality (in practice) is if a procedure works, then that is what will be used. Its not enough to prove mathematically that an algorithm is good. If the results are worse than something that isn't provable, it has little impact.

Renato Perucchio:

Scenarios for the future of automatic 3d mesh generation, in order of preference.
· Fully automatic 3d all-hex meshing, provides both generation & adaptive remeshing.
· Interactive automatic 3d all-hex meshing; provides semi-automatic mesh generation but not adaptive remeshing
· Fully automatic 3d all-tetrahedral meshing; provides auto mesh generation and adaptive remeshing
· Fully automatic 3d mixed (hex and tet) meshing; provides auto mesh generation and adaptive remeshing

For generic solid:
· Solid is defined in a solid modeling system.
· Solid is non-manifold.
· Solid is bound by free-form surfaces.
In biomechanical application researchers have began to use voxel models directly as meshes. Essentially the model is the mesh. This is new and challenging but could yield fully automatic tools at least for specific areas of application.

More Audience questions:

Q. Harley Wattrick: Cultural issue - State of affairs: Analysts have all-tet meshing tools in their hands. All the work in the tet field is focussed on loading and balancing issues. Is the hex dominate community defining the technology? Is the tet community going to pass the hexers by, e.g. 10-node tetrahedron for elastic analysis has some promise.

Pedro Marcal: Tools should provide a measure of error at the end of the analysis. We don't have that today, but we could and should.

Narrative: A small debate rages about whether current error analysis technology provides a reliable error estimate for hex meshes. Some say the theory is in place and useful for tet meshes. Some say error estimates are not reliable. Maybe it depends on the subdiscipline.

Gary Miller: We (Gary and a student) did a study of technologies/algorithms mainly in the area of applied mathematics and matrix algorithm. In all cases, its been about 20 years from conception to realization. E.g. QR factorization, interior point methods.

(Perhaps its too early to expect hex meshing to be accepted. Perhaps tet meshing will be accepted fully and there will be no need of hex meshing.)

Various speculations about why 20 years: one theory purely technical. One theory purely social - old users won't switch to new tools, so it takes 20 years for old users to retire and new users to come in who are willing to try something new.

Ted Blacker: The social explanation is based on the assumption that the user is stupid. People may be time pressured for results, but they are not stupid. The explanation for 20 years is that it takes experience for a user to have confidence in the tools. Yes, I'm right. This confidence takes time and experience. Its a matter of practicality - what can I (as a user) trust and what can I get done. Another comment is, re: Pedro Marcal's comment, error analysis is no answer.

Q: We need more theory results. We don't know the conditions under which a hex mesh exists.

A. Scott Mitchell: Well, some of us write existence proofs (see my web page and paper which answers this very question) . But I agree, there is more room for theory to make a practical impact in meshing.

Q. Scott Mitchell: Let's bring this back to the panel: Is inertia, namely unwillingness to change and use new tools, a problem in your field and a possible explanation for the 20 year phenomena?

A. Sam Key: Perhaps a little bit, but not a great deal.

A. Paul Chew: The opposite is a problem in the Theoretical Computer Science community. There are plenty of people who are willing to explore. Sometimes a fad catches on, rather than proving useful things.

A. David Field - People use tets because they have to get the job done and there was no other way to do it.
Narrative: David then gave a history of how analysis and hex elements arose at GM.

Scott Mitchell: Well, this could go on all night, but that's what the dinner cruise is for. Lets let Tammy Wilson give us directions to the boat. Lets thank the panel (applause).


Send complaints, comments, and corrections to Scott Mitchell.
Final Papers
Back to 5th IMR home page