Wake-T: A fast tracking code for plasma accelerators
Overview
Wake-T (Wakefield particle Tracker) is a tracking code for laser- and beam-driven plasma wakefield accelerators which aims at providing a fast alternative to Particle-in-Cell (PIC) simulations. Instead of relying on the computationally-expensive PIC algorithm for simulating the plasma wakefields and the beam evolution, Wake-T uses a Runge-Kutta solver to track the evolution of the beam electrons in the wakefields, which, at the same time, are computed from reduced models. This allows for a significant speed-up of the simulations, which can be performed in a matter of seconds instead or hours/days. An overview of this strategy can be seen in the following figure:
In addition to plasma-acceleration stages, Wake-T can also simulate active plasma lenses, drifts, dipoles, quadrupoles and sextupoles, allowing for the simulation of complex beamlines. The tracking along the drifts and magnets is performed using second-order transfer matrices, and CSR effects can be included by using a 1D model. This matrix approach and the CSR model are based on a streamlined version of the Ocelot implementation.
Installation
If you don't have Python 3 already installed, download the latest version, for example, from here. It is recommended to create a virtual environment for Wake-T (you can see how here, for example). Remember to activate the new environment before proceeding with the installation.
Installing from PyPI
Simply type
pip install Wake-T
in your terminal.
Manual installation from GitHub
- Clone this repository to a directory in your computer using
git
git clone https://github.com/AngelFP/Wake-T.git
or simply download the code from here and unzip it.
- If you haven't already, open a terminal in the newly created folder and perform the installation with
pip install .
References
[1] - P. Baxevanis and G. Stupakov, Novel fast simulation technique for axisymmetric plasma wakefield acceleration configurations in the blowout regime, Phys. Rev. Accel. Beams 21, 071301 (2018).
[2] - A. Ferran Pousa et al., Wake-T: a fast particle tracking code for plasma-based accelerators, J. Phys.: Conf. Ser. 1350 012056 (2019).
Release files for Wake-T 0.9.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| wake_t-0.9.1.tar.gz | 141.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wake_t-0.9.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 301.0 kB
Release files / wake_t-0.9.1.tar.gz
| Download URL | wake_t-0.9.1.tar.gz |
|---|---|
| Size | 141.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08a6ba20fe79fbe66430ff7a41fb02c702276aeabdce6f94fac7fcfaa3389069
|
|
BLAKE2b-256 checksum How to use checksums |
fa69766dfae85152ecce44ab5c35958bfb66abddcc10417595f47f0874e7ed0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 25, 2025.
Transparency logRelease files / wake_t-0.9.1-py3-none-any.whl
| Download URL | wake_t-0.9.1-py3-none-any.whl |
|---|---|
| Size | 159.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
973f4e2495c1b8de9ac6b4ca150cc0f97702d311cc212bdcf64d20e145dc3579
|
|
BLAKE2b-256 checksum How to use checksums |
0cc8bfbac28e0c7ab0b07eb17e5d0da432255a676c2f0616110c0a98c3caec42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 25, 2025.
Transparency log