IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Dec 24, 2006, 3:49:50 PM (20 years ago)
Author:
magnier
Message:

some API work to reduce dependencies on the recipes, support for mosaic astrometry

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/psModules/src/astrom/pmAstrometryObjects.h

    r10780 r10829  
    88*  @author EAM, IfA
    99*
    10 *  @version $Revision: 1.13 $ $Name: not supported by cvs2svn $
    11 *  @date $Date: 2006-12-17 09:45:20 $
     10*  @version $Revision: 1.14 $ $Name: not supported by cvs2svn $
     11*  @date $Date: 2006-12-25 01:49:49 $
    1212*
    1313*  Copyright 2004-2005 Maui High Performance Computing Center, University of Hawaii
     
    7979pmAstromStats;
    8080
    81 /*
    82  *
    83  * If the two sets of coordinates are expected to agree very well (ie, the
    84  * current best-guess astrometric solution is quite close to the radius. The
    85  * following function accepts two sets of pmAstromObj sources and determines the
    86  * matched objects between the two lists. The input sources must have been
    87  * projected to the Focal Plane coordinates (pmAstromObj.FP), and the supplied
    88  * options entry must contain the desired match radius (keyword:
    89  * ASTROM.MATCH.RADIUS). The output consists an array of pmAstromMatch values,
    90  * defined below.
     81typedef struct
     82{
     83    psStats *xStats;
     84    psStats *yStats;
     85    int     nMatch;                     ///<
     86    double  nSigma;                     ///<
     87}
     88pmAstromFitResults;
     89
     90/*
     91 *
     92 * If the two sets of coordinates are expected to agree very well (ie, the current best-guess
     93 * astrometric solution is quite close to reality), perform a match based on a simple radius
     94 * test. The following functions accept two sets of pmAstromObj sources and determines the
     95 * matched objects between the two lists using coordinates of the desired depth (depending on
     96 * the function). The input and reference sources must have been projected to the desired depth
     97 * (eg, for Focal Plane coordinates, to pmAstromObj.FP).  The specified radius must be in the
     98 * units for the matching depth (chip: pixels, focal plane: microns, tangent plane:
     99 * degrees. The output consists an array of pmAstromMatch values, defined above.
    91100 *
    92101 */
     
    94103    const psArray *st1,
    95104    const psArray *st2,
    96     const psMetadata *config
     105    double RADIUS
     106);
     107psArray *pmAstromRadiusMatchFP(
     108    const psArray *st1,
     109    const psArray *st2,
     110    double RADIUS
    97111);
    98112psArray *pmAstromRadiusMatchTP(
    99113    const psArray *st1,
    100114    const psArray *st2,
    101     const psMetadata *config
     115    double RADIUS
    102116);
    103117psArray *pmAstromRadiusMatchChip(
    104118    const psArray *st1,
    105119    const psArray *st2,
    106     const psMetadata *config
     120    double RADIUS
    107121);
    108122
     
    270284 */
    271285
     286pmAstromFitResults *pmAstromFitResultsAlloc(void);
    272287
    273288/*
     
    312327 *
    313328 */
    314 bool pmAstromMatchFit(
     329pmAstromFitResults *pmAstromMatchFit(
    315330    psPlaneTransform *map,
    316     psArray *st1,
    317     psArray *st2,
     331    psArray *raw,
     332    psArray *ref,
    318333    psArray *match,
    319     psMetadata *config,
    320     psMetadata *updates
     334    psStats *stats
    321335);
    322336
Note: See TracChangeset for help on using the changeset viewer.