Download NCS 30m Presentation

NCS 30m
IRAM
HU
Title:
New Control System for the 30m Telescope
Presentation
Identifier - Master URL:
http://www.iram.es/IRAMES/documents/ncs30mPresentation
Revision: ncs30mPresentation, v1.3
Date: 2003-12-12
Expiration Date: 2004-03-31
Author: Hans Ungerechts
Contributors: WB
Audience: IRAM community
Publisher: IRAM, Granada, Spain
Subject and Keywords: new control system, NCS 30m, presentation
Description - about this document:
New Control System for the IRAM 30-m telescope (NCS 30m). Presentation.
NCS 30m
2003-12-12
1 of 28
NCS 30m
IRAM
HU
New Control System (NCS)
for the IRAM 30m Telescope
Overview of Presentation
 People
 Goals
 New Web . PDF
 System Architecture . Overview
 Current Activities
 Observer’s Interface . paKo
 Continuous Data Acquisition
 Online Data Processing . ODP
 Subsystems
 Services . messages . monitoring
 XML
 Hardware
 Priorities
 Time Plan
NCS 30m
2003-12-12
2 of 28
NCS 30m
IRAM
HU
People
AP
Alain Perrigouard
AS
Albrecht Sievers
HU
Hans Ungerechts
WB
Walter Brunswig
JP
Juan Penalver
GP
Gabriel Paubert
SS
Salvador Sanchez
NN
(to be decided)
NCS 30m
2003-12-12
3 of 28
NCS 30m
IRAM
HU
Goals and Decisions about Design
 New Observing Modes (OMs)
and new options for existing OMs
 Flexibility of OMs, scans, subscans
 Continuous data acquisition and fast OTF
 Support for remote, service, flexible observing
 Open for future development of hardware and
OMs
 Modular design
 Standard languages: Python, C
 Standard data formats: XML, FITS
 Standard OS: Linux
 Standard Hardware IF: VME
 Observer’s user interface:
command line language: SIC
(FORTRAN 90/95!)
(GUI: add-on “decoration”)
NCS 30m
2003-12-12
4 of 28
NCS 30m
IRAM
HU
New Web . PDF
http://www.iram.es/IRAMES/ncs30m/
(see pictures)
Documents, normally in PDF, located in:
http://www.iram.es/IRAMES/documents/
NCS 30m
2003-12-12
5 of 28
NCS 30m
IRAM
HU
System Architecture . Overview
(see diagram)
http://www.iram.es/IRAMES/documents/ncs30mSysArchOverview/
NCS 30m
2003-12-12
6 of 28
NCS 30m
IRAM
HU
Recent and Current Activities (Selection)
 Antenna Mount Drive. AP, JP
basic controller OK; cascade controller OK
definition and execution of subscans; some
coordinate systems (needs more tests)
ongoing: iterate subscans/segments, synchronization
messages, trace data
TBD: pointing; planets & bodies; integration into NCS
 Secondary Drive. JP.
hardware and low-level software OK
TBD: high-level functions, integration into NCS
 Observer’s User IF and Scan Analyzer. HU
protoype, v0.3: catalog, source, receiver, backend,
switching modes, some observing modes; text and
graphical display; general handling of defaults, limits,
save; start (= “analyze” to XML)
ongoing: debug, extend scanAnalyzer
TBD: more observing modes and options,
“convenience” features
NCS 30m
2003-12-12
7 of 28
NCS 30m
IRAM
HU
 Coordinator Subsystem. WB
delayed
 Services. messages, monitoring, logging. WB
delayed
 Backend Control System. WB
delayed
 Data. AS
antenna Mount Drive trace data
 VME/ PPC Systems. JP, SS, GP
+ many related projects
NCS 30m
2003-12-12
8 of 28
NCS 30m
IRAM
HU
Observer’s Interface . paKo
 Standard Observing Modes (OM)
with some new options
 Flexible subscan sequences
 OTF in any direction
 OTF along curves
 Loosely coupled to control system
- can run standalone
 Graphical preview of OMs
 Independent parameters for all OMs
 Default option for all OMs
 Check of all parameters for limits
and standard range
 Save for each OM and setup command
 Display ~ Syntax
 SIC
 Linux
NCS 30m
2003-12-12
9 of 28
NCS 30m
IRAM
HU
Continuous Data Acquisition (DA)
 Fast OTF as standard data acquistion mode
 DA continues “between” subscans and scans
 Independent data streams from subsystems
 Synchronization via “time stamps”
 Data files organized by:
o Header. XML
o Trace. FITS
(formerly “DAPs” and backend dumps)
o Trailer. XML
 Systematic naming & organization of files
 Switching Modes:
total power, wobbler, frequency, beam, …
 (+ allow some special modes with longer
integration in hardware, e.g., for “position
switching”)
NCS 30m
2003-12-12
10 of 28
NCS 30m
IRAM
HU
Online Data Processing . ODP
 “new” ODP is already in operation
(produces calibrated data from raw data)
Design
 ODP system runs scripts in the normal
off-line data processing software
o Improved methods, e.g., for pointing
o Avoid duplication and divergence
 ODP system is a control system just like
receiver or backend control system
 Integrated in NCS via coordinator subsystem
 Future possibilities
o Special purpose scripts
o Observer could specify options for ODP
o Several stages of processing (pipeline)
…
NCS 30m
2003-12-12
11 of 28
NCS 30m
IRAM
HU
Online Data Processing and NCS …
 NCS needs ODP results from / for:
o Pointing (including spectral line OTF)
o Focus
o Tipping
o Calibration
o Receiver Arrays
o…
o Future: also for target observations
 DP software provides values, calculates
results, and calls standard (output) routines
o XML
o These “results” shall be more general
e.g., for pointing model, flux monitoring, …
NCS 30m
2003-12-12
12 of 28
NCS 30m
IRAM
HU
Subsystems. Coordinator
 Receives scan specifications (in XML)
from observing queue
 Receives control commands from telescope
operator
 Coordinates execution of scan, subscans
 Cooperates with the “coordination layer”
of each control system
 Handles failures
 Python
NCS 30m
2003-12-12
13 of 28
NCS 30m
IRAM
HU
Services . Messages
 Telescope control by distributed processes
 Messages realize communication between
processes
 Requirements for messages
http://www.iram.es/IRAMES/documents/ncs30mProjectMessages/
 Messages are in XML
 Review of message format ongoing
(compare with AlmaCS logging)
 Message exchange
o server: elvin
http://elvin.dstc.com
o clients: Python, C
o functions for Python, C
are under development
NCS 30m
2003-12-12
14 of 28
NCS 30m
IRAM
HU
Services . Monitoring
 Monitoring and logging messages
to be displayed at several stations
 Support for remote monitoring
 Early versions of software will be similar to
current monitoring

TBD: requirements and design of new
monitoring software
 Python, GUI
NCS 30m
2003-12-12
15 of 28
NCS 30m
IRAM
HU
XML . what?
See: “XML in 10 points”
presentation from W3C at:
http://www.w3.org/XML/1999/XML-in-10-points.html
NCS 30m
2003-12-12
16 of 28
NCS 30m
IRAM
HU
XML . why?
 Simple, standardized, well-defined way to
design structured documents
 Contains description with the data
 Hierarchy or Tree structure of data
 Easy to extend with additional information
 Machine (and human) readable
 Easily passed over the internet
 Can describe very complex information
 Widely accepted standard
 Software tools for design, browsing, parsing
 Problems?
o Verbose. However: easy to compress
o Not yet standardized for data and astronomy
However: this is also true for ad-hoc formats
 XML and FORTRAN?
- could use C libraries or “translation” (in Python)
NCS 30m
2003-12-12
17 of 28
NCS 30m
IRAM
HU
XML . how?
 VOTable
 Generation of XML:
o FORTRAN: directly
o Python: some tools, e.g., for log messages
 Parsing/ Processing of XML:
o Python: currently based on standard library,
in particular, expat;
(maybe also xpath and xquery)
o Libraries for C
 ProjectDoc:
for project documentation in XML using XSL,
translation tool XT (James Clark, see
http://www.blnz.com/xt), and PDFLaTex
 Tools: edit and verify in
(X) Emacs, Oxygen, (XML Spy)
 … work elsewhere: XDF, XSIL, AML, RTML,
VOTable, … at: NASA, CDS, ALMA, …
NCS 30m
2003-12-12
18 of 28
NCS 30m
IRAM
HU
Hardware changes
 VAX/VMS to Linux with change to NCS v1
 Replacement of CAMAC by VME, Linux:
2003 to 2004
 Time: GPS, IRIG-B, NTP: first half 2003 (ready)
 We may keep some systems which are
currently using VME / OS9 for NCS v1 and
change them to Linux later
 (compare overview in “NCS: Plan”)

http://www.iram.es/IRAMES/documents/ncs30mPlan/
 Other hardware CS … (e.g., bolometer)
NCS 30m
2003-12-12
19 of 28
NCS 30m
IRAM
HU
NCS planned revisions
v0.n
Development
v0.3
current
…
v1.0
all “essential” subsystems and features
… debugging …
v1.1
first release
v2
additional observing modes and features
NCS 30m
2003-12-12
20 of 28
NCS 30m
IRAM
HU
Priorities
“Essential”
needed for functioning of NCS;
must be in first release (NCS v1.1)
“High”
should be implemented as soon as
possible;
in NCS v1.1 if it can be done with
moderate effort, otherwise later
“Low”
desirable,
but can be implemented later;
in NCS v1.1 only if it can be done
with minimal effort
NCS 30m
2003-12-12
21 of 28
NCS 30m
IRAM
HU
Priorities …
 “Essential”
o Current Observing Modes (OMs)
[with some new features]
o Subsystems:
observer, operator, coordinator,
antennaCS, receiverCS, backendCS,
switchingCS, dataProcessing
o Services: messages
 “High” or “Low”
o New OMs
o Subsystems:
observationQueue, dataArchive
o Services: Monitoring
 In v1: simple solutions for some subsystems
…
NCS 30m
2003-12-12
22 of 28
NCS 30m
IRAM
HU
Priorities …
 Later:
o More OMs, more options
o Monitoring++
o Queue++
o Marriage to data base
o Move remaining control systems
from OS9 to Linux
NCS 30m
2003-12-12
23 of 28
NCS 30m
IRAM
HU
Priorities . Observing Commands
Essential
receiver, backend
totalPower, frequencySwitching, wobblerSwitching;
start, wait, killActive
calibration (ambient, cold, sky, SI-Ratio)
tipping, pointing, focus, inclinometer
track, onOff, otfMap
subscans: calAmbient, calCold, calSky, on,
reference (off-source), onFocus, onAirmass,
slewAzimuth, otfLinear
source: basis systems, B and J, projections: “none”
and “radio”; planets, satellites, “body”
NCS 30m
2003-12-12
24 of 28
NCS 30m
IRAM
HU
Priorities . Observing Commands
High
beamSwitching
haltActive, resumeActive, stopActive
calibr. (test, null, variableLoad, signalGenerator,
phase)
general onOff, general Otf
subscans: calVariableLoad, calSignalGenerator,
calPhase, slewElevation, otfFocus (?), otfCircle,
otfCurve
source: descriptive systems, projections
Low
specialSwitching
fivePoint, crossRaster, rasterMap, otfLine, otfCross,
wobblerMap
subscans: otfWobbler
NCS 30m
2003-12-12
25 of 28
NCS 30m
IRAM
HU
Time Plan
(compare Gantt charts in “NCS: Plan 2003 to 2004”)
http://www.iram.es/IRAMES/documents/ncs30mPlan/
Scenario I:
compressed (= “no air” !) schedule;
this assumed WB available in 2003 and additional
support
Scenario II:
accounts for WB’s sick leave 2003; assumes:
1. WB available in 2004
2. temporary (1 year) help
3. no other priorities
(+ more Scenarios …)
NCS 30m
2003-12-12
26 of 28
NCS 30m
IRAM
HU
Milestones
2002-11 v0.1
first tests of SS observer,
scanAnalyzer, coordinator (done)
[2003-07 v0.2]
2003-11 v0.3
some OMs (done)
some coordinate systems (done)
secondaryDrive (low-level done)
coordination between
subsystems. delayed
2004-04 v1.0
first version with all essential
features. delay to 2004-07
2004-05 to 07 extensive tests and debugging.
delay to 2004-09 to 11
2004-07 v1.1
release debugged v1.
delay to 2004-12
NCS 30m
2003-12-12
27 of 28
NCS 30m
IRAM
HU
Time Plan …
2005
. flexible observation queue
. flexible monitoring system
. improved logging
. direct interaction with data base
. automated flexible observing
. change of remaining CS to Linux
. etc.
NCS 30m
2003-12-12
28 of 28