Tohban Report 2012-04-25

From RHESSI Wiki

Jump to: navigation, search


Tohban Reports
Start Date: 18 Apr 2012
End Date: 25 Apr 2012
Tohban: Claire Raftery
Tohban email: claire@ssl.berkeley.edu
Next Tohban:
List all reports



Contents

Solar Activity

Solar activity was low with only B and C class flares in the past week. NOAA 11465 has just today been classified as beta-gamma so this region may begin to produce larger flares. There are 11 active regions on disk in all, although at least three are on the west limb and may not be observable any more. Stereo B shows that there are a number of regions approaching the eastern limb in the southern hemisphere in the coming days.

How many GOES flares occurred?

 Flares above B, C, M, X class were     11    38     0     0

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

 Flares above B, C, M, X class were      9    26     0     0

And how many had EXCELLENT coverage?

 Flares above B, C, M, X class were      6    14     0     0

There were RHESSI flares/GOES flares 356 / 49 over the time range 18-Apr-12 25-Apr-12

Memory Management

During the week the SSR was emptying by end on the week, reaching a maximum of ~40%.

Spacecraft Status

On 111/15:32 UTC the following commands were sent to change detector G2's front slow threshold to 0x60 and detector G2's front fast threshold to 0x80, also was decided to change detectors G3 and G9's rear fast threshold to 0x60.


Data Gaps

There were many data gaps this week as a result of a fault in the Wallops receiver. This has been rectified and the data is being replayed.

DATA GAPS FOR 2012/04/24
TIME RANGE: 2012-04-24T00:00:00.000 -- 2012-04-25T00:00:00.000
GAPS IN APP_ID = 1 (VC1-SOH) WITH PACKET RATE LT 30
N_GAPS           3
GAP START TIME              GAP END TIME                   GAP (SEC)
2012-04-24T03:30:00.000 -- 2012-04-24T03:40:00.000       600.00000
2012-04-24T06:55:00.000 -- 2012-04-24T07:05:00.000       600.00000
2012-04-24T08:40:00.000 -- 2012-04-24T08:45:00.000       300.00000
NO GAPS IN APP_ID = 154 (VC1-PMTRAS)
GAPS IN APP_ID = 102 (VC3-MONITOR RATES) WITH PACKET RATE LT 30
N_GAPS           6
GAP START TIME              GAP END TIME                   GAP (SEC)
2012-04-24T01:05:00.000 -- 2012-04-24T01:25:00.000       1200.0000
2012-04-24T01:30:00.000 -- 2012-04-24T01:35:00.000       300.00000
2012-04-24T01:40:00.000 -- 2012-04-24T01:45:00.000       300.00000
2012-04-24T05:50:00.000 -- 2012-04-24T06:00:00.000       600.00000
2012-04-24T06:05:00.000 -- 2012-04-24T06:30:00.000       1500.0000
2012-04-24T10:05:00.000 -- 2012-04-24T10:15:00.000       600.00000


DATA GAPS FOR 2012/04/23
TIME RANGE: 2012-04-23T00:00:00.000 -- 2012-04-24T00:00:00.000
NO GAPS IN APP_ID = 1 (VC1-SOH)
NO GAPS IN APP_ID = 154 (VC1-PMTRAS)
GAPS IN APP_ID = 102 (VC3-MONITOR RATES) WITH PACKET RATE LT 30
N_GAPS           2
GAP START TIME              GAP END TIME                   GAP (SEC)
2012-04-23T21:20:00.000 -- 2012-04-23T21:30:00.000       600.00000
2012-04-23T23:50:00.000 -- 2012-04-23T23:55:00.000       300.00000

DATA GAPS FOR 2012/04/22
TIME RANGE: 2012-04-22T00:00:00.000 -- 2012-04-23T00:00:00.000
GAPS IN APP_ID = 1 (VC1-SOH) WITH PACKET RATE LT 30
N_GAPS           2
GAP START TIME              GAP END TIME                   GAP (SEC)
2012-04-22T03:50:00.000 -- 2012-04-22T03:55:00.000       300.00000
2012-04-22T10:30:00.000 -- 2012-04-22T10:35:00.000       300.00000
NO GAPS IN APP_ID = 154 (VC1-PMTRAS)
NO GAPS IN APP_ID = 102 (VC3-MONITOR RATES) 


DATA GAPS FOR 2012/04/1 9
TIME RANGE: 2012-04-19T00:00:00.000 -- 2012-04-20T00:00:00.000 
GAPS IN APP_ID = 1 (VC1-SOH) WITH PACKET RATE LT 30
N_GAPS           1
GAP START TIME              GAP END TIME                   GAP (SEC)
2012-04-19T10:45:00.000 -- 2012-04-19T11:00:00.000       900.00000
GAPS IN APP_ID = 154 (VC1-PMTRAS) WITH PACKET RATE LT 4
N_GAPS           1
GAP START TIME              GAP END TIME                   GAP (SEC)
2012-04-19T10:45:00.000 -- 2012-04-19T11:00:00.000       900.00000
NO GAPS IN APP_ID = 102 (VC3-MONITOR RATES)


Detector issues

There have been multiple arcing/spike events in the past week. It has been determined that this is as a result of the aforementioned data gaps. This should be monitored to ensure its not a detector issue.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox