Hello, welcome to the SXT toban. ******************************** Rev. F: May 11. 1992 ************************************************************************************** This manual outlines the current toban duties and describes how to carry them out. ****The master copy lives in /home/flare1/sxt/toban/sxt_toban.manual, all changes/ updates should be made there. Then it should be copied to a read-only version in /ys/sxt/status/ where any team member can access it or copy it.***** Tobans should feel free to make appropriate changes or corrections, and to add notes on operations not yet written up. This applies especially to the pass monitoring job, and any experiences with error recovery. We learn from each other how to operate SXT efficiently and safely. Original draft by A. McAllister Feb. 1992. Updated by S. Tsuneta March 28, 1992 Commented by H. Hudson Updated by S. Tsuneta April 03, 1992 Commented by T. Shimizu, H. Hara Updated by S. Tsuneta April 07, 1992 Updated by S. Tsuneta April 12, 1992 Yobi command B changed Commented by G. Kawai May 11, 1992 GBO_Mail, how to exit SXTQLGG Note: Toban=duty operator, duty scientist Super Toban=chief duty operator, chief scientist ************************************************************************************** EMERGENCY CALL ______________ List of Super Tobans home office |---------------------------------------------------| | Saku Tsuneta 0423-35-0386 0422-34-3640 | | Hiro Hara 0424-80-5208 0422-34-3705 | | Toshi Shimizu 0424-80-4173 0422-34-3635 | |---------------------------------------------------| For the Super Toban rotation, see flare1:/home/flare1/sxt/doc/super.toban. TABLE OF CONTENTS _________________ EMERGENCY CALL 0. DAILY OPERATION SEQUENCE: A ROADMAP 1. INTRODUCTION 2. COMPUTERS 2.1. Accounts 2.2. Notes on the ISAS mainframe operating system 2.3. PF keys 3. OTHER HELP 3.1. Personnel 3.2. Written 4. PRE-PASS PREPARATION 5. SETUP COMPUTERS 6. SXT OPERATION 6.1. Error check 6.2. SXT operation sheet 6.3. Check of the observing region address 7. UPLOADING NEW CONTROL TABLES 8. ERROR RECOVERY 9. SENDING SXT POINTING DATA TO GROUND-BASED OBSERVATORIES 10. POST-PASS DUTIES 10.1. At the end of pass 10.2. Write LOG NOTE 10.3. Creation of SIRIUS database 10.4. Creation of Reformatted data base 10.5. Run SXT health check programs 10.6. File GOES and NOAA data 11. SXT DATA CHECK 11.1. After each pass and/or the 5th pass 11.2 After DSN data has arrived 12. HIKITSUGI 0. DAILY OPERATION SEQUENCE: A ROADMAP ______________________________________ ========================= Pre-operation preparation ========================= 1. Contact Super Toban (or Acton san when available) about SXT table update and any other special commanding. 2. Participate, as much as possible, in SXT table update activity with Super Toban (or Acton san or whoever is authorized to change SXT table). 3. Go upstairs to the printer room and collect copies of a) the updated table, b) change record and c) commands in the hexadecimal notation. 4. Check carefully on copies of the three items mentioned above, and if some inconsistency is found, report to Super Toban or the person who updated the table. Otherwise keep them in the binder. 5. Inform SSOC toban about the command and table update plan well before the operation time. =========== During pass =========== 1. Check error flags. 2. Jump to the contingency plan in case of error. 3. Check observing region location. 4. Check FFI and PFI images for day passes. 5. Fill the SXT operation sheet. =============== After each pass =============== 1. Write LOG NOTE anything of note and sign your name. 2. Create reformatted database whenever necessary. 3. Check FFI and PFI images. 4. Report observing region address and SXT observing status to ground-based observatories (gbo_mail). 5. Confirm that the observing sequence with new table is OK. 6. Create reformatted database for the pass. ================== After the 5th pass ================== 1. Find flare-mode flares from SAPLOT after DSN data has arrived. 2. Check the corresponding flare images to see if AEC and ARS is OK. 3. Write FLARE LOG. 4. Run filter check and temperture monitor program. 5. Orally report to Super Toban. === END === 1. INTRODUCTION _______________ There are three main groups of tasks. i) SXT HEALTH CHECK AND OBSERVING REGION CHECK First and foremost the SXT tobans monitor the SXT during the passes over KSC. This is performed in the control room on the third floor of B-toh. In addition to the routine monitoring of the passes, the SXT tobans must help check the uploading of new tables and other commands issued to the SXT in orbit. In the event (hopefully rare) of some sort of error with SXT, the tobans help to coordinate the issuing of contingency (yobi) commands to protect the instrument and to recover from the error. SXT toban also has to check the location of the observing region(OR), which is constantly updated by the SXT flight software. In case the location is not proper, SXT toban should change the OR address by updating the table with SXT Super Toban. The improper OR location damages the scientific operation as well as SXT CCD. ii) DATA BASE CREATION FOR KSC DATA There is also a series of tasks that have been assigned to the SXT tobans after the pass. SXT tobans check whether the SIRIUS data base has been created by SIRIUS subcontractor. If the SIRIUS is not available (probably because of night arrival of data), temporal version of SIRIUS needs to be created by SXT tobans. Then, SXT toban creates the reformatted data base to check the FFI and PFI images on the daily basis. iii) POST-PASS DATA CHECK SXT tobans should especially confirm that images of all flare-flagged flares are properly taken, i.e. that SXT performance during flare mode was correct. The toban should also monitor the performance of the flare trigger itself - did every flare that should have caused a trigger in fact do so? It also needs to be checked that observing region is located in the desired place. If the ARS tracking mode (ARS2) is running, SXT toban should check the long-term trajectory of the observing region location over the sun. 2 COMPUTERS ____________ 2.1. Accounts There are a few mainframe computers at ISAS, any of which can be accessed from any console. We use only #1 mainframe computer (SSOC#1). Account can be opened by entering LOGON TSS account name. However, for consoles connected to other mainframe mach1ines, it is necessary to type LOGON TSS1 acount name. Try this when you can not log in. To perform these tasks the toban will use both the ISAS main frame #1 accounts QLSA0*, where * is 5 - 6 (for SXT use) or 2 - 3 (for general use). In all cases the password is ISAS. The SXT tobans also make use of the SUN workstation FLARE1 as well as MIPS workstation FLARE11 in the Yohkoh operations room on the 2nd floor of B-toh. Login as 'sxt' with password 'fuchinobe'. Following mainframe accounts are dedicated to the specific acitivities. It is prohibited to use those accounts for other Yohkoh and SXT purposes. SR0001 SXT table update CM0002 SIRIUS database creation and other SIRIUS related activity QLSA01 Access from KSC 2.2. Notes on the ISAS mainframe operating system You can get the Facom to use English with: PFD TERMLANG(E) As you can only log on once to any given account, when using multiple screens it is necessary to logon to different account #s each time. It is also important to log off when finished, especially with key accounts such as SR0001. Don't forget that the terminal system extends all around ISAS and that there is considerable SXT activity both in B-toh and in D-toh. DO NOT LOG OFF ALL THE ACCOUNT AFTER 5 PM. THE SSOC #1 COMPUTER WILL STOP AUTOMATICALLY, IF THERE IS NOT ANY USER. 2.3. PF keys This is mainly about the use of the PF keys. PF3 exits the current screen and returns to previous one. PF8 moves down the current screen. PF7 moves up the current screen. 3. OTHER HELP _____________ 3.1. Personnel There is a 'super-SXT toban',specified on the daily basis, who should help you get started and be on call in case something unexpected comes up. This Super Toban is also responsible for the control table changes and for assisting in relaying these to KSC. See the file /home/flare1/sxt/doc/super.toban to know who the Super Toban is. SXT Super Toban should stay at ISAS for emergency. SXT toban should report SXT status at least every 24 hours in case there is nothing special. The SSOC toban does the overall Yohkoh command preparation. All table loads and other scheduled SXT commands go through the SSOC tobans, and the SXT toban should help see to it that the SSOC toban is properly informed of SXT commanding activity, such as table uploads. This should normally be done the day before the commanding activity. 3.2. Written The SSOC toban duty manual is also very useful for the beginner of SXT operation, providing some background on the spacecraft operation in general and the mainframe computers. It is kept in the Yohkoh operation room, B-toh. There exist English-language manuals on using the ISAS mainframe computers. Ask around in D-toh for a copy. 4. PRE-PASS PREPARATION _______________________ SXT control (observation) table will be updated, and tranferred to KSC with SXT table managing software (SXTSPT) by SXT Super Toban. However, it is highly recommended that SXT tobans be involved in this scientific operation for SXT as well and to be familiar with SXT table update procedure. In particular, SXT toban should do the following activities: 1. understand what modification(s) are done on the table, as well as its observational consequence to check the data, 2. confirm that table update is properly scheduled in the SSOC spacecraft operation plan, 3. Confirm with KSC toban that the new table arrives at KSC commanding computer MS. If there is other special commands instructed by SXT Super Toban, those also need to be included in the SSOC spacecraft operation plan. SXT TOBANS ARE REQUIRED TO MAKE VERY CLOSE COMMUNICATION WITH SSOC SPACECRAFT TOBANS. 5. SETUP COMPUTERS __________________ There are usually five passes over KSC each day (night). The daily schedule is posted on the marker board in the Yohkoh operations room. The tobans should report to the 3rd floor control room about ten minutes before the start of each pass. The SSOC (Yohkoh) toban has the responsibility to update this information; the timing information can also be checked using the IDL program CONTACTS on FLARE1. In preparation for each pass: 1. Turn on the two NEC consoles at the far (south) end of the line, across from the Sun workstation GREEN. These display the pass orbit and associated data, and the planned command sequence and actual commands as sent by KSC. There is also a headset under the last console that is linked to the Yohkoh tobans in KSC. 2. Bring up the mainframe screens for monitoring the pass: There are three consoles (the ones nearest the far end of the line, next to GREEN workstation) that are used to monitor the passes. The tobans also may use GREEN for communications and to display full-frame images in nearly real time. i) PREPARE SXT QUICK LOOK MONITOR This monitor displays all the SXT status in 5 different pages, which can be swapped during operation (see below). The top four lines display information on the spacecraft level (command answer back, etc.) as well as SXT basic status. The right-hand side displays vital SXT status information such as power, SXT command answer and error conditions. Turn on a monitor. This brings up the ISAS logo. prompt. you enter. logon please> LOGON TSS QLSA06 (see note above) current password for ..> ISAS ready> PROF PRE(SR0001) ready> EX S ready> SXTQLCC (for "sxt quick-look cc") input telemetry mode (..)> tmst(yymmddhhmmss)> (start time, optional for current) tmen(yymmddhhmmss)> (end time, optional for current) input page no(1-5)> 2 NOTE: This program (SXTQLCC) normally will not synchronize correctly with the incoming data until about a minute into the pass (normally the end of the "nyuukan chekku" announced from KSC. There are four screens that you need here, which are brought up with the PF keys. PF13; FFI and PFI header information. PF14; Current instrument status (main monitoring screen). PF15: Curret observing region address. PF16; errors in detail. NOTE: RECALLING INFORMATION FROM PREVIOUS PASSES. For many of the mainframe information screens, by entering a non-default response at the 'telemetry' prompt you can access old data and replay the passes. Try `RLT'. Then give the start and end times and type the screen you want. Once it has started you can use the PF keys to change screens just as for real time monitoring. One caution. It seems best to pick a start time slightly into the pass. If you give it a time between passes (where there is no data) then it will hang up. RLP and PBP access similar information, but you need to input the exact pass-number in YYMMDDXXXX format (XXXX=Pass number). With the screens accessed after 'ex s', you can get info for the last week or so this way. For earlier data replace with 'ex ss'. 'ex s' makes the quick-look software access the temporal telemetry file which contain most recent real received from KSC. (This file does not contain DSN data.) On the other hand, 'ex ss' makes it access the SIRIUS data base permanently containing all Yohkoh data. Thus, to access playback or DSN data, you need to select 'ex ss'. ii) PREPARE SPACECRAFT QUICK DISPLAY This shows all the spacecraft status in many pages. The basic instrument information including SXT status information will appear by pushing PF5. Turn on another monitor. This brings up the ISAS logo. prompt. you enter. logon please> LOGON TSS QLSA05 (must be a DIFFERENT #) current password for ..> ISAS ready> PROF PRE(QL) ready> SAQL (for "solar-a quick look") key in number please> 1 There following screens are available here. PF5; initial screen. Check for errors, lower right corner. PF7; temperature readings. PF10; BDR info. Can check this for flares by seeing if there are more than four 3's in the BDR sector listings before the BDR dump is finished. NOTE: This program synchronizes promptly and may be started even before the data actually begin to arrive. This is normally the quickest place to check for the occurrence of an SXT error. iii) PREPARE SXT TABLE MANAGER The SXT control table update system (table manager) will provide us with reasonably user-friendly environment in which to update SXT control tables. The updates can start with current, archive, or template tables. The system also carries out an error check on the parameters which operator has entered, generates the command sequence, sends it to KSC spacecraft operation computer (the so-called MS computer). It finally is also used to confirm the success of a table upload during the actual real-time telemetry contact. See separate manual "SXT table loading" written by Nariaki Nitta for details of SXT control table manager. When you are going to monitor a table upload, bring up a third monitor. prompt. you enter. logon please> LOGON TSS SR0001 current password for ..> AHONOSXT ready> PROF PRE(QL) ready> EX SXTSPT (for "solar-a sxt support") PF24 job **** submitted> enter number> [RCV (in red) should appear at top of screen. Ignore 'INPUT ERROR' at bottom.] iv) PREPARE SXT IMAGE MONITOR This displays either SXT FFI or PFI images with a primitive 8-level color table. However, this system is VERY useful and reliable, because you can see and check images whenever telemetry is available. Please check FFI and PFI images during every KSC daytime contact. Note that the images presented are reversed both in NS and EW directions. Real-time image check can be done only when the spacecraft is in day portion of the orbit. For looking at real time FFI or PFI, bring up a monitor. prompt. you enter. logon please> LOGON TSS QLSA0* (this must be DIFFERENT) current password for ..> ISAS ready> PROF PRE(SR0001) ready> EX S ready> SXTQLGG telemetry(...)> pass #> sequence #> decompress> a long line at the bottom> XY where X and Y should be chosen as below, (see also prompt line) X: N new C continued Y: F full frame P partial frame M arrange partials in matrix (NM is the standard real-time choice) (I recommend you to caps-lock the keyboard, since lower case is not accepted) Press a couple of more times till the screen blanks. It is now waiting for input from KSC. After an image was displayed on the screen, press a couple of more times again and the next image will appear. To exit SXTQLGG, enter 'X' instead of 'NM'. v) PREPARE HIGH-QUALITY SXT IMAGE MONITOR This software provides a real-time SXT high-quality FFI image monitor, which is also very useful for daytime operation. This software was developed by Shuto-san of ISAS to help SXT team. The images presented here are the best way for the toban to assess the current state of solar activity as a basis for advising on table changes. This program resides on workstation GREEN. It may need logging in or removal of the screenlock. The username is slasxt1, password isassxt. prompt. you enter. green% idl st idl> .run ffiql or idl> .run ffidl for delayed look 6. SXT OPERATION ________________ With these preparations, you are now ready to rock and roll! ====================================================================== Always bring the error recovery manual with you to the operation room. Flow the chart in mind to prepare for the emergency beforehand. ====================================================================== About 10 min before the start of the contact, there will be a roll call from KSC commander (chief operation personnel from the subcontractor) to confirm the readiness for operation. There needs 5 or 6 people only connected by voice-line: 20 m antenna->transmitter->receiver->demodulator-> command->S-3500(KSC low-bit). telemetry computer->A-400 telemetry trasnfer computer->SXT toban in Tokyo. When the commander asks if SXT at Sagamihara is ready for operation, say yes (hai). If the setup is not complete, respond 'setup in profress', and report 'SXT at Sagamihara is ready' later. Note that at the start of every pass KSC establishes its link and runs some checks (nyuukan chekku). Until this AOS check procedure is finished your screens, especially SXTQLCC, will tend to have spurious data. Wait for some time patiently. If the display is not stable, end the program either by pushing PF3 for more than 1 sec or by ALT+PA1, and start again. There is also an announcement over the speakers when initial spacecraft-level checkout (AOS check) is finished. Now your turn... 6.1. Error check Errors show up on most of the screens, see especially PF5 of the SAQL spacecraft monitor screen (lower right corner indicated as ------ SXT ------): SHT CLS <- SXT shutter status OPN or CLS FAB 3/1 <- SXT filter status B/A ER *** <- SXT error status ***(normal) or ER (red) WRE *** <- SXT software corruption indicator ***(normal) or WRM (red, software corrupted) If ER is not ***, this is an EMERGENCY situation. If WRE is WRM (not ***), then the software is corrupted due to an SEU. For some type of the error, red WRM flag appears only for short period (pulse). Watch this patiently. DOUBLE CHECK THE ERROR STATUS ALSO WITH SXTQLCC: More detailed error information can be obtained from the SXT quick look program SXTQLCC (PF14) under the **ERROR** banner (lower right), TIME, JERR, and UERR fields. For detailed error information check PF16. If red error flag appears in the main section of PF16 screen, it indicates emergency. ========================================================================= Proceed to sction 8: ERROR RECOVERY immediately in case of the erros. ========================================================================= 6.2. SXT operation sheet The main duty on every pass is to check SXT's status and fill out a copy of the "Yohkoh SXT Operations Sheet". This is done by using data on the screens brought up under i) and ii) of section 5 (SXTQLCC and SAQL). THE SXT OPERATIONS SHEET. Starting at the top: Date: today's date (UT time) AOS: pass start time (for planned start see the KSC pass plan monitor, or the board in the Yohkoh ops room. The actual start time is announced by KSC over the speakers: S-lock on!) LOS: pass end time (for the planned time, same as above. For actual time you can estimate by when the data goes funny after the link is lost) Pass: pass number (1-5) Duty: toban's initials Command: Mark if there is special command (normally no command). Notes: Comments on the pass, especially if there are errors. Pre-Contact check: Check if an SXT control table has been sent to KSC, or if commands have been FAXed to be sent up on the pass. AOS SXT check: This section should be filled out as soon as the link is fully established and the data have settled down. SXT operation: circle Normal if everything seems ok, ie. no errors, otherwise write in the condition, error, etc. Power CONTROL: On PF14, line 3, PWR CONT field. Circle AUTO or MANU. Normally AUTO. Error flag: See section 6.1. SXT CONTROL: On PF14 in SXTQLCC, line 3, SXT CONT field. Circle AUTO or MANU. Normally AUTO, but will change during a pass when sending up the table and as well as any SXT command. SXT MODE: On PF14 in SXTQLCC, line 3, MODE field. Circle as appropriate, for day, evening, night, morning. SXT BDR check: On PF14 in SXTQLCC, line 3 BDR field. Circle ENA or DIS. Usually ENA at start, but changes to DIS during contacts. DP MODE: On PF14 in SXTQLCC, top line, right end. On the monitor it will list 32K, 4K, or 1K, circle HI, MED, or LO as appropriate. The DP mode, top line, far right of PF14 in SXTQLCC is listed as FLARE(FL), QUIET(QT), NGT, or ACS. CCD temp : On PF14 (SXTQLCC) lower/center in the CCD T field. TEC: On PF14 (SXTQLCC) lower far right, H field H ON=>TEC ON Heaters. OBJ: On PF14 (SXTQLCC), under *HCE-133-* banner, F-END field. FPG: On PF14 (SXTQLCC), under *HCE-133-* banner, FPG field. TEC: On PF14 (SXTQLCC), under *HCE-133-* banner, TEC field. Serial #s. Filter A #: On PF14 (SXTQLCC), under **ODOMETER** banner, FILTER A field. Filter B #: On PF14 (SXTQLCC), under **ODOMETER** banner, FILTER B field. Shutter #: On PF14 (SXTQLCC), under **ODOMETER** banner, SHUTTER field. Aspect Door #: On PF14 (SXTQLCC), under **ODOMETER** banner, ASPECT DOOR field. FFI #: On PF13 (SXTQLCC), under **FFI** banner, SER# field. PFI #: On PF13 (SXTQLCC), under **PFI** banner, SER# field. SXTS Temp : On PF7 (SAQL), Look at temperatures in fields from MTT to CCDHT. These refer to SXT and should all be in green. (Many are in red before the link is fully established). If they are all green circle OK. Observing Region: Go to PF15 (SXTQLCC), under the **ROI TABLE** banner are a series of rows. Look at the first one, 0 ARS, copy the numbers in the EW/NS, CRT EW, and CRT NS fields. These are also used to make up the GBO mail message. Near the end of the pass, see the predicted end, and the pass trajectory on the KSC monitor, fill in the LOS SXT check section, from the same fields used for the AOS check. Send the observing region data out by e-mail. This should be done ASAP, either from the workstation GREEN in the control room (by telnet to FLARE1), or as soon as it is finished from FLARE1 in the Yokoh operations room. See below for details. You can also check for flares by looking at the PF10 (SAQL) screen, under the **BDR INF** banner. Look at the numbers in the BLK0 1,2,3,4,5,6,... fields. Normally 4 fields read 3 (but not always the same ones) and the others zero. If more of them read 2 or 3 then a flare has occurred (data has been taken in flare mode). 6.3. Check of the observing region address Location of observing region is regluarly updated by SXT onboard control softwares: ARS1 will select the brightest active region all over the Sun, while ARS2 mode tracks the specific active regions initially selected by manual specification of the address. ARS1 or ARS2 is selectable by so specifying the table. Keep always in mind which ARS is running currently. SXT toban has to confirm that the bright region is properly selected. If the dark region or region outside the sun is selected by misoperation or other reasons, AEC(automatic exposure control) will increase the exposure time to the dangerous level. Remember that whole X-ray sun is exposed on the CCD, and bright active regions, if long exposure is taken, will burn out the CCD. In particular, SXT toban must have a close watch on the location, when ARS2 mode is selected. The spacecraft level misoperation may easily lead to unsolicited patrol image acquisition at orbit night, which will cause the false positioning of the observing region. Check at every pass that the observing region address #0 is as expected, when ARS2 is running. This can be done either by checking the observing region address in SXTQLCC or by checking the PFI images. There is a possibility that more than 1 active regions are tracked by ARS2. For instance, if OR#0 and #1 are used in the PFI sequence table, OR#1 address of course has to be monitored. Contact Super-toban on which OR#s are used: OR#0 ARS controlled <=normally used OR#1 ARS controlled <=maybe used OR#2 ARS controlled <=maybe used OR#3 ARS controlled <=maybe used OR#4 Reserved for manual or ART OR#5 Reserved for manual or ART OR#6 Reserved for manual or ART OR#7 Reserved for manual or ART OR#8 Under FLARE-ARS control/fully automatic If the number is changed drastically, ask KSC commnder: SXT CONTROL MANUAL (DP/SXTE-J DC A3H) to stop SXT observation. This will put SXT in the safe configration. Call SXT Super Toban immediately. If this happens, SXT toban and SXT Super Toban prepares new upload table to correct the observing region address by next contact. This operation follows the normal table upload described in section 7. If ARS1 mode is running, and the KSC contact is at night, you need to rely on post-contact image check using play-back data. THUS IT IS IMPORTANT TO MAKE POST-CONTACT IMAGE CHECK AS EARLY AS POSSIBLE AFTER THE CONTACT. 7. UPLOADING NEW CONTROL TABLES ________________________________ New SXT table should be sent to KSC at least 1 hr prior to the contact. Bring up screen iii) (SXTSPT) as well as i) (SXTQLCC) and ii) (SAQL) of section 5. Establish contact with KSC via the headphone set. KSC will ask if SXT is ready. Confirm that you are. Be sure that you have opened the screen as listed in iii) (SXTSPT) of section 5 BEFORE the pass starts. You can see the SXT upload sequence on the KSC monitor. When the SXT operators move into the SXT segment, you will see the DP mode change to QUIET or stay at QUIET. DC commands appear on the PF14 screen monitor (SXTQLCC). The update sequence follows like this: (MANU QT H) [if not QUIET mode] BC ENA SXT TABLE WR [writing the SXT control tables to the spacecraft] SXT TABLE RE [dumping the just-written tables to the ground for verification and archiving.] The SXT table manager software (SXTSPT) automatically compares the dumped table and the uploaded table. If the verification is OK, i.e. if they are exactly the same, it will display "OK". Immediately on the SXTSPT screen: enter number> [there will briefly flash a screen with a big green box] enter number> 4 [ this should return 'OK' (in red) ] If the verification is not OK, the system will show error infomation at the bottom. In this case, please stop operation here and call Super Toban. Even if you stop here, the instrument is safe. Do not proceed to SXT CTL AUTO. If there is the observing region address update, confirm that the address is actually updated using SXTQLCC PF15(Observing region page). The dumped table for verification is stored in the archive file memory of the table manager (SXTSPT), and you can see any table since launch. In particular, you can confirm that the table just uploaded has the same contents as the upload file. You can (in general, you should) add a comment for the archive record to clarify the purpose of the new observing table by entering 3 (the Table File Utility),i then enter 3 again, enter 1, write in the comment in the box next to the correct date and time entry, and exit using PF3. Two printout is stored in the SR0001. Those are a list of changed items and its old and new values, and a copy of hex command list set to KSC. This is for tarce purpose in case of problems, and is not used normally. Please delete these files by PFD 3.8 Delete, AFTER YOU CONFIRMED THE NORMAL OPERATION UNDER THE NEW TABLE. If something not normal happens, printout those copies and retain for investigation. For details on the table update, refer to "SXT Table Loading" by Nari Nitta. 8. ERROR RECOVERY __________________ Keep the separate error recovery manual with you duing operation. FOLLOW THE FLOW CHART IN THE ERROR RECOVERY MANUAL. If there is an error, the first consideration is the safety of SXT. In order to ensure this, a) Confirm the error flag, =========== PF5 of SAQL =========== ------ SXT ------ SYS A PWR AUTO MOD D/N SHT <- SXT shutter status OPN or CLS FAB <- SXT filter status B/A ER ERR <- SXT error status ***(normal) or ER (red) WRE WRM <- SXT software corruption indicator CCDTMP -21.00 ***(normal) or WRM (red, software corrupted) This status may flicker (pulse) for some type of errors. Watch carefully. ================================ any page of SXTQLCC(lower right) ================================ G:ON H:ON ** PWR CNT ** ON: OFF: ERR: ON: **ERROR** TIME: JERR: UERR: <- Error will be indicated here. Go to PF16 for detailed error info. b) Send YOBI COMMAND A (contingency command) to put SXT into the safehold position. =================================================================================== The SXT safehold operation is to close the shutter and to move the filters to position B=1/A=3 (the narrow-band optical filter). =================================================================================== c) Confirm the shutter and filter status using PF14 of SXTQLCC or PF5 of SAQL. =========== PF5 of SAQL =========== ------ SXT ------ SYS A PWR AUTO MOD D/N SHT CLS <- SXT shutter status OPN or CLS FAB 3/1 <- SXT filter status B/A ER ERR WRE WRM CCDTMP -21.00 ============================ PF14 of SXTQLCC (lower left) ============================ FR: 0 1 2 3 4 5 6 7 SETUP: -- -- -- -- -- -- -- -- SHTR: CL CL CL CL CL CL CL CL <- This should be CLosed. AS DR: OP OP OP OP OP OP OP OP FILTR: -- -- -- -- -- -- -- -- FIL-A: 3 3 3 3 3 3 3 3 <-This should be 3. FIL-B: 1 1 1 1 1 1 1 1 <-This should be 1. d) If you can not confirm this, proceed to YOBI COMMAND B. e) Confirm the shutter and filter status again. Either the shutter close or filter B/A=1/3 is sufficient enough fot the safety of SXT. NOTE: Yobi (contingency) command sequence Yobi A SXT CONTROL MANUAL [STOP SXT OBSERVATION] BC 84H 02H 01H [DAY] BC 84H 00H 01H [CLOSE SHUTTER] BC 84H 03H 13H [POSITION FILTER B/A=1/3] Yobi B SXT HARD RESET [RESET SXTE-U MICRO] DC EXEC [EXECUTE DOUBLE COMMAND] SHUTTER OFF [INITIALIZE SHUTTER MECHANISM] SHUTTER ON CAMERA ON [OK TO SEND EVEN IF ON] FILTER ON [OK TO SEND EVEN IF ON] OG 42H [OG 66 SXT FWA FREQ] changed at Rev. F OG 43H [OG 67 SXT FWA SETTLE] changed at Rev. F BC 84H 02H 01H [DAY] BC 84H 00H 01H [CLOSE SHUTTER] BC 84H 03H 13H [POSITION FILTER B/A=1/3] Yobi C SXT CONTROL MANUAL [STOP SXT OBSERVATION] BC 84H 22H 00H [CLEAR ERROR CODE 2] BC 84H 12H 00H [CLEAR ERROR CODE 1] Yobi command A tries to put SXT into the safe position by the normal procedure. This sometimes does not work, while Yobi command B always works. For critical error such as FILTER HARD ERROR and SHUTTER ERROR, the power for the filter, shutter, camera (power status C, D, and G) are automatically shutdown by the flight software. Yobi B recovers the system even for such a case. =================================================================================== This procedure a) has the highest priority over any other spacecraft level activity DURING the pass. In case of the errors, direct KSC toban to send Yobi commands procedures with highest priority. =================================================================================== b) If the 'Super Toban' isn't there contact him and consult on what to do. See also notes below about recovery for specific cases. The Super Toban must be available for this purpose, and the toban should have information (telephone number) about where to reach him. YOU MUST NOT LEAVE THE ERROR SITUATION AS-IS. YOU MUST CONTACT SUPER-TOBAN TO CONSULT WHAT TO DO. =================================================================================== If the error happenes at 5th orbit, and if you are not absolutely sure that the filter is B/A=1/3 and SHUTTER:CLOSE, please ask KSC to prepare a 6th contact operation, if available. If the error happens on Saturday and if you have a similar situation, please ask KSC to prepare a SUNDAY operation. =================================================================================== c) Using the "Yohkoh operations command sheet" (Yohkoh operations room) FAX the recovery commands to KSC as instructed by the Super Toban for the subsequent passes. The normal error recovery command sequence is stored in KSC MS computer, and it is OK to ask for the SXT recovery commands to be issued from KSC without providing a detailed command list, as long as the error type is understood. d) Monitor the uploading of the commands on the next pass, and return to auto control if all goes well. Check the RAM patch data by obtaining hardcopy. CHECK THE IMAGES JUST AFTER THE RECOVERY AS EARLY AS POSSIBLE TO MAKE SURE THAT THE RECOVERY OPERATION IS OK. e) When recovery is completed fill out an "SXT anomaly report" and give it to the SXT Super Toban. The SXT anomaly report as well as other information should be filed in the binder tagged "SXT anomalous event file". 9. SENDING SXT POINTING DATA TO GROUND-BASED OBSERVATORIES. ______________________________________________________________________________________. The procedure is as follows: 1) login to flare1, user=sxt, password=fuchinobe (You can login to flare1 from the workstation in the control room. ) ( green% telnet 133.74.8.1 ) ( ) ( login: sxt ) ( password: fuchinobe ) ( ) (Of course, you may work at flare1 itself in the operation room. ) 2) flare1% idl 3) idl> gbo_mail, NS, EW, Contact#, /comment Where EW and NS are the Coordinates from the SXT Operations sheet and Contact# is the KSC Contact (1-5). Then the program will prompt you to iuput comments. Please write some brief comments, such as that a table was uploaded, or that there is a large loop at the east limb (if there is), etc. Never forget to including the following information * The full title of the new table, such as "920914 SXT-1 PASS3 STD ARS1" (When table was uploaded). It helps the table manager to know table is uploaded * It is generate the mail message (which will include heliocentric coordinate conversion) and display it for review. You can verify that you entered NS and EW in the proper order. You will be asked if you want to send it (default is yes). If you see a problem, just answer no and no message is sent. Example Calling Sequences: idl> gbo_mail,200,159,4,/comment ;if you want to append comments ;to the message - routine will ;prompt until null line entered. All messages generated with this routine are archived in: /home/flare1/sxt/toban/gbomail/ with a file name: gbo_mail.YYMMDD_n (n=contact number) The routine only permits execution from SXT Toban Account (username sxt). This sends the pointing information to various observatories which can use it to coordinate their schedule. Please write comments when a table is uploaded. It's quite useful for ground-based observers to know what kind of observation SXT is doing. And it's also useful for SXT table managers (mails are sent not only to gbo's but also to table managers). For table managers, please put the table number (e.g. "920507 SXT-1 PASS 2 STD ARS2") in the message.. Announcing flare mode in real time conceivably could result in a ground-based observatory obtaining critical data. 10. POST-PASS DUTIES ____________________ 10.1. At the end of pass i) At the end of each pass: During the day you can safely log off the monitors between passes. **** WARNING: At night, and sometimes on weekends etc., the mainframe goes off line. To prevent this leave terminals logged ON. Otherwise you will be unable to bring anything up, or do any monitoring. If it does get shut off, it can be brought up by some of the experienced personel, IF they are around. This takes about one hour. ********** If you are uncertain leave one job logged on. Lock the screen on the workstation 'green', (services menu). ii) After the last pass Turn off the NEC consoles, logoff the mainframe monitors, and lock the workstation screen (Services menu item --> Lock Screen). If it's late at night, turn off the lights. File the operations sheets in their binder. 10.2. Write LOG NOTE Write anything you can not understand, anything strange on the SXT log note. Even if you have noting special, write OK with your sign on the note. It does no harm to write extra information here, and anything may be helpful later on in trying to figure out what happened. Any language is OK. 10.3. Creation of SIRIUS data base Check the SIRIUS data base is created. Normally the pass finishes by noon, the SIRIUS data base is created by the afternoon. However, tha pass time is later than that, it will be created next day (by around noon-4 pm). The creation of the permanent SIRIUS data base after editing redundant telemetry from DSN and noisy frames is relgularly done by SIRIUS subcontractors. When the SIRIUS is not created after the pass, it has to be created by SXT toban for immediate data check purpose. This is not permanent SIRIUS and will be erased soon. To know whether SIRIUS is created for the given time period, logon please> LOGON TSS CM002 current password for ..> ISASSXT ready> TO INF (this is the SIRIUS reference) input no.> 1 (planet & data) input no.> 2 (solar-a/yohkoh) input no.> 2 (play back data) Find the earliest entry for the day in question. Record the starting time. Return up one level with PF3. input no.> 1 (real time data) Find the latest entry for the day in question. Record the ending time. If the permanent files have not yet been created, logon on and type SRSJCL which creates temporary files listed as 'temp.real' and 'temp.P.B.'. These can be used instead of the permanent files, and are listed separately in the 'TO INF' software. You now have the time range for the previous days KSC data. Use these in the following procedures. Exit with PF3. Note that in case the later runs go beyond 5:00 pm (or close to 5:00) not all the data sets will have been transferred (it usually takes about 30 min. for them to be loaded into Sirius.). On weekends and holidays, one must run SRSJCL as described above. 10.4. Creation of the reformatted data base Run SRSGET to transfer data from SIRIUS to workstations. First check the Hard Disk capacity with df /raw_tlm/v1/yymm If usage is over 80%-90% you need to delete the OLDEST files to make room. One day's KSC data will require about 80 MB. on flare1: enter the unix command 'srsget' at the prompts, y/n : y S(yymmddhhmm): start date/time E(yymmddhhmm): end date/time KSC real y/n : y (real time) KSC P.B y/n : y (play back) GOLDSTONE y/n : n CANBERRA y/n : n MADRID y/n : n temp. real y/n : n or y if you created tempral SIRIUS, temp. P.B. y/n : n or y these should be yes. y/n : y Sit back and let it run, it takes 1-2 hours. NOTE: If srsget is not available there is a way to do the same thing using SXTQLGG (also used to monitor the PFI realtime images) on the Facom. Ask the Super Toban. ==================== Do reformatting. ==================== When SRSGET has run, rlogin isass0 idl .run go_reformat92 then select parameters appropriately. 10.5. Run SXT health check programs There are two health check programs: 1. FLTERR checks the filter error. 2. EXPLOG list for both FFI and PFI. There are other programs which need to be run with proper period, if instructed by tsuneta i) FLTERR and EXPLOG On the Facom: logon please> LOGON TSS QLSA0X (X=0,1,...) current password for ..> ISAS ready> PFD TERMLANG(E) (gives English version) option==> 2 (the editor) it should pop up with a screen including the following, project> SR0001 (fix any of these that are different) library> LIST type> CNTL member> SXTTOBAN (type in this last one) You are now editing a JCL file. There are three sets of dates YYMMDDHHMMSS. These are currently on lines 1400/1500, 2801/2802, & 4401/4402. Edit these to match the times you found above (the first is the start time, the second is the end time). Change the account name on the top and the second lines of JCL to your account name QLSA0X. In this editor use PF8 to move down one screen, and PF7 to move up. Within a screen you can position with the cursor keys. When done bring the cursor to the command line at the top of the screen and type SUB, and hit . A message appears at screen bottom confirming the job submission (this always says QLSA0X), hit return and a similar message will appear at the top of the next screen. This includes the job number QLSA0X*, (* is an alphanumeric character). Record the alphanumeric in order not to forget it when printing out). It will take 20-30 minutes for this to run. When you think it's done, enter PFD as above, OPTION==> 3 (select utilities) OPTION==> 8 (select outlist) OPTION==> L (do listing) Returns a list of job numbers executing or waiting for output, with comments as to what their state is. If yours is "waiting for output" update the job number, (use cursor keys to get around) JOBNAME> SROOO1* OPTION==> R (print out) *****WARNING**** do not input P, even though this seems the obvious choice! It will print out on the big printer on the 3rd floor of B-toh, room #2307. To retrieve the printout, open the main printer door (push latch, top edge on right side). There are five buttons, three in one row, two more below them. The top three control the paper tray, UP/STOP/DOWN in that order. Lower the tray a bit and use the ruler (on the floor inside the printer) to detach the paper, raise the tray, and close the door. File the logs. 10.6. File GOES and NOAA data Throughout the day incoming GOES and NOAA data sheets are printed on the FLARE1 printer in the Yohkoh ops. room. These need to be filed in their respective binders. The toban should examine this other real-time data and try to understand whether or not the current SXT observing tables are appropriate. MANUAL data access: telnet 132.163.224.10 username image 1. for image data, ftp data 2. for event list, cd sys$userroot:[max91] dir *eve*.text to obtain file names ftp data. 11. DATA CHECK ______________ SXT image checking is one of the most important responsibilites of SXT toban. It is important to make sure that SXT FFI and PFI images are taken properly. 11.1. After each pass and/or the 5th pass The reformatted database have to be created twice per day. After the 1st pass, it needs to be created to check the images and the observing location as early as possible after 15 hours of non-contact time. This is particularly important when KSC operation is at night, and images can not be checked in real-time manner. After the 5th pass, the database need to be created using all the real and playback data of the day to systematically check the SXT images. i) FFI check Check that all of the FFI have been taken properly. When there is not any bright active region, long exposure (15 sec) is contained in FFI sequence table. This has to be removed when bright active region appears to protect CCD. PLEASE MAKE SURE THAT EXPOSURE TIME IS NOT EXCESSIVE. ii) PFI check Check also some PFIs to make sure that active regions are selected or tracked properly, and exposure time is properly controlled by AEC. Test_rd movie mode is suitable to make gross checks of the PFI data. iii) Observing location check Check that PFI observing region locks the desired active region. This can be known by checking the PFI images and observing region coordinates in SXTQLCC or plot_fov function of .run test_rd. PLEASE MAKE SURE THAT OBSERVING REGION IS LOCKED ON THE DESIRED ACTIVE REGION. IF OBSERVING REGION IS LOCKED SOMEWHERE DARK POINT ON OR OFF THE SUN, IT WILL SERIOUSLY DAMAGE THE CCD. IN THIS CASE EMERGENCY CORRECTIVE ACTION IS REQUIRED. 11.2. After DSN data have arrived The SSOC toban will generate SA plots containing SXS, HXS, and HXT time profiles, after all DSN data have arrived. Find the "flare mode flares" and check in the PFI images that the flare data were properly taken in terms of ARS and AEC. Record the date, time, results of the PFI data check in the FLARE CHECK notes. If a flare that was supposed to be recorded in the PFI was not in fact recorded, contact Super Toban immediately. This is an important item for SXT health. 12. HIKITSUGI _____________ After finishing your duty for one or two weeks, there maybe something which you cannot complete or you have worried about, so that the proper transfer of information to next SXT toban (hikitsugi) is vital part of your work. The system probably will have changed relative to what has been described in this document, and your suggestions may help to change the system in positive ways. Some check items are as follows: 0. SXT operation practice SXT operation procedure is changing. Even if the new toban came here a few months ago, he/she should expect subtle but important change. Make man-to-man practice for Toban work. . 1. SXT anomaly not solved 2. SXT error occurrence rate last week 3. SXT data check FFI/PFI check PFI flare check 4. SXT observing mode 5. Coordinated observation schedule, if any END of report