Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • YARR YARR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 67
    • Issues 67
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 45
    • Merge requests 45
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • YARR
  • YARRYARR
  • Issues
  • #39

Closed
Open
Created Mar 27, 2020 by Bruce Joseph Gallop@bgallopMaintainer

Use of type_index for LoopAction type discovery

When sending to remote machines we can't rely on std::type_index having the same representation.

This is a problem for LoopActionBase::type (and c another issue).

In LoopAction the type is mostly used to decide how to build histograms:

  • Events from one cycle of a trigger loop go into the same bin
  • Events from one cycle of a mask loop go into the same bin
  • Events from each step of a threshold loop go into different
  • Something else?

Also some discussion here: atlas-itk/sw/itksw-design#1

Assignee
Assign to
Time tracking