artdaq  v3_07_02
Class Hierarchy
This inheritance list is sorted roughly, but not completely, alphabetically:
[detail level 123]
oCart::AnalyzersConfig
oCFragCounter_test::Apply_id
oCFragCounter_test::ApplyWithOffset_id
oCartdaq::art_config_fileArt_config_file wraps a temporary file used to configure art
oCartdaq::artdaqappClass representing an artdaq application. Used by all "main" functions to start artdaq.
oCart::ArtdaqInput< U >This template class provides a unified interface for reading data into art
oCArtdaqSharedMemoryServiceInterfaceInterface for ArtdaqSharedMemoryService. This interface is declared to art as part of the required registration of an art Service
oCartdaq::BoardReaderCoreBoardReaderCore implements the state machine for the BoardReader artdaq application. It contains a CommandableFragmentGenerator, which generates Fragments which are then sent to a DataSenderManager by BoardReaderCore
oCBOOST_AUTO_TEST_CASE_FIXTURE
oCartdaqtest::BrokenTransferTestA class which simulates several failure modes for TransferPlugins such as sender pause/restart and receiver pause/restart
oCCommandableFragmentGenerator_t::BufferMode_id
oCCommandableFragmentGenerator_t::BufferMode_KeepLatest_id
oCCommandableFragmentGenerator_t::BufferMode_MultipleIDs_id
oCCommandableFragmentGenerator_t::CircularBufferMode_id
oCCommandableFragmentGenerator_t::CircularBufferMode_MultipleIDs_id
oCartdaq::CommandableCommandable is the base class for all artdaq components which implement the artdaq state machine
oCartdaq::CommanderInterfaceThis interface defines the functions used to transfer data between artdaq applications
oCartdaq::HostMap::ConfigTemplate for the host_map configuration parameter.
oCartdaq::TransferInterface::ConfigConfiguration of the TransferInterface. May be used for parameter validation
oCartdaq::artdaqapp::ConfigConfiguration of artdaqapp. May be used for parameter validation
oCartdaq::RoutingReceiver::ConfigAccepted configuration parameters for RoutingReceiver
oCConfig
oCArtdaqSharedMemoryService::ConfigAllowed Configuration parameters of NetMonTransportService. May be used for configuration validation
oCart::ConfigRequired configuration for art processes started by artdaq, with artdaq-specific defaults where applicable
oCart::RootDAQOut::Config
oCartdaqtest::BrokenTransferTest::ConfigConfiguration parameters for BrokenTransferTest
oCart::RootNetOutput::ConfigAllowed Configuration parameters of NetMonTransportService. May be used for configuration validation
oCartdaq::GenericFragmentSimulator::ConfigConfiguration of the GenericFragmentSimulator. May be used for parameter validation
oCartdaq::PortManager::ConfigConfiguration of PortManager. May be used for parameter validation
oCartdaq::DataSenderManager::ConfigConfiguration of DataSenderManager. May be used for parameter validation
oCartdaq::RequestReceiver::ConfigConfiguration of the RequestReceiver. May be used for parameter validation
oCartdaq::RequestSender::ConfigConfiguration of the RequestSender. May be used for parameter validation
oCartdaq::SharedMemoryEventManager::ConfigConfiguration of the SharedMemoryEventManager. May be used for parameter validation
oCartdaq::TokenReceiver::ConfigConfiguration of the TokenReceiver. May be used for parameter validation
oCartdaq::CommanderInterface::ConfigConfiguration of the CommanderInterface. May be used for parameter validation
oCartdaq::CommandableFragmentGenerator::ConfigConfiguration of the CommandableFragmentGenerator. May be used for parameter validation
oCFragCounter_test::Construct_id
oCartdaq::DataReceiverCoreDataReceiverCore implements the state machine for the DataReceiver artdaq application. DataReceiverCore receives Fragment objects from the DataReceiverManager, and sends them to the EventStore
oCartdaq::DataReceiverManagerReceives Fragment objects from one or more DataSenderManager instances using TransferInterface plugins DataReceiverMaanger runs a reception thread for each source, and can automatically suppress reception from sources which are going faster than the others
oCartdaq::DataSenderManagerSends Fragment objects using TransferInterface plugins. Uses Routing Tables if confgiured, otherwise will Round-Robin Fragments to the destinations
oCDDSDataReaderListener
oCartdaq::detail::DefaultFragmentTypeTranslatorDefault behavior for experiment-specific customizations in SharedMemoryReader
oCartdaq::DataSenderManager::DestinationsConfigConfiguration for transfers to destinations
oCEDAnalyzer
oCEDFilter
oCEDProducer
oCshared_memory_reader_t::end_of_data_id
oCanonymous_namespace{xmlrpc_commander.cc}::env_wrapWrapper for XMLRPC environment construction/destruction
oCart::RootDAQOut::Config::FileNameSubstitution
oCart::FiltersConfig
oCshared_memory_reader_t::first_event_id
oCartdaq::detail::FragCounterKeep track of the count of Fragments received from a set of sources
oCFragmentGenerator
oCartdaq::FragmentReceiverManagerReceives Fragment objects from one or more DataSenderManager instances using TransferInterface plugins DataReceiverMaanger runs a reception thread for each source, and can automatically suppress reception from sources which are going faster than the others
oCartdaq::FragmentStoreElementThis class contains tracking information for all Fragment objects which have been received from a specific source
oCartdaq::GetPackageBuildInfoWrapper around the artdaq::GetPackageBuildInfo::getPackageBuildInfo function
oCartdaq::GlobalsThe artdaq::Globals class contains several variables which are useful across the entire artdaq system
oCCommandableFragmentGenerator_t::HardwareFailure_NonThreaded_id
oCCommandableFragmentGenerator_t::HardwareFailure_Threaded_id
oCartdaq::HostMap::HostConfigEntries in the host_map should have these parameters. May be used for parameter validation
oCartdaq::HostMap
oCCommandableFragmentGenerator_t::IgnoreRequests_id
oCCommandableFragmentGenerator_t::IgnoreRequests_MultipleIDs_id
oCart::RootOutputConfig::KeysToIgnoreThese keys should be ignored by the configuration validation processor
oCart::RootDAQOut::Config::KeysToIgnore
oCRoundRobin_policy_t::LargeMinimumParticipants_id
oCRoundRobin_policy_t::ManyMissingParticipants_id
oCMessHeadThis header is sent by the TCPSocket_transfer to allow for more efficient writev calls
oCmethod
oCRoundRobin_policy_t::MinimumParticipants_id
oCMPRGlobalTestFixtureMasterProductRegistry Test Fixture
oCartdaq::NetMonHeaderHeader with length information for NetMonTransport messages
oCart::NetMonWrapperThis class wraps NetMonTransportService so that it can act as an ArtdaqInput template class
oCshared_memory_reader_t::new_run_id
oCshared_memory_reader_t::new_subrun_id
oCart::RootDAQOut::Config::NewSubStringForApp
oCshared_memory_reader_t::nonempty_event_id
oCFragCounter_test::nSlots_id
oCart::RootDAQOutFile::OutputItem
oCOutputModule
oCOutputModule
oCart::OutputsConfigConfiguration for the outputs block of artdaq art processes
oCart::PhysicsConfigConfiguration of the physics block for artdaq art processes
oCartdaq::PortManagerPortManager attempts to automatically detect interfaces and ports used for the various TCP and UDP sockets used by artdaq
oCart::ProducersConfigArtdaq does not provide any producers
oCartdaq::detail::RequestHeaderHeader of a RequestMessage. Contains magic bytes for validation and a count of expected RequestPackets
oCartdaq::detail::RequestMessageA RequestMessage consists of a RequestHeader and zero or more RequestPackets. They will usually be sent in two calls to send()
oCartdaq::detail::RequestPacketThe RequestPacket contains information about a single data request
oCartdaq::RequestReceiverReceive data requests and make them available to CommandableFragmentGenerator or other interested parties. Track received requests and report errors when inconsistency is detected.
oCartdaq::RequestSenderThe RequestSender contains methods used to send data requests and Routing tokens
oCart::RootDAQOutFile
oCart::RootOutputConfigConfgiguration for ROOT output modules
oCartdaq::detail::RoutingAckPacketA RoutingAckPacket contains the rank of the table receiver, plus the first and last sequence IDs in the Routing Table (for verification)
oCartdaq::RoutingMasterCoreRoutingMasterCore implements the state machine for the RoutingMaster artdaq application. RoutingMasterCore collects tokens from receivers, and at regular intervals uses these tokens to build Routing Tables that are sent to the senders
oCartdaq::RoutingMasterPolicyThe interface through which RoutingMasterCore obtains Routing Tables using received Routing Tokens
oCartdaq::detail::RoutingPacketEntryA row of the Routing Table
oCartdaq::detail::RoutingPacketHeaderThe header of the Routing Table, containing the magic bytes and the number of entries
oCartdaq::RoutingReceiverClass which receives routing tables and prints updates
oCartdaq::DataSenderManager::RoutingTableConfigConfiguration for Routing table reception
oCartdaq::detail::RoutingTokenThe RoutingToken contains the magic bytes, the rank of the token sender, and the number of slots free. This is a TCP message, so additional verification is not necessary
oCartdaq::RequestSender::RoutingTokenConfigConfiguration for Routing token sending
oCartdaq::RTIDDSDDS Transport Implementation
oCCommandableFragmentGenerator_t::SequenceIDMode_id
oCCommandableFragmentGenerator_t::SequenceIDMode_MultipleIDs_id
oCart::ServicesConfigConfiguration of the services block for artdaq art processes
oCart::ServicesSchedulerConfigConfiguration of the services.scheduler block for artdaq art processes
oCSharedMemoryManager
oCartdaq::detail::SharedMemoryReader< getDefaultTypes, FTT >The SharedMemoryReader is a class which implements the methods needed by art::Source
oCShmRTestFixtureSharedMemoryReader Test Fixture
oCCommandableFragmentGenerator_t::Simple_id
oCGenericFragmentSimulator_t::Simple_id
oCNoOp_policy_t::Simple_id
oCRoundRobin_policy_t::Simple_id
oCCapacityTest_policy_t::Simple_id
oCCommandableFragmentGenerator_t::SingleMode_id
oCCommandableFragmentGenerator_t::SingleMode_MultipleIDs_id
oCart::Source_generator< artdaq::detail::SharedMemoryReader< artdaq::Fragment::MakeSystemTypeMap > >Specialize an art source trait to tell art that we don't care about source.fileNames and don't want the files services to be used
oCart::Source_generator< ArtdaqInput< artdaq::TransferWrapper > >Trait definition (must precede source typedef)
oCart::Source_generator< ArtdaqInput< NetMonWrapper > >Trait definition (must precede source typedef)
oCart::SourceConfigConfiguration for the source block of artdaq art processes
oCartdaq::StatisticsHelperThis class manages MonitoredQuantity instances for the *Core classes
oCswig_artdaq
oCanonymous_namespace{genToArt.cc}::ThrottledGeneratorThrottledGenerator: ensure that we only get one fragment per type at a time from the generator
oCTimeoutPerforms registered actions at specified intervals
oCTimeout::timeoutspecSpecification for a Timeout function
oCartdaq::TokenReceiverReceives event builder "free buffer" tokens and adds them to a specified RoutingPolicy
oCartdaq::TransferInterfaceThis interface defines the functions used to transfer data between artdaq applications
oCartdaq::TransferTestTest a set of TransferInterface plugins
oCartdaq::TransferWrapperTransferWrapper wraps a TransferInterface so that it can be used in the ArtdaqInput class to make an art::Source
oCRoundRobin_policy_t::VerifyRMPSharedPtr_id
oCCommandableFragmentGenerator_t::WindowMode_Function_id
oCCommandableFragmentGenerator_t::WindowMode_Function_MultipleIDs_id
oCCommandableFragmentGenerator_t::WindowMode_RequestAfterBuffer_id
oCCommandableFragmentGenerator_t::WindowMode_RequestBeforeBuffer_id
oCCommandableFragmentGenerator_t::WindowMode_RequestEndsAfterBuffer_id
oCCommandableFragmentGenerator_t::WindowMode_RequestInBuffer_id
oCCommandableFragmentGenerator_t::WindowMode_RequestOutsideBuffer_id
\CCommandableFragmentGenerator_t::WindowMode_RequestStartsBeforeBuffer_id