Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N
NIFTy
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 10
    • Merge Requests 10
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ift
  • NIFTy
  • Merge Requests
  • !188

Merged
Opened Aug 17, 2017 by Martin Reinecke@mtrOwner

normalize descent direction for SteepestDescent and VL_BFGS (but not for RelaxedNewton!)

  • Overview 4
  • Commits 5
  • Pipelines 5
  • Changes 1

Following a discussion with Jakob, it appears that the length of the descent direction vector only has real meaning for RelaxedNewton. The other two minimizers can get into trouble (e.g. by going to extreme coordinates and causing overflows) when suplied with very long descent vectors, so I'm normalizing them. A good step length will hopefully be found by the line search algorithm.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
Reference: ift/nifty!188
Source branch: normalize_descent

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.