IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Sep 11, 2016, 2:33:18 PM (10 years ago)
Author:
eugene
Message:

add skips for chips without a valid solution (do not just crash); add recipe value for PSASTRO.MODEL.REF.CHIP.ANGLE, the position angle expected for the reference chip for an exposure with PA = 0.0; posAngle needs to be adjusted to match reference chip target value; if the projection is not TAN or DIS when attempting bilevel mosaic fitting, re-fit the projection + distortion to be TAN + distortion

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/czw_branch/20160809/psastro/src/psastroAstromGuess.c

    r31333 r39686  
    7575    pmFPA *fpa = input->fpa;
    7676
    77     if (DEBUG) psastroDumpCorners ("corners.up.guess1.dat", "corners.dn.guess1.dat", fpa);
     77    // this call only works if we have loaded a model : seg fault if not
     78    if (DEBUG && useModel) psastroDumpCorners ("corners.up.guess1.dat", "corners.dn.guess1.dat", fpa);
    7879
    7980    // load mosaic-level astrometry?
     
    9192            if (!psastroAstromGuessSetChip (fpa, chip, view, pixelScale, bilevelAstrometry)) continue;
    9293        }
     94
     95        if (!chip->toFPA || !chip->fromFPA) {
     96          char *name = psMetadataLookupStr (NULL, chip->concepts, "CHIP.NAME");
     97          fprintf (stderr, "no astrom model for %s, skipping\n", name);
     98          continue;
     99        }
    93100
    94101        if (newFPA) {
     
    312319    while ((chip = pmFPAviewNextChip (view, fpa, 1)) != NULL) {
    313320        if (!chip->process || !chip->file_exists || !chip->data_exists) { continue; }
     321
     322        if (!chip->toFPA || !chip->fromFPA) {
     323          char *name = psMetadataLookupStr (NULL, chip->concepts, "CHIP.NAME");
     324          fprintf (stderr, "no astrom model for %s, skipping\n", name);
     325          continue;
     326        }
    314327
    315328        // XXX we are currently inconsistent with marking the good vs the bad data
Note: See TracChangeset for help on using the changeset viewer.