​​ITS3 MOSS testbeam at CERN PS July

​​Documents/Info:

  • ​​[HERE] eudaq2 branch with the MOSS producer + the MOSS_Status
  • ​​addMOSSSTATUS branch
  • ​​

​​Branches

  • ​​EUDAQ2: 
  • ​​Corryvreckan: 
  • ​​Corryvreckan ITS3 Tools: 
​​
​​

​​Status and plans:

​​Todo - Post 25 July WP3 Meeting

  • ​​Try to resolve X vs Y residuals difference
  • ​​ALPIDE residual measurement
  • ​​Residual subtraction (alpides from moss)
  • ​​Review MOSS geometry and corry analysis settings/configs 
  • ​​Need to confirm these are correct!
  • ​​Focus just on Regions 0, 2 for analysis 
  • ​​Region 1 data is not trustworthy due to high beam intensity
  • ​​Need info from design team on differences between regions - this is important to understand how to interpret
  • ​​Jordan’s Thoughts:
  • ​​Include comparison of ALPIDE sensor to MOSS sensor: dimensions, pitch
  • ​​Proposals for MOSS test beam in August
  • ​​Low intensity Region 1 and 3 scans
  • ​​Region 2 above 30
  • ​​Longer runs for “good” VCASB settings? Seems like we need more statistics…

​​Report for Tue 25 July WP3 Meeting:

  • ​​Progress Updates
  • ​​Jordan
  • ​​Region 2 and region 0 StdEvent plots on elog (Region 1 to come soon!) 
  • ​​Got analysis tools installed on Mac (still fixing corry)
  • ​​Guide for installing without using docker:
  • ​​Lukas
  • ​​Cluster size vs VCASB
  • ​​Region 2 best - clear peak at 18-20
  • ​​Region 0 ok - peak at 13?
  • ​​Region 1 inconclusive - what makes it different?
  • ​​Pushed new scripts
  • ​​its-corry-tools > ll scripts
  • ​​Script changes: 
  • ​​must use MOSS_regX_0, 256x256 px
  • ​​set time_cut_abs = 1e99s
  • ​​Goals for next WP3 Meeting:
  • ​​Show current plots that we have