- 13 Nov, 2020 1 commit
-
-
Mark Olesen authored
- fixed indexing error (crashes under windows). No crash but still incorrect on other systems
-
- 10 Jun, 2020 1 commit
-
-
mattijs authored
-
- 31 Oct, 2019 1 commit
-
-
OpenFOAM bot authored
-
- 06 Feb, 2019 1 commit
-
-
OpenFOAM bot authored
-
- 11 Dec, 2018 1 commit
-
-
Mark Olesen authored
- makes the intent clearer and avoids the need for additional constructor casting. Eg, labelList(10, Zero) vs. labelList(10, 0) scalarField(10, Zero) vs. scalarField(10, scalar(0)) vectorField(10, Zero) vs. vectorField(10, vector::zero)
-
- 26 Nov, 2018 1 commit
-
-
mattijs authored
-
- 27 Sep, 2018 1 commit
-
-
Mark Olesen authored
- nBoundaryFaces() is often used and is identical to (nFaces() - nInternalFaces()). - forward the mesh nInternalFaces() and nBoundaryFaces() to polyBoundaryMesh as nFaces() and start() respectively, for use when operating on a polyBoundaryMesh. STYLE: - use identity() function with starting offset when creating boundary maps. labelList map ( identity(mesh.nBoundaryFaces(), mesh.nInternalFaces()) ); vs. labelList map(mesh.nBoundaryFaces()); forAll(map, i) { map[i] = mesh.nInternalFaces() + i; }
-
- 23 Apr, 2018 1 commit
-
-
Mark Olesen authored
- in 2.4.x the general default for polyMesh::findCell was FACE_DIAG_TRIS, but this was changed to CELL_TETS for better handling of concave cells. - in snappyHexMesh meshRefinement, findCell is used to define locations in mesh and cells for closer refinement. Using CELL_TETS causes an octree rebuild when the mesh has changed and this adds considerable overhead. For this operation, the faster FACE_DIAG_TRIS mode can be used instead.
-
- 28 Mar, 2018 1 commit
-
-
Andrew Heather authored
-
- 19 Nov, 2017 1 commit
-
-
Mark Olesen authored
-
- 21 Jul, 2017 1 commit
-
-
Mark Olesen authored
- this represents a partial revert for commit 6a0a8b99
-
- 04 Jul, 2017 1 commit
-
-
Mark Olesen authored
ENH: add degToRad() multiplier (useful for scalar fields) - use degToRad() functions throughout instead of scattered local solutions
-
- 25 Apr, 2016 2 commits
-
-
Andrew Heather authored
-
-
- 06 Jan, 2016 1 commit
-
- 10 Dec, 2015 1 commit
-
-
mattijs authored
-
- 08 Dec, 2015 1 commit
-
-
Andrew Heather authored
-
- 28 Oct, 2015 4 commits
-
-
mattijs authored
- shoot rays to nearest point on surface and two perpendicular rays (instead of always shooting in the 3 coordinate directions) - avoid bleeding through the surface intersection
-
mattijs authored
-
mattijs authored
1. multi-ray shooting. It now shoots rays in all the 3 coordinate directions from the cell centre. Before it would shoot just a single ray from the nearest point on the surface, going through the cell centre. There is a cost overhead in that now it shoots 6 rays (+-x, +-y, +-z) instead of just 1. 2. bleeding of refinement. It marks the cells inside a gap and walks out the gap-size to neighbouring cells (which are just outside the gap). This should make for a smoother refinement pattern.
-
mattijs authored
-