INTT Weekly meeting

US/Eastern
    • 20:00 20:20
      Hit Carryover: Updates on offline analysis 20m
      Speaker: Ryotaro Koike
      [Ryotaro: Hit Carryover: Updates on offline analysis]
      - An ill filter was in a private analysis code but not in the default code.
      - Recovering process will not require bco_diff peak.
      - Black points are completely same as blue points. Need to fix and update the plot.
      - To make ratio between blue and black points, you can try 25 (or 30)<BCO<80 to check the ratio become flat or not.
      -- If it become flat, we can cut the small interval region. It is better than the overcorrection.
      - Normalization factors for blue and black points are different but the procedure to estimate the factors is same.
      - In slide 7, still not sure about the cause of the distinctive structure.
      - The carryover hits include hits from other crossings.
      - What is the rate of this data?
      -- Try to check multiple runs with different rate. Maybe several runs from one good store.
       
    • 20:20 20:40
      INTT commissioning for pp run 20m
      Speaker: Yuko Sekiguchi (RIKEN)
      [Yuko: INTT commissioning for pp run]
      - The pp commissioning data were taken in the local mode.
      - About the problematic 3 ladders on INTT2, talked to Rachid and decided to leave it for now to see if the condition get better tomorrow.
      - We won't have a chance to access to the bore.
      - The right plot in slide 3 shows data before masking.
      -- 3 hot chips may cause the other chips empty. Worth trying to mask after checking status tomorrow.
      - INTT2 server's high temp issue should be irrelevant to the crazy hot chip issue.
      - We can increase the threshold only for crazy hot chips but need to communicate with the chips at least.
      -- Do we have a script to change the threshold only for some particular chips?
      -- So far we have only used one threshold for all chips, and masked chip is it is so noisy to cause DAQ issue.
      - INTT local team will investigate and decide how to avoid the noisy chips tomorrow morning.
      - One possibility of INTT2 issue is one of the optical driver is dying.
      -- List up all of the possibilities.
      -- Suspect that the FPGA or optical driver is not getting enough voltage.
      -- Increasing the voltage for FPGA or optical driver is impossible because those are after regulators.
      -- Worth trying to swap cables at Felix side?
      - Timing alignment between all INTT servers need to be checked.
    • 20:40 21:00
      Plot preparation for INTT Barrel NIM 20m
      Speaker: Cheng-Wei Shih (National Central University)

        [Cheng-Wei: Plot preparation for INTT Barrel NIM]

      - The collision data doesn't have radial restriction, which must have a bigger errors.
      -- It would be nice to have cosmic data with millipede to have additional constraint.
      - Radial shift from the geometrical calibration using collision data is not so accurate, so you can remove radial direction vectors, then show shifts only circular direction.
      - For the bco peak study, please double check it by removing some problematic ladder which show some periodic spike other than the collision peak.
      - An editorial meeting will be held next week. Plot to be prepared in December. Rachid already wrote his part.
    • 21:00 21:20
      Streaming Offline Timing QA Summary 20m
      Speaker: Joseph Bertaux (staff@purdue.edu;student@purdue.edu;member@purdue.edu;employee@purdue.edu)
    • 21:20 21:23
      APR 3m
      Speaker: Yuko Sekiguchi (RIKEN)