Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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 68
    • Issues 68
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 41
    • Merge requests 41
  • 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
  • #141

Closed
Open
Created Mar 11, 2022 by Matthias Saimpert@msaimperGuest

Possibility to record average ToT of pixels during source scan

Following the nice discussion we had at the pixel module session this week (*), the point was made by @theim that recording the average ToT during a source scan may allow to identify "half-disconnected" or "fragile" bumps highlighted by crosstalk-based/threshold-based scans but not visible on source scans.

So I open this issue to discuss the possibility to add this in the output of noise scans. Not sure about the technical feasibility of this in terms of FW/SW. IMO ideally it should be off by default but could be turned on by a flag in the scan config.

(*) https://indico.cern.ch/event/1065545/contributions/4762712/attachments/2404768/4113921/RD53A_review_electricalDAQ_20220309.pdf

Assignee
Assign to
Time tracking