Skip to content

Latest commit

 

History

History
50 lines (34 loc) · 2.78 KB

README.md

File metadata and controls

50 lines (34 loc) · 2.78 KB

EUDET-type beam telescopes using EUDAQ2

Components

  • Mimosa Sensors and NI DAQ: EUDAQ2 code here in user/eudet
  • EUDET or AIDA TLU: EUDAQ2 code in user/tlu
  • StdEventMonitor which is the EUDAQ1 OnlineMon (EUDAQ_BUILD_STDEVENT_MONITOR=ON)
  • Reference Plane, for example FEI4, USBPix / STControl: EUDAQ2 code which is currently working is here: https://github.com/beam-telescopes/USBpix/tree/release_5.3_eudaq20

Running modes

In brackets the exemplary start scripts are quoted which can be found in user/eudet/misc/start_scripts; the EUDAQ ini and conf-files in user/eudet/misc/conf.

Standard (EUDET) mode

The EUDET TLU (01_eudet_tlu) or the AIDA TLU (01_aida_tlu) in EUDET mode can be used.

EUDAQ1-like (global busy) data taking synchronising by Event ID:

  • online: using one EventIDSyncDataCollector connected to all producer (02_eudet_tlu_telescope or 02_aida_tlu_telescope_eventID-DC)
  • offline: using multiple DirectSaveDataCollector each connected to one producer (02_aida_tlu_telescope) and merge them offline using euCliMergerStandardEvtID

If the devices are reading out the Trigger ID, the synchronisation can also happen by this:

  • online: using one TriggerIDSyncDataCollector connected to all producer (02_aida_tlu_telescope_triggerID)
  • offline: using multiple DirectSaveDataCollector each connected to one producer (02_aida_tlu_telescope) and merge them offline using euCliMergerStandardTrigID

Mixed mode

This can be used with the AIDA TLU and the the DUTIgnoreBusy option in order to allow multiple triggers within one Mimosa read out:

Mixed mode data taking synchronising by Trigger ID:

  • online: using one TriggerIDSyncDataCollector connected to all producer (02_aida_tlu_telescope_triggerID)
  • offline: using multiple DirectSaveDataCollector each connected to one producer (02_aida_tlu_telescope) and merge them offline using euCliMergerMixedCombinedTrigID or euCliMergerMixedDuplicateMimosaTrigID depending on the analysis.

AIDA mode

The synchronisation by timestamps will be developed and can be in usage if a (quasi)-continous read-out of the Mimosa data stream is available. This can happen with a new Mimosa DAQ, like the MMC3 board which is currently under development: https://github.com/SiLab-Bonn/pymosa

NiRaw2StdEventConverter

Tool to convert raw mimosa data to StandardPlanes in a StandardEvent. Since two data frames are copied in the default mode, only data behind (before) the pivot pixel in the earlier (later) frame is copied. Converting all recorded hits can done via the configuration

use_all_hits =1

User Manual

Wiki-Pages for operating EUDET-type beam telescopes: https://telescopes.desy.de/User_manual