The Scream! software is available free-of-charge by request to mailto:scream@guralp.com . Please specify, when ordering, the operating system on which you wish to run the software.
Scream! for Windows is delivered as an installer packaged application so you will receive a single .exe file. Run this file and follow the instructions on screen. Please see Section 2.3 , page 10 for initial configuration steps.
Scream! for Unix/Linux can be delivered as either an RPM package or a .tar.gz compressed archive: please specify whichever is most appropriate when ordering. For users of Debian GNU Linux-based distributions, such as Ubuntu, the alien command can be used to create a .deb package from the RPM.
You can normally use your package manager to install in the usual fashion. On some systems, however, you may need to use the ‑‑nodeps option with rpm, the ‑‑force-depends option with dpkg or a similar option with other package managers. Please see Section 2.3, page 10 for initial configuration steps.
The archive is created with relative file-paths and contains, at its root, a single directory, scream- 4.5 . It should be unpacked (using tar ‑xzf scream‑ 4.5 .tar.gz or an equivalent command) into a suitable location, such as /usr/lib . After unpacking, you need to copy a file to the system library directory (usually /usr/lib ) and create a symbolic link. You normally need to have root authority to do this. Change your working directory to the scream‑ 4.5 directory and issue the following commands:
cp libborqt-6.9.0-qt2.3.so /usr/lib
cd /usr/lib
ln -s libborqt-6.9.0-qt2.3.so libborqt-6.9-qt2.3.so
You may wish to change the owner and group of the extracted files according to your local policy.
Once fully installed, the application should be started by with the command /{install_path}/ scream- 4.5 /scream . Please see Section 2.3 , page 10 for initial configuration steps.
Scream!'s S etup... screen (available under the F ile menu) allows you, amongst other things, to set the location of data files and log-files. It is wise to set these before proceeding. You can view the set-up screen at any time by keying Control-S .
The directories in which you choose to place these files must be writeable by you. They will be created when needed (if they do not already exist) as long as the parent directory is writeable by you.
Configured paths are not parsed by any command shell, so sequences such as ~ (home directory for Linux/Unix users) or %AppData% (the application data directory for Windows users) will not do what you might expect.
As the data files can grow quite large, Windows users who use roaming profiles should pick a location which avoids having to transfer these files over the network each time they log on or off. Similar concerns may apply to Linux/Unix users in complex network environments.
The directory used for storing incoming stream data is set using the Base Directory item on the Files tab of the set-up dialogue. For detailed control of the file-names used, see Section 9.2, page 100.
The directory used for storing logging information is set using the Directory item on the Event Log tab of the set-up dialogue. For more information, see Section 11, page 123.