Print

Print


Hello Brad,

 I was simply following the data through the simulation path. I'm not too concerned whether the

actual decay length makes physical sense or not, just that the values were being lost along the way.

Norman

 


From: Bradley T Yale <[log in to unmask]>
Sent: Wednesday, April 1, 2015 4:59 PM
To: Graf, Norman A.; Graham, Mathew Thomas
Cc: McCormick, Jeremy I.; hps-software
Subject: Re: Signal Generation Issue
 

As Sho mentioned, the decay length I applied, which did not take the boost into account, would make the actual decay length much larger than intended. It would probably be best to test the procedure with known (short) decay lengths to ensure that things actually pass through the SVT. I tried some mock data (mentioned in the track-assigning problem some time ago) and it had the same behavior, but you should also probably use your own, as opposed to tm_17mm as it currently is.


-Brad


From: Graf, Norman A. <[log in to unmask]>
Sent: Wednesday, April 1, 2015 4:26 PM
To: Graham, Mathew Thomas
Cc: McCormick, Jeremy I.; Bradley T Yale; hps-software
Subject: RE: Signal Generation Issue
 

Here’s a dump of the header and first event in the stdhep file.

The electron and positron from pdgid=622 do have a displaced vertex.

 

====== File Header ===========

    total blocks: 848

         version: 2.01

           title: tm_17mm.stdhep

         comment: No comment

            date: Sat Mar 28 13:43:27 2015

    closing date: Sat Mar 28 13:43:27 2015

expected events: 1000

          events: 4593

      firstTable: -1

        dimTable: 100

        nNTuples: 0

         nBlocks: 8

     block names:

                :  Standard HEP COMMON block, see STDHEP Product

                :  Standard HEP COMMON block with multiple interaction, see STDHEP Product

                :  Stdhep begin run record, see STDHEP Product

                :  Stdhep end run record, see STDHEP Product

                :  Standard HEP COMMON block with Les Houches, see STDHEP Product

                :  Standard HEP COMMON block with Les Houches and multiple interaction

                :  Les Houches HEPEUP common block

                :  Les Houches HEPRUP common block

=============================

event has 6 particles

    Track: 0, id: 11, vtx: (0, 0, 0, 0), mom: (0, 0, 6.6, 6.6, 0.0005111)

    Track: 0, mother1: 0, mother2: 0, daughter1: 3, daughter2: 6, status: 3

    Track: 1, id: -623, vtx: (0, 0, 0, 0), mom: (0, 0, 7.56373e-012, 171.24, 171.24)

    Track: 1, mother1: 0, mother2: 0, daughter1: 3, daughter2: 6, status: 3

    Track: 2, id: 622, vtx: (0, 0, 0, 0), mom: (0.03307, 0.0049935, 6.03357, 6.03736, 0.211)

    Track: 2, mother1: 1, mother2: 2, daughter1: 4, daughter2: 5, status: 2

    Track: 3, id: -11, vtx: (0.44637, 0.067401, 81.4396, 0), mom: (0.0372964, -0.063853, 5.30674, 5.30725, 0.0005111)

    Track: 3, mother1: 3, mother2: 3, daughter1: 0, daughter2: 0, status: 1

    Track: 4, id: 11, vtx: (0.44637, 0.067401, 81.4396, 0), mom: (-0.00422642, 0.0688465, 0.726836, 0.730102, 0.0005111)

    Track: 4, mother1: 3, mother2: 3, daughter1: 0, daughter2: 0, status: 1

    Track: 5, id: 11, vtx: (0, 0, 0, 0), mom: (-0.00857002, 0.0259785, 0.561974, 0.56264, 0.0005111)

    Track: 5, mother1: 1, mother2: 2, daughter1: 0, daughter2: 0, status: 1

 

 

Here’s the output from slic:

 

[log in to unmask]">

 

And the start positions are all (0,0,0).

I’ll continue to investigate.

Norman



Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1