| | 1 | This FAQ page is intended as a place to post questions and answers about faults and failures that clog up the IPP. It is organized into sections for each of the primary steps of the IPP. |
| | 2 | |
| | 3 | === Load and Setup === |
| | 4 | ==== INJECT ==== |
| | 5 | |
| | 6 | ==== REGISTER ==== |
| | 7 | |
| | 8 | === Detrends === |
| | 9 | |
| | 10 | ==== DETREND CREATION ==== |
| | 11 | |
| | 12 | === Science Processing === |
| | 13 | ==== CHIP ==== |
| | 14 | |
| | 15 | ====="I've got a few bad cells in an otherwise acceptable GPC1 exposure. How can I cover up the faults from one cell in order to proceed past the chip stage?"===== |
| | 16 | |
| | 17 | You can set the 'ignored' field to 1 in the rawImfile table for the exposure and class_id of interest. Some chips in the corner of the GPC1 (e.g. chip XY17) are really poor, so doing this can be a good idea anyway. If the offending -and now ignored - chip continues to block the camera stage, you may need to 'revert' any faulted rawImfile and chipProcessedImfile entries with regtool and chiptool. |
| | 18 | |
| | 19 | Note that chiptool will only revert a chipProcessedImfile that has a non-zero fault value, so you must first use "-updateprocessedimfile -code 6" or something, and then do "-revertprocessedimfile -code 6" to re-run them. Furthermore, once you've set a class_id to 'ignored' then it won't run through the chip stage at all, so you'll have to revert some other class_id in order to re-start the pipeline for that chipRun. |
| | 20 | |
| | 21 | ==== CAMERA ==== |
| | 22 | |
| | 23 | ==== FAKE ==== |
| | 24 | |
| | 25 | ==== WARP ==== |
| | 26 | |
| | 27 | ==== STACK ==== |
| | 28 | |
| | 29 | ==== DIFF ==== |