bininstall40.tme

speech signal process tools

command:
.nf
.ft CW
% elmadmin -z
.ft R
.fi
.pp
Note that truncating the log file by other means would be ineffectual, since
\fIelmd\fR keeps the log file open at all times.  The next \fIelmd\fR
log file write would simply use the old file pointer, filling the file to the
original length.   The \fB-z\fR option must be used to truncate the
file.
.pp
A suggested method to clean up the log file every evening is to run the
following by your \fIcrontab\fR system.   You will need your system
administrator to set this up.
.nf
.ft CW
cp elm.log elm.log.old
elmadmin -z
.ft R
.fi
.sh 1 "Checking Out a License"
.pp
Before running any ESPS programs you must checkout an ESPS license.
This allows any user on the machine with a checked out license to run
ESPS programs.   An ESPS license must be checked out for each host that
you want to run ESPS programs on.  Only one license is required to be
checked out for each host (not related to the number of different user's
on that host).    
.pp
If you have as many ESPS licenses as you have
computers that you want to run ESPS programs on, then you can just
checkout a license for each of these computers and never free it.  You
will only need to checkout the license again, if the computer is
rebooted.  If you need to share ESPS licenses among some computers (that
is, you have more computers then you have licenses) then you need to use
\fIefree\fR to free the license on a particular machine when it is not
in use.
.pp
For details see the document \fILiving with the ESPS Floating License Manager
System\fR.
.pp
Note that \fIwaves+\fR is licensed on a per user basis, so the total
number of \fIwaves+\fR that can be run at a time is limited by the
number of available licenses.
.pp
If you are running ESPS or \fIwaves+\fR on a different CPU than the
license manager daemon is running on, you have to set the environment
variable \fBELM_HOST\fR to identify the name of the host on which the 
license manager daemon is running.  
For example, if the license manager daemon is running on a CPU
with hostname \fIfido\fR, you would do:
.nf
.ft CW
% setenv ELM_HOST fido
.ft R
.fi
.pp
This environment variable tells ESPS programs where the daemon is
running.   If you are running the ESPS program or \fIwaves+\fR on the
same host as the daemon, then it is not necessary to set
\fBELM_HOST\fR.  To checkout a license you do:
.nf
.ft CW
% echeckout
.ft R
.fi
.pp
\fIEcheckout\fR will checkout a license, if possible, and then wait in
the background.   It will tell you if it has succeeded and return a
process ID number.   To free the license use the command \fIefree\fR.
\fIEfree\fR can only be used by the same user that ran \fIecheckout\fR
to get the license.    Otherwise, the super-user can find the
\fIecheckout\fR with \fIps\fR and kill it.
.pp
You can check on the status of your licenses by using the command:
.ft CW
.nf
% elmadmin -l
.ft R
.fi
.sh 1 "Getting Ready to use Waves+"
.pp
The following section only applies if you also have \fIwaves+\fR.
.pp
Everyone that is going to use \fIwaves+\fR
should copy the following three files from \fI/usr/esps/lib/waves\fR: \fI.wave_pro\fR, 
\fInb_params\fR, and \fIwb_params\fR to their home directory.
These are parameter files for \fIwaves+\fR.   See the \fIwaves+\fR
manual page for details.
.pp
Users should also edit their path assignment in their \fI.cshrc\fR (or
whatever they use) to include \fI/usr/esps/bin\fR on their search path.
.pp
Copy the files in \fI/usr/esps/demo\fR to your working directory before
looking at them with \fIwaves+\fR.  
This version of \fIwaves+\fR will try to write
some temporary files to the dirctory that the input file comes from
(\fI/usr/esps/demo\fR in this case) and you might not have write
permission on this directory.   We consider this a bug, and this will be
changed in the next version.
.pp
Also note that all of the manual pages are stored online and can be
accessed by the command \fIeman\fR.
.pp
After you are satisfied that all is well, up to this point, you should
install the device driver, if you ordered it.   
Proceed to the instructions for installing the device driver.
You can delay this,
however, if you want to, since \fIwaves+\fR will operate without the
board.  
.sh 1 "Checking it Out"
.pp
The best way to check out the installation of
the product is to change into the directory \fI/usr/esps/demo\fR and run
the demo scripts in there.
There is a README file in that directory.  We strongly
suggest that you take the time to try these examples.  Not only do they
provide an introduction to some ESPS commands, but they serve as a check
on the installation.   Note that you must have write permission on this
directory to run the demos.  The assumption is that these will be run by
the ESPS installer/maintainer.  This is one reason why we prefer not to install
ESPS as root, but as a regular user.
.pp
If you do not have write permission on the \fIdemo\fR directory, simply
copy the contents to a directory that you can write into.
.pp
We also suggest that you use \fIeman -k\fR (followed by a keyword to
search for) to familiarize yourself with the system.  See the \fIeman\fR
manual page for details.  
.sh 1 "Using the X Window Version of Waves+"
.pp
For Sun systems, there are two copies of \fIwaves+\fR, \fIlabel\fR, and
\fIspectrum\fR.  The versions by these names are for the Suntools window
system.  For the X window system, use \fIxwaves+\fR, \fIxlabel\fR, and
\fIxspectrum\fR.   Non Sun systems only  have the X versions.
.pp
This version of xwaves+ is built under the xview toolkit (from Sun).   
XView clients must be run under an ICCCM compliant window manager for 
everything to work correctly.    In addition, the OpenLook fonts are
required.
.pp
The directory \fI/usr/esps/xview\fR contains a binary copy of the
OpenLook window manager, the OpenLook fonts, and a simple script to add
the fonts to your font path.   If you are running on a Sun system and
already have the OpenLook (or OpenWindows) package from Sun installed,
then you should be OK.  Otherwise, see the README file in
\fI/usr/esps/xview\fR and follow the instructions there.
.sh 1 "ESPS Compilation Environment"
.pp
The ESPS install script creates several programs to aid users who write
their own programs using the ESPS library.   \fIecc\fR invokes the C
compiler with the correct options to cause the ESPS include files and
library to be searched.  It can be used in cases where you would
normally use the \fIcc\fR command.  Additional \fIcc\fR options can be
specified with \fIecc\fR.   The program \fIemake\fR calls make with the
correct environment defined.  For more information on this, see
reference [1] and the \fIemake\fR manual page.  A prototype makefile
suitable for use with \fIemake\fR is in the ESPS \fIlib\fR directory.
.sh 1 "Hardcopy Plotting"
.pp
As distributed, the ESPS plot programs (except for \fIimage\fR and
\fIplotsgram\fR) assume a Tektronix compatible printer when the
\fB-Thardcopy\fR option is used.    Imagen laser printers are an example
of Tektronix compatible printers.    To use the ESPS plot commands with
any other type of printer or plotter, you must provide a program that
translates Tektronix codes into what your printer needs.   We provide
such a program for Postscript.  The program is public domain, and is in
the directory \fI/usr/esps/pub/tek2ps\fR.
.pp
To configure ESPS for another plot device edit the file
\fI/usr/esps/bin/esps_plot\fR.  This script is called by the plot
programs and passed the Tektronix plot commands on standard input.  You
must add commands here to take these and produce the correct plot
commands for your printer.
.pp
For a Postscript printer, do the following.  First compile and install
\fItek2ps\fR.   You must have write permission on the ESPS binary
directory to do the following.
.nf
.ft CW
% cd /usr/esps/pub/tek2ps
% emake install
.fi
.ft R
.pp
This should compile and install \fItek2ps\fR.   Now you need to edit
\fI/usr/esps/bin/esps_plot\fR.   We cannot tell you the exact command to
put in there, since it depends on exactly what command you give on your
system to queue postscript output to your printer.  But the line in the
file with \fItek2ps\fR on it, is probably close.   
The line you want in there is one that will pass the standard input
through \fItek2ps\fR and then queue the result to your Postscript
printer.    
Be sure to delete or
comment out the existing command for Imagen printers.  (Ignore the
warning about not editing this file.  This is a holdover from a previous
version of the system.)
.pp
Note that \fIimage\fR (and \fIplotsgram\fR, since it just calls \fIimage\fR)
can internally produce Postcript.  
However, you may have to edit the shell script \fIplotsgram\fR in
\fI/usr/esps/bin\fR to change the name of the spool program to what is
correct for your system.  Change the line that begins with
\fBPS_SPOOL_CMD\fR.   See the manual page for details.
.sh 1 "In Case of Difficulty"
.pp
If you have questions about the installation process
please call Entropic for help.
.sp
.TS
box,center,tab(;);
l | l.
Entropic Research Laboratory, Inc.;Voice: 202 547-1420
600 Pa. Ave. SE, Suite 202;FAX: [phone]
Washington, DC. 20003 USA;Email: [e-mail] (uunet!epiwrl!esps)
.TE