Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bliss bliss
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 542
    • Issues 542
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 143
    • Merge requests 143
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • BlissBliss
  • blissbliss
  • Issues
  • #2744
Closed
Open
Issue created May 04, 2021 by Perceval Guillou@pguillouOwner

Roi counters validity

Check that the coordinates of a roi (rect, arc, profile) is valid compare to the current detector size/geo.

Store in settings the raw_roi instead of the current_roi to treat roi validity correctly (raw_roi is a invariant).

Discard unvalid rois.

Recompute rois after a modification of the detector geometry.

closes #1774 (closed) #2727 (closed)

Edited May 04, 2021 by Perceval Guillou
Assignee
Assign to
Time tracking