1 / 15

Offline software development status.

Offline software development status. E.Choumilov, TIM 18.07.2009. ECAL:. Now MC Geant-hits can be written to root-file (new data card ECMC 30=(0)), related codes are written and tested (be careful – very high hits multiplicity,

teresa
Download Presentation

Offline software development status.

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. Offline software development status. E.Choumilov, TIM 18.07.2009.

  2. ECAL: • Now MC Geant-hits can be written to root-file (new data card ECMC 30=(0)), • related codes are written and tested (be careful – very high hits multiplicity, • set ECMC 30=1 to let hits writing to root-file when IOPA 43 set to “write all”, • SET 30=2 to force writing at any conditions. • “On-Board” pedestals handling codes are modified according new format • (very preliminary, not tested on real data). New data card ECCA 75=(15) • is the bit-pattern describing the final content of pedestals block (A-peds, • D-peds, Thresholds, PedWidth). • Geometry is modified according to the latest beam test results (super layers • misalignment is added, lower pixel response in pixel-to-pixel transitional • area (+-3mm around pixel boundary) is introduced (40% signal reduction • at the boundary point).

  3. TOF/ACC: • “On-Board” pedestals handling codes are updated (still preliminary, not • tested on real data). New data card TFCA 40=(63) is the bit-pattern • describing the final content of pedestals block (A-peds, D-peds, • PreTrigWords, StatusWords, Thresholds, PedWidth). • Common for all sub-detectors data card CALIB 3=ijklm is decimal “bit-pattern” of sub-detectors to be used in automatic update of DB. Default • ijklm=11111 (use all sub-detectors), see datacards.doc file for more details. • TOF offline calibrations codes are modified to work with “Tof Calibration • Commander” program (“summary”-block is added in log-file). • ACC dE/dX channels saturation treatment is added (not final, need • more information from ACC-group for better accuracy, currently unique • nonlinearity curve is used). Data card ATRE 6=(0) is introduced, set it • to 1 to apply corrections to raw amplitudes. In any case these corrections • are non very important because do not affect ACC-efficiency. See also • fig.1-3 for illustration. • 4. Preliminary version of TOF Calibration Commander is released.

  4. Fig.1 (light output <=> impact point)

  5. Fig.2 (no corrections)

  6. Fig.3 (with corrections)

  7. TOF Calibration Commander features • This is the graphic interface between the user and different TOF calibration • procedures. These procedures are the part of standard offline reconstruction • program. So this interface use standard gbatch.exe executable. Interface is • written using Perl/Tk. • To use Commander SSH to pcamsr0, CD to /f2users/tofaccuser/headquarters. • Read “README_1st” file for more instructions. Use “StartTofCommander” • command to start the job. After you got window, select (left click) needed • session type (from 6 available types) and click “Start” button. The rest of • interface is build now automatically according selected session type. Use “Help” • button and right click on some critical buttons for more help. • Six available now session types are (written on related buttons) : • “PedCal” – creates pedestal/width/status tables using real data • (if in raw format !!!) or “OnBoard” created pedestal data. • “Ped2DB” - write this tables into the Data Base (DB). Before DB updating • you can check pedestals quality time evolution and remove bad tables.

  8. These two calibration types were demonstrated during one of the last year • TIMs and now just incorporated into common shell. • 3) “TdcLin” – this session creates TOF TDC nonlinearity corrections table • for each of LT (low threshold) and FT (fast trigger) SFET channels using • the real physical data runs. • “TdcL2DB” – during this session you can check the quality of all tables • accumulated in previous “TdcLin” sessions and write good ones into the DB. • The fig.4 shows the screenshot made during this session. • 5) “TAUCal” – most complicated session. Use real data to create 5 types • of calibration files: Ref-File (contains references to other calibration files), • CalibStatus-File, file with side-times offsets and effective light velocities • for each paddle, file with paddle-time offsets and slewing correction and • file with channels relative amplification factors, paddles energy loss • absolute normalizations and paddles light attenuation parameters. • This session use the results of previous “TdcLin” session. During this • session calibration quality and files consistency are checked and good • calibration sets are written into related store (directory) used in next session. • Use also “Help” button for more information. See screenshots on fig.5,6.

  9. “TAU2DB” – this session use previously accumulated calibration files sets. • You can check calibration parameters quality and their evolution in time, • exclude bad sets and write good ones into DB. For more information • use “Help” button. See also screenshot on fig.7.

  10. Fig.4

  11. Fig.5

  12. Fig.6

  13. Fig.7

  14. TOF-team members, please try to use this program (but not simultaneously !). I am ready for questions and proposals.

More Related