blockMesh: most mesh data are now demand-driven (897baf81) · Commits · Development / openfoam

Snippets Groups Projects

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Site will likely be offline for maintenance 27/28 March - more details soon

Commit 897baf81 authored 15 years ago by

Mark Olesen

Browse files

blockMesh: most mesh data are now demand-driven

- Unless the points(), cells(), patches() methods are called, the classes
  should know maintain a lightweight representation for as long as possible.

- bugfix: old-code used xferMove() instead of xferCopy() when creating the
  topology mesh - causing const pointField& to break if the code order was
  changed

- relocate blockMesh from src/meshing -> src/mesh

parent c2ad2d1b

Branches

Admin message

Admin message

blockMesh: most mesh data are now demand-driven