Tohban: Difference between revisions
Jump to navigation
Jump to search
imported>Lglesener (→Weekly) |
imported>Lglesener No edit summary |
||
| Line 7: | Line 7: | ||
===Daily=== | ===Daily=== | ||
* Monitor solar activity | * Monitor solar activity. The [http://solarmonitor.org Solar Monitor] is a useful tool for this, as are the [http://solar.physics.montana.edu/max_millennium/ Max Millenium] daily solar activity updates. Changes in solar activity levels may prompt actions such as changes in decimation states, and the current activity level should be taken into account whenever changes are made to the spacecraft program (i.e. spinups, detector changes, etc.) The [http://hesperia.gsfc.nasa.gov/~schriste/tohbanlive.php Tohban Live] page is also a good starter page that shows GOES activity and spacecraft status info. | ||
* | * Monitor the SSR fill level. If the memory is not emptying after the daily pass set, steps may need to be taken to reduce the fill level, including changing the decimation state, changing the collection of nighttime data, or changing detector parameters if one detector is causing the high fill. In rare cases of extremely high activity, data could be deleted by moving the SSR pointers. Please try to avoid deleting day-before and day-after intervals used for gamma-ray background corrections if this becomes necessary. | ||
* Monitor the | * Monitor the [http://hessi.ssl.berkeley.edu/ground_systems/hessi_spacecraft_status.html Spacecraft Status page] several times per day. This page updates once per minute during BGS and Wallops passes. Parameters that are out of range show up as red or yellow warnings. There are occasional glitches that cause values to be flagged as errors when they are not -- use judgment as to whether further action should be taken. (For example, if a parameter is in error consistently throughout a pass, or over more than one pass, then there is an error that needs to be fixed.) Look through past SOH plots to see if the parameter is unusual; send an email to Ops and the Tohban list if action needs to be taken or if you are not sure. Some past issues can be found on the "[[Log of tohban anomalies]]" page. | ||
===Weekly=== | ===Weekly=== | ||
| Line 28: | Line 20: | ||
* Write, file, and e-mail the weekly report (see previous [[:Category:Tohban Report|Tohban Reports]]). The e-mail should be addressed to tohban@ssl.berkeley.edu | * Write, file, and e-mail the weekly report (see previous [[:Category:Tohban Report|Tohban Reports]]). The e-mail should be addressed to tohban@ssl.berkeley.edu | ||
* Add any notes on individual detectors to the [[Tohban detector updates]] page. | * Add any notes on individual detectors to the [[Tohban detector updates]] page | ||
* Add issue reports to the [[Log of tohban anomalies]] page. | |||
== Communication Protocol == | == Communication Protocol == | ||
Revision as of 22:27, 13 February 2013
Tohban - (org.) japanese (def.) operator; duty officer
Duties
The job of the tohban is to help the spacecraft operators at the the Mission Operation Center (MOC), located in the north end of the second floor of the SSL Addition Building, to optimize the science quality of the observations, and maintain the working order of RHESSI's scientific instruments. Tasks include the following.
Daily
- Monitor solar activity. The Solar Monitor is a useful tool for this, as are the Max Millenium daily solar activity updates. Changes in solar activity levels may prompt actions such as changes in decimation states, and the current activity level should be taken into account whenever changes are made to the spacecraft program (i.e. spinups, detector changes, etc.) The Tohban Live page is also a good starter page that shows GOES activity and spacecraft status info.
- Monitor the SSR fill level. If the memory is not emptying after the daily pass set, steps may need to be taken to reduce the fill level, including changing the decimation state, changing the collection of nighttime data, or changing detector parameters if one detector is causing the high fill. In rare cases of extremely high activity, data could be deleted by moving the SSR pointers. Please try to avoid deleting day-before and day-after intervals used for gamma-ray background corrections if this becomes necessary.
- Monitor the Spacecraft Status page several times per day. This page updates once per minute during BGS and Wallops passes. Parameters that are out of range show up as red or yellow warnings. There are occasional glitches that cause values to be flagged as errors when they are not -- use judgment as to whether further action should be taken. (For example, if a parameter is in error consistently throughout a pass, or over more than one pass, then there is an error that needs to be fixed.) Look through past SOH plots to see if the parameter is unusual; send an email to Ops and the Tohban list if action needs to be taken or if you are not sure. Some past issues can be found on the "Log of tohban anomalies" page.
Weekly
- Survey the mission-long parameter plots to check for interesting trends.
- Run the flare-counting software hsi_tohban_flare_counter as a nucleus of information for the weekly report.
- Write, file, and e-mail the weekly report (see previous Tohban Reports). The e-mail should be addressed to tohban@ssl.berkeley.edu
- Add any notes on individual detectors to the Tohban detector updates page
- Add issue reports to the Log of tohban anomalies page.
Communication Protocol
- The Tohban is responsible for communicating any issues with the rest of the RHESSI team and to see the issue through until it is resolved.
- The Tohban should always email the entire tohban list with any issues, but if a knowledgeable person does not respond, the tohban should seek further help. The knowledgeable people include David Smith (detectors), Jim McTiernan (data), and Martin Fivian (SAS).
- The discussion of the issue should remain on the tohban list for the sake of visibility.
Tohban Tool Feature Request
- add a link to past values on the RHESSI status page to give context to values