1 / 9

Friday Oct 30

Some of the last runs …. 137322 Data09_calophys. 137441 Data09_calophys. 137158 Data09_cos. 137394+137395 Data09_cos. 137347 Data09_calophys. Friday Oct 30. Monday Nov 2. Events ending up in the debug stream, go through reprocessing with trigger offline.

vera
Download Presentation

Friday Oct 30

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Some of the last runs …. 137322 Data09_calophys 137441 Data09_calophys 137158 Data09_cos 137394+137395 Data09_cos 137347 Data09_calophys Friday Oct 30 Monday Nov 2

  2. Events ending up in the debug stream, go through reprocessing with trigger offline

  3. L2FA can be a crash or a timeout at L2. It can happen at any step, so you can have had FEXes executed - however there is no L2 result usually so we always reprocess the event offline to see anything. It's actually not easy distinguishing if it was a crash or a timeout...

  4. EF has timed out. The action taken then is that the event simply goes to debug stream, and then we reprocess with longer time offline. If the event takes "too" long (>30 mins) offline, then we should abort it offline and see where the timeout was.

  5. These are cases where a PT (EF)  crashed

  6. These events are force accepted without processing to accomplish STOP transition before the Run Control timeout expires. when the Run Control is about to go to STOP, doesn't know what to do with the events buffered and just force accepts all of them . So in fact the events in StopTransition are at the end of the run, at a large lumiblock number.

  7. From denis: FEBs kept off until collissions, see bottom right plot.

  8. Rum meeting , 9:30 am Nothing interesting for trigger. We keep with calophys mode and combined run. Today some SCT test. TRT is off for part of the day (problem HV?) Slice meeting, 3:00 pm Asked to ask trigger shifter at desk to write specific slice messages using the Trigger->trigger group->tau message type. Not sure it will be followed (hard for Shifter to guess at times, says Cristobal) Discussion about DQ flags. Sidoti will meet with me and Mansoora Wednesday After the slice meeting, and discuss how DQ flag can be overruled by expert, and also how current histograms suite the auto DQ flag settings. Cristobal wants to have machinery in place, although value of flag will be ignored wrt reprocessing at Tier0 of events. But we should make simple and sensible choice of histos to define DQ flag online. See talk of Mansoora, I think we have an idea. We should also polish our monitoring: more directive, now it is mainly descriptive (Cristobal).

  9. Updated both https://twiki.cern.ch/twiki/bin/view/Atlas/TauTriggerCommissioning and https://twiki.cern.ch/twiki/bin/view/Atlas/TauTriggerCommissioningShift Please, next expert shifter, read carefully these two pages before starting your shift. Notify me and Olya if information is wrong/missing/whatever, before changing it Yourself. Updated also https://twiki.cern.ch/twiki/bin/view/Atlas/TauTriggerGoodRuns2009 Adding now pdf with quick look at online histos, and mantaining list of hot towers appearing at L1

More Related