The YOHKOH data archive is created on Unix computers at ISAS, Japan, using standard archiving tools from the Unix operating system. All archiving is done on 8mm Exabyte tapes. Nominally, each archive tape will contain one calendar week (always beginning with Sunday) of reformatted data and all the software used to access the data. Tapes are created as soon as a complete week of the data are assembled; but, because data are collected from two sources (KSC in Japan and NASA's DSN) some delay is expected. The tapes are then sent to California for duplication and distribution to the U.S. Co-I's. At ISAS the archive tapes are copied to MO disk.
Archive tapes can be read on Unix and VMS machines such as SUN, SGI, and Digital using software package written in Interactive Data Language (IDL).
For more information on reading archive tapes see the GO_RDTAP description in the User's Guide.
YOHKOH archive tapes contain a tape directory, reformatted data and software. Tapes are created on DIGITAL's Unix (Ultrix) system using `cp', `cpio' and `tar' archiving utilities. Reformatted data files and the weekly files are all copied to tape using the `cpio' utility. The software archive is copied to tape with the `tar' utility. Since, the software archive comprises several different directory trees the `tar' utility was the logical choice because it allows one preserve these directory structures during restore operations. Archive tapes will nominally contain a single calendar week (always beginning with Sunday) of reformatted data. (Where each reformatted file contains data from a single orbit which spans approximately 90 minutes.) This calendar week is given a number (week number: 1-53) which is then encoded into the name of the tape in the format `yy_wka.xx', where `yy' is the year, `wk' is the week number, `a' is the media number (always ``a'' for tapes, but can be ``b'' for other media, such as MO disks), `xx' is the revision number or level of the archive tape.
The detailed contents of a YOHKOH data archive tape begins with two directory files in different formats (ASCII and binary), followed by a series of `cpio' data archive files, and lastly a `tar' software archive file.
Picture Omitted
Structure of the data and software archive tape. Each
cpio archive file contains only those reformatted data that
share the same file ID (e.g. archive file 2 contains files from
the file ID: 911201.1545, file 3 would contain files with file ID
911201.1715).
The tape directory file lists the contents of each tape. The file
contains general information such as when the tape was made, the name of
the tape, the number of `cpio' archive files, the first and last data
file identification (fileID) contained within the `cpio' archive, and a
breakdown on the contents of the software `tar' archive file giving
names and sizes of embedded `tar' files. The tape directory also has
two detailed tables. The first of which tabulates the weekly files
present within the first `cpio' archive and the second tabulates the
`orbit' fileID and the sizes of each reformatted file (e.g. ada, bda,
cba, hda, sfr, spr, wda) for each `cpio' archive file. This last table
is very useful for identifying whether a given file is on a tape.
The reformatted data are placed on tape with the help of the Unix
archiving utility `cpio' which allows a specified list of files to
inserted into a single archive file. Using this utility we have
bundled the data by placing files with the same data file identification
or fileID (such as 911201.1654, which corresponds to the date 1-Dec-91
at 16 hours and 54 minutes) together into a single archive file and
copied to tape. Each fileID is unique and represents one orbit of data.
Since there are about 16 orbits per day, each tape could have 112 + 1
different `cpio' archive files. The additional archive file is for the
first `cpio' file which only contains the weekly files such as the
observing log file (obs*) and the pointing file (pnt*).
Even though the software is placed on the tape, it is best to obtain the software across
the network. See Appendix for more details.
There are three IDL utility programs which access the archive tapes. An
IDL procedure called MKTAP to create archive tapes, another procedure
called RDTAP to read any of the various sections or parts of sections
of the tape (see Figure), and finally a robust procedure called
YOHKOH_SW to read and restore just the software archive files. The
YOHKOH_SW procedure is very useful and is recommended for creating a
software environment which would be quite similar to the ISAS computing
environment. Documentation for RDTAP and MKTAP are given below and
the 'yohkoh_sw' documentation can be found in separate guide which is
attached to this users guide.
When using RDTAP to read and extract data from the archive tapes be
aware that the newly created disk files are always placed in the users
default directory. RDTAP has an on-line brief help information
listing to aid the unfamiliar user. To activate this feature type
RDTAP without any parameters at the IDL prompt. To get a listing of
the contents of the tape one can either use the RDTAP utility with the
option to extract the tape directory files
The general calling sequence for RDTAP is:
In using the tape directory file to review tape contents and select data
files to be extracted from the tape, find the final table within the
file which tabulates the fileID and file prefix. The heading of table
reads FileID and cpio, followed by all of the valid file prefixes. To
find a given file with the table, match the fileID with the
corresponding row within the FileID column and then match the file
prefix with the corresponding prefix column. A non-zero entry for the
size of the file (bytes) indicates that the file is on the tape.
For VMS systems, there are two DCL commands which must be done prior to
entering IDL in order to access the tape drive. Issue the following two
commands before starting IDL:
Any tape read errors encountered while
reading the tape are flagged to the current session and an attempt is
made to continue reading the tape. All file(s) which were not restored
as a result of the tape read errors are logged to a tape error log file
called `rdtape.log'.
In general, recovering unread file(s) may be difficult. If an error
resulted in the loss of two or more consecutive files one can first
attempt to restart the file extraction beginning with the second file in
the `rdtape.log'. If this procedure is successful, it is most likely
that the first file will be unreadable, however one should still attempt
to re-read the file as the error may have been due to dust or other
contaminates on the tape. If the error log contains several of these
situations of two or more consecutive file losses repeat the above
procedure for each case.
Tapes are created with the IDL procedure MKTAP. A blank
8mm tape should be in the desired tape drive before one starts the
procedure. The nominal mode starting this procedure is to specify the
device as a parameter:
As final comment there are a number of constraints one should be aware
of when creating archive tapes. First, one must have WRITE privilege to
the data directory. This is necessary since MKTAP creates a script
file and two versions of the tape directory files in the data directory.
Secondly, an observing log with the name which corresponds to the dates
of the data archived must be on the directory or the program will prompt
the user for its name.
The following are a list of the Yohkoh principle investigator and
co-investigator sites which have the Yohkoh software and database
package. The node names and a contact person are listed.
This next table shows the various other institutions which are not primary or
co-investigator institutions and which have the Yohkoh package.
Department of Astronomy, Kyoto
A list of the most of the computer nodes which have the Yohkoh software
is listed here. To verify that the lists are accurate, we recommend
logging into sxt, isass0 or flare2 and looking at the file /etc/hosts.
Mees Solar Observatory (MSO) is located on Haleakala, Maui, at 165E
longitude and 20N latitude. MSO instrument operation hours vary from
1800-0300 UT in December to 1630-0400 UT in June. A searchable catalog
called SPAM (Spectroscopy and Polarimetry at Mees) contains MSO data logs
(not data). Some MSO data are available on line. Other MSO data can be
obtained through the Data Use Coordinator, canfield@mamane.ifa.hawaii.edu.
SPAM logs (and searchable attributes, in addition to date, day of year,
and time) include: MSO Log (instrument, NOAA AR, data type, observing
setup), SEL Event List (NOAA AR, X-ray Class), SEL Region Report (NOAA
AR), Yohkoh Orbit Summary, Yohkoh SXT Quiet Mode PFI Observations
(latitude, longitude, X-ray and optical image size), Yohkoh Flare
Observations (latitude, longitude, specific channel counts or ratios).
SPAM runs on a Sun Unix workstation at MSO, and is available over
Internet. Simply access (e.g., telnet) koa.ifa.hawaii.edu (128.171.167.1)
from any vt100, Sun, or xterm emulator. Log on as spam (lower case);
there is no password. New users are asked to read release notes and
hints.
Vector magnetograms from the MSO Stokes Polarimeter are available on line
for about a month after acquisition. These data are available by
anonymous ftp over Internet. Use ftp koa.ifa.hawaii.edu, log in as
anonymous, provide your name as the password, and then respond to the ftp
prompt with cd pub/stokes. Use get to obtain a copy of the README file
for further information and conditions for data use.
This program provides interactive computer controlled viewing of
the library of movie sequences recorded on the ISAS SONY laser
disks. The user must be logged on to the isass3 computer (remote
logon from another ISAS workstation is fine) in order to use the SONY laser disk player.
To run the software the user must log on to isass3. The calling sequence
is:
In addition to this basic mode, VIDEO_MENU may be called with
a keyword vcr set which allows non-interactive playing of frame
sequences specified in an input file. This mode of operation is
convenient for demonstrations and for making video tape copies of
selected sequences of movies.
The centerpiece of the laser disk movie
catalogue is the full disk movie which covers the duration of the
mission. However, there are over 100 entries in the menu, corresponding
to a variety of interesting sequences showing flares, large scale
coronal transients, and theoretical modeling.
The video title pages may be prepared by using an IDL program called
VIDEO_TITLE. First, you must prepare an ASCII control file that
specifies what the title pages should contain. The IDL routine reads
this file and writes the text to a Z-buffer window (using ordinary
XYOUTS commands) and then reads it back into an array that can be
stored in a *.genx file. The font type and size and placement
can be easily adjusted.
Some example calls are:
The control file specifies the position on the screen, the text, the size
and thickness of the characters. Different fonts can be used also.
A portion of that file is shown here:
The outfile = switch will cause the title pages to be written to
a *.genx file that can be written to the ISAS Sony Laser disk
using GO_NVS5. If you want the background color to be blue,
make sure that you specify color table 1 in GO_NVS5.
For the SFD option, the default increment is 10 (process 10 images at a time).
This is good if no one else is using the
workstation at the same time.
If the /sfd switch is given, go_nvs5 will prompt the user with the list of
files which are in the /yd1/sfd directory.
For the GENX option, the array will not be autoscaled (it should be a byte
type). If the number of images in the genx file is large, IDL may run out of core.
In that case, try increment=1. The program will prompt the user for the
GENX filename.
The above procedure is for starting from scratch. If you have just completed
a run and the Sony frame number has not been changed, then just type:
MK_VCR is an IDL procedure which can be used to control the Sony Laserdisk
recorder. In this way sequences can be displayed easily in order to make
VCR video recordings.
The MK_VCR procedure reads an ASCII file (described) below and then calls
sonyloop to actually control the laser disk player.
You can preform a simple test to see if things are working correctly
by typing:
If things look like they are working correctly, you can then try mk_vcr.
To get a template of the file the mk_vcr will read, execute the following
Unix command to copy the example file to your own directory:
If you want to make a movie, you could try the following IDL program:
The file has some descriptions about how to change it. Basically,
the lines in the file look like the following:
The following is a guide to record and play laser disk movies at LPARL.
The program VIDEO_MENU described in section E.1 is not available
at LPARL during the writing of this guide, however it may exist now. See one of
the software engineers to see if it is available.
A.4 Access Software
1.4.1 Reading Tapes (RDTAP)
IDL > rdtap, device, /dir
which creates the two files called `xadyy_wkd.xx' (ASCII) and
`xbdyy_wkd.xx' (binary). An alternative method is to simply copy the
first file (the ASCII file) from the tape to disk via DCL or Unix
commands (e.g. for VMS mount/for mt: and copy mt: tapedir.lis or for
Unix cp dev tapedir.lis). When extracting the binary data files from
tape to disk the files are restored without any byte swapping. This
keeps the files in their original format so that any byte swapping, if
necessary, is handled automatically and transparently to the user at the
time the disk files are read by the analysis software. Note that the
tape is rewound at the beginning of each RDTAP request, so it is more
efficient to specify all requests within a single RDTAP command than it
is to make several smaller requests. Also the requested list
of the files need not be in order of appearance on the tape as the
routine will sort all input requests for the most efficient extraction.
IDL > rdtap, dev [, file, prefix= prefix, fileID= fileID, week=week, $
IDL > dir=dir, range= range, software= software]
Where the optional parameters are enclosed within brackets (note that
when calling RDTAP with the dev parameter specified at least one other
optional parameter must also be included. In general, all non-switch
parameter inputs have a string data-type (e.g. dev = `/dev/nrmt0h'). The
definitions of the parameters is as follows:
dev is the device name (Ultrix example: '/dev/nrmt0h').
file is a list of requested file names (e.g. spr910925.1020).
prefix is a list of requested file prefixes.
fileID is a list of requested fileIDs (e.g. 910925.1020).
week is a list of weekly files to restore.
dir is a switch to restore the tape directory file.
range is a switch to create a list of files from input.
soft* is a switch to restore the software tar file to disk.
Some examples are:
IDL > rdtap, dev, ['spr911029.0300','bda911030.0440']
IDL > rdtap, dev, prefix=['spr','sfr'] or rdtap, dev, prefix=['s']
IDL > rdtap, dev, fileID=['911029.0900']
IDL > rdtap, dev, prefix='spr',fileID='910923.1234', week='all'
IDL > rdtap, dev, prefix='s', fileid=['911101.0200','9111015.0900'],/range
IDL > rdtap, def_tapd(1), /software, /dir
The first example restores just the requested spr and bda files.
The second example restores ALL SXT files from the tape (could take about two hours).
The third example restores all archived files of this fileID.
The fourth example restores just the spr910923.1234 file and all weekly files.
Note, that week=[`obs', `pnt', `fem', `evn'] will restore any
of these files found on the tape (i.e. if FEM and EVN files were
missing, only OBS and PNT files would be restored.
The fifth example restores sfr and spr files between orbits dated 1-Nov at 02:00 UT and
15-Nov at 09:00 UT.
The last example decompresses the
software archive file and restores the tape directory files
to the default directory. Using the DEF_TAPD function
to specify the device name by selecting the device number
is a simple way to get the correct device name.
1.4.2 Tape Reading on VMS
$ Allocate tapeDrive mt* where tapeDrive refers to the 'mu'
device (example: 'mub0') and mt*
refers to mt0 thru mt9, pick one.
$ Mount/FOREIGN mt* this mounts the tape to the 'logical device'
name mt* (again mt0 thru mt9).
Then enter IDL. Assuming one selected `mt0' as the logical device name
for the tape drive in the allocation command, the valid rdtap command
restoring the tape directory files would look like:
IDL > rdtap, def_tapd(0), /dir
1.4.3 Tape Read Errors
1.4.4 Writing Tapes
IDL > mktap, dev
where, dev can be either a string-type variable such as `/dev/nrmt0h' or
an integer 0, 1, 2, etc., which specifies the device number. The
procedure can also be started with out a device specified. However, in
this case the program assume the tape is in one of the follow defaults
devices (system dependent): `/dev/nrmt0h' for Ultrix systems,
`/dev/rmt/tps0d6nrnsv' for IRIX systems, and `/dev/nrst0' for SUN
systems. The first question one must answer is the name of the data
directory (note this is NOT the path). For example, if the path to the
archive data is `/yd4/92_12a' then the data directory is `92_12a'. The
second and typically last question asks whether to archive all files or
part of the files within the data directory. After answering this final
question a script file called `mktape.com' and two tape directory files
xbdyy_wka.xx (binary version) and xadyy_wka.xx (ascii version) are
created in the data directory. It is important to note that the file ID
of the tape directory files (xad and xbd) is the same as the name of the
tape which will hold these files. This completes the IDL procedure
MKTAP. To make the tape one types the following command:
% source mktap.com
MKTAP also has a number of switches which can be specified with the
MKTAP command to allow the program to run in different modes. Listed
below are a few examples, see the program header to MKTAP for a complete
list:
IDL > mktap, 1, datadir='91_50a,91_51a'
will use tape drive `/dev/nrmt1h' on Ultrix systems, and archive weekly
files from sub-directory `91_50a' and all requested reformatted data
from both sub-directories.
IDL > mktap, 1, datadir='91_50a,91_51a', /alldata
same as above
command, except that there will be no prompt for which
reformatted files to place on the tape as all reformatted data from
both directories will be archived.
B. Institutes and Nodes with the Yohkoh Package
B.1 List of Institutes
Institute Computer Nodes Contact Person
Institute of Space and isass0 thru isass4 Freeland
Astronautical Sciences (ISAS) flare1 thru flare12 Shimizu
isasxa thru isasxc Bentley
isass6 Hudson
Lockheed Palo Alto Research sxt0 thru sxt6, sag Freeland
Laboratory (LPARL)
Montana State University sxt4, msusxt6 Acton
University of Hawaii akala, akoko, maile Canfield
hau, iliahi, wiliwili
University of California, Berkeley sunspot McTiernan
Stanford University flare, panache Klimchuk
Solar Physics Research noao Harvey
Corporation (SPRC)
National Astronautical Observatory spot Tsuneta
of Japan (NAOJ)
University of Tokyo neptune Khan
Mullard Space Science MSSL Cluster Bentley
Laborartory (MSSL)
Rutherford Appleton solg1,RLSAC? Phillips
Laboratory (RAL)
Naval Research Laboratory (NRL) aspen,dogwood,sola Mariska
solb
University of Alabama at Huntsville nessie Mariska (NRL)
University of Birmingham ?? Simnett
Solar Data Analysis Center (GSFC) umbra,sdac Gurman,Zarro
California Institute of Technology sundog Zirin,Lim
NSSDC (GSFC) ?? Batchelor
Marshall Space Flight Center golem, golem2 Porter
University of Glasgow astro? Norman?
Harvard-Smithsonian Center for darmok? Kline?
Astrophysics
National Center for Atmospheric riker Stanger
Research (NCAR/HAO)
Harvard University daystrom Bookbinder
Stanford University quake, kilohoku Milford,Gethyn
Space Environment Laboratory, NOAA seldmc,sunspot McAllister,Bornmann
?? Kawai
University
Geophysical Institute, Kyoto step4ku Yatagai
Unversity
CRL - Akioka planet Akioka
CRL - Marubashi? ?? ??
Shibaura? Institute of Technology ogwl Sabah
Nagoya ? ?? Kato
Nobeyama ? ?? ??
Astronomical Institute, Czech Republic 147.231.24.1 Farnik B.2 List of Node Names and Numbers
DECNET Internet Machine
SAG 24.131 192.68.162.134 (sag.space.lockheed.com) DEC-VMS
SXT 24.134 192.68.162.107 (sxt.space.lockheed.com) SGI-Unix
SXT1 24.362 192.68.162.100 (sxt1.space.lockheed.com) DEC-Ultrix
SXT2 24.365 192.68.162.109 (sxt2.space.lockheed.com) DEC-Ultrix
SXT3 24.366 192.68.162.110 (sxt3.space.lockheed.com) DEC-Ultrix
SXT4 192.31.215.58 (sxt4.oscs.montana.edu) DEC-Ultrix
SXT6 192.68.162.158 (sxt6.space.lockheed.com) DEC-Ultrix
spot 133.40.2.120 (spot.mtk.nao.ac.jp) SUN
neptune 133.11.3.23 (neptune.astron.s.u-tokyo.ac.jp) SUN
ISASS0 40.932 133.74.8.100 (isass0.solar.isas.ac.jp) DEC-Ultrix
ISASS1 40.933 133.74.8.101 (isass1.solar.isas.ac.jp) DEC-Ultrix
ISASS2 40.934 133.74.8.102 (isass2.solar.isas.ac.jp) DEC-Ultrix
ISASS3 40.935 133.74.8.103 (isass3.solar.isas.ac.jp) DEC-Ultrix
ISASS4 40.936 133.74.8.104 (isass4.solar.isas.ac.jp) DEC-Ultrix
ISASS6 133.74.8.106 (isass6.solar.isas.ac.jp) SUN
ISASXA 40.927 133.74.8.110 (isasxa.solar.isas.ac.jp) DEC-VMS
ISASXB 40.928 DEC-VMS
ISASXC 40.929 DEC-VMS
FLARE1 133.74.8.1 (flare1.solar.isas.ac.jp) SUN
FLARE2 133.74.8.7 (flare2.solar.isas.ac.jp) SUN
FLARE3 133.74.8.3 (flare3.solar.isas.ac.jp) SUN
FLARE4 133.74.8.4 (flare4.solar.isas.ac.jp) SUN
FLARE5 133.74.12.94 SUN
FLARE6 133.74.8.6 (flare6.solar.isas.ac.jp) SUN
FLARE7 133.74.8.87 (flare7.solar.isas.ac.jp) MIPS
FLARE8 133.74.8.88 (flare8.solar.isas.ac.jp) MIPS
FLARE9 133.74.8.89 (flare9.solar.isas.ac.jp) MIPS
FLARE10 133.74.8.90 (flare10.solar.isas.ac.jp) MIPS
FLARE11 133.74.8.91 (flare11.solar.isas.ac.jp) MIPS
FLARE12 133.74.8.92 (flare12.solar.isas.ac.jp) MIPS
FLARE13 133.74.8.93 (flare13.solar.isas.ac.jp) MIPS
FLARE14 133.74.8.94 (flare14.solar.isas.ac.jp) MIPS
FLARE15 133.74.8.95 (flare15.solar.isas.ac.jp) MIPS
MSSL 19.253 DEC-VMS
MSSLV1 128.40.70.62 (msslv1.mssl.ucl.ac.uk) VMS-4000
MSSLV2 128.40.70.63 (msslv2.mssl.ucl.ac.uk) VMS-4000
MSSLVB 128.40.70.70 (msslvb.mssl.ucl.ac.uk) VMS-3100
MSSLA1 128.40.70.58 (mssla1.mssl.ucl.ac.uk) VMS-3000
ssd0 128.60.8.1 (ssd0.nrl.navy.mil) VAX
aspen 128.60.8.72 (aspen.nrl.navy.mil) SUN
dogwood 128.60.108.102 (dogwood.nrl.navy.mil) SUN
sola 128.60.8.41 (sola.nrl.navy.mil) SUN
solb 128.60.8.42 (solb.nrl.navy.mil) SUN
nessie 146.229.9.11 (nessie.optics.uah.edu) SUN
koa 128.171.167.1 (koa.ifa.hawaii.edu) SUN?
mamane 128.171.2.2 (mamane.ifa.hawaii.edu) SUN
sunspot (sunspot.ssl.berkeley.edu) SUN?
star 36.10.0.5 (star.stanford.edu) ???
flare 36.14.0.166 (flare.stanford.edu) DEC-Ultrix
panache 36.14.0.51 (panache.stanford.edu) DEC-Ultrix
ogwl (ogwl.se.shibaura-it.ac.jp) ???
setp4ku (step4ku.kugi.kyoto-u.ac.jp) SUN
riker (riker.hao.ucar.edu) SGI
darmok (darmok.harvard.edu) ???
astro (astro.glasgow.ac.uk) ???
sundog 14.905 131.215.139.154 (sundog.caltech.edu) VMS
umbra 128.183.57.24 (UMBRA.gsfc.nasa.gov) DEC-Ultrix
NOTE: To go from DECNET xx.yyy convention to the single node number
notation, take the xx portion, multiply by 1024, and add `yyy'.
So SAG becomes 24*1024 + 131 = 24707::
C. Accessing the University of Hawaii SPAM Database
D. Accessing the Optical Solar Data of NAOJ
1. Introduction
This document describes how to make access to various optical data of
the sun obtained at the National Astronomical Observatory of Japan (NAOJ).
>From workstations which support the X-window and are connected to NAOJ via
network, you may log-in to our workstation
'spot' (spot.mtk.nao.ac.jp, IP-address=133.40.2.120),
under the username 'guest'. The password can be obtained by sending
an e-mail request to either one of the following.
sakurai@spot.mtk.nao.ac.jp (T.Sakurai)
ichimoto@spot.mtk.nao.ac.jp (K.Ichimoto)
For remote users it would be more convenient to transfer the data and
the software to your own workstation and run the software locally.
The IDL package should be installed on your workstation. Files can
be transferred by anonymous ftp on 'spot'. After you are connected to
'spot' via ftp, enter 'anonymous' as the username. For password prompt,
you are requested to enter your name, which will be recorded.
These data can be utilized freely in your data analysis. If you write
a paper or give a talk by using these data, you are requested to consult
with us in terms of co-authorship.
For technical details, please contact:
Norikura heliograms/filtergrams : K.Ichimoto, K.Kumagai
Flare Telescope magnetograms/Dopplergrams: K.Ichimoto, T.Sakurai
Okayama magnetograms : T.Sakurai
H-alpha full-disk images : Y.Suematsu, N.Tanaka
These people can be accessed by e-mail at <name>@spot.mtk.nao.ac.jp.
In any case, only representative data (a few images per day)
are provided on-line. Once you figure out that the data you are
interested in are in archive tapes, you are encouraged to visit
NAOJ, recover the data from tapes, and make use of them.
2. Observing Instruments
This section briefly describes the sources of data, namely the optical
observing facilities currently being operated at NAOJ.
2.1 Mitaka Campus
(a) H-alpha flare patrol
optics: 4cm refractor + Halle H-alpha filter
field of view: full disk
pixel size: 4"
form of data: digital images of H-alpha line center
image cadence: one minute
recording media: digital audio tape
(b) The Solar Flare Telescope
This is made of four telescopes T1-T4.
field of view: 340" x 320"
pixel size: 0.66"
(T1) vector magnetograph
optics: 20cm refractor + birefringent filter (band width=1/8A)
form of data: digital I,Q,U,V intensities of Fe I 6303A line
image cadence: 3 minutes
recording media: digital audio tape
(T2) continuum telescope
optics: 15cm refractor + broad-band filters
form of data: analog images taken mostly at the wavelength of g-band
image cadence: video rate
recording media: SVHS video tape
(tapes are recycled unless no notable events are found)
(T3) H-alpha telescope
optics: 15cm refractor + Zeiss H-alpha filter
form of data: analog images of H-alpha line center
image cadence: 10 seconds
recording media: laser video disk
(T4) Dopplergraph
optics: 20cm refractor + birefringent filter (band width=1/5A)
form of data: digital I,V,Doppler shifts of Fe I 6337A line
image cadence: 3 minutes
recording media: digital audio tape
(c) STEP Full-Disk Magnetograph (STEP=Solar Terrestrial Energy Program)
20cm heliostat + 6cm refractor + birefringent filter
field of view: full disk
pixel size: 5"
form of data: digital I,V,Doppler shifts of Fe I 5324A line
image cadence: (the instrument is now under testing)
recording media: digital audio tape
2.2 Norikura Coronagraph Station
(a) Automated Digital Coronagraph
optics: 10cm coronagraph + interference filters
field of view: 2600" x 2400"
pixel size: 5"
form of data: digital images of the corona in the following wave bands
wavelength band width
5303A 3A
He D3 4A
H-alpha 3A
continuum at 6630A 21A
image cadence: 3 minutes
recording media: digital audio tape
(b) Spectroheliographic Observations
optics: 25cm coronagraph + Littrow spectrograph
raster area: four swaths of 500" wide (2.5" step)
synthesis of full disk maps is made after the observation
spectral coverage: 2A (0.2A x 10 wavelength points)
form of data: digital spectroheliogram of He I 10830A
image cadence: one map per day (one raster scan takes 30 minutes)
recording media: optical disk
2.3 Okayama Observatory
optics: 65cm reflector + Littrow spectrograph + photoelectric magnetograph
raster area: 500" x 450" (10" step) or 420" x 390" (6" step)
spectral coverage: 27-80mA from the center of 5250A line
(detectors are photomultipliers; no wavelength resolution)
form of data: digital I,Q,U,V,Doppler shifts of Fe I 5250A
image cadence: a few maps per day (one raster scan takes one hour)
recording media: magnetic tape and magneto-optical disk
The data available on-line are:
part of Mitaka H-alpha full-disk images (2.1a),
part of Flare Telescope vector magnetograms (2.1b-T1),
all of Norikura He 10830 fill-disk heliograms (2.2b), and
all of Okayama vector magnetograms (2.3).
Other data are archived in tapes in digital form, or recorded on analog media.
3. Browsing the Data by 'show'
After you log-in at 'spot' under the username 'guest', follow the instruction
shown on the banner message. You simply type
spot% show
and then enter your machine's IP-address after the prompt. An interactive,
menu-driven session on the X-window will start.
By using the mouse you first select from
magnetic data of flare telescope
Ha full disk image of Mitaka
Norikura data (He10830, corona)
Okayama magnetic data
exit
On all the menus, <return> means that you go back to the main menu, and
the 'show' program stops by selecting <exit>.
3.1 Flare Telescope Vector Magnetograms
The data have names 'fbyymmdd.hhmm', where yymmdd and hhmm designate,
respectively, the date and time in UT. By using the mouse, select the file
you want to see. When the menu is too big and is split into several pages,
you may select 'next page' and the next page of the file list will
be shown. The other options control plotting styles and printer output.
<contour> : magnetogram in contour
<spot+contour> : magnetogram in contour, sunspots in gray scale
<red-blue> : magnetogram in red-blue, sunspots in contour
<PostScript> : make postscript output file
<printout> : print postscript file at a local printer at Mitaka
<PostScript> is only selectable after you have selected data to be displayed.
In order to transfer the postscipt file, use anonymous ftp. The contour plot
is saved in 'tmp/magcont.ps' under the anonymous ftp directory.
After you exit, the data are stored in arrays: intensity map in 'img',
longitudinal magnetid field in 'Bl', and transverse magnetic fields in
'Bx,By'. The header h contains observing parameters. The magnetic data
are 2 byte integer in unit of 0.1 Gauss and each image has 256*240 pixels,
where a pixel corresponds to about 1.35 arcseconds. The instrument tends to
saturate for magnetic fields stronger than about 1700 Gauss. The field
strength in large sunspots should be used with some caution.
The direction of the transverse magnetic field (i.e. the resolution of
the 180 degree ambiguity) is determined by referring to the potential field
calculated from the longitudinal magnetic field distribution. The direction
may not be correct in regions with high magnetic shear.
In order to obtain the observation status, type
IDL> fstplot
and then choose yymmdd.
3.2 Mitaka Full-Disk H-alpha Images
The data have names 'hayymmdd.hhmm', where yymmdd and hhmm designate,
respectively, the date and time in UT. By using the mouse, select the file
you want to see. After you exit, the image data are stored in an array
'img', and the header h includes the observing parameters.
3.3 Norikura Spectroheliograms
In the 'Norikura' menu ( He10830, corona ) you should select He10830.
The other entry is not yet implemented. The data have names 'heyymmdd.hhmm',
where yymmdd and hhmm designate, respectively, the date and time in UT.
The data names followed by '.v' are Doppler images. By using the mouse, select
the file you want to see. After you exit, the image data are stored in an array
'img', and the header h includes the observing parameters.
3.4 Okayama Vector Magnetograms
First you select the year (1982 - ), and the file list appears.
The data have names 'ymddn.D', where y is a letter indicating the year
(B=1982, C=1983, ,,, M=1993), m indicates the month (1=Jan, ,, 9=Sept,
A=Oct, B=Nov, C=Dec), dd is the date, and n=A,B,C,,, are sequence
numbers of observation on the day. Then you are asked to enter
several numbers from the keyboard as follows.
obs.area : 0=skip, 1=show: _
(location of the observed area on the sun)
halftone map: 0=skip, 1= I, 2= BL, 3= VL: _
contour map : 0=skip, 1= I, 2= BL, 3= VL: _
vector map : 0=skip, 1=( BX, BY): _
Here I is the intensity map, BL is the longitudinal magnetogram, VL
is the Doppler map, and (BX,BY) are the transverse field vectors. If 0 is
entered, the corresponding map is not shown. If the potential field lines
had been computed and stored in a file 'ymddn.L', you will be asked:
field lines : 0=skip, 1=show : _
At the next prompt
1=plot again, 2=hardcopy, 9=exit > : _
you can plot the map in a different style by selecting 1. The postscript
output file will be created if you select 2. The postscript file can
be later transferred by anonymous ftp.
After you exit, the data are stored in a floating array 'rdata',
and the structure 'mparam' contains observing parameters.
The 'mparam.status' includes fields such as
i, q,u,v, bx,by,bl,,,,.
If for example the data By are stored in rdata(*,*,2), mparam.status.by
takes the value 2. In order to know which part of rdata contain valid
data, type
IDL> help,/st,mparam.status
The data whose status value is -1 are not stored in rdata array.
The electric current distribution can be seen by typing
IDL> .run jn
IDL> magplot, mparam, rdata, /nomenu
Then you will see the following prompt.
obs.area : 0=skip, 1=show: _
halftone map: 0=skip, 1= I, 2= BLP, 3= BL, 4= VL, 5= JN: _
contour map : 0=skip, 1= I, 2= BLP, 3= BL, 4= VL, 5= JN: _
vector map : 0=skip, 1=( BXP, BYP), 2=( BX, BY): _
1=plot again, 2=hardcopy, 9=exit > : _
Here JN is the normal component of the electric currents, and the field
components followed by P are those of the potential magnetic field.
4. Anonymous ftp Access to spot
When you are connected to 'spot' via anonymous ftp, under the home directory
you have directories
flare : Flare Telescope magnetograms
- log : Flare Telescope magnetograms
monochro : H-alpha full-disk images
norikura - he10830 : He10830 spectroheliograms
- corona
okayama - 1982 : Okayama magnetograms
- ...
doc : documents
idlsoft : IDL routines
All the IDL routines used here are stored under 'idlsoft'.
Compressed tar files of IDL software is provided as naojidl.tar.Z
in the home directory. The 'doc' directory contains text files explaining
the software and the data analysis.
The observation log files of the Flare Telescope are in /solar/flare/log.
The files 'yymmdd.log' give you the time and the observing region
for all data on the day. The files 'lv##.log' contain list of H-alpha
video disk recordings of the Flare Telescope T3.
5. Description of the Software
The 'show' program assumes the directory structure of NAOJ workstations.
Therefore, when you want to display and analyse the data obtained via ftp,
you have to invoke lower-level IDL routines.
5.1 Flare Telescope Vector Magnetograms
To read a file named 'fbyymmdd.hhmm' and store the data into img,Bx,By,Bl:
IDL> f1data, 'fbyymmdd.hhmm', h, img, Bx, By, Bl
Or an interactive program can be invoked by
IDL> .run fdisp
The map can be displayed by
IDL> magtv1, h=h, img, Bx, By, Bl
or
IDL> magtv2, h=h, img, Bx, By, Bl
or
IDL> magcont, h=h, img, Bx, By, Bl
To calculate and display electric current distribution:
IDL> .run jnft1
(The data should exist in h,img,Bx,By,Bl.)
5.2 Mitaka H-alpha Images and Norikura He10830 Heliograms
To read a file and store the image into 'img':
IDL> nkrget, <filename>, h, img
To display:
IDL> tvscl, img
5.3 Okayama Vector Magnetograms
To read a magnetogram file:
IDL> readm, mparam, rdata, filename=<filename>
To display magnetograms and potential field lines:
IDL> magplot, mparam, rdata, /nomenu
To calculate and display electric current distribution:
(The data should exist in mparam and rdata.)
IDL> .run jn
E. Using the Laser Disk System at ISAS
E.1 Viewing Existing Movies (VIDEO_MENU)
IDL > video_menu
The user is prompted to check for
the proper settings on the SONY disk drive, and then a listing is
displayed from which the user selects a movie sequence for display.
Upon selection the sequence is played repeatedly. While the
sequence is playing the user may adjust the speed by keyboard input.
The user may interrupt the movie at any time and return to the menu.
The library of available movie sequences is updated manually as movies
are recorded on the SONY, so the listing could be out of date.
E.2 Making Title Pages
IDL > array = video_title(filename)
; Display the results
IDL > array = video_title(filename,/plot,outfile='video1',/high)
IDL > array = video_title(filename,/plot,outfile='video1')
The variable filename specifies the name of an ASCII control
file that contains the text of the page. For example try the
following:
IDL > array = video_title('/ys/gen/doc/howto_video_title.doc',/plot)
where /ys/gen/doc/howto_video_title.doc is the name of a
``how to" file which is also an example control file. This file
explains the format of the control file. For the first time users,
it is recommended to copy that file over and make changes to it to
accommodate your needs.
; howto_video_title.doc J. R. Lemen Rev A, 4-Jan-94
;
; The control file contains 5 items per line separated by a double
; slash or "//". The first and second fields are the positions in
; the 620 by 480 sized video window (0,0 is the lower left corner).
; It is advisable not to write too close to any edge, since the
; text may be lost, depending on the display monitor. Setting xpos
; equal to -1 will cause the text to be automatically centered (and
; leading or trailing blanks will be discarded). The third field
; is the text and the fourth and fifth fields are the character
; size and thickness, respectively.
;
; The Fonts can be changed using the standard !n IDL vector commands
; (see the example below).
;
; This entire document is an example control file (since every line
; except the important ones below begin with an ";"). Below the
; dashed line is a specific example. This file will cause two
; pages to be generated (because of the NEWPAGE// line). It is not
; necessary to have more than one title page per file.
;
; ------------------------------------------------------------------
; Semicolons are treated as comments
; Separate fields with //
; xpos // ypos // Text // size // thickness
; (size and thickness will default to 1.0 if omitted)
; (setting xpos to -1 will cause x position to auto-center)
-1//425//X-RAY CORONA OF THE SUN //2.8//2.8
-1//375//Images from the Soft X-ray Telescope //2.1//1.4
-1//345//on the YOHKOH mission //2.1//1.4
-1//275//Data from: November 11 to 27, 1991 //2.1//1.4
-1//220//!8Prepared by: //2.1//1.4
-1//190//J. Lemen, G. Slater, K. Strong, and S. Tsuneta //1.7//1.7
-1//100//Institute for Astronautical Research, Japan //1.4/1.4
-1// 75//National Aeronautics and Space Administration, USA//1.4//1.4
-1// 30//(V1.0 13 April 1992)//1.4
NEWPAGE//
-1//300//Data from: November 11 to 27, 1991 //2.1//1.4
-1//200//!18Displayed 100,000 times real time //2.1//1.4
The /high switch makes the routine run slow, but gives a higher
quality result. It is recommended to debug the output without the
/high switch and only use it for the final result.
E.3 Recording a New Movie to Laser Disk
5.3.1 Hardware: Positioning the Sony Laser Disk
5.3.2 Software
; Standard weekly movie making
; Standard weekly movie making
; For on-line documentation
; to use a GENX type file as the input
The temporary NVS files will be written to your home directory.
Use the nvsdirfn='/1p/user/nvs0' switch to redirect to another location.
5.3.3 Adding Another Movie
IDL > go_nvs5 [,/sfd]
to make the next movie.
5.3.4 NVS/Sony Problems
E.4 Transferring a Movie to VCR Video
5.4.1 Initial setup
5.4.2 Short test of hardware communications.
; Position laser disk to frame number 6000
; Play from 6000 to 6200 at normal speed
; Play a factor of 2 slower
5.4.3 Running MK_VCR
% cp /ys/gen/data/mk_vcr_example.txt .
After you copy the example file, do the following. Insert Side B of the
laser optical disk. Then,
IDL > mk_vcr,'mk_vcr_example.txt',1,3
which execute lines 1 to 3 of the file. (Line 0 puts up a blank frame).
If you type
IDL > mk_vcr,'mk_vcr_example.txt
the routine will inform you of the number of lines in the file and
ask you to enter the start and stop line numbers.
;Get it to a blank frame
;There are 24 lines in the file
;End on a blank frame
As you can see, the sequence in the `for loop' will execute 3 times. Each
time through takes about 7 minutes, so the whole movie will be just over
20 minutes in length.
5.4.4 How to create/modify the file that MK_VCR uses
8000 ; Position to a blank frame (provide leader)
6077, 6077, 4, 0, [ -1 0 0 0] "Movie Title Page"
6078, 6078, 2, 1, [ -1 0 0 0] "Nov 1991 Movie - Title"
5048, 5225, 2, 1, [ 1 2 1 -1] "Nov 1991 Movie"
; c0 c1 c2 c3 [c4] " c5 "
The above sequence will display the Nov 91 press release sequence if Side B
is inserted. Some notes about the format:
0 is no operation
1 is normal speed (30 frames per second)
2 is twice slower (15 frames per second)
3 is 3x slower, etc (10 frames per second)
-2 is 3x faster.
If a fifth parameter is specified in the brackets, it is a repeat number.
If this number is negative, sonyloop will play the sequence forward
and backward. For example,
5048, 5225, 2, 1, [ 1 0 0 0 1] "Nov 1991 Movie" ;1 time forward
5048, 5225, 2, 1, [ 1 0 0 0 -1] "Nov 1991 Movie" ;1 time forward/backward
5048, 5225, 2, 1, [ 1 0 0 0 -3] "Nov 1991 Movie" ;3 times forward/backward
SPECIAL NOTES:
F. Using the Laser Disk System at LPARL
F.1 Viewing Existing Movies
6.1.1 Using IDL and Menu Driven Software
6.1.2 Displaying a Single Recorded Image
The Panasonic optical disk recorder/player and the Panasonic optical disk player may be ``manually'' controlled by using either the buttons on the front of each machine or the remote controllers. These buttons and the remote controller are labeled in English and are easily understood.
The Panasonic optical disk recorder/player and the Panasonic optical disk player may be played ``manually'' by using either the buttons on the front of each machine or the remote controllers. These buttons and the remote controller are labeled in English and are easily understood.
See the description in the previous chapter on page E.2 describing the laser disk system at ISAS.
If no test image appears after issuing the PTEST command in the instructions described in the previous section, then do these things:
As of the writing of this document, the routine MK_VCR (which is described on page E.4) was not available for the LPARL video system. The routine may be expanded in the future. The best method for transferring a laser disk movie to VCR video is to talk to one of the LPARL software engineers.
A complete archive of the Yohkoh data for the whole mission is available on Magneto-Optical (MO) disks at ISAS.
A Unix script and associated alias is available to mount and dismount MO (magneto optical) disks at ISAS. An IDL interface routine is also provided to allow MO mounts and dismounts from within an IDL session or callable from other IDL routines. Once mounted, access to data on these drives is identical to other magnetic disks - standard Unix operations (ex: ls) are permitted. For MO disks containing Yohkoh data, the standard IDL functions (ex: yodat access) are available.
MO disks are available on several machines of the SUN machines at ISAS. including flare3, flare4, flare6, flare13, flare14, flare15. The first (and in most case, only) MO drive on any machine is referred to as drive 0. Some machines may have a second drive (drive 1) - all drives are clearly marked with a drive number. Find an available (empty) drive and insert your disk - if you intend to write, verify that the write protect switch allows writing. By default, the mount is executed on the machine which contains the MO driver. If that machine is different than the machine which executes the command, then the MO disk is automatically 'exported' and mounted on the local machine. Use the /all switch to force mounting on all ISAS machines.
The alias momount executes the script which performs all MO operations.
Parameters and switches allow specification of machine name, drive number,
access mode, dismounts, etc. Options include /write /umount /eject /1
and /all.
Some sample calling sequences are:
# mount flare13 , drive 0, readonly
# dismount same
# mount flare4, drive 1, read/write
# dismount and eject same
# mount flare15, drive 0, on all nodes
An IDL driver sets up the parameters and spawns a call to the same script
file described above to allow IDL MO control (interactive or via routine).
Keyword options similar to the Unix script are available with the IDL
routine. Some examples are:
; mount flare13 , drive 0, readonly
; dismount same
; mount flare4, drive 1, read/write
; dismount and eject same
The following documents are useful for understanding different aspects of the operations of Yohkoh.
| /ys/gen/doc/ssoc_tohban_manual_* | A detailed description of how to perform the SSOC tohban duties |
| auto_toban2.pro | The header of this program describes in detail the different steps on how the daily KSC reformatting is performed |
| /ys/gen/doc/ref_super.doc | This document describes the different steps which are performed during the standard reformatting |
| /ys/gen/doc/cron.doc | Describes the different cron jobs that are run automatically at ISAS and LPARL to process data, distribute software and data, and to copy data from GBO sites |
| /ys/gen/doc/howto_term_images.doc | Explains the procedure SSOC Tohbans should follow when planning SXT terminator images |
| /ys/gen/doc/krasm.doc | Explains how the SSOC Tohbans may access the RASM scheduling computer by modem |
1 The previous organization had an `atest', `rel', and `usercontrib' branch under each `soft' directory.
2 If this code is used as a template, we recommend that the calling sequence be index,data for all routines
3 If this code is used as a template, we recommend that the calling sequence be index,data for all routines