Minutes of the Trigger Operation Meeting (Jan.17, 2006)
Attendees: Rainer Bartoldus, Jamie Boyd, Kris Chaisanguanthum, Al Eisner, Fang Fang, Selina Li, Dong Su, Dan Walker
- BaBar has been taking data with lumi ~4-5x10^33 lately. There is a long acess period from Tuesday to Friday (depending on the vacuum leak problem). This is an oppotunity to work on non-colliding-beam related tests.
- Dan and Jamie did the EMT prescale with colliding beam data yesterday during swing shift. The luminosity was low enough that no changes were observed in the deadtime due to EMT when changed the prescale to 3. It remains to be 3 for the rest of the data taking till we get to higher lumi runs at which point we will repeat the tests to get the most optimal points for reducing deadtime. Rainer suggested to create some physics keys with different prescale factors so that the pilots can easily change the prescale as requested. Currently, the prescale for calibration remains to be 1. We looked at a few plots. Jamie pointed out that the L1Ntuple needs to be updated to use the prescale bit.
- Jamie showed some of the things that can be improved for DCZ. The TSF LUT can be improved.
- The TSF input data is the biggest, and could be prescaled or compressed. However, currently the ZPD hasn't showed up as a big contributor to the deadtime yet probably because FEX is fast.
- Marc will continue working on the TSF firmware issues.
- Last Sunday morning, there were synchRequest errors in the DCZ crate. It turned out to be TSF-X, as shown in the rom logfile. According to Jamie, these are dataflow error messages indicating real fundamental problems. Other detector subsytems should also see the same problem unless it's a problem with the DCC for the TSF-X crate.
- After removing the test stand dependency, the DCZ online library .o file is half of the size as before the removal.
- Rainer suggested that the DCT calibration should use the same library as in data-taking if we decide to put the DCT calibration in run control.
This page is created by Selina Li (email@example.com); however, you are welcome to edit and/or correct above items, specially for those who attended the meeting. Thanks.