| 26 | | * |
| | 26 | * The flags that have to be used to tell that a detection has problems are: for flags: DEFECT, SATURATED, MOMENTS_FAILURE, BIG_RADIUS, AP_MAGS, SIZE_SKIPPED, ON_SPIKE, ON_GHOST, OFF_CHIP; for flags2: ON_SPIKE, ON_BURNTOOL |
| | 27 | * Some flags are correlated or have fixed values: FITFAIL is set only if FITTED is set; EXTERNALPOS, CR_LIMIT, SKY_FAILURE, SKYVAR_FAILURE, MOMENTS_SN should always be 0; |
| | 28 | |
| | 29 | ''Actions'' |
| | 30 | * A-009 (See details): Answer Gene's questions: |
| | 31 | * 1) (Serge/Heather for plots) What fraction of the detections have flux / flux_sig < 5 (the nominal cutoff) or < 3 (a possible agressive cutoff)?; |
| | 32 | * 2) (Serge/Roy/Heather) What is the spatial distribution of these detections? |
| | 33 | * 3) (Who?) What does the histogram of pixel value / sqrt(pixel variance) look like in areas / cells with large numbers of these detections? Should be a Gaussian with a width of 1, but if there is excess noise from the camera in some areas, the width will be > 1 (we underestimate the variance). |
| | 34 | * A-010 (Roy): Is the false detections filter dependent? |
| | 35 | * A-011 (Roy/Heather for plots): Classify "matched": statistics similar to the unmatched (flags, flags2, flux_sig/flux ratio histogram, anything else) |
| | 36 | * A-012 (Roy): Build DS9 region files for "matched" detections with bad flags (see Heather for details, will help answering Gene's questions) |
| | 37 | * A-013 (?): Comments/Open Questions |
| | 38 | * 1) How were the "unmatched" detections defined? |
| | 39 | * 2) What has been missed from the Sloan detections? |
| | 40 | * 3) Using the flags we cut about 2/3 of the good detections |
| | 41 | * A-014 (Serge) (1) Check if FITFAIL flag is set only if FITTED flag is set; (2) EXTERNALPOS, CR_LIMIT, SKY_FAILURE, SKYVAR_FAILURE, MOMENTS_SN should always be 0; |
| | 42 | |
| | 43 | |
| | 44 | ''Pending Actions'' |
| | 45 | * A-008 (Heather):'''Done''' Once A-005 is done, check flux_sig/flux ratio for true positive |
