Changeset 6683 for trunk/Ohana/src/addstar/include/addstar.h

Timestamp:

Mar 26, 2006, 10:46:32 AM (20 years ago)

Author:

eugene

Message:

adding proper motion and parallax to addstar, dropping _PS from RA and DEC in average

File:

• trunk/Ohana/src/addstar/include/addstar.h (modified) (3 diffs)

trunk/Ohana/src/addstar/include/addstar.h

@@ -69 +69 @@
 double  SNLIMIT;
 int     ACCEPT_ASTROM;  // accept even bad astrometry solutions (NASTRO == 0)
+int     ACCEPT_MOTION;  // accept reference proper motion measurements
 int     TEXTMODE;       // force input file to be loaded as RAW
 int     SUBPIX;         // apply a subpix correction
@@ -125 +126 @@
 double     get_subpix             PROTO((double x, double y));
 Stars     *getgsc                 PROTO((SkyRegion *patch, int *NSTARS));
-Stars     *gettycho               PROTO((SkyRegion *catstats, int photcode, double epoch, int *Nstars));
+Stars     *gettycho               PROTO((SkyRegion *catstats, int photcode, int *Nstars));
 Stars     *getusno                PROTO((SkyRegion *catstats, int photcode, int *Nstars));
-Stars     *getusnob               PROTO((SkyRegion *catstats, int photcode, double epoch, int *Nstars));
+Stars     *getusnob               PROTO((SkyRegion *catstats, int photcode, int *Nstars));
 Image     *gimages                PROTO((FITS_DB *db, Image *image, Coords *mosaic, int *Npimage));
 Stars     *grefcat                PROTO((char *Refcat, SkyRegion *catstats, int photcode, int *nstars));
@@ -188 +189 @@
 
 /** 
-  there is an inconsistency to be resolved: fixed structures (like Image)
-  need a fixed bit-length time (e_time), but these functions all use the
-  UNIX time_t types, which may be 32 or 64 bits, depending on the machine.
-  This can be resolved by using time_t with these functions, but casting 
-  between e_time and time_t when necessary (ie, cannot return data to an
-  e_time pointer from one of these functions)
+    there is an inconsistency to be resolved: fixed structures (like Image)
+    need a fixed bit-length time (e_time), but these functions all use the
+    UNIX time_t types, which may be 32 or 64 bits, depending on the machine.
+    This can be resolved by using time_t with these functions, but casting 
+    between e_time and time_t when necessary (ie, cannot return data to an
+    e_time pointer from one of these functions)
 **/