Changes between Version 1 and Version 2 of req_5977

Timestamp:

May 27, 2010, 4:11:05 PM (16 years ago)

Author:

bills

Comment:

--

req_5977

@@ -1 @@
-This request came in on May 27. It has 2624 rows most of which are bycoord requests. These are the slowest to parse.
+This request came in on May 27. It has 2624 rows all of which are bycoord requests. These are the slowest to parse.
 
 The request started parsing at 13:38 HST May 27. We can see this because that is the time stamp on the request file. At 15:55 it is about half done. 4994 jobs have been queued so far and all but 200 are requests for cleaned up data. So the parsing will probably complete
 around 18:00
 
-
-
-The program pstampdump can be used to list the contents of a fits table
-
+The following is a diary of me watching this request process. If some faults occur this may provide a debugging and repair
+tutorial.
 
 {{{
+# The program pstampdump can be used to list the contents of a fits table
+
 (ippdb02:work/20100527/5977) bills% pstampdump -simple web_1695.fits > dumpreq.txt
 
@@ -43 +43 @@
 1 row in set (0.02 sec)
 
+# where are we now?
+(ippdb02:work/20100527/5977) bills% date ; grep -n `grep Collected psparse.5977.log | tail -n 1 | awk '{print $7}'` dumpreq.txt
+Thu May 27 16:06:56 HST 2010
+1665:100774 205.543583 28.359453 100 100 2 stamp 1 gpc1 bycoord chip null null null null y 0 0 search 
 
+1665 of 2564 64%
+
+# There are lots of dependents pending. The poll limit in pstamp  pantasks is 256 so 1/4 of these are queued for updates.
+
+(ippdb02:work/20100527/5977) bills% pst -pendingdependent -simple | wc
+   1027   11297   94484
+
+No faults in the pstamp or update pantasks as yet. 
 }}}