RHESSI Tohban report, 19-aug-2002 to 26-aug-2002 J.McTiernan, jimm@ssl.berkeley.edu 1. Solar Activity: Plenty of activity, numerous C-flares, one or two M flares/day, one X3.5 for which RHESSI observed the first 20 minutes, but skipped the SXR peak. (See http://hesperia.gsfc.nasa.gov/hessidata/metadata/2002/08/23/hsi_20020823_233700_rate.png and the plots that follow. There is an odd little hump in the > 100 keV channels, but probably not flare gamma-rays, since there is no excess emission in the 50-100 keV channel.) 2. Memory Managment: Due to activity, shutters were in 1-3 mode for most of the week. For 20-aug, 24-aug, 25-aug, and 26-aug, we used the following procedure: When the SSR_fill level dropped below 40%, shutters were put into 0-1-3 mode, (typically the 2nd BGS pass). The shutters were placed back into 1-3 mode during the last pass. An exception was made on 24-aug when the shutter was put in for 1 orbit during the long decay of the X flare. This procedure resulted in the SSR fill level of 45-50% at the start of the passes, and 25-30% at the end of the passes. For 21-aug, 22-aug and 23-aug, the shutters were left in 1-3 mode the entire time to reduce memory down to just less than 20%. There was not time to pull the this attenuator out on the last pass for the 23-aug, so the memory was only filled to 48% by the X3.5 flare. 3. Data Gaps: None due to pointer movement, since the shutter was in for the X flare. There are several small gaps on 19-aug and 20-aug. 4. Misc: There is now a setup.hessi_env file to the home tohban directory, to define some env variables for orbit data access. Also there is now a web document "tohban_useful_idl" to the tohban home page. This includes some documentation for the hsi_any_sohdata routine, which can be used to get SOH data, the hsi_obs_summ_flag object, which can be used to get info about attenuator states, decimation, and all sorts of other things, and also the function hsi_ssr_fill_per_orbit, which can be used to return the difference in SSR fill level for a given orbit. Note that you need to setenv the DISPLAY variable in your tohban session correctly to use SSWIDL for a remote shell (at least till there is ssh access).