RHESSI TOHBAN REPORT 11/17/04 - 11/24/04 Hugh Hudson (hhudson@ssl.berkeley.edu) 1) Solar Activity A low level of activity, but not an utter low - the daily GOES average did not go below B. At present a new eager active region has appeared at the SE limb and has been making C-class flares. How many GOES flares occurred? Flares above B, C, M, X class were 28 12 0 0 And how many of these are listed in the RHESSI flare list? Flares above B, C, M, X class were 7 9 0 0 And how many had EXCELLENT coverage? Flares above B, C, M, X class were 4 7 0 0 There were RHESSI flares/GOES flares 32 / 40 over the time range 16-Nov-04 23-Nov-04 2) Memory Management Memory usage began the week deep in the hole, but has recovered. On the first BGS pass today the SSR fill was below 40%. RHESSI is heading for a local maximum (Nov. 26) in length of orbit day at > 74 minutes. 3) Data Gaps 18-Nov 13:05 - 15:50, unfortunately containing an interesting fast flare at 15:00. 4) Special operations From Mark: "The new table increases torque authority while in ACS normal mode, from 30 amp-m^2 to 45 amp-m^2. This is still well below the 60 amp-m^2 used in ACS precession mode. The new table was loaded at 2004-323-00:52:17 UT. The flight ops team will be closely monitoring ACS performance." 5) Shutter-moving particle events See 16-Nov, 20 Nov, 21 Nov ~ 20:00; we were driven into the A3 state. And voila, the SOH daily averages of the particle rates reached their 5th-highest level in RHESSI history in the HE channel. The tohban surmises that this resulted from the particle events of Nov. 8 or Nov. 10. But why was the injection so delayed? Were there two injections, the 16th and the 20th? Note that these big particle events often confused the flare finder and probably contributed to our SSR problem. Another odd shutter motion took place 18-Nov 11:52 or so, with no obvious cause (no GRB in the GCN circular listing). According to David Smith, "The odd shutter movement on Nov 18 was due to an arc in detector G6, which resulted in a temporary high fast-LLD rate and a corresponding temporary dip in livetime. The attenuators trigger on a drop in the average livetime over several detectors, including G6. They do not check to see if the deadtime is due to only one detector or is shared equally." 6) Observing campaigns None the tohban is aware of. 7) Next week's tohban This week's tohban inadvertently left the beeper at home today and therefore, according to a newly established precedent, will continue to be tohban next week too.