1 / 15

String-18 New-DAQ Commissioning

String-18 New-DAQ Commissioning. Azriel Goldschmidt AMANDA Collaboration Meeting Berkeley, March 2002. Hardware Installation. 5 TB-DAQ PCs + 1 String-DAQ PC 40 DOMCOM boards (for 40 DOMs), 37 in use because of bad DOMs. -KHS-

kamin
Download Presentation

String-18 New-DAQ Commissioning

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. String-18 New-DAQ Commissioning Azriel Goldschmidt AMANDA Collaboration Meeting Berkeley, March 2002

  2. Hardware Installation • 5 TB-DAQ PCs + 1 String-DAQ PC • 40 DOMCOM boards (for 40 DOMs), 37 in use because of bad DOMs. -KHS- • Clock distribution unit with Rb atomic clock and GPS input. -GTP-

  3. New DOM Failures • Ch601 (DOMID 1036) started drawing too much current and burns DAQ channels. • Ch630 (DOMID 1049) not communicable for some reason (not powered…we think). Further hardware measurements needed to understand what happened in these two cases. They were flawless a year ago.

  4. 1. tbdaq-1 ch. 1: DOMID 1019 OM681 No fiber "by construction" Its physical location is between OM599 and OM600. 2. no daq-channl: DOMID 1036 OM601 burns DOMCOM channels (was ok until 02) cable:Q20L. (could use further debugging with an ohm meter). Not powered. 3. no daq-channl: DOMID 1044 OM604 base went bad, gives 1Mhz hits. This one broke in the pole 00-01 campaign. Not powered. 4. no daq-channl: DOMID 1007 OM610 intermittent electrical. Bad since deployment. Not powered. 5. tbdaq-3 ch. 4: DOMID 1039 OM620 bad fiber connector at surface. Could get fixed by someone that knows about fixing fiber connectors, etc. Powered but no analog hits. 6. no daq-channl: DOMID 1049 OM630 Kalle said it is not good. But Leuthold does not report as bad analog. Cable: Q6S. are we powering it? through a DOMCOM? Was good before 02. 7. tbdaq-5 ch. 1: DOMID 1013 OM632 bad fiber in ice, also bad base, since deployemnt. 8. tbdaq-5 ch. 7: DOMID 1034 OM638 used to have bad surface fiber but now it does not appear in Leuthold bad list (was it fixed?). Has a bad comm DAC at the DOM end or something that makes strange ticks up when captured on the surface. Can be used for time synchronization but it needs special treatment of the data. 9. tbdaq-3 ch. 6: the surface clock counter does not reset but problem follows the clock channel/cable and not the DOMCOM. Could take a spare clock channel/cable to fix it. Has been requested. 10. tbdaq-2 ch. 0: now a "bad" spare, it was before DOMID 1030 but since it failed (clock issue?) it was left empty. 11. tbdaq-2 ch. 1: DOMID 1009 OM608 bad base (cannot set value of voltage), but usable PMT signals and digital data. This one broke in the pole 00-01 campaign. 12. tbdaq-5 ch. 4: DOMID 1029 OM635 cannot do timming becasue the DOM renders a flat comm ADC (can it do coarse 30nsec synchronization? without fits?) 13. tbdaq-3 ch. 7: DOMID 1032 OM622 comm DOM ADC waveforms are off-scale. They seem usable but need special treatment in analysis. This is a problem at the DOM end. 14. tbdaq-1 ch. 5: DOMID 1033 OM605 ATDW1 output is bad (all samples equal 682) ATWD0 is good. 15. tbdaq-4 ch. 6: DOMID 1022 OM629 ATWD1 data is bad (some samples 0-1 others just wrong, depending on the channel). ATWD0 is good. 16. tbdaq-1 ch. 0: DOMID 1004 OM599 ATWD0 is bad ATWD1 is good (high gain all 0-1 low gain saturates

  5. Fixes/upgrades after installation • One burnt CPU replaced with the only spare. • A couple of bad cables/channels being swapped • A problem with the time reset operation fixed with remote loading of new firmware to clock unit

  6. Analog Output Status Summary • 1 channel no fiber. • 2 new failures, DOMs do not communicate: need further study. • 2 bad bases (a third bad base is still usable). • 1 intermittent electrical connector.

  7. Cable Delay Measurements Using RAP Method • Repeated measurements from last year with new DAQ hardware. Analyzed by D. Cowen: consistent results. • Improved surface noise (diff. Amplifier) • Effect of Rb clock stability, compared to GPS’s is being studied. • Main achievment is that now all channels (before just 4) can deliver physics data.

  8. Time Synchronization 2001-TestBoards

  9. Time Synchronization 2002-DOMCOM

  10. Time Sync Waveforms (ADC)

  11. Time Sync Waveforms: Noise

  12. Down-going Muon Events • A 15 min long run with all modules collecting LC hits • Each DOM with a live-time of ~5-10% • individual LC rate is 3-6 Hz • Obtained 2 events with 6 DOMs hit in each. • Clear down-going time structure confirming correctness of time stamping.

  13. 6-OM Downgoing Muonswith LC (no proc-sync)

  14. From here to Physics Ready Data... • DAQ software: Upgrade well under way, will support full data retrieval from all eight channels on each DOMCOM PC. -JEJ- • DAQ Trigger Software: Ready to be tested. -KH & DC- • Event buffering at the DOM • Firmware upgrades, in progress -GTP- • DOM Software upgrades, coming soon -CMP- • Fast communications (~50% Surface end implemented) -GTP- • Feature extraction: work being done in Sweden.

  15. Other Future tasks and issues • Calibrations: flashers, transit times, etc. • Studies in connection with AMANDA/TWR/SPASE. • Test Bed for IceCube modus operandi (similar but not identical to current scheme)

More Related