| ReWARD Project Refraction/Wide-Angle Reflections Database |
INGV-Italy
Unit of Milano |
 |
| ReWARD Project Refraction/Wide-Angle Reflections Database |
INGV-Italy
Unit of Milano |
|
Software information copied from Lennartz public documentation given with its free software package:
NAME
fdls - shows directory
listing of a MARS-88
floppy disk
INTRODUCTION
The
fdls program is furnished on a
3.5" MSDOS disk formatted at 1.44 MB. In order to run it, you need an
IBM
compatible computer equipped with a suitable disk drive, a suitable
BIOS that
supports disk format 4 (1.44 MB) and a suitable version of MSDOS or
PCDOS. We
have verified correct operation with MSDOS 3.20 on an AST Premium/286
with the
AST BIOS dated 10/23/86.
SYNOPSIS
fdls
device
DESCRIPTION
The
fdls utility can be used to get a
directory listing of a MARS-88 floppy disk. The directory is written to
standard output. Besides the file name, the size of the file (in bytes)
and its
modes are indicated. In the three-character mode string, 'r' stands for
read
permission, 'w' stands for write permission, and 'b' stands for binary
file
(this information is relevant only for MARS-88 internal purposes, and
is likely
to disappear in a future release).
The
date of creation and the last modification date
are also indicated in a format comparable with the format used by ls(1)
on Unix
systems.
There
are no command line options available. The
device name must be given; no default value is assumed.
EXAMPLE
fdls
b:
get
MARS-88 directory from the floppy in the
drive B: (MSDOS)
fdls
/dev/rdsk/fd0
get
MARS-88 directory from the floppy in the
drive known to Unix as the special device file 'dev/rdsk/fd0'.
KNOWN
PROBLEMS
On
some systems (depending on the particular
operating system) it's not possible to use a write-protected MARS-88
floppy,
even if it's accessed only for reading.
AUTHOR
Lennartz
electronic GmbH. The executable program
file is placed in the public domain. You may do with it whatever you
want,
except sell it for profit. Lennartz electronic GmbH, by making it
available to
you, does not assume any responsibility for damages caused by this
program. The
WARRANTY section in the front of the MARS-88 Operation manual applies
to this
program and documentation.
RELEASE
INFORMATION
1.8
of 90/02/09
TRADEMARKS
Unix:
AT&T
Bell labs.
MSDOS:
Microsoft
Corp.
IBM:
International Business machines.
NAME
marsdump
- dump MARS-88 data to local file
system
SYNOPSIS
marsdump
[-options]
INTRODUCTION
The
marsdump program is furnished on a
3.5" MSDOS disk formatted at 1.44 MB. In order to run it, you need an
IBM
compatible computer equipped with a suitable disk drive, a suitable
BIOS that
supports disk format 4 (1.44 MB) and a suitable version of MSDOS or
PCDOS. We have
verified correct operation with MSDOS 3.20 on an AST Premium/286 with
the AST
BIOS dated 10/23/86.
The
marsdump program is also part of the
Unix-based FDM software package. This documentation applies to both
versions.
DESCRIPTION
The
marsdump program allows reading the
contents of a 3.5" floppy disk written by MARS-88/FD system.
Output
consists of files (one file per channel and per event). By default,
these files
contain ASCII data (one sample per line). The first line in the file is
a
comment line (with a '#' as its first character). This line describes
the
device ID, sampling rate, channel number, scale, and starting time of
the data.
COMMAND
LINE OPTIONS
-b
Write
output files as binary files (as opposed
to ASCII files). The binary data format is described in a MARS-88
Application Note.
-c
chno
Extract
only data for channel chno. This
option may be given only omce on the command line. For example, you can
not use
"-c 0 -c 1" to extract channels 0 and 1 only.
-d
devid
Search
for files written by the instrument with
the device ID devid. The device ID can also be
communicated to the
program via the environment variable MARS_DEVID.
The devid specified on
the command line takes precedence over the setting of the environment
variable,
though. The device ID of the instrument that has written the data can
be found
out by looking at the disk's directory with the fdls(1)
utility. MARS-88
file names are of the form m88_nnnnn.dat
where nnnnn is the five digit device
ID.
-e
Use
extended file names. See below for a detailed
explanation.
-f
firsttime
Do
not dump data from the beginning of the disk,
but first search for data starting at firsttime.
Firsttime is entered as
yy(yy)mmddhhmmss (yyyy for years after 1999). E.g.: 890823140000 for
August 23,
1989, 2 p.m.; or 20010318080015 for March 18, 2001, 08:00:15. If this
option is
not used, dumping will start with the first data on the disk.
-l
lasttime
Stop
dumping after having found data later than lasttime.
If this option is not used, all data up to the end of the disk will be
dumped.
-n
No
comment line. This option omits the first
line in the ASCII output file. If the -b option is selected, this
option is
meaningless.
-p
pathname
Look
for the MARS-88 floppy on the device
indicated by pathname. The pathname can also be
communicated to the
program via the environment variable MARS_PATH. The
pathname
given on the command line takes precedence over the setting of the
environment
variable, though. Under MSDOS, the trailing semicolon must be part of
the
pathname (e.g. '-p B:'). Under Unix, the path name must not include the
trailing slash. See the EXAMPLES section for an
MSDOS and a Unix
example.
-s
Setup
blocks are written to a file named
"setup" in the target directory. This is an ASCII file even if the -b
option has been selected. It contains the setting of all important
parameters
in a human readable format. For each setup block, the beginning of its
validity
is printed at the beginning.
-t
List
only Table of Contents to standard output.
Do not dump any data. Firsttime and lasttime settings are ignored. The
Table of
Contents (TOC) consists of the number of the event, the starting and
ending
time, and the number of blocks in the event. The TOC is derived from
channel 0
data. Thus, it reflects only "events" recognized from channel 0
blocks.
-v
Verbose.
If this option is used, diagnostic
messages are written to stderr.
-x
Print
data words in hexadecimal instead of
decimal. Only useful for ASCII output.
EXAMPLES
marsdump
-t
Get
the
Table of Contents only. The path name and device ID are read from the
environment variables MARS_PATH and MARS_DEVID,
respectively. If
these variables are not set, the program uses built-in defaults which
most
certainly won't match your particular configuration.
marsdump
-p A: -d 12 -t
(MSDOS
example).Get the TOC of the MARS-88
floppy in drive A:; the device ID is '12'.
marsdump
-p /dev/rdsk/fd1mf2hd -d 14
(Unix example). Dump the whole contents of the MARS-88
floppy that resides in '/dev/rdsk/fd1mf2hd'; the device ID is '14'.
marsdump
-d 22 -f 890830123000 -l
890830130000
Dump
data that fall within the range Aug. 30,
1989, 12:30 to 13:00; the device ID is 22; the default path (or the
path set in
MARS_PATH) is used.
PROGRAM
STRUCTURE
The
marsdump program first checks the
correspondence between the data and index files. Then, it reads the
entire
index file. If the user has selected the TOC option ( -t ) the Table of
Contents is generated and printed, and the program finishes without
even
looking at the data file. The table of contents reflects the contents
of
channel 0 only.
If
the user has entered first and last times,
the program then checks if any data fall within the user-selected
range. If
this is not the case, an appropriate message is generated, and the
program
stops. If data matching the user's range is found, the program then
seeks the
correct position in the data file and starts extracting blocks. If the
setup
blocks option ( -s ) has been selected, setup blocks are extracted
first. Then,
it steps through the data file channel by channel. That is, channel 0
is
extracted first, then channel 1, then channel 2. This means that events
are
built on a single-channel basis.
OUTPUT
FILE NAMES - DEFAULT CASE
By
default, marsdump creates ASCII files.
The files are named evnn_chm.asc where nn
is the number of the event
(starting at 0) and m is the channel number (0, I or
2). An example
would be ev23_ch2.asc (event number 23, channel 2).
For
binary files (see the -b command line
option), the file name in the above example would be ev23_ch2.bin.
OUTPUT
FILE NAMES - EXTENDED
By
using the -e command line option,
output file names are named according to a different scheme. The idea
is to
have more descriptive file names. However, operating system
restrictions (file
name length!) prevent the use of truly intuitive file names. Thus, a
compromise
had to be found.
Under
MSDOS, file names are limited to a
length of 11 characters, with a period ('.') inserted after the eighth
character. 11 characters are not enough to accommodate the complete
starting
time (this alone would take 12 characters) and the channel number.
Thus, the
year has been left out (reducing the starting time to 10 characters)
and the
channel number is simply appended at the end. As an example, an event
starting
at Feb.6, 1990, 14h30m20s, channel 1, would be named:
02061430201 but
the operating system would convert this
into: 02061430.201
We
leave it up to you if you find this format
more descriptive than the default format.
Under
Unix, the situation is better.
Here, 14 characters file names are always supported, and the operating
system
does not insert a period in the filename. Thus, under Unix, we can
afford the
full 12-character time string plus one additional character ('c') to
separate
time and channel number. Our above example would look as follows under Unix:
900206143020c1.
Obviously
, in the extended file name
case, the file name can no longer be used to tell the difference
between an
ASCII and a binary file. You must take care of that distinction
yourself.
Further,
the device ID is also not included in
the file name. It is recommended to put files coming from different
devices
into different directories by judicious use of the MARS_TARGET
environment variable.
DIAGNOSTICS
WARNING:
EXPONENT <n> DATA !
This
warning message appears if the program
encounters data written with a non-default format (that is, data
created with
exponent not equal to zero). In the case of ASCII files, the resulting
output
data will are the equivalents of 32-bit long integers, and will have to
be
divided by 65536 before comparing them with data written at exponent 0.
Possible decimal digits may appear in the division (increased
resolution).
error
opening output file(s)
This
error occurs if either the environment
variables HOME or MARS_TARGET indicate an invalid directory, or if the
target
disk or directory is full or write-protected.
last
time later than first time
Incorrect
setting of the -l and -f options.
'filename.dat'
does not exist
Unable
to find the data file. Perhaps the device
ID and/or the pathname were set incorrectly.
index
file 'filename.inx' does not
exist - use ifck..
The
data file was found, but the corresponding
index file is not present. On a Unix system, you can use ifck(1) to
rebuilt the
index file from the data file.
index
and data file size
inconsistent - use ifck..
Both
index and data files were found, but their
sizes do not coincide. Probably the disk was not completely written.
error
reading index file
Very
unlikely message. Please notify us and, if
possible, include the offending disk.
CAVEATS
Output
files are written to the directory
indicated by the MARS_TARGET environment variable.
If MARS_TARGET has
not been set, marsdump attempts to write output
files to the directory
indicated by the HOME environment variable. If
neither of these two is
set, output files are written to the current directory, and an
appropriate
warning message is issued. It is good practice to allocate a separate
target
directory for each device ID.
The
method for setting environment variables is
different depending on your command line interpreter (shell). To set an
environment variable in MSDOS use the syntax:
set MARS_TARGET=C:\DATA
Under
the Unix sh(1) or ksh(1) shells, you would
use: MARS_TARGET=/urs/myhome/data
and
under the Unix csh(1): setenv
MARS_TARGET /usr/myhome/data
Note
that there should be no blanks before or
after the "=" sign!
There
is no error checking (e.g. for a
"disk full" condition) when writing output files.
Previously
existing files in the target
directory are overwritten. To avoid confusion, you may want to delete
all files
in the target directory before dumping another disk.
KNOWN
PROBLEMS
On
some systems (depending on the particular
operating system) it's not possible to use a write-protected MARS-88
floppy,
even if it's accessed only for reading.
AUTHOR
Lennartz
electronic GmbH. The executable program
file is placed in the public domain. You may do with it whatever you
want,
except sell it for profit. Lennartz electronic GmbH, by making it
available to
you, does not assume any responsibility for damages caused by this
program. The
WARRANTY section in the front of the MARS-88 Operation manual applies
to this
program and documentation.
SEE
ALSO
fdls(1)
RELEASE
INFORMATION
1.8
of 90/02/09
TRADEMARKS
Unix:
AT&T Bell labs.
MSDOS:
Microsoft
Corp.
IBM:
International Business machines.
marssave -
save a setup file to a MARS-88 floppy
disk
marslist
- list a setup file from a MARS-88 floppy
disk
INTRODUCTION
The
marssave and marslist programs
are furnished on a 3.5" MSDOS disk formatted at 1.44 MB. In order to
run
them, you need an IBM compatible computer equipped with a suitable disk
drive,
a suitable BIOS that supports disk format 4 (1.44 MB) and a suitable
version of
MSDOS or PCDOS. We have verified correct operation with MSDOS 3.20 on
an AST
Premium/286 with the AST BIOS dated 10/23/86.
SYNOPSIS
marssave
| marslist device setup no
DESCRIPTION
The
marssave utility can be used to write
a setup file to a MARS-88 floppy disk. Input is read from stdin,
so you
will want to prepare a setup file with your local text editor and then
use
input redirection.
The
marslist utility reads a setup file
from a MARS-88 floppy disk and writes it to stdout,
so you will want to
save the output of marslist in a file of your
choice, using the
operating system's output redirection feature.
For
both utilities, you must give a device name
(e.g. BJ
and the number of the setup file. Do not use numbers less than zero or
greater
than 99.
EXAMPLES
marslist
b: 2 >myfile
reads
the MARS-88 file 'setup_02.cmd' from drive
B: and writes its contents to the local file 'myfile'.
marssave
b: 1 <infile
reads
the contents of the local file 'infile'
and saves them on the MARS-88 floppy in drive B: under the name
'setup_01.cmd'.
SEE
ALSO
The
manual pages for save setup and list
setup in the MARS-88 Operating Manual.
KNOWN
PROBLEMS
On
some systems (depending on the particular
operating system) it's not possible to use a write-protected MARS-88
floppy,
even if it's accessed only for reading.
AUTHOR
Lennartz
electronic GmbH. The executable program
file is placed in the public domain. You may do with it whatever you
want,
except sell it for profit. Lennartz electronic GmbH, by making it
available to
you, does not assume any responsibility for damages caused by this
program. The
WARRANTY section in the front of the MARS-88 Operation manual applies
to this
program and documentation.
RELEASE
INFORMATION
1.8
of 90/02/09
TRADEMARKS
Unix:
AT&T Bell labs.
MSDOS:
Microsoft
Corp.
IBM:
International Business machines.