-
Notifications
You must be signed in to change notification settings - Fork 24
Add flag to disable laser evolution #1323
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
base: development
Are you sure you want to change the base?
Conversation
Co-authored-by: Alexander Sinn <64009254+AlexanderSinn@users.noreply.github.com>
…pace- into huixingjian/desable_laser_evo
copy laser to next step
| ux = ux_next; | ||
| uy = uy_next; | ||
| uz = uz_next; | ||
| if (do_uz_push) uz = uz_next; |
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.
During the pusher subcycles, the local value of uz will still be updated and used for ux, uy and gamma. Maybe this could lead to unexpected effects. Would it also work for your case to just set Ez to zero but still update uz using the B fields? I think this would be more self-consistent.
This PR add two options
beams.do_uz_pushandlasers_solver_type = disablethat disable beam particle acceleration and laser evolution respectively. These features are regarded useful for non-linear beam matching with strong ion motion.