<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear g12,<div class="">had anyone any change to look at this? Furthermore, I see other inconsistencies in the g12 trig table (table 3 in the note). For example, I never see trigger bit 8, that a part from L2, should be the same as trigger bit 1.</div><div class="">I see this effect also in MK thesis (fig. 93 pag 140) - trigger bit 2 is ON for some events, while trigger bit 8 is always OFF.</div><div class=""><br class=""></div><div class="">Thanks</div><div class="">Andrea</div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 14, 2019, at 16:49, Andrea Celentano <<a href="mailto:andrea.celentano@ge.infn.it" class="">andrea.celentano@ge.infn.it</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Dear g12,<br class="">
I am looking at the trigger efficiency of trigger bit #5 (STxTOF x
(ECPx2)). <br class="">
<br class="">
Before doing so, I wanted to do some checks on the way trigger bits
were reported in the output banks. <br class="">
I have taken from tape a single file from run 56541 (file A00), and
I opened it via bosdump, printing HEAD, TGBI and RC26 banks.<br class="">
<br class="">
According to g12 note (table 2 pag. 5), for this run trigger bits
1..6 are MORA x (STxTOF)_i x (STxTOF), without any prescale and
without L2.<br class="">
Trigger bit 8 is MORA x (STxTOF)x2.<br class="">
<br class="">
Therefore, for any event with one of trigger bits 1..6 set, trigger
bit 8 should also be present (for example, if trigger bit 1 is set,
it means that MORA is TRUE, and that there are two sectors with
STxTOF, one of which is sector #1: trigger bit 8 is also satisfied
for this event).<br class="">
<br class="">
However, this is not the case for the events I am scrutinizing. I
report to you some events showing this issue. I also CC this to
Sergey and Ben, so that they can provide further input to the
discussion.<br class="">
<br class="">
<br class="">
<b class="">EVENT:</b><br class="">
Version: 0<br class="">
Run: 56541<br class="">
Event: 858<br class="">
Type: 1 (physics data)<br class="">
ROC: 0<br class="">
CLASS: 14<br class="">
Trgbit: 0x5405 --> bit 1, bit 3, bit 11, bit 13,
bit 15. By the way, what are trigger bit 13 and 15? They are not
reported in table 2.<br class="">
TIME: Thu May 21 18:02:01 2144<br class="">
<br class="">
<b class="">EVENT:</b><br class="">
Version: 0<br class="">
Run: 56541<br class="">
Event: 853<br class="">
Type: 1 (physics data)<br class="">
ROC: 0<br class="">
CLASS: 14<br class="">
Trgbit: 0x8c20 --> bit 6, bit 11, bit 12, bit 16. By
the way, what is trigger bit 16? This is not reported in table 2.<br class="">
TIME: Thu May 21 18:02:01 2144<br class="">
<br class="">
<b class="">EVENT:<br class="">
</b>Version: 0<br class="">
Run: 56541<br class="">
Event: 947<br class="">
Type: 1 (physics data)<br class="">
ROC: 0<br class="">
CLASS: 14<br class="">
Trgbit: 0x5c15 --> bit 1, bit 3, bit 5, bit 11, bit 12,
bit 13, bit 15. By the way, what is trigger bit 15? This is not
reported in table 2.<br class="">
TIME: Thu May 21 18:02:01 2144<b class=""><br class="">
<br class="">
<br class="">
</b>Thanks,<br class="">
Andrea<br class="">
</div>
</div></blockquote></div><br class=""></div></body></html>