AMS offline software progress report.

1. AMS offline software progress report. E.Choumilov, AMS TIM 23.04.07

2. Introduction. Most of the software changes are connected with real data decoding section of the offline program. The processing of SOC-stored real data files is performed using some common interface plus detector-oriented functions (each sub-detector have to supply the set of standard functions like XXX::checkblockid(id), XXX::buildraw(len,*p), XXX::getmaxblocks() and some others). This interface was developed by V.Choutko for AMS-01 and with some minor (?) changes could be used for AMS-02 (V.Choutko will make the final updates as soon as the final DAQ-event format will be ready and officially released (by A.Kounin ?)). It would be very useful for sub-detector software writers to have the detailed block-diagram of this interface logic from V.Choutko as soon as possible. To my mind it is high time to start writing of at least preliminary versions of decoding functions for all sub-detectors (working online with “on-board” software writers). The electronics system tests and even beam tests are in progress already and we have to be prepared for decoding software debugging quite soon (autumn is too optimistic ?). The list of responsible persons for every sub-detector must be established.

3. ECAL software. DAQ-section: • Addressing scheme of EDR/ETRG boards in crate is set according to the • latest specifications (from Stefano di Falco). Double redundancy is taken • into account by doubling the number of legal addresses in the crate list. • EDR/ETRG cabling scheme is implemented. It establish one-to-one • correspondence between the hardware and software addresses of • every readout channel. Address (channel_id) description: • hw_id -> CSSRRR (Crate/Slot/Readout_channel), • sw_id -> LTTPG (superLayer/Tube(pmt)/Pixel/Gain). • The set of the functions for hw_id <-> sw_id translations is developed to • be used for decoding and reconstruction of real data. See more details in • ecid.C(h) files. • 3) The preliminary version of decoding program for raw and compressed • formats was written. Here and below the decoding means not only • unpacking and regrouping of the original data but also necessary • hw_id to sw_id translations plus low level reconstructed objects creation. • Wait for final EC/electronics/on_board_software tests and documentation • to complete the job. See more details in daqecblock.C(h) files, preparation • of detailed documentation is foreseen.

4. Calibration-section: It is implied now that in compressed data format (bulk DAQ-mode) the ADC- count values passed through the on-board compression (“0”s reduction algorithm) are not pedestal-subtracted. The pedestals subtraction and the final “0”s suppression are done in offline program using either “on-board” measured ped/rms tables (clock trigger) or/and offline calculated ped/rms, based on so-called “downscaled” events (according to Stefano di Falco). These events are ~1/1000 of normal (in trigger) ones but transmitted without “0”s suppression by on-board procedure (means all channels of given EDR are present). Because really fired is only the part of the EC-cells (depending on the energy and the trigger type) the rest is supposed to contain the “pedestals” values. The obvious problem of pedestal tails have to be solved. Taking into account the above considerations the currently developed and MC-tested pedestals manipulation procedure includes 2 main modes: a) Scanning of SOC-stored DAQ-files and selection of all “on-board” created ped/rms tables, checking their quality, storing them in standard files and in DB. b) Scanning of DAQ-files, selection of empty (“pedestal”) cells in “downscaled” events (one EDR per event ?) and storing cells ADC-counts in the accumulation

5. arrays. At the end of the scan the ped/rms values are calculated, checked and stored in standard files and DB (crosscheck with “on-board” tables for the same period have to be done). The empty (“pedestal”) cell selection algorithm used isolation criteria (no fired neighbour in the same super layer) combined with rejection procedure of right-tail events (removal of some percentage of highest values (truncated mean method)). Typical result is shown on fig.1 (all calculations were done using the adc-values accumulated in the fixed (+/- 3 rms) window based on preliminary defined (on the small subset of data) mean pedestal and rms values). That “subset” procedure also used truncated mean calculation method. More details in ecalcalib.C(h) files. Above procedure have to be finally tuned and tested using the real data.

7. Missing 1st priority items (also valid for other sub-detectors) : • ECAL slow control data handling (documentation on data format + volunteer • from ECAL group with ideas on what and how to use …). • some (semi-)automatic stand-alone procedure which during the data taking • (beam tests, on-earth cosmic tests, in space) search for new pedestals • files of different kinds, check/compare (if there are two for the same period) • their quality and write the best (or combined) ones to DB . • 3) Other proposals are welcome !..

8. TOF/ANTI software. DAQ-section: • Addressing scheme for SFET/SFEA/SFEC/SPT boards in crate is set according • to existing specifications. Double redundancy is taken into account. • SFET/SFEA/SFEC cabling scheme is implemented. SPT board registers • bit-to-channel map have to be modified according to new scheme (have to be • supplied by A.Basili). • The cabling scheme establish one-to-one correspondence between the • hardware and software addresses of every readout channel. • Address (channel_id) description: • hw_id -> CSSRR (Crate/Slot/Readout_channel), • sw_id -> LBBSPM for TOF, BSPM for ANTI. Here L – for Layer, BB – for • scintillator bar number, S – for Side, P – for PMT numbers within one side • (1 anode, up to 3 dynodes, M – for measurement type: LT_Time/Charge/ • FT_Time/SumHT_Time/SumSHT_Time. The set of the functions for • hw_id <-> sw_id translations is modified according to new specifications. See • more details in tofid.C(h) files. • 3) The preliminary version of decoding program for raw format is written. • For compressed format – is under development (working online with A.Kunin who

9. is writing on-board software. The TOF/ANTI-boards temperature data decoding is written (not final – need exact algorithm for temperature calculation using two encoded values (scale factors, offsets ???), the ideas how to use it for practical corrections is also missing – need input from TOF-group hardware experts…) More details in daqs2block.C(h) files. Calibration-section: For the moment TOF/ANTI pedestals manipulation scheme is similar to ECAL one (but the isolation criterion is not used). The final logic have to be reviewed according to “on-board” software logic which is under development (by A.Kunin). My proposal is to use the same “no ped-subtraction on board” feature as for ECAL. Plus “no ped-suppression” for ANTI (for SFEA board charge-data) as was requested some time ago by ANTI-counter group (W.Wallraff). More details in tofcalib02.C(h) files. Level-1 software. The DAQ-format decoding program is under construction (most of the tools and skeleton are ready). Need final format specifications from “on-boards” software writers. The already existing simulation and reconstruction parts are unchanged.

10. Here is the list of missing (partly or completely) decoding software sorted by related sub-detectors names. The decoding software writers have to be provided by group leaders as soon as possible. TOF : E.Choumilov, A.Basili, need more peoples from TOF-detector group ! ANTI : E.Choumilov, A.Basili, …………………………… ANTI………………. Tracker : V.Choutko (?), ……………………………………Tracker …………… TRD : ??? ECAL : E.Choumilov, Stefano di Falco, ………………… ECAL …………….. RICH : ??? StarTrk : ??? Magnet : ??? DAQ-files reading (interface) : V.Choutko GPS : ??? PS. Almost weekly changes in decoding software (no stable documentation = work online with on-board software writers) prevent me from official release. Who want to study all mentioned files – see /f2users/choumilo/AMS/CC(include, doc,…).