Speech:Spring 2015 Kyle Poirier Log


 * Home
 * Semesters
 * Spring 2015
 * Proposal
 * Report
 * Information - General Project Information
 * Experiments - List of speech experiments

Week Ending February 3, 2015
1/31/15
 * Task:
 * Read logs from previous semesters.
 * Read logs of systems groups from all previous semesters.
 * Set up a virtual linux machine on my personal computer.
 * Research redhat and learn more about it.

2/1/15
 * Read through more logs.
 * Practice using a linux machine.

1/31/15
 * Results:
 * Read logs from previous semester and read over previous systems groups logs.
 * Installed a virtual linux machine on my personal computer.
 * Researched redhat and read material relating to the software.

2/1/15
 * Practiced using virtual linux machine to become familiar with controls and commands.
 * Read through more logs from previous systems teams.

2/3/15
 * Read through more logs.
 * Read through RedHat installation logs.

1/31/15 1/31/15
 * Plan:
 * Work with the systems team to convert the current system over to use the redhat system.
 * Find a way to backup the current system in case of any issues.
 * Concerns:
 * Learning all of the appropriate material and converting the system without issues.

Week Ending February 10, 2015
1/5/15
 * Task:
 * Read logs.
 * Practice Linux commands.
 * Work with systems group to install Red Hat on methusalix using documentation.

Practice commmands, look through experiments, learn how to complete a train.
 * Meet with group this week to get Red Hat functioning properly on the donated server.

1/6/15
 * Read logs.
 * Practice Linux commands.

1/5/15
 * Results:
 * Read logs.
 * Practiced commands on virtual machine.

1/6/15
 * Read logs.
 * Practiced Linux commands.


 * Plan:


 * Concerns:

Week Ending February 17, 2015

 * Task:

2/11/15
 * Results:
 * Logged into Caesar as root to change my password because it was lost.
 * Read and tested some perl code.
 * Installed SSH Secure Shell on my personal computer.

2/12/15
 * Read logs on training, tools, and experiments.
 * Read through other group logs and personal logs.
 * Installed a ssh client on my cell phone so I can have access to Ceasar whenever and wherever I need it.

2/14/15 2/14/15
 * Plan:
 * Work with systems group to begin copying files from Caesar to Brutus.
 * Begin testing the Brutus server to ensure it functions the same as Caesar.
 * Eventually turn off Caesar and user Brutus as the main server.
 * Concerns:
 * Being able to access the server room when we need to.
 * Copying all of the files from Caesar to Brutus without issues.

Week Ending February 24, 2015
2/21/15
 * Task:
 * Figure out how to create a network bridge so the drones can access the internet.
 * Read logs and understand more of the training and experiment process.

2/23/15
 * Read the wiki pages for training and experiments.
 * Read more logs about training and experiments.
 * Still trying to find a solution for the network issue. Difficult to try some things because of the risk of disconnecting Caesar.

2/24/15
 * Results:
 * Mohamed was able to figure out the network issue and activate RedHat.

2/22/15
 * Plan:
 * Figure out the network bridge.

2/24/15 2/22/15
 * Complete the same network configurations on the rest of the drones and make sure they are activated.
 * Begin the process of getting Brutus online and ready.
 * Concerns:
 * Getting the network bridge to work properly.
 * Having an easy transition to the new server and no serious issues during the process.

2/23/15
 * The network issue has become a main concern and has been very difficult to understand and figure out.

Week Ending March 3, 2015
2/25/15
 * Task:
 * The systems group met after class and we were going to activate RedHat on the Brutus server but when we turned the system on it was not running properly. We followed the documentation a second time and reinstalled RedHat (64 bit) on the Brutus server.

3/1/15
 * Still going through various directories looking for a good one to complete a test cp with sub-directories inside it as well.


 * Also been looking through the wiki to see if something similar has been done in the past.

2/25/15
 * Results:
 * We weren't able to get the system activated because we were unable to get it connected to the network. We will likely have to do some network card configuring to get it to work. The system may not be reading from the correct network card.

3/2/15
 * I was unable to meet with my group today due to a scheduling conflict. The rest of the group stayed late after a class to begin copying all of the data from Caesar to Brutus. If everything works as planned we will be able to start trains on Brutus as soon as all the data has been copied over correctly.

2/27/15
 * Plan:
 * Working on figuring out the -cp command and using it with the -r so that all the files will be saved recursively. I am working on trying to find a good smaller directory to copy so that I can test whether or not this will work. I will attempt to do this on a much smaller scale and then slightly larger until we are ready to transfer all of the 500gb+ data.

3/3/15 2/27/15
 * Tomorrow I will be going through Brutus and making sure all the directories were copied over correctly and have all the same permissions.
 * Concerns:
 * Getting the data to copy correctly and recursively because if this holds us back it will cause a lot of stress for our group because we need to begin the trains on Brutus as soon as possible.

Week Ending March 10, 2015
3/4/15
 * Task:
 * Verify that all the permissions were carried over properly from Caesar to Brutus.

3/10/15
 * Need to continue with the rest of the verification and document it in the systems group page. Also we need to document everything we do doing the switch over so that if it works it can be repeated by others in the future.

3/5/15
 * Results:
 * Verification is done for my assigned Exp/ directories and everything is the same. I verified around 20 of the experiment directories.

3/4/15
 * Plan:
 * The group is meeting Friday 5:00 to complete the transition over to Brutus and turn it into the new Caesar.

3/5/15
 * Group was planning to meet later in the day (5:00) but it seems that the school is closing early.

3/9/10 3/4/15
 * Complete verification and verify some directories outside of the Exp/ directory.
 * Concerns:
 * Slightly concerned of any issues occurring when a train and decode is run on Brutus and then from Verleihnix to Brutus but so far everything has gone well and it seems as though it should work.

3/10/15
 * The switch over to the new server hasn't been going very smoothly so far. We have been having some difficulties getting some of the network and mounting issues worked out. It is also difficult for us to work together when a few of our schedules do not line up so we will have to work somewhat separately for the next few tasks.

Week Ending March 24, 2015

 * Task:


 * Results:


 * Plan:


 * Concerns:

Week Ending March 31, 2015
3/28/15
 * Task:
 * Work with Chris from the systems group to complete our tasks for documenting and editing the current documentation of the systems group page.
 * Complete a train now that Caesar is back up and running, I tried running one on Wednesday but it froze, likely do to the amount of people logged in also trying to run a train.
 * Work with systems group to mount the remaining servers to the new Caesar so that they can be allocated for the two groups.

3/29/15
 * Once all of the drones are set up I plan to run a train from one to Caesar.
 * Still working with the systems group to complete any tasks we may still need to finish.

3/29/15
 * Results:
 * Still reading through a lot of logs and trying to gain a better understanding of the training process.

3/30/15
 * I was unable to meet with the systems group today to mount the drone servers. The rest of the group was able to successfully mount the drones without issues. Schedule conflicts have been hard to work around.
 * I have been continuing to read through previous logs. I have reread through many of them to make sure that I understand the key parts that could help further understand the process as a whole.

3/28/15
 * Plan:
 * I plan to complete go through a train and research further into the process so that I fully understand what is happening in the background in order to offer suggestions on how to lower our error rate.
 * Stay in connection with the rest of the system group members so that we can complete the mounting process and make sure that all of our tasks through the semester have been documented properly and with detail, if we find anything missing it will be added to the page accordingly.

3/30/15 3/28/15
 * Finish the remaining steps in order to completely finish my train.
 * Finish any remaining tasks that have been assigned to me.
 * Concerns:
 * Keeping Caesar up and running without any errors, it helps that the majority of the construction process is complete and they likely won't be shutting the power off again hopefully.

3/29/15
 * Being successful in lowering our error rate.

3/31/15
 * I have had to change the password for my username multiple times without it being deleted or the original user perl script being run, I am wondering if there is a possibly issue happening somewhere that is causing usernames to be reset. Multiple people have also been complaining about this issue.

Week Ending April 7, 2015
3/3/15
 * Task:
 * Run a 125hr train and continue researching what could change our error rate.

3/6/15
 * Results:
 * My laptops hard drive got corrupted due to a battery failure. I didn't have a backup but was able to purchase a new hard drive and install it. I was also able to get Windows 7 through the DreamSpark program and installed the OS to the new hard drive. I hope to be able to recover some of my data from the corrupted hard drive. I should have had everything backed up. I wasn't able to get much done this week without my computer working and without my all of my files.

3/6/15 3/1/15
 * Plan:
 * Recover any and all data I can from the old hard drive and go through any notes that can be recovered. I was in the process of researching what could possibly lower our error rate.
 * I want to try and run a 125hr train once I have time and no longer need to worry about my personal devices.
 * Concerns:
 * Deciding and agreeing on which type of train we should go with; 125hr or 256hr, and how it will affect our results.

Week Ending April 14, 2015

 * Task:


 * Results:


 * Plan:


 * Concerns:

Week Ending April 21, 2015

 * Task:


 * Results:


 * Plan:


 * Concerns:

Week Ending April 28, 2015
4/24/15
 * Task:
 * Create more experiments but begin creating them inside their own folder. I have originally been deleting the contents of the same folder and running trains in it and just deleting everything once I was done. I will begin creating more folders in order to not lose track of any changes that may better my error rate.

4/28/15
 * Run more trains with an adjustment to the dictionary, look through the data that is being checked for.

4/26/15
 * Results:
 * Ran a few trains but was unable to get a significant change in results.

4/28/15
 * All the trains I have run up to this point have had no significant change to my error rate.

4/28/15 4/25/15
 * Plan:
 * Continue to edit scripts and see what changes improve my error rate.
 * Concerns:
 * Being able to get a lower error rate. The amount of changes that I have made had no significant changes and barely changed my results whether it be positive or negative. I did have one result much worse than before but unfortunately deleted it.

Week Ending May 5, 2015

 * Task:


 * Results:


 * Plan:


 * Concerns: