| | 58 | |
| | 59 | * 10:57 CZW: Mark pointed out an exposure that was stuck with chipRun.state = 'error_cleaned' and warpRun.state = 'update'. This blocks LAP somewhat, as it waits for a warp that is waiting for a chip that isn't updating because chiptool refuses to update data that isn't in state 'cleaned'. This has happened on occasion before, and my solution has been to issue the commands generated by the output of {{{/data/ippc18.0/home/watersc1/PV2.LAP.20130717/fixes/scan_chips_for_errorCleaned.sql}}}. An example output is listed below. The run_update_for_chip_id.pl script issues the chiptool/camtool/warptool commands to set things to be updated. |
| | 60 | {{{ |
| | 61 | chiptool -updaterun -set_state cleaned -chip_id 574277 |
| | 62 | chiptool -updaterun -set_state cleaned -chip_id 574396 |
| | 63 | chiptool -updaterun -set_state cleaned -chip_id 574444 |
| | 64 | chiptool -updaterun -set_state cleaned -chip_id 837183 |
| | 65 | /home/panstarrs/watersc1/bin//run_update_for_chip_id.pl 574277 |
| | 66 | /home/panstarrs/watersc1/bin//run_update_for_chip_id.pl 574396 |
| | 67 | /home/panstarrs/watersc1/bin//run_update_for_chip_id.pl 574444 |
| | 68 | /home/panstarrs/watersc1/bin//run_update_for_chip_id.pl 837183 |
| | 69 | }}} |
