SSOC Tohban Report for Week 02 (04-Jan-2000 to 08-Jan-2000) SSOC: H. Hara, M. Nishio KSC: Te. Watanabe, M. Shimojo 0. Meeting Attendees No meeting held ------------------------------------------------------------------------------- 1. Solar Activity Solar activity was in sub-C levels, though few C-class flares were recorded. ------------------------------------------------------------------------------- 2. Standard Operations 2.1 SXT Table Uploads The following SXT tables were uploaded: ================================================================ JST Day UT Start Time Pass Table ID ================================================================ Wednesday AM 04-JAN-2000 17:18 3 000104 P3 ARS1 DKCAL Friday AM 06-JAN-2000 17:43 3 000106 P3 ARS1 DKCAL Saturday AM 07-JAN-2000 12:48 1 000107 P1 ARS1 DIFF Sunday AM 08-JAN-2000 14:48 2 000108 P2 ARS1 STD ================================================================ 2.2 STT Timer setting STT timer was re-set during Pass 2, 000104-1032, on 04-Jan-2000 (UT). STT Times was stopped during Pass 4, 000107-1136, on 07-Jan-2000 (UT). ------------------------------------------------------------------------------- 3. Special Operations 3.1 Test uplink for Y2K problem analysis was done durling Pass 1, 000103-0929, on 03-Jan-2000 (UT). 3.2 HXT Calibration HXL CAL operations were done during Pass 1, 000105-0929, on 04-Jan-2000(UT), Pass 3, 000105-1136, on 05-Jan-2000(UT), and Pass 1, 000106-1136, on 06-Jan-2000(UT). After these operations, HXT FINE GAIN ADJUST was done durling Pass 4, 000107-1136, on 07-Jan-2000(UT). ------------------------------------------------------------------------------- 4. Errors and Problems 4.1 BCS Errors: None 4.2 SXT Errors: Several operational problems were reported by SXT chief observer (SXT_CO) and they were, at first, regarded as problems of a ground support software (SXTSPT) for SXT table change. Hara investigated cause of the problems. It was found that they would be due to misoperations by SXT chief observer. A problem associated with the so-called 'compare list' (old compare list was registered as a new one to a file in flare1) was caused by abnormal order of job executions by SXT_CO. This will be improved by modifying SXTSPT, not to cause the same mistake. 4.3 Report of Y2K problems I. KSC (S3500) No Y2K problems were reported for S3500. II. ISAS (1) DL function of SAQL (Mainframe: GS8310) Delay Look (DL) software did not work on 3 Jan. It was due to a trivial bug in the SAQL software. It was fixed on 4 Jan. (2) SIRIUS Access with flare1 The first byte data of SIRIUS data in the sub-frame are replaced by SRSGET working in flare1 for Yohkoh reformat database. It includes a Y2K problem. This was resolved on 27 Dec with help of Shuto san and Slater. SIRIUS access with SRSGET for data obtained after 1 Jan 2000 could not be done until Wednesday. It works now. But SIRIUS access programs are still being updated, so the current version of SIRIUS softwares is tentative. (3) SAOCS software A software for STT timer set did not work on 4 Jan. Orbit determination/ orbit operation support softwares called 'SAOCS' had been replaced for Y2K problem, but the module for execution was not replaced from old to new one last year. The problem was fixed after its replacement. (4) Orbital elements Orbital elements for next week operation were manually input to SIRIUS data base. It is uncertain if an automatic registration of the orbital elements to SIRIUS datadase can be done now. Transfer of orbital elements from the mainframe to isass0 and sending e-mail to DSN are both OK. (5) OP-OG editor There was a Y2K problem in the OP-OG editor. In case of 4-Jan-2000, input like '000104' at the first line in the OP was rejected. In the original FORTRAN code, years between 1991 and 1999 were only accepted. The FORTRAN code of OPOGEDT was corrected on 4-Jan-2000. There has been no problem since then. (6) SXT QL softwares Recompilation of SXT QL (SXTQLCC) for SIRIUS access has been finished on 8 Jan. III. Solar soft Yohkoh softwares (1) OP_FIRST_GUESS.PRO A minor Y2K problem was found in the command sheet. '19' characters for '19XX' appeared in the top area of command sheet. This has not been fixed yet. (2) DSN_CONFLICT.PRO DSN_CONFLICT.PRO did not correctly work on 7 Jan. The cause of this problem was lack of ASCA FEM files. It has bcome to work since 7 Jan. (3) SXT TBL softwares In the reformat databese there are SXT table data that were used for SXT operation. SXT tables used after 2000 were not read with solar soft. ------------------------------------------------------------------------------- 5. NASA Station Scheduling 5.1 Contact pass cancellations/additions The following DSN/NASA passes were added/deleted: =========================================================================== DSN/NASA Schedule Week Schedule Changes =========================================================================== Final 02 4 Cancellations by SSOC Final 03 13 Cancellations by SSOC Preliminary 04 4 Cancellations by SSOC Strawman 05 49 Cancellations by SSOC =========================================================================== 5.2 Data Transmission from NASA Ground Stations ----(to be copied from /home/flare1/yohkoh/dsn_corrupt/2000/00_02)---- 353 46 1032 not received requested 21-Dec Closed/ correct data(22-Dec) 354 46 1045 missing data requested 21-Dec Closed/ same data(22-Dec) 359 82 1047 corrupted tape requested 28-Dec Closed/ same data(29-Dec) 362 74 1823-1832: 14946 blocks Only 14946 blocks received due to antenna in keyhole from AOS to 182700. 363 82 1317 not received requested 05-Jan ------------------------------------------------------------------------------- 6. KSC Pass Conflicts and Schedule In Week 03, 14 KSC contacts will be lost, 4 for ASCA, 4 for HALCA, and 6 for AKEBONO. ------------------------------------------------------------------------------- 7. Hikitsugi Items 7.1 Tohbans for next Week SSOC: K. Nakakubo(ex14,17), K. Ichimoto(ex17) KSC: M. Shimojo, T. Yamasaki 7.2 STT Timer Setting The next STT TIMER SET is due on Wednsday '12-Jan-2000 (UT)'. 7.3 OP OP for 10 Jan starting in the evening has already been prepared by W02 SSOC tobans. 7.4 ASTRO-E launch operation at KSC ASTRO-E will be launched in February. Some operation for preparation of ASTRO-E launch may happen within two months. Please be careful. ------------------------------------------------------------------------------- 8. Unchanged Hikitsugi Items from Last Week 8.1 Elevation angle limit at Santiago (w49) Seko_san noticed two fault reports from Santiago (DSS-74) due to low elevation at the end of the pass: These were shown as max elevations of 11.1 degrees (323/1322) and 10.7 degrees (315/1645) in our database. Accordingly, after consultation with Watanabe-san, we suggest increasing the threshold (for this station only) to 13.5 degrees maximum elevation. 8.2 Weekend Terminators If possible, please schedule terminator opportunities on any weekend table (i.e., if room permits). 8.3 Keeping Santiago contacts Currently, ASCA conflicts cause the loss of about 10 KSC contacts per week. We do not know which contacts Yohkoh will lose until the weekly meeting. Santiago contacts occur on the same orbits as KSC contacts. Therefore, please keep as many Santiago contacts as possible in the DSN Strawman and Preliminary Forecasts. 8.4 OP and Real-time Command Glossary We need a shorthand glossary for common OP and command-sheet commands. This already exists pretty much in the Sakao-san manual in Japanese, and the Week 26 tohbans started accumulating an English version on "yohkoh.glossary" 8.5 Software Problems pr_gev with /hc keyword produces a temporary output file but does not print it at the printer. 8.6 OP_FIRST_GUESS problem (1999-w38) In a situation with two KSC cancellations on each of two days (a rare condition) the BDR optimization feature of OP_FIRST_GUESS crashed. After experimentation, we found that it ran OK without the final cancellation request (two the first day, but just the first one on the second day). The second one then had to be removed manually. Records of the problem were forwarded to Lemen-san, but no answer had arrived at the time of writing. 8.7 Keeping Wallops contacts (1999-w42) This is not a new policy, but to emphasize (paraphrased from e-mail from Hugh Hudson): We should keep all valid Wallops passes, independent of day/night status, in order to maximize our Wallops use and minimize our DSN use. NASA won't give us many DSN passes anyway, so if we select a Goldstone pass in preference to a Wallops one, we'll normally just lose both. Another reason is that CANCEL_DSN software needs some repair, since it seems to replace the DSS identifier WGS with 0. This is likely to cause confusion, but of course if we don't cancel Wallops passes we won't have this problem often. 8.8 OP_FIRST_GUESS problem (1999-w42) In one instance, op_first_guess produced a nested RB HV RDCT ON/ RB HV RDCT OFF sequence (i.e. ON-ON-OFF-OFF). This problem is easily spotted, and corrected by deleting the second ON command and the first OFF command manually. The bug has been reported to J. Lemen. 8.9 Tohban Manual (1999-w42) The English-language version of the Tohban Manual has been updated recently and should be considered authoritative. The corresponding checksheet is also new (August 1999). 8.10 A New Antenna System in Wallops (1999-w43) Since October 1, a new antenna GN-WGS is used instead of a 9m antenna DSS-76 in Wallops station. SSOC tohbans should not be surprised at the unfamiliar antenna code GN-WGS in the DSN schedules. This new code GN-WGS is replaced with DSS-80 in solass.w## and solsf.w## by the program "fmt_wallops". But some programs for the strawman scheduling replace it with DSS-0. 8.11 OP_FIRST_GUESS Problem (1999-w46) OP_FIRST_GUESS printed "Night" instead of "Day" (as it should have printed) on pass sheets for 1999/11/15 Pass 5(991115-1341). 8.12 OP_FIRST_GUESS Problem (1999-w46) During the preparation of the 991115-1031 OP, OP_FIRST_GUESS inserted a QUIET RATE HIGH command during an SAA passage at a time when about 20 minutes of daylight remained. The maximum duration of QUIET RATE HIGH mode during an SAA in daylight should be 10 minutes. 8.13 OP_FIRST_GUESS Problem (1999-w46) During the preparation of 991109-1238 OP,991110-1135 OP and 991111-1032 OP OP_FIRST_GUESS crashed with the message "OP_START_END: problem with detection of LOS/AOS/DSN Repro events". This problem was solved by changing OP_FIRST_GUESS options: choose optimization 1 rather than 2. All these 3 problems above (item 8.10, 8.11 and 8.12) occurred also on week 45 in 1999. === END ===