Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • N NIFTy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ift
  • NIFTy
  • Merge requests
  • !536

Closed
Created Jun 12, 2020 by Lukas Platz@lplatzDeveloper
  • Report abuse
Report abuse

WIP: Catch FloatingPointError exeception in `energy.at` to store crashing position

  • Overview 5
  • Commits 1
  • Pipelines 2
  • Changes 5

Most numerical errors (overflows, divisions by zero, …) with NIFTy occur during minimization runs. Tracking down what caused the fault condition is hard, as the NIFTy minimizers only return positions on non-faulty exits and the exact location of the numerical error has to be reconstructed manually by observing the tracelog.

Typically, the numerical errors occur in the energy functionals to be minimized. Because of this, I propose to augment those to pickle their position on internal crashes.

This will help users in reconstructing the state at crash and in finding the crash reasons.

Edited Jun 24, 2020 by Lukas Platz
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: energy_at_exception