SSOC Tohban Report for Week 20 (08-May-2000 to 14-May-2000) SSOC: K. Matsuzaki KSC: S. Morita, S. Nagata 0. Meeting Attendees Ogawara, Hudson, Khan, Slater, Handy, Watanabe, Hanaoka, Sakao, Matsuzaki ------------------------------------------------------------------------------- 1. Solar Activity At the begining of this week, the sun was quiet. Rigion rising from south east edge is active and there was six C8-M1 class flare from Wednesday to Saturday. The soft X-ray (GOES) background level of this week has rising from B3 at the begining to about class C2 at the weekend. ------------------------------------------------------------------------------- 2. Standard Operations 2.1 SXT Table Uploads The following SXT tables were uploaded: ====================================================================== JST Day UT Start Time Pass Table ID ====================================================================== Monday PM 08-May-00 02:50 1 000508 P1 ARS1 DKCAL Monday PM 08-May-00 07:56 4 000508 P4 ARS0 JOP122 Tuesday PM 09-MAY-00 06:23 3 000509 P3 ARS1 DIF Wednesday PM 10-MAY-00 01:27 1 000510 P1 ARS1 RAPID Thursday PM 11-MAY-00 03:18 2 000511 P2 ARS1 RAPID Friday PM 12-MAY-00 05:09 3 000512 P3 ARS1 RAPID Saturday PM 13-MAY-00 05:19 4 000513 P4 ARS1 STD ====================================================================== 2.2 STT Timer setting After shutdown of the stt timer in the last week, the STT timer was set in Pass 1 on Tuesday, Pass ID: 000509-0206. The next timer setting should be done on 16-MAY-2000 (Tuesday). ------------------------------------------------------------------------------- 3. Special Operations 3.1 Pointing change Normal pointing was modified into W1.69 N1.15 at pass 1 of 11 May (Wednesday). 3.2 Threshold modification Following the solar activity, a flare flag threshold (SXS-NFL) has changed from C6-7 to C2-3 in pass 1 of 9 May (Tuesday) and has recovered to the original value in pass 4 of 11 May (Thursday). ------------------------------------------------------------------------------- 4. Errors and Problems 4.1 From week 20, we have no longer Santiago down-link passes. ---------- As far as I know your routine operational support has been discontinued at Santiago. Sorry about any inconvenience this may cause. Regards, Debbie ------------------------------------------------------------------------------- 5. NASA Station Scheduling 5.1 Contact Pass Cancellations/Additions We requested recovery of passes, former canceled by tohban in strawman phase, for final and forcast schedule. The following schedule changes were requested (approved): =========================================================================== DSN/NASA Schedule Week Schedule Changes =========================================================================== Final 20 0(0) additions Final 21 17(3) additions Forecast 22 7(2) additions Strawman 23 47 cancellations =========================================================================== Numbers of DSN contacts in final schedule are w17 37 / w18 46 / w19 36 / w20 36 / w21 31. 5.2 Data Transmission from NASA Ground Stations ----(Copied from /home/flare1/yohkoh/dsn_corrupt/2000/00_20)---- 113 76 0418 corrupted tape requested 26-Apr no response tape requested 08-May no response tape requested 10-May 120 82 2245 corrupted tape requested 10-May Closed/ correct data 121 82 0210 corrupted tape requested 10-May Closed/ correct data 121 82 0353 corrupted tape requested 10-May Closed/ correct data 121 82 1933 corrupted tape requested 10-May Closed/ correct data 121 76 2255 corrupted tape requested 10-May Closed/ correct data 122 82 0220 corrupted tape requested 10-May Closed/ correct data 123 82 2314 corrupted tape requested 10-May Closed/ correct data 116 66 2042 not received reqeusted 08-May Closed/ No Data Unable to process any telemetry data. RF signal from TLM RCVR'S appeared very noisy. Neither TGC channel was able to lock on TLM. Tried different MFR'S. TLM sidebands were observed in the spectrum analyzer. Bad RF performance suspected (LNA-1 in use). ** The following data were canceled by SSOC toban for w18. 121 82 0027 - 0041 No data 122 82 0037 - 0051 No data 122 66 2139 - 2149 8748 blocks TGC failed outputing data blocks on both CHN's after aos. 130 46 1144 - 1154 10519 blocks Telemetry dump was already on at horizon break. Predicted AOS 4.22 deg, maximum elevation was 7.23 deg and set was 7.62 deg. ------------------------------------------------------------------------------- 6. KSC Pass Conflicts and Schedule In Week 20, Yohkoh lost 5 passes to ASCA and 1 to Akebono. In Week 21, Yohkoh will lose 6 passes to ASCA. ------------------------------------------------------------------------------- 7. Hikitsugi Items 7.1 Tohbans for Next Week SSOC: Khan, Hanaoka KSC: Nagata (16>SSOC), Hagino 7.2 STT Timer Setting The next STT TIMER SET is due on Tuesday, 16-MAY-2000 (JST). 7.3 OP OP and command sheets for Monday, 15-May-00 has already been sent to KSC. 7.4 Holiday Schedule Next Yohkoh holiday will be Sunday, 21-May-00 (UT). 7.5 Meeting for long-term scheduling among Halca, Asca, and Yohkoh will be held in May. 7.6 Testing of 34m antena @ KSC will be held on 21-24 May. ------------------------------------------------------------------------------ 8. Unchanged Hikitsugi Items from Previous Weeks: 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. SSOC Tohban for w09 asked Hudson-san to prepare an azimuth-elevation map in Santiago station. 8.2 Weekend Terminators If possible, please schedule terminator opportunities on any weekend table (i.e., if room permits). 8.3 Software Problems PR_GEV with /hc keyword produces a temporary output file but does not print it at the printer. 8.4 OP_FIRST_GUESS Problem (1999-w38, 1999-w45) 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.6 Keeping Wallops Contacts (1999-w42, 1999-w45) 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.7 OP_FIRST_GUESS Problem (1999-w46, 1999-w45) 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. 8.8 DSN Pass Additions (2000-w19) Yohkoh loses DSN passes as follows: 1) Canceled due to conflicts with ASCA 2) Canceled because Santiago is unavailable 3) Canceled by the SSOC Tohbans 4) Deleted by DSN The Tohbans SHOULD COMPARE the STRAWMAN, PRELIMINARY and FINAL schedules -------------- for each week to see if some of the passes lost by case (4) could be replaced by ones from case (3). This means it may be possible to request pass additions for the PRELIMINARY and FINAL week schedules from the (case (3)) STRAWMAN cancellations. The routine to use is ADD_DSN: e.g., IDL> ADD_DSN, 49 Decide on the complete list of passes to be added and select them like CANCEL_DSN. Then ftp and email the appropriate file. ------------------------------------------------------------------------------