2021-12-03T09:33:44Z 100 Note that LIFE's target database is living data. The content – and to some extent even structure – of these tables may change at any time without prior warning. The LIFE Target Star Database LIFETD 1.3 The LIFE Target Star Database contains information useful for the planned `LIFE mission`_ (mid-ir, nulling interferometer in space). It characterizes possible target systems including information about stellar, planetary and disk properties. The data itself is mainly a collection from different other catalogs. \betawarning .. _LIFE mission: https://life-space-mission.com/ stars exoplanets circumstellar-disks astrometry 10.21938/ke_e6lzO_jjX_vzvVIcwZA Menti F.; Quanz S.; Alei E.; Caballero J. A.; Demleitner M.; Garcia Munoz A.; Kennedy G.; Schmitt U.; Stassun K.; Wyatt M.; Gaehler M.; LIFE Collaboration LIFE Research Archive Adding mes_h_link table containing all links between pair of objects Updated to contain Exo-Mercat 2.0 data instead of earlier version. Changed planetary parameters from prototype demonstration version into parameters that match data from provider better. Concretely removed mass_pl_rel parameter and replaced mass_pl_err with mass_pl_err_max and mass_pl_err_min. Source Table A list of all the sources for the parameters in the other tables. \betawarningsource_id data/sources.xml Object table A list of the astrophysical objects. \betawarningobject_id data/objects.xml Provider Table A list of all the providers for the parameters in the other tables. \betawarningprovider_name data/provider.xml Basic stellar parameters A list of all basic stellar parameters. \betawarningobject_idref data/star_basic.xml Basic planetary parameters A list of all basic planetary parameters. \betawarning object_idref data/planet_basic.xml Basic disk parameters A list of all basic disk parameters. \betawarning object_idref data/disk_basic.xml Object relation table This table links subordinate objects (e.g. a planets of a star, or a star in a multiple star system) to their parent objects. Contains only best link for each pair of objects. \betawarning parent_object_idref,child_object_idref, h_link_source_idref data/best_h_link.xml Object identifiers table A list of the object identifiers. \betawarning object_idref,id,id_source_idref data/ident.xml Mass measurement table A list of the planetary mass measurements. \betawarning data/mes_mass_pl.xml Effective temperature measurement table A list of the stellar effective temperature measurements. \betawarning object_idref,teff_st_source_idref data/mes_teff_st.xml Radius measurement table A list of the stellar radius measurements. \betawarning object_idref,radius_st_source_idref data/mes_radius_st.xml Mass measurement table A list of the stellar mass measurements. \betawarning object_idref,mass_st_source_idref data/mes_mass_st.xml Multiplicitz measurement table A list of the stellar multiplicitz measurements. \betawarning object_idref,binary_flag,binary_source_idref data/mes_binary.xml Phys. separation measurement table A list of the stellar phys. separation measurements. \betawarning data/mes_sep_ang.xml Object relation table This table links subordinate objects (e.g. a planets of a star, or a star in a multiple star system) to their parent objects. \betawarning data/h_link.xml A view containing the most basic data for simple consumption by the cone search service. src, name object.main_id, star_name object.main_id, planet_name star_basic.coo_ra, ra star_basic.coo_dec, dec star_basic.dist_st_value, dist planet_basic.mass_pl_value, planet_mass planet_basic.mass_pl_err_max, planet_mass_error_max planet_basic.mass_pl_err_min, planet_mass_error_min CREATE VIEW \qName AS (SELECT \colNames FROM ( select distinct star_ob.main_id as star_name, planet_ob.main_id as planet_name, coo_ra as ra, coo_dec as dec, dist_st_value as dist, mass_pl_value as planet_mass, mass_pl_err_max as planet_mass_error_max, mass_pl_err_min as planet_mass_error_min from life_td.star_basic as s join life_td.h_link as slink on (parent_object_idref=s.object_idref) join life_td.object as star_ob on (s.object_idref=star_ob.object_id) join life_td.object as planet_ob on (child_object_idref=planet_ob.object_id) left outer join life_td.planet_basic as p on (child_object_idref=p.object_idref) WHERE star_ob.type = 'st' AND planet_ob.type = 'pl' )q) life_td cone LIFE Target Database Cone Search testQuery.ra: 312.27 testQuery.dec: 37.47 testQuery.sr: 0.01 Please note that the Simple Cone Search service is intended for very casual use only. The primary interface to the LIFE target database is `through TAP`_; see also the `query examples`_ for LIFE-TD. .. _through TAP: /tableinfo/life.object?tapinfo=true .. _query examples: /life/q/ex/examples LIFE TAP examples In LIFE, we have a single table for all kinds of objects (planets, stars, disks, multi-star systems). They are kept in :taptable:`life_td.object`: .. tapquery:: SELECT TOP 10 object_id, main_id FROM life_td.object WHERE type='st' Objects in LIFE are in a hierarchy (e.g., a planet belongs to a star). The parent/child relationships are given in the :taptable:`life_td.h_link` table which you can join to all other tables that have an object_idref column. For instance, to find (direct) children of a star, you would run: .. tapquery:: SELECT DISTINCT main_id as Child_main_id, object_id as child_object_id FROM life_td.h_link JOIN life_td.ident as p on p.object_idref=parent_object_idref JOIN life_td.object on object_id=child_object_idref WHERE p.id = '* alf Cen' Objects in LIFE are in a hierarchy (e.g., a planet belongs to a star). The parent/child relationships are given in the :taptable:`life_td.h_link` table which you can join to all other tables that have an object_idref column. For instance, to find (direct) parents of a star, you would run: .. tapquery:: SELECT DISTINCT main_id as parent_main_id, object_id as parent_object_id FROM life_td.h_link JOIN life_td.ident as c on c.object_idref=child_object_idref JOIN life_td.object on object_id=parent_object_idref WHERE c.id = '* alf Cen A' In LIFE, we have individual tables for all kinds of parameters where multiple measurements for the same object are available. They are kept in the tables starting with ``mes_`` e.g. :taptable:`life_td.mes_teff_st`: .. tapquery:: SELECT * FROM life_td.mes_teff_st JOIN life_td.ident USING(object_idref) WHERE id = '* alf Cen A' In LIFE we keep for each object the best measurements of its kind in the basic data table corresponding to the object type. For instance, to find the best measurements for the star '* alf Cen' you would run: .. tapquery:: SELECT * FROM life_td.star_basic JOIN life_td.ident USING(object_idref) WHERE id = '* alf Cen' In LIFE we keep for each object the best measurements of its kind in the basic data table corresponding to the object type. For instance, to find the best measurements for the disk around the star '* bet Cas' you would run: .. tapquery:: SELECT DISTINCT main_id disk_main_id, object_id as disk_object_id, db.* FROM life_td.h_link JOIN life_td.disk_basic as db ON db.object_idref=child_object_idref JOIN life_td.ident as p on p.object_idref=parent_object_idref JOIN life_td.object on object_id=child_object_idref WHERE p.id = '* bet Pic' and type='di' In LIFE we keep information about the quality of a measurement. This can serve as motivation for future observations to fill in knowledge gaps. For instance, to find where reliable measurements for the parallax are missing you would run: .. tapquery:: SELECT star_ob.main_id as star_name, plx_value, plx_err, plx_qual, plx_source_idref FROM life_td.star_basic as s JOIN life_td.object as star_ob on (s.object_idref=star_ob.object_id) WHERE plx_value is Null or plx_qual in ('D','E') or plx_qual is Null The input catalog for the LIFE yield estimations (LIFE-StarCat) is created using the following query in addition to some postprocessing in regards of multiplicity afterwards. If you want to access the latest version of the catalog go to `LIFE-StarCat`_ .. _LIFE-StarCat: https://drive.google.com/file/d/12F7N0w3kGHJw3FBbf_P6xF9Pers38wbu/view?usp=sharing .. tapquery:: SELECT o.main_id, sb.coo_ra, sb.coo_dec, sb.plx_value, sb.dist_st_value, sb.sptype_string, sb.coo_gal_l, sb.coo_gal_b, sb.teff_st_value, sb.mass_st_value, sb.radius_st_value, sb.binary_flag, sb.mag_i_value, sb.mag_j_value, sb.class_lum, sb.class_temp, o_parent.main_id AS parent_main_id, sb_parent.sep_ang_value FROM life_td.star_basic AS sb JOIN life_td.object AS o ON sb.object_idref=o.object_id LEFT JOIN life_td.h_link AS h ON o.object_id=h.child_object_idref LEFT JOIN life_td.object AS o_parent ON h.parent_object_idref=o_parent.object_id LEFT JOIN life_td.star_basic AS sb_parent ON o_parent.object_id=sb_parent.object_idref WHERE o.type = 'st' AND sb.dist_st_value < 30. cone/form self.assertHasStrings( "Matched: 3", "* 14 Her c", # planet id (main ids can change over time) "17.90", # Distance "7.1") # planet mass of planet c (can change over time) /tap/sync rows = self.getVOTableRows() self.assertEqual(len(rows), 1) self.assertAlmostEqual(rows[0]["mass_pl_value"], 8.5) self.assertAlmostEqual(rows[0]["coo_ra"], 242.60131531625294) self.assertEqual(rows[0]["type"], 'pl') self.assertEqual(rows[0]["host_name"], '* 14 Her')