Glossary: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
'''E''' | '''E''' | ||
;Equipment : | ;Equipment : see "Software Equipment" | ||
:;Hardware Equipment | :;Hardware Equipment | ||
:: Hardware modules (e.g. a set of scalers) grouped together for convenience of data readout | :: Hardware modules (e.g. a set of scalers) grouped together for convenience of data readout by a Software Equipment. | ||
:; Software Equipment | :; Software Equipment : also called "Equipment". A single or a collection of sub-tasks meant to collect and regroup logical or physical data under a single and uniquely identified event. Software Equipments are usually found in [[Frontend Operation#Frontends| Frontends]]. | ||
'''F''' | '''F''' |
Revision as of 15:37, 18 October 2013
D
- Driver
- (also device driver) Software that allows access to a particular hardware module.
E
- Equipment
- see "Software Equipment"
- Hardware Equipment
- Hardware modules (e.g. a set of scalers) grouped together for convenience of data readout by a Software Equipment.
- Software Equipment
- also called "Equipment". A single or a collection of sub-tasks meant to collect and regroup logical or physical data under a single and uniquely identified event. Software Equipments are usually found in Frontends.
F
- Frontend (task)
- A MIDAS application built by the user which usually has access to hardware equipment in use by the experiment.
- Frontend code
- User-written part (e.g. frontend.c) describing sequence of actions to acquire the hardware data. It is linked with a fixed framework mfe.c to form a Frontend..
O
- ODB
- Online Data Base contains all the information needed for an experiment
R
- Run
- A run starts when the MIDAS system receives a Start Transition , and continues until it receives a Stop transition
T
- Transition