Here are the classes, structs, unions and interfaces with brief descriptions:

[detail level 12]

anonymous_namespace{AsciiSimulator_generator.cc}
art
EventReporterOutput	An art::OutputModule which does nothing, but reports seen events and their fragments. This module is designed for debugging purposes, where writing events into ROOT files or sending events down stream is not necessary
artdaq	The artdaq namespace
NthEventTransfer	Demonstration TransferInterface plugin showing how to discard events Intended for use in the transfer_to_dispatcher case, NOT for primary data stream!
demo	Namespace used to differentiate the artdaq_demo version of GetPackageBuildInfo from other versions present in the system
ASCIIDump	An art::EDAnalyzer meant for decoding demo::ASCIIFragment objects
CheckIntegrity	Demonstration art::EDAnalyzer which checks that all ToyFragment ADC counts are in the defined range
RootApplication	Provides a wrapper for displaying ROOT canvases
ToyDump	An art::EDAnalyzer module designed to display the data from demo::ToyFragment objects
WFViewer	An example art analysis module which plots events both as histograms and event snapshots (plot of ADC value vs ADC number)
GetPackageBuildInfo	Wrapper around the demo::GetPackageBuildInfo::getPackageBuildInfo function
AsciiSimulator	Generates ASCIIFragments filled with user-specified ASCII strings
ToySimulator	ToySimulator 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
CommandPacket	Struct defining UDP packet used for communicating with data receiver
UDPReceiver	An artdaq::CommandableFragmentGenerator which receives data in the form of UDP datagrams
MisbehaviorTest	A test RoutingManagerPolicy which does various "bad" things, determined by configuration
NthEvent	An art::EDFilter module that passes one out of N events
ToyHardwareInterface	JCF, 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