IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links
wiki:Processing_Log

Version 14 (modified by bills, 16 years ago) ( diff )

--

This page is intended to be a running log of the special activities of the IPP Processing Czar

2010-06-09 Bill

  • Bad weather last night never opened.
  • chip processing was generating lots of errors due to missing detrends. It turns out that some engineering exposures got made with obs_mode = '3PI'. Set these chipRuns to drop.
  • camRun 85769 repeatedly failed. exp_name o5354g0523o. jpeg images for exposures around this time have lots of missing chips. Observing log says 'g0490o - g0523o Most of these exposures were taken in twilight and need to be redone' Set camRun to drop with note to this effect
  • 4 warpSkyfiles were repeatedly failing. This was because one of the input images chip_id 100112 class_id XY17 was corrupted. Re-ran chip_imfile.pl by hand, reverted warp, and it completed. The command line was
     chip_imfile.pl --no-update --verbose --exp_id 176615 --chip_id 100112 --chip_imfile_id 5832194 --class_id XY17 --uri neb://ipp026.0/gpc1/20100603/o5350g0442o/o5350g0442o.ota17.fits --camera GPC1 --run-state new --deburned 0 --outroot neb://ipp026.0/gpc1/ThreePi.nt/2010/06/03/o5350g0442o.176615/o5350g0442o.176615.ch.100112 --redirect-output --dbname gpc1
    
    
  • What!? camRun 85769 got set changed from drop to new! Looks like camtool -revertprocessedexp is obsolete. Paul investigated and fixed in trunk.
  • 4 of the twilight exposures from MJD 55354 failed at warp stage. Set the corresponding runs' state to 'drop'.
  • Eric Morganson reports that some postage stamp requests he submitted last night (HST) didn't complete. Turns out each one referenced some warpRuns in unexpected state: state = 'full' magicked = -1 Fixed by setting the corresponding magicDSRuns to state new. This shouldn't have happened. Magicked gets set to -1 when cleaned and at update time, since the chips are magicked the warps are magicked. These were the only runs in this state (at any stage) so I let this go for now.
  • Investigated incomplete runs
    • warp - 38 runs were descendents of camRuns with poor quality. This is a bug in camtool. It should not advance run to fake if the quality is poor. Set to drop. Checked fix to camtool into the trunk.
    • diffRun 58718 and stackRun 116037 are blocked because one of their inputs warpSkyfile 70847 skycell.075 is corrupt
    • stackRun 116184 gets 'no fake sources suitable for PSF fitting'
    • distRun 177188 component X15 from chipRun 94549 is corrupt (streaksremove output)
    • 117 magicDSRuns were in state new but the corresponding warpRuns had been purged. Set to goto_cleaned.
    • magicDSRun 52543 for camera stage cannot proceed because the chipRun has been cleaned. Set to goto_cleaned.
    • magicDSRun 162057 for chipRun 99733 cannot proceed because the camera mask file for chip XY17 is corrupt (camRun 83891)
    • magicDSRun 152644 for diffRun 56728 repeatedly fails on skycell.2266.020 with fault 4 The program segvs due to a bug in the function censorSources. It looks like the input cmf file may be corrupt. Fix to streaksremove committed to the trunk.
    • 4 diff stage distRuns were in state new but the corresponding diffRuns had been cleaned. Set to goto_cleaned
    • 49 diffRuns in state new but the corresponding warpRuns have been cleaned.
    • several magicRuns were in state new with diffRuns that have been cleaned. Set to drop. Changed magictool to allow state = 'drop'
    • 23 magicRuns were in state new whose corresponding diffRuns were in state 'new' This is quite bizarre. The data_group was ThreePi.20100XXX where XXX in 221, 222, 223, 227, 228, 301. Set magicRun.state to drop.
Note: See TracWiki for help on using the wiki.