] > Information on the whiteboard after morning meeting of Aug. 8. File contains a list of operating modes, followed by a list of <delegates> (in the MOOT sense; see e.g. http://www.slac.stanford.edu/exp/glast/ground/notes/moot/moot21july05.shtml) and a list of <FSWinputs>. A <delegate> may have arbitrary collections of <parm> and <parmGroup> children; a <parmGroup> may also have <parm> and <parmGroup> children, so the hierarchy under a <delegate> may be to arbitrary depth. The smallest possible number of <parm>s should be used, subject to the following conditions: 1) information belonging to a single <parm> must all be destined for the same FSW input and 2) validity lifetime of all information encompassed in a single <parm> should be approximately the same 3) all information belonging to a single <parm> should come from "the same place". Configuration parameters for LAT housekeeping Configuration for charge injection calibrations. May also be enhanced to handle timing scans. This is the only delegate which allows registers to be set dynamically and repeatedly under program control. Other delegates concerned with registers ask to set them once. Can concatenate descriptions of multiple scans in a single calibration, but there is no easy way to express that here. If calibrations are typically done by running several scans in sequence, it may be a lost cause to try to specify it all here. Would be better to just let CAL_calib take a single value, which is a reference to a file containing all the details. Same would go for ACD and TKR calibrations. Thermal control parameters. Since input values all go into the same FSW file and probably tend to have the same lifetime, just need one <parm> element Does EBM really stand for 'Event Buffer Manager' ? In any case, there isn't much here and it should hardly change. Not sure this belongs here; may belong under PIG Output for this one will be scattered among different LATC output files. Is this contained within a single LATC output, or is it split, e.g., between AEMout and ARCout? Should check that everything here really does end up in GEMout this one was questionable (paranthesized) Couldn't make out the word on the whiteboard Output must be handled by CDM. How many pieces are there? n instances of the parms below. Output for this one will be split among different LATC files; needs to be understood and specified in detail. This was paranthesized. Was it because it's handled by PIG? Will need to change over time. Need to change this to a parmGroup with individual values for readout controller masks (out='ARCout') and FE masks (out='AFEout'). Veto DAC register and veto vernier register? PHA threshold registers Seems to correspond to Max PHA enable register Output for this one will be split among different LATC files; needs to be understood and specified in detail. This was paranthesized. Was it because it's handled by PIG? Will need to change over time. Should change to a parmGroup with individual <parm> children for Output for this one will be split among different LATC files; needs to be understood and specified in detail. This was paranthesized. Was it because it's handled by PIG? Will need to change over time Will need to change over time This delegate is different from the others in that it is not handled by FMX; hence there is no associated <FSWinput>. MOOT probably will not be involved in establishing a particular state, but it might be involved in tracking the state. For several objects a choice must be made whether to use the primary or redundant unit (or neither or both, if it makes sense). List below is not exhaustive. Which ones are on. Maybe should have a separate parameter for each Same comments as for TEMSpower: keep track of which are on. May want separate parameter for each EPU. An <FSWinput> represents one of the kinds of files to be input to a FSW service. These should almost map 1-1 to files output by FSW. LATC outputs 15 different kinds of files, by last count. LCI outputs one kind, and CDM will ultimately transform all other kinds of input (housekeeping, event filter parameters,...) Single output for LAT Housekeeping parameters For ACD readout controller registers For ACD front-end registers For Trigger Interface Control registers For Calorimeter Cable Controller registers For Calorimeter Readout Controller registers For Calorimeter Front-End registers For Tracker Cable Controller registers For Tracker Readout Controller registers Guessing this is for Tracker splits For Tracker Front-End registers For Tracker Digital Converter registers FSW output binary contains values for one each of the register classes (GEM, AEB, ARC, AFE,...) This has no corresponding MOOT source file; it is created when LATC is asked to make a (LATC) master config file, so perhaps should change name to master CAL charge injection config. TKR charge injection config. ACD charge injection config. Single output for Thermal Control parameters Need to check that there really is such a thing as an output file dedicated to EBM