Frontend Application: Difference between revisions

From MidasWiki
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...")
 
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Pagelinks}}
== Links ==
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
* [[Frontend Operation#Frontend|Frontend Operation]]
* [[Frontend user code]]
</div>
== Frontend Task ==
== 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 information to a central place where data logging and  
The purpose of a <span style="color: green; font-style:italic; ">''frontend task''</span> is to collect data from the hardware and transmit this information to a central place where data logging and  
Line 4: Line 13:


A  <span style="color: green; font-style:italic; ">''frontend task''</span> is built by the user
A  <span style="color: green; font-style:italic; ">''frontend task''</span> is built by the user
(see [[#Frontend Operation#Frontend|Frontend]]) and consists of as "user part" and a "system framework"
(see [[Frontend Operation#Frontend|Frontend Operation]] ) and consists of as "user part" and a "system framework"


== Arguments ==
== Arguments ==
The system framework code (mfe.c) has the following arguments:
The system framework code (mfe.cxx) has the following arguments:


   [-h hostname ] : host name (see @ref RC_odbedit_utility)
   [-h hostname ] : host name (see [[Common Parameters to MIDAS Utilities]])
   [-e exptname ] : experiment name (see @ref RC_odbedit_utility)
   [-e exptname ] : experiment name (see [[Common Parameters to MIDAS Utilities]])
   [-D ] : Become a Daemon.
   [-D ] : Become a Daemon.
   [-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 @ref FE_mevb_utility . See also @ref  FE_principle_eb).
   [-v [level]] : Set verbosity level (as an integer). A bare '-v' implies '-v 1'
 
  [-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).
Note that the new argument (-i index) has been introduced to
facilitate the multiple frontend configuration operation required for the [[Event Builder]]
 


== Usage ==
== Usage ==
Line 30: Line 36:


  e.g. fegpib -e exp218 -h isdaq10 -p 7077 -D
  e.g. fegpib -e exp218 -h isdaq10 -p 7077 -D
[[Category:Frontend]]

Latest revision as of 10:26, 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.cxx) 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
 [-v [level]] : Set verbosity level (as an integer). A bare '-v' implies '-v 1'
 [-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