Frontend Application: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (→Arguments) |
||
| Line 23: | Line 23: | ||
[-O ] : Become a Daemon but keep stdout | [-O ] : Become a Daemon but keep stdout | ||
[-d ] : Used for debugging the frontend | [-d ] : Used for debugging the frontend | ||
[-i index] : Set frontend index (used with [[Mevb]] | [-i index] : Set frontend index so you can have [[Equipment_List_Parameters#Equipment_Name|multiple instances of the same executable running with different names]] (can be used with [[Mevb]] / [[Event Builder#Principle of the Event Builder and related frontend fragment|event builder]] or standalone). | ||
== Usage == | == Usage == | ||
Revision as of 16:09, 5 January 2024
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 so you can have multiple instances of the same executable running with different names (can be used with Mevb / event builder or standalone).
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