Support #642
Spurious particles/wrong PID in simulation
100%
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
Updated by Rogers, Chris about 12 years ago
Please send me the input you use to run the simulation.
Updated by Santos, Edward about 12 years ago
- File simulate_mice.py simulate_mice.py added
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.
Updated by Rogers, Chris about 12 years ago
- Assignee changed from Santos, Edward to Rogers, Chris
Updated by Rogers, Chris about 12 years ago
- File read_simulation.py read_simulation.py added
- File simulation.log simulation.log added
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?
Updated by Tunnell, Christopher about 12 years ago
- Status changed from Open to Rejected
If it persists, reopen.
Updated by Tunnell, Christopher about 12 years ago
- Status changed from Rejected to Closed
- % Done changed from 0 to 100