1 / 17

SctRodDaq

SctRodDaq. Calibration mode GUI improvements Error reporting New & improved tests Information for offline Physics mode. Modify various parameters on-the-fly. TIM module GUI view or modify registers. New “DAQ crate view”. To err is … inevitable.

keola
Download Presentation

SctRodDaq

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. SctRodDaq • Calibration mode • GUI improvements • Error reporting • New & improved tests • Information for offline • Physics mode Alan Barr, UCL

  2. Modify various parameterson-the-fly TIM module GUIview or modify registers New “DAQ crate view” Alan Barr, UCL

  3. To err is … inevitable • All data errors are reported by SctApi (SctApiCrateServerX.out file) • In case of a scan stall it is now much easier to find out what the cause of the problem is • Errors reported clearly in RawScanResult output • ROD-triggered scans and TIM-triggered scans • DSP code also does error-counting per link • not currently read out Alan Barr, UCL

  4. Error report on stall Alan Barr, UCL

  5. Errors calculatedfrom “absent events” Alan Barr, UCL

  6. RxThreshold • Optical cross-talk • Config register modified (for the duration of this scan) so that adjacent fibres send different data • If optical cross-talk is present it should now be visible • Analysis • More robust analysis • Looks for valid headers (111010) rather than just ‘any combination of clean binary data’ • ‘Rise time’ of VCSEL amplitude calculated (number clocks between 25% and 75% max signal) • Long rise time ‘linked with infant mortality’ Alan Barr, UCL

  7. max best min “Normal” link max,min &best! Worst-case link Alan Barr, UCL

  8. Tim Triggers • Fixed Frequency Trigger Veto in place • We cannot run synchronous calibration scans with FFT! • “SynchTriggerNoise” test now uses TIMs pseudo-randomised triggers • [For those in the know it’s the randomiser version 2] • Check is made for FFTV application • Warning message if FFTV has been applied during scan  statistics sent to MRS Alan Barr, UCL

  9. Δt Δt Δt Δt Synch Double Triggers • Uses TIM sequencer to send pairs of L1A’s separated by a time interval which is scanned • The pairs are initiated by randomiser 2 • Otherwise FFTV would • Analysis same as for “normal” double trigger noise • Look for optical/electrical pick-up on second trigger at T ~ L1 pipeline depth Triggers t Alan Barr, UCL

  10. General analysis improvements • Scan options are recorded in book-keeping data and are reproduced in test result • Much easier to work out from data exactly how the test was performed • Options such as “Full” / “Tim” / “Ope” etc. • Distinguishes e.g. DoubleTriggerNoise (TIM=0) from SynchDoubleTriggerNoise (Tim=1) • Visible in summaries too • Part way towards fully-configurable scans Alan Barr, UCL

  11. Tim external trigger • Trigger to TIM from LEMO • Tested with cosmics trigger from TRT • “Full mode” scan  all three time bins • Analysis & display understand how to interpret different time bins • Combine all information into single plot Alan Barr, UCL

  12. Scan delay in steps of 3*bunch crossings Histogram all 3 time bins Combine information in analysis Full Scan - PreTriggerNoise 10 bins 30 bins Time bin t-1 Time bin t Time bin t+1 Alan Barr, UCL

  13. Calibration Information flow Displays Results of Scan &Tests produced by SctRodDaq (Raw, Fits, Analysed) Reads + interprets Text summaries(Assembly DB) Bad channels, Noise, Noise Occ to COOLvia CDI Archiving to file Replacement of text summaries by IS summaries in progress – should improve GUI performance Alan Barr, UCL

  14. Physics Mode • Physics mode “proven” • Large system with 6 pc’s, dozens of processes • Not yet routine • Still at “expert level” • Need to do some “by hand” work on transition • Combined testing done with TRT DAQ • Data output as text from eventDecoder • No online test of Athena or Monitoring as yet • Though should be possible in principle • Several new features already made to Atlantis on request Alan Barr, UCL

  15. Physics running TRT LTP SCT LTP To … Event display Monitoring ROS Events TIM Triggers ROD ROD ROD ROD histogrammingduring physics runningnot yet fully available Scintillators SBC Analysis PC,GUI Alan Barr, UCL

  16. Known shortcomings • Complete test with DIM (new DCS interface) still to be done • Transition between physics mode and calibration mode needs smoothing • Some details of ROD firmware still being investigated • XXX more here XXX Alan Barr, UCL

  17. Improvements on the cards • Sorting out previous shortcomings! • Fully configurable scans • Set scan points, options etc in advance via GUI • Increased speed for raw scans • Needs on-rod compression of histogram data • In binaries but not used in current release • Readout of DSP’s errorInfo scans • Full info about errors by link and by type • Dynamic removal of modules on error • Perhaps randomiser in DAQ scans? Alan Barr, UCL

More Related