Speech:Spring 2016 Tools Group

From Openitware
Jump to: navigation, search


Group Member Logs

Assigned machine is: Majestix -


  • Read previous semesters work to better understand project and determine current tools.
  • Research other tools to determine if there's something better out there than what we currently have.
  • Write proposal by the end of February.
  • 3/9 Spring break task
    1. SSH key gen connect in order to establish seamless login (using without password) from Ceaser to
      1. asterix
      2. majestix
    2. In case of losing file, find software for comparing application
    3. Research and install emacs, screen tree, SCLite on majestix
    4. Install compiler
  • 3/23 Install on Majestix:
    1. Tree
    2. Emacs
    3. Screen
    4. SSH seamless login into Ceaser
    5. Figure out way of installation
    6. rSync - talk with Josh (IT guy) about backup destination.
    7. Red Hat Registration - talk with Bruce (IT guy).

Group Log

Feb 3

  • Logged in as root.
  • Discussed Tools group's tasks.
  • Discussed current software configuration.
  • Discussed Emacs and other possible software upgrades.
  • Diccussed about proposal document and assign task to each group member.
Using rsync to fix sox dependencies on Caesar
--- Using rsync ---
# Step 1. log into Caesar and attempt to run sox. This will give you an idea of what files are missing.
sox: error while loading shared libraries: libuuid.so.1: cannot open shared object file: No such file or directory
brutus (base install)

# Step 2. ssh to brutus
ssh root@brutus
# Step 3. Locate missing file on brutus
whereis libuuid.so.1
# Step 4. Use rsync to compare directories
rsync -avn --ignore-existing /lib/libuuid* root@caesar:/lib/
# This will find all files starting with libuuid and compare to those that exist on caesar in the same dir. /lib
# Using -n makes rsync run in dry mode (don't do anything) 
# Using -a means archive, this will preserve permissions and soft links
# --ignore-existing makes sure not to make changes to anything already on caesar.
# -v makes the output verbose
# Once all changes look ok, run without -n
# All matching files that are missing on target are copied. Including permissions.

March 2

Recommend backup of


March 7

Upgrade Recomendations:

  • Sphinx Decoder 3.7 to 3.8 - Not sure if we are currently using 7 or 8 because we are basing version number off a readme file on Caesar which, after downloading 3.8, is the same readme file for both versions. Despite this, there is no documentation that we could find on 3.8 changes on the Internet or in Github. Due to both of these setbacks our recommendation is to keep the decoder at the version that we are currently using.
  • Sphinx Decoder 3.7 to 4.5 - There are not many benefits to upgrading to version 4. There are pros and cons of each version, but altogether they are basically equal. Professor Jonas mentioned that he would rather stick with the C version of Sphinx during one of our classes. We can agree on this. Sphinx 4 has some nice-to-haves such as a java swing ui, but Sphinx 3 integrates better with the course (allows for heavy UNIX usage).
  • CMU Language Model Toolkit - Up-to-date.
  • Sphinx Trainer - No upgrade recommendation. There has been no new version since last year. We are currently using Sphinx Trainer 1.0 and the latest version is Sphinx Trainer 1.0.8. The new version adds a single sphinxtrain command in order to access all training processes. The new version also fixes some memory leaks and build issues. The downside is that the latest version is intended for use with Sphinx4 which we are not using.
  • CMU Dictionary - No upgrade recommendation. There has been no new version since last year. We are currently using CMU Dictionary 0.6 and the latest version is CMU Dictionary 0.7. The new version has a new file format and some more words.

Majestix Installations

GCC Install Documentation

SFTP File Transfer Documentation

Tree Install Documentation

Tree Usage Instruction

Screen Install Documentation

Screen Usage Instruction