Tohban Report 2013-11-20

From RHESSI Wiki

Revision as of 22:23, 4 September 2014 by Lglesener (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Tohban Reports
Start Date: 13 Nov 2013
End Date: 20 Nov 2013
Tohban: Lindsay Glesener
Tohban email: glesener@ssl.berkeley.edu
Next Tohban: Mitsuo Oka
List all reports



Contents

Solar Activity

While it was a mostly quiet week, there were some highlights, including an X1.0 class flare on 2013/11/19 at 10:14:00 near the western limb. RHESSI missed most of the impulsive phase but caught the first few minutes (preimpulsive phase). The GOES baseline flux level was approximately C1 class for most of the week, though it has since quieted down to upper-B class. For a good portion of the week, there were C-class flares happening so often that RHESSI was recording flares almost continuously. This produced more data than normal for a quiet week, but not to the extent that there were problems with the SSR fill.

There are currently 8 active region on the disk, with 3 of them flaring (mostly C flares). Region 11893, which produced the X flare, is right on the western limb and so will soon be occulted. This region has decayed a bit and has not produced much today, but there is still a Major Flare Watch in effect due to the X flare yesterday. With that active region decaying and rotating off, and the other regions producing only C flares, I expect that activity will not be high in the next few days.

How many GOES flares occurred?

 Flares above B, C, M, X class were      0    77     5     1

And how many of these are listed in the RHESSI flare list?

 Flares above B, C, M, X class were      0    53     4     0

There were RHESSI flares/GOES flares 404 / 83 over the time range 13-Nov-13 20-Nov-13

Memory Management

No issues. SSR max was 22%; it's emptying by the end of each pass set.

Spacecraft Status

Cold plates 1 and 2 are at 118.5 and 117, respectively.

Spin rate is 14.6; a spinup should be performed in the next ~2 weeks.

Data Gaps

A single corrupted APPID packet on Nov. 15.

Detector issues

Isolated spike in D1 on Nov. 10 at 11:39, maybe caused by attenuator shift.

Other notes

Decimation Active/Vigorous
HLAT Decimation Rear decimation weight 6, no front decimation
Night time data (fronts) Disabled, except for +/- 4 min
Night time data (rears) Enabled
Require extra passes? No
Requirement for moving pointer? No
Attenuator operation Normal
Detector problems? Small, isolated spike D1
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox