Session Notes for CONT17 campaign: c1714 Prepared by D. Behrend, NVI, Inc./GSFC Refer to https://ivscc.gsfc.nasa.gov/program/cont17/ for general information. This set of notes consists of two parts: 1) Individual day notes 2) General CONT17 notes (repeated for all CONT17 days) *** Individual day notes *** =========================================================== ----- Parameter listing -------------------------------------- Experiment: C1714 Description CONT17 DAY 14 Scheduler: NASA Correlator: BONN Start: 2017-345-00:01:17 End: 2017-346-00:00:00 Current yyyyddd: 2017345 (2017.95) ( 18099 MJD, MON. 11DEC.) Greenwich sidereal time: 05:20:53 (00:01:17 UT) Sun's RA and DEC: 17h 12.7m -22d 59.5 =========================================================== First observations Observation listing from file ./c1714.skd for experiment C1714 Source Start DURATIONS name yyddd-hhmmss Bd Ft Ho Ht K1 Ke Kk Ma Ny On Ww Wz Ys Zc 0308-611 17345-000117| 173 240 240 | 0059+581 17345-000315| 24 56 72 46 72 53 72 56 26| 2309+454 17345-000503| 300 226 188 300 242 224 | 0307+380 17345-000511| 137 137| 1732+389 17345-000552| 135 135 | 1954-388 17345-000621| 86 180 180 | ... End of listing. =========================================================== Last observations Observation listing from file ./c1714.skd for experiment C1714 Source Start DURATIONS name yyddd-hhmmss Bd Ft Ho Ht K1 Ke Kk Ma Ny On Ww Wz Ys Zc 0454-234 17345-235453| 27 20 27 23 20 | End of listing. Observation listing from file ./c1714.skd for experiment C1714 Source Start DURATIONS name yyddd-hhmmss Bd Ft Ho Ht K1 Ke Kk Ma Ny On Ww Wz Ys Zc ... 0446+112 17345-235113| 157 157 102 148 49 78 61| 1741-038 17345-235126| 76 157 45 20 157 | 1221+809 17345-235322| 20 33 33 | 0454-234 17345-235453| 27 20 27 23 20 | End of listing. =========================================================== SKED Summary from file ./c1714.skd for experiment C1714 (all scans with at least one subnet station) Average number of obs. per baseline per source(normalized by up-time) = 5.7 Min = 0.0 Max = 205.7 (Baseline Ho-Ys on 2227-088) RMS = 9.0 Total time: 1434 minutes ( 23.9 hours). Key: Bd=BADARY Ft=FORTLEZA Ho=HOBART26 Ht=HART15M K1=KASHIM11 Ke=KATH12M Kk=KOKEE Ma=MATERA Ny=NYALES20 On=ONSALA60 Ww=WARK12M Wz=WETTZELL Ys=YEBES40M Zc=ZELENCHK Bd Ft Ho Ht K1 Ke Kk Ma Ny On Ww Wz Ys Zc Avg % obs. time: 32 40 35 53 44 59 58 55 62 63 57 64 57 34 51 % cal. time: 5 4 5 5 3 4 5 4 5 5 5 6 6 5 5 % slew time: 57 42 55 25 10 14 25 32 23 25 14 15 32 55 31 % idle time: 4 13 4 16 42 22 11 7 9 6 23 14 5 6 13 total # scans: 449 335 463 432 258 367 434 385 441 408 429 514 493 443 417 # scans/hour : 19 14 19 18 11 15 18 16 18 17 18 22 21 19 17 Avg scan (sec): 62 103 65 105 146 137 116 123 122 133 114 107 99 65 106 # data tracks: 32 32 32 32 32 32 32 32 32 32 32 32 32 32 # Mk5 tracks: 32 32 32 32 32 32 32 32 32 32 32 32 32 32 Total TB(M5): 1.8 2.2 1.9 2.9 2.4 3.2 3.2 3.0 3.4 3.5 3.1 3.5 3.1 1.8 2.8 # OF OBSERVATIONS BY BASELINE | Bd Ft Ho Ht K1 Ke Kk Ma Ny On Ww Wz Ys Zc Total -------------------------------------------------------------------------------- Bd| 57 50 109 137 67 109 160 241 195 34 236 204 247 1846 Ft| 10 194 7 0 50 163 97 129 18 159 179 115 1178 Ho| 88 51 235 152 12 16 16 330 13 4 22 999 Ht| 14 72 0 159 122 162 51 188 219 172 1550 K1| 84 91 37 64 45 51 52 47 65 745 Ke| 116 28 39 37 198 33 26 46 981 Kk| 72 157 96 176 108 92 78 1297 Ma| 220 286 2 301 292 240 1972 Ny| 302 14 313 300 263 2148 On| 8 342 318 269 2205 Ww| 3 0 10 895 Wz| 409 333 2490 Ys| 306 2396 Zc| 2166 Number of 2-station scans: 646 Number of 3-station scans: 380 Number of 4-station scans: 168 Number of 5-station scans: 84 Number of 6-station scans: 63 Number of 7-station scans: 104 Number of 8-station scans: 71 Number of 9-station scans: 58 Number of 10-station scans: 12 Number of 11-station scans: 1 Number of 12-station scans: 0 Number of 13-station scans: 0 Number of 14-station scans: 0 Total number of scans: 1587 Total number of obs: 11434 Total integrated obs-time: 999945 Average obs-time: 87.5 Histogram of observation durations Dur: 15 30 45 60 75 90 105 120 135 150 165 180 195 210 225 240 255 270 285 300 #Obs: | 1857| 1443| 1323| 1112| 1062| 958| 889| 729| 556| 370| 296| 180| 135| 145| 84| 89| 44| 41| 121| Average X-band SNRs by baseline | Bd Ft Ho Ht K1 Ke Kk Ma Ny On Ww Wz Ys Zc AVG ------------------------------------------------------------------------------- Bd| 51 81 61 48 52 70 64 106 93 53 151 208 222 119 Ft| 28 47 38 - 34 41 53 56 41 95 145 96 73 Ho| 44 42 53 41 50 49 53 61 88 136 127 56 Ht| 43 39 - 52 63 65 32 117 158 121 83 K1| 41 44 39 48 50 40 77 95 82 53 Ke| 35 41 45 49 48 82 113 90 51 Kk| 39 57 53 41 85 120 109 59 Ma| 67 77 47 141 182 132 99 Ny| 102 41 160 211 171 120 On| 43 190 243 180 131 Ww| 69 - 98 51 Wz| 428 297 209 Ys| 390 255 Zc| 209 Average S-band SNRs by baseline | Bd Ft Ho Ht K1 Ke Kk Ma Ny On Ww Wz Ys Zc AVG ------------------------------------------------------------------------------- Bd| 31 45 53 47 35 70 39 58 46 32 74 56 67 55 Ft| 17 32 22 - 27 19 21 20 18 35 28 22 26 Ho| 34 31 27 38 19 25 20 29 30 22 29 31 Ht| 37 27 - 32 34 33 29 60 48 39 40 K1| 33 48 24 30 25 29 37 26 27 35 Ke| 33 19 22 20 26 29 23 23 27 Kk| 33 43 36 38 54 42 41 42 Ma| 29 29 20 52 37 30 34 Ny| 35 21 55 39 36 40 On| 19 56 40 33 37 Ww| 24 - 23 30 Wz| 71 55 57 Ys| 40 46 Zc| 41 =========================================================== *** General CONT17 notes *** ===================================================================== CONT17 Session Notes November-December, 2017 These are the notes for the Legacy-1 network of CONT17. There are separate notes for the Legacy-2 network (VLBA+ network) and for the VGOS Demonstration network. First session start: November 28, 2017 0:00:00 UT End of last session: December 12, 2017 23:59:59 UT The CONT17 sessions will be observed in UT days, i.e. in sessions of 0-24 UT. UT-day observing yields the most accurate combination and comparison of results from other techniques. The Legacy-2 network will also observe in UT days, while the VGOS Demonstration network is shifted by one hour (for operational constraints at stations with several radio telescopes). UT-day observing is planned to be the operational mode of VGOS once it becomes the production system of the IVS. ===================================================================== Number of 24-hr sessions: 15 Participating stations (14 stations): Badary, Fortaleza, HartRAO (15-m), Hobart (26-m), Kashima (11-m), Katherine, Kokee Park, Matera, Ny Alesund, Onsala (60-ft), Warkworth, Wettzell (20-m), Yebes (40-m), Zelenchukskaya Average number of scans per day: 1,500 Average number of observations per day: 13,500 Total number of scans in campaign: 23,408 Total number of campaign observations: 175,058 ===================================================================== Schedules The sources were selected using the following three criteria: (1) flux values higher or equal to 0.25 Jy in both S- and X-band (August 2017 SKED flux catalog), (2) failure rate in 2017 lower or equal to 20% in both S- and X-band, and (3) structure index (SI) in X-band better than 3 (updated list of SI from Patrick Charlot, Bordeaux Observatory). The selection led to a list of 142 sources. Out of the 142 candidate sources, the best 90 were chosen using sked's BESTSOURCE command. To improve coverage in the southern sky, two southern sources were added manually; their failure rate has been 24% so far in 2017. The final list contains 92 sources. SNR Targets: Minimum SNR for all baselines (except with Kashima): X-band (margin 0): 20 S-band (margin 0): 15 Minimum SNR for baselines with Kashima: X-band (margin 0): 29 S-band (margin 0): 17 ===================================================================== Special Instructions Refer to the schedule summary at the end of the file for the overall schedule of sessions. One or two session days will be recorded onto one disk module. Session days may be grouped together for sharing modules creating the following recording groups (stations physically shipping their modules are asked not to change the recording groups, e-transfer stations may or may not follow the recording groups). Recording groups for all stations: C1701 ==> ---+ C1702,C1703 ==> | C1704,C1705 ==> | C1706,C1707 ==> +---> Ship your modules or C1708,C1709 ==> +---> e-transfer your data C1710 ==> +---> to the Bonn Correlator C1711,C1712 ==> | C1713,C1714 ==> | C1715 ==> ---+ All CONT17 sessions will be correlated at the Bonn Correlator. This includes also the R4-equivalents. The data transport to the correlator will be done either by physical shipment of modules or by electronic transfer of data (e-transfer). The following stations will ship their recording modules to the Bonn Correlator: Kokee Park and Matera. Fortaleza will ship the recording groups C1701, (C1702 & C1703), (C1706 & C1707), C1710, and (C1713 & C1714) to the Washington Correlator and the the other four recording groups to the Bonn Correlator. All other stations will e-transfer their data to the Bonn Correlator. CABLE CAL CHECK: A cable check should be performed before the start of the first session and after the end of the last session. Stations should NOT do any cable cal checks (or anything else that might interrupt the 5 MHz to the antenna unit) between sessions. SYSTEM CHECKS: There are no system checks planned for the duration of the CONT17 campaign. The stations are asked to check out their systems prior to the start of the first campaign day. If a system problem develops during the observation of CONT17, station staff should take corrective measures if possible. This can involve leaving the observation of CONT17 for the repair and a subsequent reentry. Please keep the Coordinating Center abreast of any such occurrences. The Intensive sessions IVS-INT1, IVS-INT2, and RuI have precedence over CONT17 observing (no IVS-INT3 will be observed during CONT17). The four stations that observe in the Intensive sessions (Kokee Park and Wettzell for the IVS-INT1 and IVS-INT2, Badary and Zelenchukskaya for the RuI sessions) have scheduled gaps in the CONT17 observing schedules; these gaps are one hour plus a padding at either end for schedule switchovers of 15-min (Kokee Park, Wettzell) and 10-min (Badary, Zelenchukskaya), respectively. The "Intensive stations" were scheduled in tag-along mode during their Intensive periods and should rejoin as soon as practical after their Intensive sessions. Before rejoining please consider the slewing time from the antenna's current position to the next scan, including which cable wrap the antenna should be on. You may need to pick a slightly later scan in order to have enough slewing time and reach the correct cable wrap. A suggested technique for breaking away from the schedule for any reason (e.g., Intensive observing, necessary repair work) is to use the "halt" command to stop the schedule to then begin the other activity. The "halt" should be executed while not recording. Alternatively, issue an "disk_record=off" immediately after the "halt". Once the other activity is completed and the scan to rejoin the schedule has been determined, a suggested way to rejoin is to use the following command: schedule=session,#line where "session" is the name of the .snp schedule file and "line" is the line number for the scan shown in the schedule listing. MODULE SHIPPING: The modules can be sent as soon as no further recording is planned on them. This can be at the end of a single session (C1701, C1710, C1715) or at the end of a set of sessions (recording group). Stations should label the modules to indicate which session(s) the modules contain. The R-type sessions will be processed within the nominal 15 day time delay for the rapid sessions. These sessions require that the modules be shipped to the correlator expeditiously. Rapid sessions are C1701, C1703, C1707, C1710, and C1714. E-TRANSFER: The data of the R-type sessions need to be transferred as soon as possible and all rapid sessions (C1701, C1703, C1707, C1710, and C1714) are to be transferred before any of the other sessions. The Bonn Correlator has a limited bandwidth for e-transfers (1 Gbps). Hence, e-transfer rates are limited for each station to around 100 Mbps. The transfer of a single session will thus take up to three full days per station. The Bonn Correlator might be able to increase bandwidth for CONT17 for a limited time. The e-transfer stations should consult with the Bonn Correlator on organizing the e-transfers. MIDOB: Each station should verify that their MIDOB procedure completes in 20 seconds or less. The minimum scan length is 20 seconds. MARK 5B OPERATIONS: Stations using Mark 5B recorders should be aware that they should not automatically re-sync the 5B if they receive the error message: ?ERROR sc -24 setcl: Mark 5B syncerr_gt_3, use fmset 's' option to fix. This error message is poorly worded. Newer FS versions have the message (some intermediate versions have "using" misspelled): ?ERROR sc -24 setcl: Mark 5B syncerr_gt_3, CONSIDER using fmset 's' option to fix. You should not use fmset to re-sync the Mark 5B unless fmout-gps is greater than +/- 500 milliseconds. If you do a re-sync, please be sure the time is correct as well. In other cases, you should not reset the Mark 5B time unless it is off by more than +/- 5 seconds (as shown by setcl in units of 0.01 seconds). For the station using a DBBC (in particular AuScope stations), if the fmout-gps starts to change continuously, it may be worthwhile to reset the DBBC (and re-sync and set the time in the 5B with fmset), if that will stop the continuous changing. B2A PROBLEM: Please be aware that for some Mark 5 recorders it is not possible to record a module in bank A if it has already been recorded on in bank B. There should not normally be a need to move a module from one bank to another. However, if it does, please be aware of this restriction. KEY SWITCH ISSUE: We would like to remind all stations to not touch the Mark 5 while it is recording. If you turn a key switch while recording, even for the inactive bank, you will probably corrupt the data on the active disk pack. Additionally, if the key for the inactive bank is turned to locked, the Mark 5 will not respond to some commands from the FS for 20 seconds or more. Please turn the key to "unlocked" only when not recording. Please turn the key to "locked" only when the Mark 5 is not recording and the FS will be idle for at least 20 seconds. If you have any questions about this, please contact Ed Himwich (Ed.Himwich@nasa.gov). LOG FILES: Log files should be ftp'd to an IVS Data Center every day, following the end of each session. This will ensure the logs are available for the correlator to set up for pre-passing and for processing the rapid sessions. It will also let the status of each station be checked. Automatic scripts process the logs each night, the summary files and plots are posted on the session web page, and the session performance matrix is updated. STARTING SCHEDULES: For the first schedule you will need to make sure that you start it early enough to reach the first source. Please check to make sure you go to the right cable wrap for this scan. If your antenna interface does not support the "cable wrap" parameter for the "source=..." you may need to force the antenna to the right wrap manually. Of course changing the wrap will require additional time if it is needed. The cable wrap needed can be found in the DRUDG listing (for example the one from option 5) or from the "source=..." command in the .snp file. Starting with the second schedule we have allowed enough time to slew to the new source from the last source in the previous schedule if the schedule is started by 0000 UT. The cable wrap should be handled correctly without taking special action if this rule is followed. In order to get as much data, and with as few gaps, as possible, we have allowed a minimum of only three minutes for changes between schedules. In other words, at a schedule transition the old schedule will end recording by 23:57:00 UT and the operator needs to start the new schedule before 00:00:00 UT. This is a short time, but we think it should be sufficient. For stations with Mark 5 recorders we think that at most two operator actions should be needed for a schedule transition. The first action is that between some schedules it may be necessary to change the recording bank with a "mk5=bank_set=inc;" command and then wait up to 20 seconds for the recorder to settle for the "Selected" LED to come on. The second is that every schedule transition will require the new schedule to be started with a "schedule=..." command. The "bank_set" command should require less than 30 seconds for the operator to enter and 20 seconds or so for the Mark5 to complete since the module can already be inserted. The "schedule=..." command should require 30 seconds or less to enter. This still leaves an additional minute and a half or so in case an old module must be removed and a new one inserted and selected and/or there are minor problems. In case of a more serious problem, please rejoin the schedule as soon as possible. Since we are not expecting many problems, we didn't want to allow a lot of extra time to handle them, but we recognize that they may happen. Once the schedule has started, you will need to quickly enter a "mk5relink" to continue the schedule after the "halt" in "ready_disk". Assuming that there is no need to insert a module, it is possible to automate the transition for Mark 5 stations. The cable wrap information is carried forward between consecutive schedules to make this possible. There are many possible ways to automate this. One is to place a procedure, perhaps called "change", in the "station" procedure library with contents similar to: "uncomment next two lines if a bank change is needed "mk5=bank_set=inc;" "!+30s schedule=c17nnxx,#1 where "nn" is the schedule number and "xx" is the station's two letter code. Before the schedule change time, the operator would enter a time schedule command such as: change@2017.ddd.23:58:00 where "ddd" is the day number. The contents of "change" would need to be modified for each transition, changing the schedule name and possible commenting/uncommenting the "mk5=..." and "!+30s" commands as appropriate. You will also need to comment out the "halt" in your "ready_disk" procedure. This approach has *NOT* been tested, but we expect it to work. If you want to use this approach, it can easily be tested before use and/or should be monitored the first time it is used. Other schemes are possible as well. READY, START, and STOP messages: Stations are requested to slightly modify their normal procedures for sending READY, START, and STOP messages. Please send the normal READY and START messages for the first experiment and the normal STOP message after the last experiment. Due to the quick transitions between schedules, the procedure for the other messages should be modified to make them reasonable. A suggested scheme would be to send the STOP message as soon as convenient after the start of the next schedule. The START message for the new schedule can be sent as soon as convenient after that. If you normally use "msg" to send your READY, START, and STOP messages, you probably still can. However, for the second and following schedules the following changes are recommended: (1) For the STOP message, please be sure the correct (previous) session name is shown and enter disk inventory only for CONT17 modules. Any problems should be summarized in the "comments" text box. Please be sure to include information about any problems with disk modules requiring use of a spare. (As a reminder, please be sure to send a timely message about any disk module problem to ivscc@lists.nasa.gov when the incident happens. The sooner the Coordinating Center is informed of a problem, the better the chance that a useful response will be possible.) (2) After sending the previous schedule's end message, select the START message form manually and enter the required information. Please verify that the name of the session is correct. If you have the name and time for the first source that was observed, please enter it. Otherwise, you can use 0000 as the time and "source" as the name of the source. MARK5 MODULE PREPARATION: Please prepare all modules you will use for CONT17, including spares, before the session begins. It is strongly recommended that all modules be conditioned after shipping and before recording. Whether a module has been locally conditioned or not, it is *necessary* to perform the so-called "FS Checks" procedure for *every* module and to perform it using the Mark 5 it will be recorded in. If you have any questions, please contact Ed Himwich (Ed.Himwich@nasa.gov). Please monitor the first "scan_check" after a change of module, particularly at schedule transition, to make sure the new module is working. If not, please change to a spare module and rejoin the schedule as soon as possible. Please set the bad module aside, inform the Coordinating Center (ivscc@lists.nasa.gov) and only try to re-use it if you have otherwise run out of media towards the end of CONT17. ===================================================================== Table 1: CONT17 Observing Plan Summary Day Code Start End Correlator Rapid --- ----- ---------- ---------- ---------- ----- Mon system check cable check Tue C1701 332-000000 332-235700 Bonn *R1* Wed C1702 333-000000 333-235700 Bonn Thu C1703 334-000000 334-235700 Bonn *R4* Fri C1704 335-000000 335-235700 Bonn Sat C1705 336-000000 336-235700 Bonn Sun C1706 337-000000 337-235700 Bonn Mon C1707 338-000000 338-235700 Bonn *R1* Tue C1708 339-000000 339-235700 Bonn Wed C1709 340-000000 340-235700 Bonn Thu C1710 341-000000 341-235700 Bonn *R4* Fri C1711 342-000000 342-235700 Bonn Sat C1712 343-000000 343-235700 Bonn Sun C1713 344-000000 344-235700 Bonn Mon C1714 345-000000 345-235700 Bonn *R1* Tue C1715 346-000000 346-235959 Bonn Wed cable check Notes for stations: - Do NOT do any cable checks other than the two checks shown. - Each schedule will end no later than the listed "End" time. - When schedule days change, enough time has been allowed to slew from the last source of the old schedule to the first source of the new schedule assuming the new schedule is started by 0000 UT. The actual first observation can be up to a few minutes after the nominal start. - Shipping stations must send modules for the "Rapid" sessions express to the correlator, as usual. e-transfer stations need to transfer the data of all "Rapid" sessions first; non-"Rapid" sessions shall be e-transferred after all "Rapid" sessions are completed. The correlator is Bonn for all sessions. - e-transfer stations need to keep all modules onto which CONT17 data were recorded until the Bonn Correlator gives the go-ahead to re-use these modules for other sessions. This could take several months. - Stations should label the disk modules with DRUDG printed labels to show which CONT17 session days are recorded on them. - Stations should confirm all initiated shipments to the correlators. - There were no system checks scheduled for the duration of CONT17. A system check should be performed prior to the start of CONT17. - The observation of the Int1, Int2, Ru-I Intensives will continue during CONT17. There will be no Int3 Intensive. The slots for Intensive observing plus changeover time are 90 min for the Int1 and Int2, and 80 min for the Ru-I Intensives. The stations Bd, Kk, Wz, and Zc will leave the CONT17 schedule 15 min (Kk and Wz) and 10 min (Bd and Zc) before the actual Intensive start. The same buffer periods are added after the end of the Intensives. As the stations are added in tag-along mode for the padded Intensive period, the stations can re-join as soon as they are ready after the Intensive. Please consider the cable wrap when re-entering. - If necessary, it should be possible to automate the change in schedules. If you want to do this and want advice, see above or please contact Ed Himwich (Ed.Himwich@nasa.gov). Notes for the correlator (BONN): - A disk module may contain data of one or two observation days. The disk modules have labels according to the sessions being recorded. - The Int1, Int2, and Ru-I Intensive sessions will be observed during CONT17. There are no Int3 Intensive sessions scheduled. The correlation of the Int1, Int2, and Ru-I sessions will be done at the Washington, Tsukuba, and IAA correlators; the shipment of the data for the Intensive sessions has precedence over CONT17. - Five of the 15 CONT17 days are considered rapid turn-around sessions. These R1 and R4 equivalents are to be correlated first. The equivalents are: C1701 = R1, C1703 = R4, C1707 = R1, C1710 = R4, C1714 = R1. - The accumulation period (AP) should be set to 1 sec. ============================================================================== Table 2: Recording Groups and Module Usage Summary: ============================================================================ Bd Ft Ho Ht K1 Ke Kk Ma Ny On Ww Wz Ys Zc ============================================================================ C1701 1.6 2.1 1.8 2.9 2.9 3.3 3.3 3.2 3.4 3.5 3.2 3.5 3.2 1.9 -------------------------------------------------------------------- D G D G G G G G G G G G G D ============================================================================ C1702 1.9 2.2 2.0 3.2 2.4 3.2 3.3 3.1 3.4 3.5 3.2 3.5 3.1 1.9 C1703 1.8 2.1 2.1 3.1 2.5 3.3 3.2 3.0 3.4 3.5 3.2 3.5 3.0 1.9 -------------------------------------------------------------------- 3.7 4.3 4.1 6.3 4.9 6.5 6.5 6.1 6.8 7.0 6.4 7.0 6.1 3.8 G H H J H J J J J J J J J G ============================================================================ C1704 1.7 2.2 2.1 3.0 2.4 3.3 3.3 3.1 3.4 3.5 3.1 3.5 3.1 1.8 C1705 1.8 2.1 2.0 3.0 2.4 3.4 3.2 3.1 3.4 3.5 3.3 3.6 3.1 1.9 -------------------------------------------------------------------- 3.5 4.3 4.1 6.0 4.8 6.7 6.5 6.2 6.8 7.0 6.4 7.1 6.2 3.7 G H H J H J J J J J J J J G ============================================================================ C1706 1.8 2.1 2.0 3.1 2.3 3.5 3.3 3.0 3.4 3.6 3.3 3.6 3.1 1.9 C1707 1.7 2.2 2.0 3.0 2.4 3.3 3.2 3.1 3.4 3.5 3.2 3.5 3.0 1.8 -------------------------------------------------------------------- 3.5 4.3 4.0 6.1 4.7 6.8 6.5 6.1 6.8 7.1 6.5 7.1 6.1 3.7 G H H J H J J J J J J J J G ============================================================================ C1708 1.9 2.1 2.0 3.1 2.3 3.2 3.1 3.1 3.4 3.5 3.3 3.5 3.1 1.9 C1709 1.8 2.2 2.1 3.2 2.5 3.3 3.2 3.1 3.5 3.6 3.2 3.5 3.1 1.9 -------------------------------------------------------------------- 3.7 4.3 4.1 6.3 4.8 6.5 6.3 6.2 6.9 7.1 6.5 7.0 6.2 3.8 G H H J H J J J J J J J J G ============================================================================ C1710 1.8 2.1 2.0 3.2 2.2 3.3 3.2 3.1 3.4 3.6 3.3 3.6 3.1 1.9 -------------------------------------------------------------------- D G D G G G G G G G G G G D ============================================================================ C1711 1.8 2.1 2.0 2.9 2.3 3.2 3.3 3.0 3.4 3.5 3.3 3.5 3.1 1.9 C1712 1.9 2.1 2.0 3.1 2.4 3.5 3.2 3.1 3.6 3.5 3.4 3.6 3.2 1.9 -------------------------------------------------------------------- 3.7 4.2 4.0 6.0 4.7 6.7 6.5 6.1 7.0 7.0 6.7 7.1 6.3 3.8 G H H J H J J J J J J J J G ============================================================================ C1713 1.8 2.0 2.0 3.1 2.4 3.3 3.2 3.1 3.4 3.5 3.2 3.5 3.2 1.9 C1714 1.8 2.2 1.9 2.9 2.4 3.2 3.2 3.0 3.4 3.5 3.1 3.5 3.1 1.8 -------------------------------------------------------------------- 3.6 4.2 3.9 6.0 4.8 6.5 6.4 6.1 6.8 7.0 6.3 7.0 6.3 3.7 G H G J H J J J J J J J J G ============================================================================ C1715 1.9 2.2 2.0 3.1 2.1 3.2 3.3 3.0 3.6 3.6 3.3 3.6 3.1 1.9 -------------------------------------------------------------------- D G D G G G G G G G G G G D ============================================================================ Module sizes: B ( 1.44 TB) Note: The storage requirement listed includes D ( 2.00 TB) the tag-along periods for the Intensives. G ( 4.00 TB) Actuals will thus be slightly smaller. H ( 6.00 TB) J ( 8.00 TB) L (16.00 TB) Notes: - Example (recording group C1711, C1712 for station Matera): + record session C1711 on the J module, then + record session C1712 on the same J module. - Suggestions for handling disk module changes are provided at the end of this document. - Each station has two spare modules allocated that can be used when a regular disk fails. - An "extra" module is normally inserted once recording has started on the last allocated module for an experiment. This is done in case the the current module fills early. Typically, this should be the module that would be inserted next if recording goes as planned. If nothing goes wrong, this will make it easy to transition to the next module/schedule. If a module does fill early, the station will have to consider how to record the end of the next experiment, since some of that experiment's module will have been used too for the current experiment. Please also see the DISK MODULE CHANGES section below. Please inform the Coordinating Center (ivscc@lists.nasa.gov) if a module fills prematurely. ===================================================================== Recording mode Name Code GEOSX8N 8F Recording mode for: BADARY FORTLEZA HART15M HOBART26 KASHIM11 KATH12M KOKEE MATERA NYALES20 ONSALA60 WARK12M WETTZELL YEBES40M ZELENCHK Mode Tot.Rate Tot.BandW #BBC #bits Barrel Mk341:1 512 Mbits 128 MHz 14 2 NONE Chan.BW #Subpasses Tracks(*fan) Tot.tracks 8.00 MHz 1 32(*1) 32 X-band spanned bw= 720.0 MHz rms spanned bw= 280.4 MHz S-band spanned bw= 140.0 MHz rms spanned bw= 50.9 MHz Effective number of 1-bit channels recorded per sub-pass X S Total 19.13 11.48 30.61 ===================================================================== =================== DISK MODULE CHANGES =================== These experiments should only require one (or part of a) disk module each. Some modules will have two experiments recorded on them. Stations should follow the assigned list of module sizes according to Table 2 in these notes. DRUDG does not know the sizes, so it shows an ever-increasing GByte count in the listings. Please be aware that for the second experiment on a module, the Byte Count in the listing will not reflect the volume of data on the module from the previous experiment. Here are four suggestions for handling the changes: 1) Planning: Select the modules you will use for each experiment ahead of time using the sizes in Table 2 above as a guide. 2) Changes: After the last experiment for a module has been recorded and recording has switched to a new module, change the old module as soon as practical. You should put in the next module that is needed after the new one that is currently recording. It is good practice to change the module as soon as possible because then the FS will have a module to switch to in case the one being recorded becomes full prematurely. You should check periodically during the experiments that the modules are filling at the expected rate. If a module does fill prematurely, a window will appear prompting you to change the module. The window will give both the VSN and bank that needs to be changed. You should dismiss the window once the module has been changed. In situations where you have a module fill prematurely, you will need to make a practical decision about the next module to put in. You will at this point be recording the rest of the current experiment on the module for the next experiment. It may be a good choice to put in a spare module that will allow you to finish recording the next experiment once the current module is full. Please be aware this may affect your plans for automated module changes and which modules will need to receive expedited shipping. 3) Labels: Label the modules before removing then from the Mark 5, also affix a red dot. This will help avoid mixing-up the modules. At a minimum, label the module with the experiment it was used in and its sequence number. You should be able to print a label using: cd /usr2/log drudg LOG_NAME VSN where LOG_NAME is the name of the experiment log, including the ".log" and VSN is the eight character VSN. It should be done whenever a module has been filled or a schedule has ended (in the case of a not completely filled module). This ensures that the label contains the correct informa- tion. The label should then be affixed promptly to help keep track of the module contents. If you are not able to print module labels and need help trouble-shooting this, please contact Ed Himwich (Ed.Himwich@nasa.gov). This issue can be worked on even after CONT17 has started. 4) Locking and unlocking: When inserting or removing a module, turn the latch to "locked" or "unlocked" only when the Mark 5 is not recording. In addition, do not turn the key to "locked" unless the FS will not be sending commands (either to setup or start recording) to the Mark 5 for at least 20 more seconds. An "unlocked" module can be safely slide in or out at anytime. If you have any questions, please contact Ed Himwich (Ed.Himwich@nasa.gov).