|
|
| Reporter | rperry | Assigned To | user4 | |
|---|
| Priority | normal | Severity | minor | Reproducibility | always |
|---|
| Status | resolved | Resolution | fixed | |
|---|
| Platform | Suse enterprise 10 | OS | Other | OS Version | (please specify) |
|---|
|
|
| Summary | 0000825: snappyHexMesh checkMesh -meshQuality flag does not work for skewness limits |
|---|
| Description | This was pointed out during the Friday session of the users conference:
When running checkMesh with the -meshQuality flag for user defined mesh quality, ZERO cells are marked as violating the boundary or internal skew limits, even when the standard checkMesh output shows cells which definitely are above this limit. |
|---|
| Steps To Reproduce | Simply run checkMesh on any case with the -meshQuality flag, and set the skew limits in meshQualityDict to be lower than the known maximum skew. The first run of checkMesh will report the correct max skew and number of violating elements, and the second run on the custom criteria will not. |
|---|
| Tags | checkMesh, snappyHexMesh |
|---|
|
|
