Making Use of MOOT Remotely

MOOT for Offline is comprised of a MySQL database, an archive of configuration-related files, and services which let you access these things. All the information needed for access flows from one environment variable, MOOT_ARCHIVE. This should be defined to point to a suitable directory: /afs/slac.stanford.edu/g/glast/moot/archive-mood if that's accessible; otherwise a local directory. There is one special site-specific file which goes in the archive called myHost.xml. It's described in detail below. Typical remote users will only need to copy a small fraction of the production archive files.

Archive Structure

You can see for yourself by taking a look at the production archive, /afs/slac/g/glast/moot/archive-mood. There are two regular files in the top-level directory and several subdirectories.

Subdirectories

The subdirectories contain archived copies of various kinds of configuration-related files. Exactly which ones you'll need depends on what you plan to do. Most of the subdirectories have a similar structure. They have subdirectories of the form yyyy-mm (e.g. 2008-05). These have subdirectories whose names indicate which kind of object is being archived. For example, the Param/2008-02 has subdirectories latc_GEM_TRG_GEM, latc_TFE_TKR_Strips, and lci_ACD among many others.

SubdirectoryUse
Ancil Ancillary files, such as results from charge-injection calibrations. Input in process of creating configuration; not of interest to most users
CalibSo far unused; some day it will replace the calibration archive
Constit Contains xml representations of certain Flight Software CDM shareables, include filter configurations.
FswIn Contains LATC master files (which MOOT itself has to create). Not of general interest
ParamSo-called "parameter files". The bulk of the archive is taken up with these. Included are LATC source files and lci scripts. Many of these are of potential interest to Offline but others (e.g., anything in a directory whose name is of the form latc_XXX_backup) are not.
Vote Vote files describe intent of a configuration. They probably will be of interest to Gleam if they're not already.
tmpOf no interest whatsoever

Describing the connection

The two top-level files are needed to find the correct MySQL database which matches the archive. connection.xsd is the same for everyone. Just copy the one in the production archive. Contents of myHost.xml depend on

The following should work for a typical off-site user needing to connect to the production database for read only:

<?xml version="1.0" ?>
<connection xsi:noNamespaceSchemaLocation="connection.xsd"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            dbname="mood" write="false" nickname="prod_" >
  <master host="glastDB.slac.stanford.edu" port="0"  />
</connection>

MOOT_ARCHIVE

If you set MOOT_ARCHIVE to the top level of your archive MOOT code will be able to find everything it needs. This can be done where ever you set other site variables (e.g., GLAST_EXT) or, if you're using the IMootSvc interface in Gleam for your Moot access you can set the value in the job option MootSvc.MootArchive, e.g.

  MootSvc.MootArchive="/tmp/myArchive";

To use the SLAC archive this would be

  MootSvc.MootArchive="/afs/slac.stanford.edu/g/glast/moot/archive-mood";
Created: 23 May 2008
Last revised: Friday, 23-May-2008 14:08:04 PDT 		J. Bogart jumping