Bug #1640
EMR bar size incorrect by factor 2?
100%
Description
I ran a Monte Carlo data set using the EMR. I plotted EMRHit.GetPosition().x()
against EMRHit.GetChannelId().GetBar() % 59 + 1
and for all hits in the Monte Carlo. It looks like the position is in the range (-225, 225), which I think is wrong by a factor 2? Or maybe I am doing something stupid?
I attach my monte carlo datacards, simulation script, geometry file and a sample root output file.
Files
Updated by Rogers, Chris over 8 years ago
- Category set to EMR
- Assignee set to Drielsma, François
Inline the plot for your convenience
Updated by Rogers, Chris over 8 years ago
Just to be complete, my command line was
./simulate_emr.py --configuration_file emr_and_polarised_decay_config.py \ --output_root_file_name data/maus_mc_output_production_threshold=0.1_physics_processes=standard_cards=0.root \ --production_threshold 0.1 --physics_processes standard --default_keep_or_kill True
Updated by Drielsma, François over 8 years ago
Hello Chris,
It's a problem that I've unravelled very recently and it's probably not fixed in the trunk quite yet. The geometry of the EMR in MAUS is wrong. I don't know when it was made but the orientation of the planes is incorrect and so is the size of the bar. Everything is fixed in my branch but there is still a test failure under investigation before it can be merged to the trunk. The x position should range from more or less -500 to 500.
Updated by Rogers, Chris over 8 years ago
Okay, but myself and Sophie just wasted a month debugging your EMR code! A bug report would be nice on this sort of thing.
Updated by Drielsma, François over 8 years ago
- File bar_vs_truth.png bar_vs_truth.png added
- Due date set to 01 April 2015
- Target version set to Future MAUS release
- Workflow changed from New Issue to Closed
The problem has been solved and will be in the next MAUS release, please review at your convenience.
Updated by Dobbs, Adam over 8 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
- Workflow changed from Closed to New Issue
Fixed since 0.9.4.