| | 9 | |
| | 10 | * Processed MD09.20090910 through magic, sent email to harvard with link to data |
| | 11 | * Processed M31.20090917 through magic. |
| | 12 | * Processed MD10.20090915 through chip stage, half fail at cam stage (investigating, some psastro, some ppstats related. ppstats related to burntool state) |
| | 13 | * Processed M31.2008.20090918 through chip stage, half fail at cam stage (investigating...) |
| | 14 | * burntooled all dates between 06-01-09 and 09-16-09 |
| | 15 | * edited [wiki:PS1_DataRequestManagement wiki] to keep track of which data I'm processing: |
| | 16 | * checked md5sum on 568794 gpc1 images, found 6 corrupted images, removed them and replicated the good copy. |
| | 50 | * Began pushing old data through the chip and warp cleanup process. |
| | 51 | |
| | 52 | * Fixed resulting bugs in the cleanup code that did not arise during |
| | 53 | simtest tests. |
| | 54 | |
| | 55 | * Added burntool_state column to rawImfile table, and rewrote |
| | 56 | ipp_apply_burntool.pl and chip_imfile.pl to handle the new burntool |
| | 57 | versioning system. |
| | 58 | |
| | 59 | * Still working on getting register_imfile.pl and ppStats to |
| | 60 | successfully identify if the summit has run burntool, and if so, |
| | 61 | set burntool_state correctly in the database. |
| | 62 | |
| | 63 | * Identified new bug in burntool when run in a two-step process. |
