org.hps.record and its sub-packages use the FreeHep Record module to implement a flexible record processing
backend.See: Description
| Interface | Description |
|---|---|
| LCSimEventBuilder |
This is an interface that should be implemented by classes which build LCSim events from EVIO raw data.
|
| RecordProcessor<RecordType> |
This is a generic interface for event processing which implements hooks for starting the job, starting a new run,
processing individual records, ending a run and ending a job.
|
| Class | Description |
|---|---|
| AbstractLoopAdapter<RecordType> | |
| AbstractRecordLoop<RecordType> | |
| AbstractRecordProcessor<RecordType> |
An abstract implementation of
RecordProcessor with "no operation" method implementations. |
| AbstractRecordQueue<RecordType> |
Implementation of AbstractRecordSource using a dynamic queue that can receive events "on the fly", e.g.
|
| StandardCuts |
| Exception | Description |
|---|---|
| EndRunException |
An
Exception thrown when end of run occurs in event processing. |
| MaxRecordsException |
Exception thrown when maximum number of records is reached.
|
| RecordProcessingException |
This is a generic error type for exceptions that occur during event processing.
|
org.hps.record and its sub-packages use the FreeHep Record module to implement a flexible record processing
backend. Its current primary usage is providing the record processing chain for the HPS Monitoring Application, but
it can be used stand-alone outside of that framework. The primary class for user interaction is the
CompositeLoop class which implements a record loop that can convert
EtEvent objects to EvioEvent objects and then finally build LCSim event, or
EventHeader objects from the EVIO, using a series of adapter classes on the loop. The loop implementation
is flexible so that it may be configured to use an ET server, an EVIO file or an LCIO file for the record source.
The CompositeLoopConfiguration class should be used to configure the loop by the user.Copyright © 2019. All rights reserved.