INTT Weekly meeting

US/Eastern
Description


 INTT Mapping Code Change Updates: Joseph
  - Two ch-mapping codes
    - InttFelixMap and InttMapping are kept.
    - InttFeeMap and InttMap are removed
       - These codes access CDB
         but the ch-mapping is the same during sPHENIX running.
  - checking the Jenkins test in GitHub
    - Strange behavior found.  Joseph creates the testing code
      to verify the consistency of INTT-related variables.


 Beam Test analysis: ChengWei

  - Discussed about DAC scan
  - Baseline normalization method was changed to 6th bin method
  - L1 data issue (10 times more data than L0 and L2)
     - L1 Hitmap looks OK therefore L1 scan data was included in the analysis
     - Is it OK to use or not to use?

  - How do we show the MIP distribution in the paper
     - CW proposed not to show the MIP peak position and S/N value.
       -> Genki had a concern about this proposal (not to show the S/N).
          will make additional comments by e-mail.

     - YA recommended to show these values with an explanation about the concerns of 50V bias voltage.
       50V was not enough to have full depletion.
       This would be good to keep our record and avoid future misunderstandings.
       We agreed to show the MIP value and its energy deposit or Nelectrons.

  - Noise level
     - YA proposed to use the calibration data to see the noise level.
       CW will talk with YA offline

  - What we agreed during the meeting
    - Normalisatin method: 6th bin method instead of 6+7th bin method.
     - Fitting function should cover the full range of DAC histogram (not just MIP region)
     - The single ladder method (current method) is used to make DAC histogram.
        - Tracking method can nicely reduce the noise, but we are concerned that the different thresholds may cause unrecognised bias
     - Systematic uncertainty on the different normalization methods is not employed because no other method is reliable for comparison.
     - Systematic uncertainty on the ladder by ladder variations needs to be taken

  - We will have a special Beam Test meeting early next week (Monday is likely)
     - The discussion was cut by the time the pre-GM meeting started.
       Need to continue it.

********
  - The analysis is almost final, so if you have any comments, please send it to the list in one week.
********

There are minutes attached to this event. Show them.