| | 32 | * Propagate zero points from cam to diff. Source lists from ppSub now have calibrated magnitudes. |
| | 33 | * Propagate FWHM from warp to diff for ppSub parameter scaling. ppSub now doesn't have to measure the FWHM (at least for warps; not tested on stacks yet). |
| | 34 | * Diff failures: |
| | 35 | * MD06.077 failing due to bad reference stack (stack_id = 52606); fixed error code. |
| | 36 | * Every other fault=2 inspected was due to filesystem errors. |
| | 37 | * All fault=5 have dtime_script <= 3 sec, apparently due to difftool unable to find the SQL file. |
| | 38 | * Reworked all ippTools to put fault=2 (SYS_ERROR) when can't find SQL file (presumably due to NFS problems). Removed DATA_ERROR because ippTools don't work on data (astronomical images or catalogues). This should allow us to turn on revert for fault=2 only. |
| | 39 | * Reworked ppSub to be better about error codes and their translation to exit codes. |
| | 40 | * Add exposure comment to data store when publishing detections. |
| | 41 | * Stack failures: |
| | 42 | * "Stack list contains less than 2 elements" accounts for most of the fault=2. Added "-min_num 4" to automate_stacks.pl and stacktool now requires min_num to be specified and >= 2. |
| | 43 | * fault=5 modes: |
| | 44 | * A bunch of failures in the relative photometry that doesn't make sense on reading the log. They may be due to rebuilding the code mid-way and repeating. Best to revert and retry. |
| | 45 | * dtime_script < ~ 10 are generally due to all (or most) inputs having few lit pixels. Added "-select_good_frac_min 0.05" to automate_stacks.pl to correspond with BADFRAC in the PPSUB recipe. |
| | 46 | * Nebulous errors account for most of the rest, often reading from ipp004 from a range of machines. |
| | 47 | * Reworked ppStack to be better about error codes and their translation to exit codes. |
| | 48 | * fault=4 (PROG_ERROR) seem to be due to failure to find a PSF model, and then triggering a SEGV in ppStack; fixed SEGV. |
| | 49 | * Chasing down camera runs in ThreePi.Run5c.20100217 that didn't write all masks |
| | 50 | * 399/2655 = 15% have at least one missing mask (actually, this can be due to bad data quality at chip stage too) |
| | 51 | * Fixed camera_exp.pl to check that masks are written |
| | 52 | * Fixed warp_skycell.pl to ensure mask is available |
| | 53 | * Re-ran camera stage through pcontrol for bad runs |
