From AtlasID to ROBID
Atlas ID StName/StEta/StPhi/DoubletR/DoubletZ/Doubl etPhi/GasGap/MeasuresPhi/strip I primi 4 identificano la collezione offline (da utilizzare per ottenere lhashID) –St. Eta ( da -8 a +8) Serve solo il segno per capire il Side A (+) e side C (-) –St. Name (BOL,BML,BOS,BMS,etc..) –St. Phi (da 1 a 8) –DoubletPhi (equivalente a HV RO sulle stazioni a muoni) Servono per stabilire il settore di trigger e quindi il ROD –Doublet R è ininfluente nella selezione del ROB ID
Settori di Trigger e Station Phi View from side C to Side A Station Phi = 1 Station Phi = 2
Atlas ID Sign (St.Eta)St. PhiSt. NameDbl PhiROD IDROB ID 1BML/BOL1150x66000f 1BML/BOL200x BMS/BOS100x BMS/BOS210x BML/BOS110x BML/BOS220x BMS/BOS120x BMS/BOS230x BML/BOS130x BML/BOS240x BMS/BOS140x660004
Atlas ID La tabella ha 64 entries Possible o una lookup-table o un algoritmo Utilizzando solo StName/StEta/StPhi dunque, si possono ottenere 2 ROBID differenti. Solo utilizzando anche dblPhi si ottiene un ROBID univoco.
Error Handling in Online RPCDecoding
Possible data fragment errors NO_RX_FRAG –No Rx frag inside ROD frag. Skipping event BAD_RX_FRAG –Rx frag is corrupted. Skipping rx frag NO_PAD_FRAG –No PAD frag inside Rx frag. Skipping BAD_PAD_FRAG –PAD frag is corrupted. Skipping pad frag NO_CM_FRAG –No CM frag inside PAD frag. Skipping BAD_CM_FRAG –CM frag is corrupted. Skipping CM frag
Still missing Too long events are truncated by ROD and flagged. –No reaction by Decoder, also good subfragments rejected. No check of error words inside the fragments footer. –Only stored in the containers without any reaction.