1 / 8

Test Beam Meeting Monday, January 31, 2000 Fpix1 Calibration Status What we have What to do

Test Beam Meeting Monday, January 31, 2000 Fpix1 Calibration Status What we have What to do Monitor Software to use now Current Version Calibration Fpix0 Fpix1 SSD Pedestal Magnet Track Finding Position Algorithm for Pixels Electronic Run Log Book.

raanan
Download Presentation

Test Beam Meeting Monday, January 31, 2000 Fpix1 Calibration Status What we have What to do

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. Test Beam Meeting • Monday, January 31, 2000 • Fpix1 Calibration Status • What we have • What to do • Monitor Software to use now • Current Version • Calibration • Fpix0 • Fpix1 • SSD Pedestal • Magnet • Track Finding Position Algorithm for Pixels • Electronic Run Log Book

  2. FPIX1 Calibration StatusWhat we have • Pulse scan from 0.05V to 0.48V by step of 0.001V • Fpix1-pstop (board 4)(Vth=2.2V and Vth=1.95) • Fpix1-pspray (board 1)(Vth=2.25V) • 128 patterns • The two board Tested in parallel • 100Hz pulse rate: 24 hours • Xray sources: • Tb(Kalpha=44.23keV=12286elect) • Ag(Kalpha=22.10keV=6138elect) • Mo(Kalpha=17.44keV=4844elect) • Trigger rate 100Hz • Vth0 scan from 1.8 to 2.2V (2.22V) by step of 0.01V 10000 events each • The data are now in ntuple format • Event number • Iadc,icol,irow,idchip • Amplitude(Pulse amplitude or Vth0) • From the ntuple the two groups of data collected make sense but the program to fit each cells for each adc as a function of the amplitude is still not ready

  3. FPIX1 Calibration StatusWhat to do • Still some test to do as suggested by Simon: • Cross Talk as a function of the position of the cells • To try to read out more than three cells in the same column and rows>85 for Fpix1 • To measure the pspray Front End noise as a function of the bias • To do more Xray source measurements for Fpix1-pspray • (If possible) Before to move every think from Mtest analyze the data to see if they are enough to calibrate the fpix1

  4. Tb-Xray Source Fpix1-pstop(board 4)

  5. Monitor Software to use nowCurrent version Must be good for every runs and the different Setups are handled by changing: tb_monitor.dat • planes to drop some time: • plane 4 (x SSD plane upstream box) • planes 10,11 (fpix1) • planes to drop always: • planes 9 (fpix1) • Manual geometry files • x, y offset for all planes used must be adjusted • z offset set to nominal value • alpha, beta, phi angles SSD planes set to 0 • alpha, beta angles PSD planes set to 0 • beta angle PSD plane under test set to nominal value • phi angle PSD planes must be adjusted • Manual geometry files in B • in magnetic field alpha, beta, phi angle plane 7 must be adjusted, the pitch and the active area must be swap in x and y • In magnetic field alpha7 must be changed for each current

  6. Monitor Software to use now Calibration • Fpix0 • JC’s files, two line in tb_monitor.nml: • pixel_calib_file(1) = '~wangjc/testbeam/db/pstop_fpix0_v2.dat' • pixel_calib_file(2) = '~wangjc/testbeam/db/pspray_fpix0_v2.dat' • JC’s subroutine to copy in running area: • ~wangjc/testbeam/src/pix_pstop_convert.F • ~wangjc/testbeam/src/pix_pspray_convert.F • Fpix1 • Single chip thresholds Now(a little changein the subroutine pix_adc_convert.F + two files for the plane 10 and 11). • Single cells thresholds with Fortran code • SSD planes • No SSD pedestal subtraction • Magnetic field vs Imagnet (estimated error) • Dave’s measurement

  7. Monitor Software to use now Track Finding Position Algorithm for Pixels • The TFP monitor software must not be changed • Try several TFP algorithm use Fortran code: • for example the Rita’s Fortran code (also it handles more than one Hbook files)

  8. Monitor Software to use now Electronic Run Log Book • It is easy to display with the Run Log Book shell the files stored in Datad1,Datad2…,Datad9. • Io Wrote an email to Dario Manasce to understand how to run a kumac by this shell. • The list of Basic Sample of Runs in place with the Jeff’s suggested corrections but other ones still to do.

More Related