Skip to content
Snippets Groups Projects

Remove sTGC hits with negative calibrated charge

Merged Chav Chhiv Chau requested to merge chchau/athena:removeNegCharge into 22.0
All threads resolved!

sTGC calibrated charge in data may become negative due to the lack of proper calibration constants. The negative charges are removed to prevent errors downstream. They represent a small fraction of hits that have low deposited energy, so discarding them would have a negligible impact. With proper calibration, all charge values should be positive.

This merge request targets ATLASRECTS-714, restoring some changes by @sangelid to protect against corrupted data !55062 (closed). Tagging also @pscholer, @jojungge, @rosati

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Let me also inform @nstyles, @elmsheus, @mhodgkin, @goetz, @pberta, @jmaurer that this MR will potentially violate the frozen-tier0-violating policy. The changes are necessary as the information from the chips is complete gabarge and should be vetoed from the reconstruction.

  • Johannes Junggeburth resolved all threads

    resolved all threads

  • added 1 commit

    Compare with previous version

  • This merge request affects 2 packages:

    • MuonSpectrometer/MuonCnv/MuonMM_CnvTools
    • MuonSpectrometer/MuonCnv/MuonSTGC_CnvTools

    Affected files list will not be printed in this case

    Adding @rosati ,@wleight ,@stavrop ,@jojungge ,@apsallid ,@pscholer as watchers

  • I am confused by the description and statements. The original description says the issue is some hits have -ve charge and that should not be used. It also says the cause is a lack of proper calibration. Then @jojungge says the information is garbage, but that sounds quite different from not properly calibrated. Or are there are two different issues being solved here?

    For the calibration issue would we eventually have a proper calibration that means we will never see these -ve charge hits?

    Unless its super urgent, we could discuss this with everyone in next weeks RIG.

    Cheers,

    Mark

    Edited by Mark Hodgkinson
  • :white_check_mark: CI Result SUCCESS (hash fc2a77d5)

    Athena DetCommon
    externals :white_check_mark: :white_check_mark:
    cmake :white_check_mark: :white_check_mark:
    make :white_check_mark: :white_check_mark:
    required tests :white_check_mark: :white_check_mark:
    optional tests :white_check_mark: :white_check_mark:

    Full details available on this CI monitor view. Check the JIRA CI status board for known problems
    :white_check_mark: Athena: number of compilation errors 0, warnings 0
    :white_check_mark: DetCommon: number of compilation errors 0, warnings 0
    :pencil: For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 56989]

  • Please resolve open threads (L1).

  • Chav Chhiv Chau mentioned in merge request !55126 (closed)

    mentioned in merge request !55126 (closed)

  • added 1 commit

    • ec2ea7b2 - Print a warning message per rdo collection

    Compare with previous version

  • This merge request affects 2 packages:

    • MuonSpectrometer/MuonCnv/MuonMM_CnvTools
    • MuonSpectrometer/MuonCnv/MuonSTGC_CnvTools

    Affected files list will not be printed in this case

    Adding @rosati ,@wleight ,@stavrop ,@jojungge ,@apsallid ,@pscholer as watchers

  • Chav Chhiv Chau resolved all threads

    resolved all threads

  • Author Contributor

    The conversion between charge and ADC counts is linear. The hits with low ADC counts (some have zero count) are shifted to the negative region. I looked at some data files that include sTGC. The part in the negative region is a small fraction and looks like noise, as shown below. So it is likely garbage. The detector is being commissioned, therefore the calibration that should be done per readout channel is not yet available. stgc_negative_calibrated_charge

  • Hi, just to confirm that is fine to remove hits with negative charge (caused by temporarily improper calibration as normal with a detector being commissioned): this modification will cause no relevant change in the reconstruction, as we already discussed in the NSW community. In any case hits with negative charge should not be used in the reco, the negligible fraction that we have now is coming, as Chav already wrote, from temporary calibrations (so it is not exactly garbage but we should not use them in the reconstruction if not yet properly calibrated). thanks, cheers, Stefano

  • Julien Maurer resolved all threads

    resolved all threads

  • :white_check_mark: CI Result SUCCESS (hash ec2ea7b2)

    Athena DetCommon
    externals :white_check_mark: :white_check_mark:
    cmake :white_check_mark: :white_check_mark:
    make :white_check_mark: :white_check_mark:
    required tests :white_check_mark: :white_check_mark:
    optional tests :white_check_mark: :white_check_mark:

    Full details available on this CI monitor view. Check the JIRA CI status board for known problems
    :white_check_mark: Athena: number of compilation errors 0, warnings 0
    :white_check_mark: DetCommon: number of compilation errors 0, warnings 0
    :pencil: For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 57016]

  • Approving - Oleh L1

  • Peter Berta mentioned in commit 5438a883

    mentioned in commit 5438a883

  • merged

  • Please register or sign in to reply
    Loading