1 / 8

A Object Oriented Code for FPD Trigger Studies

Proton ID 03/13/2003. A Object Oriented Code for FPD Trigger Studies. Wagner de Paula Carvalho Universidade do Estado do Rio de Janeiro (UERJ). MI Rejection Studies - W. Carvalho. Overview.  Create a FPD_Hits class to hold all trigger information

kylynn-jenkins
Download Presentation

A Object Oriented Code for FPD Trigger Studies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proton ID 03/13/2003 A Object Oriented Code for FPD Trigger Studies Wagner de Paula Carvalho Universidade do Estado do Rio de Janeiro (UERJ) Proton ID

  2. MI Rejection Studies - W. Carvalho Overview Create a FPD_Hits class to hold all trigger information  FPD_Hitsinherits fromFPD_Particle: class FPD_Hits : public FPD_Particle {...} This allows us to easily use the FPD tracking program (by Barreto, Oguri & Carley) to study the trigger patterns and generate new sets of trigger equations Proton ID

  3. MI Rejection Studies - W. Carvalho FPD_Particle Review A FPD_Particleobject propagates across the Tevatron lattice and has the following member variables: FPD_Vector vec : x,y,z - spatial coordinates xs,ys - slopes of momentum inxzandyzplanes zs =  int charge double mass double beam momentum Proton ID

  4. MI Rejection Studies - W. Carvalho FPD_Hits Member variables: string arm_flag[4] : array to hold the name (UP,DOWN,IN,OUT) ofthe hit arm for each FPD station FPD_Vector initial_particle_vector : save initial state FPD_Vector FPD_Vector potn_particle_vector : save FPD_Vectors at FPD station n intpotn_hits[6] : array to hold fiber hits map (U,U’,X,X’,V,V’) at station n intpotn_hits[3] : array to hold segment hits map (U,X,V) at station n n = 1  A1,P1 ; n = 2  A2,P2 ; n = 3  D1 ; n =4  D2 ; Proton ID

  5. MI Rejection Studies - W. Carvalho FPD_Hits Member functions (methods): FPD_Hitsuses methods from:  FPD_Particle : as it inherits from this class, a FPD_Hits propagates as a FPD_Particle ;  FPDdetectorclassfrom Mike Martens with a few modifications (for the sake of uniformity) ; Some code of myself . Proton ID

  6. MI Rejection Studies - W. Carvalho A few more FPD_Hits features A few modifications were made toFPD_Particle’s method Propagate, to remove hard-wired values of beam widths and pots positioning ; They were moved to the header file BeamPotsParameters.hpp ; Detector related methods like: accelerator  detector coordinate transformation, position  fiber hits and fiber hits  segment hits, were kept in a separate header,FPD_Detector.hpp ; Proton ID

  7. MI Rejection Studies - W. Carvalho Testing the code To test the code I’m using the trigger equations tabulated by Mike Martens (see http://waldo.fnal.gov/~martens/cvs/fnal/fpd/equations/). There are 3 equation flavors: PU, PI and DI. The other spectrometers’ equations (PD,PO,AU,AD,AI,AO) are equal to some of these; PU equations have been more exhaustively used to test the program. Apparently, all original equations keep passing when beam energy is set to 1000GeV/c, as used by Martens. Need to perform more “calibration” tests, including for pbeam = 980GeV/c, as some recent changes to the code have to be certified;  Only a few tests were made on PI and DI equations;  No numbers included due to very recent modifications that I do not trust yet!!. Proton ID

  8. MI Rejection Studies - W. Carvalho Plans for the future Finish, certify and freeze this code. One possible major modification is change FPD_Particle::Propagate to automatically fill FPD_Hits variables as the particle propagates;  Start playing with different pot positions and compare with original equations; Set pots positions to their current operational values and generate new sets of equations. I’ll start by DI spectrometer, in order to be able to implement the equations into the firmware; Modify code to take plane by plane geometry/alignment into account. Proton ID

More Related