Testing DAQ Commissioning Plan for 2005/06 - PowerPoint PPT Presentation

About This Presentation
Title:

Testing DAQ Commissioning Plan for 2005/06

Description:

Leak-test All DOMs. at patch panel. Sep 28th, 2005. SPTS. The ... Leak Test All new DOMs at patch panel. Get hub back from real DAQ if they have it. 1 hour ... – PowerPoint PPT presentation

Number of Views:19
Avg rating:3.0/5.0
Slides: 15
Provided by: markkr
Category:

less

Transcript and Presenter's Notes

Title: Testing DAQ Commissioning Plan for 2005/06


1
Testing DAQ Commissioning Plan for 2005/06
  • Mark KrasbergUniversity of Wisconsin
  • 28 Sep, 2005

2
Commissioning a DOMwith The Testing DAQ
Question Test
Does the DOM pass communications? MOAT
Does the DOM function properly? STF
Does the DOMs Local Coincidence connections work? LCCHAIN.PY
Does the DOM calibrate its HV? DOMCAL
Does the DOM have reasonable rates? Multimon/TestDAQ
Does the DOM take data properly? TestDAQ
From last year
3
Commissioning a Stringwith The Testing DAQ
Question Test
Does a string take data properly? TestDAQ
Do strings have timing skews relative to other strings? TestDAQ Flasher runs
4
This season
  • Deployments start early December, then every few
    days
  • There will be three stages of commissioning
  • DOMs in water
  • Some DOMs in ice and some in water after two
    weeks
  • All DOMs in ice after four weeks or more
  • DOMs will be separated into two groups
  • Leakers (leaking quads are never plugged into
    hubs)
  • Non-Leakers
  • DOMs will be put into two categories two weeks
    after deployment
  • DOMs which are frozen-in 2 weeks after deployment
    (around 48 DOMs)
  • DOMs which are not frozen-in 2 weeks after
    deployment
  • Strings will be divided into two groups
  • Those designated for Minimal Testing DAQ
    Commissioning
  • Almost all strings
  • Those designated for Expanded Testing DAQ
    Commissioning
  • 1st and 2nd deployed strings (see later), maybe
    another one?

5
Leaking DOMs
  • Like last year
  • All DOMs will be leak-checked before they are
    plugged in.
  • When DOMs are used in water, they will be
    repeatedly leak-checked

6
(No Transcript)
7
Minimal Commissioning in Water (within T48
hours)
  • As soon as possible after the drop

Task Action Length of Test
Leak-test All DOMs at patch panel Plug in good QUADs from patch panel to DOR cards 60 minutes
Turn on all DOMs Verify DOM positions Check LC connections Check Noise Rates Do short MOAT run 60 minutes
Turn off all DOMs Turn off power to all DOMs on back of hub
8
Upper String Minimal Commissioning in Ice, part
1
  • Two weeks after deployment, perform minimal
    commissioning in ice

Task Action Length of Test
Leak Test All DOMs at patch panel Plug in good QUADs from patch panel to DOR cards 60 minutes
Turn on all DOMs Verify DOM positions Check LC connections Check Noise Rates Do short MOAT run 60 minutes
Turn off all DOMs Unplug QUADs which are not frozen-in 30 minutes
Same as in water
9
Upper Minimal Commissioning in Ice, part 2

Task Action Length of Test
Upload firmware 30 minutes
Calibrate DOMs Run DOMCal 60 minutes
Short TestDAQ checkout Verify mechanics 30 minutes
Check Communications MOAT 14 hours
Check DOM function STF 1 hour
Automated TestDAQ checkout Run desired steering files 48 hours
Give hub to real DAQ if they want it
10
Entire String Minimal Commissioning in Ice

Task Action Length of Test
Get hub back from real DAQ if they have it
Leak Test All new DOMs at patch panel Plug in good QUADs from patch panel to DOR cards 60 minutes
Determine which QUADs are frozen in Unplug QUADs which are not frozen in or perhaps delay test 30 minutes
Upload firmware 30 minutes
Calibrate DOMs Run DOMCal 60 minutes
Short TestDAQ checkout Verify mechanics 30 minutes
Check Communications MOAT 14 hours
Check DOM function STF 1 hour
Automated TestDAQ checkout Run desired steering files 48 hours
Give hub to real DAQ if they want it
Same as Deployment2 weeks
11
Expanded Commissioning
  • A small number of strings will be earmarked for
    expanded commissioning
  • 1st deployed string (only during first two weeks)
  • 2nd deployed string (for entire freeze-in
    process)
  • Why these strings?
  • Maximizes likelihood of being able to do
    something about a problem
  • Leak-checks can be done at same time
  • Expanded Commissioning can continue on 2nd string
    after 1st string is given to real DAQ
  • Monitor rates, monitor temperatures, will
    freeze-in before end of season, flasher runs in
    water etc.
  • Strings are nearby one another

12
Expanded Commissioning in Water (T 12 hours)
  • As soon as possible after the drop, in addition
    to Minimal Commissioning in water

Task Action Length of Test
Perform repeated leak checks Plug in non-leaking QUADS to DOR cards
Monitor Noise rates Multimon/TestDAQ As often as possible
Take special runs (flasher runs, for example) Requires firmware, DOMCal, TestDAQ
13
Expanded Commissioning in Ice
  • Similar to Minimal Commissioning in Ice, except
    continue to monitor rates, and take requested
    runs, whenever possible. Continue to leak-check
    until all DOMs are frozen-in.

14
One idea
  • The final commissioning stage for each string (ie
    the bottom 12 or so DOMs)
  • Perhaps we want to do this part of the
    commissioning in March/April all at the same
    time.
  • Minimizes handoffs back and forth from real DAQ
    to TestDAQ to real DAQ.
  • TestDAQ is used in one large final commissioning
    test
  • special multi-string runs can be taken
  • Final set of steering files can be generated for
    all DOMs to be used by real DAQ
Write a Comment
User Comments (0)
About PowerShow.com