SSOC Tohban Report for Week 44_95 (October 30 - November 6, 1995) SSOC: R. Kano, (M. Mizutani) KSC : M. Akioka, M. Yamamoto Attendance at WOM: L.Acton, E.Deluca, H.Hara, H.Hudson, K.Ichimoto, T.Ishii, R.Kano, J.Khan, T.Sakao, S.Savy, M.Sawa, Te.Watanabe 1. Solar Activity -------------------------------------------------------- The solar activity was very low. The GOES level is about A2. There was no flare in the last week. 2. Standard Operations --------------------------------------------------- 2.1 SXT Table Uploads : 3 total --------------------------------------------------------------------- Date Pass number Name --------------------------------------------------------------------- 30-Oct-95 4 951030 P4 ARS1 STD+LONG 31-Oct-95 2 951031 P2 ARS1 DKCAL 1-Nov-95 2 951101 P2 ARS1 STD+LONG --------------------------------------------------------------------- Each time an SXT Table was uploaded a patrol image was taken by executing the command 'DP BC "8C 05"'. 2.2 STT Timer Setting The STT Timer was set on 1-Nov-95 (Wednesday) pass # 2. The next timer should better be set 7-Nov-95 (Tuesday). 2.3 S/C pointing The S/C normal pointing OG-20H(32D) was executed on 30-Oct-95, because the S/C pointed slightly southward after the ACS recovery operation. The E17-N00 offpoint was done twice on 2-Nov-95 and 3 times on 3-Nov-95 for the SXT terminator image 3. Errors & Problems ------------------------------------------------------- 3.1 No SXT Errors 3.2 No BCS Errors 3.3 The flare1 printer was fixed. 4. DSN Communications ----------------------------------------------------- 4.1 DSN Final Schedule for W45 None. 4.2 DSN Preliminary Schedule for W46 We canceled 4 DSN contacts from the Preliminary Schedule for W46. 4.3 DSN Strawman Schedule for W47 The last Friday was the holiday. The negotiation with ASCA was postponed. This afternoon, we will cancel DSN contacts from the Strawman Schedule for W47. 4.4 Pass additions None. 4.5 Re-transmission requests Katano_san sent 3 re-transmission requests for data as follows: DSS 46, 288/16:28 5th request: 1-Nov-95 DSS 66, 299/10:41 1st DSS 16, 304/18:43 1st 5. Yohkoh/Asuka/SFU Pass Conflicts at KSC --------------------------------- In W45, 10 KSC passes were lost because of the conflicts with ASCA. There were no pass conflicts between Yohkoh and SFU. The orbit of SFU will be changed in two weeks, and it will be operated in the week of 12- to 18-Nov- 95 at KSC. 6. Special operations ------------------------------------------------------ None. 7. Holiday Schedule -------------------------------------------------------- The next holiday will be on Sunday, 11-Nov-95. 8. Hikitsugi Items --------------------------------------------------------- 8.1 Tohbans for Week #45 KSC : M. Yamamoto, M. Mizutani SSOC : T. Ishii, K. Ichimoto 8.2 STT Timer Setting The next STT Timer should be done on Tuesday, 7-Nov-95 (Tue). 8.3 Offpoint terminator images If terminators appear in the OP generated by running `op_first_guess,' then the OP should be faxed to the SXT_CO (Chief Observer) in D-toh. The SXT_CO will then inform the SSOC tohbans if offpointing will be carried out. If so, the OP will need to be edited appropriately. 8.4 Transmission of OP Please note that the OP could be transmitted to KSC anytime and report them to Shuto_san, if you have troubles (See appendix-A). 8.5 SXT Patrol Image Dumps The command `DP BC "8C 05(Hex)"' should be executed whenever an SXT table upload occurs. This command dumps an SXT patrol image which is needed to check the ARS parameters since the Sun is very quiet. ^L Appendix-A ----------------------------------------------------------------- Yokoh Operation Memo 1995 November 3 written by T. Kosugi Subject: Transmission of OP/OG or SXT Table files from SSOC to KSC There have been troubles in transmitting OP/OG files or SXT Table file from SSOC to KSC, which resulted in a rumor that OP/OG or SXT Table files are better NOT to be transmitted during a certain period, say, from 30 min prior to the KSC AOS till 10 min after the KSC LOC of an ASCA satellite. This is not a groundless rumor, of course, because we have actually experienced troubles, because we have discussed this at WOM, and also because we have seriously hoped to avoid unnecessary troubles due to a missing transmission. It has become clear, however, that this passive attitude is not good to solve the real problem by removing bugs which may still be alive in our operation system. Now we'd like to establish a new guideline, whose aim is to pinpoint the cause of the trouble. This memo is written for this purpose. Please read carefully and obey this new guideline when you are assigned SSOC or KSC Tobans. The SXT Chief Observer is also requested to know the following. 1. Possible causes of missing transmission ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The figure below shows the transmission route. SSOC #1 ---| |--------> SSOC MS ---------> KSC MS SSOC #2 ---| OP/OG files are edited either by SSOC #1 or SSOC #2 and stored in a common DASD between them. On the other hand, SXT Tables are handled only by SSOC #1. Both are first sent to SSOC MS computer, through which they are transmitted to KSC MS computer. Thus, possible causes of missing transmission are: i) Files are not created in SSOC #1 or #2; ii) Files are not sent to SSOC MS; iii) Files are missing in between SSOC and KSC MS computers. If the cause is Case iii) above, the NEC operator at KSC may handle the recovery. The known cause for this is either of the following two: a) Files are sent when KSC MS is under IPL. b) Files are sent when KSC MS is hung up. In either case, once the KSC MS is set up, the NEC operator at KSC can know if there are files in SSOC MS which have not been sent to KSC MS, and to resend them from SSOC MS to KSC MS. I have asked the NEC operator at KSC to establish a procedure to check this point, say 10 min prior to the start of the operation. The SSOC Toban is responsible for Cases i) and ii), if any (I don't know whether we've experienced such cases). I strongly recommend the SSOC Toban as well as the SXT Chief Observer to retry the transmission IF they are not sure whether what they've done is the correct handling of the SSOC #1/#2 computers in transmitting the files. IMPORTANT: From now on, no checking is required on the file transmission status by checking the MS displays or printouts at the third floor of Building B. Instead, SSOC Toban as well as the SXT Chief Observer is requested to make a report on the trouble, especially on the transmission time. By knowing the precise times we can trace the problem. Please let Shuto san as well as me know if Toben has such a case. 2. Transmission Timings ^^^^^^^^^^^^^^^^^^^^^^^ There is no need to be concerned about the timing of file transmission from SSOC to KSC. 3. If Files are Found Missing or Not Prepared in Time ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ In cases when the NEC operator at KSC finds that there are no files successfully received by neither of SSOC nor KSC MS computers, say at 10 min prior to the operation, 1) (OP/OG files) KSC Toban is requested to logon the SSOC #1 or #2 and retry to send the relevant files to KSC MS. 2) (SXT Table file) As a baseline, KSC Toban may cancel the planned operation (upload of the table) at that pass, and halt the SXT operation by placing an SXT HALT OG (OG 46H (70 in decimal)) as ROG. When the KSC Toban is sure that the current SXT Table does not contain anything dangerous, the SXT operation may be continued. The most important thing is to take a record on the times of file creation ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ (in cases of OP/OG files, the time to press return key for the transmission) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ and let Shuto san and Kosugi know the time if a trouble happens. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ (end of memo)