This is mainly a list brain dump to

• This is mainly a list (brain dump) to trigger discussion • technical details can be filled in later • important for today is to list all components and get a more detailed price estimate now (or soon) • What about spares, contingency – let’s all be equally pessimistic / optimistic

Main ingredients of the telescope • • • Mechanics Sensor layers SPIDR 4 readout / DAQ Reference Timing planes Central logic unit (TLU) Software (Run/Slow control, DAQ, online analysis) • Support? (incl. documentation)

Mechanics • should consider to make each plane a separate entity / box instead of common enclosure – like the AIDA/EUDET telescope – most heat generating electronics is in open air – eases cooling, cabling and is sideways less space constrained • mounted on common base ‘plate’ – use optical rail? – preferably flat base (y-stage of Du. T not sticking out below) • manual rotation + tilt (yaw, pitch) stage per plane? – optimise angles depending on type/thickness of sensor -> flexibility • temperature control of telescope planes – budget for separate ‘warm’ cooling unit? • big motion stage for entire telescope? – or use DESY table? • Du. T motion stage part as of project – remotely controlled: x, y, yaw, pitch

Sensors • 8 planes with timepix 4 based hybrid pixel detectors • sensor type to be determined • upgrade when faster sensors become available -> hence reserve budget for more chipboards • consider hybrid system with separate hi-res spatial and timing planes • Budget for sensor acquisition and bump bonding – assume we can buy the sensors, no development – including bump bonding masks • ASIC thinning? • We shouldn’t forget the bias voltage supplies (multiple for a hybrid system)

SPIDR 4 / DAQ readout for 8 planes (details in last slide) • • Assume DAQ for LHCb sensor programme is not part of telescope package 8+ chipboards ? 8 slow control boards, ‘low rate’ DAQ 8 ports 10 Gb. E + DAQ computers (4 systems, or one big server) 1 control PC (with 8 x 1 Gb. E) Local data storage consider reserving budget for 1 high rate DAQ board – honestly mostly ‘for fun’ – but argument is that we can test the scalability of the DAQ towards a high rate system

Reference timing planes • • • 2 planes for fast timing reference including fast TDC (pico. TDC project? ) Locked to the 40 MHz system clock provided by Linked to telescope shutter signal DAQ Controlled via 1 Gb. E? • Extra TDC channels for offline synchronisation of data (external Du. Ts)? • Or should the TDCs (also for ref. planes) be part of TLU subproject?

Central logic unit (TLU? ) • • • clock generation (with external ref clock input) – stability / jitter is very important – clock signal distribution, 16+ channels, various signal levels – per channel tunable phase, better than 5 ps per step shutter signal distribution T 0 -reset signal distribution configurable/controllable (via 1 Gb. E? ) level adapters (conversion boxes) to accommodate to DAQ of external Du. Ts Should we add trigger functionality? – or use (old) NIM logic for scintillators – not easy to make a universal solution • logging of actions, use GPS time? – means that the TLU will be source of data too

Software • Run control (relatively simple) – with scripting/scanning option – web based status page? • Instrument controls – Bias voltage – motion stages – labview based? • Online monitoring / DQM – – Just hitmaps & signal (To. T) distributions or also tracks? Do we need a separate DAQ (monitoring) stream for this environmental: temperature / data volume etc. computing requirements (e. g. large status screens)? • Track reconstruction – kepler based? (fair chance that we will mix TPX 3 and TPX 4 based systems) – portability (non-LHCb users) – Quasi online? computing resources? • Integration with EUDAQ?

In which workpackage do we put these items? • extra TDC inputs needed for offline synchronisation of data from (external) Du. Ts – we could use the “digital pixels” of the TPX 4, but these have limited resolution (195 ps bins) – extra TDC channels, same as reference timing planes • Environmental monitoring – temperature – humidity – others status signals

Some SPIDR 4 basics • SPIDR 4 is the name of the system, not that of a single board • Complete system consists of multiple board, but not all are needed for the telescope – Chipboard: hosts the Timepix 4 chip • first type of chipboard will host 1 chip • multi-chip boards planned (but not needed for telescope) • ~500 euro / board – Controlboard: • • slow control electro-optic conversion for 16 high speed links ‘low rate’ DAQ via 10 Gbits/s ethernet (still tens of million track/s) ~2500 euro – DAQ board (commercial FPGA-PCIe card) for 160 Gbits/s rate • would need 1 per chip for max rate • ~15 keuro, including server (check, is maybe excl. VAT) – White rabbit compatible (but not for telescope)