Changes between Version 5 and Version 6 of PS1_IPP_Czarlog_20131223

Timestamp:

Dec 24, 2013, 3:31:13 PM (13 years ago)

Author:

eugene

Comment:

--

PS1_IPP_Czarlog_20131223

@@ -12 +12 @@
 
  * 11:10 EAM : a lot of LAP runs were blocked by chip runs in state of error_cleaned.  I conferred with Bill and he put them all in state goto_cleaned and they are cleaning up.
+ * 15:30 EAM : there were a number of lapExp entries in the active lap runs which were in an inconsistent state: lapExp.data_state was 'full' but there were outstanding chips or warps to be updated.  I set these lapExp entries to a data_state of 'pending_update' and things now seem to be running.  query to list the inconsistent states:
+
+{{{
+select lap_id, lapExp.data_state as lap_data_state, lapExp.exp_id, chipRun.chip_id, chipRun.state as chip_data_state, chipRun.label, camRun.state as cam_data_state, camRun.label, warpRun.state as warp_data_state, warpRun.label from lapExp join chipRun using (chip_id) join camRun using (chip_id) join fakeRun using (cam_id) join warpRun using (fake_id) where lap_id >= 20800 and lap_id < 21000 and warpRun.state != 'full';
+}}}
+
+I used commands like this to set the data_state:
+{{{laptool -dbname gpc1 -updateexp -lap_id 20958 -exp_id 78569 -set_data_state pending_update}}}
 
 === Wednesday : 2013-12-25 ===