In addition to images, GCX handles lists of astronomical objects generally referred to as stars. There are several types of stars, and the various types have different kinds of information attached. They can be grouped in two classes:
A relatively straight-forward star detection algorithm is implemented in GCX. It will search for local intensity peaks that satisfy the following conditions:
The star detection routine is called by selecting Stars/Detect Sources, or automatically by other operations (WCS fitting and frame alignment). The detection routine will produce detected stars, except when called on an alignment reference frame, in which case it will produce alignment stars.
Another way of creating frame stars is to control-click on or near an otherwise unmarked star image. This will initiate a spiral star search in a region around the the cursor, with the SNR parameter set to a low value (3.0). In this way, even very faint stars that are located near the cursor can be marked. This procedure creates user stars.
As their name implies, catalog stars are generally loaded from catalog files. GCX supports three kinds of catalogs: object catalogs, from which the stars are loaded by name (like GCVS, NGC, Messier, IC); field star catalogs, from which the stars are loaded by region of interest; and star files (including recipe files), which are loaded in their entirety, as they presumably contain stars in a region of interest.
As catalog stars are located by world coordinates, the program cannot display any of them if it doesn't have at least an approximate idea of what the image's coordinates are in the real world. The frame must have at least an initial WCS.4.1
If the frame WCS is unset, the program will refuse to load field stars; it will set the initial WCS so that the loaded object is at the center of the frame if a single object is loaded from an object catalog; and it will refuse to load a star file, unless the star file is a recipe that contains target coordinates, in which case the initial WCS will be set from those coordinates.
There are two ways of loading stars from object catalogs: Selecting Stars/Add From Catalog will prompt for an object name and load it. If the frame has the OBJECT FITS field set, selecting Stars/Show Target will try to load the object specified in that field. Stars loaded from object catalogs are of the catalog object type.
Currently, the program supports two field star catalogs directly: GSC (and GSC-ACT) and TYCHO2. It can also load GSC2 objects in the form of star files (see below).
To load stars from GSC or Tycho, the frame has to have at least an initial WCS; then select File/Load Field Stars/From GSC Catalog or File/Load Field Stars/From Tycho2 Catalog.
Options under Star Detection and Search Options control the maximum number of stars loaded and the limiting magnitude. When more stars than the specified limit are found in the catalog, only the brightest ones are loaded. The region searched is slightly larger than the frame's size in world coordinates.
http://www-gsss.stsci.edu/support/data_access.htmlIt can be loaded into GCX by selecting File/Load Field Stars/From GSC-2 file. Stars loaded this way are marked as field stars.
The program expects the various catalogs to be set up in a certain way. Here are the requirements for the various catalogs.
The program reads the GSC or GSC-ACT4.3 catalogs in the compact (binary) form. It can be downloaded in this format from:
ftp://cdsarc.u-strasbg.fr/pub/cats/I/255/GSC_ACT/Place the downloaded files in a directory (for instance /usr/share/gcx/gsc-act) and set File and Device Options/GSC Location to point to that directory. Make sure all the directory and file names under the gsc dir use all lower case letters.
The Tycho2 catalog can be downloaded from
ftp://cdsarc.u-strasbg.fr/pub/cats/I/259/We need to download all the tyc2.dat.nn.gz files, unzip them and concatenate together to create one (big) tycho2.dat file, perhaps like this:
zcat tyc2.dat.??.gz >tycho2.datAfter that, set File and Device Options/Tycho2 location to the full path of the file, like for instance:
/usr/share/gcx/tycho2/tycho2.datGCX must have write permissions to the directory where the tycho2.dat file is located, as it needs to create some indexes when the catalog is first accessed.
To tell the program what native format catalog files to load, set the File and Device Options/Catalog files option to a comma-delimited list of files. The list can contain wildcards and is tilde-expanded. An example entry would be:
All .edb files that are searched must be located in the same directory, specified in File and Device Options/EDB files. Depending on the searched object's name, GCX will look in a specific file:4.4
|Objects with names starting in ``M''&Messier.edb|
|Objects with names starting in ``NGC''&NGC.edb|
|Objects with names starting in ``UGC'' or ``UGCA''&UGC.edb|
|Objects with names starting in ``IC''&IC.edb|
|Objects with names starting in ``SAO''&sao.edb|
|Objects with ending in a constellation name||gcvs.edb|