STYLE: use autoPtr instead of tmp for holding sensitivities (5e954d28) · Commits · Development / openfoam · GitLab

Skip to content

GitLab

Explore

Sign in
Register

Primary navigation

Project

openfoam
- Activity
- Members
- Labels
- Releases
- Service Desk
- Contributor analytics
- Model experiments

Snippets Groups Projects

Admin message

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.

Admin message

Site will likely be offline for maintenance 14/15 April - more details soon

Development
openfoam
Commits
5e954d28

Commit 5e954d28 authored 4 years ago by

Mark OLESEN

Downloads
- Patches
- Plain Diff

STYLE: use autoPtr instead of tmp for holding sensitivities

- since only pointers are stored, autoPtr is better fit than tmp

parent e2021550

Branches

Tags

Changes 4

Hide whitespace changes

Inline Side-by-side

Showing

src/optimisation/adjointOptimisation/adjoint/solvers/adjointSolvers/adjointSolver/adjointSolver.H 1 addition, 1 deletion

...oint/solvers/adjointSolvers/adjointSolver/adjointSolver.H
src/optimisation/adjointOptimisation/adjoint/solvers/adjointSolvers/incompressible/adjointSimple/adjointSimple.C 6 additions, 6 deletions

...jointSolvers/incompressible/adjointSimple/adjointSimple.C
src/optimisation/adjointOptimisation/adjoint/solvers/adjointSolvers/incompressible/incompressibleAdjointSolver/incompressibleAdjointSolver.C 2 additions, 2 deletions

...incompressibleAdjointSolver/incompressibleAdjointSolver.C
src/optimisation/adjointOptimisation/adjoint/solvers/solver/solver.C 1 addition, 1 deletion

...ation/adjointOptimisation/adjoint/solvers/solver/solver.C

with 10 additions and 10 deletions

0% or .

You are about to add 0 people to the discussion. Proceed with caution.

Finish editing this message first!

Please register or sign in to comment