Repository of code and data supporting the newly discovered active long-period radio transient
- RA: 18:39:02.0 (18.6505 hrs, 279.7583 deg)
- Dec: -10:31:49.5 (-10.5304 deg)
- Uncertainty: 0.15"
The analysis code below is self-contained except for a planetary ephemeris file that is needed to do the barycentring.
The ephemeris assumed by this code can be downloaded from http://naif.jpl.nasa.gov/pub/naif/generic_kernels/spk/planets/de430.bsp and should be placed in the dynspec folder.
One way to do download this file on the command line is
cd dynspec
wget -O de430.bsp http://naif.jpl.nasa.gov/pub/naif/generic_kernels/spk/planets/de430.bsp
There is also a rule in the Makefile in the dynspec directory, so one can also run
cd dynspec
make de430.bsp
Each recipe below corresponds to a different folder within this one.
In some cases, the subfolder has its own README.md with more in-depth instructions.
Some subfolders are prerequisites for others, according to the following diagram:
To re-make the flowchart:
dot -Tpng flowchart.dot > flowchart.png
The listed command(s) are inteded to be run in the corresponding subfolder.
In all of the below, if there are make commands, you can use the -j command to parallelise execution.
lightcurves_nobary: Prepare lightcurves without barycentring
make lightcurves
Expected output: *_lightcurve.txt files
lag_analysis: Combining same-pulse lightcurves and lag analysis
python lag_analysis.py
Expected output: *_lightcurve_mod.txt files
toas_nobary: Get the non-barycentred TOAs
make all_toas_mod.tim
Expected output: all_toas_mod.tim
toas_bary: Get the barycentred TOAs
make all_toas.tim
Expected output: all_toas_mod.tim
P_Pdot_diagram: Grid search in F0 and F1
To generate chi2_grid.csv:
python grid_search_f_fdot.py dofit.par ../toas_nobary/all_toas_mod.tim
To generate Ppdot_search.pdf:
python plot_P_Pdot_search.py
make_table: Generate `.tex` and `.csv` tables of individual pulse information
python make_table.py
Some (not necessarily all) of the final figures and tables that result from the above analyses are also git-tracked.
Such files are kept in the upload_materials folder so that they do not clash with the files generated by the analysis scripts.
If the analysis scripts are changed in any way that affects the results, the way to affirm the new results is to copy the relevant file(s) into the upload_materials folder and overwrite the previous version.
