Open SchroederSa opened 8 months ago
We have the reference beta * gamma
in the reduced diagnostics, but we could add all reference particle info there and explicitly also add kinetic energy.
Commented: https://impactx.readthedocs.io/en/latest/dataanalysis/dataanalysis.html#reduced-beam-characteristics
px_mean/min/max, py_mean/min/max, pt_mean/min/max
Not explicit / clear enough.
In general, I would suggest we avoid mixing beam particle data and reference particle data in the output. The organization/philosophy of the code is such that these objects are treated separately--using independent tracking algorithms, coordinate systems, and normalization conventions--and beam particle data is always expressed relative to the reference particle. (In a similar way, the reduced diagnostics for the beam particle data and the data for the reference particle are output to separate files in IMPACT-Z.)
I very much like the approach of expressing beam data relative to the reference particle. I just think it requires a mention in the docs of the reduced diagnostics. https://impactx.readthedocs.io/en/latest/dataanalysis/dataanalysis.html
Reading the first sentence ImpactX calculates reduced beam characteristics like averaged positions, momenta, beam emittances and Courant-Snyder (Twiss) parameters during runtime.
gave me the impression I got the absolute beam information.
That sounds like a good improvement to do!
Just as a note for completion, the reference particle is also written in a text file, named diags/ref_particle.*
.
Hi, I was trying to extract the kinetic energy of the particle beam using the reduced diagnostic file output. Doing so for the apochromatic example, I get the following outputs:
In the reduced beam characteristics file, _ptmean is essentially 0. For the reference particle, however, pt is 100GeV. How can I understand mean_pt other than as longitudinal momentum?
Thanks! Sarah
p.s.: The terminology ptmean, ptmin, pt_max but sig_pt is a bit confusing.