Tohban Report 2012-04-04: Difference between revisions
imported>Lglesener (Created page with "{{Infobox Tohban Report| |start_date = 29 Mar 2012 |end_date = 4 Apr 2012 |tohban_name = Lindsay Glesener |tohban_email = glesener@ssl.berkeley.edu |next_tohban = }} == Solar ...") |
imported>Lglesener No edit summary |
||
| Line 21: | Line 21: | ||
== Memory Management == | == Memory Management == | ||
At one point the SSR filled. See below. | |||
== RHESSI Operations == | == RHESSI Operations == | ||
April 3, 22:26:42 UT: The SAS data rate was increased for coordinated limb observations with an SDO roll maneuver. Although this commanding was expected to only cause a small increase in the SSR fill, it instead caused the SSR to fill completely. | |||
March 30, 17:53:27 UT: The front fast event threshold for detector 2 was raised by 0x10, from 0x60 to 0x70. This was done in order to save livetime that was being eaten up by excess fast rates in G2 due to light leak. | |||
== Data Gaps == | == Data Gaps == | ||
Revision as of 16:47, 4 April 2012
| Tohban Reports | |
|---|---|
| Start Date: | 29 Mar 2012 |
| End Date: | 4 Apr 2012 |
| Tohban: | Lindsay Glesener |
| Tohban email: | glesener@ssl.berkeley.edu |
| Next Tohban: | |
| List all reports | |
Solar Activity
This was a very quiet week, with no flares above C level. The past few days have been especially quiet, with no flares above B level.
How many GOES flares occurred?
Flares above B, C, M, X class were 16 7 0 0
And how many of these are listed in the RHESSI flare list?
Flares above B, C, M, X class were 12 5 0 0
And how many had EXCELLENT coverage?
Flares above B, C, M, X class were 8 4 0 0
Memory Management
At one point the SSR filled. See below.
RHESSI Operations
April 3, 22:26:42 UT: The SAS data rate was increased for coordinated limb observations with an SDO roll maneuver. Although this commanding was expected to only cause a small increase in the SSR fill, it instead caused the SSR to fill completely.
March 30, 17:53:27 UT: The front fast event threshold for detector 2 was raised by 0x10, from 0x60 to 0x70. This was done in order to save livetime that was being eaten up by excess fast rates in G2 due to light leak.