Bug #853: SpecialVirtual hit and TOF hit have different particle id field - MAUS - MICEmine

Bug #853

SpecialVirtual hit and TOF hit have different particle id field

Added by Rogers, Chris almost 12 years ago. Updated over 11 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Rogers, Chris

Category:

Detector Integration

Target version:

MAUS-v0.2.3

Start date:

06 January 2012

Due date:

% Done:

100%

Estimated time:

Workflow:

New Issue

Description

In TOF MC hits, it's called "particle_id", i.e.

        {
          "energy_deposited": 0.0, 
          "path_length": 0.0, 
          "energy": 156.8029666692641, 
          "particle_id": -13, 
          "track_id": 1, 
          "channel_id": {
            "type": "TOF", 
            "station_number": 2, 
            "plane": 0, 
            "slab": 6
          }, 
          "charge": 1.0, 
          "mass": 105.6584, 
          "time": 201805.6223029375, 
          "position": {
            "y": 109.861496589517, 
            "x": 97.60824925893533, 
            "z": 6524.5
          }, 
          "momentum": {
            "y": 24.69225780507105, 
            "x": 22.519160655669, 
            "z": 110.9353535784441
          }
        },

In SpecialVirtual MC hits its called "pid", i.e.

        {
          "energy_deposited": 3.600154406356154e-05, 
          "energy": 166.6567578132797, 
          "pid": -13, 
          "track_id": 1, 
          "channel_id": {
            "station_number": 9002, 
            "type": "SpecialVirtual" 
          }, 
          "charge": 1.0, 
          "mass": 105.6584, 
          "time": 201797.0959873077
        },

Should be the same in both (and need to check also other detectors. Long term fix would be to use proper data structure and MCHit type.