Today is the day we here in the U.S. of A. traditionally set aside to take stock of the good things in our lives and contemplate the essence of gratitude and good fortune.
Oddly, we do this by consuming a gluttonous amount of food and drink and screaming obscenities at our least favorite players in the litany of football games on TV.
As someone who’s worked in the field mesh generation for nearly 30 years, there are a few special things I’d like to give thanks for (before everyone else in the house wakes up and wants to know why I’m hiding in my office).
Things For Which Only a Mesher Would be Thankful
- A CAD file that can imported without failures.
- CAD models that are easier to repair than recreate from scratch.
- Files in the right format that I don’t have to translate.
- Meshing guidelines that help me generate something good, not just something that’s not bad.
- Meshing guidelines of any kind. (Throw us a bone, people.)
- A fully and accurately documented flow solver file format. (“Use the source, Luke” works only in movies.)
- 2D, because making things work in 3D is not an easy extension.
- CFD visualizations, because that’s when we know the mesh worked.
Happy Thanksgiving to all.
“Let us be grateful to the people who make us happy; they are the charming gardeners who make our souls blossom.” ~Marcel Proust
RSS - Posts
4) It’s usually a good idea for the solver guy to provide the meshing guy a table of relevant element quality criteria. Unfortunately, many solvers don’t have all of those documented in 1 place (I cynically suspect this is to support the common, often incorrect, marketing claim that the solver can handle any element you throw at it.)
At my previous job I created an Excel spreadsheet with element quality criteria as I found them, and frequently refer to it.
Thanks, Judah. It’s so helpful to have those guidelines. I get especially frustrated by the “You should know what’s good for me.” reply.