RHESSI Tohban report, 27-aug-2002 to 02-sep-2002
Martin Fivian, mfivian@ssl.berkeley.edu

1. Solar Activity:

- Low to medium activity. (3 M-class flares, 1 X-class flare)
- Sometimes background level up to C4
- Several particle stormes during BGS passes (mostly during night)
- Another X-class flare has been observed between night and SAA. Somewhere in the
  decay, RHESSI went into SAA.

Aug 28
8330 +     1645   1658      1709  GO8  5   XRA  1-8A      M1.3 1.3E-02   0083

Aug 29
8440 +     0245   0253      0302  GO8  5   XRA  1-8A      M1.6 1.1E-02       
8520 +     0456   0506      0526  GO8  5   XRA  1-8A      M1.8 2.3E-02       
8610 +     1242   1252      1256  GO8  5   XRA  1-8A      M3.2 1.5E-02   0095 (night)

Aug 30
9010 +     1247   1329      1335  GO8  5   XRA  1-8A      X1.5    7.0E-02   0095


2. Attenuator Operation:

attn mode 0-1-3 : state 0, Aug 28, 11:25UT - (autom to state 1 before Aug 29, 01:25)
attn mode 0-1-3 : state 0, Sep 02, 10:30UT -
expect attn state 0 : 10:57 - 

attn mode 1-3 : state 1, otherwise


3. Memory Managment:

During most of the week, the shutters were in 1-3 mode. 
On Aug 28, During the last pass of the serie the shutters has been commanded
to 0-1-3 mode and the thin shutters has been pulled out. The Solar activity filled up
the SSR to 70% until the first pass on the next serie. It took several days to
get down to a normal level again because of two reasons. First, several
particel stroms accured in high magnetic lattitude and the GOES background
level went temporily up to C4.

SSR fill levels after the last passes of the BGS series of passes:

Aug 28, 24.7 %
Aug 29, 39.6 %
Aug 30, 32.9 %
Sep 01, 24.3 %
Sep 02, 18.4 %


4. Data Gaps:

Aug. 28, 00:00 - 03:10, new ATS hasn't been loaded and old ran out.

None due to pointer movement.


5. Misc:

The ATS load with the S/C commands starting at Aug. 28, 00:00 UT hasn't been
uploaded with the following consequences:

- transmitter didn't go on
- no imager day/night activity
- no SAA/high magn lattitude transitions
- and therefore, the mentioned data gap

It took a while to figure out what happened. It seems that there is a hole in the
sceme of monitoring the operation which has to be fixed before we go to autonomous
operation.