-
Notifications
You must be signed in to change notification settings - Fork 17
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
Fix the batch execution for elements with tilts or misalignments #157
Fix the batch execution for elements with tilts or misalignments #157
Conversation
tests/test_tilted_elements.py
Outdated
@@ -0,0 +1,51 @@ | |||
import torch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cr-xu Is there a reason you didn't just put these into test_quadrupole.py
? That seems more logical to me.
CHANGELOG.md
Outdated
@@ -15,6 +15,7 @@ | |||
|
|||
- Now all `Element` have a default length of `torch.zeros((1))`, fixing occasional issues with using elements without length, such as `Marker`, `BPM`, `Screen`, and `Aperture`. (see #143) (@cr-xu) | |||
- Fix bug in `Cavity` `_track_beam` (see [#150](https://github.com/desy-ml/cheetah/issues/150)) (@jp-ga) | |||
- Fix bugs when tracking elements with `tilt` or `misalignment`. (see #157) (@cr-xu) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cr-xu Did you fix anything other than the vectorisation? I guess because the changelog is with respect to the previous release (and not master), rather than adding a bug fix, we should add the issue and your name to the breaking vectorisation change entry. Does that make sense?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, that's only with the vectorisation. Yes it makes sense to move it in the vectorisation entry.
Description
Motivation and Context
Closes #154.
Types of changes
Checklist
flake8
(required).pytest
tests pass (required).pytest
on a machine with a CUDA GPU and made sure all tests pass (required).Note: We are using a maximum length of 88 characters per line