It's MOOT

LAT Configuration TIM 8/15/05

J. Bogart

Goals and approach

Database design

Use cases

What next?

Modes of Operation Tracking

Goals and Approach

MOOT's primary tasks for October 1st are to track configurations of the

LAT– consisting of register settings, input to parts of FSW code such as

CAL pedestals for the Event Filter, charge calibration parameters, etc. –

and to provide some help in creating and uploading them.

At the lowest level, a configuration consists of a large number of atomic

quantities, such as register settings, but this representation should only

be resorted to when absolutely necessary.

Flight software concerned with creating and uploading configuration

files tends to group the atomic quantities one way; people using the

LAT for some particular purpose, another.

Translation

Part of MOOT's job is to translate between the two views.

This xml file represents both.

FSW inputs

Delegates

Each parm should correspond

to a source file (needs work)

Database design

MOOD will have primary tables with a row for each instance of the fundamental objects: configs, FSW input files and

parameters. One more primary table is needed for history. It

will gain a row each time a new config upload is requested. These tables are known as Configs, FSW_input, Parameters and History.

Secondary tables Config_FSW and FSW_Parm are needed to keep track of relations between the objects in the primary tables and to store information about types of, e.g. FSW inputs (FSW_class).

History table

Configs table

FSW_input table

Secondary tables

Use cases

Activate pre-existing config – see below

Find config constituents – easy

Find active config by time – easy

Add parm (precursor) file – rdbGUI-like

Create config – for Oct. 1 an entirely offline process. MOOT might provide some help

Assume....

All (precursor) parameter files exist and have been registered in the Parameters table

All FSW inputs have been constructed and entered in FSW_input.

FSW inputs have been transformed to binaries, entered in FMX Logical table.

Entry in Configs exists; secondary tables are also up to date.

Activate (approximate)

MOOT queries FMX – binaries uploaded?

If not,

Report missing binaries to LICOS

LICOS reformats into packets, uploads

Informs MOOT, FMX when complete

LICOS selects files via telecommand

When complete, LICOS invokes MOOT service to update History, relay to FMX

What next?

Complete and correct parameters description

Pin down handling of LATC master config.

Find a home for parameter source files (precursors to FSW_input files)

Close the loop: analysis outputs →precursors

Think through inter-db issues

Write the thing!

More details

Go to MOOT index: http://www.slac.stanford.edu/exp/glast/ground/notes/moot/

Follow link “Report for Aug. 11” for most material in this talk

Follow link “Delegates” to see the xml file excerpted in early slides.

2005-08-12T16:03:22