|
Size: 1314
Comment:
|
Size: 1517
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| == The chain == | == The processor chain == |
| Line 15: | Line 15: |
| || step || Processor name || Data output type || Default collection name || | || step || Processor name || Data output type || Default collection name || Conditions objects needed || |
| Line 22: | Line 22: |
== Conditions processing == For the chain to work several conditions objects are needed, although for now they may be implemented as processor parameters. |
The objective
The plan is: create a MarlinTPC processor chain that completely reflects the MultiFit reconstruction chain.
Use data taken with the MediTPC.
The processor chain
The first thing you need is the raw data from your detector. This LCIO file might have a single collection inside of the type Tracker'Raw'Data with the default name 'TPCRawData'.
In a table like fashion:
step |
Processor name |
Data output type |
Default collection name |
Conditions objects needed |
1. Data conversion |
TrackerRawDataToDataConverterProcessor |
TrackerData |
TPCConvertedData |
|
Pedestal Calculation |
PedestalCalculator |
LCGenericObject |
TPCPedestal |
|
2. Pedestal Subtraction |
PedestalSubtractorProcessor |
TrackerData |
TPCData |
|
3. Pulse finding |
PulseFinderProcessor |
TrackerPulse |
TPCPulses |
|
4. Channel mapping |
ChannelMapperProcessor |
TrackerPulse |
TPCPulsesMapped |
|
5. Hit finding |
? |
??? |
??? |
Conditions processing
For the chain to work several conditions objects are needed, although for now they may be implemented as processor parameters.