DOM INTEGRATION MEETING

DAAN VAN EIJK

28 JANUARY 2016

2

ISSUES AND ACTIONS FROM PREVIOUS MEETING• DOM integration halted at optical splice due to AHRS problems

• This decision affects us (DOM integration teams) heavily• But: PMT structures and bottom hemispheres can be fully

integrated!• News on AHRS status will follow very soon

• Firmware and embedded software versions to be flashed on CLB’s

• Revision to flash: rev150904• DOM registration software:

• Version 1.7 (bug fixes, added Ti bolts and nuts, A/D filter from unique to batch product) to be redistributed soon.

• @Daniele:

• What is status in DB of 6 (or 31?) re-tuned PMTs in Naples during DOM test? New test result?

3

CURRENT ITEMS• New DOM exploded view (v12)

• DCR raised (version change request) and new version uploaded• Changes:

• Include Ti bolts and nuts as batch products (STAC request)• Change A/D filter from unique product to batch product

• Ti bolts and nuts:

• DB:• 3.4.1.1.4 Ti bolt gr 5 M6 x 25• 3.4.1.1.5 Ti nut gr 5 M6• To do: container map (also change A/D filter to batch!)

• DOM integration software:• Changes incorporated, but need to add columns for bolts and

nuts• Electrostatic discharge safety (ESD):

• What is done where?

4

DOM TEST SHEETS• New version DOM test sheets

• DCR raised (version change request) and new version uploaded• Changes:

• Change humidity ranges to 20-50% (was 30-50%)• Change ToT range to 24-30 ns (was 25-28 ns)• Change WR temperature to CLB temperature• Add SFP temperature (since we also monitor FPGA

temperature)

5

DOM TEMPERATURES

Humidity and temperature should come from same sensor:Hence: change WR temperature to CLB temperature

6

DOM TESTING• To analyse the optical data from a DOM test (i.e. the root files),

everyone should use http://svn.km3net.de/data_analysis/MRunAnalyzer/

• DOM test sheets should be stored in DB as attachment

• Next on my list: ask Cristiano whether the data can be saved as “Test” instead of attachment to DB entry.

• Alternative (preferred, but not possible yet): data is saved automatically as DOM testing will progress to operating a DOM like a mini-detector.

7

DOM PRODUCTION STATUS: LINE TYPES• Amsterdam: type B and type C

• Request to build type A for first ORCA line. • Currently, no A-type SFP’s at Nikhef anymore and type C line

DOM production has already started.• Catania: type C

• Naples: type D

• Erlangen: Commissioning DOM test setup

Type A: CH56C-CH22CType B: CH55H-CH21HType C: CH55C-CH21CType D: CH54H-CH20H

8

DOM PRODUCTION PLANNINGLocation 2014 End 2015 Spring

2016End 2016 TOTAL

Amsterdam 19 38 +80 (doubling 2015 production rate)

137

Naples 4 +18 +36 58

Catania 4 +18 +36 58

Erlangen +36 36

Number of DOMs to be built before the end of 2016: 80+54+54+36= 224

Total number of DOMs produced by the end of 2016: 224+65 = 289

DOMs needed for KM3NeT Phase-1: 31 x 18 = 558

End of 2016

9

DOM COMPONENTS• I will bring DOM components for 18 DOMs to Erlangen for Collaboration

Meeting

• Penetrators:

• Testing of 64 PAVE penetrators at Nikhef done:• New order of 100 penetrators placed, expected to arrive end of

March (but pushing to send them sooner)• Naples still needs 7 penetrators to complete 18 DOMs• Catania still needs 12 penetrators to complete 18 DOMs• But: there are (legal/tax) issues with shipments for PON money

components• Waiting for more info

10

TODO…• Documentation DOM production:

• List of Applicable Documents• Most notably the DOM Integration Procedure

• In good shape, will rediscuss open questions with Edward/Rene

• Otherwise, just aesthetics• Integration Plan

11

DOM PRODUCTION AMSTERDAM (IN ABSENCE OF RONALD)

Script to produce plots from local integration DB can be found in: http://svn.km3net.de/integration/DOM_Production_Rate/

12

BACKUP