IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changeset 31022


Ignore:
Timestamp:
Mar 23, 2011, 10:08:25 AM (15 years ago)
Author:
eugene
Message:

add PSASTRO.GRID.NREF.MAX and PSASTRO.GRID.NRAW.MAX values; add an STS-specific recipe block

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/eam_branches/ipp-20110213/ippconfig/gpc1/psastro.config

    r30982 r31022  
    1515PSASTRO.GRID.OFFSET    F32    1000.
    1616PSASTRO.GRID.SCALE     F32      50
    17 PSASTRO.GRID.NSTAR.MAX S32     800 # max stars accepted for fitting
     17PSASTRO.GRID.NSTAR.MAX S32     800 # deprecated
     18PSASTRO.GRID.NREF.MAX  S32     800 # max stars accepted for fitting from ref catalog
     19PSASTRO.GRID.NRAW.MAX  S32    1200 # max stars accepted for fitting from raw image
    1820
    1921PSASTRO.MAX.NRAW      S32      1000   # max stars accepted for fitting (0 for all)
     
    4446PSASTRO.MATCH.RADIUS.N5 F32    10
    4547PSASTRO.MATCH.RADIUS.N6 F32    10
    46 PSASTRO.MATCH.RADIUS.N7 F32     5
    47 PSASTRO.MATCH.FIT.NITER S32     8
     48PSASTRO.MATCH.RADIUS.N7 F32    5
     49PSASTRO.MATCH.FIT.NITER S32    8
    4850
    4951# for iterations >= N, require a single match per reference
     
    295297    PSASTRO.CATDIR              STR      SAS.REF.V1
    296298END
     299
     300# these values worked to get solutions for the STS observations from 2009 & 2010
     301# these field has damage from excessive persistence and the impact of burntool
     302STS_DATASET  METADATA
     303
     304  # need to boost the total number of stars available for the fit:
     305  # allow more stars per chip and boost the density to which we query
     306  # from the reference database.
     307  PSASTRO.MAX.NRAW      S32      2000   #
     308  PSASTRO.MAX.NREF      S32      8000   # max stars accepted for fitting (0 for all)
     309  DVO.GETSTAR.MAX.RHO   F32      60000.0
     310 
     311  # the crowding is high, so unless we restrict somewhat tightly early
     312  # on, we get very noisy (and wrong) fits.  These values are probably
     313  # too restrictive for the general observation: we would risk missing
     314  # matches.
     315
     316  # single-chip radius match in pixels
     317  PSASTRO.MATCH.RADIUS.N0 F32    10
     318  PSASTRO.MATCH.RADIUS.N1 F32    5
     319  PSASTRO.MATCH.RADIUS.N2 F32    5
     320  PSASTRO.MATCH.RADIUS.N3 F32    5
     321  PSASTRO.MATCH.RADIUS.N4 F32    3
     322  PSASTRO.MATCH.RADIUS.N5 F32    3
     323  PSASTRO.MATCH.RADIUS.N6 F32    5
     324  PSASTRO.MATCH.RADIUS.N7 F32    5
     325  PSASTRO.MATCH.FIT.NITER S32    5
     326END
Note: See TracChangeset for help on using the changeset viewer.