Tohban

From RHESSI Wiki

Revision as of 18:42, 23 June 2012 (view source) Lglesener (Talk | contribs) (→Weekly) ← Older edit		Latest revision as of 18:57, 28 September 2015 (view source) Ayshih (Talk | contribs) m
(6 intermediate revisions not shown)
Line 1:		Line 1:
	Tohban - (org.) japanese (def.) operator; duty officer		Tohban - (org.) japanese (def.) operator; duty officer
		+
		+	Link to extensive list of tohban material: [[:Category:Tohban|Category: Tohban]]
	[[File:Tohban_callig.jpg|200px|thumb|right|Tohban Calligraphy]]		[[File:Tohban_callig.jpg|200px|thumb|right|Tohban Calligraphy]]
Line 7:		Line 9:
	===Daily===		===Daily===
-	* Monitor solar activity as described here. Then look at the respective data gap files, and check for gaps coincident with the flare times. If such gaps exist, contact an operator and ask to replay the data.	+	* 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.
-	* Record [[attenuator]] state changes and [[decimation]] state changes, which can be seen in the [http://hesperia.gsfc.nasa.gov/hessidata/metadata/ metadata plots]. For obtaining more exact times via IDL, refer to the [[Tohban Useful Routines]] page. This is also very useful for imaging spectroscopy. Ideally, each major flare would be mentioned along with any changes in attenuator state or decimation state during that time though this is not required.	+	* 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 SSR fill level. Consult with the [[RHESSI operator]] about memory management (possible use of decimation if SSR fill level is too high (>50%).) At times of high activity, it is sometimes necessary to delete data 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 [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 for tohban anomalies]]" page.
-	* Confirm that the decimation program is appropriate to solar and magnetospheric conditions. The decimation pages give full information about this.	+	* Check detector monitor rates in the [http://sprg.ssl.berkeley.edu/~tohban/browser/ Browser] for individual detector problems, such as a detector becoming very noisy or showing spikes in the rates.  If you see something unusual, check the [[Detector Updates]] page to see if this is a known problem.  Email the tohban list if a detector starts acting up.
-	* Communicate if necessary with ground-based observers (e.g. via [http://solar.physics.montana.edu/max_millennium Max Millennium]) with regard to observing campaign activities.	+	===Weekly===
		+	* Run the flare-counting software [[hsi_tohban_flare_counter]] as a nucleus of information for the weekly report.
-	* Keep David Smith informed of shutter program changes.	+	* Check data gap records to see if there are any outstanding gaps during the week that have not been filled in.  Bring it up at the Ops meeting if so.
-	* Update the [[Data Gaps]] log if a pointer adjustment was made.	+	* NEW!!!  Look at long-term temperature trends to identify if anything has recently changed with the cryocooler operation.  Long-term SOH trends, and also the plots generated by Kim's IDL routines, are best for this.  Look at Cold Plate (especially #1) temperatures to see if fast changes are occurring (for example, on the order of >1 degree rise per month).  Look at Cold Tip temperatures to ensure that we are staying below the "safe" cryocooler power-temperature curve.
-	===Weekly===	+	* At the weekly Ops meeting, report on current solar activity, detector health, data gaps, and any other tohban issues.
-	* Survey the [http://hessi.ssl.berkeley.edu/hessidata/metadata/hsi_1day_sohdata/ 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 a weekly report and publish it on this Wiki (see previous [[:Category:Tohban Report|Tohban Reports]]).
-		+
-	* 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 for tohban anomalies]] page.
	== Communication Protocol ==		== Communication Protocol ==
Line 36:		Line 38:
	* The discussion of the issue should remain on the tohban list for the sake of visibility.		* The discussion of the issue should remain on the tohban list for the sake of visibility.
-	== Tohban Tool Feature Request ==	+	== Tohban Context Tool ==
		+
		+	To get an idea of what RHESSI state-of-health (SOH) parameter values to expect at any given time, it is best to consult the [http://hesperia.gsfc.nasa.gov/hessidata/metadata/hsi_1day_sohdata/  RHESSI SOH data 1-day Averages page].  This site has daily average values for all SOH parameters, both as ASCII text lists and as graphs of the values vs. time since launch.
		+
		+	You can also access the [http://sprg.ssl.berkeley.edu/hessiops/state-of-health/welcome.html daily SOH plots] that show more detailed plots of various SOH parameters for each day since launch.
-	* add a link to past values on the RHESSI status page to give context to values
	[[Category: Operations]]		[[Category: Operations]]
	[[Category: Tohban]]		[[Category: Tohban]]

---

Latest revision as of 18:57, 28 September 2015

Tohban - (org.) japanese (def.) operator; duty officer

Link to extensive list of tohban material: Category: Tohban

Contents 1 Duties 1.1 Daily 1.2 Weekly 2 Communication Protocol 3 Tohban Context Tool

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 for tohban anomalies" page.

• Check detector monitor rates in the Browser for individual detector problems, such as a detector becoming very noisy or showing spikes in the rates. If you see something unusual, check the Detector Updates page to see if this is a known problem. Email the tohban list if a detector starts acting up.

Weekly

• Run the flare-counting software hsi_tohban_flare_counter as a nucleus of information for the weekly report.

• Check data gap records to see if there are any outstanding gaps during the week that have not been filled in. Bring it up at the Ops meeting if so.

• NEW!!! Look at long-term temperature trends to identify if anything has recently changed with the cryocooler operation. Long-term SOH trends, and also the plots generated by Kim's IDL routines, are best for this. Look at Cold Plate (especially #1) temperatures to see if fast changes are occurring (for example, on the order of >1 degree rise per month). Look at Cold Tip temperatures to ensure that we are staying below the "safe" cryocooler power-temperature curve.

• At the weekly Ops meeting, report on current solar activity, detector health, data gaps, and any other tohban issues.

• Write a weekly report and publish it on this Wiki (see previous Tohban Reports).

• Add any notes on individual detectors to the Tohban detector updates page.

• Add issue reports to the Log for 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 Context Tool

To get an idea of what RHESSI state-of-health (SOH) parameter values to expect at any given time, it is best to consult the RHESSI SOH data 1-day Averages page. This site has daily average values for all SOH parameters, both as ASCII text lists and as graphs of the values vs. time since launch.

You can also access the daily SOH plots that show more detailed plots of various SOH parameters for each day since launch.