%ADASS_PROCEEDINGS_FORM%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% SAMPLE2.TEX -- ADASS XII (2002) ASP Conference Proceedings sample
% paper with complicated markup. Based on ADASS XI (01) version.
%
% This is a comprehensive example, meaning that we have made use of each
% of the capabilities of the LaTeX + the ASPCONF macro package that we think
% you may need to use.  If you want to see a "base-bones" sample paper,
% take a look at sample1.tex.
%
% Much of the input will be enclosed by braces (i.e., { }).  The
% percent sign, "%", denotes the start of a comment; text after it
% will be ignored by LaTeX.  You might also notice in some of the
% examples below the use of "\ " after a period; this prevents LaTeX
% from interpreting the period as the end of a sentence and putting
% extra space after it.   
% 
% You should check your paper by processing it with LaTeX.  For
% details about how to run LaTeX as well as how to print out the User
% Guide, consult the README file.  
%
% If you do not have access to the LaTeX software or a laser printer
% at your site, you can still prepare your paper following the
% instructions in the User Guide.  In such cases, the editors will
% process the file and make any necessary editorial adjustments.
% 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 
\documentclass[11pt,twoside]{article}  % Leave intact
\usepackage{adassconf}

% If you have the old LaTeX 2.09, and not the current LaTeX2e, comment
% out the \documentclass and \usepackage lines above and uncomment
% the following:

%\documentstyle[11pt,twoside,adassconf]{article}

\begin{document}   % Leave intact

%-----------------------------------------------------------------------
%			    Paper ID Code
%-----------------------------------------------------------------------
% Enter the proper paper identification code.  The ID code for your
% paper is the session number associated with your presentation as
% published in the official conference proceedings.  You can
% find this number locating your abstract in the printed proceedings
% that you received at the meeting or on-line at the conference web
% site; the ID code is the letter/number sequence proceeding the title
% of your presentation.
%
% This will not appear in your paper; however, it allows different
% papers in the proceedings to cross-reference each other.  Note that
% you should only have one \paperID, and it should not include a
% trailing period.
%

\paperID{P9-8}
%%%% ID=P9-8

%-----------------------------------------------------------------------
%		            Paper Title 
%-----------------------------------------------------------------------
% Enter the title of the paper.
%
% EXAMPLE: \title{A Breakthrough in Astronomical Software Development}
%
% If your title is so long as to fill the page header when you print it,
% then please supply a short form as a \titlemark.
%
% EXAMPLE:
%  \title{Rapid Development for Distributed Computing, with Implications
%         for the Virtual Observatory}
%  \titlemark{Rapid Development for Distributed Computing}
%

\title{The CARMA Monitor System (CAM) - Transforming Cyclically Collected Telemetry into a Linear Stream}
\titlemark{The CARMA Monitor System}

%-----------------------------------------------------------------------
%		          Authors of Paper
%-----------------------------------------------------------------------
% Enter the authors followed by their affiliations.  The \author and
% \affil commands may appear multiple times as necessary.  List each
% author by giving the first name or initials first followed by the
% last name.  Authors with the same affiliations should grouped
% together. 
%
% Try to limit the front matter to no more than three \author
% commands.  Group authors with the same affiliations.  Too many
% \author commands fills the first page of the paper with little
% actual text.

\author{N.\ S.\ Amarnath\altaffilmark{1}, Stephen\ L.\ Scott\altaffilmark{2}, James\ Colby\ Kraybill\altaffilmark{3}, Andrew\ D.\ Beard\altaffilmark{2}, Paul\ Daniel\altaffilmark{2}, Chul\ Gwon\altaffilmark{1}, Rick\ Hobbs\altaffilmark{2}, Erik\ Leitch\altaffilmark{4}, David\ Mehringer\altaffilmark{5}, Raymond\ Plante\altaffilmark{5}, Marc\ W.\ Pound\altaffilmark{1}, Kevin\ P.\ Rauch\altaffilmark{1}, Peter\ J.\ Teuben\altaffilmark{1}}

% Notice that some of these authors have alternate affiliations, which
% are identified by the \altaffilmark after each name.  The actual alternate
% affiliation information is typeset in footnotes at the bottom of the
% first page, and the text itself is specified in \altaffiltext commands.
% There is a separate \altaffiltext for each alternate affiliation
% indicated above.

\iffalse	%%% ORIGINAL
\altaffiltext{1}{University of Maryland, College Park, MD} 
\altaffiltext{2}{California Institute of Technology/ Owen's Valley Radio Observatory} 
\altaffiltext{3}{University of California, Berkeley, CA}
\altaffiltext{4}{University of Chicago, Chicago, IL}
\altaffiltext{5}{NCSA/University of Illinois, Urbana-Champagne, IL}
\else		%%% More Stamndard
\vspace*{2ex}
\altaffilmark{1}\affil{
   University of Maryland, College Park, MD} 
\altaffilmark{2}\affil{
   California Institute of Technology/ Owen's Valley Radio Observatory} 
\altaffilmark{3}\affil{
   University of California, Berkeley, CA}
\altaffilmark{4}\affil{
   University of Chicago, Chicago, IL}
\altaffilmark{5}\affil{
   NCSA/University of Illinois, Urbana-Champagne, IL}
\fi

%-----------------------------------------------------------------------
%			 Contact Information
%-----------------------------------------------------------------------
% This information will not appear in the paper but will be used by
% the editors in case you need to be contacted concerning your
% submission.  Enter your name as the contact along with your email
% address.

\contact{N. S. Amarnath}
\email{amar@astro.umd.edu}

%-----------------------------------------------------------------------
%		      Author Index Specification
%-----------------------------------------------------------------------
% Specify how each author name should appear in the author index.  The 
% \paindex{ } should be used to indicate the primary author, and the
% \aindex for all other co-authors.  You MUST use the following
% syntax: 
%
% SYNTAX:  \aindex{LASTNAME, F. M.}
% 
% where F is the first initial and M is the second initial (if
% used).  This guarantees that authors that appear in multiple papers
% will appear only once in the author index.  

\paindex{Amarnath, N. S.}
\aindex{Scott, S. L.}
\aindex{Kraybill, J. C.}
\aindex{Beard, A. D.}
\aindex{Daniel, P.}
\aindex{Gwon, C.}
\aindex{Hobbs, R.}
\aindex{Leitch, E.}
\aindex{Mehringer, D. M.}
\aindex{Plante, R.}
\aindex{Pound, M. W.}
\aindex{Rauch, K. P.}
\aindex{Teuben, P. J.}

%-----------------------------------------------------------------------
%                     Author list for page header
%-----------------------------------------------------------------------
% Please supply a list of author last names for the page header. in
% one of these formats:
%
% EXAMPLES:
% \authormark{LASTNAME}
% \authormark{LASTNAME1 \& LASTNAME2}
% \authormark{LASTNAME1, LASTNAME2, ... \& LASTNAMEn}
% \authormark{LASTNAME et al.}
%
% Use the "et al." form in the case of seven or more authors, or if
% the preferred form is too long to fit in the header.

\authormark{Amarnath, N. S., \& Scott, Stephen L., et al.}

%-----------------------------------------------------------------------
%			Subject Index keywords
%-----------------------------------------------------------------------
% Enter up to 6 keywords describing your paper.  These will NOT be
% printed as part of your paper; however, they will be used to
% generate the subject index for the proceedings.  There is no
% standard list; however, you can consult the indices for past ADASS
% proceedings (http://iraf.noao.edu/ADASS/adass.html). 

\keywords{astronomy: radio telescopes, instruments, monitoring: systems, telemetry, interferometry}

%-----------------------------------------------------------------------
%			       Abstract
%-----------------------------------------------------------------------
% Type abstract in the space below.  Consult the User Guide and Latex
% Information file for a list of supported macros (e.g. for typesetting 
% special symbols). Do not leave a blank line between \begin{abstract} 
% and the start of your text.

\begin{abstract}          % Leave intact
The Combined Array for Research in Millimeter-wave Astronomy (CARMA) will be the combination of the BIMA, OVRO, and SZA millimeter arrays, at a new high elevation site (7200', 2200 m). With first light scheduled for 2005, CARMA will be the first heterogeneous millimeter array, combining antennas with diameters of 3.5, 6.1 and 10.4 meters.

CARMA's monitoring system (CAM), is designed to collect monitor data periodically from a set of heterogenous systems and organize these monitor points hierarchically. It allows for the collection/collation of sampled values from arbitrary monitor points and the storage of such monitor point values in files and databases. Monitor points may be mapped to multiple hierarchies, for example, physical hierarchies like antennas, receivers, and drives, or logical hierarchies like sub-arrays and antennas.

The monitor system was designed to accommodate monitor points associated with state machines, physical quantities (such as voltages), complex quantities (such as phases) and logical quantities like process health. It is also designed to help identify and isolate problems quickly, especially during integration at the new high site.
\end{abstract}

%-----------------------------------------------------------------------
%			      Main Body
%-----------------------------------------------------------------------
% Place the text for the main body of the paper here.  You should use
% the \section command to label the various sections; use of
% \subsection is optional.  Significant words in section titles should
% be capitalized.  Sections and subsections will be numbered
% automatically. 

\section{Design Considerations}

The Combined Array for Research in Millimeter Astronomy (CARMA) is a project
undertaken jointly by the California Institute of Technology 
(Owen's Valley Radio Observatory), the University of California (at Berkeley), 
the University of Illinois (Urbana-Champagne), the University of Maryland 
(College Park), and the University of Chicago. CARMA will combine two existing arrays, the Berkeley-Illinois-Maryland array (BIMA) and the array at Owen's Valley Radio Observatory (OVRO), and a new radio millimeter array, the SZA, being built at the University of Chicago.

The design of the CARMA Monitoring System (CAM) was shaped primarily by 
the need to facilitate development by teams distributed across multiple 
institutions, and by anticipated usage of monitor data.

Specifically, the design was governed by the following:

\begin{itemize}
\item CARMA is a collaboration between multiple institutions, each developing
software and/or hardware at their respective locations. 
\item The Array Control Computer will require a uniform stream
of monitor data from all of the different types of antennas, each with its own hardware and software. 
\item Minimal effort should be required to integrate CARMA monitoring data 
to existing methods of displaying health information for operating arrays 
such as OVRO and BIMA.
\item Some monitor data will be used for correcting visibility data.
\item Monitor data should provide the observers and engineers who operate and maintain the array with the information required to perform their functions.
\item Allow for independent evolution of the various portions of CARMA (antennas, correlators, and other subsystems) by decoupling major subsystems.
\end{itemize}

\section{The CARMA Software System - An Overview}

The CARMA Software System conceptual design is  based on the principle that
the software must reflect the instrument being manipulated (the array) and
must also provide the capability to use the instrument for radio astronomy.
As Figure-\ref{P9-8-fig-1} shows, the Observer Object encapsulates knowledge 
about astronomy and the CARMA Array Object(s) encapsulate knowledge about the 
instrument. The Array Object communicates with the various subsystems like
the antennas and the correlators through standardized interfaces using 
CORBA services. This insulates the Array Object and the array control 
subsystem from heterogenous hardware and software.

\begin{figure}[htb!]
\epsscale{.80}
\plotone{P9-8_1.eps}
\caption{A Block Diagram of the CARMA Software System. The dark arrows represent
commands, and the lighter arrows represent monitor and visibility data}\label{P9-8-fig-1}
\end{figure}

\section{The CARMA Monitor System - An Overview}

\begin{figure}[htb!]
\epsscale{.60}
\plotone{P9-8_2.eps}
\caption{A Block Diagram of the CARMA Monitor System.}\label{P9-8-fig-2}
\end{figure}

Figure-\ref{P9-8-fig-2} shows the architecture of the CARMA monitor system.
It is designed to provide a uniform framework for 

\begin{enumerate}
\item writing sampled monitor data onto the monitor stream
\item collecting all monitor data from each subsystem into a subsystem frame,
\item sending the subsystems frames to the array control computer every 
half-second, and
\item presenting CARMA monitor data to processes within the array control 
computer.
\end{enumerate}

\noindent %% FO
The CARMA Monitor System provides a half-second heartbeat for the array
as a whole, and presents monitor data from heterogenous hardware and software,
in a structured, uniform way, to processes within the array control computer.

\section{Monitor Points}
The monitoring system is composed of Monitor Points whose sampled values 
are monitor data. Monitor data is any data produced by the array excepting
the visibilities (auto and cross spectra produced by the correlators) and
a limited set of data produced by procedures that are run on demand 
(for example, optical pointing). Monitor data are collected and sent to the 
Array Control Computer (ACC) every half-second. Monitor data include values 
produced directly from hardware as well as copies of commanded hardware states. 
Monitor data values such as total power and calibration device state are
used in the processing of correlator data.

\section{Monitor Hierarchy}

Monitor points are arranged in a hierarchy to provide structure to the large 
numbers of Monitor Points in the monitor system. the levels in the hierarchy 
can be purely logical constructs, such as an Antenna Local Oscillator System,
or they may represent physical devices (called MonitorDevices) such as a
Gunn oscillator. The root of the hierarchy is ``CARMA Monitor System" which 
represents the collection of all monitor points across the entire CARMA system.
An example of programmatic use of the hierarchy and API is: 

\begin{verbatim}
    CarmaMonitorSystem carmaMon; 
    Gunn3mmMon gunn = carmaMon.OVROantenna(4).LOsystem().Gunn3mm(); 
    float tunerPosition = gunn.TunerPosition().getValue(); 
\end{verbatim}

\section{Monitor Data Flow}

A monitor subsystem is any collection of CARMA components that communicates 
with the ACC through a single computer (a Linux box). Within each monitor 
subsystem, monitor data are collected into a ``subsystem monitor frame". 
Each such frame is sent to the ACC using a CORBA Notification channel. 
A collator process in the ACC waits for such notifications and collates the 
frames received from all subsystems into a consolidated CARMA system monitor 
frame. This CARMA system frame is then made available to every process on 
the ACC. This process of sending notifications and collation/creation of a 
system frame occurs every half-second.

% We reset the footnote counter for the hyperlink since it does not
% appear to recognize the previous 3 footnotes generated from the
% altaffilmarks.  The command \htmladdnormallinkfoot puts the link as a
% footnote in the printed paper.  The command \htmladdnormallink with
% the same arguments will ignore the link in the printed copy.

\setcounter{footnote}{3}


% In this section, we see the use of the \subsection command to set off
% an independent subsection.  We only have one here; usually there would
% be several.
%
% We show the use of several of the displayed math environments
% described in the User Guide, and you get a healthy dose of
% mathematical typesetting examples.  Also, observe the use of the LaTeX
% \label command after the \subsection to give a symbolic tag to the
% subsection for cross-referencing in a \ref command.  LaTeX
% automatically numbers the sections, equations, tables, etc. as it
% goes, so in general you don't know what number something is going to
% have.  We'll refer to the "hairymath" section a little later.

% \acknowledgments


% That's the end of the main body of the paper.  Now we will have some
% back matter.
%
%-----------------------------------------------------------------------
%			      References
%-----------------------------------------------------------------------
% Now comes the reference list.  Since we typed out the citations ourselves,
% the reference list is enclosed in a "references" environment.  Each
% new reference begins with a \reference command which sets up the proper
% indentation.  Typography that may be required in the reference list by
% the editorial staff must be included by the author.
%
% Observe the "standard" order for bibliographic material: author name(s),
% publication year, journal name, volume, and page number for articles.
% Some journal names are available as macros; see the package
% instructions for a listing of which ones have been "macro-ized".
%
% There is no need to engage in any other typographic manipulation.
%
% List your references below within the reference environment
% (i.e. between the \begin{references} and \end{references} tags).
% Each new reference should begin with a \reference command which sets
% up the proper indentation.  Observe the following order when listing
% bibliographical information for each reference:  author name(s),
% publication year, journal name, volume, and page number for
% articles.  Note that many journal names are available as macros; see
% the User Guide for a listing "macro-ized" journals.   
%
% Note the following are some of the tricks that can be used:
%
%   o  \& is used to format an ampersand symbol (&).
%   o  \'e and \`e puts an accent agu and accent grave, respectively,
%      over the letter e.  See the User Guide for details on
%      formatting special characters.
%   o  "\ " after a period prevents LaTeX from interpreting the period 
%      as an end of a sentence.
%   o  \aj is a macro that expands to "Astron. J."  See the User Guide
%      for a full list of journal macros
%   o  \adassviii is a macro that expands to the full title, editor,
%      and publishing information for the ADASS VIII conference
%      proceedings.  Such macros are defined for ADASS conferences I
%      through X.
%   o  When referencing a paper in the current volume, use the
%      \adassviii and \paperref macros.  The argument to \paperref is
%      the paper ID code for the paper you are referencing.  See the 
%      note in the "Paper ID Code" section above for details on how to 
%      determine the paper ID code for the paper you reference.  
%
\begin{references}
\reference Gwon, C.\ 2004, \adassxiii, \paperref{P9-5}
\reference Scott, S.\ L.\ 2004, \adassxiii, \paperref{O10-4}
\end{references}

% Do not place any material after the references section

\end{document}  % Leave intact
