Skip to content

Option for aligning the beam axis of generated beam to its propgation direction at Source #165

Merged
ben-c-2013 merged 14 commits into
mainfrom
add_beam_pointing_angle_at_Source
Jan 21, 2026
Merged

Option for aligning the beam axis of generated beam to its propgation direction at Source #165
ben-c-2013 merged 14 commits into
mainfrom
add_beam_pointing_angle_at_Source

Conversation

@ben-c-2013

@ben-c-2013 ben-c-2013 commented Nov 18, 2025

Copy link
Copy Markdown
Collaborator

Modified Source.track() in order to align the beam axis of the generated beam to its propagation direction, as several of the stage subclasses do not allow tilted drive beams with a propagation direction not aligned to the beam axis ("crab beams").

Also needed to modify several other files in order to make everything consistent.

@ben-c-2013 ben-c-2013 requested a review from kyrsjo November 18, 2025 16:52
@ben-c-2013 ben-c-2013 added the enhancement New feature or request label Nov 18, 2025
@kyrsjo

kyrsjo commented Dec 19, 2025

Copy link
Copy Markdown
Collaborator

PR looks fine, but I'm worried about if particle time of arrival to point in s, and the s position of a particle at a given time, has been mixed.

The normal convention in tracking codes is that the particles are pushed between s positions. Not sure what HiPace does. But there might be that the "de-crabbing" is actually adding a crab... Let's discuss next year.

@kyrsjo

kyrsjo commented Dec 19, 2025

Copy link
Copy Markdown
Collaborator

Reccomend to add issue to discuss the convention and its application, but merge this.

@ben-c-2013 ben-c-2013 merged commit e55cbdb into main Jan 21, 2026
1 check passed
@ben-c-2013 ben-c-2013 deleted the add_beam_pointing_angle_at_Source branch January 21, 2026 07:12
@ben-c-2013 ben-c-2013 restored the add_beam_pointing_angle_at_Source branch January 21, 2026 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants