Table Description:
This table is available for ADQL queries and through the TAP endpoint.
Resource Description:
For a list of all services and tables belonging to this table's resource, see Information on resource 'ARIGFH object catalog'
This table has an associated publication. If you use data from it, it may be appropriate to reference 1989AGAb....2...33W (ADS BibTeX entry for the publication) either in addition to or instead of the service reference.
To cite the table as such, we suggest the following BibTeX entry:
@MISC{vo:arigfh_nid, year=2011, title={{ARIGFH} object catalog}, author={Schwan, H. and Demleitner, M. and Wielen, R.}, url={https://dc.zah.uni-heidelberg.de/tableinfo/arigfh.nid}, howpublished={{VO} resource provided by the {GAVO} Data Center}, doi = {10.21938/7p:fef29C9YeU6XdXdwSVw} }
ARIGFH (ARI's "Geschichte des Fixsternhimmels") was a project running from at least 1990 until the early 2000s at Astronomisches Rechen-Institut Heidelberg (today a part of Zentrum für Astronomie of Heidelberg University). It strived to become the successor to Geschichte des Fixsternhimmels (see below) and succeeded in digitizing roughly 2500 and cross-matching about 1600 historical catalogs but petered out in the early 2000s for various reasons.
What is left is a large set of published positions, many matched against a master catalog, quite a few unresolved. There are also rough catalog descriptions, the raw catalogs in ASCII format, and FORTRAN subroutines (of admittedly varying quality) to parse the raw catalogs.
Some work has been done on bringing the systems of some of those catalogs to the ICRS and do further processing with the aim of producing proper motions of the objects. You are welcome to contact the operators if you are interested in taking up this work. Note that some command of German would certainly help a lot in this case.
Two main entry points might be interesting for the casual user -- for one, the cone search that gives you, for a given object or ICRS position, all observations that were matched to master objects near that position. Note that the first columns from the result tables come from the master catalog, i.e., they are all identical for the same star. The later quantities (e.g., raCat and decCat) give what is in the catalog. Of course, positions and other data are for the equinoxes and epochs specified with each row.
The second entry point for the casual user is katkat, the catalog of catalogs. Look for data for particular epochs, search by titles or authors, or just browse (links for doing that are in the katkat service info). Catalogs that have Teleki numbers have links into ARIGFH leading to the objects identified and not identfied from these tables.
Advanced users will want to directly access the tables.
The arigfh schema consists of several tables. The most important one is the arigfh.gfh table, containing almost all published data. In it, positions and proper motions are largely as they were published, i.e., in a wild mixture of equinoxes for a wild mixture of epochs. Also, not all objects have both a usable RA and Dec. Therefore, there is no spatial index on the table. We have indexed RA and Dec separately, though.
The primary way to approach the gfh table (apart from sequential scans, which due to the moderate size of the table should be no big issue) is through catid (the catalog id, formed like tNNNNpNN; see katkat for details) and catan (the ARIGFH-assigned running number within the catalog, as opposed to catcn, the published catalog number).
Within the arigfh.gfh table, there should for most objects be sufficient metadata to at least precess the objects. What ARIGFH actually did to crossmatch the objects was to precess and transform a master catalog (in the arigfh.master table) to the published epoch and equinox and use that to crossmatch the objects.
The result of this matching is in the arigfh.identified table. It connects each identified position from the gfh table via the catid/catan pair to a position in the master catalog (via the masterNo column). These relationships are flattened out in the arigfh.id table. This is the basis for the SCS and web services since it contains ICRS positions as well as the historic observations.
Analoguosly, there is the arigfh.unidenfied table, giving catid and catan for the objects from gfh that could not be matched to the master catalog. Selecting those from the gfh table yields arigfh.nid. There's a simple web frontend for that table at arigfh/q/nidweb/form. Most of what is in there these probably just represents typos, but if you look, you will certainly find all kinds of weird things. Who knows -- maybe you could even find the optical counterpart of a historic GRB...
Where available, the katkat service lets you download the FORTRAN subroutines that were used to parse the data files. To understand them, please refer to to the (German) descriptions or ask the operators for the documents to be translated; of course, all comments in the FORTRAN code are in German, too. On the other hand, those comments are not terribly useful in the first place.
The subroutines use some functions that we have not yet published, mainly because they might be embarrassing to the anonymous authors. If you actually intend to use the subroutines, let us know and we will try to cook up a source file that contains all functions used.
While working on the import of the old data, many subroutines needed to be fixed. Most changes fixed spurious line feeds, uninitialized variables, changes in the FORTRAN compiler's way to evaluate string comparisons, etc. Since the original routines are still stored, it would be possible to reconstruct the changes, but since they are unlikely to have introduced additional problems, we do not list changes here.
However, with this experience in mind, it is certain that additional problems connected to changing FORTRAN semantics lurk in the parsing subroutines and thus the data. Bug reports are welcome.
Having said all that, the only thing the subroutines should probably used for is to glean metadata from them. The student assistants who wrote the subroutines were supposed to carefully study the introductions to the catalogs in order to fill out the metadata fields (kennx4/8), and quite a number of them actually did.
ARIGFH's predecessor or inspiration, "Geschichte des Fixsternhimmels" (Paetsch et al) or GFH, "The history of the stellar sky", is a massive collection of stellar positions from almost all published catalogs for the 18th and 19th centuries.
The endeavor started in 1898 with a memorandum by Friedrich Wilhelm Ristenpart of Heidelberger Sternwarte (with input by Arthur von Auwers, who had suggested a similar project some 20 years before) to the Prussian Academy of Sciences proposing the generation of a "Thesaurus positionum stellarum affixarum". Auwers then applied for funding and got it for fiscal year 1898/99. Ristenpart was appointed director of the project.
The source material of GFH consisted of 442 catalogs with roughly 250000 objects and about a million individual positions. These had to be brought to equinox B1875.0 and crossmatched, all without the help of modern digital computers.
One first result of Ristenpart's activities was the "Fehlerverzeichnis zu den Sternkatalogen des 18. und 19. Jahrhunderts" ("Directory of Errors in the Star Catalogs of the 18th and 19th centuries"), published in 1908. When Ristenpart moved to Santiago de Chile, Hans Paetsch took over. Due to Auwer's death, World War I, and problems in the preprint phase, the first volume of GFH, covering 0h in RA on the northern sky, was only published in 1922.
In the 1920s, work was significantly delayed when temporarily Paetsch was the only person actually working on GFH. Starting 1926, personnel was re-allotted to GFH, such that by 1936 the northen part of GFH was finished.
The publication of the southern part of GFH began in 1937, after Johannes Haas had taken over from Paetsch when the latter had retired in 1929. World War II and the split of the program into a western part in Bonn and a dormant eastern part in Potsdam had brought GFH to a standstill until IAU's executive committee passed a decision noting the importance of the volumes still missing.
The last volume of the original GFH (full catalog set reduced to equinox B1875.0) was published by the East German GFH project in 1966; somewhat earlier, the Bonn group published their last volume in 1958, but they were missing some catalogs that they considered sufficiently covered by the Hamburg Index.
This section is heavily based on 1972S&W....11..224A. The bibliography there lists the following items that are not yet in ADS:
Sorted by DB column index. [Sort alphabetically]
Name | Table Head | Description | Unit | UCD |
---|---|---|---|---|
catid | Cat. | Catalog identifier as t(teleki no)p(part)(version) | N/A | meta.ref |
catan | ARI catno | Object number in source catalog, ARI assigned | N/A | meta.id |
catcn | Cat id | Object number in source catalog, as in source | N/A | meta.id |
catca | Cat id suffix | Suffix to the designation in the source catalog | N/A | meta.id |
dscode | Comp | Code for multiple star component designation [Note b] | N/A | meta.code.multip |
mag | mag | Apparent magnitude as specified by magsys | N/A | phot.mag |
magsys | Mag. Sys. | System of mag [Note m] | N/A | meta.code;phot.mag |
varflag | Var? | Code for photometric variability [Note v] | N/A | meta.code;src.var |
raCat | RA (cat) | Right ascension at catalog equinox and epoch | deg | pos.eq.ra |
eqRA | Eq. RA | Equinox of the catalog RA, Julian years | yr | time.equinox;pos.eq.ra |
epRA | Ep. RA | Epoch of the catalog RA, Julian years | yr | time.epoch;pos.eq.ra |
meanepRA | Mean Ep. RA | Mean Epoch of RA, Julian years | yr | time.epoch |
e_RA | Err. RA | Mean error in right ascension as given in catalog | deg | stat.error;pos.eq.ra;meta.main |
nobRA | #(RA) | Number of observations combined into raCat | N/A | meta.number;obs |
useRA | Use RA? | 0=RA unusable, 1=RA usable, 2=RA good, but epoch guessed | N/A | meta.code;pos.eq.ra |
raflags | RA flags | Details on observation and processing of RA (see note) [Note c] | N/A | meta.code;pos.eq.ra |
decCat | Dec (cat) | Declination at catalog equinox and epoch | deg | pos.eq.dec |
eqDec | Eq. Dec | Equinox of the catalog declination, Julian years | yr | time.equinox;pos.eq.dec |
epDec | Ep. Dec | Epoch of the catalog declination, Julian years | yr | time.epoch;pos.eq.dec |
meanepDec | Mean Ep. Dec | Mean Epoch of the declination, Julian years | yr | time.epoch |
e_Dec | Err. Dec | Mean error in declination as given in catalog | deg | stat.error;pos.eq.dec;meta.main |
nobDec | #(Dec) | Number of observations combined into decCat | N/A | meta.number;obs |
useDec | Use Dec? | 0=Dec unusable, 1=Dec usable, 2=Dec good, but epoch guessed | N/A | meta.code;pos.eq.dec |
decflags | Dec flags | Details on observation and processing of dec (see note) [Note c] | N/A | meta.code;pos.eq.dec |
pmra | PM (RA) | Cat. proper motion in RA | deg/yr | pos.pm;pos.eq.ra |
eqPmra | Eq. PM(RA) | Equinox of cat. PM in RA | yr | time.equinox;pos.pm;pos.eq.ra |
epPmra | Ep. PM(RA) | Epoch of cat. PM in RA | yr | time.epoch;pos.pm;pos.eq.ra |
e_pmra | Err. PM (RA) | Mean error in the proper motion in RA according to the catalog | deg/yr | stat.error;pos.pm;pos.eq.ra |
nobpmra | #PM (RA) | Number of observations combined into the proper motion in RA | N/A | meta.number;obs |
pmraflag | PM RA type | Type of PM RA; see note [Note p] | N/A | meta.code;pos.pm;pos.eq.ra |
pmde | PM (Dec) | Cat. proper motion in declination | deg/yr | pos.pm;pos.eq.dec |
eqPmde | Eq. PM(Dec) | Equinox of cat. PM in Dec | yr | time.equinox;pos.pm;pos.eq.dec |
epPmde | Ep. PM(Dec) | Epoch of cat. PM in declination | yr | time.epoch;pos.pm;pos.eq.dec |
e_pmde | Err. PM (Dec) | Mean error in the proper motion in Dec according to the catalog | deg/yr | stat.error;pos.pm;pos.eq.dec |
nobpmde | #PM (Dec) | Number of observations combined into the proper motion in Declination | N/A | meta.number;obs |
pmdeflag | PM Dec type | Type of PM Dec; see note [Note p] | N/A | meta.code;pos.pm;pos.eq.dec |
Columns that are parts of indices are marked like this.
The following services may use the data contained in this table:
VO nerds may sometimes need VOResource XML for this table.