IS server and IGUI

The Local Controller in each crate needs to be able to publish information about its crate. For this purpose we will run a dedicated IS server [4] for the L1Calo system.

This should contain the following information:

• for each module in the full configuration, a status block with entries indicating if the module is actually present, whether its links to other modules are up, detailed error counts and any other useful data.
• for each crate in the full configuration, a status block with entries indicating if the crate is currently enabled, and summaries of error counts from modules within the crate.
• from each PPM, the rate histogram for each channel (is this too much data to ship around? Perhaps each crate just publishes a limited amount of processed information?).
• other histograms from each crate?

We will almost certainly want to be able to specify run control parameters to the run controllers - especially for calibration runs. The standard way to do this is via L1Calo specific panels in the Integrated GUI (IGUI). Such panels, written in Java, can set and display run parameter variables in our IS server. These can be read by the run controllers before they execute each transition.

We should also provide an IGUI panel to display the status information read from each module and summarised for each crate.