1 / 8

From AtlasID to ROBID

From AtlasID to ROBID. Atlas ID. StName/StEta/StPhi/DoubletR /DoubletZ/DoubletPhi/GasGap/MeasuresPhi/strip I primi 4 identificano la collezione offline (da utilizzare per ottenere l’hashID) St. Eta ( da -8 a +8) Serve solo il segno per capire il Side A (+) e side C (-)

maegan
Download Presentation

From AtlasID to ROBID

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. From AtlasID to ROBID

  2. Atlas ID • StName/StEta/StPhi/DoubletR/DoubletZ/DoubletPhi/GasGap/MeasuresPhi/strip • I primi 4 identificano la collezione offline (da utilizzare per ottenere l’hashID) • 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

  3. Settori di Trigger e Station Phi • View from side C to Side A Station Phi = 2 Station Phi = 1

  4. Atlas ID

  5. 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.

  6. Error Handling in Online RPCDecoding

  7. 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

  8. 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.

More Related