sTGC StripSegmentTool: Fix calculations for segments and infinte_p track && Fix the arrangement of 8 bit RIndex
Fix the defination of infinte_p track:
- the defination of which in code didn't agree with the note written by NSW Trigger Processor Group, in page 4 of the attanched fileNSW_SectorLogic_InterfaceSpec.pdf, the brief description could be seen in slides 16, https://indico.cern.ch/event/1128868/contributions/4789388/attachments/2411428/4126440/2022-03-18%20sTGC%20Trigger%20Simulation%20%28Overlay%29.pdf
- morever, that one in code was unreasonable, due to the average point had been effected by the deflection of the magnetic field, not suitable to represent for the infinte_p track
- hence, the logic in the note has been implemented, using the line between IP and the first centroid in that corresponding bandId to represent the infinte_p track
Fix calculations for segments:
- the previous calculation is only right in very special case, the details and fixing logics could be seen in slides 16, https://indico.cern.ch/event/1128868/contributions/4789388/attachments/2411428/4126440/2022-03-18%20sTGC%20Trigger%20Simulation%20%28Overlay%29.pdf, that is, use the vector operation, also simplifying the overall calculation process
Fix the arrangement of 8 bit RIndex:
- also in the attanched file in the 1st point, page 3 wrote, the 0 index should be assigned for the lowest radial bin, and the track exceeding the detector envelope should be abandoned without rindex, while the code assigned the tracks, whose r smaller than rmin, as 0 index
- moreover, in that wrong logic, the last, second-to-last, third-to-last rslice bin would be assigned the same rindex of 255, and the track exceeding the detector envelope would also be assigned the rindex with 0 or 255
- those are fixed by removing the traks exceeding the detector spacial range firstly, and shifting rindex arrangement by 1 to the normal logics, one comment said the loop would be broken in 255-256, just due to the last bin with 256 exceeded the range ([0, 255]) of unit_8 before, which is fixed now
And the redundancy code will be removed once validations for the strips trigger is done compeletely, thanks for the review