SSOC Tohban Report for Week 30, 1996 (22 July - 28 July) SSOC: Y.Nakagawa and S.Masuda KSC: S.Akiyama and J.Koyama 0. Meeting Attendance ---------------- H.Hudson J.Khan S.Masuda Y.Nakagawa Y.Ogawara M.Ohyama S.Savy M.Sawa T.Shimizu A.Sterling T.Watanabe 1. Solar Activity ---------------- The activity was generally low. However, an active region appeared from the east limb on July 25. GOES base-level was gradually increasing to the B-class level. 2. Standard Operation ---------------- 2.1. SXT Table Uploads ---------------- ---------------------------------------------------------------- Date(JST) Pass Table ID ---------------------------------------------------------------- Thursday 25-July-96 4 960724 P4 ARS2 DKCAL Friday 26-July-96 2 960725 P2 ARS2 STD+DIFF Friday 26-July-96 4 960725 P4 ARS2 STD+LONG Friday 26-July-96 1 960726 P1 ART VLA TEST Saturday 27-July-96 5 960726 P5 ARS1 STD+LONG Saturday 27-July-96 1 960727 P1 ARS1 STD ---------------------------------------------------------------- 2.2. STT timer setting ---------------- The STT timer was set during pass 2 on 24-July-96 JST. 2.3. HXT calibration and gain adjustment ------------ HXT calibration had been done 8 times in this week. They were done in the passes, #960721-1033, #960721-1136, #960722-1030, #960724-0928, #960724-1032, #960724-1135, #960726-0826, and #960727-1033. We planed another HXT calibration on the first pass of 27-July UT, but we canceled this operation because of BCS recovery. It will be done on the second pass today. "HXT gain adjustment" operation was done on the pass #960725-1032. 2.4. BCS calibration ------------ BCS calibrations (Stim Cal and Source Cal) were done in this week. The former was done during the pass#960725-1136. The latter was done by OP from 20:35UT on 25 July. 3. Errors and Problems ---------------- 3.1. Mini-computer (A400) Problem ----- The mini-computer for online data acquisition (A400) is troubled, and it was recovered on Tuesday evening. 3.2. BCS Errors ---------------- There were two errors in this week. First one was detected during the pass#960723-1238, and it was recovered on the next pass #960723-1343. The second one was detected during the pass #960725-1342. KSC tohbans tried to recover this error in the pass#960726-1136, but failed. They tried it again on the pass #960727-0827 and didn't completed it again. This error was successfully recovered in the fourth pass #960727-1137 on the same day, and now BCS is working well. 3.3. SXT Errors ---------------- None. 3.4. SXT Table Read ----------- The SXT table uploaded on the pass#960725-1239 was confirmed only by the MS computer, although we usually make a confirmation both with SXTSPT and the MS computer. KSC Tohban could not log-in the mainframe from the G-150 terminal in KSC because of a network error. It was maybe caused by the mis-selection of the network switch of the G-150 terminal. 3.5. SXT Problem ---------------- In the pass #960727-1137, SXT Table Upload had been canceled and we deleted the command related to this operation in the "command sheet", but we forgot to delete the "SXT CTL MANU" command. Nobody in the KSC doubted this, so in that pass, the "SXT CTL MANU" was executed. The current status of SXT is as follows. the filters A/B are 3/1 and the shutter is open. Because of this operation, SXT has taken no images since that pass. The "SXT CTL AUTO" command should be executed in the first pass today. 3.6. flare5 problem -------------------------- A workstation in KSC, namely flare5, was broken on July 26 (JST). This machine was used to get the SXT data from S-3500. Then KSC tohban could not watch SXT images on that day. On July 27, the GPIB board was set on another workstation (flare4) and KSC tohban connected it to S-3500. Now they can watch SXT images on flare4. The workstation manager will send a workstation from D-tou to KSC in this week. 4. DSN Communications ---------------- 4.1. DSN Final schedule for W30 ---------------- We canceled 3 passes. 4.2. DSN Final schedule for W31 ---------------- 1 pass was canceled. 4.3. DSN Preliminary schedule for W32 ---------------- No passes were canceled. 4.4. DSN Strawman schedule for W33 ---------------- 32 passes were canceled. 4.5 Data Transmission from DSN ---------------- Problems of data transmission from DSN were listed by Katano-san. ------------------- 196 76 0932 4% corrupted. Requested 15 Jul. tape Requested 18 Jul. Closed/tape data is corrupted too. 196 74 2140 not arrived. Requested 19 Jul. Closed/correct 199 16 1528 100% corrupted. Requested 23 Jul. not received tape Requested 26 jul. 200 17 1404 3% corrupted Requested 23 Jul. not received tape Requested 26 jul. 203 76 1145 71% corrupted Requested 23 Jul. Closed/by e-mail confirmation. 203 74 1844 not received Requested 26 jul. 204 76 0655 26% corrupted Requested 23 Jul. Closed/by e-mail confirmation. 204 17 1337 18% corrupted Requested 23 Jul. not received tape Requested 26 jul. 205 76 0857 3% less than expected Requested 26 jul. //// detailed report of retransmission request ****** message received but 3 data not received *************************** I have received your FAX requesting retransmission of YOHKOH data and I will request a second re-transmission of these data. DSS DOY START STOP 16 199 1528 1537 17 200 1404 1413 76 203 1145 1153 76 204 0655 0705 17 204 1337 1346 FYI, DOY/203 and 204 were transmitted once before as the report listed below indicates. SOLAR-A OPERATIONAL PASS REPORT ORBIT NR.7069 1. 21/1145-1153Z (SCHEDULED TRACK TIME) 2. RF AOS : 114600Z 3. DUMP ON : 114657Z 4. DUMP OFF: 115138Z 5. RF LOS : 115200Z 6. ANT: 9METER 7. 21/1454-1532Z (PLAYBACK TIME) 8. BLOCK COUNT 17832 9. REMARKS: TAPE NR.241 FILE NR.003F ************************************************************** ( retransmit data : 5 data ) ### The following data is closed. ### (*Please tell us, if it is inconvenient) 76 203 1145 1153 (71% corrupted) 76 204 0655 0705 (26% corrupted) @@@ The following data is suspended -> Closed(3/4) 175 76 20:02 not received(no data). arrived data / correct 175 76 21:45 not received(no data). arrived data / correct 175 76 23:28 not received(no data). arrived data / correct @@@ The following data is suspended -> not Closed(1/4) ********************************(received the following message) * SOLAR-A OPERATIONAL PASS REPORT ORBIT NR.6675 * * 1. 24/2204-2215Z (SCHEDULED TRACK TIME) * 2. RF AOS : 220400Z * 3. DUMP ON : 220716Z * 4. DUMP OFF: 221244Z * 5. RF LOS : 221300Z * 6. ANT: 9METER * 7. 25/0124-0206Z (PLAYBACK TIME) * 8. BLOCK COUNT 20630 * 9. REMARKS: TAPE NR.233 FILE NR.002 * * GWPS SENDS ******************************************************** but not received data "176 76 22:04 not received(no data)." retransmit this data once more? ---------------------------------------------------------------- 5. Yohkoh/ASCA Pass Conflicts at KSC ---------------- 2 passes in W31 are scheduled to be lost for ASCA. 6. Special Operations ---------------- Coordination with the VLA (Benz) planed on July 27. No special SXT table was uploaded for this campaign because of appearing an active region from the east limb. 7. Holiday Schedule ---------------- The next KSC holiday is 4-Aug-1996. 8. Hikitsugi Items ---------------- 8.1. Tohbans for W31 ---------------- SSOC: Ohyama and Khan KSC: Akiyama and Takahashi 8.2. STT Timer setting ---------------- The next setting should be on 30-July-96 JST. 8.3. Op_first_guess LOS Medium/High Mode. ---------------- The op_first_guess fails switching to the medium mode during the KSC passes in the OP plan when there are canceled passes. Alphonse Sterling sent a note to Jim Lemen about this and the SSOC tohbans suppose Jim is working on this. In the meantime, tohbans should be careful to check the KSC LOS mode in the next day's operations in the OP. 8.4. RASM switched to flare20. ---------------- The RASM script, krasm, now works on flare20, but not flare11. 8.5. Flare1 printer ---------------- The new printer next to the flare1 workstation does not accept plain- text files' printing jobs, but works only for PostScript files. Most of printing jobs from flare20 were resumed to work, but it still needs modification of scripts. Report to the software managers, if you notice any problem. The jobs to printout new DSN schedules automatically don't work correctly. We should do this manually.