- 07 Jan, 2020 1 commit
-
-
OpenFOAM bot authored
-
- 11 Nov, 2016 2 commits
-
-
Mark Olesen authored
-
Mark Olesen authored
- Cannot test if these older reader modules actually build, owning largely to build issues since with paraview 3.14 (Feb 2012) and paraview 3.98 (Dec 2012) themselves.
-
- 03 Nov, 2016 1 commit
-
-
Mark Olesen authored
Note: classes are prefixed with 'foamVtk' instead of 'vtk' to avoid potential conflicts with VTK itself. foamVtkCore ~~~~~~~~~~~ - General very low-level functionality. foamVtkPTraits ~~~~~~~~~~~~~~ - Traits type of functionality for VTK foamVtkOutputOptions ~~~~~~~~~~~~~~~~~~~~ - The various format output options as a class that can be passed to formatters etc. foamVtkCells ~~~~~~~~~~~~ - Intended for unifying vtkTopo and PV-Reader code in the future. - Handles polyhedron decompose internally etc foamVtkOutput, foamVtkFormatter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Output helpers. - Selector for individual formatters. Currently write all scalar data a 'float' (not 'double'). Can revisit this in the future.
-
- 13 Oct, 2016 1 commit
-
-
Henry Weller authored
For example, to mesh a sphere with a single block the geometry is defined in the blockMeshDict as a searchableSurface: geometry { sphere { type searchableSphere; centre (0 0 0); radius 1; } } The vertices, block topology and curved edges are defined in the usual way, for example v 0.5773502; mv -0.5773502; a 0.7071067; ma -0.7071067; vertices ( ($mv $mv $mv) ( $v $mv $mv) ( $v $v $mv) ($mv $v $mv) ($mv $mv $v) ( $v $mv $v) ( $v $v $v) ($mv $v $v) ); blocks ( hex (0 1 2 3 4 5 6 7) (10 10 10) simpleGrading (1 1 1) ); edges ( arc 0 1 (0 $ma $ma) arc 2 3 (0 $a $ma) arc 6 7 (0 $a $a) arc 4 5 (0 $ma $a) arc 0 3 ($ma 0 $ma) arc 1 2 ($a 0 $ma) arc 5 6 ($a 0 $a) arc 4 7 ($ma 0 $a) arc 0 4 ($ma $ma 0) arc 1 5 ($a $ma 0) arc 2 6 ($a $a 0) arc 3 7 ($ma $a 0) ); which will produce a mesh in which the block edges conform to the sphere but the faces of the block lie somewhere between the original cube and the spherical surface which is a consequence of the edge-based transfinite interpolation. Now the projection of the block faces to the geometry specified above can also be specified: faces ( project (0 4 7 3) sphere project (2 6 5 1) sphere project (1 5 4 0) sphere project (3 7 6 2) sphere project (0 3 2 1) sphere project (4 5 6 7) sphere ); which produces a mesh that actually conforms to the sphere. See OpenFOAM-dev/tutorials/mesh/blockMesh/sphere This functionality is experimental and will undergo further development and generalization in the future to support more complex surfaces, feature edge specification and extraction etc. Please get involved if you would like to see blockMesh become a more flexible block-structured mesher. Henry G. Weller, CFD Direct.
-
- 09 Oct, 2016 1 commit
-
-
Henry Weller authored
-
- 08 Oct, 2016 1 commit
-
-
Henry Weller authored
-
- 22 Nov, 2016 1 commit
-
-
Andrew Heather authored
-
- 08 Nov, 2016 1 commit
-
-
Andrew Heather authored
-
- 05 Oct, 2016 1 commit
-
-
Andrew Heather authored
-
- 30 Sep, 2016 1 commit
-
-
Andrew Heather authored
Note: should be using the result of the parent::read(dict) when deciding whether to read local entries...
-
- 23 Sep, 2016 2 commits
-
-
Andrew Heather authored
-
Andrew Heather authored
-
- 07 Oct, 2016 1 commit
-
-
Mark Olesen authored
- potentially useful for static builds
-
- 04 Oct, 2016 1 commit
-
-
Mark Olesen authored
-
- 20 Sep, 2016 1 commit
-
-
Andrew Heather authored
-
- 24 Aug, 2016 1 commit
-
-
Henry Weller authored
- There will be triangles rendered inside the mesh (when surface-rendering), because one of the cell's triangles is defined as a quadrangle in VTK_WEDGE. - Therefore, this VTK_WEDGE representation is only used when decomposing the mesh, otherwise the correct representation is done by VTK_POLYHEDRON. - Furthermore, using VTK_PYRAMID gave worse result, because it renders 2 triangles inside the mesh for the collapsed quadrangle, likely due to mismatch with the adjacent cell's face. - Using VTK_HEXAHEDRON was not tested in this iteration, given that it should give even worse results, when compared to using VTK_PYRAMID. Patch contributed by Bruno Santos Resolves bug-report http://bugs.openfoam.org/view.php?id=2099
-
- 16 Aug, 2016 1 commit
-
-
Henry Weller authored
Patch contributed by Bruno Santos Resolves bug-report http://bugs.openfoam.org/view.php?id=2192
-
- 05 Aug, 2016 1 commit
-
-
Henry Weller authored
Requires gcc version 4.7 or higher
-
- 24 Jun, 2016 1 commit
-
-
Henry Weller authored
Patch contributed by Mattijs Janssens
-
- 18 May, 2016 1 commit
-
-
Henry Weller authored
-
- 30 Apr, 2016 2 commits
-
-
Henry Weller authored
-
Henry Weller authored
GeometricField: Renamed internalField() -> primitiveField() and dimensionedInternalField() -> internalField() These new names are more consistent and logical because: primitiveField(): primitiveFieldRef(): Provides low-level access to the Field<Type> (primitive field) without dimension or mesh-consistency checking. This should only be used in the low-level functions where dimensional consistency is ensured by careful programming and computational efficiency is paramount. internalField(): internalFieldRef(): Provides access to the DimensionedField<Type, GeoMesh> of values on the internal mesh-type for which the GeometricField is defined and supports dimension and checking and mesh-consistency checking.
-
- 26 Apr, 2016 1 commit
-
-
Henry Weller authored
-
- 25 Apr, 2016 1 commit
-
-
Henry Weller authored
-
- 24 Apr, 2016 1 commit
-
-
Henry Weller authored
-
- 07 Sep, 2016 1 commit
-
-
Andrew Heather authored
-
- 06 Sep, 2016 1 commit
-
-
Mark Olesen authored
- reported by Bruno
-
- 22 Jul, 2016 1 commit
-
-
Andrew Heather authored
-
- 12 Jul, 2016 1 commit
-
-
Mark Olesen authored
- remove old VTK_CONVEX_POINT_SET code, since VTK_POLYHEDRON exists since several years ENH: improve robustness of paraFoam script - only check the relevant plugin types, fallback to native reader if needed/possible.
-
- 20 Jun, 2016 1 commit
-
-
Mark Olesen authored
- more consistent with the rest of the OpenFOAM source tree - improve wmake / wclean behaviour
-
- 17 Jun, 2016 1 commit
-
-
Mark Olesen authored
-
- 16 Jun, 2016 1 commit
-
-
Mark Olesen authored
- although the build is not 100% complete, it is only the run-time post-processing with VTK that is affected. - improve robustness and warning messages COMP: adjust build order (solvers, utilities) - as per http://bugs.openfoam.org/view.php?id=2116
-
- 22 Jun, 2016 1 commit
-
-
Andrew Heather authored
-
- 10 Jun, 2016 2 commits
-
-
Andrew Heather authored
Fixes #99 #121 #127 #128 #138 * -case argument support and nFrames > 1 warning for static mode * viewAngle reset in static camera mode
-
Andrew Heather authored
-
- 26 Apr, 2016 1 commit
-
-
Andrew Heather authored
-
- 22 Apr, 2016 1 commit
-
-
Andrew Heather authored
-
- 21 Apr, 2016 1 commit
-
-
Andrew Heather authored
-
- 25 Apr, 2016 1 commit
-
-
Andrew Heather authored
-