Welcome to program SCHED. Version: 9.40 Release Jan. 13, 2011. The manual is at http://www.aoc.nrao.edu/software/sched/index.html Unix users should set $SCHED to the base area where SCHED is installed. Most run time messages will be in sched.runlog Some useful commands to give now if running interactively: SCHedule= : Specify input file. PLOT : Invokes uv, xy, rd, and uptime plotting. FREQLIST=lowF,highF : Make frequency list (MHz). Then exit. EXIT : Leave program. / : End of inputs - run program (or EXIT). SRREAD: Reading source catalog: Program_input RDSET: Reading setup file: sess211.L1024 STREAD: Reading station catalog: ./ey015a_sta.sess211.dat STREAD: Reading locations file: ./ey015a_locations.dat SRREAD: Reading source catalog: /aps3/sched9.4/catalogs/sources.vlba GETFREQ: Reading frequency file: /aps3/sched9.4/catalogs/freq.dat INPUT: Found 162 input scans. SHORTN: WARNING - Source names longer than 8 characters used. Mark III correlators and geodetic software will have problems. SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETCHAN: Must use dual sidebands because of the maximum BBCs available at some site: 8 SETFCAT: In setup: sess211.L1024 Station WSTRBORK Only 244.98 of 256.00 MHz total bandwidth is within the IFs in the setup file before any FREQ or DOPPLER shifts. SETFCAT: In setup: sess211.L1024 Station ONSALA85 Only 244.98 of 256.00 MHz total bandwidth is within the IFs in the setup file before any FREQ or DOPPLER shifts. SETFCAT: In setup: sess211.L1024 Station MEDICINA Only 160.00 of 256.00 MHz total bandwidth is within the IFs in the setup file before any FREQ or DOPPLER shifts. SETFCAT: In setup: sess211.L1024 Station SHANGHAI Only 244.98 of 256.00 MHz total bandwidth is within the IFs in the setup file before any FREQ or DOPPLER shifts. SETFCAT: In setup: sess211.L1024 Station JODRELL1 Only 224.98 of 256.00 MHz total bandwidth is within the IFs in the setup file before any FREQ or DOPPLER shifts. SETFCAT: In setup: sess211.L1024 Station SVETLOE WRTMSG: Special message from routine SETFCAT: ----------- WARNING ----------- SCHED could not find a frequency catalog group that matched the setup file and station mentioned above. Below are the closest matches with at least some overlap in RF frequency. You can use FREQLIST (a main program input) to get the frequency catalog group and IF numbers that are available. Or you can look in freq.dat in the catalogs area. Since SCHED cannot confirm the validity of your setup, check and be very sure it is correct! In the table below, a match is indicated by a T. A mismatch is indicated by F. FreqCat Baseband FreqCat IF First Pol RF VLA FE RF RF Group Channel IF Name LO Chan 1 IF Freq Band --------------------------------------- SETFCAT: In setup: sess211.L1024 Station ZELENCHK WRTMSG: Special message from routine SETFCAT: ----------- WARNING ----------- SCHED could not find a frequency catalog group that matched the setup file and station mentioned above. Below are the closest matches with at least some overlap in RF frequency. You can use FREQLIST (a main program input) to get the frequency catalog group and IF numbers that are available. Or you can look in freq.dat in the catalogs area. Since SCHED cannot confirm the validity of your setup, check and be very sure it is correct! In the table below, a match is indicated by a T. A mismatch is indicated by F. FreqCat Baseband FreqCat IF First Pol RF VLA FE RF RF Group Channel IF Name LO Chan 1 IF Freq Band --------------------------------------- SETFCAT: In setup: sess211.L1024 Station BADARY WRTMSG: Special message from routine SETFCAT: ----------- WARNING ----------- SCHED could not find a frequency catalog group that matched the setup file and station mentioned above. Below are the closest matches with at least some overlap in RF frequency. You can use FREQLIST (a main program input) to get the frequency catalog group and IF numbers that are available. Or you can look in freq.dat in the catalogs area. Since SCHED cannot confirm the validity of your setup, check and be very sure it is correct! In the table below, a match is indicated by a T. A mismatch is indicated by F. FreqCat Baseband FreqCat IF First Pol RF VLA FE RF RF Group Channel IF Name LO Chan 1 IF Freq Band --------------------------------------- SETFCAT: In setup: sess211.L1024 Station EFLSBERG WRTMSG: Special message from routine SETFCAT: ----------- WARNING ----------- SCHED could not find a frequency catalog group that matched the setup file and station mentioned above. Below are the closest matches with at least some overlap in RF frequency. You can use FREQLIST (a main program input) to get the frequency catalog group and IF numbers that are available. Or you can look in freq.dat in the catalogs area. Since SCHED cannot confirm the validity of your setup, check and be very sure it is correct! In the table below, a match is indicated by a T. A mismatch is indicated by F. FreqCat Baseband FreqCat IF First Pol RF VLA FE RF RF Group Channel IF Name LO Chan 1 IF Freq Band ef1570 1 1 F F T T T T T T ef1570 2 2 F F T T T T T T ef1570 3 1 F F T T T T T T ef1570 4 2 F F T T T T T T ef1570 5 1 F F T T T T T T ef1570 6 2 F F T T T T T T ef1570 7 1 F F T T T T T T ef1570 8 2 F F T T T T T T ef1570 9 1 F F T T T T F T ef1570 10 2 F F T T T T F T ef1570 11 1 F F T T T T F T ef1570 12 2 F F T T T T F T ef1570 13 1 F F T T T T F T ef1570 14 2 F F T T T T F T ef1570 15 1 F F T T T T F T ef1570 16 2 F F T T T T F T ef1590 1 1 F T T T T T T T ef1590 2 2 F T T T T T T T ef1590 3 1 F T T T T T T T ef1590 4 2 F T T T T T T T ef1590 5 1 F T T T T T T T ef1590 6 2 F T T T T T T T ef1590 7 1 F T T T T T T T ef1590 8 2 F T T T T T T T ef1590 9 1 F T T T T T T T ef1590 10 2 F T T T T T T T ef1590 11 1 F T T T T T T T ef1590 12 2 F T T T T T T T ef1590 13 1 F T T T T T T T ef1590 14 2 F T T T T T T T ef1590 15 1 F T T T T T T T ef1590 16 2 F T T T T T T T ef18cm 1 1 F F T T T T T T ef18cm 2 2 F F T T T T T T ef18cm 3 1 F F T T T T T T ef18cm 4 2 F F T T T T T T ef18cm 5 1 F F T T T T T T ef18cm 6 2 F F T T T T T T ef18cm 7 1 F F T T T T T T ef18cm 8 2 F F T T T T T T ef18cm 9 1 F F T T T T T T ef18cm 10 2 F F T T T T T T ef18cm 11 1 F F T T T T T T ef18cm 12 2 F F T T T T T T ef18cm 13 1 F F T T T T T T ef18cm 14 2 F F T T T T T T ef18cm 15 1 F F T T T T T T ef18cm 16 2 F F T T T T T T --------------------------------------- TWOHDSET: Using 64 track mode for wide bandwidth. TWOHDSET: Using 16 Mbps per track record rate. Mark IV format on disk only. SCHOPT: First output scan will be number 1 WRTMSG: Special message from routine AUTODOWN: * Stations using automatic tape allocation or disk recording systems are being removed from scans when the source is below the antenna pointing limits. This behavior can be overridden using DODOWN. WRTMSG: Special message from routine AUTODOWN: * Some stations are unable to reach a scheduled source before the scan end time. In most cases, those stations, if using disk recordings, are being removed from the affected scans. This behavior can be overridden using DODOWN. Also using DWELL time scheduling can prevent such cases. With DWELL with a second, but not a third argument, this may still happen if there are slow antennas. Note that, if using DWELL with a second argument, the antenna that does not make it to source is counted as one of the ones not to wait for. So don't be surprised if, for example, you specified not to wait for 2 and there is only one that gets there late. There is likely to be another that was scheduled for the scan that has been removed for too long a slew. In cases where an antenna is removed from a scan for too long a slew, a "W" will be placed as the UP indicator. That appears as a flag (along with "D", "H", "R", and "S") on some lines in the summary file scan listings. It also appears in some cases in the sch file. Removing scans with too long slews is capable of creating an undesired situation when phase referencing. When a wrap is needed, it is usually needed for one source before the other of a referencing pair. With scan removal, this causes one of the sources to get skipped repeatedly until the second source needs the wrap, even though both sources would have been ok after a wrap. To try to avoid this syndrome, SCHED will not remove a station from a scan for too long slew if it is an ALTAZ antenna and the slew is more than 315 degrees - ie it is a wrap. Removing scans with too longs slews can have another bad effect when scheduling with DURATION. If a long slew preceeds a series of short scans, it is possible to reject all of those short scans as each is rejected, causing the next to move up to where it will be rejected in turn. Therefore SCHED detects when it it has emptied a scan of stations because of slews and, instead of skipping the scan as it would one with all antennas down, it reinstates all of the long-slew stations. Those stations won't get to the source, but at least the next scan will be pushed out to where they will get to it. Be warned that, if your project can be time shifted as part of dynamic scheduling, incidents of problems with long slews can affect different scans than those for which you tested the schedule. SCHOPT: There will be 162 output scans ( 1 - 162) from 161/02:20:00 to 161/08:20:00 CHKSCN: 133 scans had more than half the antennas arrive on-source after the start time. This could be normal if using duration scheduling with small gaps. SUMOPE: Writing summary file ey015a.sum STALST: WARNING - A station has zero axis offset, which is unlikely. Accurate positions, including axis offsets are needed for correlation. Is your station location information adequate? See the summary file station list to see which stations are suspect. OMSOUT: Writing OMS file ey015a.oms VXWRT : Writing V E X file ey015a.vex VXWRIF: WARNING, Phase cal not under computer control for some stations. Contact stations by e-mail to make sure phase cal is switched off Phase cal is under computer control for VLBA stations and many others. EFLSBERG has 29 Tsys measurements. Maximum interval = 18 minutes. WSTRBORK has 29 Tsys measurements. Maximum interval = 17 minutes. ONSALA85 has 29 Tsys measurements. Maximum interval = 18 minutes. MEDICINA has 29 Tsys measurements. Maximum interval = 18 minutes. TORUN has 29 Tsys measurements. Maximum interval = 18 minutes. SVETLOE has 29 Tsys measurements. Maximum interval = 18 minutes. ZELENCHK has 24 Tsys measurements. Maximum interval = 18 minutes. BADARY has 29 Tsys measurements. Maximum interval = 17 minutes. URUMQI has 31 Tsys measurements. Maximum interval = 18 minutes. SHANGHAI has 29 Tsys measurements. Maximum interval = 18 minutes. VXSCH: Tsys calibration at most MkIV stations is taken during every gap in recording, but these appear over 15 min apart for the stations listed above! This can be improved by inserting gaps at regular intervals. Note this is not an issue for Westerbork or Arecibo WRTMSG: Special message from routine VXSCH: For most MkIV stations (e.g. most of the EVN) the calibration diode is only fired during gaps in recording. Although the total power is monitored continuously during scans, the calibration diode must be fired regularly to allow these total power levels to be accurately converted to system temperatures. It is recommended that, where possible, you leave a gap in recording at least every 15 minutes to allow the system temperature measurements. The gap should be at least 15 seconds, but you should also try to ensure that these gaps are long enough that all the antennas are on source before the next scan starts. Note that warnings about Westerbork and Arecibo can be safely ignored because they have continuous system temperature measurements. EFLSBERG: only 20 out of 29 Tsys measurements are on-source TORUN : only 26 out of 29 Tsys measurements are on-source BADARY : only 27 out of 29 Tsys measurements are on-source VXSCH: Stations listed above are affected by slewing during Tsys calibration WRTMSG: Special message from routine VXSCH: Note that although you may have left gaps during which the system temperature can be measured at MkIV stations, one or more stations are still slewing at the scan starts. System temperatures measured when the antennas are slewing are unlikely to be useful. The time between useful Tsys measurements is therefore likely to be longer than the recommended 15 minutes at the stations listed above. Note that warnings about Westerbork and Arecibo can be safely ignored. V2DOUT: Writing V2D file ey015a.v2d FLAGS: Writing apriori flagging file ey015a.flag Processing EFLSBERG Processing WSTRBORK Processing ONSALA85 Processing MEDICINA Processing TORUN Processing SVETLOE Processing ZELENCHK Processing BADARY Processing URUMQI Processing SHANGHAI Processing JODRELL1