IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Apr 4, 2005, 1:23:04 PM (21 years ago)
Author:
jhoblitt
Message:

change configuration file subsubsections to paragraphs

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/pslib/psLibSDRS.tex

    r3653 r3654  
    1 %%% $Id: psLibSDRS.tex,v 1.195 2005-04-04 23:19:51 jhoblitt Exp $
     1%%% $Id: psLibSDRS.tex,v 1.196 2005-04-04 23:23:04 jhoblitt Exp $
    22\documentclass[panstarrs,spec]{panstarrs}
    33
     
    39383938On error, the function shall return \code{NULL}.
    39393939
    3940 \subsubsection{Comments}
     3940\paragraph{Comments}
    39413941
    39423942The configuration file shall consist of plain text with
     
    39513951which should not form part of the key.
    39523952
    3953 \subsubsection{Types}
    3954 \paragraph{Scalar \& Vector}
     3953\paragraph{Types}
     3954\subparagraph{Scalar \& Vector}
    39553955
    39563956Next, to assist the casting of the value, shall be a string identifying the
     
    39943994and/or +/-infinity values for selected types.}
    39953995
    3996 \paragraph{MULTI}
     3996\subparagraph{MULTI}
    39973997
    39983998An additional hurdle is the specification of keys that may be non-unique (such
     
    40474047files.
    40484048
    4049 \subsubsection{Complex Types}
    4050 \paragraph{TYPE}
     4049\paragraph{Complex Types}
     4050\subparagraph{TYPE}
    40514051
    40524052We support a modest tree structure by defining a reserved keyword \code{TYPE}.
     
    40754075Figure~\ref{fig:metadata}.
    40764076
    4077 \paragraph{METADATA}
     4077\subparagraph{METADATA}
    40784078
    40794079Another way to form a tree-like structure is to directly define a
     
    40934093\end{verbatim}
    40944094
    4095 \subsubsection{Scoping Rules}
     4095\paragraph{Scoping Rules}
    40964096
    40974097A simple set of ``Scoping Rules'' are required to properly parse a
Note: See TracChangeset for help on using the changeset viewer.