RHESSI Tohban report, 06-Apr-2004 to 12-apr-2004 Hugh Hudson, hhudson@ssl.berkeley.edu 1. Solar Activity There was essentially only a single active region, 588, at the end of the week. As it progressed across the disk to about W40 it had an almost M flare; then and only then did an SEP occur. How many GOES flares occurred? Flares above B, C, M, X class were 32 6 2 0 And how many of these are listed in the RHESSI flare list? Flares above B, C, M, X class were 13 4 2 0 And how many had EXCELLENT coverage? Flares above B, C, M, X class were 10 0 1 0 There were RHESSI flares/GOES flares 45 / 40 over the time range 04-Apr-04 11-Apr-04 As usual, the RHESSI flares are undercounted because of the processing latency. Note last week's report, which caught up on this comparison over a longer interval and found a roughly 2/1 ratio of RHESSI flares to GOES flares. 2. Decimation Normal/Normal all week. 3. Memory Management Starting fill levels on the order of 25%, so no problem. The particles may be coming back, though... 4. Data Gaps There were no data gaps of any significance through 08:00 April 8. Looking backwards, the first five hours of April 1 are missing - was this reported? The quicklook processing is complete through 08:00 April 9, 2004. This is longer latency than usual. Is it related to the near-disaster reported at the operations meeting, where the Wallops data had been lost due to a glitch in the data-handling process. 5. Time variability of cooler diagnostics A quick look at the VC1 time series shows that the dominant period in the variability noted last week is at about 4 minutes. 6. Special incident: ADP exception No further trouble with the ADP this week. 7. Tohban Andre Csillaghy volunteered to be the next tohban, and Richard Schwartz after that.