GLAST Large Area Telescope T&C Database Management 1 July 2005 Bryson Lee blee@slac.stanford

1. Gamma-ray Large Area Space Telescope GLAST Large Area Telescope T&C Database Management 1 July 2005 Bryson Lee blee@slac.stanford.edu 650-926-2866

2. Topics • Database Format(s) • Available Content • Missing Content • Content Producers • Tools • Content Consumers • Management Strategy

3. Database Format(s) • XML representation • .catc / .cath files in CVS repository of each FSW constituent. • engineering-unit (EGU) conversions in LATTE schemata • Python representation • class definitions for each command & telemetry mnemonic, part of FSW's “VPI” package. • Oracle representation • Set of relational tables in SLACDEV / SLACPROD Oracle instances. • Flat-file representation • Text files with “.dbx” file extension. • Format (theoretically) governed by DFCD. • LAT deliverable to GLAST project.

4. Available Content • Record types (with dbx monicker): • Subsystem names for grouping mnemonics (ssi) • Telemetry mnemonics (tlm) • Analog polynomial EU conversions (alg) • Discrete EU conversions (dsc) • Arbitrary EU conversions (xpr) • look-up table generated from a mathematical expression • Limits on mnemonic values (lim) • Attributes of CCSDS telemetry packets (map) • Associations of packet contents to mnemonics (pkt) • Command mnemonics (cmd) • User-specified command data fields (fld) • Discrete values for command data fields (sub)

5. Missing Content • Command functional verifications / responses • Telemetry mnemonic units (determined by EU conversion algorithm) • Default telemetry “presentation” format • How to represent the mnemonic value for display • Something like FORTRAN formatted-io specifier (“F6.2”), or C printf format specifier (“%6.2f”) • EU-to-raw conversions for command mnemonic data fields.

6. Content Producers • Flight Software • telemetry & command mnemonic definitions • database content intimately tied to FSW code • records derived from XML representation • Subsystems / Systems • Ground limits • Command functional verifications • LAT direct / hardware telemetry mnemonics • Engineering unit conversions • CHS • “Derived” records (map, ssi) • “Value Added” tlm / cmd mnemonics • Alternative representations to assist operations

7. Tools • LCAT (maintained by FSW) • generates flat-file and Python representations from XML representation. • also generates C-language structure definitions for FSW • dbxodb (GOTS ITOS component) • compiles .dbx files into a form directly usable by ITOS. • can generate HTML documentation of .dbx content • mkdb.sh (maintainted by CHS) • wrapper script for dbxodb that generates missing map/pkt/tlm/ssi records and merges ISOC “value-added” content with FSW-supplied content • useDbx.py (maintained by CHS) • generates SQL statements to insert .dbx content into Oracle

8. Content Consumers • FSW • C structures from LCAT compiled into FSW constituents • FSW Test • Python representation from LCAT used by LTX script engine • I&T Online • Python representation from LCAT used by LATTE5 • CHS • flat-file representation used to “stoke” Oracle representation and configure local ITOS installations • Oracle representation used for CHS monitoring, Mission Planning, Timeline Reconciliation, etc. • MOC • flat-file representation used to configure ITOS for all LAT operations

9. Strategy • CHS team is focal point for integrating database content and delivering updates. • Need to evolve tools and processes for: • Entering redlines to contents • Generating and tracking database releases