Welcome to program SCHED. Version: 10.20 Release of about July 12, 2012 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). RDSET: Reading setup 1 sess213.K1024 RDSET: Reading setup file: sess213.K1024 STREAD: Reading station catalog: ../sta.sess213.dat STREAD: Reading locations file: /homes/vlbsoft/sched10.2/catalogs/locations.dat SRREAD: Reading source catalog: /homes/vlbsoft/sched10.2/catalogs/sources.vlba GETFREQ: Reading frequency file: /homes/vlbsoft/sched10.2/catalogs/freq.dat INPUT: Found 135 input scans. 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 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: sess213.K1024 Station JODRELL2 Only 200.00 of 256.00 MHz total bandwidth is within the IFs in the setup file before any FREQ or DOPPLER shifts. SETFCAT: In setup: sess213.K1024 Station TORUN 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: sess213.K1024 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 ef1cm 1 1 F F T T T T T T ef1cm 2 2 F F T T T T T T ef1cm 3 1 F F T T T T T T ef1cm 4 2 F F T T T T T T ef1cm 5 1 F F T T T T T T ef1cm 6 2 F F T T T T T T ef1cm 7 1 F F T T T T T T ef1cm 8 2 F F T T T T T T ef1cm 9 1 F F T T T T T T ef1cm 10 2 F F T T T T T T ef1cm 11 1 F F T T T T T T ef1cm 12 2 F F T T T T T T ef1cm 13 1 F F T T T T F T ef1cm 14 2 F F T T T T F T ef1cm 15 1 F F T T T T F T ef1cm 16 2 F F T T T T F T --------------------------------------- SETFCAT: In setup: sess213.K1024 Station ONSALA60 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 ons1cm 1 1 F T T T T T T T ons1cm 2 2 F T T T T T T T ons1cm 3 1 F T T T T T T T ons1cm 4 2 F T T T T T T T ons1cm 5 1 F T T T T T T T ons1cm 6 2 F T T T T T T T ons1cm 7 1 F T T T T T T T ons1cm 8 2 F T T T T T T T ons1cm 9 1 F T T T T T T T ons1cm 10 2 F T T T T T T T ons1cm 11 1 F T T T T T T T ons1cm 12 2 F T T T T T T T ons1cm 13 1 F T T T T T T T ons1cm 14 2 F T T T T T T T ons1cm 15 1 F T T T T T T T ons1cm 16 2 F T T T T T T T --------------------------------------- SETFCAT: In setup: sess213.K1024 Station METSAHOV 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 mh1cm 1 1 F T T T T T T T mh1cm 2 2 F T T T T T T T mh1cm 3 1 F T T T T T T T mh1cm 4 2 F T T T T T T T mh1cm 5 1 F T T T T T T T mh1cm 6 2 F T T T T T T T mh1cm 7 1 F T T T T T T T mh1cm 8 2 F T T T T T T T mh1cm 9 1 F T T T T T T T mh1cm 10 2 F T T T T T T T mh1cm 11 1 F T T T T T T T mh1cm 12 2 F T T T T T T T mh1cm 13 1 F T T T T T T T mh1cm 14 2 F T T T T T T T mh1cm 15 1 F T T T T T T T mh1cm 16 2 F T T T T T T T --------------------------------------- SETFCAT: In setup: sess213.K1024 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 --------------------------------------- TWOHDSET: Using 64 track mode for wide bandwidth. TWOHDSET: Using 16 Mbps per track record rate. Mark IV format on disk only. CHK4DAR: Inconsistent patching BBC#04 is not on Low CHK4DAR: Inconsistent patching BBC#03 is not on Low CHK4DAR: Inconsistent patching BBC#06 is not on Low CHK4DAR: Inconsistent patching BBC#05 is not on Low CHK4DAR: Inconsistent patching BBC#06 is not on Low CHK4DAR: Inconsistent patching BBC#05 is not on Low CHK4DAR: Inconsistent patching BBC#08 is not on Low CHK4DAR: Inconsistent patching BBC#07 is not on Low CHK4DAR: Inconsistent patching BBC#08 is not on Low CHK4DAR: Inconsistent patching BBC#07 is not on Low CHk4DAR: Requested mixed patching for URUMQI in setup sess213.K1024 Decrease frequency coverage or change LO, or verify with station that this is OK! CHK4DAR: Inconsistent patching BBC#02 is not on Low CHK4DAR: Inconsistent patching BBC#01 is not on Low CHK4DAR: Inconsistent patching BBC#04 is not on Low CHK4DAR: Inconsistent patching BBC#03 is not on Low CHK4DAR: Inconsistent patching BBC#04 is not on Low CHK4DAR: Inconsistent patching BBC#03 is not on Low CHK4DAR: Inconsistent patching BBC#06 is not on Low CHK4DAR: Inconsistent patching BBC#05 is not on Low CHK4DAR: Inconsistent patching BBC#06 is not on Low CHK4DAR: Inconsistent patching BBC#05 is not on Low CHK4DAR: Inconsistent patching BBC#08 is not on Low CHK4DAR: Inconsistent patching BBC#07 is not on Low CHK4DAR: Inconsistent patching BBC#08 is not on Low CHK4DAR: Inconsistent patching BBC#07 is not on Low CHk4DAR: Requested mixed patching for MEDICINA in setup sess213.K1024 Decrease frequency coverage or change LO, or verify with station that this is OK! 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 135 output scans ( 1 - 135) from 163/19:30:00 to 164/10:30:00 SUMOPE: Writing summary file er034.sum PROTECT: No PT or MK, so will not check that preemptable times are present. 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 er034.oms VXWRT : Writing V E X file er034.vex V2DOUT: Writing V2D file er034.tv2d FLAGS: Writing apriori flagging file er034.flag Processing EFLSBERG Processing ONSALA60 Processing JODRELL2 Processing METSAHOV Processing MEDICINA Processing NOTO Processing YEBES40M Processing TORUN Processing ZELENCHK Processing BADARY Processing SVETLOE Processing URUMQI Processing SHANGHAI