SSOC Tohban's Report for Week 11 (9 Mar 1998 - 15 Mar 1998) SSOC : Y. Liu & K. Shibasak KSC : Te. Watanabe & Kubo 0. Meeting Attendance Ohyama, Kosugi, Shimizu, Watanabe, Hudson, Khan, Liu, Shibasaki 1. Solar Activity Solar activity returned to a high level, but thus far without major flares. The extraordinary high-latitude region (46N plus solar tilt) gave us a novel perspective on AR loops away from the E or W limbs. There are many active regions currently on the Sun. (ftp://isass0.solar.isas.ac.jp/pub/sxt_co/SXTweekly.html). 2. Standard Operations 2.1 SXT Table Uploads The following SXT tables were uploaded last week. ---------------------------------------------------------------- Pass ID Pass Table ID ================================================================ 980309-0101 3 980308 P3 ARS1 STD 980309-1443 2 980309 P2 ARS1 STD DIFF 980311-0103 4 980310 P4 ARS1 DARKCAL 980311-1341 2 980311 P2 ARS1 STD-JET 980312-1342 2 980312 P2 ARS1 STD ---------------------------------------------------------------- 2.2 STT timer setting STT timer was set at Pass 4 (980310-0102) on 10-Mar (Tuesday). 2.3 HXT & BCS Calibrations 3. Errors and Problems 3.1 SXT Errors and Problems None 3.2 BCS Errors Error was found at Pass 2 (980309-1443) on March 10 and was recovered during the pass. 3.3 Command transmitter trouble Around the Pass 2 (980313-1342) on March 13, the command transmitter of 20 m antenna failed. Due to the combination of misoperation and the transmitter failure, the weekend OP write and SXT table upload could not be done during the pass. As the quick recovery was not expected, we cancelled all the DSN contacts during the weekend. The repair was successfully done during the weekend and Yohkoh operation resumed from the first pass on Monday. 4. Special Operations There were no special operations this week. 5. DSN Communications 5.0 RASM use discontinued NASA ground-station support activities has handed over from JPL to Wallops from mid week10. All the DSN related works should be done using routines under flare20/wallops. The new system uses e-mail and FTP instead of RASM. Temporal manual for the new system is in flare20/wallops/README file. Please use this version and comment to Hudson san if it has errors. 5.1 DSN Schedule Passes were deleted by DSN and SSOC Tohbans as follows. ------------------------------------------------------------------- DSN Schedule Week Deleted Passes =================================================================== Final W11 20 passes canceled by SSOC W11 1 pass canceled by DSN Final W12 10 passes canceled by SSOC W12 2 passes canceled by DSN Preliminary W13 2 passes canceled by SSOC Strawman W14 92 passes canceled by SSOC ------------------------------------------------------------------- 5.2 Data Transmission from DSN 055 46 1721 corrupted Requested 02 Mar no response Requested 04 Mar no response Requested 10 Mar no response Requested 13 Mar 058 46 1308 not received Requested 04 Mar no response Requested 10 Mar no response Requested 13 Mar 061 16 2307 corrupted Requested 04 Mar no response Requested 10 Mar Closed / same data 064 66 0722 not received Requested 10 Mar Closed / correct data 066 76 1430 corrupted tepe Requested 10 Mar Closed / same data /home/flare1/yohkoh/dsn_corrupt/98_11 made by Seko-san 6. KSC Pass Conflicts and Schedule In week 11, 4 passes were lost due to HALCA operation and 6 passes due to AKEBONO. In week 12, 5 passes will be lost due to 20m antenna maintenance, 1 pass due to HALCA, and 5 passes due to AKEBONO. The antenna maintenance will last three weeks (W12 - W14). 7. Hikitsugi Items 7.1 Tohbans for week 12 SSOC : Akita KSC : Kubo, Shinoda 7.2 OP and Command Sheets for Monday The OP and Command Sheets for Monday have been sent to KSC. The approved OP has also been transferred to KSC. However, we have to wait for the recovery of the transmitter. 7.3 STT timer setting STT timer setting is due on 16 March, Monday. 7.4 Holiday Schedule The next holiday will be on 23 March, Monday. ===================================================================== || The following is the same as the previous week's report. || ===================================================================== 8.1 DSN scheduling From this year, Wallops schedules DSN passes, instead of JPL. The system to communicate with Wallops is still under construction. For details, see README in the subdirectory "wallops" in flare20. All DSN-related software should be run from an IDL session in this directory. 8.2 Bug in op_first_guess (Quoted from the previous week's report) SSOC tohbans should be aware of a bug in op_first_guess: "% OP_START_END: Problem with detection of LOS/AOS/DSN Repro Events" appears when we have close enough contacts (more than two downlinks in an orbit). We avoided the problem, when using op_first_guess, by responding to "Change any standard op_first_guess options?" by choosing yes, then in response to "Enter BDR optimization (1 or 2), by choosing 1. 8.3 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 tenth of the normal capacity. As far as we know this error has not been recovered yet. Please note the special commands now routinely appearing in the command sheets. This is part of the recovery attempt. 8.4 E-mail communications (Quoted from the previous week's report) 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. 8.5 Long Range Schedule Arrangement (W49-1997) Since the launch of HALCA, the KSC tracking facilities have been running in operation nearly twenty four hours a day. No time has been available yet for maintenance this year. NEC and MELCO are planning to reserve a pair of two- week periods for maintenance with both of these two-week intervals occurring before the end of March 1998. The work requires six consecutive hours each day. Candidate periods; 17-31 of January and 16-31 of March, During these periods, we will perhaps lose one contact per day at KSC. Also, Planet-B will be launched next summer. In spite of the fact that Planet-B is a Japanese mission, it will be launched during summertime; its launch window starts July 4, 1998 for the mission to Mars. During the flight operation (lasting for the 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 scheduling during the Planet-B flight operation interval will be negotiated among the five teams namely: AKEBONO, YOHKOH, ASCA, HALCA and Planet-B (in March, perhaps). Tetsuya WATANABE (NAOJ) 8.6 New database (W10-1998) R. Bentley and S. Freeland have apparently finished installing a new and very convenient database in the Yohkoh system. It is "orb" and one gets orbit data from it via IDL> rd_orb, t1, t2, orb IDL> utplot,orb,orb.height,/ynoz ; for example Now at last we know where the satellite was at all times! (Hudson) 9. Action Items (Same as last week's SSOC Report) 9.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. 9.2 Week-48-A/I-1 /Hudson/status AJAR. Hudson has fixed print_ogsel (Week 48). Upon editing the OG's, this command from IDL will print the edited OG item on the workstation printer in B-toh. 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. 9.3 Week-10-A/I-1 /Hudson, Lemen/status OPEN DSN_CONFLICT does not work with the new Wallops files. It needs fixing before the next conflict season starts (perhaps in May?). 9.4 New database R. Bentley and S. Freeland have apparently finished installing a new and very convenient database in the Yohkoh system. It is "orb" and one gets orbit data from it via IDL> rd_orb, t1, t2, orb IDL> utplot,orb,orb.height,/ynoz ; for example Now at last we know where the satellite was at all times! -- end of report -----------------------------------------------------------