Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S src
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Issues
  • #611

Closed
Open
Created Oct 06, 2020 by gsell@gsellOwner

fix floating point comparisons in BoundaryGeometry

Summary

Under certain conditions the line-segment triangle intersection test fails due to incorrect usage of floating point comparisons.

Steps to reproduce

Run simulation with the following input files:

  • SAAMG-BeamPipe.in
  • Pipe_1m_10cm.h5

What is the current bug behavior?

If a line-segment intersects with a triangle on or very close to an edge, the intersection is not found.

Possible fixes

Use a proper algorithm to compare floating point numbers.

Edited Oct 06, 2020 by gsell
Assignee
Assign to
Time tracking