50 likes | 256 Views
Jessica Leonard 7 Feb. 2008. GREN Analysis Notes. Issue: HCAL Timing. Depending on run, half to most of data not in correct time sample (“sample of interest”) Solution: hack RCT code to loop over all samples in each digi, take the one with highest energy. Issue: RCT isolation.
E N D
Jessica Leonard 7 Feb. 2008 GREN Analysis Notes
Issue: HCAL Timing • Depending on run, half to most of data not in correct time sample (“sample of interest”) • Solution: hack RCT code to loop over all samples in each digi, take the one with highest energy
Issue: RCT isolation • All data candidates are non-isolated, all emulator candidates were isolated: • Reason: EISO ASIC treats threshold of 0 differently from other values • Emulator file updated Entry: 0 (event:67 | run:30205) sys:RCT (2), type:RCT em ... number of candidates: 2 un-matched (2) data: 0x0045, rank=0x05, region=1, card=0, crate=13, iso=0, index=2, bx=0 emul: 0x0045, rank=0x05, region=1, card=0, crate=13, iso=1, index=2, bx=0 data: 0x00d7, rank=0x17, region=1, card=1, crate=17, iso=0, index=3, bx=0 emul: 0x00d7, rank=0x17, region=1, card=1, crate=17, iso=1, index=3, bx=0
Issue: Energy differences • Occasionally see data < emul by 4: • Only happens in Crate 3 – hardware? • To be checked out when we have some rack time • May be causing some candidates to show up in emulator only • Rare differences in other crates: may be due to looking for what we think is correct data? data: 0x0181, rank=0x01, region=0, card=3, crate= 3, iso=0, index=1, bx=0 emul: 0x0185, rank=0x05, region=0, card=3, crate= 3, iso=1, index=1, bx=0