artdaq_demo  v3_00_01
Class Hierarchy
This inheritance list is sorted roughly, but not completely, alphabetically:
[detail level 12]
oCCommandableFragmentGenerator
|oCdemo::AsciiSimulatorGenerates ASCIIFragments filled with user-specified ASCII strings
|oCdemo::ToySimulatorToySimulator is a simple type of fragment generator intended to be studied by new users of artdaq as an example of how to create such a generator in the "best practices" manner. Derived from artdaq's CommandableFragmentGenerator class, it can be used in a full DAQ simulation, obtaining data from the ToyHardwareInterface class
|\Cdemo::UDPReceiverAn artdaq::CommandableFragmentGenerator which receives data in the form of UDP datagrams
oCdemo::CommandPacketStruct defining UDP packet used for communicating with data receiver
oCEDAnalyzer
|oCdemo::ASCIIDumpAn art::EDAnalyzer meant for decoding demo::ASCIIFragment objects
|oCdemo::CheckIntegrityDemonstration art::EDAnalyzer which checks that all ToyFragment ADC counts are in the defined range
|oCdemo::RootApplicationProvides a wrapper for displaying ROOT canvases
|oCdemo::ToyDumpAn art::EDAnalyzer module designed to display the data from demo::ToyFragment objects
|\Cdemo::WFViewerAn example art analysis module which plots events both as histograms and event snapshots (plot of ADC value vs ADC number)
oCEDFilter
|\CNthEventAn art::EDFilter module that passes one out of N events
oCdemo::GetPackageBuildInfoWrapper around the demo::GetPackageBuildInfo::getPackageBuildInfo function
oCRoutingMasterPolicy
|\Cdemo::MisbehaviorTestA test RoutingMasterPolicy which does various "bad" things, determined by configuration
oCRoutingMasterPolicy
|\Cartdaq::NthEventPolicyAn example RoutingMasterPolicy which redirects every Nth event to a desginated destination. Other events are Round-Robin'ed to the other configured destinations
oCart::Source_generator< artdaq::detail::SharedMemoryReader< demo::makeFragmentTypeMap > >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
oCToyHardwareInterfaceJCF, Mar-17-2016: ToyHardwareInterface is meant to mimic a vendor-provided hardware API, usable within the the ToySimulator fragment generator. For purposes of realism, it's a C++03-style API, as opposed to, say, one based in C++11 capable of taking advantage of smart pointers, etc. An important point to make is that it has ownership of the buffer into which it dumps its data - so rather than use new/delete, use its functions AllocateReadoutBuffer/FreeReadoutBuffer
\CTransferInterface
 \Cartdaq::NthEventTransferDemonstration TransferInterface plugin showing how to discard events Intended for use in the transfer_to_dispatcher case, NOT for primary data stream!