RHESSI Tohban Report, 24-mar-2003 to 31-mar-2003 Paula Balciunaite, balciunaite@ssl.berkeley.edu (1) Solar Activity: Solar activity rose from baseline ~B2 at the beginning of the week to ~B6-B7 at the end of the week, with 23 C flares, 10 of which were partially or totally observed by RHESSI: 24-MAR-03 04:26 04:31 04:35 C2.0 26-MAR-03 17:05 17:10 17:17 C2.2 27-MAR-03 01:56 02:01 02:14 C2.2 27-MAR-03 09:40 09:45 09:49 C3.6 (only decay phase) 27-MAR-03 14:49 14:55 15:05 C2.3 (only impulsive phase) 27-MAR-03 19:38 19:43 19:51 C1.6 29-MAR-03 10:11 10:15 10:25 C7.2 (only impulsive phase) 29-MAR-03 12:24 12:30 12:35 C5.7 29-MAR-03 20:47 20:51 20:54 C1.3 30-MAR-03 01:21 01:25 01:29 C3.6 Unfortunately, we have data gaps during the times of these flares: 27-MAR-03 01:56 02:01 02:14 C2.2 (seems to be replayed, except with a small glitch at ~2:06) 27-MAR-03 09:40 09:45 09:49 C3.6 (only decay phase) (only first 2 minutes after SAA lost). (2) Antenna: This was the week of antenna problems. After last weekend's power outage, BGS went out of operation because of a problem with one of the Windows NT operating system files on the PC inside the antenna. The BGS was back in operation Monday night, and the science/engineering data downlinked to Wallops and Santiago stations during the downtime was recovered at that time. Then, Wednesday night BGS was down again, this time because the antenna brakes stopped disengaging. The last 3 BGS passes were missed that night. The problem turned out to be a malfunctioning CMOS chip in the antenna electronics. BGS was back up Thursday night just in time for the next set of passes, and the data from the lost passes was recovered. (3) Attenuators: The attenuators were in an autonomous mode all week, although during some flares, temporarily changed to State 1. (4) Memory Management/Decimation tables: Decimation table T3 (Quiet Solar Region Configuration) was loaded the entire week. However, some apparent abnormalities in the corrected count rate plots (pointed out by Martin Fivian) warranted a check with the operators whether T3 was really loaded on Mar 22. It turned out that the following mistake was made in loading the tables: Procedure to load decimation table T4 (Active Solar Region Configuration) (Mar 18): > idpu_load_ssrtable_active (this was not done) > idpu_load_dectables_active Thus T4 was loaded, but not the corresponding SSR Table. T3 was then loaded the following way, without reloading the SSR Table (Mar 22): > idpu_load_dectables It is to be determined what effects such a procedural deviation could have and why. (5) Data Gaps: GAPS IN APP_ID = 102 (VC3-MONITOR RATES) WITH PACKET RATE LT 30 N_GAPS 3 GAP START TIME GAP END TIME GAP (SEC) 2003-03-24T01:55:00.000Z -- 2003-03-24T02:10:00.000Z 900.00000 2003-03-24T17:20:00.000Z -- 2003-03-24T17:25:00.000Z 300.00000 2003-03-24T23:40:00.000Z -- 2003-03-24T23:50:00.000Z 600.00000 2003-03-25T23:20:00.000Z -- 2003-03-25T23:30:00.000Z 600.00000 2003-03-25T23:35:00.000Z -- 2003-03-25T23:50:00.000Z 900.00000 2003-03-27T02:05:00.000Z -- 2003-03-27T02:10:00.000Z 300.00000 2003-03-27T09:10:00.000Z -- 2003-03-27T09:45:00.000Z 2100.0000 2003-03-28T15:00:00.000Z -- 2003-03-28T15:25:00.000Z 1500.0000 2003-03-29T03:10:00.000Z -- 2003-03-29T06:35:00.000Z 12300.000 2003-03-29T09:20:00.000Z -- 2003-03-29T09:25:00.000Z 300.00000 GAPS IN APP_ID = 154 (VC1-PMTRAS) WITH PACKET RATE LT 4 N_GAPS 1 GAP START TIME GAP END TIME GAP (SEC) 2003-03-25T11:20:00.000Z -- 2003-03-26T00:00:00.000Z 45600.000 2003-03-26T00:00:00.000Z -- 2003-03-26T02:15:00.000Z 8100.0000 2003-03-28T01:00:00.000Z -- 2003-03-28T02:20:00.000Z 4800.0000 2003-03-29T09:00:00.000Z -- 2003-03-29T10:45:00.000Z 6300.0000 GAPS IN APP_ID = 1 (VC1-SOH) WITH PACKET RATE LT 30 N_GAPS 1 GAP START TIME GAP END TIME GAP (SEC) 2003-03-29T09:00:00.000Z -- 2003-03-29T10:45:00.000Z 6300.0000 (6) Other: Conversion between IDPU Version # and Decimation Table ID (thanks to Jim McTiernan) is now added to the Tohban page.