-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Beam read_from_file also reads spin #1172
base: development
Are you sure you want to change the base?
Conversation
Co-authored-by: Alexander Sinn <64009254+AlexanderSinn@users.noreply.github.com>
Thanks for the review, some tests are on the way, I'll merge once we have confirmation that it works as expected. |
Co-authored-by: Alexander Sinn <64009254+AlexanderSinn@users.noreply.github.com>
Looks great! was this on GPU? If not, do you know why there is a tiny difference, don't we expect them to be equal to machine precision? |
Unfortunately, there are tiny differences even on CPU. I added some oscillations in x to the witness so the spin has a signal. Without that, the spin is very constant, and both cases are within 1e-6, but with the autoscale plot the restart looks different. One possible reason for this could be that the momentum is multiplied with the speed of light and its inverse. |
As reported by @pots007, when reading a beam from file the spin data is currently ignored. This PR proposes to fix this. The behavior is determined by the user: if
do_spin_tracking
is specified, the corresponding runtime components are allocated and read from file. Otherwise, they are neither allocated nor read.