120 likes | 230 Vues
Field System Topics Ed Himwich, John Gipson, and Jonathan Quick. Current Status - FS 9.10.0. Mark 5B Recorder Support Mark 5 Sampler Module Support Rack types Mark5 and VLBA5 Not suitable for Mark 5A Recorder, but 9.10.1 will be GNPLT bug fixes
E N D
Field System Topics Ed Himwich, John Gipson, and Jonathan Quick
Current Status - FS 9.10.0 • Mark 5B Recorder Support • Mark 5 Sampler Module Support • Rack types Mark5 and VLBA5 • Not suitable for Mark 5A Recorder, but 9.10.1 will be • GNPLT bug fixes • Systests improved and Mark5B rack/recorder support • DRUDG • Support for Dymo printers under FS Linux 6, “sarge” • Equipment selection improved • New Mark IV rack patch algorithm to better harmonize geodesy and astronomy
FS 9.10.1 (November 2007) • Supports Mark 5A (again) • Fixes “fmset” problem for rack=none for recorder=Mark5B • Fixes error in default values (“*”) in “vsi4” command • Elimination of “postob_mk5” procedure • Fix for “preob” issue with “early start” may be included, otherwise in 9.10.2 • Other minor fixes and improvements
FS 9.10.2 (Winter 2007-2008) • Fix for “preob” issue with “early start” if was not in 9.10.1 • Eliminate use of some mk5=… commands for normal operations • Phase-cal extraction support for Mark IV decoders? • CHEKR monitoring of Mark5 • Update Mark 5 “Remaining Capacity” display while recording • S2 DAS support put on hold • Other small items generated by this meeting …
Mark 5B Recorder Support • New “mk5b_mode” command to set Mark 5B mode • “fmset” support for time setting/checking and configuration of timing parameters • New display of timing parameters and status • Mark 5B should be controlled by the “dimino” version of the Mark5A program, only “dimino” is officially supported by FS • Every time “dimino” is restarted, the operator should visit “fmset” to verify/set time. No change is needed if time is okay • In addition if Mark 5B is rebooted (hard or soft), the “s” command must be used in “fmset” to “synch” before verifying/setting the time • Some command log output format changes to agree with “dimino” forms of device commands • Documentation on using Mark 5B with FS in /usr2/fs/misc/mk5b_ops.txt
Mark 5 Sampler Module Support • Module is a replacement for Mark IV formatter, plugs into slot, but produces VSI-H output for, e.g., Mark 5B recorder • New “vsi4” command to control/monitor VSI4 board in Mark 5 Sampler module • Tsys/tpi features support device selection based on VSI4 bit stream selections and mark 5B recorder bit mask, i.e., analogous to Mark IV, VLBA4 support • Documentation on using Mark 5 Sample modlue with FS in also in /usr2/fs/misc/mk5b_ops.txt
FS Linux 6 • FS Linux 6 Distribution now available • Based on Debian “Sarge” • Uses RAID1 for more robust operations with two disks • Back-up scheme with three disks rotates disks periodically • Clean install • Upgrading path from FS Linux 5 (woody) will be to do a clean install and then copy /usr2 partition, etc. to new system • Not fully documented yet • Still supported with security patches • Now looking toward FS Linux 7, based on “etch” • GPIB driver issues need to be resolved • Router/Firewall • Inexpensive, <US$100 • Should be used with older, no longer supported distributions, including FS Linux 5
Longer term development items I • DBBC/DBE support • Documentation Update, wiki for documentation, operations discussion, bug reports • Improve prediction of disk pack change times • Pointing software clean-up • Eliminate redundancies in pointing configuration information by introducing a source coordinate database file and reorganizing point.prc and ctlpo.ctl (aquir control file). • Documentation clean-up to reflect new procedures and utilities • Improved Tsys • Most items completed • Post processing program to generate AIPS (ANTAB) format TSYS files from Cormac Reynolds • Periodic firing of calibration diode with flagging needed • Convert from fort77/f2c to g77 • Will allow use of source level debugger • Must maintain compatibility with f2c for older distributions
Longer term development items II • TNX (“Thanks”) command expansion • This command currently provides a syntax to eliminate the display of errors that the operator knows can’t be fixed and should be ignored • Will be extended to allow different error messages with the same number and two letter code to be distinguished • Will not allow an error that has not occurred to be masked off. • FSVUE • Integrated X client (Tcl/Tk) FS Operator Interface for FS • Second iteration now, uses client-server model • Allows multiple “Operator Input/Log Display” consoles for remote operation • Initially add-on, eventually main interface • Includes log display (scrolling doesn’t jump on new input) and operator input windows • Buttons to allow you to examine logs, help, and run various utilities: monit, logpl, msg, and others.
Longer term development items III • Band changes • Band configuration procedures added to set-up by DRUDG. • The DRUDG control file will be expanded to include a table of station defined procedures that can be used to set-up local station equipment for a band. These procedures can also be used manually by the operator as needed. Note that use of the existing SAVE_FILE command can be used in these procedures and INITI to recover the receiver set-up between FS terminations and restarts. • Add a command LOCONFIG. • This will be used after the LO= commands in the IFD set-up procedure. This can be used as trigger to start configuring the Los, if doing so in each individual LO= command might cause problems. By default, LOCONFIG will be a NO-OP, but it can be defined locally and do whatever is necessary for LO configuration in one step. • CALON and CALOFF SNAP variables. • This intended to deal with stations that have different cal control methods for different bands. The idea is that variables will be introduced into SNAP, specifically two: CALON and CALOFF. These can be defined by the band set-up procedures described above and used as $CALON and $CALOFF in procedures when the noise diode needs to be controlled.
Additional Future Items I • IF patching automation for Mark IV racks • EVN has hardware design, but not implemented in field yet. We will need one relatively simple SNAP command to support it: • A special version of PATCH and a way to control which version is used. • Mark IV decoder support • This is beyond the phase-cal monitoring mentioned above, mainly a few SNAP commands to control the decoder manually. Most of the effort here is actually divining what is needed and developing documentation
Additional Future Items II • Phase-cal control monitoring from VEX schedules • Mark IV decoder support already planned • AIPS format file generated from post-processing • Support for VLBA digital switch board