Project

General

Profile

Feature #694

Tracker Variables Status

Added by Santos, Edward about 10 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Simulation
Target version:
Start date:
04 September 2011
Due date:
% Done:

0%

Estimated time:
Workflow:

Description

Please have a look at the file attached. It summarises a number of issues we are finding.


Files

tracker_param.pdf (9.59 MB) tracker_param.pdf Santos, Edward, 04 September 2011 10:20
#1

Updated by Rogers, Chris about 10 years ago

  • Is bottom right MC truth in tracker 1?
  • How did you extract the data. Should attach the script used to generate data and extract it - I need to be able to reproduce the bug if you want me to look at it.
  • Are you saying there is an issue with the track reconstruction or the MC?
#2

Updated by Santos, Edward about 10 years ago

It's an issue with the MC. It becomes an issue with the reconstruction when we miss the position calculation by large values (more than a couple of mm), but happens < 1% of the time.

I'm extracting values by writing them to a txt file during run-time.

ES

#3

Updated by Rogers, Chris about 10 years ago

What geometry? What input beam? I need to be able to reproduce the bug if you want me to look at it.

#4

Updated by Santos, Edward about 10 years ago

Default geometry and input beam - I mean the ones set in the trunk. I know the geometry is Stage6 but i never looked at the beam definitions...

#5

Updated by Santos, Edward about 10 years ago

In order to reproduce those results you can just pick the trunk version and spit out MC values of position and momentum from SciFiSD.

#6

Updated by Rogers, Chris about 10 years ago

  • Category changed from Tracker to Simulation
  • Assignee changed from Long, Kenneth to Rogers, Chris
  • Target version set to Future MAUS release

Great - thanks for help. I'll have a look...

#7

Updated by Rogers, Chris about 10 years ago

Are these electrons or muons? For example, decay electrons are allowed to travel backwards with high pz...

#8

Updated by Santos, Edward about 10 years ago

I forgot to output the particle ID... scrolling through the json output, I found pid 22 and 2112 (although these don't seem to be interacting with the tracker) and 11 (these definitely create space points with weird pz).

#9

Updated by Rogers, Chris about 10 years ago

FYI, PID lookup table (from xboa.Common):

pdg_pid_to_name  = {0:'none', 11:'e-', 12:'electron neutrino', 13:'mu-', 14:'muon neutrino', 
22:'photon', 111:'pi0', 211:'pi+', 321:'K+', 2112:'neutron', 2212:'proton', 1000010020:'deuterium', 
1000010030:'tritium', 1000020030:'3He', 1000020040:'4He', 130:'K0L', 310:'K0S', 311:'K0', 3122:'lambda', 
-11:'e+', -12:'electron antineutrino', -13:'mu+', -14:'muon antineutrino', -211:'pi-', -321:'K-', 
-2112:'antineutron', -2212:'antiproton', -3122:'antilambda'}

22 is photon, 2112 is neutron. Neutrals don't tend to deposit energy like charged particles, they just make background noise (so important to simulate, but just a pain that mucks up reconstruction).

Can you remake the plots one for each PID? Especially muons and electrons are interesting.

#10

Updated by Santos, Edward about 10 years ago

Thanks for that table. The particle decoding makes sense, remembering the energy deposits and momentum I saw for pid's 11, 22 and 2112. That's both exciting and a relief. :) Will do the plots you asked, just need a little time.

#11

Updated by Rogers, Chris almost 10 years ago

  • Status changed from Open to Rejected

Please re-open if there is still a problem...

Also available in: Atom PDF