Changes between Version 80 and Version 81 of Processing
- Timestamp:
- Aug 5, 2010, 3:07:18 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Processing
v80 v81 230 230 == Reverting == 231 231 232 Another column in the same tables is 'fault', which is populated with integer values with the following definitions:232 When exposures fail at a certain stage (chip, cam, warp etc) they are given a 'fault' code: 233 233 234 234 || '''Code''' || '''Description''' || … … 241 241 || >6 || Reserved for magic || 242 242 243 The faults are often of value '2', which is more often than not an NFS error and can be resolved by 'reverting'. For examples, for warps with a fault 2, you can revert with 243 It is sometimes possible to 'revert' certain failed exposures. Reverting simply means attempting to process an exposure second time in case the cause of the fault was temporary, for example an NFS error. Faults like these are usually given fault code '2'. Turning reverts on via the czartool page will attempt to revert all those exposures that failed with code '2'. Behind the scenes, czartool is using {{{pantasks_client}}} to perform the reverts, as described in the next section. 244 245 === Reverting from {{{pantasks_client}}} === 246 247 To manually revert failures with fault code 2, do something like the following in {{{pantasks_client}}} 244 248 245 249 {{{ … … 247 251 }}} 248 252 249 Remember to switch off again afterwardswith253 And off again with 250 254 251 255 {{{ … … 268 272 destreak.on 269 273 }}} 274 275 === Reverting faults with codes other than 2 === 276 277 By running the stage tool program directly it may be possible to revert failures with codes other than 2. For example, for the chip stage: 278 279 280 {{{ 281 chiptool -revertprocessedimfile -label M31.nightlyscience -fault 4 -dbname gpc1 282 }}} 283 284 Similar arguments can be used with {{{warptool}}}, {{{camtool}}} etc. 285 270 286 271 287 == Removing a troublesome host ==
