Changes between Version 66 and Version 67 of PS1_IPP_CzarLog_20111017

Timestamp:

Oct 25, 2011, 12:34:49 PM (15 years ago)

Author:

Mark Huber

Comment:

--

PS1_IPP_CzarLog_20111017

@@ -80 +80 @@
  * 16:50 two LAP chips stuck in update.. likely due to chip data on ipp036, why not faulting?
  * 19:40 registration stalled, restarted. stare night but some normal 3PI data taken at beginning.
- * 22:00 not able to unstick LAP, looks like ipp036 hit each group unsurprisingly. queuing up a new group to see if makes it though. not with secondary instances on ippb00. loaded 2 manually to work through
+ * 20:00 summary of attempts to move LAP along 
+{{{
+- collection of XY76 chips having problems, setting qualty to 42 but wait to set corrupt until looked at when ipp036/ippb00 back up
+-- stuck in chipRun as update
+ chiptool -updateprocessedimfile -set_state full -chip_id 328426 -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -fault 0 -set_quality 42 -chip_id 328426 -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -set_state full -chip_id 328452 -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -fault 0 -set_quality 42 -chip_id 328452 -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -set_state full -chip_id 328507 -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -fault 0 -set_quality 42 -chip_id 328507 -class_id XY76 -dbname gpc1
+-- didn't help, try and drop from the LAP set. no change
+laptool -updateexp -lap_id 1381 -exp_id 169255 -set_data_state drop
+laptool -updateexp -lap_id 1368 -exp_id 222467 -set_data_state drop
+-- also stuck in chipRun update due to XY55 on ipp036, if set to quality to 42 move it forward? no
+ chiptool -updateprocessedimfile -set_state full -chip_id 308565  -class_id XY55 -dbname gpc1
+ chiptool -updateprocessedimfile -fault 0 -set_quality 42 -chip_id 308565  -class_id XY55 -dbname gpc1
+-- stuck in destreak
+ chiptool -updateprocessedimfile -set_state full -chip_id 328511  -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -fault 0 -set_quality 42 -chip_id 328511  -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -set_state full -chip_id 328571  -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -fault 0 -set_quality 42 -chip_id 328571  -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -set_state full -chip_id 328615  -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -fault 0 -set_quality 42 -chip_id 328615  -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -set_state full -chip_id 328641  -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -fault 0 -set_quality 42 -chip_id 328641  -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -set_state full -chip_id 328643  -class_id XY76 -dbname gpc1
+ chiptool -updateprocessedimfile -fault 0 -set_quality 42 -chip_id 328643  -class_id XY76 -dbname gpc1
+-- 8 camera exposures stuck, try dropping one of them from LAP. still stuck
+laptool -updateexp -lap_id 1375 -exp_id 174295 -set_data_state drop
+}}}
+ * 22:00 not able to unstick LAP, looks like ipp036 hit each group unsurprisingly. queuing up a new group to see if makes it though. not with secondary instances on ippb00. loaded 2 manually to work through and also stalls
 {{{
 laptool -definerun -dbname gpc1 -projection_cell skycell.1670 -tess_id RINGS.V3 -ra 327.273 -decl 14 -radius 5 -seq_id 8 -label LAP.ThreePi.20110809 -dist_group LAP.ThreePi -filter z.00000