Notes of EMU Hardware Alignment meeting, 2/15/07 ------------------------------------------------ Present: Oleg, Jim B., Duncan, Jeff, Valeri A., Samir, Marcus 1) Sensor naming conventions: - Marcus presented an updated view of the alignment data flow from online to offline via DBs and root files. He stresses that the new sensors names should be used throughout all of the data flow. Jim points out that the root file maker should also access some online DB to determine good and bad alignment runs which isn't explicitly shown in the data flow diagram. Nobody voices any objections to the definition of the names so far. New names are implemented in COCOA for ME+2 SLM2 model. (see slides) - Samir shows progress on implementing names in root files. Root files provide sensor data in event-by-event format and also a histogram for each sensor for quick checks. Currently creating root file for MTCC2 DCOPS data using final sensor names. (see slides) - Xiaofeng couldn't make the meeting. Hasn't started to implement new names in analog readout. Valeri says that this could be done within a week. However, this week might come only after the hardware installation. We expect a progress update on this implementation at the next software meeting (after CMS week). - Jim hasn't updated names, yet, either, but claims that this can be done quickly within a week or two. We expect an update on progress at the next software meeting. - Valeri says that the implementation should be no problem for his DQM code. - We agree that the implementation of new names should be finished within a month across the whole system. Marcus urges everyone to check NOW if the names as defined in the "authoritative list" work in everyone's datastream so that we don't have to change again since this change affects five different places and various people. 2) Update on Data Quality monitoring - Valeri A. Valeri wasn't ready to present, yet. He will present his data analysis which is related to DQM at the next hardware meeting; i.e. before CMS week. 3) Discussion on DCS plans It was unclear to the group what the scope of DCS is for alignment; just "start, pause, abort" of the DAq and monitoring of hardware, e.g. LV, or also checks on the quality of data, e.g. DCOPS profiles and fits? Marcus suggests that Texas A&M could maybe take charge here since they already expressed interest in the latter aspect. Oleg will compile a list of ME alignment parameters that should be checked by DCS and will present at the meeting. He will also contact Gervasio who is in charge of DCS for the entire Muon alignment system and will report back.