\documentstyle[epsf]{article}
\setlength{\topmargin}{-45pt}
\setlength{\oddsidemargin}{0cm}
\setlength{\evensidemargin}{-0cm}
\setlength{\textheight}{24cm}
\setlength{\textwidth}{16cm}

\newcommand{\ind}{\par\hangindent=0.5cm\hangafter=1\noindent}
\newcommand{\indd}{\par\hangindent=1.0cm\hangafter=1\hspace*{0.5cm}}
\newcommand{\idl}{\hspace*{5mm}{\tt IDL>\ }}
\newcommand{\unix}{\hspace*{5mm}{\tt unix\%\ }}
\newcommand{\crmk}{{\bf $<$CR$>$}}
\newcommand{\norh}{{\tt \$\{NORH\}}}
\newcommand{\ssw}{{\tt \$\{SSW\}}}



\begin{document}
\title{\bf Nobeyama Radioheliograph (NoRH) \\
Analysis Manual
\\
ver. 3.2
}
\author{Nobeyama Solar Radio Observatory, NAOJ}
\date{\today}
\maketitle

\clearpage
\tableofcontents

\clearpage

\section{Change Log}


\begin{itemize}
\item Version 2.3e: 25 October 2001,  written by Yokoyama, T. 
\item Version 3.0e:  7 September 2007, written by  Meshalkina, N.
\item Version 3.1e: 25 March 2010, written by Shimojo, M.
\end{itemize}

\section{Introduction}
\label{introduction}

This is a manual for analyzing the data of
Nobeyama Radioheliograph [NoRH] 
that is an imaging radio telescope (17/34GHz)
for the Sun in Nobeyama Solar Radio Observatory
[NSRO] of the National Astronomical Observatory of Japan [NAOJ]
(Nakajima et al. 1994; Nishio et al. 1994; Hanaoka et al. 1994). 
The contents are as follows: 
Section \ref{howtouse} describes how to install this package,
Section \ref{withidl} describes how to analyze the data using IDL.
Section \ref{withoutidl} describes how to analyze {\it without} IDL.
The detailed description of synthesis programs are
given in Section \ref{program}. 
Appendix \ref{norhdata} and \ref{fits} give 
the detailed information on NoRH data and
on the FITS header used, respectively.
A brief introduction of the NSRO data archive is given in the last section
Appendix \ref{archive}.

For any questions and requests, please send an e-mail to \\
\bigskip
\hspace*{1cm}{\tt service@solar.nro.nao.ac.jp}

The latest information on NoRH is updated on NSRO Web site.
The URL is \\
\bigskip
\hspace*{1cm} {\tt http://solar.nro.nao.ac.jp/norh/}\\

\section{How to set up the Analysis Softwares}
\label{howtouse}

To use the softwares that are introduced in this manual,
the following set-up is necessary.

\subsection{For analysis with IDL}

\medskip
\noindent
(1) Installation of the {\it SolarSoftware}.

Install the SolarSoftware (SSW) with the subpackage 'Radio/NoRH'.
We strongly recommend to install 
the SolarSoftware with the sub-package for Yohkoh/SXT.
If these softwares were not installed, please contact your
system manager. 
The primary distribution site for SolarSoftware is:
{\tt http://www.lmsal.com/solarsoft/}
We define the top directory of SSW as \ssw\ and that of NoRH subpackage
as \norh\ (usually {\ssw}{\tt /radio/norh}) in this manual.
The original version of the NoRH software is included 
in the distribution CD-ROM.

\medskip
\noindent
(2) Installation of {\it NoRH data base}

Copy the NoRH data base  after getting them from the NoRH distribution
CD-ROMs or from the NSRO archive at
{\tt ftp://solar-pub.nao.ac.jp/pub/nsro/norh/data}. 
The recommended destination is \norh{\tt/data}.

\medskip
\noindent
{\bf Note 1 ! }
Due to the limited network capability in Nobeyama,
we strongly recommend you to use CD-ROMs for the initial setup and
then to update through the network.

\medskip
\noindent
{\bf Note 2 ! }
The 'tsx' data (see Appendix \ref{tsx}) in NoRH data base is quite huge
although it is still possible to analyze the NoRH data {\it without}
this. So you do not have to install it.

\medskip
\noindent
(3) Setup of your personal environment

Include the followings in your environment setup file ({\tt \char126/.cshrc}). \\
{\tt
\hspace*{10mm} setenv SSW {\it SSW-directory}\footnote{
{\tt /share/ssw} in NSRO} \\
\hspace*{10mm} setenv SSW\_INSTR ``norh'' \\
\hspace*{10mm} setenv NORH \$\{SSW\}/radio/norh \\
\hspace*{10mm} source \$\{SSW\}/gen/setup/setup.ssw \\
\hspace*{10mm} source \$\{NORH\}/setup/setup.norh  \\
}
Note that the enviroment variable {\ssw} can be different 
(Ask your system manager)\footnote{In NSRO, it is {\tt /share/ssw}}.
In case you analyze many kinds of 
data at the same time, define SSW\_INSTR as follows, e.g. \\
{\tt
\hspace*{10mm} setenv SSW\_INSTR ``sxt hxt norh'' \\
}
In some sites, to save the disk space,
the NoRH data base could be installed somewhere 
that is not the default place ({\norh}{\tt /data})
\footnote{In NSRO, it's in default place.}. 
In this case, include following \\
{\tt
\hspace*{10mm} setenv NORHDB {\it data-base-directory} \\
}


\subsection{For analysis without IDL}

\medskip
\noindent
(1) Installation of {\it NoRH software} package 

Install the NoRH software package. The destination directory is basically
arbitrary. We define this top directory
as \norh\ in this manual.

\medskip
\noindent
(2) Installation of {\it NoRH data base}

Copy the NoRH data base  after getting them from the NoRH distribution
CD-ROMs or from the NSRO archive at
{\tt ftp://solar-pub.nao.ac.jp/pub/nsro/norh/data}.
The recommended destination is \norh{\tt/data}.

\medskip
\noindent
{\bf Note 1 ! }
Due to the limited network capability in Nobeyama,
we strongly recommend you to use CD-ROMs for the initial setup and
then to update through the network.

\medskip
\noindent
{\bf Note 2 ! }
The 'tsx' data (see Appendix \ref{tsx}) in NoRH data base is quite huge
although it is still possible to analyze the NoRH data {\it without}
this. So you do not have to install it.

\medskip
\noindent
(3) Setup of your personal environment

Include the followings in your environment setup file ({\tt \~{}/.cshrc}). \\
{\tt
\hspace*{10mm} setenv NORH {\it NoRH-directory} \\
\hspace*{10mm} source \$\{NORH\}/setup/setup.norh \\
}
Note that the enviroment variable {\norh} can be different 
(Ask your system manager)\footnote{In NSRO, it is {\tt /archive/pub/norh}}.
In some sites, to save the disk space,
the NoRH data base could be installed somewhere
that is not the default place ({\norh}{\tt /data})
\footnote{In NSRO, it's in default place.}.
In this case, include following \\
{\tt
\hspace*{10mm} setenv NORHDB {\it NoRH-data-base-directory} \\
}


\clearpage
\section{Analysis with IDL}
\label{withidl}

\subsection{Start up  SSW/IDL}
\label{startsswidl}

The NoRH IDL procedures described in this section all depend on the
SolarSoftware (SSW). When you start the analysis, start up
the SSW/IDL as follows: \\
\unix {\bf sswidl \crmk}\\
If you start up the SSW/IDL on the computer of Nobeyama Solar Radio
Observatory, the start-up command is as follows:\\
\unix {\bf idlh \crmk}

\subsection{Data Base}
\label{database}

\subsubsection{Observation Time and Logs}
\label{observationtime}

There is a data base for the observation time
('info' data: Appendix \ref{info}).
For example, to see the observation time of the schedules
on 1998-7-25 UT of 17GHz steady-mode (1sec integration) data, \\
  \idl {\bf norh\_pr\_info,'1998-07-25' \crmk} \\
or for data from 1998-7-25 to 1998-7-28, \\
  \idl {\bf st\_time='1998-07-25' \crmk} \\
  \idl {\bf ed\_time='1998-07-28' \crmk} \\
  \idl {\bf norh\_pr\_info,st\_time,ed\_time \crmk} \\
For 17GHz event-mode (50/100 msec integration) data, \\
  \idl {\bf norh\_pr\_info,st\_time,ed\_time,/event \crmk} \\
For 34GHz event-mode data, \\
  \idl {\bf norh\_pr\_info,st\_time,ed\_time,/event,freq=34 \crmk} \\
Then you will get \\
%
%
\hspace*{0.5cm} \begin{minipage}[t]{15cm} \small \begin{verbatim}
              Start      End   Schedule   StFr   EdFr
               (UT)      (UT)
1998-06-30 22:45:22  06:44:56   980701       1  28775
1998-07-01 22:45:24  06:44:57   980702       1  28774
\end{verbatim} \end{minipage}\medskip\\
%
%
One line is for one NoRH schedule (Appendix \ref{schedule}).
From left, 
start time,end time, 
schedule ID, start frame number, end frame number.
If you see the observation logs ('lob' data: Appendix \ref{lob}), \\
  \idl {\bf norh\_pr\_info,st\_time,ed\_time,/log \crmk} \\
You will get \\
%
%
\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
### 92/07/24
Data between 08:03 and 08:35 were lost.

### 92/07/31
*Phase tracking software bug was fixed. Phase jumps which were found every
250 sec. will disappear.
\end{verbatim}\end{minipage}\medskip\\
%
%

\subsubsection{Event List}
\label{eventlist}

There is a data base for the events
('evx' data: Appendix \ref{evx}).
In order to list them, e.g. on 1998-4-23 UT, \\
  \idl {\bf norh\_pr\_evx,'1998-04-23' \crmk} \\
or for data from 1998-4-23 UT to 4-27 UT, \\
  \idl {\bf st\_time='1998-04-23' \crmk} \\
  \idl {\bf ed\_time='1998-04-27' \crmk} \\
  \idl {\bf norh\_pr\_evx,st\_time,ed\_time \crmk} \\
For 34 GHz event list, \\
  \idl {\bf norh\_pr\_evx,st\_time,ed\_time,freq=34 \crmk} \\
For the events that are beyond some 
 averaged correlation value (say, 1.5 \%), \\
  \idl {\bf norh\_pr\_evx,st\_time,ed\_time,criterion=0.015 \crmk} \\
To see GOES class and NOAA ID of the active regions of the 
events\footnote{It is necessary to have the 
Yohkoh software and data base installed.}, \\
  \idl {\bf norh\_pr\_evx,st\_time,ed\_time,/goes \crmk} \\
Moreover you can display even with Yohkoh/HXT counts\footnote{It is 
necessary to have the Yohkoh software and data base installed.}, \\
  \idl {\bf norh\_pr\_evx,st\_time,ed\_time,/goes,/hxt \crmk} \\
Then \\
%
%
\hspace*{0.5cm}\begin{minipage}[t]{15cm}\footnotesize \begin{verbatim}
              Start      Peak      End    Dur    Max Cor. / GOES NOAA  Loca- /  HXT                   
              (UT)       (UT)      (UT)  (sec)  (x 10^-4) /             tion /   Low  Med1  Med2  High
1992-11-02 02:40:31  02:49:18  03:40:30   3599       1769 / X9.0             /  5278  1500   210    30
1992-11-05 06:06:44  06:20:41  06:39:59   1995        171 / M2.0             /    68    36    22    15
1992-11-23 03:33:42  04:31:07  06:37:18  11016        555 / C9.1 7347 S09W13 /    12     7     5    10
\end{verbatim}\end{minipage}\medskip\\
%
%

\subsection{Time-series data}
\label{timeseries}

After the daily observation, files that contain
the averaged correlation value 
are automatically
created from the raw data. This data is convenient for 
quick-look of the data.
Definition of 'correlation' is "averaged values of correlation of
antenna pairs (after removing short base-line pairs) of NoRH".
Correlation increases as a strong microwave signal comes 
due to e.g. a flare. So it is used instead of the {\it real} light curve
(plot of flux density). For 17 GHz plot, 1 \% of correlation corresponds
to 30 SFU flux density. It is used because 
much computation resource is necessary for image synthesis
that is the only method to obtain flux density 
at each time (see section \ref{section:tbflux}).
And correlation has an advantage that it is almost
not affected by the weather condition. However,
it does not increase when the flux is so strong because
it has an upper limit of unity.


\subsubsection{Correlation tcx data}
\label{correlationtcx}

The 'tcx' data is relatively small that uses less memory space
(Appendix \ref{tcx}).
But it has no information on circular polarization, and time accuracy
is about 1 sec. To read this data,
e.g. 1998-4-20 JST 17GHz, \\
  \idl {\bf norh\_rd\_tcx,'1998-4-20',index,data \crmk} \\
e.g., from 1998-4-23 JST to 4-27 \\
  \idl {\bf norh\_rd\_tcx,'1998-4-23','1998-04-27',index,data \crmk} \\
for 34GHz, \\
  \idl {\bf norh\_rd\_tcx,'1998-4-20',index,data,freq=34 \crmk} \\
You can directly  give the file name as an argument \\
  \idl {\bf norh\_rd\_tcx,file,index,data \crmk} \\
To plot the data use the Solar Software standard routine {\tt utplot}\\
  \idl {\bf utplot,index,data \crmk} \\

\subsubsection{Correlation tsx data}

The 'tsx' data is relatively huge but including the 
circular polarization information (for 17GHz only), and
the time accuracy is 1 msec (Appendix \ref{tsx}).
To read this data,
e.g. 1998-4-20 JST 17GHz, \\
  \idl {\bf norh\_rd\_tsx,'1998-4-20',index,data \crmk} \\
e.g., from 1998-4-23 JST to 4-27 \\
  \idl {\bf norh\_rd\_tsx,'1998-4-23','1998-4-27',index,data \crmk} \\
for 34GHz, \\
  \idl {\bf norh\_rd\_tsx,'1998-4-20',index,data,freq=34 \crmk} \\
You can directly  give the file name as an argument \\
  \idl {\bf norh\_rd\_tsx,file,index,data \crmk} \\
to plot the data use the Solar Software standard routine \\
  \idl {\bf utplot,index,data(0,*) \crmk} ; 17GHz RCP component \\
  \idl {\bf utplot,index,data(1,*) \crmk} ; 17GHz LCP component \\
  \idl {\bf utplot,index,data \crmk} ; 34GHz \\

\clearpage

\subsection{Image Synthesis}

\subsubsection{Image Files at NSRO Archive}

Some synthesized images (Table \ref{table:archive})
are put in the NSRO archive (Table \ref{archive}).
You can obtain them by anonymous FTP. Before synthesizing
by yourself, try them first.

\begin{table}[!h]
\caption{Image Files at NSRO Archive}
\begin{center}
\begin{tabular}{lllll} \hline
Data & Frequency & Synth. Prog. & Covered duration & Directory \\\hline
10 min. interval & 17GHz & koshix & since 1999 & {\tt images/10min} \\
@3:00 UT (noon in Japan) & 17/34GHz & koshix/hanaoka & since Jul 1992 
& {\tt images/daily} \\
Event$^{*}$ & 17/34GHz & hanaoka/fujiki & since Jun 1992 & {\tt images/event} \\
Weak Event$^{*}$ & 17/34GHz & hanaoka & since Jun 1992 & {\tt images/eventw} \\
GOES M,X Event & 17/34GHz & hanaoka & since Jun 1992 & {\tt images/goes\_event} \\\hline
\end{tabular}
\label{table:archive}
\end{center}
*: The 'Event's here have peak correlation more than 1.5 \%, the 'Weak Event's
have more than 0.5 \% and less than 1.5 \%.
\end{table}

\subsubsection{Pre-Processing for Image Synthesis --- Transfer of Raw Data}
 
You have to transfer the raw-data and 'SZ' files 
(Appendix \ref{raw} and \ref{sz})
from NSRO archive (Appendix \ref{archive}) to your computer through the network
before synthesis of the NoRH images.

\medskip
\noindent
{\bf Note !} The size of one raw-data file is about 16 Mbytes
(that includes 10 minutes of data, i.e. 600 image frames ). 
We strongly recommend the 
users who are far away ( in the sence of the network)
to request us to send the data to you by ordinary mail as a form of CD-ROM
(Appendix \ref{archive}).

\medskip
\noindent
(1) Basics 

For example, to transfer the raw data that is necessary
to synthesize one frame (image) every 600 seconds
between 1997-4-20 1:30 UT and 3:30 UT, \\
  \idl {\bf st\_time='1997-04-20 1:30:00' \crmk} \\
  \idl {\bf ed\_time='1997-04-20 3:30:00' \crmk} \\
  \idl {\bf interval=600 \crmk} \\
  \idl {\bf norh\_trans,st\_time,ed\_time,interval \crmk}

\medskip
\noindent
(2) Images at specific times

To transfer the raw data that is necessary
for synthesis of images at specific times, \\
  \idl {\bf time=['1997-04-20 1:30:00','1997-04-20 1:40:00'
    ,' 1997-4-21 2:00:00']\ \crmk} \\
  \idl {\bf norh\_trans,time \crmk}

\medskip
\noindent
(3) 34GHz

To transfer 34GHz data, \\
  \idl {\bf norh\_trans,time,freq=34 \crmk}

\medskip
\noindent
(4) Event-mode

To transfer event-mode data, \\
  \idl {\bf norh\_trans,time,/event \crmk}

\subsubsection{Image Synthesis}

This package has three programs for synthesis,
See table \ref{table:program} for supporting data.
Detailed description for each program is given in Section \ref{program}.

\medskip
\noindent
{\bf Note !} All the synthesis programs are written in 
Fortran 77 (partially 90). The IDL procedures described in 
this section call externally the executive binaries of these programs.
We prepared the binaries for Intel x86 with Linux OS architectures
in this package. So it is possible to synthesize the NoRH package
on machines with these architecture. To run on others,
it is necessary to compile them by yourself
(You have to purchase commercial numerical library in this case.
See Section 5 for detail.).

\medskip
\medskip
\noindent
(1) Basics 

For example, 
to synthesize one frame (image) every 600 seconds
between 1997-4-20 1:30 UT and 3:30 UT, \\
\idl {\bf st\_time='1997-04-20 1:30:00' \crmk} \\
\idl {\bf ed\_time='1997-04-20 3:30:00' \crmk} \\
\idl {\bf interval=600 \crmk} \\
\idl
{\bf norh\_synth,st\_time,ed\_time,interval \crmk} \\
Note that in this case, the synthesis program runs on the local workstation (Linux with Intel x86 architecture)
that you are working on.

\medskip
\noindent
(2) Non-uniformly spaced

You may synthesize the images
non-uniformly in time. For example, for images
at 1997-4-20 1:30, 1:40 and 1997-4-21 2:00 UT, \\
  \idl {\bf time=['1997-04-20 1:30:00','1997-04-20 1:40:00'
    ,'1997-4-21 2:00:00'] \crmk} \\
  \idl {\bf norh\_synth,time \crmk}

\medskip
\noindent
(3) 34GHz

For synthesis of 34GHz images\footnote{34GHz synthesis is
only available by program Hanaoka},\\
  \idl {\bf norh\_synth,time,freq=34 \crmk}

\medskip
\noindent
(4) Event mode

To synthesize the data of the event mode: \\
  \idl {\bf norh\_synth,time,/event \crmk}

\medskip
\noindent
(5) Koshix, Fujiki

The default synthesis program is Hanaoka.
To use Koshix or Fujiki,
\footnote{Fujiki can synthesize only partial images.
So it is necessary to give the center of the field-of-view.}: \\
  \idl {\bf norh\_synth,time,prog='koshix' \crmk}

\medskip
\noindent
(6) Partial Sun image

For partial Sun images,
the spatial shift from the Sun center to the image center 
and the size of the field of view have to be given.
The spatial shift could be given by unit of [1] arc-seconds
or [2] pixel. See table \ref{table:program} for size of pixel in
unit of arcsec.
%
The size of FOV is given as number of pixels.
See table \ref{table:program} for size of field of view in 
unit of pixels for each synthesis program.
%
For example, for an image that has (-431,54) arc-seconds shift from
the Sun center to the image center and with FOV (256$\times$ 256) pixels, \\
  \idl {\bf norh\_synth,time,cenunit=1,cenfnl=[-431,54],size=256 \crmk}\\
For (100,-20) pixel shifted image with FOV (128$\times$ 128) pixels, \\
  \idl {\bf norh\_synth,time,cenunit=2,cenfnl=[100,-20],size=128 \crmk}

\medskip
\noindent
(7) Syntesize an image at the designated time

In default, the frame to be synthesized is chosen by using
'info' data (Appendix \ref{info}). But in this case
it sometimes chooses the frame a little bit (1-sec  at maximum)
away from the designated time. If you need to synthesize image with
more accurate timing,
use 'tsx' data (Appendix \ref{tsx}) as follows\footnote{
This is because 'info' data only contains the start and end
times of a schedule but 'tsx' data contains one by one
correspondence of frame number and observation time.} \\
  \idl {\bf norh\_synth,st\_time,ed\_time,interval,/usetsx \crmk}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\subsection{Data Analysis}

\subsubsection{Read and display images}

You can directly give the file names as an argument. \\
  \idl {\bf norh\_rd\_img, file, index, data \crmk} \\
Then, the images of brightness temperature (unit K) 
is stored in array 'data'
and structure 'index'. To display \\
  \idl {\bf stepper, data, norh\_get\_info(index) \crmk}

\subsubsection{Beam Pattern}

To obtain a beam pattern \\
\idl {\bf beam=norh\_beam(index) \crmk} \\
This is a $21 \times 21$ pixels array. To display this pattern
 (contour of half power beam width [HPBW]) \\
\idl {\bf ocontour,beam,levels=[0.5] \crmk}

\subsubsection{Coordinate grid}

To overlay the coordinate gird on the image, \\
\idl {\bf stepper, data(*,*,0), norh\_get\_info(index(0)) \crmk} \\
\idl {\bf norh\_grid, index(0) \crmk} \\
To get the heliographic coordinate of the pointer \\
\idl {\bf norh\_grid, index(0), /read\_out \crmk}

\subsubsection{Getting Information about Images}

To get the observation time \\
\idl {\bf print,fmt\_tim(index) \crmk} \\
To get the image frequency \\
\idl {\bf print,norh\_gt\_freq(index) \crmk} \\
To get the circular polarization information \\
\idl {\bf print,norh\_gt\_polariz(index) \crmk} \\
To get the position of the image center in the coordinate 
in which the origin is the solar disk center and the unit is arcsec \\
\idl {\bf print,norh\_gt\_imgcen(index) \crmk} \\
To get the roll of the image (usually zero) \\
\idl {\bf print,norh\_cen(index,roll=roll) \crmk} \\
To get the exposure duration of the image \\
\idl {\bf print,norh\_gt\_expdur(index) \crmk} \\

\subsubsection{Using map procedure of the SolarSoftware}

In order to coalign the NoRH image with those obtained by 
the other instruments, it is convinient to use the map procedures
made by Dr. D. Zarro (for detailed information, see \\
{\tt http://orpheus.nascom.nasa.gov/\~{}zarro/idl/maps.html}.
The map of the NoRH image can be made as follows: \\
\idl {\bf norh\_index2map,index,data,map  \crmk} \\
\idl {\bf plot\_map,map  \crmk}

\subsubsection
{Derivation of Flux Density ($F_{\nu}$) from Brightness Temperature ($T_{b}$)}
\label{section:tbflux}

An NoRH image indicate distribution of brightness temperature (unit K).
To know the intensity (unit SFU/sterad) from each pixel, \\
\idl {\bf fi=norh\_tb2flux(data,index,/intensity) \crmk} \\
The flux density (unit SFU) of the whole image, the procedure is as follows. \\
\idl {\bf fi=norh\_tb2flux(data,index) \crmk} \\
The flux density from the partial area of
an image, $i0<i<i1$ $j0<j<j1$ is \\
\idl {\bf box=[i0, i1, j0, j1] \crmk}\\
\idl {\bf fi=norh\_tb2flux(data,index,box=box) \crmk} \\
or by giving the $(x, y)$ coordinate (origin solar disk center; unit arcsec),
for the area $x0\le x\le x1$ and $y0 \le y \le y1$, \\
\idl {\bf abox=[x0, x1, y0, y1] \crmk}\\
\idl {\bf fi=norh\_tb2flux(data,index,abox=abox)  \crmk}

\subsubsection
{Circular Polarization Degree}
\label{section:polarization}

From a pair of (R+L) and (R--L) images of 17 GHz,
distribution of circluar polarization degree can be obtained.
It is used for judging the emission mechanism and/or
deriving the magnetic field strength.
The definition is; \\
$$
r_{c}
\equiv {F_{\nu}^{(R-L)}\over F_{\nu}^{(R+L)}}
= {T_{b}^{(R-L)}\over T_{b}^{(R+L)}}
$$
Minimum is --1 (perfectly left-handed circular polarized), and
maximum is +1 (perfectly right-handed circular polarized).
The procedure is : \\
\idl {\bf file='./ipa990828\_005642' \crmk} \\
\idl {\bf norh\_rd\_img,file,indexa,dataa \crmk} \\
\idl {\bf file='./ips990828\_005642' \crmk} \\
\idl {\bf norh\_rd\_img,file,indexs,datas \crmk} \\ 
\idl {\bf fi17=norh\_tb2flux(dataa,indexa,/intensity) \crmk} \\
\idl {\bf fv17=norh\_tb2flux(datas,indexs,/intensity) \crmk} \\
\idl {\bf norh\_polariz,indexa,fi17,indexs,fv17,indexp,pol,mvdp \crmk} \\
{\tt pol} is an array of $r_{c}$. {\tt mvdp} is an array including 
the values of unity (1) for valid data or zero (0) for non-valid data.
{\tt indexp} is an index correspoinding to data {\tt pol}.


\subsubsection
{Make the Size of Beams Same between Two Images}
\label{section:convolv}

In order to analyze data of dual frequency observation,
the size of the beams have to be made same before taking ratio.
The method is as follows, \\
\idl {\bf norh\_rd\_img,file0,index0,data0 \crmk} \\
\idl {\bf norh\_rd\_img,file1,index1,data1 \crmk} \\
\idl {\bf norh\_convol,index1,index0,data0,index0c,data0c \crmk} \\
By {\tt norh\_convol}, data {\tt data0} is convolved by a beam
associated with {\tt index1}. The pixel size of the result array 
{\tt data0c} will become the coarser one between the beam and the image. 
Similarly, \\
\idl {\bf norh\_convol,index0,index1,data1,index1c,data1c \crmk} \\
then {\tt data0c} and {\tt data1c} have the same beam and
the same pixel size.

\subsubsection
{Spectrum Distribution}
\label{section:spectrum}

From a pair of 17GHz and 34GHz images,
spectrum distribution can be obtained.
It is used for judging the emission mechanism and/or
deriving the power-law index of non-thermal elecrons.
The derived variable is $\alpha$ whose definition is 
$$
F_{\nu} \propto {\nu}^{\alpha}
$$
Since available frequencies for NoRH are only two,
the actual derivation is
$$
{\alpha} =
{\log{(F_{\nu}^{34{\rm GHz}}/F_{\nu}^{17{\rm GHz}})}
\over
\log{({34{\rm GHz}}/{17{\rm GHz}})}}
$$
By using a pair of images of 17 GHz and 34 GHz with the same field of view \\
\idl {\bf file='./ipa990828\_005642' \crmk} \\
\idl {\bf norh\_rd\_img,file,indexa,dataa \crmk} \\
\idl {\bf file='./ipz990828\_005642' \crmk} \\
\idl {\bf norh\_rd\_img,file,indexz,dataz \crmk} \\
\idl {\bf fi17=norh\_tb2flux(dataa,indexa,/intensity) \crmk} \\
\idl {\bf fi34=norh\_tb2flux(dataz,indexz,/intensity) \crmk} \\
\idl {\bf norh\_convol,indexz,indexa,fi17,indexa\_c,fi17\_c \crmk} \\
\idl {\bf norh\_convol,indexa,indexz,fi34,indexz\_c,fi34\_c \crmk} \\
\idl {\bf norh\_alpha,indexa\_c,fi17\_c,indexz\_c,fi34\_c
,indexal,alpha,mvda \crmk} \\
{\tt alpha} is the power law index of spectrum $\alpha$.
{\tt mvda} is an array including 
the values of unity (1) for valid data or zero (0) for non-valid data.
{\tt indexal} is an index correspoinding to data {\tt alpha}.

\subsubsection
{Curves of Flux, Circular Polarization, and Spectrum Index from 
a Partial Area}

In order to obtain curves of flux, circular polarization degree, 
and spectrum index from  a partial area of a series of images, \\
\idl {\bf abox=[23,35,33,41] \crmk}\\
\idl {\bf fi17=norh\_tb2flux(dataa,indexa,abox=abox) \crmk}\\
\idl {\bf fv17=norh\_tb2flux(datas,indexs,abox=abox) \crmk}\\
\idl {\bf fi34=norh\_tb2flux(dataz,indexz,abox=abox) \crmk}\\
\idl {\bf norh\_polariz,indexa,fi17,indexs,fv17,indexp,polariz,mvdp \crmk}\\
\idl {\bf norh\_alpha,indexa,fi17,indexz,fi34,indexal,alpha,mvda \crmk}\\
Plot as, say,  \\
\idl {\bf utplot,indexp,polariz \crmk} \\
\idl {\bf utplot,indexal,alpha \crmk} 


\subsubsection
{Optically-Thin  Non-Thermal Gyrosynchrotron Emission}
\label{section:gyrosynchrotron}

{\bf Note: The procedures described in this subsection are under testing.
Comments are welcome for improvement.}

Based on approximation models, the relation between
the physical variables of emitting region and the emission can be
derived. The electron distribution function is assumed to be
the power law.
$$
{{d NV(E)} \over {d E}} = K \left({{E}\over{E_{0}}}\right)^{-\delta}��
$$
where $E$ is electron energy (keV), $NV(E)$ is number of electrons (particles)
that has larger energy than $E$. This distribution is described with parameters
$\delta$, $E_{0}$, and $K$. But it is usual to use 
$NV(E_0)=K/(\delta -1)/E_0^{\delta-1}$ instead of $K$. And we fix
$E_{0} = 10\ {\rm keV}$ after Dulk (1985).

\noindent 
(a) From Physical Variables to Emission

Inputs; power-law index $\delta$, magnetic field strength (G), angle between
magnetic field and line of sight (degree), and $NV$
--- total number (particles) of non-thermal electron (of $E> 10\ {\rm keV}$):
Outputs; flux density (SFU), circular polarization degree: \\
By Dulk's (1985) method:\\
\idl {\bf dulk\_gysy,delta,bb,theta,nv,freq,fi,rc \crmk} \\
If the size of emitting source (by solid angle in unit of sterad) is given
additionally, optical depth is also obtained \\
\idl {\bf dulk\_gysy,delta,bb,theta,nv,freq,fi,rc,omega,tau \crmk} \\
By Ramaty's (1969) method:\\
\idl {\bf ramaty\_gysy,delta,bb,theta,nv,freq,fi,rc \crmk} \\
\idl {\bf ramaty\_gysy,delta,bb,theta,nv,freq,fi,rc,omega,tau \crmk}

\noindent
(b) From Emission to Physical Variables

Based on Dulk's (1985) model we may derive the physical variables from emission.
After deriving $\alpha$ (see \ref{section:spectrum}),
power law index of non-thermal electron distribution function is \\
\idl {\bf norh\_alpha,indexa,fi17,indexz,fi34
,indexal,alpha,mvda \crmk} \\
\idl {\bf norh\_alpha2delta,alpha,delta \crmk} \\
If V-component (R$-$L) of 17 GHz is given adding to this,
physical variables can be derived to some extent. For this,
we have to assume one of three variables to be obtained --- 
magnetic field strength (G), angle between
magnetic field and line of sight (degree), and total number of non-thermal
electron of $E> 10\ {\rm keV}$ (particles). \\
\idl {\bf norh\_gysy\_inv,fi17,fi34,delta,fv17,thetain,bb,nv,/assumetheta
\crmk} \\
\idl {\bf norh\_gysy\_inv,fi17,fi34,delta,fv17,bbin,nv,theta,/assumebb
\crmk} \\
\idl {\bf norh\_gysy\_inv,fi17,fi34,delta,fv17,nvin,theta,bb,/assumenv
\crmk} \\
Adding to this, if the size of emission source is given
(as solid angle. Unit is sterad), optical thickness is derived \\
\idl {\bf norh\_gysy\_inv,fi17,fi34,delta,fv17,thetain,bb,nv,/assumetheta
,omega,tau \crmk} \\
\idl {\bf norh\_gysy\_inv,fi17,fi34,delta,fv17,bbin,nv,theta,/assumebb
,omega,tau \crmk} \\
\idl {\bf norh\_gysy\_inv,fi17,fi34,delta,fv17,nvin,theta,bb,/assumenv
,omega,tau \crmk} 

\medskip
{\bf Note:} In case of images, make the size of beams same between two images
(see section \ref{section:convolv}).

\subsubsection{Optically-Thin  Thermal Free-Free Emission}
\label{section:freefree}

{\bf Note: The procedures described in this subsection are under testing.
Comments are welcome for improvement.}

Based on Dulk (1985)'s approximation model, the relation between
the physical variables of emitting region and the emission can be
derived. \\

\noindent
(a) From Physical Variables to Emission

Inputs; electron temperature (K), line-of-site component
of magnetic field (G), and volume emission measure (cm$^{-3}$)
Outputs; flux density (SFU), circular polarization degree: \\
\idl {\bf dulk\_frfr,te,b\_loc,vem,freq,fi,rc \crmk} \\
If the size of emitting source (by solid angle in unit of sterad) is given
additionally, optical depth is also obtained \\
\idl {\bf dulk\_frfr,te,b\_loc,vem,freq,fi,rc,omega,tau \crmk}


\noindent
(b) From Emission to Physical Variables

Inputs; I-component (R$+$L) and V-component (R$-$L) of flux density (SFU):
Outputs; line-of-sight component of magnetic field (G), $VEM/\sqrt{T_e}$
where $VEM$ is volume emission measure, $T_e$ is electron temperature: \\
\idl {\bf norh\_frfr\_inv,fi,fv,b\_los,vem\_over\_sqrtte \crmk} \\
If one of $VEM$ or $T_e$ is assumed, the other is derived: \\
\idl {\bf norh\_frfr\_inv,fi,fv,b\_los,tein,vem,/assumete \crmk} \\
\idl {\bf norh\_frfr\_inv,fi,fv,b\_los,vemin,te,/assumevem \crmk} \\
Adding to this, if the size of emission source is given 
(as surface angle. Unit is sterad), optical thickness is derived \\
\idl {\bf norh\_frfr\_inv,fi,fv,b\_los,tein,vem,/assumete,omega,tau \crmk} \\
\idl {\bf norh\_frfr\_inv,fi,fv,b\_los,vemin,te,/assumevem,omega,tau \crmk} 

\subsection{Example of Analysis Session}

\subsubsection{Choose an Event}

Many interesting events are introduced in NoRP web site.
It is recommended to access first to these pages. The URL is {\tt http://solar.nro.nao.ac.jp/norh/}

\subsubsection{Light Curves}

\begin{figure}
\begin{center}
\epsfxsize=10cm
\epsfbox{corplot.eps}
\caption{Light curves (Correlation plot)}
\label{figure:corplot}
\end{center}
\end{figure}

After choosing an event for analysis, see the light curves.
It is useful to plot the correlation instead of the flux density.
The method is as follows (Fig \ref{figure:corplot}). \\
\idl {\bf norh\_rd\_tcx,'1999-8-28',index,data \crmk} \\
\idl {\bf utplot,index,data,/ylog \crmk} \\
Definition of 'correlation' is "averaged values of correlation of
antenna pairs (after removing short base-line pairs) of NoRH".
Correlation increases as a strong microwave signal comes
due to e.g. a flare. So it is used instead of the {\it real} light curve
(plot of flux density). For 17 GHz plot, 1 \% of correlation corresponds
to 30 SFU flux density. It is used because 
much computation resource is necessary for image synthesis
that is the only method to obtain flux density
at each time (see section \ref{section:tbflux}).
And correlation has an advantage that it is almost
not affected by the weather condition. However,
it does not increase when the flux is so strong because
it has an upper limit of unity.

\subsubsection{Image Synthesis}

For the choosen event, synthesize images.
Before this, search for the already synthesized images
in our FTP server since we prepare images for 
most of the important events. The URL is \\
{\tt ftp://solar-pub.nao.ac.jp/pub/nsro/norh/images}.
It can be reached by following the link in our web page\footnote{
They are under {\tt /archive/pub/norh/images} in NSRO.}.

For the one who wants to synthesize by her/himself, 
do the following two sets of commands. \\
\idl {\bf norh\_trans,['1999-8-28 0:56:42']\crmk} \\
\idl {\bf norh\_synth,['1999-8-28 0:56:42']\crmk} \\
The former is for transfering the raw data file ({\tt ss17990828...} 
including Fourier components and {\tt sz00990828...} 
including ephemeris parameters)
from NSRO archive to the current directory. It takes several minutes
depending on the network condition. Please ignore the warning message
"{\tt No such file or directory}". If the trasfer is successful,
you have files named {\tt ss17990828027} ($\approx$ 16 Mbyte) and
{\tt sz00990828001} ($\approx$ 200 byte). The second command is the
actual synthesis procedure and it takes tens of seconds to a few minutes
per an image. If it is successful, you will obtain
{\tt ifa990828\_005642} and {\tt ifs990828\_005642} in the current directory.
These are the FITS files whose contents are NoRH (R+L) and (R--L) images,
respectively. For spectrum analysis, make also  34 GHz image, \\
\idl {\bf norh\_trans,['1999-8-28 0:56:42'],freq=34\crmk} \\
\idl {\bf norh\_synth,['1999-8-28 0:56:42'],freq=34\crmk} \\
Similarly, the raw data files ({\tt ss17990828...} and
{\tt sz00990828...} are transformed and image FITS file
{\tt ifz990828\_005642} is made. Note only (R+L) component for 34 GHz image.


\subsubsection{Image Plot}
\label{section:image_plot}

\begin{figure}
%\begin{minipage}{7cm}
\begin{center}
\epsfxsize=10cm
\epsfbox{norh_plot_a.eps}
\caption{17GHz (R+L) image}
\label{figure:mapa}
\end{center}
%\end{minipage}
%
%\begin{minipage}{7cm}
\begin{center}
\epsfxsize=10cm
\epsfbox{norh_plot_s.eps}
\caption{distribution of 17GHz circular polarization degree}
\label{figure:maps}
\end{center}
%\end{minipage}
\end{figure}

Next, plot the images. We use a FITS file {\tt ipa990828\_005642}.
This file contains "an image of partial Sun of 17 GHz (R+L) component
at 00:56:42 UT on Aug 28, 1999". To read \\
\idl {\bf file='./ipa990828\_005642' \crmk} \\
\idl {\bf norh\_rd\_img,file,indexa,dataa \crmk} \\
\idl {\bf stepper,dataa,norh\_get\_info(indexa) \crmk} \\
\idl {\bf norh\_grid,indexa \crmk} \\
Easy plot is (Fig \ref{figure:mapa}) \\
\idl {\bf norh\_plot,indexa,dataa \crmk} \\
The unit of data is brightness temperature (K). Solar north is up. \\
For preparing to overplot with other instrumental data, change the
data format to SolarSoftware map. \\
\idl {\bf norh\_index2map,indexa,dataa,mapa \crmk} \\
\idl {\bf plot\_map,mapa,/cont,/grid \crmk} \\
\idl {\bf beam=norh\_beam(indexa,xbeam=xbeam) \crmk} \\
\idl {\bf contour,beam,!x.crange(0)+xbeam,!y.crange(0)+xbeam,/over,levels=[0.5]
\crmk} \\


\subsubsection{Polarization Plot}
\label{section:pol_plot}
From a pair of (R+L) and (R--L) images of 17 GHz,
distribution of circluar polarization degree can be obtained.
It is used for judging the emission mechanism and/or
deriving the magnetic field strength.
The definition is; \\
$$
r_{c}
\equiv {F_{\nu}^{(R-L)}\over F_{\nu}^{(R+L)}}
= {T_{b}^{(R-L)}\over T_{b}^{(R+L)}}
$$
Minimum is --1 (perfectly left-handed circular polarized), and
maximum is +1 (perfectly right-handed circular polarized).
The procedure is : \\
\idl {\bf file='./ips990828\_005642' \crmk} \\
\idl {\bf norh\_rd\_img,file,indexs,datas \crmk} \\
\idl {\bf fi17=norh\_tb2flux(dataa,indexa,/intensity) \crmk} \\
\idl {\bf fv17=norh\_tb2flux(datas,indexs,/intensity) \crmk} \\
\idl {\bf norh\_polariz,indexa,fi17,indexs,fv17,indexp,pol,mvdp \crmk} \\
{\tt pol} is an array of $r_{c}$. {\tt mvdp} is an array including
the values of unity (1) for valid data or zero (0) for non-valid data.
{\tt indexp} is an index correspoinding to data {\tt pol}. 
For easy plot (Fig \ref{figure:maps})\\
\idl {\bf norh\_plot,indexa,dataa,indexp,pol,mvdp \crmk} \\
For preparing to overplot with other instrumental data, change the
data format to SolarSoftware map. \\
\idl {\bf norh\_index2map,indexp,pol*mvdp,mappol \crmk} \\
\idl {\bf plot\_map,mappol,/cont,levels=[-0.8,-0.4,-0.2,0.2,0.4,0.8] \crmk}


\subsubsection{Spectrum Distribution}
\label{section:spectrum_plot}

\begin{figure}
\begin{center}
\epsfxsize=10cm
\epsfbox{norh_plot_alpha.eps}
\caption{Spectrum Distribution (gray scale),
$T_{b}^{\rm 17GHz}=1{\rm MK}$ (contour of thick line),
and circular polarization degree (contour of thin line)}
\label{figure:mapalpha}
\end{center}
\end{figure}

From a pair of 17GHz and 34GHz images,
spectrum distribution can be obtained.
It is used for judging the emission mechanism and/or
deriving the power-law index of non-thermal elecrons. 
The derived variable is $\alpha$ whose definition is
$$
F_{\nu} \propto {\nu}^{\alpha}
$$
Since available frequencies for NoRH are only two, 
the actual derivation is
$$
{\alpha} =
{\log{(F_{\nu}^{34{\rm GHz}}/F_{\nu}^{17{\rm GHz}})}
\over
\log{({34{\rm GHz}}/{17{\rm GHz}})}}
$$
By using a pair of images of 17 GHz and 34 GHz with the same field of view \\  
\idl {\bf file='./ipa990828\_005642' \crmk} \\ 
\idl {\bf norh\_rd\_img,file,indexa,dataa \crmk} \\
\idl {\bf file='./ipz990828\_005642' \crmk} \\
\idl {\bf norh\_rd\_img,file,indexz,dataz \crmk} \\
\idl {\bf fi17=norh\_tb2flux(dataa,indexa,/intensity) \crmk} \\
\idl {\bf fi34=norh\_tb2flux(dataz,indexz,/intensity) \crmk} \\
\idl {\bf norh\_convol,indexz,indexa,fi17,indexa\_c,fi17\_c \crmk} \\
\idl {\bf norh\_convol,indexa,indexz,fi34,indexz\_c,fi34\_c \crmk} \\
\idl {\bf norh\_alpha,indexa\_c,fi17\_c,indexz\_c,fi34\_c
,indexal,alpha,mvda \crmk} \\
{\tt alpha} is the power law index of spectrum $\alpha$.
{\tt mvda} is an array including
the values of unity (1) for valid data or zero (0) for non-valid data.
{\tt indexal} is an index correspoinding to data {\tt alpha}.
For easy plot (Fig \ref{figure:mapalpha})\\
\idl {\bf norh\_plot\_alpha,indexal,alpha,mvda,indexp,pol,mvdp,indexa,dataa 
\crmk} \\
For preparing to overplot with other instrumental data, change the
data format to SolarSoftware map. \\
\idl {\bf norh\_index2map,indexal,alpha*mvda,mapalpha \crmk} \\
\idl {\bf plot\_map,mapalpha,dmin=-4,dmax=2 \crmk}

\subsubsection{Interpretation of Data}

\begin{figure}
\setlength{\unitlength}{1mm}
\begin{picture}(160,100)
\put(20,90){\framebox(120,10)
{Strong polarization ($>$ sev.$\times$10\%), 
Bright even in quiet, above a sunspot ?}}

\put(60,70){\framebox(40,10)
{$T_{b}^{\rm 17 GHz} > 1\ {\rm MK}$ ?}}

\put(27,50){\framebox(20,10){$\alpha>0$}}
\put(47,50){\framebox(20,10){$\alpha\le0$}}

\put(88,50){\framebox(20,10){$\alpha>0$}}
\put(108,50){\framebox(20,10){$\alpha\approx 0$}}
\put(128,50){\framebox(20,10){$\alpha<0$}}

\put( 0,20){\dashbox(18,20){\shortstack{gyro- \\ resonance}}}

\put(21,20){\dashbox(25,20){\shortstack{opt-thick\\ synchrotron}}}

\put(49,20){\thicklines\framebox(25,20)
{\shortstack{\bf opt-thin \\ \bf synchrotron \\ 
\bf \underline{non-therm $\delta$}}}}

\put(77,15){\dashbox(25,25)
{\shortstack{opt-thick \\ synchrotron \\ 
or \\ opt-thick \\ free-free}}}

\put(105,10){\thicklines\framebox(25,30)
{\shortstack{\bf opt-thin\\ \bf synchrotron \\
\bf \underline{non-therm $\delta$} \\
or \\
\bf opt-thin \\ \bf free-free \\ \bf \underline{coronal $B$}}}}

\put(133,20){\thicklines\framebox(25,20)
{\shortstack{\bf opt-thin \\ \bf synchrotron \\
\bf \underline{non-therm $\delta$}}}}

\put(9,95){\vector(0,-1){55}}
\put(9,95){\line(1,0){11}}
\put(9,96){Yes}
\put(80,90){\vector(0,-1){10}}
\put(81,85){No}

\put(47,75){\vector(0,-1){15}}
\put(47,75){\line(1,0){13}}
\put(47,76){Yes}
\put(118,75){\vector(0,-1){15}}
\put(118,75){\line(-1,0){18}}
\put(114,76){No}

\put(37,50){\vector(0,-1){10}}
\put(57,50){\vector(0,-1){10}}
\put(98,50){\vector(0,-1){10}}
\put(118,50){\vector(0,-1){10}}
\put(138,50){\vector(0,-1){10}}


\end{picture}
\caption{Chart for interpretation of emission mechanism from the spectrum
distribution}
\label{figure:interpret}
\end{figure}

The interpretation is done by using the chart in Figure \ref{figure:interpret}.
Physical information can be obtained when the emission is by
"optically-thin gyrosynchrotron" or by "optically-thin free-free".
We can derive the variable using the Dulk's (1985) models.

In case "optically-thin gyrosynchrotron" emission,
we obtain power-law index of the non-thermal electrons.
Here we assume the distribution function of electrons to be 
$$
{{d NV(E)} \over {d E}} = K \left({{E}\over{E_{0}}}\right)^{-\delta}.
$$
where $E$ is electron energy (keV), $NV(E)$ is number of electrons (particles)
that has larger energy than $E$. This distribution is described with parameters
$\delta$, $E_{0}$, and $K$. But it is usual to use
$NV(E_0)=K/(\delta -1)/E_0^{\delta-1}$ instead of $K$. And we fix
$E_{0} = 10\ {\rm keV}$ after Dulk (1985).
If we find the emission to be "optically-thin gyrosynchrotron",
we will obtain $\delta$ from $\alpha$ by
$$
\delta=-1.1 (\alpha - 1.2).
$$

In case "optically-thin free-free" emission,
we obtain line-of-sight component of coronal magnetic field.
From the circular polarization degree $r_{c}$,
$$
B \approx 30 {\rm G} \left({r_{c}\over 1\%}\right).
$$

For example, figure \ref{figure:mapalpha} can be interpreted as follows:
First, the strong polarized source at $(x,y)=(180,-520)$ is by 
gyroresonance. It may be confirmed by comparing the image with
optical magnetogram to see if there is a sunspot. Next, 
the area inside the contour line of $T_{b}^{\rm 17GHz}=1{\rm MK}$
is emitting by optically-thin gyrosynchrotron. Non-thermal power-law
index $\delta$ is obtained from $\alpha$ immediately and we see
that the emission from two-sides 
of the loop structure is 'softer' than that of the top.
Next is for the area where $T_{b}^{\rm 17GHz}<1{\rm MK}$.
Around $(x,y)=(270,-500)$, it is hard to judge if it is
'optically-thin gyrosynchrotron' or 
"optically-thin free-free" because $\alpha \approx 0$.
If it is bright in soft X-ray it may be free-free emission.
In this case, line-of-sight component of coronal magnetic field
is obtained. Since the other area has $\alpha>0$, it is
optically thick and no information can be obtained.

\subsection{Others}

\subsubsection{Read Raw Data Directly}
\label{section:rd_rdt}
If the raw data is installed under directory \verb*+${NORH}/rawd+ in order to read raw data directly, \\
\idl {\bf norh\_rd\_rdt,st\_time,ed\_time,rdata,header \crmk} \\
for 34 GHz \\
\idl {\bf norh\_rd\_rdt,st\_time,ed\_time,rdata,header,freq=34 \crmk} \\
To read the raw data after copying to the current directory,\\
\idl {\bf norh\_rd\_rdt,st\_time,ed\_time,rdata,header,dir\_raw='.' \crmk} \\
To read by giving file name \\
\idl {\bf norh\_rd\_rdt17,file,rdata,header \crmk} \\
\idl {\bf norh\_rd\_rdt34,file,rdata,header \crmk} \\
For obtaining observing time (JST) \\
\idl {\bf timej=norh\_rdt2timej(rdata) \crmk}


\subsubsection{Antenna/Antenna-Pair ID and Name}
\label{section:antnum}

Each NoRH antenna has its own ID number and name.
The correspondance is \\
\idl {\bf antname=norh\_antnum2name(indgen(84)) \crmk} \\
The inverse is \\
\idl {\bf antnum=norh\_antname2num(['n15','w01']) \crmk} \\
Each NoRH anttena-pair pair has its own ID number.
The correspondance of this number and the names of anttennas of this pair
is given by \\
\idl {\bf ant=norh\_pair2ant(indgen(84*83/2)) \crmk}\\
The inverse is \\
\idl {\bf pair=norh\_ant2pair([0,28]) \crmk}

\subsubsection{Sun Position at Nobeyama}
\label{section:azel}

The azimuth and elevation of the Sun at Nobeyama is obtained by\\
\idl {\bf norh\_t2azel,time,az,el \crmk} \\
Unit is degree.

\subsubsection{Make original SZ file}
\label{section:mksz}


For making original SZ file by some reason,\\
\idl {\bf norh\_mksz,date \crmk} \\
For unusing some data obtained by some paticular antenna 
from synthesis procedure, make a new SZ file \\
\idl {\bf norh\_mksz,date,['n1','e10'] \crmk} \\
In this example, data of antenna N01 and E10 are unused.


\clearpage
\section{Analysis without IDL}
\label{withoutidl}

It is described in this section how to analyse the NoRH
data {\it without} IDL.
This is based on the UNIX commands, C-shell scripts and 
free astronomy softwares such as AIPS, IRAF etc.

\subsection{Data Base}

The observation time (info), logs (lob), event lists (evx) are
recorded in ASCII text files. you can read them directly by using
any editor softwares. The detailed explanation of each file is given
in Appendix \ref{norhdata}.

\subsection{Time-series data and Images}

Time-series averaged correlation (tcx, tsx) and
images (ifx, ipx) are both recorded as FITS format files.
You can read them by using  popular free astronomy softwares
such as AIPS, IRAF etc.

\subsection{Image data}

\subsubsection{Image Files at NSRO Archive}

Some synthesized images (Table \ref{table:archive})
are put in the NSRO archive (See Section \ref{archive}).
You can obtain them by anonymous FTP. Before synthesizing
by yourself, try them first.

\subsubsection{Transfer of raw data}

You have to transfer the raw-data and 'SZ' files (Appendix \ref{raw} 
and \ref{sz})
from NSRO archive (Appendix \ref{archive}) 
to your computer through the network
before synthesis of the NoRH images. It is convenient to use the
{\tt norh\_trans} command for this purpose. This is a C-shell script
that can be run on any UNIX machine. Or you can directly log in the
NSRO anonymous FTP server.

\medskip
\noindent
{\bf Note !} The size of one raw-data file is about 16 Mbytes 
(that includes 10 min. of data, i.e. 600 image frames). We strongly ask the 
users who are far away (in the sence of the network)
to request us to send the data to you by ordinary mail as a form of CD-ROM
(see Appendix \ref{archive}).

\medskip
\noindent
(1) By using norh\_trans

After editing the input file (say {\tt input}) adequately \\
\unix {\bf norh\_trans input \crmk} \\
The raw data files as well as corresponding 'SZ' files will be
transfered. The format of the input file is as follows: \\
%
%
\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small 
{\tt ss17980214006    }\hspace{1.5cm}\# 17GHz \\
{\tt ss34980214006    }\hspace{1.5cm}\# 34GHz \\
{\tt ss17920812002 b  }\hspace{1.2cm}\# schedule b \\
{\tt se17990216085759 }\hspace{1cm}\# event \\
\end{minipage} \\
%
%
One line corresponds to one raw-data file.
For steady-mode data that has multiple schedules (Appendix \ref{schedule}),\\
\hspace*{1cm}(file name) (schedule ID)  \\
The explanation for schedule and names of files are given in Appendix 
\ref{norhdata}.

\medskip
\noindent
(2) By logging in to anonymous FTP server

You can get the data by logging in to the FTP server, \\
\unix {\bf ftp solar-pub.nao.ac.jp \crmk} \\
The NoRH raw-data is put in the directory {\tt /pub/nsro/norh/raw}.
Do not forget to retrieve the 'SZ' file for corresponding day.

\subsubsection{Image synthesis}

This package has three programs for synthesis,
See table \ref{table:program} for supporting data.
Detailed description for each program is given in Section \ref{program}.

\noindent
{\bf Note !} All the synthesis programs are written in 
Fortran 77 (partially 90). The C-shell scripts described in 
this section call externally the executive binaries of these programs.
We prepared the binaries for Intel x86 with LinuxOS architectures
in this package. So it is possible to synthesize the NoRH package
on machines with these architecture. If you run on other,
it is necessary to compile them by yourself
(You have to purchase commercial numerical library in this case.
See section \ref{program} for detail.).

It is convenient to use the
{\tt norh\_synth} command for synthesis. This is a C-shell script
that can be run on any UNIX machine. 
After editing the input file (say {\tt input})\\
\unix {\bf norh\_synth input \crmk} \\
The format of input file is dependent on what synthesis program is used.
See section \ref{program} for detailed information.

The default program is Hanaoka for 17GHz data.
For 34GHz data,\\
\unix {\bf norh\_synth -p hanaoka34 input \crmk} \\
For using Fujiki,\\
\unix {\bf norh\_synth -p fujiki17 input \crmk} \\
For using Koshix,\\
\unix {\bf norh\_synth -p koshix17 input \crmk}


%\subsection{Pre-processing for usage of AIPS}

%AIPS is a popular software among the radio astronomical society.
%You have to re-format the NoRH raw data to be 
%readable by AIPS. The program {\tt c2fits} is developed for
%this purpose. 

%For 17GHz data,\\
%\unix {\bf c2fits17 $<$ input \crmk} \\
%For 34GHz data,\\
%\unix {\bf c2fits34 $<$ input \crmk} \\
%The format of input file (a template is given in \$\{NORH\}{\tt/soft/c2fits})
%is as follows,\\

%\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
%Inputs file for C2FITS17
%------------------------------------------------------------------
%Data file path and prefix     : ./ss17921008
%Ephemeris file path and name  : ./sz00921008001
%Frame info file path and name : ./info
%Phase diff file path and name : ../../../data/rlphdif/sun0706_2rlphdif
%Output file path and name     : 921008F
%Start time                    : 110000
%End time                      : 111000
%UT or JST?                    : JST
%Image Averging time           :  10
%Image Increment               : 300
%Smoothing Time (sec)          :   1
%Bypass Amplitude Calibration? :  NO
%Fixed Calibration Interval?   :  NO
%Start time of interval        : 120001
%End time of interval          : 120010
%Dump calibration solutions?   :  NO
%Skip output of FITS files?    :  NO
%------------------------------------------------------------------

%Note 1: The meaning of bypassing the amplitude calibration is that
%        instead of computing the amplitude of the complex gains
%        explicitly, the value 1.0 is used for all antennas. If the
%        amplitude calibration is bypassed the amplitude smoothing
%        time is ignored.

%Note 2: If a fixed calibration interval is used, the smoothing time
%        is ignored. It is assumed that the time standard for the
%        fixed calibration interval is the same as that of the data
%        interval.
%\end{verbatim} \end{minipage}\medskip\\


\clearpage
\section{Detailed Description of Synthesis Programs}
\label{program}

The standard NoRH synthesis programs, Hanaoka, Koshix, Fujiki
are explained in this section (table \ref{table:program}). 
The executable binary files are
given for Intel x86 with LinuxOS architectures in this package.
Compile procedure will be necessary if you run these programs
on others. See section \ref{compile} (You may have to purchase commercial
numerical libraries).
%
%
\begin{table}
\caption{Summary of synthesis programs}
\begin{center}
\renewcommand{\arraystretch}{1.2}
\begin{tabular}{lccccccc} \hline
& \multicolumn{3}{c}{Supported data [Yes/No]} & 
\multicolumn{2}{c}{Pixel Size [arcsec]} &
\multicolumn{2}{c}{Field of View [pixel]}\\ 
& 17/34GHz & Steady/Event & Full/Part & 17GHz & 34GHz & 17GHz & 34GHz \\ 
\hline
Hanaoka & Y/Y & Y/Y & Y/Y & 4.9 & 2.45 & $\le 512$ & $\le 1024$\\
Koshix & Y/N & Y/Y & Y/Y & 4.9 & -- & $\le 512$ & -- \\
Fujiki & Y/N & Y/Y & --/Y & 2.45 &  -- & 128 & -- \\\hline
\end{tabular}

\bigskip
\begin{tabular}{ll} \hline
& Note \\ \hline
Hanaoka & good at flares, no-good at diffuse sources \\
Koshix & good at diffuse faint sources, no-good at flares \\
Fujiki & high-spatial resolution synthesis of compact sources \\
\hline
\end{tabular}
\label{table:program}
\end{center}
\end{table}
%
%

\subsection{Hanaoka}

This is the most basic program for synthesis.
It applies the CLEAN algorithm to the point sources on the images
and is good at analysis of flares.
On the other hand, it is not good at diffuse sources.

\noindent
Present version \hspace{1cm} ver. 6.2

\noindent
Supported computer architecture \hspace{0.5cm} Intel x86 with LinuxOS, NEC/SX

\noindent
Supported data \hspace{0.5cm}
17GHz/34GHz, Steady/Event, Full/Partial Sun

\noindent
Pixel Size \hspace{0.5cm}
4.9 arcsec/pixel (17GHz), 2.45 arcsec/pixel (34GHz)

\noindent
Field of View \hspace{0.5cm}
Under 512 pixels for 17GHz.
Under 1024 pixels for 34GHz.

\noindent
How to use\\
\hspace*{5mm}(1) \unix {\bf hanaoka17 $<$ input17}  \\
\hspace*{5mm}(2) \unix {\bf norh\_synth -p hanaoka17 input}  \\
\hspace*{5mm}(3) \idl {\bf norh\_synth,time,prog='hanaoka',freq=17} \\
\hspace*{5mm}(4) \unix {\bf hanaoka34 $<$ input34}  \\
\hspace*{5mm}(5) \unix {\bf norh\_synth -p hanaoka34 input}  \\
\hspace*{5mm}(6) \idl {\bf norh\_synth,time,prog='hanaoka',freq=34} \\

\clearpage
\noindent
Example of input file

The line numbers are given for convinience. 
The item with ({\tt *}) usually do not have to be changed.
A template is given in \norh{\tt/soft/synthesis/hanaoka}.

\medskip
\noindent
17GHz

\medskip
\hspace*{0.5cm} \begin{minipage}[t]{15cm}
\begin{tabular}{rll}
  1:&{\tt .                 }& ; output directory \\
  2:&{\tt ss17980419        }& ; raw-data file name \\
  3:&{\tt sz00980419001     }& ; 'SZ' file name \\
  4:&{\tt 512               }& ; FOV pixel size \\
  5:&{\tt 1,0,0             }& ; image center offset from Sun center \\
  6:&{\tt 1                 }& ; start frame number \\
  7:&{\tt 3600              }& ; end frame number \\
  8:&{\tt 600               }& ; frame interval \\
  9:&{\tt 1                 }& ; *number of integration frames 
                                  for calibration \\
 10:&{\tt 1                 }& ; *number of integration frames for synthesis \\
 11:&{\tt -0.5,-0.5         }& ; *CLEAN criterion 1 (R+L), (R-L) \\
 12:&{\tt 0.01              }& ; *CLEAN criterion 2 \\
\end{tabular} \end{minipage}

%\clearpage
\medskip
\noindent
34GHz

\medskip
\hspace*{0.5cm} \begin{minipage}[t]{15cm}
\begin{tabular}{rll}
     1:&{\tt .                 }&  ; output directory \\
     2:&{\tt ss34980419        }&  ; raw-data file name \\
     3:&{\tt sz00980419001     }&  ; 'SZ' file name \\
     4:&{\tt 1024              }&  ; FOV pixel size \\
     5:&{\tt 1,0,0             }& ; image center offset from Sun center \\
     6:&{\tt 1                 }&  ; start frame number \\
     7:&{\tt 3600              }&  ; end frame number \\
     8:&{\tt 600               }&  ; frame interval \\
  9:&{\tt 1                 }& ; *number of integration frames 
                                  for calibration \\
 10:&{\tt 1                 }& ; *number of integration frames for synthesis \\
    11:&{\tt -1                }&  ; *CLEAN criterion 1 \\
    12:&{\tt 0.01              }&  ; *CLEAN criterion 2 \\
\end{tabular} \end{minipage}


\medskip
\noindent
Explanation for each item

\smallskip \noindent
{\bf (line 1) output directory}

\smallskip \noindent
{\bf (line 2) raw-data file name} \\
In case of steady-mode data, give only {\tt ss{\it FFYYMMDD}}
where {\it FF} is frequency (17 or 34), {\it YYMMDD}
is the date of observation. Do not give full file name
like {\tt ss{\it FFYYMMDD\#\#\#}}
where {\it \#\#\#} is the file number. That is automatically calculated
from the given frame. In case of event-mode data, give full file name.

\smallskip \noindent
{\bf (line 3) 'SZ' file name} \\
'SZ' file name corresponding to the date of the raw-data file.

\smallskip \noindent
{\bf (line 4) pixel size of the field of view} \\
A square region with pixel size given in this line will be the
field of view of the syntehsized image. In case of 17GHz data,
the full Sun image is 512-pixel square, and in case of 34GHz data,
that is 1024-pixel square. Pixel size is 4.9 (2.45) arcsec for 17GHz (34GHz).

\smallskip \noindent
{\bf (line 5) image center offset from Sun center}\\
Give non-zero values
if you synthesize an image with the center that has an offset from 
the Sun center.
The first element indicates the unit of shift, arcsec if 1, pixel if 2.
If you do {\it not} want to get a shifted image, just give '{\tt 1,0,0}'.

\smallskip \noindent
{\bf (line 6) first frame to synthesize}\\
Give zero in case of non-uniform interval.

\smallskip \noindent
{\bf (line 7) last frame to synthesize}\\
Give number of frames in case of non-uniform interval.

\smallskip \noindent
{\bf (line 8) frame interval}\\
Give frame numbers in case of non-uniform interval.
If it's too long, give in multiple lines.

\smallskip \noindent
{\bf (line 9) number of intergration frames for calibration }

\smallskip \noindent
{\bf (line 10) number of intergration frames for synthesis }

\smallskip \noindent
{\bf (line 11) CLEAN criterion 1}\\
Continue CLEAN until the maximum of the dirty map will become this value.
The unit is brightness temperature (steady solar disk is 10000 K).
The criterion that is given in the next item (line 12) will be adopted if
it is larger than this value. If given values are negative,
the absolute value of them times the disk brightness would be adopted
as the criterion. For 17GHz data, give values for (R+L) and (R-L),
the recommended values are -0.5 and -0.5, respectively. For 34GHz data,
give value only for (R+L), the recommended value is -1.


\smallskip
\noindent
{\bf (line 12) CLEAN criterion 2}\\
This given value times the maximum of the dirty map will become the other
criterion for CLEAN algorithm. The criterion given in the previous
item (line 11) will be adopted if it is larger than this value.
The recommended value is 0.01. It is safer to give larger value
for poor S/N data.

\clearpage

\subsection{Koshix}

This program is based on the Steer algorithm.
It applies the CLEAN method to the diffuse sources on the images and
is good at analysis of the quiet Sun and filaments.
On the other hand, it is not good at flares.


\noindent
Present version \hspace{1cm} ver. 6.2

\noindent
Supported computer architecture \hspace{0.5cm} Intel x86 with LinuxOS, NEC/SX

\noindent
Supported data \hspace{0.5cm}
17GHz (non-support for 34GHz), Steady/Event, Full/Partial Sun

\noindent
Pixel Size \hspace{0.5cm}
4.9 arcsec/pixel

\noindent
Field of View \hspace{0.5cm}
Under 512 pixels.


\noindent
How to use\\
\hspace*{5mm}(1) \unix {\bf koshix17 $<$ input17 }\\
\hspace*{5mm}(2) \unix {\bf norh\_synth -p koshix17 input }\\
\hspace*{5mm}(3) \idl {\bf norh\_synth,time,prog='koshix',freq=17}\\

\noindent
Example of input file

The line numbers are given for convinience.
The item with ({\tt *}) usually do not have to be changed.
A template is given in \norh{\tt/soft/synthesis/koshix}.

\medskip
\hspace*{0.5cm} \begin{minipage}[t]{15cm}
\begin{tabular}{rll}
  1:&{\tt .                 }& ; output directory \\
  2:&{\tt ss17980419        }& ; raw-data file name \\
  3:&{\tt sz00980419001     }& ; 'SZ' file name \\
  4:&{\tt 512               }& ; FOV pixel size \\
  5:&{\tt 1,0,0             }& ; image center offset from Sun center \\
  6:&{\tt 1                 }& ; start frame number \\
  7:&{\tt 3600              }& ; end frame number \\
  8:&{\tt 600               }& ; frame interval \\
  9:&{\tt 1                 }& ; *number of integration frames 
                                  for calibration \\
 10:&{\tt 1                 }& ; *number of integration frames for synthesis \\
 11:&{\tt 3000,3000         }& ; *CLEAN criterion (R+L), (R-L)
\end{tabular} \end{minipage}

\medskip
\noindent
Explanation for each item

\smallskip \noindent
{\bf (line 1) output directory}

\smallskip \noindent
{\bf (line 2) raw-data file name} \\
In case of steady-mode data, give only {\tt ss{\it FFYYMMDD}}
where {\it FF} is frequency (17 or 34), {\it YYMMDD}
is the date of observation. Do not give full file name
like {\tt ss{\it FFYYMMDD\#\#\#}}
where {\it \#\#\#} is the file number. That is automatically calculated
from the given frame. In case of event-mode data, give full file name.

\smallskip \noindent
{\bf (line 3) 'SZ' file name} \\
'SZ' file name corresponding to the raw-data file.

\smallskip \noindent
{\bf (line 4) pixel size of the field of view} \\
A square region with pixel size given in this line will be the
field of view of the syntehsized image. In case of 17GHz data,
the full Sun image is 512-pixel square, and in case of 34GHz data,
that is 1024-pixel square. Pixel size is 4.9 (2.45) arcsec for 17GHz (34GHz).

\smallskip \noindent
{\bf (line 5) image center offset from Sun center}\\
Give non-zero values
if you synthesize an image with the center that has an offset from 
the Sun center.
The first element indicates the unit of shift, arcsec if 1, pixel if 2.
If you do {\it not} want to get a shifted image, just give '{\tt 1,0,0}'.

\smallskip \noindent
{\bf (line 6) first frame to synthesize}\\
Give zero in case of non-uniform interval.

\smallskip \noindent
{\bf (line 7) last frame to synthesize}\\
Give number of frames in case of non-uniform interval.

\smallskip \noindent
{\bf (line 8) frame interval}\\
Give frame numbers in case of non-uniform interval.
If it's too long, give in multiple lines.

\smallskip \noindent
{\bf (line 9) number of intergration frames for calibration }

\smallskip \noindent
{\bf (line 10) number of intergration frames for synthesis }

\smallskip \noindent
{\bf (line 11) CLEAN criterion 1}\\
Continue CLEAN until the maximum of the dirty map will become this value.
The unit is brightness temperature (steady solar disk is 10000 K).
For 17GHz data, give values for (R+L) and (R-L),
the recommended values are 3000 and 3000, respectively. 

\clearpage
\subsection{Fujiki}

It is possible to analyze the flare images in detail with this program
because it synthesizes the compact sources
with a narrow beam by emphasizing the power of the 
higher wavenumber components. This program always outputs the partial
Sun images.

\noindent
Present version \hspace{1cm} ver. 6.2

\noindent
Supported computer architecture \hspace{0.5cm} Intel x86 with LinuxOS, NEC/SX

\noindent
Supported data \hspace{0.5cm}
17GHz (non-support for 34GHz), Steady/Event, Partial Sun

\noindent
Pixel Size \hspace{0.5cm}
2.45 arcsec/pixel

\noindent
Field of View \hspace{0.5cm}
128 pixels fixed.

\noindent
How to use\\
\hspace*{5mm}(1) \unix {\bf fujiki17 $<$ input17} \\
\hspace*{5mm}(2) \unix {\bf norh\_synth -p fujiki17 input} \\
\hspace*{5mm}(3) \idl {\bf norh\_synth,time,prog='fujiki',freq=17} \\

\noindent
Example of input file

The line numbers are given for convinience.
The item with ({\tt *}) usually do not have to be changed.
A template is given in \norh{\tt/soft/synthesis/fujiki}.

\medskip
\hspace*{0.5cm} \begin{minipage}[t]{15cm}
\begin{tabular}{rll}
     1:& {\tt .             }& ; output directory \\
     2:& {\tt ss17980419    }& ; raw-data file name \\
     3:& {\tt sz00980419001 }& ; 'SZ' file name \\
  4:&{\tt 1,0,0             }& ; image center offset from Sun center \\
     5:& {\tt 1             }& ; start frame number \\
     6:& {\tt 3600          }& ; end frame number \\
     7:& {\tt 600           }& ; frame interval \\
     8:& {\tt 1           }& ; *number of integration frames for calibration \\
     9:& {\tt 1           }& ; *number of integration frames for synthesis \\
    10:& {\tt 10            }& ; reference frame number \\
    11:& {\tt 1             }& ; *num. of integ. frames for 
                                    calibration of reference \\
    12:& {\tt 1             }& ; *num. of integ. frames for 
                                    synthesis of reference \\
    13:& {\tt 10000,10000   }& ; *CLEAN criterion 1 (R+L), (R-L) \\
    14:& {\tt 10000,10000   }& ; *CLEAN criterion 2 (R+L), (R-L) \\
    15:& {\tt 0.01          }& ; *CLEAN criterion 3 \\
\end{tabular} \end{minipage}

\medskip
\noindent
Explanation for each item

\smallskip \noindent
{\bf (line 1) output directory}

\smallskip \noindent
{\bf (line 2) raw-data file name} \\
In case of steady-mode data, give only {\tt ssFFYYMMDD}
where {\tt FF} is frequency (17 or 34), {\tt YYMMDD}
is the date of observation. Do not give full file name
like {\tt ssFFYYMMDD\#\#\#}
where {\#\#\#} is the file number. That is automatically calculated
from the given frame. In case of event-mode data, give full file name.

\smallskip \noindent
{\bf (line 3) 'SZ' file name} \\
'SZ' file name corresponding to the raw-data file.

\smallskip \noindent
{\bf (line 4) image center offset from Sun center}\\
Give non-zero values
if you synthesize an image with the center that has an offset from 
the Sun center.
The first element indicates the unit of shift, arcsec if 1, pixel if 2.
If you do {\it not} want to get a shifted image, just give '{\tt 1,0,0}'.

\smallskip \noindent
{\bf (line 5) first frame to synthesize}\\
Give zero in case of non-uniform interval.

\smallskip \noindent
{\bf (line 6) last frame to synthesize}\\
Give number of frames in case of non-uniform interval.

\smallskip \noindent
{\bf (line 7) frame interval}\\
Give frame numbers in case of non-uniform interval.
If it's too long, give in multiple lines.

\smallskip \noindent
{\bf (line 8) number of intergration frames for calibration }

\smallskip \noindent
{\bf (line 9) number of intergration frames for synthesis }

\smallskip \noindent
{\bf (line 10) frame number of reference frame }

\smallskip \noindent
{\bf (line 11) number of intergration frames for calibration 
of reference frame}

\smallskip \noindent
{\bf (line 12) number of intergration frames for synthesis 
of reference frame}

\smallskip \noindent
{\bf (line 13) CLEAN criterion 1}\\
Continue 1st CLEAN until the maximum of the dirty map will become this value.
The unit is brightness temperature (steady solar disk is 10000 K).
For 17GHz data, give values for (R+L) and (R-L),
the recommended values are 10000 and 10000, respectively.  
The criterion that is given in the next item (line 15) will be adopted if
it is larger than this value.

\smallskip \noindent
{\bf (line 14) CLEAN criterion 1}\\
Continue 2nd CLEAN until the maximum of the dirty map will become this value.
The unit is brightness temperature (steady solar disk is 10000 K).
For 17GHz data, give values for (R+L) and (R-L),
the recommended values are 10000 and 10000, respectively. 
The criterion that is given in the next item (line 15) will be adopted if
it is larger than this value.

\smallskip \noindent
{\bf (line 15) CLEAN criterion 2}\\
This given value times the maximum on the dirty map will become the other
criterion for CLEAN algorithm. The criterion given in the previous
item (line 13) will be adopted if it is larger than this value.
The recommended value is 0.01.

%\clearpage

\subsection{Compilation of synthesis programs}
\label{compile}

All the synthesis programs are written in 
Fortran 77 (partially 90). The executable binary files are
given for Intel x86 with LinuxOS, Sun/Sparc, NEC/EWS, NEC/SX architectures in this package.
Compile procedure that is explained in this section
will be necessary if you run these programs
on other architectures.  You may have to purchase commercial
numerical libraries.

\medskip
\noindent
(1) install numerical libraries

Get and install the following numerical libraries. \\

\begin{tabular}{lll}
Fujitsu/SSLII
& Commercial & {\tt http://www.fujitsu.co.jp/} \\
NEC/ASL 
& Commercial & {\tt http://www.nec.co.jp/} \\
\end{tabular}

\medskip
\noindent
{\bf Note !} NEC/ASL is necessary only to compile on NEC/SX or NEC/EWS.

\medskip
\noindent
(2) install the FITSIO library

Get and install the I/O library for FITS format data from

\hspace*{1cm} {\tt http://legacy.gsfc.nasa.gov/docs/software/fitsio/}

\medskip
\noindent
(3) compile HeliogLib

Compile and create library under \norh{\tt/soft/helioglib/ver6.2}.

\smallskip
\noindent
(4) compile the synthesis programs

Compile the programs under \norh{\tt/soft/synthesis}.

\clearpage
\appendix

\section{NoRH data}
\label{norhdata}

In this section, the NoRH data is explained in detail
(Table \ref{table:norhdata}).
We use marks that are explained in Table \ref{table:abrebiation}.
\begin{table}
\caption{NoRH data}
\begin{center}
\begin{tabular}{lll}
\hline
pre-fix & contents & directory \\ \hline
ss17,ss34 & raw data (steady mode) & anywhere [{\tt raw/steady}] \\
se17,se34 & raw data (event mode) & anywhere [{\tt raw/event}] \\
sz00 & 'SZ' data &
anywhere [{\tt raw/steady},{\tt data/sz\_update}] \\
ifa,ifs,ifr,ifl,ifz & Full Sun Image & anywhere [{\tt images}] \\
ipa,ips,ipr,ipl,ipz & Partial Sun Image & anywhere [{\tt images}] \\
info & observation time & {\tt data/info} \\
rlphdif & R/L phase difference & {\tt data/rlphdif} \\
tsa,tsz & averaged correlation & {\tt data/tsx} \\
tca,tcz & averaged correlation (only R+L) & {\tt data/tcx} \\
eva,evz & event list & {\tt data/evx} \\
lob & observation log (antenna conditions etc.) & {\tt data/lob} \\
rep & tohban report & {\tt data/rep} \\
\hline
\end{tabular}
\end{center}
[ ] : at the NSRO archive (nsrl-archive)
\label{table:norhdata}
\end{table}

\begin{table}
\caption{abreviation marks used for file names}
\begin{center}
\begin{tabular}{ll} \hline
{\it YY} & last two digits of year \\
{\it MM} & month \\
{\it DD} & day \\
{\it HH} & hour \\
{\it MN} & minute \\
{\it SS} & second \\
{\it LLL} & milli-second \\
{\it \#\#\#} & sequential number \\
{\it S} & schedule ID \\ \hline
\end{tabular}
\label{table:abrebiation}
\end{center}
\end{table}

\subsection{Observation mode of NoRH}
\label{observationmode}

Basically there are two modes of NoRH data recording.
In the {\it steady} mode, the raw data is recorded 
as a {\it frame} after 1-sec integration.
One raw-data {\it file} has 600 frames (i.e. 600 sec) each
and is named with a sequential number.
In the {\it event} mode, the raw data is recorded
as a {\it frame} after 50 milli-seconds (before September 1995)
or 100 milli-seconds (after October 1995) integration.
The event data is recorded when a flare-event occurs on the Sun.
One event-mode {\it file} corresponds to one flare-event
and has almost no limitation on number of frames.

\subsection{What is {\it Schedule} for NoRH ? }
\label{schedule}

The unit of NoRH observation  is called {\it schedule}.
In principle, one day has one schedule. But when some trouble
happens to the observing system, there may be multiple schedules.
The {\it schedule ID} is given to identify each schedule.
They are "date + an alphabet letter". That may be only "date" 
if there is only one single schedule per day. For example,
the schedule ID on July 10, 1992 is "920710" because there was only
one schedule on that day. On the other hand, there were
two schedules "920712a" and  "920712b" on July 12.

\subsection{Raw data (ss17,ss34,se17,se34)}
\label{raw}

\noindent
File name

\begin{tabular}{ll}
{\tt ss17{\it YYMMDD\#\#\#}}  & steady mode, 17GHz \\
{\tt ss34{\it YYMMDD\#\#\#}}  & steady mode, 34GHz \\
{\tt se17{\it YYMMDDHHMNSS}}  & event mode, 17GHz \\
{\tt se34{\it YYMMDDHHMNSS}}  & event mode, 34GHz \\
\end{tabular}

\noindent
The {\it HHMNSS} part in the event data file name 
is the start time of the event.

\medskip
\noindent
Unit of storage

Steady-mode raw data is processed one file per 600 frames (600 seconds), and
event-mode is one file per one event.

\medskip
\noindent
Directory

Anywhere. In NoRH archive, they are put under {\tt raw}.



\subsection{'SZ' data (sz00)}
\label{sz}

The files that contains information on ephemeris and
valid antennas.
(1) Ephemeris data:
solar declination $\delta$ (in arc-degree),
hour angle (in time-sec), apparent solar radius (in arc-sec),
solar {\it p-}angle (in arc-degree),
solar {\it b-}angle (in arc-degree) at JST noon for previous,
present, next days.
(2) Valid antenna: 
In the order of N01 -- N28, E28 -- E01, and W01 -- W28.
0: use when synthesis, 1: unuse.


\noindent  
File name

{\tt sz00{\it YYMMDD}001}

\noindent
Unit of storage

One file per one day

\noindent
Directory  

Anywhere. In NoRH archive, they are put under {\tt raw/steady}.
This file may be updated if some trouble on antennas is found later.
In this case, the file will be put in {\tt data/sz\_update}.




\subsection{Images (ifa,ifs,ifz,ipa,ips,ipz)}
\label{image}

FITS format files that contain the NoRH images.
See Appendix \ref{fits} for the detailed description for the FITS headers,
The unit of intensity in the image is brightness temperature in Kelvin. 

\medskip
\noindent
File name

\smallskip
\begin{tabular}{llll}
  Steady mode &&& \\
  {\tt ifa{\it YYMMDD}\_{\it HHMNSS}} & Full Sun & 17GHz & (R+L)  \\
  {\tt ifs{\it YYMMDD}\_{\it HHMNSS}} &         &       & (R$-$L)  \\
% {\tt ifr{\it YYMMDD}\_{\it HHMNSS}} &         &       &        \\
% {\tt ifl{\it YYMMDD}\_{\it HHMNSS}} &         &       &        \\
  {\tt ifz{\it YYMMDD}\_{\it HHMNSS}} &         & 34GHz & (R+L)  \\
  {\tt ipa{\it YYMMDD}\_{\it HHMNSS}} & Partial & 17GHz & (R+L)  \\
  {\tt ips{\it YYMMDD}\_{\it HHMNSS}} &         &       & (R$-$L)  \\
% {\tt ipr{\it YYMMDD}\_{\it HHMNSS}} &         &       &        \\
% {\tt ipl{\it YYMMDD}\_{\it HHMNSS}} &         &       &        \\
  {\tt ipz{\it YYMMDD}\_{\it HHMNSS}} &         & 34GHz & (R+L)  \\
%  \hlin
%\end{tabular}

  &&& \\
%\smallskip
%\begin{tabular}{llll} \hline
  Event mode &&& \\
  {\tt ifa{\it YYMMDD}\_{\it HHMNSS.LLL}} &  Full Sun & 17GHz & (R+L)  \\
  {\tt ifs{\it YYMMDD}\_{\it HHMNSS.LLL}} &         &       & (R$-$L)  \\
% {\tt ifr{\it YYMMDD}\_{\it HHMNSS.LLL}} &         &       &        \\
% {\tt ifl{\it YYMMDD}\_{\it HHMNSS.LLL}} &         &       &        \\
  {\tt ifz{\it YYMMDD}\_{\it HHMNSS.LLL}} &         & 34GHz & (R+L)  \\
  {\tt ipa{\it YYMMDD}\_{\it HHMNSS.LLL}} & Partial & 17GHz & (R+L)  \\
  {\tt ips{\it YYMMDD}\_{\it HHMNSS.LLL}} &         &       & (R$-$L)  \\
% {\tt ipr{\it YYMMDD}\_{\it HHMNSS.LLL}} &         &       &        \\
% {\tt ipl{\it YYMMDD}\_{\it HHMNSS.LLL}} &         &       &        \\
  {\tt ipz{\it YYMMDD}\_{\it HHMNSS.LLL}} &         & 34GHz & (R+L)  \\
\end{tabular}

\medskip
\noindent
Example \\
{\tt ifa981123\_020533}\hspace{10mm} 
Full-Sun, 17GHz, R+L, Steady 1998-11-23 2:5:33 UT \\
{\tt ipz981123\_020533.824}\hspace{5mm} 
Partial, 34GHz, R+L, Event 1998-11-23 2:5:33.824 UT \\

\noindent
Directory

Anywhere. 
We have daily images, 10min-interval images, event images 
(maximum averaged correlation $>$ 1.5\%)
under {\tt images} in NoRH archive. The synthesis of a 
raw data file ( e.g., ss17... ) results in these image files (e.g.
ifa... and ifs... ).

\clearpage

\subsection{Observation Time (info)}
\label{info}

This is an ASCII-text file that contains the observation time,
and its corresponding frame number.

\noindent
File name

\begin{tabular}{ll}
   {\tt info{\it YYMM}s} & steady \\
   {\tt info{\it YYMM}e} & event
\end{tabular}

\noindent
Unit of storage

One file per one month

\noindent
Directory

{\tt data/info}

\medskip \noindent
Example of Contents

\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
s99030108001 ss17990301001 990301 080023 140022 000001 021600 TRACK
s99030108001 sz00990301001
s99030108002 ss17990301037 990301 140023 151458 021601 026076 TRACK
s99030108002 ss34990301001 990301 080023 151458 000001 026076 TRACK
s99030108002 sl00990301001
s99030108002 sz00990301001
\end{verbatim}\end{minipage}
\smallskip

The 1st, 3rd, and 4th lines are the records for raw-data files and
the 2nd and 6th lines are for 'SZ' files.
From the left: The volume ID of the master CD-ROM for this data,
the first file name of the sequence of raw-data files,
observing date, the time (JST) of the first frame 
in the corresponding data file,
that of the last frame, ID number of the first frame, that of the last frame,
and the recording mode (TRACK means the ordinary observation sequence).
In this example, it means that the data of 1999-3-1 is contained in
the CD-ROM {\tt s99030108001} and {\tt s99030108002}. From the 1st to
the 36th file are in CD-ROM {\tt s99030108001}. These files include
frame 1 to 21600 that correspond to the data from 8:00:23 JST 
to  14:00:22 JST. The CD-ROM {\tt s99030108002} has the data from 14:00:23 JST
to 15:14:58 JST. Each of these CD-ROMS has its own {\tt sz00990301001} file.


\subsection{R/L phase difference (rlphdif)}
\label{rlphdif}

There are 3 files. Each file is valid for the following
term(s).  These files are used in the older version of synthesis
programs. In the newest version of synthesis programs, 
these are no longer necessary. But for C2FITS program, still necessary.

\medskip
\noindent
\begin{tabular}{ll} \hline
   file & valid term \\ \hline
   {\tt sun0628rlphdif}   &     -- 1992-6-28  \\
   {\tt s971101rlphdif}   &     1997-10-30 -- 1997-11-06 \\
                          &     1998-01-21 -- 1998-01-26  \\
   {\tt sun0706\_2rlphdif} &    all days other than above \\ \hline
\end{tabular}
\medskip

\noindent
File name

   {\tt s{\it YYMMDD}rlphdif }

\noindent
Unit of storage

 non-periodically 

\noindent
Directory

{\tt data/rlphdif}



\subsection{Averaged correlation (tsa,tsz)}
\label{tsx}

This FITS file contains:
1) exact time of observation,
2) correlation averaged over the antenna pairs (max is 100\%),
   (R+L) \& (R$-$) components for 17GHz, (R+L) for 34GHz.
3) observation status,
4) intensity.
See Appendix \ref{fits} for the detailed description for the FITS header,

\noindent
File name

\begin{tabular}{lll}
  {\tt tsa{\it YYMMDDS}}  &     17GHz & Steady \\
  {\tt tsz{\it YYMMDDS}}   &    34GHz & Steady \\
  {\tt tsa{\it YYMMDD\_HHMNSS}} & 17GHz & Event \\
  {\tt tsz{\it YYMMDD\_HHMNSS}} & 34GHz & Event
\end{tabular}

\noindent
The {\it HHMNSS} part of event data is the start time of the event.

\medskip
\noindent
Unit of precess

One file per one schedule/event

\noindent
Directory

{\tt data/tsx}




\subsection{Averaged correlation Digest (tca,tcz)}
\label{tcx}

This FITS file contains:
correlation averaged over the antenna pairs (max is unity).
Only (R+L) components.
See Appendix \ref{fits} for the detailed description for the FITS header,

\noindent
File name

\begin{tabular}{lll}
  {\tt tca{\it YYMMDDS}}  &     17GHz & Steady \\
  {\tt tcz{\it YYMMDDS}}   &    34GHz & Steady \\
  {\tt tca{\it YYMMDD\_HHMNSS}} & 17GHz & Event \\
  {\tt tcz{\it YYMMDD\_HHMNSS}} & 34GHz & Event
\end{tabular}

\noindent
The {\it HHMNSS} part of event data is the start time of the event.

\medskip
\noindent
Unit of storage

One file per schedule/event

\noindent
Directory

{\tt data/tcx}



\subsection{Event list (eva,evz)}
\label{evx}

ASCII-text files that contains the lists of events (flares).

\noindent
File name

\begin{tabular}{ll}
   {\tt eva{\it YYMM}}  & 17GHz \\
   {\tt evz{\it YYMM}}  & 34GHz \\
\end{tabular}

\noindent
Unit of storage

One file per one month

\noindent
Directory

{\tt data/evx}

\noindent
Example

\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
   1  1999-04-01  23:00:47    23:11:24  23:02:42    637     23    17.7     0.6 22/ 19
\end{verbatim}\end{minipage}
\smallskip

From the left:
Sequential number, date, start (UT), end (UT), peak (UT),
duration (sec), max. averaged correlation $\times$ 32768
and so on. In this example, there was an event with peak
correlation of $23/32768\approx0.007=0.7\%$ at 23:02:42 UT
with duration of 637 seconds.


\subsection{Observation log (lob)}
\label{lob}

ASCII-text files that contain useful information for
data analysis, e.g., antenna conditions, weather, etc.

\noindent
File name

  {\tt lob{\it YYMM}}

\noindent
Unit of storage

One file per a month

\noindent
Directory

{\tt data/lob}

\noindent
Example

\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
### 99/03/10
   Due to an ice sticked to 84 antenna dishes, data quality is
   not good during the following times (before the sun shined
   and melt the ice):
       Mar. 10, 00:00 UT - Mar.10, 02:30 UT.
\end{verbatim}\end{minipage}


\subsection{Tohban report (rep)}
\label{rep}

Observing tohban's (duty observer) 
weekly reports that has brief description
on Solar activity, significant events on that week.

\noindent
File name

  {\tt rep{\it YYWW}}

\noindent
Unit of storage

one file per one week

\noindent
Directory

{\tt data/rep}

\subsection{Sun tracking table (track\_table)}
\label{track_table}

Information for tracking the Sun at Nobeyama.
They are obtained by using the ephemeris data and
the latitude/longitude of Nobeyama.
The contents are solar declination $\delta$ (in arc-degree),
hour angle (in time-sec), apparent solar radius (in arc-sec),
solar {\it p-}angle (in arc-degree), 
solar {\it b-}angle (in arc-degree) at JST noon.

\noindent
File name

  {\tt track\_table{\it YY}.dat}

\noindent
Unit of storage

one file per one year

\noindent
Directory

{\tt data/ephe}


\section{NoRH FITS header}
\label{fits}

In this section, the regulation of
the FITS header  that is adopted by NoRH data is given.
This is used in the files of image (ifx, ipx), and
averaged correlation (tcx, tsx).

\subsection{Header Regulation}

\noindent
(1) Needed Part

\medskip
\noindent
$\bullet$ The keywords for standard FITS

The keywords below must appear in all FITS files
and have a fixed format.

\hspace*{0.5cm} \begin{tabular}{ll}
{\tt SIMPLE}&: '{\tt T}' if the file subjects to the FITS regulation \\
{\tt BITPIX}&: number of bits and type of the data \\
{\tt NAXIS}&: number of dimensions of the data \\
{\tt NAXIS1}&: number of pixels in x-axis \\
{\tt NAXIS2}&: number of pixels in y-axis \\
\end{tabular}


\medskip
\noindent
$\bullet$ Basic information for NoRH data

The keywords bellow should appear in all FITS files
related to NoRH data.

\noindent
\hspace*{3mm}
$\circ$ Information on observation time

\hspace*{0.5cm} \begin{tabular}{ll}
{\tt STARTFRM} &: the first IDs of used frames \\
{\tt ENDFRM}&: the last IDs of used frames \\
{\tt JST-STRT} &: the start time (JST) of integration for {\tt STARTFRM}  \\
{\tt JST-END} &: the end time (JST) of integration for {\tt ENDFRM} \\
{\tt JST-TIME} &: exact middle time (JST) between the {\tt JST-STRT} 
and {\tt JST-END} \\
{\tt JST-DATE} &: the date (JST) for {\tt JST-STRT}. The format is yyyy-mm-dd \\
{\tt STRT-OBS} &: UT for {\tt JST-STRT} \\
{\tt END-OBS} &: UT for {\tt JST-END} \\
{\tt TIME-OBS} &: UT for {\tt JST-TIME} \\
{\tt DATE-OBS} &: UT for {\tt JST-DATE} \\
\end{tabular}

\noindent
\hspace*{3mm}
$\circ$ Information of data contents

\hspace*{0.5cm} \begin{tabular}{ll}
{\tt OBJECT}&: fixed to {\tt sun} \\
{\tt TELESCOP}&: fixed to {\tt radioheliograph} \\
{\tt ORIGIN}&: fixed to {\tt nobeyama radio obs} \\
{\tt POLARIZ}&: choose from {\tt rcp}, {\tt lcp}, {\tt r+l},
      {\tt r-l}, {\tt l-r}, {\tt r|l}, {\tt (r-l)/(r+l)}, {\tt unknown} \\
{\tt ATT-10DB}&: choose from {\tt 00dB}, {\tt 10dB} \\
{\tt OBS-MODE}&: choose from {\tt fix}, {\tt alt} \\
{\tt OBS-FREQ}&: choose from {\tt 17GHz}, {\tt 34GHz} \\
{\tt FRM-STAT}&: choose from {\tt 1-sec obs}, {\tt event}, {\tt calib} \\
{\tt DATA-TYP}&: brief description of data type, e.g. {\tt cleaned\_map} \\
\end{tabular}

\noindent
\hspace*{3mm}
$\circ$ Information of FITS header version 

FITS header version.  Now the newest is ver 2.0

\hspace*{0.5cm} \begin{tabular}{ll}
{\tt HDRIDENT}&: {\tt 'HeliogFITS 2.0'} \\
\end{tabular}

\bigskip
\noindent
(2) Ephemeris 

\medskip
The keywords bellow should appear in NoRH image files.
These are necessary for obtaining the heliographic coordinates
or the beam patterns.  They are not only the parameters
determined from the date and time, but also those 
local to the Nobeyama site.

\hspace*{0.5cm} \begin{tabular}{ll}
{\tt SOLR}&: apparent radius of the solar disk \\
{\tt SOLP}&: polar angle of the sun \\
{\tt SOLB}&: the heliographic latitude of the solar disk center \\
{\tt DEC}&:  declination of the Sun at Nobeyama \\
{\tt HOURA}&: hour angle of the Sun at Nobeyama \\
{\tt AZIMUTH}&: azimuthal angle of the Sun at Nobeyama \\
{\tt ALTITUDE}&: altitude of the Sun at Nobeyama \\
{\tt ZANGLE}&: zenith angle of the Sun at Nobeyama \\
{\tt PMAT1/2/3/4}&: transformation matrics between the antenna coordinates
   (on the geosphere: \\
                 & antenna north is up) and the solar-disk coordinates
(on the celestial sphere: \\
& solar-north is up)\\
\end{tabular}

\clearpage
\bigskip
\noindent
(3) Image coordinates

\medskip
The keywords bellow should appear in NoRH image files
in order to co-align them with images obtained at other frequencies.
They are basically regulated by the FITS standard.

\medskip\hspace*{0.5cm}
{\tt CTYPE1} / {\tt CTYPE2}:  \\
\hspace*{1.5cm}\begin{minipage}[t]{13cm}
  type of coordinate axis. 
  Usually '{\tt solar-west}' and '{\tt solar-north}', respectively.
  The origin is at the solar disk center.
\end{minipage}

\hspace*{0.5cm}
{\tt CDELT1} / {\tt CDELT2}:
  size of pixel in arcsec

\hspace*{0.5cm}
{\tt CRVAL1/CRVAL2/CRPIX1/CRPIX2}: \\
\hspace*{1.5cm}\begin{minipage}[t]{13cm}
  The coordinate value of center of the {\tt CPIX1}th pixel equals to 
  the {\tt CRVAL1} in coordinate {\tt CTYPE1}. That's same for '...2'.
  The NoRH standard is  \\
    \hspace*{0.5cm}\begin{minipage}[t]{10cm}
    {\tt CRVAL1} = 0.00  (fixed) \\
    {\tt CRVAL2} = 0.00  (fixed) \\
    {\tt CRPIX1} = 'x' of the pixel for the solar disk center in the image  \\
    {\tt CRPIX1} = 'y' of the pixel for the solar disk center in the image  \\
    \end{minipage} \\
  In case of partial images (ipx), CRVAL1 and CRVAL2 may be
  larger than the size of the image or may have negative values.
\end{minipage}

\bigskip
\noindent
Note that, in the FITS regulation, the {\it center of the pixel} 
is the origin of the position. Be careful when you 
try to coalign with the image  described with a coordinate
which has its origin at the {\it edge of the pixel}.
%
The distance (in arcsec) of the image center from 
the Solar disk center is given as \\
\hspace*{3cm}x-offset = 
({\tt NAXIS1}/2+0.5-{\tt CRPIX1})*{\tt CDELT1}+{\tt CRVAL1} \\
\hspace*{3cm}y-offset = 
({\tt NAXIS2}/2+0.5-{\tt CRPIX2})*{\tt CDELT2}+{\tt CRVAL2} \\

\bigskip
\noindent
(4) Parameters for each synthesis program

Parameters for synthesis should be given in order to
make it possible to re-synthesize with these.
Although they may be diffferent from one program to another,
some keywords are common.
They may be input parameters for synthesis \\
\hspace*{5mm}$\circ$ what program is used for synthesis, \\
\hspace*{5mm}$\circ$ parameters for calibration (e.g. used frame ID), \\
\hspace*{5mm}$\circ$ parameters for synthesis itself, 
(CLEAN parameters etc.) \\
and output on synthesis \\
\hspace*{5mm}$\circ$ value of an indicator variable for CLEAN results. \\
%
The following keywords 
are recommended to be included at least.


\hspace*{0.5cm} \begin{tabular}{ll}
{\tt PROGNAME}&: The format is arbitrary \\
%\end{tabular}
%
%\hspace*{0.5cm} \begin{tabular}{ll}
{\tt NFRCAL}&: number of frames used for calibration \\
{\tt CRITER}&: CLEAN criterion \\
{\tt SOLR-FAC}&: ratio of the radio to optical solar disk radius \\
{\tt MBEAMC}&: main beam correction \\
%\end{tabular}
%
%\hspace*{0.5cm} \begin{tabular}{ll}
{\tt NCOMPO}&: number of CLEAN conponents  \\
{\tt DDOFF1}&: x-offset of the center of the dirty solar disk \\
{\tt DDOFF2}&: y-offset of the center of the dirty solar disk \\
{\tt DSKBR}&:  brightness of the dirty solar disk \\
{\tt BUNIT}&:  unit of the intensity of the image, usually brightness 
temperature in Kelvin (K). \\
\end{tabular}


\noindent
(5) Others

Other keywords could be added.

\subsection{Example of Header}

\noindent
(1) Needed Part

\noindent
$\bullet$ The keywords for standard FITS

\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
SIMPLE  =                    T / file does conform to FITS standard
BITPIX  =                  -32 / number of bits per data pixel
NAXIS   =                    2 / number of data axes
NAXIS1  =                  512 / length of data axis   1
NAXIS2  =                  512 / length of data axis   2
\end{verbatim} \end{minipage}\medskip\\

\noindent
$\bullet$ Basic information for NoRH data

\noindent
$\circ$ Information on observation time

\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
DATE-OBS= '1998-05-09'         /
TIME-OBS= '03:20:23.754'       /
STRT-OBS= '03:20:21.254'       /
END-OBS = '03:20:26.254'       /
JSTDATE = '1998-05-09'         /
JSTTIME = '12:20:23.754'       /
JST-STRT= '12:20:21.254'       /
JST-END = '12:20:26.254'       /
STARTFRM=                16499 /
ENDFRM  =                16503 /
\end{verbatim} \end{minipage}\medskip\\


\noindent
$\circ$ Information of data contents

\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
POLARIZ = 'r+l     '           /
ATT-10DB= '00dB    '           /
OBS-MODE= 'alt     '           /
OBS-FREQ= '17GHz   '           /
FRM-STAT= '1-sec obs'          /
DATA-TYP= 'cleaned_map'        /
OBJECT  = 'sun     '           /
TELESCOP= 'radioheliograph'    /
ORIGIN  = 'nobeyama radio obs' /
\end{verbatim} \end{minipage}\medskip\\

\noindent
$\circ$ Information of FITS header version 

\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
HDRIDENT= 'HeliogFITS 2.0'     /
\end{verbatim} \end{minipage}\medskip\\

\noindent
(2) Ephemeris

\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
SOLR    =               952.22 / optical solar radius (arcsecond)
SOLP    =             -22.5235 / solar polar angle (degree)
SOLB    =              -3.3307 / solar b0 (degree)
DEC     =              17.2807 / declination (degree)
HOURA   =              2270.83 / hour angle (second)
AZIMUTH =              27.7610 / azimuth (degree)
ALTITUDE=              70.3056 / altitude (degree)
ZANGLE  =              23.5280 / zenithangle (degree)
PMAT1   =              0.98640 / projection matrix
PMAT2   =              0.09448 / projection matrix
PMAT3   =             -0.04883 / projection matrix
PMAT4   =              0.94981 / projection matrix
\end{verbatim} \end{minipage}\medskip\\

\noindent
(3) Image coordinates


\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
CRVAL1  =                 0.00 / arcsec
CRVAL2  =                 0.00 / arcsec
CRPIX1  =               257.00 /
CRPIX2  =               257.00 /
CDELT1  =              4.91106 / arcsec
CDELT2  =              4.91106 / arcsec
CTYPE1  = 'solar-west'         /
CTYPE2  = 'solar-north'        /
\end{verbatim} \end{minipage}\medskip\\

\clearpage
\noindent
(4) Parameters for each synthesis program

\noindent
$\bullet$ example for Hanaoka

\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
PROGNAME= 'snap2d17 v5.1  Y. Hanaoka' /
BUNIT   = 'K       '           / disk = 10000 K
SOLR-FAC=              1.01250 / radius correction factor
NFRCAL  =                    1 / number of calibration frames
CRINPUT =                -0.50 / clean criterion input
MBEAMC  = 'yes     '           / main beam correction
DISKRSTR= 'yes     '           / disk restoration
DDOFF1  =               -12.77 / x-offset of the dirty disk
DDOFF2  =                10.68 / y-offset of the dirty disk
DDCORR  =               0.9631 / correlation between dirty disk and model
DSKBR   =             37145.51 / brightness of the dirty disk
CRITER  =             24384.39 / clean criterion
NCOMPO  =                 1050 / number of clean components
\end{verbatim} \end{minipage}\medskip\\

\noindent
$\bullet$ example for Koshix

\hspace*{0.5cm}\begin{minipage}[t]{15cm}\small \begin{verbatim}
PROGNAME= 'snap2d51_koshix_vfast' /
FRAME   =                16501 /
ICAL    =                    3 / integration for calibration
ITGR    =                    3 / integration for restoration
ICLN    =                    3 / integration after restoration
BUNIT   = 'k       '           / disk = 10000 K
CRITER  =               3000.0 / CLEAN criterion
SOLR-FAC=              1.01250 / radius correction factor
GAINP   =                0.020 / CLEAN loop gain for estimation of sky and disk
GAINE   =                0.200 / CLEAN loop gain
TRIM    =                0.800 / CLEAN trim level
NCOMPO  =                66143 / number of CLEAN components
DDOFF1  =                  0.5 / x-offset of the dirty disk
DDOFF2  =                  0.9 / y-offset of the dirty disk
NCLNYN  = 'yes     '           / negative CLEAN
JCIMYN  =                    1 / jitter - add/sub - integration
PJIMYN  =                    1 / projection - integration
MBEAMC  = 'yes     '           / main beam correction
\end{verbatim} \end{minipage}\medskip\\


\subsection{Implimentation to subroutines}

Subroutines are given in {\tt soft/helioglib}
in order to write the above header to NoRH FITS files.

1. For {\it Needed} part, use subroutine {\tt puthdr}.

2. For {\it Ephemeris} part, use subroutine {\tt putoep}.

3. For {\it Coordinate} part, use subroutine {\tt putcor}.

4. For parameters of each synthesis program, make an
   adequate subroutine for its own. 


\clearpage

\section{NoRH data archive: anonymous FTP}
\label{archive}

The Nobeyama Solar Radio Observatory (NSRO/NAOJ) has prepared
the anonymous FTP server for the NoRH data archive.
The URL is

\bigskip
{\tt ftp://solar-pub.nao.ac.jp/pub/nsro/norh}
\bigskip

If you need to transfer a large amount of data ,
please contact

\bigskip
{\tt nsro-service@solar.nro.nao.ac.jp}

We will make and mail a CD-ROM for you.
The network capability in Nobeyama is limited.

\section{Acknowledgement}

We thank the following people.
SolarSoftware is a software package for analysis of Solar
Data on IDL. That is supported under various
NASA contracts (SXT/EIT/MDI/TRACE/YPOP etc.) and is all in
the public domain.
Yohkoh is an international project for solar observation 
by ISAS in Japan, NASA in the U. S. and SERC in the U. K.
GOES data are supplied
courtesy of NOAA/NGDC from www.ngdc.noaa.gov.
The utility program C2FITS is developed by Dr. T. Bastian at NRAO
and is improved by Dr. S. White (U. Maryland).
The JavaScript program in our NoRH Web site is developed
by Dr. D. Zarro at NASA/GSFC.
IDL is a product by Research System Inc.
We also thank
Dr. S. Pohjolainen from HUT, Metsahovi Radio Observatory for
reading and checking the manual.

\section*{References}

Dulk, G. A., 1985, ARAA, {\bf 23}, 169 \\
Hanaoka, Y., et al., 1994, Proc. of Kofu Symp., 35 \\
Nakajima, H., et al., 1994, Proc. of the IEEE, {\bf 82}, 705 \\
Nishio, M., et al., 1994, Proc. of Kofu Symp., 19 
Ramaty, 1969, ApJ, {\bf 158}, 753 \\

\end{document}
