SSOC Tohban Report for Week 42_95 (October 16 - October 23, 1995) SSOC: K. Marubashi, J. Lemen KSC : M. Takahashi, K. Yoshimura Attendance at WOM: J. Khan, J. Lemen, S. Savy, T. Yoshida, R. Kano, K. Marubashi, S. Masuda, M. Sawa, T. Kosugi (chair) and T. Watanabe 1. Solar Activity ----------------------------------------------------------- Another week of enhanced solar activity, mainly from NOAA 7912. The GOES level was at Class B for most of the week. On 20-Oct-1995 there was an M2 flare from 7912 that occurred just after the SAA. Like the event of last week on 13 October, this flare produced a Type II burst and ejecta was observed in the SXT X-ray images. NOAA 7912 was the target for the Chromospheric Activity campaign for most of the week and this region will be within a day of the west limb at the time of the solar eclipse. 2. Standard Operations ------------------------------------------------------ 2.1 SXT Table Uploads : 5 total --------------------------------------------------------------------- Date Pass number Name --------------------------------------------------------------------- 16-Oct-95 3 951016 P2 ARS2 DKCAL 17-Oct-95 1 951017 P1 ARS2 STD 18-Oct-95 1 951018 P1 ARS0 ECL TEST 18-Oct-95 3 951018 P3 ARS2 STD+LONG 21-Oct-95 2 951021 P2 ARS2 STD --------------------------------------------------------------------- Each time an SXT Table was uploaded a patrol image was taken by executing the command `BC 8C 05'. 2.2 STT Timer Setting The STT Timer was set on 17-Oct-95 (Tuesday), pass #2 and 23-Oct-95 (Monday) pass # 2. The next timer setting should be 31-Oct-95. 2.3 OP offpoints The upcoming eclipse (see below) requires offpoints, so SXT must obtain off-pointed images at terminator times. Several offpoints were accomplished last week to acquire the necessary terminators. It was discovered that the W17 offpoint produced a band of straylight in the SXT images. Therefore, the W17 offpoint OG (#34) was revised to be a W07 offpoint by Hugh Hudson. The terminator for the W07 offpoints will be acquired on Monday between Passes 4 and 5. The offpoints for the special eclipse observations have already been planned. The general rule for offpoint OG insertion is as follows: Offpoint OG at one time step before the SXT CTL MAN Normal point OG at 1 time step after SXT CTL AUTO 3. Errors & Problems ------------------------------------------------------- 3.1 SXT Errors None. 3.2 BCS Errors None. 3.3 KSC MS Computer Problem On Saturday at pass 2 (951021-0309) the MS computer at KSC hung during operations. As a result, there were no data acquired between Pass 2 and Pass 4 (Pass 3 was an ASCA pass). The BDR dump was done at Pass 2 and the SXT Table was loaded, but the BDR REC command could not be issued. 3.4 Flare1 printer The flare1 printer failed on 9 October and has not yet been fixed. The "lpr" command is now directed to the ASCA printer next door. op_first_guess stopped printing on the ASCA printer because the que name in the printcap file on the flare workstations was changed. op_first_guess was modified. 3.5 OP_FIRST_GUESS If op_first_guess schedules a terminator and medium telemetry rate is selected before the Camp Obs Off OG, make sure to delete the terminator. This will be fixed in a future release of op_first_guess. The strategy for choosing KSC LOS as QT-H or QT-M on the "second" day was revised according to the discussion held at last week's WOM. However, we found this strategy did not work properly for a special weekend type of command load. One of us (JRL) will continue to investigate the optimum solution. For the time being, we have restored the older strategy. 3.6 Line down for file transfer On 18 October and 19 October we experienced failures of file transmissions from ISAS to KSC. On 18 October it was an SXT table that was not transferred. On 19 October it was the OP/OG that failed. We contacted Shuuto san. He was able to investigate the second failure and determined that the problem was that we had sent the table during an IPL (Initial Program Loading) following an ASCA pass. This led us to a different understanding about when it is permissible to send the OP/OG to KSC (see Appendix A). We propose that this point be discussed, that the procedure be updated and documented, if necessary. 3.7 Mainframe 2 Down for Maintenance On Friday, 20-Oct-1995, SSOC Mainframe #2 was down for maintenance during the morning until 13:00. This had several effects on Tohban life. First, op_first_guess could not automatically transfer the OP by FTP. Second, the s88239 account could not be used to run the op(opogedt) editor. As it turns out, we were able to get around these problems by trial and error using Mainframe #1. However, we recommend that Sterling san add additional instructions to the Tohban Manual for this case (see appendix B). 4. DSN Communications ------------------------------------------------------- 4.1 DSN Final Schedule for W42 We canceled no DSN contacts from the Final Schedule for W42. Three passes were canceled on 18 October by JPL for STS support, but after the Shuttle launch was postponed, they were reinstated. Two other passes were canceled by JPL. One on 20-Oct-95 and the other on 23-Oct-95. 4.2 DSN Final Schedule for W43 There were no (0) cancellations for W43. 4.3 DSN Preliminary Schedule for W44 We made 19 cancellations for W44. 4.4 DSN Strawman Schedule for W45 We canceled 94 DSN contacts from the Strawman Schedule for W45. Of these 31 were out-of-bounds Santiago passes. The allowed time range is 1300-2345 Monday-Thursday, and 1245-2330 Friday- Sunday. We sent a message to Jose Valencia to find out why these out-of-bounds Santiago passes are included in the Strawman plan. 4.5 Pass additions None. 4.6 Re-transmission requests We sent re-transmission requests for data as follows: DSS 76, 285/19:38 3rd request: 20-Oct DSS 76, 287/02:49 2nd DSS 46, 288/16:28 2nd DSS 76, 292/21:51 1st The first two have been sent before, but they were corrupted. 5. Yohkoh/Asuka/SFU Pass Conflicts at KSC ------------------------------------ 5.1 In W42, 9 KSC passes were lost because of the conflicts with Asuka. There were no pass conflicts between Yohkoh and SFU. 6. Special operations ------------------------------------------------------ 6.1 Terminators OG #34 was changed for the eclipse observation to S/C W07 N00. Terminators were scheduled at the E18 and W07 offpoint positions. Please coordinate future terminator operations with the SXT Chief Observer. 6.2 Eclipse 24-October. The "eclipse committee" met on Wednesday. The participants included Hudson, Watanabe, Yoshida, Marubashi, Savy, and Lemen. Kano san was unable to attend but he and Yoshida san have prepared a comprehensive OP and OG plan to conduct special operations during the eclipse. By a special favor Asuka has moved its holiday schedule to the eclipse day. Thus, Yohkoh will use all SIX passes for eclipse operations. 6.3 OG Write was done on 20-Oct-95 pass #1. 6.4 DP Error Recovery Plans We received a memo via Te. Watanabe from Fujitsu, dated 20 September 1995, which discussed the issue of DP errors and the appropriate recovery plan. The document was in Japanese and a version has been attached to this report (not included in the e-mail version). We will attempt a brief summary here. A. Yohkoh team proposals: The Yohkoh team made four (4) proposals to Fujitsu which were as follows: Option 1. For any kind of DP error, send 3 commands: 1. ERR DUMP-H 2. ERR LOG CLEA 3. ERR CANCEL Prior confirmation/notification of Fujitsu is not required before sending these commands. Fujitsu must be notified after the fact. Option 2. Send the above three commands if any of four particular DP errors occur. These are errors that have previously occurred during Yohkoh operations: 1. DP error 81: BDR write timeout error. 2. DP error 90: BDR error. 3. DP error A4: SXT -- related to interruption of long exposure. 4. DP error A5: SXT -- related to interruption of long exposure. Prior confirmation/notification of Fujitsu is not required before sending these commands. Fujitsu must be notified after the fact. Options 3 and 4. These options are essentially the same. They propose that Fujitsu be contacted in the case of a DP error. The Yohkoh team must wait for instructions from Fujitsu. B. Fujitsu Analysis. Fujitsu have considered these three proposals. They think Option 1 as proposed is too dangerous. If a new DP error occurs, the above commands may not be the appropriate response and further investigation may be required. As for Option 2, they agree with this option for SXT-related errors, since the cause is well understood and it is also certain that there is no implied harm for the spacecraft. However, the BDR-related errors are not well understood, and so Fujitsu does not want this automatic response to be implemented for BDR-related errors. Options 3 and 4 were essentially the same. Fujitsu thought it was not necessary for the Yohkoh team to contact Fujitsu in the case of the well-understood SXT-related errors. C. DP Error Recovery Plan Summary In case of DP errors A4 and A5 (SXT-related errors), the Yohkoh team should execute the three recovery commands (given under Option 1), resume normal operations, and then notify Fujitsu. For all other DP errors, the Yohkoh team must contact Fujitsu and wait for instructions. 7. Holiday Schedule -------------------------------------------------------- The next holiday will be on Sunday, 29-Oct-95. Last week's tohbans did not assign 4 November (starting at 19:00 UT) as a holiday when they held their discussions with the ASCA team (the Nagase san meeting). Nagase san suggested that Yohkoh and ASCA make 4 November the spacecraft holiday. 8. Hikitsugi Items --------------------------------------------------------- 8.1 Tohbans for Week #43 KSC : K. Yoshimura, M. Akioka SSOC : S. Morita (ex. 23rd), Te. Watanabe 8.2 STT Timer Setting No STT Timer settings are required by this week's Tohbans. The next STT Timer should be done on Tuesday, 31-Oct-95. 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 Last week it was reported: Please note that the OP should not be transmitted to KSC during the times of SFU passes. Before transmitting the OP the tohbans should check the sheet `Tracking Passes at KSC' to see whether an SFU pass is in progress. This procedure may need to be updated according to the WOM discussion. 8.5 SXT Patrol Image Dumps The command `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. 8.6 SSOC Check List The SSOC Check List was updated. Please make sure to use the version dated 21-Oct-1995. As suggested by last week's tohbans, we have added a new check item to file the KSC operations report electronically on the flare1:/home/flare1/yohkoh/ops_rep directory. ^L 21-Oct-1995 Appendix A: Transmitting OP/OG files from ISAS to KSC The recently released English Tohban manual (16-Oct-1995, A. Sterling) and the hikitsugi item 8.4 both warn against transmitting OP/OG files from ISAS to KSC _DURING_ an SFU real-time contact. During W42, we found that this procedure is not sufficient. We spoke with Shuuto san and also with ASCA personnel and have come to the following conclusions: 1. Yohkoh OP/OG files should not be transmitted at times which are close to real-time operations of Yohkoh, ASCA or SFU. 2. The period during which files should not be sent are: 30 min prior KSC AOS until 10 min after KSC LOS After the LOS, the IPL (Initial Program Loading) may be run. If this is started slightly late, then waiting 10 min might not be enough time, in which case it may be necessary to re-send the file. ^L 21-Oct-1995 J. R. Lemen Appendix B: How to be an SSOC Tohban without Mainframe 2 If Mainframe 2 goes down, it is possible to conduct most necessary SSOC operations using Mainframe 1. There are some different procedures when using Mainframe 1 which will be noted here. 1. OP file transfer from op_first_guess to mainframe. The op_first_guess program will normally FTP the OP list to the mainframe for you. The FTP file transfer does this via Mainframe #2. It is not possible for a workstation to send files to the more secure Mainframe #1, so one must initiate the transfer manually from Mainframe #1. Here are the steps to follow. - Create the opymmddp.hex file using op_first_guess on the workstation. - Logon to Mainframe #1 using one of the ISAS/SSOC accounts (eg., qlsa02, qlsa03, etc.) - Next type the following set of commands: PROF PRE(SR0001) FTP ftp> h flare1 ; The actual ftp prompt is just the ; letters FTP on a separate line. >>>> SXT ; You are asked for your username (in Japanese) >>>> password ; You are next asked for the password. Ask the ; previous week's tohbans for the flare1 SXT ; account password. ftp> recv INPUT FILENAME -- /ydb/orbit/opog/opymmddp.hex OUTPUT FILENAME -- opseq.infile(opymmddp) ftp> end 2. OPOGEDT editing and file transfer. The opogedt editor can be run on Mainframe #1 using one of the ISAS/SSOC accounts. Use the following steps: - Logon to Mainframe #1 using one of the ISAS/SSOC accounts (eg., qlsa02, qlsa03, etc.) - Next type the following set of commands: PROF PRE(SR0001) EX OP(OPOGEDT) then proceed as normal. The print command is different (see below). 3. Printing OPs from Mainframe #2. The OP generated with editor opogedt can be printed from the Mainframe #1 computer much the same as it is done on Mainframe #2. First, you must exit opogedt and then logon again. Next type a command like: out qlsa02(Txxxx) new(E) ; Mainframe #1 If you make a mistake and use new(D) on Mainframe #1, then you must type a command like: cancel qlsa02(Txxxx) p to delete the output file.