Click here for BHTOM2 API documentation.
Note: the documentation is still in preparation.
In the meantime, you can listen to a recording on the BHTOM2 presentation by Lukasz Wyrzykowski from Malta 2023 workshop
Please contact us if you plan to use the data in a publication. By downloading the data from BHTOM you agree to follow our data policy and to use this acknowledgment:
The data was obtained via [BHTOM](https://bhtom.space), which has received funding from the European Union's Horizon 2020 research and innovation program under grant agreement No. 101004719 (OPTICON-RadioNet Pilot).
For more information about acknowledgement and data policy contact us and visit https://about.bhtom.space
Brokers in BHTOM search for time-series archival data in photometric (and soon also radio and spectra) archives providing publicly available data. We access the data either via API's provided by each service, or we access copies of archives stored in the Whole Sky Data Base (WSDB), maintained at the Institute of Cambridge, UK, by Sergey Koposov.
Webpage: https://gsaweb.ast.cam.ac.uk/alerts
Oficial Gaia DR3 data release. Limited to selected sources only.
ALLWISE is an archival MID-IR WISE data, while NEOWISE is a new on-going scanning mission, providing data every 6 months for targets from all-over the sky
Read directly from Caltech archive, contain neary 10-year long time-series for most of the sky (North and South) except the Galactic Plane. Observations were taken in a broad-band clear filter we call CRTS (CL)
From WSDB.
Problem: only mean epoch JD is stored in that table. Returns flux in miliJanskys (ReducedDatumUnit.MILLIJANSKY). Filter name: FIRST(Flux 1.4GHz)
ZTF data is read from most recent Data Release and ANTARES broker (newest data).
Reads WSDB archive, DR14 is read, typically 1 observation per filter per epoch, but for targets from e.g. Stripe82 there are way more epochs.
WSDB is read for typically single epochs in multiple bands.
Uses WSDB. About 10 years-long timeseries in a clear filter we call LINEAR(CL).
Old service, Cambridge Photometric Calibration Server, now used only as a repository of old observations prior to BHTOM2.
As of 2023, there are three sources of ASASSN photometry: variable star catalogue, pre-computed photometry and photometry on request (most fresh data). Because of that, the ASASSN URL for a Target has to be the full path to the URL with the object. First, the user has to manually identify the object in ASASSN SkyPatrol db by entering coordinates (https://asas-sn.osu.edu/), then select one of the three paths there, one the webpage with the object and copy its URL as the ASASSN url, for example, https://asas-sn.osu.edu/photometry/31a0bd00-3b2c-541b-9bb6-1a3bf050da34. The only exception is for variable, where for the name the user has to copy the link to the CSV file, e.g. for variable star https://asas-sn.osu.edu/variables/448970 it is going to be https://asas-sn.osu.edu/photometry/31a0bd00-3b2c-541b-9bb6-1a3bf050da34.csv. For the ASASSN name one can use either the name found in ASASSN archive, or a generic ASASSN+Ra+Dec name.
The data from this Survey orignate from ATLAS Webpage: https://fallingstar-data.com/forcedphot/. For a new target created, the request is sent to this service. It typically takes up to 15 minutes for the request on the entire ATLAS time-span to be generated. The data are then automatically loaded to the target. Then, an automated process is taking care to keep ATLAS light curve up-to-date, with refresh time of 12h. Note, we download magnitudes which include reference flux (if available).
ATLAS data is automatically cleaned from extreme outliers (scipy.stats.z_score>10) as well as limited to 5>mag>22, including negative magnitudes (limits), which are not currently stored nor showed.
Cite: Tonry et al. (2018), Smith et al. (2020), Heinze et al. (2018), Shingles et al. (2021).