Tohban Report 2013-02-13
From RHESSI Wiki
|Start Date:||6 Feb 2013|
|End Date:||13 Feb 2013|
|Next Tohban:||Mitsuo Oka|
|List all reports|
Low, low, low, and nothing exciting expected to happen soon.
How many GOES flares occurred?
Flares above B, C, M, X class were 12 5 0 0
And how many of these are listed in the RHESSI flare list?
Flares above B, C, M, X class were 6 5 0 0
And how many had EXCELLENT coverage?
Flares above B, C, M, X class were 5 2 0 0
There were RHESSI flares/GOES flares 84 / 17 over the time range 06-Feb-13 13-Feb-13
No memory issues. The SSR is emptying at the end of the daily pass set, with a maximum of about 21%.
The ADP hung at 16:33 UT on Sunday (Feb. 10), requiring a reset of the ADP on Monday the 11th. We lost about 25 hours of SAS data.
Cold plate temperatures were similar to last week (106.7K and 108.1K). We expect these temperatures to start coming up with the day length decrease soon.
No gaps in monitor rates.
A week ago we increased the rear fast threshold (16 steps) on detector 4 to cut down excessive rates that were degrading livetime for that detector segment by about 10%. The threshold change was immediately effective in reducing the excessive counts and the livetime is no longer compromised.
Detector 2 remains unsegmented, with no hint of segmenting soon. The current plan is to remain at this voltage for awhile to get a sense of how spectral parameter changes are related to radiation damage (as opposed to HV changes).
In the meantime we will lower the front slow threshold on detector 2 by 8 counts to see if the low-energy counts that troubled us before (at a lower HV) are still present or not. This change will happen this afternoon.
A tohban discussion took place during the ops meeting and continued afterward, centering around how to deal with spacecraft status issues. The ADP issue this week was remedied fairly quickly and didn't result in the loss of significant data. But an issue during an active solar time could have been more serious, so we discussed how to quickly notify, assess, and remedy problems that come up. Ideas brought up included: (1) to have an automatic texting/paging system to notify tohbans if there is an error on the spacecraft status page after a pass; (2) to add an ADP error to the list of issues that will trigger an Ops page; (3) to go ahead with a reset even if Martin can't be contacted, if an ADP freeze is suspected; (4) add a list of one-line problem reports to the tohban wiki so that we have a referenceable list of past problems; and (5) add a wiki page that has more information about the ADP and SAS and describes the parameters pertaining to this topic.
After a lot of discussion, we decided *not* to implement a tohban page but Ops will add the ADP error to the list of issues that auto-pages them. We also decided to add the problem list (similar to the detector issues pages) and the ADP/SAS info page. The problem list is online now ( link: Log for tohban anomalies ); it will serve as a concise list of spacecraft or instrument problems that come up, with a few sentences describing what the problem was, how it was identified, and what was done to fix it. This starts with the ADP error this week (sorry, no legacy events!) and the tohban should update after each issue is resolved. For the ADP/SAS info page, Martin is tasked to write a few paragraphs of info useful to tohbans. This info page should not be considered an exhaustive reference but may aid the tohbans in figuring out if there's a problem and knowing what questions to ask.
I've also taken this opportunity to update the Tohban page with what I believe are more up-to-date descriptions of what is expected from a tohban. All tohbans (or interested parties) are encouraged to read through this page and make their own further edits.
|HLAT Decimation||Rear decimation weight 6, no front decimation|
|Night time data (fronts)||+/- 4 minutes|
|Night time data (rears)||Taking data at nights|
|Require extra passes?||No|
|Requirement for moving pointer?||No|