04.02.2013 Views

Technical Design Report Super Fragment Separator

Technical Design Report Super Fragment Separator

Technical Design Report Super Fragment Separator

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2.4.A Appendix<br />

DRAFT<br />

The appendix of the <strong>Super</strong>-FRS TDR describes components and sub-systems which are strongly<br />

related to the <strong>Super</strong>-FRS but at the same time have an overlap or are common to other FAIR facilities.<br />

2.4.A1 NUSTAR DAQ<br />

The NUSTAR data acquisition (DAQ) concept tries to incorporate and deal with the changes that<br />

are related to the discontinuation of production and support of all CAMAC and FASTBUS modules,<br />

together with the much increasing number of channels in the different experiments. Dedicated<br />

front-end electronics boards are foreseen in most experiments for NUSTAR. The other main issue<br />

is to provide a maximum interoperability of the different setups of the NUSTAR facility for many<br />

parts of particular setups, detectors systems and their associated DAQ systems. An example is the<br />

in-ring instrumentation of the NESR that will be used in parallel by the EXL and ELISe collaborations.<br />

The same holds for the combination of <strong>Super</strong>-FRS instrumentation – R 3 B setup, or gamma<br />

spectroscopy arrays in conjunction with reaction setups. As the communities overlap to a large<br />

extent it is favourable to come up with a combined DAQ framework that allows sharing expertise,<br />

thus saving manpower and running cost. The GSI MBS [84] system is an example for such a<br />

flexible DAQ scheme, that provides a generalized multi-processor environment, suitable for the<br />

readout, control and data storage of heterogeneous setups. The necessary extensions of the scheme<br />

have to be evaluated and integrated into the developing system by the NUSTAR DAQ group. A<br />

major part of this will be the integration of ‘foreign’ stand-alone DAQ systems or similarly the<br />

control and operation of various front-end electronics. System integration should be possible at<br />

different stages of the DAQ system.<br />

(a) “NUSTAR” DAQ systems: It should be possible to couple different standalone<br />

“NUSTAR” DAQ systems, together in a simple way. Typically the individual DAQ systems<br />

are used to setup and debug detector groups or experiments. By foreseeing the necessary<br />

interconnects for triggers and control signals and by keeping the modularity of the<br />

system in mind while building local triggers and event buffer capabilities, such a scheme<br />

can be realized. The R 3 B/CaveC setup together with the current FRS is an example where<br />

the necessary prerequisites are currently specified. Note, that different schemes of coupling<br />

might be used here: (i) the systems are synchronized with one common trigger (ii)<br />

the DAQ systems run standalone and are synchronized via timestamps (see section<br />

2.4.A1.1).<br />

(b) Front-end electronics (FEE): For the common NUSTAR DAQ system, specific<br />

front-end electronics together with its digitization part is seen as part of the detector. This<br />

has the advantage that all analogue signal processing is done by the working groups with<br />

the most experience on the particular detector system. Only the control, trigger and data<br />

flow will be specified as interface description by the common NUSTAR DAQ system.<br />

This includes the necessary trigger types to be implemented, such as data, calibration and<br />

synchronization triggers together with a prescription how to lock the FEE to realize a<br />

clearly defined dead time of the total system. The timestamp-data interface has to be<br />

specified and slow control issues like version numbering, firmware revisions, software<br />

up/download from e.g. databases to particular FEE boards require R&D work. A first<br />

155

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!