Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 381
    • Issues 381
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1540

Closed
Open
Created Jan 02, 2020 by Vaggelis Papoutsis@vaggelispDeveloper

BUG: continuation of updateMethods with empty activeDesignVariables

Summary

When activeDesignVariables are not set explicitly, all design variables are treated as active. These are allocated properly when starting from 0 but not when starting from an intermediate optimisation cycle (e.g. running 5 optimisation cycles, stopping and restarting). The bug affects the BFGS, DBFGS, LBFGS, SR1, SQP and conjugateGradient updateMethods.

Steps to reproduce

  1. Copy an optimisation case using BFGS, say $FOAM_TUTORIALS/incompressible/adjointOptimisationFoam/shapeOptimisation/sbend/turbulent/opt/BFGS/op1
  2. Comment out the activeDesignVariables in optimisationDict.
  3. Run for a number of optimisation cycles using adjointOptimisationFoam, say 5.
  4. Change the endTime to 10, to run another 5 optimisation cycles and re-run adjointOptimisationFoam. The solver will crash upon trying to compute the update of the design variables since the activeDesignVariables list will be empty.
Assignee
Assign to
Time tracking