Using the stand-alone executables

• Unix : Just find the correct executable (in the bin/ subdirectory of the QS distribution), move it somewhere in the user's path, and give the name Qs. If you do not have root privileges and want to try Qs from your area, find the correct executable and define a symbol Qs pointing to it. A typical sequence of commands would be : ⁷

  $ cd Qs/bin/SGI/
  $ mv IRIX64_R10000_IP27 Qs
  $ ln -s ./Qs ./Qsi
  $ pwd
  /usr/people/something/Qs/bin/SGI
  $ alias Qs /usr/people/something/Qs/bin/SGI/Qs
  $ alias Qsi /usr/people/something/Qs/bin/SGI/Qsi
  

• VMS & Windows : The executables that I distribute are at the current release with the exception that the FFT step is still based on a radix-2 algorithm. The reason for this is that I couldn't even try to build FFTW on these two architectures. To use the program from VMS you will need something like $Qs :== $dsk$12:[my.directory]QS.EXE in your login.com file. For windows, you will probably have to run QS via MS-DOS.

Footnotes

... be :⁷

QS can output VT100-compatible control characters to help making its output more readable (mainly by highlighting errors and warnings). Because these control characters are a nuisance when incorporated in a log file, the feature is off by default. To switch it on, you must create a copy of the executable (or, better still, make a link with ln -s) to a file with the name Qsi (i for ``interactive''). When QS is called as Qsi, it will emit control characters understandable by the great majority of terminal emulators.