Tohban Report 2015-08-26

From RHESSI Wiki

(Difference between revisions)
Jump to: navigation, search
(Created page with "{{Infobox Tohban Report| |start_date = 19 Aug 2015 |end_date = 26 Aug 2015 |tohban_name = Lindsay Glesener |tohban_email = glesener@ssl.berkeley.edu |next_tohban = TBD }} == S...")
Line 32: Line 32:
Detectors 3 and 4: The front fast thresholds were raised in order to lower fast rates and free up livetime.  Both changes were successful in achieving this.  For D3, livetime rose from ~50% to >90%.  For D4, livetime rose from ~0% to ~50%.  The D4 threshold should be raised again to further raise the livetime.  Over the next few days this action was not repeated because the D9 business ate up my own livetime.
Detectors 3 and 4: The front fast thresholds were raised in order to lower fast rates and free up livetime.  Both changes were successful in achieving this.  For D3, livetime rose from ~50% to >90%.  For D4, livetime rose from ~0% to ~50%.  The D4 threshold should be raised again to further raise the livetime.  Over the next few days this action was not repeated because the D9 business ate up my own livetime.
 +
Detector 9:  More on the D9 rear ULD escapade below; here is only a note on the front threshold change, which occurred on Aug. 20.  This was an attempt to free up livetime, but it was unsuccessful; there was no measured effect.  D9 front livetime is very low, about 15%.
 +
 +
Detector 6:  D6 is not in good shape, with high slow and fast rates, high resets, and somewhat reduced livetime in the front.  Livetime is also somewhat low in the rear segment, and fast rates are high, but the rear resets are not terrible.  This detector needs attention (first try fast threshold changes in front and rear) but there wasn't time for it this week.
 +
 +
15-232-22:16:08 start idib_chg_thrshld (3, FRONT, FAST, 0x50)
 +
15-232-22:16:30 /IDPUDUMPTABL TABLE=DIBTBL3
 +
15-232-22:16:30 /IDPUTABLE3 OFFSET=FRONTFASTDAC
 +
15-232-22:16:41 /IDPLOAD VALUE=0x50
 +
 +
15-232-22:17:53 start idib_chg_thrshld (4, FRONT, FAST, 0xA0)
 +
15-232-22:18:12 /IDPUDUMPTABL TABLE=DIBTBL4
 +
15-232-22:18:12 /IDPUTABLE4 OFFSET=FRONTFASTDAC
 +
15-232-22:18:25 /IDPLOAD VALUE=0xA0
 +
 +
15-232-22:19:13 start idib_chg_thrshld (4, FRONT, FAST, 0xB0)
 +
15-232-22:19:23 /IDPUDUMPTABL TABLE=DIBTBL4
 +
15-232-22:19:23 /IDPUTABLE4 OFFSET=FRONTFASTDAC
 +
15-232-22:19:32 /IDPLOAD VALUE=0xB0
 +
 +
15-232-22:21:09 start idib_chg_thrshld (9, FRONT, FAST, 0x90)
 +
15-232-22:21:38 /IDPUDUMPTABL TABLE=DIBTBL9
 +
15-232-22:21:38 /IDPUTABLE9 OFFSET=FRONTFASTDAC
 +
15-232-22:21:46 /IDPLOAD VALUE=0x90
 +
 +
More on D9 ULD anomaly:

Revision as of 21:46, 22 August 2015


Tohban Reports
Start Date: 19 Aug 2015
End Date: 26 Aug 2015
Tohban: Lindsay Glesener
Tohban email: glesener@ssl.berkeley.edu
Next Tohban: TBD
List all reports



Contents

Solar Activity

We had an active week with many M flares.


Memory Management

On Aug 20/21, the SSR filled up due to skyrocketing ULD events in D9 rear. See description below.


Spacecraft Status

Data Gaps

Some long gaps (~half a day) due to need to skip pointer after SSR filled up.

Detector issues

Some threshold were changed on Aug. 20 around ~22:20:

Detectors 3 and 4: The front fast thresholds were raised in order to lower fast rates and free up livetime. Both changes were successful in achieving this. For D3, livetime rose from ~50% to >90%. For D4, livetime rose from ~0% to ~50%. The D4 threshold should be raised again to further raise the livetime. Over the next few days this action was not repeated because the D9 business ate up my own livetime.

Detector 9: More on the D9 rear ULD escapade below; here is only a note on the front threshold change, which occurred on Aug. 20. This was an attempt to free up livetime, but it was unsuccessful; there was no measured effect. D9 front livetime is very low, about 15%.

Detector 6: D6 is not in good shape, with high slow and fast rates, high resets, and somewhat reduced livetime in the front. Livetime is also somewhat low in the rear segment, and fast rates are high, but the rear resets are not terrible. This detector needs attention (first try fast threshold changes in front and rear) but there wasn't time for it this week.

15-232-22:16:08 start idib_chg_thrshld (3, FRONT, FAST, 0x50)
15-232-22:16:30 /IDPUDUMPTABL TABLE=DIBTBL3
15-232-22:16:30 /IDPUTABLE3 OFFSET=FRONTFASTDAC
15-232-22:16:41 /IDPLOAD VALUE=0x50
15-232-22:17:53 start idib_chg_thrshld (4, FRONT, FAST, 0xA0)
15-232-22:18:12 /IDPUDUMPTABL TABLE=DIBTBL4
15-232-22:18:12 /IDPUTABLE4 OFFSET=FRONTFASTDAC
15-232-22:18:25 /IDPLOAD VALUE=0xA0
15-232-22:19:13 start idib_chg_thrshld (4, FRONT, FAST, 0xB0)
15-232-22:19:23 /IDPUDUMPTABL TABLE=DIBTBL4
15-232-22:19:23 /IDPUTABLE4 OFFSET=FRONTFASTDAC
15-232-22:19:32 /IDPLOAD VALUE=0xB0
15-232-22:21:09 start idib_chg_thrshld (9, FRONT, FAST, 0x90)
15-232-22:21:38 /IDPUDUMPTABL TABLE=DIBTBL9 
15-232-22:21:38 /IDPUTABLE9 OFFSET=FRONTFASTDAC
15-232-22:21:46 /IDPLOAD VALUE=0x90

More on D9 ULD anomaly:




Other notes

Spacecraft Management

Decimation Normal/Vigorous
Night time data (fronts) +- 4 minutes
Night time data (rears) +- 4 minutes
Require extra passes? No
Requirement for moving pointer? YES
Attenuator operation Normal
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox