J. Kube1,
-
B. T. Gänsicke1,2 -
F. Euchner1 -
B. Hoffmann1
1 - Universitäts-Sternwarte Göttingen, Geismar Landstraße 11, 37083
Göttingen, Germany
2 -
Department of Physics and Astronomy, University of Southampton,
Hampshire, Southampton SO17 1BJ, UK
Received 29 November 2002 / Accepted 12 March 2003
Abstract
CVcat is a database that contains published data on
cataclysmic variables and related objects. Unlike in the
existing online sources, the users are allowed to add data to the
catalogue. The concept of an "open catalogue'' approach is reviewed
together with the experience from one year of public usage of
CVcat. New concepts to be included in the upcoming AstroCat framework
and the next CVcat implementation are presented. CVcat can be found at
http://www.cvcat.org.
Key words: astronomical data bases: miscellaneous - catalogues - stars: novae, cataclysmic variables
CVcat has been developed in order to overcome major conceptual shortcomings of
existing CV catalogues: Ritter & Kolb (1998) include only systems with known
orbital period, which limits their catalogue to 1/3 of all CVs and
related objects. Downes et al. (1997) do list all known CVs, but their catalogue
provides only very limited information on each individual system, i.e., the
only binary parameter included is the orbital period. Our aim was to develop
an online data base that combines the information of the existing catalogues
and allows the users to actively contribute to the content of the data
base, implementing a first version of an "open catalogue''.
CVcat differs from other CV catalogues and other astronomical databases in the concept of the data input. So far, the majority of astronomical catalogues have been compiled by relatively small editorial teams consisting of scientists knowledgeable in the fields covered by the catalogues (e.g. McCook & Sion 1999; Downes et al. 1997; Liu et al. 2001; Ritter & Kolb 1998). These catalogues typically contain more or less detailed information on a specific class of astronomical objects. Updates are published, if at all, only on a very irregular basis. The catalogues contain just one value for each listed property (e.g. distance, orbital period) of a given object. Whilethis is helpful for non-specialist users to obtain a quick overview ofthe properties of an individual object, or of the statisticalproperties of a given group of objects, the more expert user willcertainly benefit if different and possibly competing values for agiven parameter are referenced in such catalogues. This is particularly useful if the information has been obtained by different methods.
Some of the aforementioned catalogues moved from "classical'' printed publication to online web-based publication, which allows shorter update cycles (e.g. the "living edition'' of the Downes et al. 1997 CV catalogue, Downes et al. 2001), however, the overall concepts remained unchanged. In addition to these specialized catalogues for a specific object class there exists huge data bases like SIMBAD (Wenger et al. 2000), which provide very basic properties for an enormously large number of objects. However, due to the very global coverage of astronomical objects, data contained in SIMBAD are prone to be incomplete and/or inaccurate.
The concept of an "open catalogue'' implemented in CVcat permits every
registered user to add data to the catalogue, which is instantly
visible to all other users. The quality control is performed by an editorial
team (Sect. 2.1), which may alter or remove erroneous data. For every
property of an object, an arbitrary number of values can be stored
(e.g. several published values for the distance). CVcat returns one of these values as the "bestavailable'' value, selected as such by the editors. However, as sucha selection process often involves some subtle subjective view of theeditor, the more expert user may decide to inspect the original sources forthe competing values, and, thereafter, decide based on his/herexperience which value is best suited for a given purpose.
![]() |
Figure 1: Classical, current, and future concepts for adding and editing catalogue data in comparison. |
Open with DEXTER |
A sketch of the different concepts of data input and validation is given in Fig. 1 (a) for classical catalogues and (b) for the CVcat concept. (c) introduces the concept that will be implemented in the next release of CVcat, which is adressed in Sect. 4. In the future version, newly-added data will be instantly visible as it is now (Fig. 1, (b)), but will be tagged as "unapproved'' until an editor cross-checks the data. In the current implementation (b), the user cannot see if a database entry has been approved by an editor.
![]() |
Figure 2: Search form in CVcat: A large fraction of the search form focuses on the detailed selection of the object class. |
Open with DEXTER |
High state magnitude (922), low state magnitude (794), optical spectrum exists (665), orbital period (509), distance (221), general magnitude (209), primary mass (156), inclination (153), secondary mass (142), superhump period (128), secondary spectral type (121), mass ratio (93), Doppler tomogram exists (80), primary temperature (76), optical light curve exists (61), hydrogen column density (58), orbital ephemeris (55), eclipsing (48), spin period (36), primary radius (33), secondary radius (29), uv data exists (22), general magnetic field strength of primary star (18), field strength of primary magnetic pole (17), X-ray data exists (14), eclipse map exists (11), secondary temperature (8), colatitude of primary magnetic pole (5), field strength of secondary magnetic pole (3), spin ephemeris (3), azimuth of primary magnetic pole (2), magnitude in eclipse (2), azimuth of secondary magnetic pole (1).
Every value stored in CVcat is linked to its original publication, either in the NASA ADS using the ADS bibcode of the paper (Kurtz et al. 2000), to the astro-ph/arXiv e-print archive, or to the VSNET messages (Nogami et al. 1997). Besides references to the publications from which the data entries contained in CVcat are taken, a list of articles with general information on a given object can be stored in CVcat.
We allow inclusion of data from astro-ph, which is not necessarily identical to the datapublished in the final refereed version (or which may in some casesnever make it through the refereeing stage). Most of the astro-ph data, however, is promoted to refereed information at some point. It is a typical task of the editors to track such updates and to conduct the appropriate changes to the database, i.e. changing the source from an astro-ph to an ADS bibcode.
Data retrieval from CVcat works in two ways: (i) the user obtains all
available data for a specific object, which can be found using its object
type, its coordinates, or one of its names, (ii) the user creates a table
containing selected properties for a list of objects. The latter method allows the user
to create data tables suitable for easy graphics generation as well as
ready-to-publish LATEX-tables.
![]() |
Figure 3: Search result in CVcat: Some of the data stored for SS Cygni. |
Open with DEXTER |
Searching in CVcat is organized as a two-step process. In the first step, the user can enter the search pattern, which can be the name or a substring of the name, a set of object classes, and the coordinate range of the object (Fig. 2). The object class is selected using a grid of logical operators ("and'', "or'', and "not''). It is possible, e.g., to look for dwarf novae, which have also been observed as novae: choose "and DN'' and "and Nova''. Another example is to look for nova-likes which do not show the SW Sex phenomenon: the corresponding selection would be "or NL'' and "not SW''.
After submitting this search request a list with all objects matching the search criteria is returned (not shown). In this list, all object names are hyperlinks to the page showing all results for the specific object (Fig. 3). Alternatively, a set of objects can be chosen from this list to generate a user-configurable list with certain properties of the objects. This list may be adjusted in a way that objects without a published value for a certain property are not included. By iterative calls of the list generator it is possible to distill a table containing e.g. all objects with known masses and periods.
An example of the results of such a list creation process is given in the following section.
![]() |
Figure 4:
Secondary mass plotted
against orbital period (points) and period histogram (gray bars) for all CVs with
known orbital period and secondary mass. The full line shows the relation from
Eq. (1), the short dashed line from
Eq. (3), the long dashed line from
Eq. (4). Full boxes and error bars are used for
systems with estimated errors in M2, open boxes for secondary star masses
with an unknown error range. The given (M2,P) data pairs represent
![]() ![]() ![]() |
Open with DEXTER |
The log file analysis of CVcat usage over a one year period shows that CVcat has a stable user community which is still slowly increasing. The typical usage of CVcat is to request all available data on a specific object, which is normally queried by its name. List generation of objects selected by their class ranks second in the usage of the database. The current growth rate of the catalogue is around 50 entries per month, mostly from the CVcat editors.
The data flow into CVcat originating from outside the CVcat core team is not yet satisfying. It is unclear why most users refrain from adding data from their own publications. Users should bear in mind that the probability of having their papers cited increases if the information from their publications can be found in the database.
The concept of CVcat has demonstrated the benefits of a public scientific catalogue with a globally-shared expertise of its users and editors. The general structure of CVcat is also applicable to other fields of astronomy. Hence, a more general software based on the experiences with CVcat which will allow the implemenation of catalogues for arbitrary object classes, called "AstroCat'', is currently being developed. This software will also include additional features to improve the knowledge management of astronomical results and data:
The data is stored in a MySQL data base to which the Perl script communicates using the standard Perl DBI/DBD interface.
For the implementation of AstroCat, an XML layer will be included between the data base and the HTML layer. This XML layer can be used to automatically include larger data sets into the database. Another possible application will be to use the AstroCat framework as an archive for reduced data from robotic telescopes that use RTML (Hessman 2001) for their observation requests, accomplished observations, and some of the metadata. A technical advantage of the usage of XML is the easy availability of many very good tools specialized in the processing of XML data and the transformation of XML documents into HTML pages. This will improve the quality and the speed of the implementation. PHP might be used in addition to Perl as the scripting language for the AstroCat programs.
With CVcat we have implemented an online catalogue for cataclysmic variable stars, which - for the first time - allows its users to add data instantly visible to all other users. The quality control is realized by a team of experts who share the responsibility for the different object classes. From the experiences of one year of public usage of the catalogue we have compiled a number of new concepts which will be implemented in the next generation of CVcat in the context of a more general framework for astronomical databases, AstroCat.
Acknowledgements
We would like to thank all the colleagues who volunteered to take the responsibility for one of the object classes included in CVcat: Domitilla de Martino, Don Hoard, Steve Howell, Tom Marsh, Klaus Reinsch, Matthias Schreiber, and John Thorstensen. The AstroCat/CVcat project is funded by the Deutsche Forschungsgemeinschaft (DFG) project number LIS 4 - 554 95 (1) Göttingen. The development of the feasibility study has partially been supported by the DLR under grant 50 OR99 03 6. BTG also acknowledges support from a PPARC Advanced Fellowship.We appreciate the helpful comments from the referee, Dr. Ochsenbein, to both this paper and the CVcat database itself.