Project

General

Profile

Support #642

Spurious particles/wrong PID in simulation

Added by Rogers, Chris about 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Rogers, Chris
Category:
Simulation
Target version:
Future MAUS release
Start date:
08 August 2011
Due date:
% Done:

100%

Estimated time:
Workflow:

Description

Email from Edward:

I'm seeing 3 weird things in the simulation:

1 - production of secondaries (I though this was disabled);

2 - the "input file" specifies pid = 13. When running the simulation, the first spills are -13. It's only after some spills that I see a primary pid = 13...

3 - I have muons with negative pz. They seem to be coming from the cooling channel. Other details from these guys: track id = 13, parent ID = 0, track ID = 1. The primary is inverting its direction??? I have no clue of what's going on.

Are you aware of any of these issues?

Files

simulate_mice.py (2.56 KB) simulate_mice.py Santos, Edward, 08 August 2011 09:39
read_simulation.py (314 Bytes) read_simulation.py Rogers, Chris, 08 August 2011 17:39
simulation.log (1.16 MB) simulation.log Rogers, Chris, 08 August 2011 17:39
#1

Updated by Rogers, Chris about 12 years ago

Please send me the input you use to run the simulation.

#2

Updated by Santos, Edward about 12 years ago

I attached the input... It's simply simulate_mice.py. If you add these lines in SciFiSD.cc, it might make it easier for you to find those things:

int parent = aStep->GetTrack()->GetParentID();
  int track  = aStep->GetTrack()->GetTrackID();
  double alarm = 0;
if (_hits[hit_i]["momentum"]["z"].asDouble() < 0.0 ) {
    alarm=-999;
  }
    std::ofstream out1("negative_mom.txt", std::ios::out | std::ios::app);
    out1 << aStep->GetTrack()->GetCurrentStepNumber() << " " << _hits[hit_i]["momentum"]["x"].asDouble() << " " << _hits[hit_i]["momentum"]["y"].asDouble() << " " << _hits[hit_i]["momentum"]["z"].asDouble() << " " 
         << _hits[hit_i]["hit_position"]["x"].asDouble() << " " << _hits[hit_i]["hit_position"]["y"].asDouble() << " " << _hits[hit_i]["hit_position"]["z"].asDouble()
         << " " << edep << " " << pid << " " << parent << " " << track << " " <<  alarm << "\n";
    out1.close();

Then do a CRT+F to find entries with -999 (neg momentum). You will also see the evolution of the pid and secondaries.

#3

Updated by Rogers, Chris about 12 years ago

  • Assignee changed from Santos, Edward to Rogers, Chris
#4

Updated by Rogers, Chris about 12 years ago

I tried running attached read_simulation.py against simulation.out and got attached simulation.log. Couldn't find any instances of -13 in simulation.log tracker space points.

I also changed keep_tracks to True and then looked for particle_id on the tracks - again, couldn't see any mu+

You sure?

#5

Updated by Tunnell, Christopher about 12 years ago

  • Status changed from Open to Rejected

If it persists, reopen.

#6

Updated by Tunnell, Christopher about 12 years ago

  • Status changed from Rejected to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF