SSOC Tohban's Report for Week 27 (29 June - 5 July 1998) SSOC : Yokoyama, Tsuneta KSC : Magara, Akiyama 0. Meeting Attendance Hara, Hudson, Khan, Kosugi, Ogawara, Sawa, Shirts, Slater, Suematsu, Watanabe, Yokoyama ----------------------------------------------------------------------- 1. Solar Activity and significant operational event Solar activity of this period was low to moderate. There were two M1 flares with several C-class flares. Owing to the Planet-B launch operation at KSC, all the Yohkoh operations on the nights of June 30, July 3, 4 were cancelled. The operation on July 5 (Sunday night) was done. Since the OP sent on the night of July 2 covered 3 days, most of DSNs were cancelled. ----------------------------------------------------------------------- 2. Standard Operations 2.1 SXT Table Uploads The following SXT tables were uploaded last week. ---------------------------------------------------------------- Pass ID Pass Table ID ================================================================ 980701-1030 1 980701 P1 ARS1 STD+TRACE 980701-1237 3 980701 P3 ARS2 DARKCAL 980702-1134 1 980702 P3 ARS1 STD 980705-1032 3 980705 P3 ARS1 DIFF ---------------------------------------------------------------- The table upload at Pass4 at June 30 Tue (980629-1239) was unsuccessful. It was because of the trouble of the main-frame network during the Planet-B preparation. It is recovered now. 2.2 STT timer setting STT timer was set at pass 2 (980629-1032) on June, 30. 2.3 Calibration 2.3.1 HXT Calibration None 2.3.2 BCS Calibration None -------------------------------------------------------------------------- 3. Errors and Problems 3.1 BCS Errors Pass 3, July 6 (980705-1032). Recovery on the next pass. 3.2 SXT Errors One bit-map error Pass 1, July 2 (980701-1030). Recovery on the same pass. 3.3 The harddisk on flare1 workstation Crashed One of the hard-disks on flare1 workstaion has crashed on Saturday. It included the home-directory of the 'yohkoh' account. Most of the files younger than one-month old were lost. But the KSC and SSOC operation reports were recovered. ----------------------------------------------------------------------- 4. Special Operations None ----------------------------------------------------------------------- 5. DSN Communications 5.1 DSN Schedule Passes were deleted by SSOC Tohbans as follows. ------------------------------------------------------------------- DSN Schedule Week Deleted Passes =================================================================== Final W28 3 passes deleted by SSOC Preliminary W29 No passes deleted by SSOC Strawman W30 62 passes deleted by SSOC ------------------------------------------------------------------- 5.2 Data Transmission from DSN 169 46 0728 not received Requested 22 Jun Closed/ No data 177 76 0704 corrupted tape Requested 30 Jun Closed/ Correct data 177 76 1211 corrupted tape Requested 30 jun Closed/ Same data 179 76 1103 corrupted tape Requested 30 Jun Closed/ Correct data ----------------------------------------------------------------------- 6. KSC Pass Conflicts and Schedule 14 passes (including whole 2 days) were lost due to the launch (and its preparation) of the Planet-B. 2 more passes were lost due to conflicts with the other space crafts (HALCA, AKEBONO). ----------------------------------------------------------------------- 7. Hikitsugi Items 7.1 Tohbans for week 28 (6 July -12 July) SSOC : Suematsu, Sawa KSC : Akiyama, Shiozawa 7.2 STT timer setting Should be done on schedule Monday, 6 July if possible. The Canopus tracking situation is good. 7.3 Holiday Schedule The holiday in week 28 will be on Friday, 10 July (JST). 7.4 Update on the Late Arrival of the Final Schedule from Wallops The final schedules for week 27 arrived on Thursday, as we had hoped. 7.5 KSC operations on July 8 The 1st and 2nd passes on July 8 are not confirmed yet. They depend on the Planet-B situations. Be careful with the e-mail communication from Murata san who are responsible for the operation scheduling. ===================================================================== || The following is the same as the previous week's report (except || || for some rewriting). || ===================================================================== 7.5 DSN selection by the program FMT_WALLOPS The SSOC tohbans should check the ACTIVITY column of the 7dayss-list to make sure that the keyword TKG PASS is not omitted or replaced with another term. This happened last week. The FMT_WALLOPS program searches for TKG PASS and willeliminate passes without this keyword. According to Wallops they will not use other comments in the ACTIVITY columun. But the SSOC tohbans should check this for the next few weeks just to make sure. 7.6 Pass Additions and Wallops Deletions At the meeting it was decided that for the Strawman schedule the SSOC tohbans should select the best DSN passes but, in addition, they should not delete any Wallops passes. After receiving the Preliminary schedule with JPL/DSN deletions, the unnecessary Wallops passes should be deleted. 7.7 DSN scheduling Since mid week 10, 1998, Wallops schedules all DSN passes instead of JPL. The system to communicate with Wallops is still under construction. For details, see the temporary manual in the file ~wallops/README file on flare20. All DSN-related software should be run from an IDL session in the flare20/wallops subdirectory. Please immediately report any problems with the DSN software or errors in the manual to Hudson san. (New week 25) Please retain all Wallops passes in the Strawman cancellation process. We have been informed by Wallops that this is OK. These passes are cancelled by NASA less frequently, so by doing this we avoid days with almost no coverage. 7.8 Bug in op_first_guess SSOC tohbans should be aware of a bug in op_first_guess, e.g., "% OP_START_END: Problem with detection of LOS/AOS/DSN Repro Events". If DSN-related software in the directory ~yohkoh/wallops does not work correctly, check to see if the files being used which you have obtained through ftp from Wallops (e.g., 7dayss.wNN) are written in the same format as the previous weeks' files. We experienced (week 25) some confusion about the timing of KSC AOS and the DAY OG. Please be careful. If there is an KSC-AOS NIGHT one step before the DAY OG, normally the two commands can simply be interchanged and the AOS command switched to DAY. 7.9 BDR trouble (See 'DP error' in "SSOC Tohban's Report for Week 02" in 1998.) A DP error (error code = 90 ->75) was found during the data dump at 980106-0411. 2 of 20 BDR blocks are not accessible. As a result, the capacity of BDR is at the moment nine-tenths that of the normal capacity. This error has not been recovered yet. Please note the special commands, RST BAD BANK DP DC EXEC now routinely appearing in the end of command sheets. This is part of the recovery attempt. 7.10 E-mail communications We rely upon e-mail more and more. For operations-related e-mail, it's hereby suggested that we make it a rule to ACKNOWLEDGE the receipt of any such e-mail message. This applies particularly among SSOC, SXT_CO, KSC and SXT_ST. 7.11 Long Range Schedule Arrangement for Planet-B Planet-B was launched on July 4, 1998 for the mission to Mars. During the flight operation (lasting for twenty six days before the launch window begins), the KSC 20-meter antenna system will be used. After the launch, Planet-B will be tracked by the USD 64m and the newly (to be) installed KSC 34m antenna. Tracking schedule during the flight operation interval will be negotiated among the five teams namely: AKEBONO, YOHKOH, ASCA, HALCA and Planet-B. (Tetsuya WATANABE,NAOJ) * For more information, see a filed report (written in Japanese). ----------------------------------------------------------------------- 8. Action Items (Same as last week's SSOC Report) 8.1 Further software development. Status CONTINUING. It would be greatly appreciated if the SSOC tohbans could recommend any software development that they think will save future tohbans time and which improves the reliability of their work. 8.2 Week-48-A/I-1 /Hudson/status AJAR. PRINT_OGALL still does not work well. Hudson will fix it next. After the corrections are made, these procedures should be incorporated into the tohban manual. === END ===