Transients Pipeline
The Transients Pipeline (or "TraP") is a system for detecting transient and variable sources in a stream or batch of astronomical images. It primarily targets LOFAR data, but is also applicable to a range of other instruments.
Documentation: https://transients-pipeline.readthedocs.io/en/latest/
This is a rework of the original package hosted here: https://github.com/transientskp/tkp An overview of the package and it's initial design can be found in the original TraP paper. If you make use of TraP in work leading to a publication, we ask that you cite this reference.
The rework is focussed on performance, ease of deployment and ease of use and code maintainability. The approach of associating sources between images is still based on the paper linked above, as this approach has shown itself to be suitable to finding a variety of transient and variable sources.
How TraP operates (high level overview)
The way the package is meant to operate is that it will run on astronomical images (.FITS recommended) and will use a source finder (PySE) to find all the sources in a given image. This is done for all images individually. The source finder returns information on each source extracted from the image, such as it's position, the intensity (flux) and their related errors. In order to construct light curves/time series of each source, the sources extracted from the first image are matched to (associated with) the sources extracted from the second image. This creates a table of known source locations. We track the locations of each of these as we go, but we export the information of every source extracted from every image in the export database. For more information on the export database structure, see the Database Reference For every source we export to the database, we also save the index of the source it was associated with in the previous image. This creates a daisy-chain of ids we can use to reconstruct a lightcurve.
Interpreting the results
We want to support a broad range of transients and variability science. During the processing therefore, we make few assumptions about what makes a good source. Any kind of filtering on the data can be done afterwards. The database can be queried to select the sources in a given position or with a certain intensity, error margin, etc.. The user can then decide what qualities make for an interesting source. The most common way to interact with the data is to use a Jupyter Notebook, read some results from the database and plot the results. Some basic examples can be found in the Example Gallery
Metadata
Release files for trap 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| trap-1.4.0.tar.gz | 87.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trap-1.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 145.3 kB
Release files / trap-1.4.0.tar.gz
| Download URL | trap-1.4.0.tar.gz |
|---|---|
| Size | 87.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63764c65bb19618743e33ca6fbda3c47e2f1883839d0a80119b3bb78c46cc28c
|
|
BLAKE2b-256 checksum How to use checksums |
2ac74c638fe65e96c2ce6a61b99062c406fc219a6eef3871ec6cacba1d28b786
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / trap-1.4.0-py3-none-any.whl
| Download URL | trap-1.4.0-py3-none-any.whl |
|---|---|
| Size | 57.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d85ebed56acfe512f543a33ec18d6273f21cc6656290ae4d0c6ece85ef974059
|
|
BLAKE2b-256 checksum How to use checksums |
4e86b0286b0ca58e4830d02f8f37e4b320a8b6a2b3426bbb3b24054e27c3d776
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|