| | 1 | Grand Reprocessing Concerns/wishlist |
| | 2 | |
| | 3 | * burntool is not complete / done for certain days. |
| | 4 | * Is there a way to reburn these days? If so, it needs to be documented |
| | 5 | * Can we automatically detect & reburn these, rather than have a human find them (as they fail), and requeue by hand? |
| | 6 | |
| | 7 | * Can we have a well defined and complete document/wiki of what the |
| | 8 | reprocessing tasks are? |
| | 9 | * the different stages for each survey |
| | 10 | * the different diffs |
| | 11 | * with well defined processing, we will know ultimately what should happen |
| | 12 | to each exposure. We should have a webpage to track each exposure, so that |
| | 13 | we can verify each exposure goes through all the necessary stages (unlike |
| | 14 | now, where nightly science tasks like stacks and diffs often get missed) |
| | 15 | |
| | 16 | * can we have a robot that automatically queues things for us (and adds them |
| | 17 | to pantasks as necessary?) |
| | 18 | |
| | 19 | * We should add a column in rawImfile or rawExp for files which can't be |
| | 20 | processed, and chiptool should avoid queueing them. |
| | 21 | * some of these files are misfires (the camera died or other camera glitches) |
| | 22 | * some of these are ones that the observers flag as bad in email |
| | 23 | * this can simplify things for future reprocessings (whether GR2 or special |
| | 24 | request reprocessing) |
| | 25 | |
| | 26 | * will there be improved diff photometry? |
| | 27 | |
