Backend database code and data for OTTER
confidence
keywordThese confidence scores are our rough confidence values in the classification of this object. They were determined using the following, somewhat arbitrary, system:
Confidence | Reason |
---|---|
0.1 | Classifications with these values are from the Open TDE Catalog and either did not have a classification reference or were not strictly classified as a TDE in that catalog |
0.5 | These classifications are from TNS. We give classifications from TNS a confidence of 0.5 because there are a select few that are wrong on TNS (e.g. 2017bcc) |
1 | We trust the reference for this classification |
Warning: This confidence score system is still under development and may have bugs or mistakes, please trust at your own risk!
We expect the data to come as a zip file that contains a single meta.csv
file, a separate csv photometry file for each transient (but not necessarily
required for each transient), and an individual FITS file for every spectra.
More details about each file are below.
meta.csv
This file contains metadata for the transient event you are providing. A list of possible column names are below.
Required Columns:
name
: The name (internal or IAU) of the transientra
: The right ascencsion of the transientdec
: The declination of the transientra_units
: The units of the provided RAdec_units
: The units of the provided declinationreference
: The ads bibcode associated with this dataOptional Columns:
phot_path
: The path of the photometry file, relative to the directory that
the meta.csv
file is in.spec_path
: The path of the spectrum file, relative to the directory that the meta.csv
file is in.redshift
: The measured redshift (only provide if YOU measured it)luminosity_distance
:dispersion_measure
:date_discovery
: Discovery date of the transient if you discovered itdate_discovery_format
: Format of the discovery dateclass
: The classification of the transient (e.g. SN, TDE, FRB, etc.)There should be one file per event in the meta file. These photometry csv files have the following columns.
Required Columns:
date
: The date the photometric observation was madedate_format
: The format of the date givenraw
: The raw photometry. This can be a flux, flux density, magnitude,
energy, or count.raw_units
: The units (or system in the case of a magnitude) of raw
filter
: The name of the telescope filterRequired/Optional Columns (Only required in some cases):
telescope_area
: Collecting area of the telescope. Required if the
photometry is given in counts!val_k
: The k-correction value applied. Only required if a k-correction
was applied.val_s
: The s-correction value applied. Required if an s-correction was
applied.val_av
: The value of the applied Milky Way Extinction. Required if the
photometry was corrected for Milky Way Extinction.val_host
: The value of the applied host correction. Required only if the
photometry is host subtracted.val_hostav
: The value of the host extinction. Required if the photometry
was corrected for host extinction.Optional Columns:
raw_err
: The error on the raw photometry value given.date_err
: The error on the date given.upperlimit
: Boolean. True if this is an upperlimit.sigma
: Significance of the upperlimit.instrument
: The instrument used to collect this data.phot_type
: is the photometry PSF, Aperature, or synthetic.exptime
: The exposure timeaperature
: The aperature diameter in arcseconds, if aperature photometry.observer
: Name of the observer for this point.reducer
: Name of the person who reduced this data point.pipeline
: Name and version of the pipeline used to reduce this data.filter_eff
: The effective wavelength or frequency of the filter. We will
use the filter_eff_units
key to determine this.filter_eff_units
: The units of filter_eff
.telescope
: The name of the telescope or observatory.Spectra are not supported at this time.