Collaboration diagram for Managers:
|
Classes | |
| class | atm::AAerosolSQLManager |
| Manager for aerosol portion of atmospheric monitoring database. More... | |
| class | atm::ACloudSQLManager |
| Manager for cloudy portion of atmospheric monitoring database. More... | |
| class | atm::ALidarSQLManager |
| Manager for lidar portion of atmospheric monitoring database. More... | |
| class | atm::AManagerRegister |
| Singleton MangerRegister for the Atmosphere. More... | |
| class | atm::AMolecularSQLManager |
| Manager for molecular portion of atmospheric monitoring database. More... | |
| class | atm::AOverallQualitySQLManager |
| Manager for aerosol portion of atmospheric monitoring database. More... | |
| class | cdet::CManagerRegister |
| Singleton MangerRegister for MARTA. More... | |
| class | cdet::CModelsXMLManager |
| Manager for MARTA station description in XML "model" files. More... | |
| class | cdet::COverrideXMLManager |
| Manager for SD description in XML "override" files. More... | |
| class | cdet::CStationListManager |
| Common implementation of the station list manager. More... | |
| class | cdet::CStationListXMLManager |
| Manager for MARTA description in XML station lists. More... | |
| class | fdet::EventPointingManager |
| reads the telescope point from the current Fd event More... | |
| class | sdet::EventStationPositionsManager |
| Manager to retrieve station positions from the raw event. More... | |
| class | fdet::FCalibSQLManager |
| Manager for FD calibration and monitoring data residing in MySQL database. More... | |
| class | fdet::FdAlwaysUpManager |
| default FD up time manger: always on ! More... | |
| class | fdet::FdChannelMappingManager |
| Class to manage Fd camera channel-pixel mapping. More... | |
| class | fdet::FdUpTimeFileManager |
| Class to manage Fd UpTime ROOT files. More... | |
| class | fdet::FdUpTimeSQLManager |
| class | fdet::FFixCalibManager |
| Manager for FD calibration with fixed constants. More... | |
| class | fdet::FFixOpticalEfficiencyLossManager |
| Manager for FD optical efficiency correction with fixed constants. More... | |
| class | fdet::FManagerRegister |
| Singleton MangerRegister for the FD. More... | |
| class | fdet::FModelsXMLManager |
| Manager for FD description in XML "model" files. More... | |
| class | fdet::FOpticalEfficiencyLossSQLManager |
| Manager for FD optical efficiency correction constants read from SQL database. More... | |
| class | fdet::FSimulationCalibManager |
| Manager for FD calibration with a fixed constant. More... | |
| class | fdet::FTelescopeListXMLManager |
| Reads data from XML file(s) containing data unique to telescopes and eyes (eg. positions, orientations, commission times, and so forth). More... | |
| class | det::ManagerRegister |
| Register for detector description managers. More... | |
| class | rdet::MonitoringSQLManager |
| Manager to access monitoring data. More... | |
| class | rdet::RAntennaTypeXMLManager |
| Manager for RD description in XML "AntennaType" files. More... | |
| class | rdet::RBadStationSQLManager |
| Manager for RD Bad Stations. More... | |
| class | rdet::RBeaconSQLManager |
| Manager for RD description of Station-Channels in SQL DB. More... | |
| class | rdet::RChannelSQLManager |
| Manager for RD description of Station-Channels in SQL DB. More... | |
| class | rdet::RHardwareProfileXMLManager |
| Manager for RD description in XML "HardwareProfile" files. More... | |
| class | rdet::RManagerRegister |
| Singleton MangerRegister for the RD. More... | |
| class | rdet::RModelsXMLManager |
| Manager for RD description in XML "model" files. More... | |
| class | rdet::RSimulationStationListManager |
| Manager for RD description in SQL or XML station lists. More... | |
| class | rdet::RStationListManager |
| Common implementation of the station list manager. More... | |
| class | rdet::RStationListSQLManager |
| Manager for SD description in SQL station lists. More... | |
| class | rdet::RStationListXMLManager |
| Manager for Radio description in XML station lists. More... | |
| class | sdet::SDenseStationListXMLManager |
| Manager to return station positions for array defined in shower coordinates. More... | |
| class | sdet::SManagerRegister |
| Singleton MangerRegister for the SD. More... | |
| class | sdet::SModelsXMLManager |
| Manager for SD description in XML "model" files. More... | |
| class | sdet::SStationListManager |
| Common implementation of the station list manager. More... | |
| class | sdet::SStationListSQLManager |
| Manager for SD description in SQL station lists. More... | |
| class | sdet::SStationListXMLManager |
| Manager for SD description in XML station lists. More... | |
| class | sdet::T2LifeFileManager |
| Class to manage T2Life files. More... | |
| class | sdet::T2LifeROOTFileManager |
| Class to manage Sd life time ROOT files. More... | |
| class | det::VManager |
| Interface for detector managers. More... | |
| class | det::VManagerBuilder |
| class | det::VSQLManager |
| Interface for detector managers that use MySQL. More... | |
| class | det::XManagerRegister< DetectorInfo > |
| Singleton Template MangerRegister for arbitrary detector type (X stands for an unknown detector type, be it M, S, F, for instance). More... | |
| class | det::XXMLManager< Info > |
| General Manager for reading detectors descriptions in XML files. More... | |
Files | |
| file | ManagerBuilderRegisterEntry.h |
Detailed Description
Requests for information about the detector are sent from the Detector User Interface (see det::Detector) to a collection of so-called managers, each of which is designed to deal with a particular data format. A manager is a class which inherits from the det::VManager interface class, and implements the purely virtual data retrieval methods defined in det::VManager.Once a manager locates the requested data, it returns it to the user interface, where it is internally cached so that if another request is made for the same data, it can be more quickly retrieved. The user interface may also perform some simple analysis and/or packaging of the data in to a convenient object before returning it to the interface. Managers are collected into det::ManagerRegister's, which are also concrete implementations of det::VManager.The figure below illustrates the general idea. The left side of the figure depicts the hierarchy of objects in the Detector user interface. These objects relay requests for data to a registry of managers (right) which handle multiple data sources and formats. The small plug labeled "Manager Interface" represents the det::VManager interface class.
Currently there are three different ManagerRegister's in the Offline software:
- atm::AManagerRegister for atmospheric monitoring data
- fdet::FManagerRegister for FD-related information
- sdet::SManagerRegister for SD-related information
<FDetectorManagerList> <manager> FdChannelMappingManager </manager> <manager> FdAlwaysUpManager </manager> <manager> FTelescopeListXMLManager </manager> <manager> FModelsXMLManager </manager> <manager> FCalibSQLManager </manager> </FDetectorManagerList>ManagersRegisters implement a "Chain of responsibility". This means when a request for data is sent to a det::ManagerRegister, each manager in the list is given the opportunity to respond to the request in the order the managers are listed in the configuration file. With this approach, it is possible to implement more than one manager for a particular sort of data. The manager appearing first in the det::ManagerRegister configuration will take precedence over the manager appearing later. In this way, a special manager can override data from a general manager. For example, a user can decide to use a database for the majority of the description of the detector, but override some data by writing them in an XML file which is interpreted by the special manager. To give a concrete example, if one wanted to replace the calibration constants returned by the fdet::FCalibSQLManager for a particular telescope, one could write a special manager called, say FCalibOverrideManager, and then include it in the FDetectorMangerList in a position before the fdet::FCalibSQLManager:
<FDetectorManagerList> <manager> FdChannelMappingManager </manager> <manager> FdAlwaysUpManager </manager> <manager> FTelescopeListXMLManager </manager> <manager> FModelsXMLManager </manager> <manager> FCalibOverrideManager </manager> <manager> FCalibSQLManager </manager> </FDetectorManagerList>You can find the names of the default det::ManagerRegister config files by looking in the default bootstrap files:
path_to_offline_install/share/auger-offline/config/standardFdIdealDetConfig.xml path_to_offline_install/share/auger-offline/config/standardFdRealDetConfig.xml path_to_offline_install/share/auger-offline/config/standardSdIdealDetConfig.xml path_to_offline_install/share/auger-offline/config/standardSdRealDetConfig.xml
In these files, you will find a configLink for the three managers mentioned above, with configLink id's called SManagerRegister, FManagerRegister and AManagerRegister. The SManagerRegister link can be found in the SD configuration file. Both F- and AManagerRegister are referenced in the FD configuration.See the fwk::CentralConfig for more information about configLinks and bootstrap files.