Frontend Application: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== Frontend Task == The purpose of a <span style="color: green; font-style:italic; ">''frontend task''</span> is to collect data from the hardware and transmit this informatio...") |
(No difference)
|
Revision as of 17:49, 15 October 2013
Frontend Task
The purpose of a frontend task is to collect data from the hardware and transmit this information to a central place where data logging and analysis can be performed.
A frontend task is built by the user (see Frontend) and consists of as "user part" and a "system framework"
Arguments
The system framework code (mfe.c) has the following arguments:
[-h hostname ] : host name (see @ref RC_odbedit_utility) [-e exptname ] : experiment name (see @ref RC_odbedit_utility) [-D ] : Become a Daemon. [-O ] : Become a Daemon but keep stdout [-d ] : Used for debugging the frontend [-i index] : Set frontend index (used with @ref FE_mevb_utility . See also @ref FE_principle_eb).
Note that the new argument (-i index) has been introduced to facilitate the multiple frontend configuration operation required for the Event Builder
Usage
Start the application as a daemon, using the default host, experiment and port :
e.g. fevme -D
Start the application superceding the default host, experiment and port:
e.g. fegpib -e exp218 -h isdaq10 -p 7077 -D