FPGATrackSimRegionMap.h File Reference

Maps ITK module indices to FPGATrackSim regions. More...

#include "FPGATrackSimMaps/FPGATrackSimPlaneMap.h"
#include <vector>
#include <map>
#include <fstream>

Include dependency graph for FPGATrackSimRegionMap.h:

Go to the source code of this file.

Classes
struct	FPGATrackSimRegionBoundaries
class	FPGATrackSimRegionMap

Detailed Description

Maps ITK module indices to FPGATrackSim regions.

Author

Riley Xu - riley.nosp@m..xu@.nosp@m.cern..nosp@m.ch (rewrite from FTK)

Date

Janurary 7th, 2020 The region map is a text configuration file that defines the regions in FPGATrackSim. A region is roughly an eta/phi slice that handled by the same TP board (??? not quite sure if this is right). The region map delineates the modules in each region based on InDetIdentifier ids.

Region map format:

1. The first line should read towers <NTOWERS> phi <NPHI> where NTOWERS is the number of regions, and NPHI is ???. TODO rename tower to region
2. A list of the region definitions with the below format, seperated by empty lines, in order.

Region definition format:

1. A line with the region number.
2. A line for each detector layer (see FPGATrackSimPlaneMap), which is a space-separated list with the below values.

Line values (i.e. columns):

1. isPixel (1/0) |
2. isEndcap (1/0) } – These identify the detector layer
3. physical layer (see FPGATrackSimPlaneMap) |
4. minimum phi id ] – in this detector layer in this region
5. maximum phi id ]
6. total phi modules – in this detector layer among all regions
7. minimum eta id
8. maximum eta id
9. total eta modules

The min and max ids are the important fields that actually define the boundary of the region, and are inclusive. TODO there is no reason to store total phi/eta module in each region.

Author

Riley Xu - riley.nosp@m..xu@.nosp@m.cern..nosp@m.ch (rewrite from FTK)

Date

Janurary 7th, 2020 See header.

Definition in file FPGATrackSimRegionMap.h.