A brief overview of EM calibrations

Eduardo do Couto e Silva and Joanne Bogart

I&T SVAC/SAS, Oct 29 , 2002

Data

  1. The calibration list is NOT the same as the functional tests list, the former is only a subset of the latter and it has been defined in LAT-MD-00446-04.

  2. There are two ways of producing calibration data: either via EGSE python scripts (relevant to this meeting) and SAS scripts (IDL procedures, root macros or something else)

  3. The  EM calibration list contains a preliminary description of each type of calibration

Metadata

  1. There is a preliminary  definition of the metadata required for every calibration dataset.

  2. For the moment we expect this metadata to be produced in an ASCII file so that it can be loaded with the dataset in the database. For the future we plan to implement an interface using XML files. 

  3. We have already implemented a simple example of the table structure and individual records with some  instructions for browsing the metadata.

Infrastructure

  1. There is an interface developed by SAS that will load all calibration data and corresponding metadata into a mySQL database. Procedures for data loading are expected not to be linked to the GAUDI infrastructure so that it minimizes the burden on users. Users may have a "READ ONLY" or "WRITE NEW RECORDS" access , but will not be allowed to modify existing records in the database. For the EM, SAS/I&T will take care of the database loading.

  2. There is an interface developed by I&T that will load the calibration data into ORACLE and provide web access for a limited set of queries, with the purpose of monitoring activities during I&T. This interface will also produce automated reports whose format is TBD. 

What does I&T expect from subsystem people writing scripts (EGSE or SAS) ?

  1. You deliver one tested script and one reference dataset for each calibration item in the EM calibration list

  2. You provide a simple documentation that includes, among other things, data format and algorithm description (see example)

  3. You deliver scripts the produce an output format the agrees with our definition of metadata (please fell free to provide comments to our example)