The new version of Binary stars database (BDB)

1. The new version of Binary stars database (BDB) P. Kaygorodov1, B. Debray2, N. Kolesnikov3, D. Kovaleva1, O. Malkov1 1 INASAN, 2 Observatoire de Besançon, 3 SAI MSU The new version of BDB database that combines data from a variety of catalogues of binary stars is presented. The main goal of BDB is to allow user to interrogate of data for all categories of binary stars. The technologies, which the current version of BDB was built on, don't allow effectively integrate it into a modern infrastructure. So, in 2010 it was decided to create a new version using the recent tools. The new version is written in Python and based on Nagare framework, which allows to create web applications with natively integrated Web 2.0 features. The PostgreSQL database is used for data storage. To date, the backend parts of the new version is almost done, including the tools for importing catalogues from VizieR. At present, efforts are focused on frontend modules, including searching, real-time communications with other databases and cross-identification tools. Introduction Binary stars are very common, and binaries provide accurate data that are very difficult to determine for single stars, such as masses and radii. The binary star data are those of single stars extended to system characteristics. Usually data on different classes of binaries are presented in particular databases, e.g., WDS, CHARA, SB9, etc. There is no database synthesizing the various categories, and Binary star Data Base, BDB2 aims to fill this gap. The main goal of BDB is to allow user to interrogate of data for all categories of binary stars. To achieve this goal we should integrate and provide an access to data from large catalogues of binaries [CCDM, WDS, …]; to establish links with databases of binary stars: [SB9, Sidonie, …] and general databases [SIMBAD, IBVS, ...], and to integrate data from catalogues of astrophysical parameters (masses, radii, etc.) of binary components. Besides numerical data, BDB should also contain images. The following two main problems should be solved. First, right data should be linked with right components. It includes a development of a unique and consistent system for component designations (A, Ab, B, AB, C, ...) and a solution of problem of component identifications in different catalogues (cross-identification problem). The other problem is compilation of a list of data sources (catalogues, databases) for binaries of different types to be included in or linked with BDB. Query result Fundamental data for CCDM 04078+6220 (user can check one or more catalogues to retrieve data): CCDM • ICRS: 04 07 51.3945 +62 19 48.367, pm = 0.13 –2.25, par = 0.48; 22 components • A: ADS 2984 A, IDS 03590+6204 A, HD 25638, GCVS NSV 1458 V=6.99, B0III • B: ADS 2984 B, IDS 03590+6204 B, GCVS SZ Cam, HIP 19270 V=7.26, O9.5V+B0, P=2.7 • Bab: ,=(300,0.071) • Bb: P=2.8 • AB: BD +61 676 V=7.0+7.1, B0, ,=(304,17.9) • AC: HIP 19272 V=7.0+12.9, B0, ,=(257,6.0) • …. • AQ: V=6.91+13.2, ,=(325,45.2) CCDM CCDM CCDM GCVS CCDM Queries to BDB GCVS SB9 ecl_HIP Organization of BDB database: INT4 • Query by binary type (e.g., visual binary, spectroscopic binary) • Query by catalogue (e.g., WDS, Hipparcos) • Query by identifier of binaries (e.g., ADS, CCDM) • Query by coordinates • Query by parameters of binaries (e.g., angular separation, magnitude difference, component mass) From the set of catalogues (most of them was downloaded from VizieR) we extract data on various types of binaries. Our database contains two types of records: systems and pairs. The records has the following fields, which can be used for querying: CCDM SB9 WDS CCDM Retrieved data Data extracted from selected catalogues shown as a set of tables. Descriptions of the tables can be revealed via [show] links WDS WDS INT4 Output of query result (for one object or for a list of objects): HTML, ASCII, XML (VOTable) New fields can be added in future to extend query types. All records hold ID’s from original catalogues. Each record can include several ID’s. For example, CCDM catalogue has its own ID, but also includes HD, DM, ADS/BDS and some others. BDB has cross-identification table, so, querying by, for example, HD identifier can return results from catalogues that do not use HD identifiers, but contain the requested object. Query result returns information from all catalogues, containing requested object, but final output can be filtered by user to include only selected data.