XML Configuration Files: Standards and Best Practices
80 likes | 179 Vues
Guide to define common dictionary for XML config files. Align with OT.XML definition. Use standard notation and ACSIS examples. Ensure clear specifications and avoid ambiguous terms.
XML Configuration Files: Standards and Best Practices
E N D
Presentation Transcript
XML Generalisation Tim Jenness JCMT Interfaces Meeting / April 2nd-6th 2001
Goals • Define common dictionary for XML configuration files generated by the translator • Match the OT XML definition as closely as possible
Examples • Use <rest_frequency units=“??”> rather than <rest_freq> • Use <sideband> rather than <sb> • Specify numeric ranges in standard way: • <range units=“km/s”> • <min>-10.0</min> • <max>100.0</max> • </range>
ACSIS • Will use TCS target specification to determine map centre (as opposed to tracking centre) and scan area (including map position angle) • Baseline regions are specified as a collection of <range> elements. • <spw_assoc> uses XML ID’s and IDREFS explicitly
ACSIS example - decimation • <archive> tag now replaced explicitly by <decimation> specification: • <decimation> • <range> <min>A</min> <max>B</max> • </range> • <increment>N</increment> • </decimation> • rather than <archive>A:B:N</archive>
Frontend • Uses <freq_offset_scale units=“??”> so this is how the OT must specify frequency switching
Undecided • Where to specify host names for specific drama tasks • IP aliases: • tcs.jcmt.jach.hawaii.edu? • Slave1.jcmt.jach.hawaii.edu? • Ws.jcmt.jach.hawaii.edu ? • Specify names in wiring file