+ All Categories
Home > Documents > IceCube System Testing John Cavin 22 March 2005. Design / Verification Model System Engineering...

IceCube System Testing John Cavin 22 March 2005. Design / Verification Model System Engineering...

Date post: 27-Dec-2015
Category:
Upload: mitchell-moore
View: 215 times
Download: 0 times
Share this document with a friend
Popular Tags:
20
IceCube System Testing John Cavin 22 March 2005
Transcript

IceCube System Testing

John Cavin

22 March 2005

Design / Verification Model

System Engineering (R

equirements) Sy

stem

Inte

grat

ion

(Sol

utio

ns)

Project Science Goals

AchievedInstrument

Performance

System Architecture

Configuration Item Definition

Detailed Design

Requirements

(Manufacturing)

DetailedPerformance

Measurements

Incremental System Build-Up

& On-going Assessment

System Verification

Comparisons between Requirements and achieved performance are made at each

level in the System Hierarchy, starting with the simplest items and culminating in demonstration of overall instrument

functionality.

IceCube System Testing Facilities

• Factory Acceptance Test (FAT)

• System Test Facility

• South Pole Test System (SPTS)

• South Pole System (SPS)

Other IceCube Testing Facilities

• SPLTS – LBNL DAQ subsystem test

• DOM MB Testing @ LBNL plus vendor testing

• Pensar – Board testing of flasher board, high voltage base

• Chiba – PMT testing

Factory Acceptance Test (FAT)

• Verify operation of newly manufactured DOMs• Operate over temperature cycles• Obtain calibration data• Consists of facilities @ PSL, DESY, Uppsala:

– Dark Freezer Lab (DFL)

– TestDAQ software

– DOM Test software

South Pole Test System (SPTS)

• Operational configuration of deployed system• Integrate software/hardware subsystems• Test software in the “real” environment• Test deployment methods• Reproduce/debug problems in Northern

Hemisphere• Create the software versions that are released for

use at the South Pole

South Pole System (SPS)

• Operational IceCube System at the South Pole

PY03 Deployment Questions

• Will the HW/SW deployed at the South Pole Work?

• How can we gain confidence and/or find show stoppers before we deploy?

PY03 Hardware Configuration Items (CI) and Functional Interfaces

IceTopFreeze Control

IceTopFreeze Power

IceTopDOM

SurfaceJunction

Box

IceTopFreeze Control

IceTopFreeze Power

IceTopDOM

Tank 1

Tank 2

Surface Cable Assy

Surface to DOM Cable Assy

U-DOM

Paro

Keller

T-DOM

TCHPatchPanel

In-IceDOM Hub

In-IceInstrumentation

IceTopDOM Hub

IceTopFreeze Power

IceTopFreeze Control x 30

Created System Test Facility

• Provide a realistic test environment– Test subsystems– Interfaces– End to end data transfer

• Consists of:– DOMs in Chest Freezers– Surface to DOM Cables– Surface Junction Box– Surface Cables– DOMHubs– Test Software and/or Operational Software

System Integration Testing Goals- First Season

1. Discover issues associated with interfaces and device interactions prior to deployment

2. Demonstrate basic operation of software and hardware in a realistic system configuration

3. Demonstrate dataflow through the test system4. Demonstrate basic timing and local coincidence behavior5. Establish a readily accessible test-bed for interpreting SP

system behavior 6. Establish an off-line resource for continuing software

development7. Begin formal verification of devices and subsystems

Demonstrated under controlled conditions:

• Simultaneous, stable, operation of In-Ice and IceTop DOM

• Simultaneous, stable, operation of Sensor Subsystem and IceTop Freeze Control / Power Subsystems

• Reliable DOM operation under realistic conditions– No test DOM failures to date

• Reliable DOM Hub operation under realistic conditions– One SBC card failure, root cause investigation still open

Formal Engineering Verification at System Level

• Capability is now in place for Sensor Subsystem verification

• Fundamental tests defined and waiting for operator resources to conduct:– Part One: Establish Timing Baseline– Part Two: TCAL Rate Sensitivity Analysis– Part Three: Hit Input / Reporting Linearity– Part Four: Communications Stability in the Presence of Noise– Part Five: Timing Performance in the Presence of Noise

• Results can be available to support PY05 design decisions, but not in time to guide PY04

Scheduled Uses

• Complete timing and local coincidence testing – 30 Apr 2005

• Investigate Quad 2 problem – 30 May 2005• Integration and Test of DOR Rev 1 cards, DAQ

FPGA, and DAQ software – 1Jun 2005 thru 31 Jul 2005

• Move System test facility – 31Jul 2005 – 30 Aug 2005

• Support software testing – 1 Sep 2005 ---• Noise sensitivity of communications and timing –

Results of PY03 System Testing

• Putting system together uncovered issues:– Connector soldering problems

– Communication with IceTop DOMs on short cable

– Communication Testing over all cables

• Lots of work to do:– Timing characterization under controlled environment

– Will utilize test resources to understand and interpret behavior observed on String 21

– Integration and test of DOR Rev1, DAQ FPGA, DAQ software

– Support software development / check-out /certification prior to use at the pole.

Proposed Changes for Overall Testing Facilities

• Need to better utilize available space and resources

Conclusions

• Hardware and software testing will remain an important part of IceCube

• Capability exists to perform tests under a more controlled environment

• Released software will require rigorous testing before deployment to the South Pole

• PY03 testing contributed to success at South Pole


Recommended