Frontend Application: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==== Links ==== | ==== Links ==== | ||
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> | <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> | ||
* | * [[Frontend Operation#Frontend|Frontend Operation]] | ||
* | * [[Frontend Code]] | ||
</div> | </div> | ||
Revision as of 18:55, 15 February 2014
Links
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 Operation ) 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 Common Parameters to MIDAS Utilities) [-e exptname ] : experiment name (see Common Parameters to MIDAS Utilities) [-D ] : Become a Daemon. [-O ] : Become a Daemon but keep stdout [-d ] : Used for debugging the frontend [-i index] : Set frontend index (used with Mevb . This argument 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