Table information for 'blaauw.raw'

General

This table is available for ADQL queries and through the TAP endpoint.

Resource Description: This database contains the header information of the raw observations made in the Blaauw Observatory. It is currently in heavy development!

For a list of all services and tables belonging to this table's resource, see Information on resource 'Raw Observation Data'

Citing this table

To cite the table as such, we suggest the following BibTeX entry:

@MISC{vo:blaauw_raw,
  year=2023,
  title={Raw Observation Data},
  author={Sten Sipma},
  url={http://vo.astro.rug.nl/tableinfo/blaauw.raw},
  howpublished={{VO} resource provided by the Blaauw Archive}
}

Resource Documentation

It is recommended to query the archive using another program via TAP, like TOPCAT or Python. Some examples on how to work with the database from Python is given in the example TAP Queries Notebook .

For some comprehensive guides on how to use ADQL look at the ADQL tutorial .

Some example queries (with what they mean)

Select all observations which have been made in 2020.
SELECT *
FROM blaauw.raw
WHERE date_obs_mjd between 58849 and 59215

The best way to compare dates is to use the date_obs_mjd (date of the observation in Modified Julian days). A convenient calculator is: https://mjdconverter.com/. Here 2020 (first of January 00h) refers to 58849, 2021 to 59215. Some common values are:

Useful MJD Values
2018 2019 2020 2021 2022 2023 2024 2025
58119 58484 58849 59215 59580 59945 60310 60676

A more specific variant: all observations which have been made on a specific day (this case 18th April 2020). Using the calculator we find that the MJD is 58957, which will be 18th of April at 00:00, so it refers to the night 17-18 in April. We therefore need to add half a day (18th at noon) for the lower limit, and add 1.5 days for the upper limit (19th at noon).:

SELECT *
FROM blaauw.raw
WHERE date_obs_mjd between (58957 + 0.5) and (58957 + 1.5)

Note that this can be tricky as 'date_obs_mjd' is the exact moment of the observation, take this into account!

Flat Fields in R of GBT
SELECT *
FROM blaauw.raw
WHERE filter = 'R' AND image_type = 'FLAT' AND telescope = 'GBT'
ORDER BY date_obs

Note the use of AND to combine multiple conditions into one expression. The OR operator is also available.

Select all files with obs_date closest to a given date

Given some date (in MJD format) [ref_date], query the files which have been taken most recent (past or future) w.r.t. it.

SELECT filename, date_obs_mjd, ABS(date_obs_mjd - [ref_date]) AS difference
FROM blaauw.raw
ORDER BY difference

Key feature here is that you can compute your own column (based on simple mathematical expressions) and give them a name using the 'AS' keyword.

A more specific example: Retrieve the nearest 3x3 binned flat field images to the night of 17th of april 2020 (2020-04-18 00:00:00, MJD: 58957).

SELECT TOP 10 filename, date_obs_mjd, ABS(date_obs_mjd - 58957) AS difference
FROM blaauw.raw
WHERE image_type = 'FLAT' AND binning = 3
ORDER BY difference

Note that there are some issues, as it does not take into account the filter in which the flat field was taken. Ideally you would want to execute this query for each desired filter (e.g. add: WHERE ... AND filter = 'R'). In addition, if there are viable flats in the day before and after, the result can be mixed (as the difference is taken absolute). A possible solution is to compute the same column but without taking the absolute and use that column in some other program.

SELECT TOP 10 filename, date_obs, ABS(date_obs_mjd - 58957) AS abs_difference, date_obs_mjd - 58957 AS difference
FROM blaauw.raw
WHERE image_type = 'FLAT' AND binning = 3
ORDER BY abs_difference

How to use this query in another program (Python) is one of the examples in the TAP Queries Notebook .

Columns

Sorted by DB column index. [Sort alphabetically]

NameTable Head DescriptionUnitUCD
file_id File_id Combination of the folder date and file name to compare raw and processed files. N/A meta.id;meta.file;meta.main
ra Ra Right Ascention coordinate of where the telescope is pointed. deg pos.eq.ra;meta.main
dec Dec Declination coordinate of where the telescope is pointed. deg pos.eq.dec;meta.main
alt Alt Alt-azimutal altitude deg pos.eq.alt
az Az Alt-azimutal azimut deg pos.az.azi
date_obs_mjd Date_obs_mjd Observation date and time as Modified Julian Date (MJD). Derived from the 'DATE_OBS' keyword. d time.epoch;obs
date_obs Date_obs Observation date and time in UTC. N/A time.epoch;obs
filename Filename Absolute path to the corresponding FITS file. Will point to the most detailed version of the file (i.e. to the WCS version if it is available, raw version otherwise) N/A meta.id;meta.file
raw_filename Raw_filename Absolute path to the corresponding FITS file on the Vega data server. N/A meta.id;meta.file
wcs_filename Wcs_filename Absolute path to the corresponding FITS file with WCS information. N/A meta.id;meta.file
telescope Telescope The telescope which produced the observation, either: GBT (Gratema Bernoulli Telescope) or LDST (Lauwersmeer Dark Sky Telescope). N/A instr.tel
instrument Instrument Instrument / Detection which produced the observation. N/A instr.instr
image_type Image_type The type of image, e.g. 'LIGHT', 'DARK', 'BIAS' or 'FLAT'. N/A meta.code;obs
filter Filter The name of the filter used in the Observation. N/A meta.code;instr.filter
target_object Target_object Name of the (intended) object being observed. N/A N/A
exposure_time Exposure_time Exposure time of the observation (in seconds). s time.duration;obs.exposure
binning Binning The binning of the CCD (typically 1). N/A N/A
airmass Airmass Airmass of the observation N/A obs.airmass
has_wcs Has_wcs Boolean which indicates if the file has a valid WCS. N/A N/A
created_at Created_at Datetime on which the entry was first inserted into the database. N/A time.creation
updated_at Updated_at Datetime on which the entry last updated. N/A time.creation
id Id Database identifier of the file. N/A meta.id;meta.main

Columns that are parts of indices are marked like this.

Other

The following services may use the data contained in this table:

VOResource

VO nerds may sometimes need VOResource XML for this table.