Dear Members of the Low Energy Group: We at CSUDH would be willing to take on the responsibility of formulating and disseminating the good run list. We are presently hiring several undergraduate students as part of our NSF Super-K research grant. This task would provide us with a good technique for getting our students actively involved in the nuts and bolts of the experiment. We will have one CSUDH undergraduate with a backup supervised by myself work on this project. I propose that we (the CSUDH group) do the following. We will obtain information from the log books (these are presumambly at the mine), the "summary" files, and directly from the shift workers (electronically). We will compile a run summary and add it to a database at a world wide web site at both CSUDH and UCI soon after the conclusion of each run. The run summary would contain the following information, suggested by Bob Svoboda, and other information agreed upon by the US low energy group; 1. Run number 2. number of low energy events read by the DAQ 3. Number of low energy events that are written to disk that pass the Level-1 filter. 4. Number of low energy events written that pass the Level-2 filter 5. The GPS start time recorded on tape (for the run) 6. The GPS end time recorded on tape. 7. The live time for the run 8. The run type (normal data, special data (e. g. very low threshold), calibration, source, etc.) 9. Special run information such as the source or laser position, location of flashers, major failures, interesting events recorded on line (like the New York Times and Dan Quayle proton decay events of IMB). The good run list web site project is one that will significantly benifit our undergraduates and will help us to fufill some of the major goals of our NSF grant; to introduce the CSUDH undergraduates to Elementary Particle Physics Research and to encourage and mentor them to go to careers in the Sciences and Engineering. Please send me your suggestions......Ken Date: Tue, 18 Jun 1996 22:30:43 +0900 (JST) From: William Keig Run 1921 Start 6/17 02:20 End 6/17 12:52 Normal trigger Good run but no checksheet. Ended because no OD data. Run 1920 Start 6/17 00:34:34 End 6/17 02:15:20 Normal trigger Good run ended because no OD data Run 1919 Start 6/16 16:34:57 End 6/17 00:29:47 Normal trigger Good run ended because no OD data Run 1917 Start 6/15 19:53:36 End 6/16 16:04:07 Normal trigger Good run BUT! You may either take the attitude that there is no run 1918, or you may take the attitude there is no run 1917. Because of an operator error the end of run summary lists this as run 1918. [The operator reset this from 1918 to 1917 later in the initialization process than she should have]. In analyzing this run watch for periods of no data from PMTs controlled by Hut 2 Channel 2.3. Several HV trips at that channel. When I call a run ended by no OD data good, that means we were getting frequent error messages only near the end of the run complaining about no OD data. The actual message was "Anti-counter header only!" --- Bill Date: Tue, 18 Jun 1996 20:56:51 +0900 (JST) From: William Keig Subject: more recent runs What I have for more recent runs is not as good because the computer stopped printing run summaries with Run 1930 and until now no one inquired why. Run 9999 Start 6/18 02:45:11 End 6/18 03:00:06 Normal trigger Dummy run, whatever that means. I think it doesn't belong on your good run list. Run 1928 Start 6/18 02:50 End 6/18 02:54 Normal trigger Bad run. Stopped for anticollector stack. Run 1929 Start 6/18 03:03:54 End 6/18 05:23 Normal trigger May not be a good run. Stopped because disk/export/online3 is full and cannot write. This halt was followed by a sukonh disk crash. Run summary is garbage, and who knows what other mischief the disk crash caused? Run 1930 Start 6/18 11:56 End 6/18 11:59 Normal trigger The first of 3 bad runs, also no run summary for this and all the next ones. No OD data. Run 1931 Start 6/18 12:11 End 6/18 12:13 Normal trigger Bad run. No OD data. Run 1932 Start 6/18 12:20 End 6/18 12:25 Normal trigger Bad run. No OD data. Run 1933 Start 6/18 12:39 End 6/18 14:42 Normal trigger At 12:45 GPS cable not working [editorial comment not worth publishing: this meant that kingfish got the wrong times for the events]. Jiggled then OK. Probably good run. Stopped to put in new internal hard disk. [see 1929 in connection with this] Run 1934 Start 6/18 17:14 End 6/18 17:20 Normal trigger Bad run. This was the first of several runs designed to test the effect of lowering the Low Energy threshold. For this run it was lowered to 300 mV (from 320 mV). It was a bad run because Hut 2 gave event mismatch. After several failed attempts we finally succeeded in getting Hut 2 online. Run 1935 Start 6/18 18:10 End 6/18 18:19 Normal trigger Low energy threshold at 300 mV Run 1936 Start 6/18 18:22 End 6/18 18:36 Normal trigger Low energy threshold at 290 mV Run 1937 Start 6/18 19:19 End 6/18 20:26 Normal trigger Low energy threshold at 296 mV Runs 1935 to 1937 should probably be considered good runs. The only difference is their higher trigger rates. --- Bill