You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just want to highlight an important fact and a workaround I've done in case others need it.
The "histo" EnergyMode in g4sim assumes that you are passing a momentum amplitude spectrum in MeV. I was trying to use this to read in Nam's kinetic energy spectrum for protons but they obviously aren't compatible.
So I've written a script in commit 0be6cd4 that converts the histograms and saves the compatible one in the same ROOT file.
There is also a script in commit 919a313 that plots the initial kinetic energy spectrum from a MC run if you ever want to check that what you're putting in is what you're using.
The text was updated successfully, but these errors were encountered:
After working with this a bit more - I'm not sure if this is good enough. I feel the bins may be a bit wide so I changed the code (not committed) to use Nam's histogram directly. Here's the diff:
Hi Everyone.
I just want to highlight an important fact and a workaround I've done in case others need it.
The "histo" EnergyMode in g4sim assumes that you are passing a momentum amplitude spectrum in MeV. I was trying to use this to read in Nam's kinetic energy spectrum for protons but they obviously aren't compatible.
So I've written a script in commit 0be6cd4 that converts the histograms and saves the compatible one in the same ROOT file.
There is also a script in commit 919a313 that plots the initial kinetic energy spectrum from a MC run if you ever want to check that what you're putting in is what you're using.
The text was updated successfully, but these errors were encountered: