-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add space-charge effects in Cheetah #137
Comments
Small comment: I'll take a look at #142 🚀. Just for the above, technically, the space-charge kick is modeled like a thin element (always |
Yes, we are aware that the space charge kick does not add length to the element (see for instance this comment). In As suggested by @jank324, the above |
Yes. One aspect I forgot to mention and related to your link, it's not fully equivalent to our ds in ImpactX because we do not model space charge kicks conceptionally as elements. I stead, we slice elements (slice_ds=ds/N) and add collective effects between slices. For that reason, our space charge kick is not even a subclass of our thin elements (where we define ds=0), because it is not an element (in our concept). As I said, just a comment. There are many ways to express this. Maybe we could make collective effects thin elements as well in ImpactX :) |
It would be valuable to add space-charge effects in Cheetah.
This could be done by adding space-charge to existing elements by using the standard technique of sub-stepping through an element (used in other accelerator codes). For instance, a drift without space-charge
would be replaced (here with 3 substeps) by
One could use the integrated Green function method for
SpaceChargeKick
, described here:https://journals.aps.org/prab/abstract/10.1103/PhysRevSTAB.9.044204
This could then be benchmarked with examples from https://inspirehep.net/literature/1690374, as well as the example from the section "Free Expansion of a Cold Uniform Bunch" in https://inspirehep.net/files/178e98af93e0aaf3838a175835781aa0
The text was updated successfully, but these errors were encountered: