DATA ARCHIVING and PROCESSING SYSTEM
DAPS USER’S GUIDE
Version V2.0
17 November 1999
Revisions to V2.0
22 November 1999
DAPS V2.0 User’s Guide – 11/99
2
TABLE OF CONTENTS
1 Introduction ...............................................................................................4
1.1 Document Purpose .................................................................................4
1.2 Organization ...........................................................................................4
1.3 DAPS V2.0 Capabilities .........................................................................4
1.4 Changes From DAPS V1.0 .....................................................................5
1.5 System Setup and Requirements ..........................................................5
1.6 Establishing Trust for the DAPS Applet...............................................6
1.7 Contact Information ..............................................................................7
2 Doing Simple Queries ...............................................................................7
2.1 Listing the Available Data .....................................................................7
Step 1: Specify the Start and Stop Time of the Desired Data ....................7
Step 2: Specify a Channel ..........................................................................8
Step 3: Select the Search Button ................................................................8
2.2 Accessing Observation Metadata..........................................................9
Step 1: Select an Observation.....................................................................9
Step 2: Request Metadata for the Observation ...........................................9
2.3 Transferring Data ..................................................................................9
Step 1: Select an Observation .....................................................................9
Step 2: Choose a Format.............................................................................9
Step 3: Request the Data...........................................................................10
Step 4: Specify a File Name .....................................................................10
2.4 Accessing Housekeeping Data.............................................................10
3 Doing More Complex Queries................................................................11
4 Reading the NetCDF files .......................................................................12
4.1 IDL Routines Description.....................................................................12
DAPS V2.0 User’s Guide – 11/99
3
4.2 IDL Structure Description ...................................................................15
5 The Summary Browse Product...............................................................20
Appendix A - Document Figures ...............................................................22
Appendix B - System Setup and Installation ............................................26
1. Introduction ............................................................................................26
2. Installing the Java Plug-In on IE/Windows and Netscape/Solaris ....26
3. Installing/Upgrading MRJ 2.1 ..............................................................27
Appendix C - Additional Information.......................................................29
1. Known Problems and Liens ..................................................................29
2. Note on Start-Time Metadata Information .........................................29
DAPS V2.0 User’s Guide – 11/99
4
1 Introduction
1.1 Document Purpose
This document is the user’s guide for the UVIS Data Archiving and
Processing System (DAPS). It applies to version 2.0 of the DAPS.
It can be copied as a pdf file from the UVIS team website (at
http://lasp.colorado.edu/cassini).
1.2 Organization
The document is organized into three main sections. The first section
describes a simple sequence of steps that can be used to query data from the
DAPS; the second section describes more sophisticated query capabilities;
and the third section examines the IDL routines that can be used to access
data after they have been transferred to the user’s local machine.
All sections give specific references to components of the user interface.
For an illustration of the interface, see Figure 1 in Appendix A. In Figure 1,
the user interface components are labeled using numerals. These numbers
are used throughout the text whenever it refers to part of the user interface.
1.3 DAPS V2.0 Capabilities
DAPS V2.0 provides the following high-level capabilities:
• Access to the level 1a (L1a) data inventory via a web-based user interface
• Transfer of selected L1a science data and metadata and selected level 1b
(L1b) housekeeping data to the client host computer in NetCDF format
• Access to the NetCDF-formatted file via IDL routines.
Therefore, the DAPS V2.0 has two main components: a web interface and a
set of IDL routines to read the data transferred from the DAPS database.
DAPS V2.0 User’s Guide – 11/99
5
1.4 Changes From DAPS V1.0
DAPS V2.0 provides many improvements over DAPS V1.0.
• Usability
The user can access multiple observations in a single query, default and
unique filenames are provided, and there are no limitations on the object
size. Refer to section 2.3. A summary browse product has been added
(section 5).
• Performance
The overall performance of the DAPS has been improved by giving the
DAPS write privilege to the local file system. This is made possible by
establishing trust for the DAPS applet (sec. 1.5-1.6).
• L0 to L1 bug fixes
FUV and EUV observations which were absent due to redundant time tags
because of missing data are now accessible, and HDAC objects with missing
data are no longer concatenated.
• Improved IDL reader routines
Wildcard filenames are supported and time information is provided using the
spacecraft clock and UTC. Refer to paragraph 4.0 for a description of the
IDL interface.
1.5 System Setup and Requirements
The DAPS is available through the World Wide Web. The home page for
the DAPS is located at http://cassini.colorado.edu/DAPS/UVISDB.html.
Access to this page has been tested using the following configurations:
1. Netscape Navigator 4.5 running on a Sparc/Solaris platform
2. Microsoft Internet Explorer 4.5 running on a Macintosh platform
3. Microsoft Internet Explorer 4.0 running on a Windows 95/98 or NT
platform.
Other configurations may be available, but they have not been tested.
DAPS V2.0 User’s Guide – 11/99
6
For Windows and Unix platforms, the browser requires Sun Microsystem’s
Java plug-in (version 1.1.3) and Sun Microsystem’s Java Development Kit
(JDK 1.1.8).
On the Macintosh, the browser requires Apple’s MRJ 2.1.x Java Virtual
Machine and the MRJ Software Development Kit (MRJ SDK 2.1).
Refer to Appendix B for more details on SDK, MRJ, JDK and the plug-in.
When you access the DAPS web page, your configuration is automatically
checked by DAPS and you are redirected to the DAPS web page compatible
with your system. If the check fails (which can happen if the network is
slow), you will end up at an “unsupported configuration” page. In that case,
you should try to access the DAPS directly via the one of following
addresses:
For a Macintosh platform:
http://cassini.colorado.edu/DAPS/UVISDB_mac.html
For a Windows and a Sparc/Solaris platform:
http://cassini.colorado.edu/DAPS/UVISDB_win.html
1.6 Establishing Trust for the DAPS Applet
In order to decrease DAPS network overhead, it is necessary to establish
trust for the DAPS. Trust will allow the DAPS applet code running in a
browser to write to the local file system. Once JDK (or MRJ on the
Macintosh) has been installed, establishing trust is a one-time process and
can be accomplished using the following steps:
1 Get the file DAPS.x509 from the Cassini team site documents archive.
On UNIX systems, issue the commands:
2 javakey –c “DAPS” true
3 javakey –ic “DAPS” DAPS.x509
DAPS V2.0 User’s Guide – 11/99
7
On Windows systems (using the DOS command line), issue the commands:
2 javakey.exe –c “DAPS” true
3 javakey.exe -ic “DAPS” DAPS.x509
On Macintosh systems:
2
3
4
5
6
7
8
Invoke the javakey application.
Choose “create” from the commands list.
Enter “DAPS” in the text field and check the “trusted” box.
Select the “do javakey” button.
Choose “import certificate” from the commands choice list.
Find the file DAPS.x509 from the choose file choice list.
Select the “do javakey” button.
Note: The javakey command creates a file called identitydb.obj. This file
must reside in the user home directory (Unix system), the Preferences folder
(Macintosh system) or the user subdirectory of the Profiles directory
(Windows system). We have found that on Windows systems the
identitydb.obj file may be created elsewhere. .In that case it should be
moved to the user subdirectory of the Profiles directory.
1.7 Contact Information
Please address all questions and comments regarding the DAPS functionality
to Dave Judd at judd@lasp.colorado.edu, with cc: to Alain Jouchoux at
jouchoux@lasp.colorado.edu.
2 Doing Simple Queries
2.1 Listing the Available Data
Step 1: Specify the Start and Stop Time of the Desired Data
Several mechanisms can be used to select the time range of a data query.
You may choose from a set of start-and-stop-time names (see 1 and 3 in
Figure 1). Click on the choice list for a list of names associated with
important time ranges within the mission. Selecting a choice will cause the
name to be entered into the appropriate start or stop text field (2 and 4).
DAPS V2.0 User’s Guide – 11/99
8
The Events text area (5) contains a more extensive list of start/stop time
choices. By clicking the mouse on a line of the text area, the start and stop
time contained on the line will be entered into the start and stop text fields (2
and 4).
You may enter a start or stop time directly into the start or stop time field.
The date/time formats currently supported are:
• yyyy-DDD HH:mm:ss (as in 1999-175 20:26:00)
• dd-MMM-yyyy HH:mm:ss (as in 26-jun-1999 20:26:00)
• dd-MMM-yyyy (as in 26-jun-1999).
Step 2: Specify a Channel
You must choose a channel from the Channel choice list (6). When you
select a channel, the choice list will be replaced by a list of Boolean
operators. You may choose from this list to define a relationship between
more than one channel. For example, to get a list of data that includes
observations from the EUV or FUV channels, choose “or” from the list of
Boolean operators. To get a list of observations in which both the FUV and
the EUV channels were on, choose “and” from the list. When you select a
Boolean operator, the choice list will be replaced by the initial list of
channels. You can start over at any time by selecting “clear,” which will
erase the contents of the channel text field (7) and reset the choice lists.
Step 3: Select the Search Button
To submit your data search query, click the Search button (13). Your
request is sent to the DAPS, and the results are listed in the Search
Results text area (11). For an example of search query results, see Figure
2. The contents of the Search Results text area (11) is a list of
available observations identified by the channel and the start time of the
observation, e.g., EUV1999-01-07 17:08:52.00.
DAPS V2.0 User’s Guide – 11/99
9
2.2 Accessing Observation Metadata
Step 1: Select an Observation
Select a single observation by highlighting the entire line of the observation
name in the Search Results text area (11).
Step 2: Request Metadata for the Observation
Request metadata for the selected observation by selecting the GetData
menu button (14) and then choosing the Metadata menu item.
The result of your metadata request appears in the Status text area (12).
Before the metadata, a sequence of status messages may appear.
The metadata are displayed as a sequence of name - value pairs. Each name
corresponds to some aspect of the instrument configuration as derived from
telemetry. The value of the parameter corresponds to the state of the
instrument for the duration of the observation (see Figure 2 for an example
of a metadata listing).
The number-of-records parameter is derived from the DAPS archive. It
generally corresponds to the number of integrations taken during the
observation. The volume of data can be determined from the number of
records and the integration size. For HSP and HDAC, the record size is
arbitrarily set at 2048 bytes.
2.3 Transferring Data
Step 1: Select an Observation
Select observation(s) from the Search Results text area (11) by
highlighting the observation name(s).
Step 2: Choose a Format
The default format is NetCDF (NCDF). This is the only supported format in
version 2.0 of the DAPS.
DAPS V2.0 User’s Guide – 11/99
10
Step 3: Request the Data
Click the GetData menu button (14) and then select the Data menu item.
A sequence of status messages will appear in the status text area (12, Figure
3)
Step 4: Specify a File Name
A file dialog box will be displayed. This box will allow you to specify the
names of the files that are to be written by the DAPS applet. The default file
name is the name of an observation as displayed in the search results text
area.
On UNIX and Windows systems, one may override the default name by
entering a preferred name in the dialog box. In that case, when downloading
more than one observation, the file names are formed by appending 1…n to
the specified name.
On the Macintosh, a file name is specified by selecting an existing file.
Nevertheless, the output files will be written using the default naming
convention (the selected file is used to choose the folder, not the file
name(s)).
2.4 Accessing Housekeeping Data
Accessing housekeeping data more or less follows the steps detailed above.
Housekeeping data are selected via the Channel choice list (6). After
querying the data availability via the Search button (13), look for the
results in the Search Results text area (11, Figure 4). The first line of
the resulting text can be used to select all the housekeeping data available in
the selected time range.
Double clicking on the first line and selecting Metadata from the
Getdata menu button result in the listing of the effective time range and
number of records of the available data in the Status text window (12).
Before transferring the data, it is necessary to select one or more housekeeping components via the menu button (6.1).
DAPS V2.0 User’s Guide – 11/99
11
3 Doing More Complex Queries
The steps described above are the minimum required to extract data from the
DAPS. It is often desirable to select a particular type of observation from the
archive. For example, you may be looking for spectra from the FUV channel
as opposed to full spatial/spectral images. In order to make such a
specification, use the channel configuration choice list (6.1).
When you choose a channel from the Channel choice list (6), the channel
configuration choice list is filled with a sequence of options. These options
correspond to aspects of the instrument’s configuration. You can select from
this list and then specify a value for the configuration in order to refine a
search. From the previous example, a user looking for FUV spectra would
specify a spatial bin value of 64.
When a configuration name is chosen by a user, the contents of the
configuration list are replaced with a sequence of relational operators (=, >,
<, etc.). If you choose from this list, the operator will be appended to the
configuration text area (8). After an operator is chosen, type the desired
parameter value into the configuration text area. Also, when the operator is
chosen, the contents of the choice list will change to a sequence of Boolean
operators. By choosing one of the Boolean operators, you can produce a
sequence of parameter/value expressions. Note that choosing “clear” from
the channel choice list (6) resets the channel text field (7) and the
configuration text area (8).
If you were interested in EUV spectra with an integration time of greater
than 4 seconds, you would:
Choose “EUV” from the channel choice list.
Choose “Integration” from the choice list.
Choose “>” from the configuration choice list.
Type “4” into the configuration text area.
Choose “and” from the configuration choice list.
Choose “EUVBinSpatial” from the configuration choice list.
Choose “=” from the configuration choice list.
Then finally, type “64” into the configuration text area.
DAPS V2.0 User’s Guide – 11/99
12
The contents of the configuration text area will be:
Integration > 4 and EUVBinSpatial = 64.
Instead of using the choice lists, you may type directly into the
configuration text area. However, the DAPS query interpreter is
not capable of recognizing or fixing incorrect expressions.
4 Reading the NetCDF files
4.1 IDL Routines Description
Four IDL routines can be used to access that data after they have been
transferred:
• hk_reader.pro for a housekeeping data file
• hdac_reader.pro for an HDAC data file
• hsp_reader.pro for an HSP data file
• feuv_reader.pro for an FUV or EUV data file.
In addition, the routine convert_sclk.pro can be used to convert from
spacecraft clock to spacecraft event time.
The calling sequence of each routine can be obtained by entering the name
of the routine at the IDL prompt. Note that the *_reader.pro routines support
the use of wildcard notation for the filename parameter.
IDL> hdac_reader
To read data, enter the following at the IDL prompt:
hdac_reader,filename,pinfo,desc,data
where filename is in single quotation marks, and all other parameters
are optional. data contains the data itself. It is a 3-dimension
array where the first dimension is sized according to the dwell
time, the second dimension is fixed to 16 (size of modulation
table) and the third dimension depends on the observation duration.
pinfo is a structure containing version information.
desc is a structure that characterizes the data product
IDL> HDAC_reader,filename
will result in program execution stopping allowing interactive
examination of all variables using
IDL> help
DAPS V2.0 User’s Guide – 11/99
IDL> hsp_reader
To read data, enter the following at the IDL prompt:
hsp_reader,filename,pinfo,desc,data
where filename is in single quotation marks, and all other parameters
are optional. data contains the data itself. It is a 2-dimension
array where number of columns corresponds to
the number of data point returned in each packet and
the number of rows depends on the observation duration.
pinfo is a structure containing version information.
desc is a structure that characterizes the data product
IDL> HSP_reader,filename
will result in program execution stopping allowing interactive
examination of all variables using
IDL> help
IDL> feuv_reader
To read data, enter the following at the IDL prompt:
feuv_reader,filename,pinfo,desc,window,w1,w2,w3,w4,w5,w6,w7,w8,w9,w10
where filename is in single quotation marks, and all other parameters
are optional. w1 through w10 contain the data for the 10 possible
windows. If only one window defined for this data, then
IDL> feuv_reader,filename,pinfo, desc, window, w1
will put the data for that window in the variable named w1.
pinfo is a structure containing version information
desc is a structure that characterizes the data product
window is a structure that describes the window parameters
IDL> feuv_reader,filename
will result in program execution stopping allowing interactive
examination of all variables using
IDL> help
IDL> hk_reader
|--------------------------------------------------------------------|
PRO GET_Hk_DP,file, pinfo, desc, data
|--------------------------------------------------------------------|
*file
=> the source data file to access
*pinfo
=> version information
*desc
=> associated metadata
*data
=> two dimension array of calibrated values
The first dimension indices the measurements contained
the file. The second dimension is the measurement values
Example:
hk_reader,'hk_ico_logic_temp.dat,', p, d, lgc_temp
|--------------------------------------------------------------------|
IDL> convert_sclk
To convert from spacecraft clock (sclk) to
spacecraft event time (scet) enter the following
at the IDL prompt:
convert_sclk, sclk_second, sclk_millisecond, scet
where sclk_second is the spacecraft second and
13
DAPS V2.0 User’s Guide – 11/99
14
sclk_millisecond the millisecond value derived from
the fractional portion of the sclk
The DAPS routine returns the sclk in second and millisecond
(see sctime_sec_start and sctime_ms_start)
In the CCSDS header the time is returned as second and
a fractional part (milliseconds = fractional part * 3.096)
The scet is returned as UTC time in the parameter scet, in
in structure of the following form:
scet = { scet_dp, $
year: long(0), $
doy : long(0), $
hour: long(0), $
min : long(0), $
sec : double(0.0)}
The IDL files should be pre-compiled using the IDL procedure daps_tools.pro:
IDL> .r daps_tools
% Compiled module:
% Compiled module:
% Compiled module:
% Compiled module:
% Compiled module:
% Compiled module:
% Compiled module:
% Compiled module:
% Compiled module:
% Compiled module:
% Compiled module:
FEUV_READER.
WINSUM.
HSP_READER.
HDAC_READER.
HK_READER.
INIT_STRUCTURES_DP.
POLYF.
CONVERT_HK_DP.
ATTGET.
GET_FILENAME.
CONVERT_SCLK.
The IDL routines can be downloaded from the UVIS team website as a
compressed tar file (called idl_daps_tools_v2.0.tar.Z) or as a binhexed stuffit
archive file (called idl_daps_tools_v2.0.sit.hqx). Each source file can be
extracted from the archive file idl_daps_tools_v2.0.tar.Z using a utility
program such as Stuffit Expander with DropStuff (Macintosh), gunzip and
tar (Unix), or WinZip (Windows). Each source file can be extracted from the
archive file idl_daps_tools_v2.0.sit.hqx using a utility program such as
Stuffit Expander (Macintosh).
Below is the index at
http://lasp.colorado.edu/team-site/archive/docs/code/daps_tools:
DAPS V2.0 User’s Guide – 11/99
Name
15
Last modified
Size
Description
-----------------------------------------------------------------------Parent Directory
DAPS.x509
idl_daps_tools.sit.hqx
idl_daps_tools.tar.Z
idl_daps_tools_v2.0.s..
idl_daps_tools_v2.0.t..
11-Jul-1999
26-Oct-1999
17-Jul-1999
10-Jul-1999
26-Oct-1999
26-Oct-1999
22:49
14:33
18:18
23:12
14:32
14:32
0k
1k
13k
13k
19k
19k
4.2 IDL Structure Description
Pinfo Structure
This structure is returned in the first parameter of the IDL *_reader routines.
IDL> hdac_reader,'hdac*',pinfo,desc,data
1 HDAC1999_01_07_16_31_08_000
2 HDAC1999_01_07_16_33_08_000
3 HDAC1999_01_07_16_36_14_000
4 HDAC1999_01_07_16_42_08_000
Enter the number of the file you want: 1
accessing: HDAC1999_01_07_16_31_08_000
Data stored in array "data":
Record size:
1 * 16
Number of records: 60
IDL> help,pinfo,/st
** Structure PRODUCT_INFO_DP, 2 tags, length=4:
L02L1VERSION
INT
1
NETCDFVERSION
INT
1
L02L1VERSION is the version of the L0 to L1a code used in the processing
of the raw data.
NETCDFVERSION is attached to the format of the NetCDF files.
Desc Structure
This structure is returned in the first parameter of the IDL routines. The
format of the structure is channel dependent.
EUV and FUV format
IDL> help,desc,/st
** Structure FEUV_DES_DP, 16 tags, length=56:
SCTIME_SEC_START
DAPS V2.0 User’s Guide – 11/99
SCTIME_MS_START
YEAR_START
DOY_START
HOUR_START
MIN_START
SEC_START
ODC_ID
COMPRESSION
INTEGRATION
HVPS_LEVEL
WINDOWS
OCC_COVER
SLIT_POSITION
TEST_PULSE
CHANNEL
LONG
LONG
LONG
LONG
LONG
LONG
DOUBLE
INT
BYTE
FLOAT
BYTE
BYTE
BYTE
BYTE
INT
STRING
16
=
1295207522
0
1999
16
19
47
15.821564
12
1
60.0000
1
1
0
2
0
SCTIME_SEC_START and SCTIME_MS_START are the spacecraft clock
values at the end of the first integration.
*_START contains the UTC time equivalent.
COMPRESSION: 0 = no compression, 1 = sqrt_9, 2 = sqrt_8, 3 = 8-bit
INTEGRATION is expressed in seconds.
HVPS_LEVEL: 0 = off, x 1 to 3 = on at the specified level
OCC_COVER: 0 = closed, 1 = open
SLIT_POSITION: 0 = high resolution, 1 = low resolution, 2 = occultation
TEST_PULSE: 0 = off, 1 = on
HSP format
IDL> help,desc,/st
** Structure HSP_DES_DP, 12 tags, length=52:
SCTIME_SEC_START
LONG
=
1294644083
SCTIME_MS_START LONG
0
YEAR_START
LONG
1999
DOY_START
LONG
10
HOUR_START
LONG
7
MIN_START
LONG
16
SEC_START
DOUBLE
40.522231
ODC_ID
INT
9
COMPRESSION
BYTE
1
INTEGRATION
FLOAT
8.00000
HVPS
BYTE
0
CHANNEL
STRING
Array[1]
SCTIME_SEC_START and SCTIME_MS_START are the spacecraft clock
values at the end of the first integration.
*_START contains the UTC time equivalent.
DAPS V2.0 User’s Guide – 11/99
17
COMPRESSION: 0 = no compression, 1 = sqrt_9, 2 = sqrt_8, 3 = 8-bit
INTEGRATION is expressed in milliseconds.
HVSP: 0 = off, 1 = on
HDAC format (only a partial structure is shown here)
IDL> help,desc,/st
** Structure HDAC_DES_DP, 47 tags, length=88:
SCTIME_SEC_START
LONG
=
1294418149
SCTIME_MS_START LONG
0
YEAR_START
LONG
1999
DOY_START
LONG
7
HOUR_START
LONG
16
MIN_START
LONG
31
SEC_START
DOUBLE
7.9624179
ODC_ID
INT
2
COMPRESSION
BYTE
0
INTEGRATION
FLOAT
0.125000
HVPS
BYTE
1
D_FILAMENT
BYTE
1
H_FILAMENT
BYTE
1
DWELL_TIME
INT
72
D_LEVEL_1
BYTE
0
D_LEVEL_2
BYTE
0
D_LEVEL_3
BYTE
0
D_LEVEL_4
BYTE
0
D_LEVEL_5
BYTE
0
D_LEVEL_6
BYTE
0
D_LEVEL_7
BYTE
0
D_LEVEL_8
BYTE
2
D_LEVEL_9
BYTE
0
D_LEVEL_10
BYTE
3
SCTIME_SEC_START and SCTIME_MS_START are the spacecraft clock
values at the end of the first integration.
*_START contains the UTC time equivalent.
COMPRESSION: 0 = no compression, 1 = sqrt_9, 2 = sqrt_8, 3 = 8-bit
INTEGRATION is expressed in milliseconds. For HDAC this is always
0.125.
HVSP: 0 = off, 1 = on
D_FILAMENT: 0 = first filament, 1 = second filament
H_FILAMENT: 0 = first filament, 1 = second filament
DWELL TIME is expressed in number of integrations.
DAPS V2.0 User’s Guide – 11/99
HK Format
IDL> hk_reader,'HK*',pinfo,desc,data
accessing: HK1990_01_01_00_00_00_000.secon
Data stored in array "data"(Number of records , Record size)
Number of records: 4
Record size:
1349
Each record corresponds to the following telemetry point
0 seconds
1 fuv_dettemp
2 hdac_tmrate
3 fuv_tmrate
IDL> help,desc,/st
DESC
STRING
= Array[4]
IDL> print,desc
seconds fuv_dettemp hdac_tmrate fuv_tmrate
DESC is an array for character string. Each string contains the name of the
measurement stored at the same index in the data array.
Data Structure
This structure is returned in the third parameter of the HSP_READER,
HDAC_READER, and HK_READER routines. It is returned in the fourth
(and beyond) parameter of the FEUV_READER routine. Its format is
channel dependent.
EUV and FUV format
IDL> feuv_reader,'FUV*',pinfo,desc,win,data
1 FUV1999_01_10_07_16_50_000
2 FUV1999_01_16_19_47_15_000
Enter the number of the file you want: 2
accessing: FUV1999_01_16_19_47_15_000
Number of windows:
1
********* Window summary *******
Window number 1
Data stored in array "w1":
Number of spectral elements: 1024
Number of spatial elements:
64
Number of records:
2
The data are in the form of a three-dimensional array with the first
dimension the wavelength, the second dimension the spatial dimension.
Each integration is a separate record in the third dimension.
18
DAPS V2.0 User’s Guide – 11/99
19
HDAC format
IDL> hdac_reader,'HDAC*',pinfo,desc,data
1 HDAC1999_01_07_16_31_08_000
2 HDAC1999_01_07_16_33_08_000
3 HDAC1999_01_07_16_36_14_000
4 HDAC1999_01_07_16_42_08_000
Enter the number of the file you want: 4
accessing: HDAC1999_01_07_16_42_08_000
Data stored in array "data":
Record size:
1 * 16
Number of records: 60
IDL> help,data,/st
DATA
LONG
= Array[1, 16, 60]
The data are in the form of a three-dimensional array. The first dimension
corresponds to the dwell dimension. The second dimension is always sized
at 16 and represents the depth of the filament modulation table. Each cycle
through the filament modulation table is a separate record in the third
dimension.
HSP format
IDL> hsp_reader,'HSP*',pinfo,desc,data
1 HSP1999_01_10_07_16_40_000
2 HSP1999_01_16_20_18_05_000
Enter the number of the file you want: 1
accessing: HSP1999_01_10_07_16_40_000
Data stored in array "data":
Record size:
945
Number of records: 854
IDL> help,data,/st
DATA
LONG
= Array[945, 854]
The data are in the form of a two-dimensional array. This structure format is
linked to the way the data are returned in packets from the spacecraft. The
first dimension represents packet contents. Each packet is a separate record
in the second dimension.
HK format
IDL> hk_reader,'HK*',pinfo,desc,data
accessing: HK1990_01_01_00_00_00_000.secon
Data stored in array "data"(Number of records , Record size)
Number of records: 4
Record size:
1349
Each record corresponds to the following telemetry point
DAPS V2.0 User’s Guide – 11/99
0
1
2
3
20
seconds
fuv_dettemp
hdac_tmrate
fuv_tmrate
The data are in the form of a two-dimensional array. The first dimension is
the channel index. The second dimension is the data itself. In the example
above, data(1,*) contains the FUV detector temperature. Note that the name
of channel for index 1 is in desc(1). The channels are returned in the order
they were requested in the GetData query.
5 The Summary Browse Product
This release contains the initial version of a summary browse product. You
may access it by clicking the Browse button at the bottom of the DAPS
user interface, then choosing Summary from the choice list. The browse
product consists of two parts, a listing (on a per-day basis) of products, and a
graphical display of the observations taken on a given day. To choose a
product for a given day, click on the appropriate entry in the list of days.
The graphical display consists of two images. These images consist of a
sequence of 48 horizontal lines. For each line there is a corresponding time;
the sequence of times is a timeline taken at 30-minute intervals through the
day.
Each horizontal line in the images describes the observation taking place at
that time. The first image is a sequence of spectra derived by binning FUV
data by 64 in the spatial dimension and by 16 in the spectral dimension. The
second image is a sequence of spatial lines derived by binning FUV data by
1024 in the spectral dimension. There are 64 elements in a line. The color
of the element corresponds to the log of the total counts for that element as
derived from the binning process.
Each line is prefixed by four squares indicating the on/off status of the four
UVIS channels. The On state is indicated by green for HDAC, yellow for
HSP, white for EUV, and red for FUV. The Off state is indicated by the
background color (dark blue).
If the user clicks on a horizontal line, five pieces of information are
displayed at the bottom of the page: the product timeline value, the start and
stop time of the observation from which the line was produced, its name, and
DAPS V2.0 User’s Guide – 11/99
the FUV observation type from which the line was generated. Through cut
and paste, you can transfer this information back to the DAPS interface to
specify query parameters.
To leave the browse product display select Close from the browser file
menu.
21
DAPS V2.0 User’s Guide – 11/99
22
Appendix A - Document Figures
1
2
3
11
4
5
6
6.1
7
12
8
9
9.1
11
13
14
15
16
Figure 1: The DAPS V1.0 user interface
17
DAPS V2.0 User’s Guide – 11/99
Figure 2: Example of metadata listing
23
DAPS V2.0 User’s Guide – 11/99
Figure 3: Example of data transfer
24
DAPS V2.0 User’s Guide – 11/99
.
Figure 4: Example of housekeeping data query
25
DAPS V2.0 User’s Guide – 11/99
26
Appendix B - System Setup and Installation
1. Introduction
Running the DAPS requires installing two off-the-shelf software packages.
The Java plug-in is a browser plug-in that enables Internet Explorer and
Netscape Navigator to run Java code based on up-to-date Java releases. The
Java Development Kit is a set of utilities used to support Java application
development and execution. Section 2 below describes the Java plug-in;
Section 3 describes the JDK.
2. Installing the Java Plug-In on IE/Windows and
Netscape/Solaris
The following paragraph is excerpted from the Sun Microsystems web
page at http://java.sun.com/products/plugin/1.1.3/index-1.1.3.html:
On Internet Explorer: The first time a user's web browser
comes across a web page that is enabled for the Java plug-in
product, it automatically downloads and installs the Java plugin software (and hence the latest implementation of the JRE)
on the user's system. From that point forward, the browser
will automatically invoke the Java plug-in software every time
it comes across web pages that support the technology—
completely transparent to the end user.
On Netscape Navigator: The first time a user's Web browser
comes across a Web page that is enabled for the Java Plug-in
product, it redirects the user to a web page to download and
install the Java plug-in software on the user's system. From that
point forward, the browser will automatically invoke the Java
plug-in software every time it comes across Web pages that
support the technology—completely transparent to the end user.
Note that on IE/Windows, if the plug-in does not install automatically, it will
have to be installed manually. This requires administrator privileges.
DAPS V2.0 User’s Guide – 11/99
27
3. Installing/Upgrading MRJ 2.1
The Java Development Kit (JDK) is available from Sun Microsystems for
the Solaris and Windows platforms. The URL for JDK downloads is
http://java.sun.com/products/jdk/1.1/
The Macintosh version of the JDK is the Java SDK; it is available from
http://developer.apple.com/java/text/download.html#sdk
For Macintoshes running operating systems prior to OS8.5, an additional
download is required. MRJ 2.1 is the Java Virtual Machine used by Internet
Explorer. It is included with OS8.5 and later. However, for older operating
systems or for upgrades to MRJ see:
http://developer.apple.com/java/text/download.html
The following description of MRJ 2.1.2 is excerpted from Apple's web page
at http://developer.apple.com/java/text/download
MacOS Runtime for Java (MRJ) 2.1.2 is Apple's implementation of the Java
Virtual Machine (JVM), based on Sun Microsystems' Java 1.1.7
specification. MRJ allows you to run Java applications and applets. MRJ
2.1.2 makes many improvements over Apple's previous JVM, including
greatly increased performance, improved reliability, and support for
AppleScript and Sun's JFC/Swing. MRJ 2.1.2 also runs more applications
and applets than earlier versions.
MRJ 2.1.2 Installer
NOTE: In order to install this package, you will need Disk Copy.
Minimum System Requirements for MRJ 2.1.2:
• Macintosh computer with a PowerPC processor.
• System 7.6.1 or later.
• 32 megabytes (MB) of RAM are recommended, with virtual memory
turned on and set to at least 33 MB. Installing more than 32 MB of RAM
will greatly improve performance and increase the number of Java
applets and applications that can run simultaneously.
• At least 20 MB of free disk space.
DAPS V2.0 User’s Guide – 11/99
28
• Using Java applets over the Internet requires Open Transport 1.1 or later
and an active Internet connection.
• You may experience improved performance if you have QuickTime 3.0
installed. QuickTime 3.0 is installed with Mac OS 8.5, or you can
download it from Apple's QuickTime website.
NOTE: Microsoft Internet Explorer and Apple Applet Runner currently
work with MRJ. Netscape Communicator and Navigator 4.5 currently use
their own internal Java Virtual Machine and cannot be configured to use
MRJ. Apple is currently working with Netscape so that future versions of
Netscape Communicator and Navigator will support MRJ.
29
Appendix C - Additional Information
1. Known Problems and Liens
All of the capabilities delivered with DAPS V2.0 have been extensively
tested, with the exception of the complex query described in paragraph 3.
Below is a list of known errors and liens.
Known Errors
The start time of some HDAC data sets is incorrect. This problem seems to
occur only when the filament voltage tables are non-zero. This may be a
flight code error or a L0 to L1A processing error.
Known Liens
The HSP timing information is not part of the archived data.
The HSP and HDAC data-set stop time is approximate. The real stop time is
earlier than reported. Consequently, the data array in the NetCDF file can be
oversized.
The start times reported in status window are correct to about 0.5 seconds.
The start times reported in the NetCDF files should be used instead.
The DAPS does not support standard input time format.
On a Window machine, when doing a large query, the status of the query
stops being reported to the status window. Everything looks like the query
has terminated. In fact, the execution of the query is continuing.
The memory requirements on the client machine are not currently well
understood. For example, on a 64Kbyte Macintosh, some large data sets
cannot be transferred, as IE runs out of memory.
2. Note on Start-Time Metadata Information
The start time reported in the metadata is the time of the first integration
interrupt.
DAPS V2.0 User’s Guide – 11/99
30
For example, assuming an FUV data set where the integration time is 32
seconds: the start time in the data-set metadata is the time of the first
interrupt. The data in the first record of the data set were acquired between
the start time − 32 seconds and the start time.