Skip to content
wyldckat edited this page Jan 14, 2014 · 12 revisions

Table of Contents

Introduction

On this page we would like to collect various tips and tricks about enGrid.

Contributions from users are explicitly encouraged! If you have solved an annoying problem, it would be great if you could take a few minutes and write it down here.

Installation Related

Reset Configuration Settings

A new version of enGrid often requires different settings than the previous version. The default behaviour is that the existing settings are kept if a new version is installed. Not only might this lead to unexpected results, it also clutters your settings window with obsolete configuration options.

On a Linux system the settings are stored in the following file ".config/enGits/enGrid.conf" relative to the user's home directory. If this file is deleted or moved, enGrid will create a new file with the default values of the installed version.

It would be great, if someone could shed some light on how to achieve the same thing on Windows or MacOS.

Workarounds for Bugs and Other Misbehaviour

Illegal state observed in swapimprove ...

Sometimes a window might pop-up which reports an error inside the Netgen library. The reason for this happening is not entirely clear; it could be a bug in Netgen or a somewhat defect surface mesh. In many cases, however, it helps to let the surface mesher run for a few more iterations and then try again to create the volume grid.

Bug in guidivideboundarylayer.cpp:125

If you get the following message while trying to divide the boundary layer, you might have to call create/improve volume mesh before.

Not possible to project point, when creating prismatic boundary layer

Diagnostic:

  1. The error message box stating that a bug exists in surfaceprojection.cpp, line 242.
  2. The error message No projection found for point, id_node= 12345 , xp= nan nan nan (12345 is just an example) is shown on the console/command line with the error output.
Reason: This can occur when a patch with prismatic layer is co-planar or oblique to another patch that does not have the prismatic layer. The result is that the points between the two patches will attempt to project onto the patch that does not have a prismatic layer, leading to a failed projection, since it's beyond sight.

Solution: Assign a prismatic layer to the other patch as well.