Axel Huebl

You can add something similar to: ```cmake # copy MAD-X lattice file file(COPY ${ImpactX_SOURCE_DIR}/examples/fodo/fodo.madx DESTINATION ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/FODO.MADX.py) ``` in `examples/CMakeLists.txt` for the SXF file to be available during `ctest` runs.

Clang on Windows seems happy but MSVC is not yet: ``` 4>C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(248,5): error MSB8066: Custom build for 'D:\a\impactx\impactx\build\CMakeFiles\c134c98d71a9573b76308dc0d94c59ed\copy-compile-commands.rule;D:\a\impactx\impactx\CMakeLists.txt' exited with code 1. [D:\a\impactx\impactx\build\copy-compile-commands.vcxproj] ``` Actually, how does...

> > Is placing this in the source directory best practice? > > Per the [docs](https://clangd.llvm.org/design/compile-commands#where-do-compile-commands-come-from): > > We first check for a compilation database in the directory containing the...

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` - Average / minimum / maximum beam momenta normalized by reference particle momentum (unit: dimensionless, radians for transverse momenta) Not explicit / clear enough.

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.*`.

Chapter 5: http://madx.web.cern.ch/madx/webguide/manual.html > 5.2 CALL > > CALL, FILE="filename"; > > where filename is the name of an input file. The named file is then read until a RETURN...

Discussed with @WeiqunZhang today: - `queryAdd("amrex.throw_exception", 1)`: in `src/initialization/InitParser.cpp` - will make `amrex::Abort()`s throw an exception instead of exit - careful: then generally no backtraces? - add backtrace logic in...

Implemented in #223 Follow-ups: - [x] implement helper function that simplifies ImpactX property getters to a one-liner - and throws from ImpactX (not accross dynamic libs via `amrex::Abort`) #265 -...

Thanks for looking into this! It's the example we have checked in for CI: examples/input_fodo.in That one should have 1 particle: we hard-code init of one particle atm.