What is mootCore? And what isn't it?
mootCore is a package containing the class MootQuery and some utility classes. MootQuery provides all the database queries to the MOOT (configuration and, someday,also calibration) metadata database needed by Online and Offline applications. Applications which add or modify database entries also need the services provided by another package, MOOT. Gleam only needs read access so only mootCore is of interest here. Supported queries include
/**
Store a list of structures in @info argument concerning configs
which satisfy cuts on status, instrument and mode. They're sorted
in ascending order by key. Return value is count of Configs
satisfying the cuts.
*/
unsigned getConfigInfo(std::vector<ConfigInfo>& info,
const std::string& status="CREATED",
const std::string& instr="LAT",
const std::string& mode="");
/** Given fmx logical id for a latc master, look up associated
parameter files (latc source) and return a little structure
of information about each.
*/
bool getParmsFromMaster(unsigned fmxMasterKey,
std::vector<ParmOffline>& parms);
and many more.
mootCore is not a Gaudi package (can't be since it's used by Online); it knows nothing about TDS, conversion services, etc.
OktoberTest
The immediate goal is to make the LATC GEM configuration available to Gleam in a manner somewhat similar to the way calibrations are currently handled - merely "somewhat" because the configuration information itself will not be stored in the TDS. Instead, clients will be given a file path (or paths, since information which belongs together in the client's view might be stored in several source files) and will take responsibility themselves for parsing the information (as Martin's Trigger code already does).