Speech:Spring 2012 Bethany Ross Log

From Openitware
Jump to: navigation, search


Week Ending February 13th, 2012

Task
  • Friday- Read logs and proposal.
  • Saturday- Read logs concerning issues with downloads.
  • Sunday- Downloaded Virtual Box and OpenSuse.
  • Monday- Played around with Virtual Box and OpenSuse. Read information about Sphinx 3 that was posted by other classmates. Attempted to log into caesar and majestix.
Results
  • Got Virtual Box and OpenSuse to work.
  • Couldn't find Sphinx 3 files, as others had stated.
  • I was able to log into caesar.
Plan
  • Talk to classmates about Sphinx 3.
  • Figure out how to log in majestix.
  • Discuss proposal with group.
Concerns
  • Unable to find Sphinx 3 files.
  • Unable to switch to majestix or other machines.

Week Ending February 20th, 2012

Task
  • Friday: Read logs and what was added to proposal.
  • Saturday: Read logs.
  • Sunday: Added to software groups part of the proposal. Did research into what open source cloud hosting could be used. Explored Casear to see what file types would need to be backed up.
  • Monday: Continued research as mentioned above.
Results
  • Possibly Google Code could be used to host files. I am going to do some more research on file size, types that can be uploaded to Google Code.
  • I will continue to look for other possible cloud services as well.
Plan
  • Create spreadsheet to identify which cloud hosting would be best.
Concerns
  • None currently.

Week Ending February 27th, 2012

Task
  • Friday: Read logs
  • Saturday: Read logs and proposal
  • Sunday: Wrote proposal about backing up system.
  • Monday: Finished proposal about speech software configuration and created timeline for backing up the system and creating the configuration table.
Results

Finished the two sections of the proposal and now have a timeline set up. This will help me to stay on track with what needs to be done for the project.

Plan

Next week I will complete the two sets of tasks that I assigned to myself in the proposal. Which are:

  • (2/28-3/6) Identify the files that need to be backed up and an open source service to use.
  • (2/28- 3/5) Begin creating table and determine what current version there are of the speech tools. Also where to find the current versions.
Concerns

My biggest concern at this point is finding the current and newest versions of the software tools. I think that it may take a large amount of time and research to do.

Week Ending March 5th, 2012

Task
  • Tuesday: Research Cloud Storage for speech tools on Caesar. Created Google Code account to upload files for purpose of backup. Started research on location of current and newest version of the speech tools.
  • Saturday: Read logs.
  • Sunday: Read logs.
  • Monday: Read README and installation guides for speech tools that are on Caesar to find information about current tools such as version number. Started to upload this information to the Information page about speech tools.
Results
  • Tuesday: Used http://alternativeto.net/software/ to research what backup storage could be used. Researched TierraCloud, JustCloud, ownCloud and GoogleCode. GoogleCode offers the most storage and does not require any additional downloads if the user needs to download a file that was backed up on the GoogleCode site. Started collecting links for online locations of speech tools.
  • Monday: Found some of the version information for the speech tools.
Plan

Next week I will complete the two sets of tasks that I assigned to myself in the proposal. Which are:

  • (3/6- 3/12) Determine what the newest version of the speech tools are and where to find them.
  • (3/6- 3/12) Upload files and post sign in information to wiki.
Concerns

Finding a website that has the older versions of the speech tools.

Week Ending March 19th, 2012

Task
  • Tuesday (3/6): Created table in Speech Software Functionality. The headers and therefore information that I need to research are Speech Tool, Current version (on Caesar), Newest Version, Does the newest version work with OpenSUSE11.3? and Differences between current and newest versions.
  • Tuesday (3/13): Read logs.
  • Friday: Read logs.
  • Monday: I had to reinstall openSUSE11.3 on my computer and downloaded Sphinx 4.
Results
  • Tuesday (3/6): Researched the current versions for Sphinx, CMU Language Model Toolkit, and SphinxTrain on Caesar. Found the source files on sourceforge via http://cmusphinx.sourceforge.net/wiki/download/ . Researched the newest versions for Sphinx, CMU Language Model Toolkit, and SphinxTrain.
  • Monday: I decided that the easiest way to figure out if the newest versions of the speech tools would be compatible with the version 11.3 would be to test them on my own computer. Because I could not find much information online about compatibility.
Plan

Finish infrastructure work. Finish the table on speech tools. Finish the cloud hosting service setup.

Concerns

I might run into some issues testing compatibility because I'm not too sure on how the programs work.

Week Ending March 26th, 2012

Task
  • Friday: Read logs to catch up with what I missed Tuesday.
  • Saturday: Added information to the Speech System Information page.
  • Sunday: Read logs.
  • Monday: Worked on Speech System Information page and back up page.
Results
  • Saturday: Most of what was added to the Speech System Information page was the last column detailing the differences between the current version of the speech tool and the newest version. This information was not very easy to find. I added a resource section to the bottom of the Speech System Information page that shows the websites where I got the information.
Plan
  • Read logs.
  • Make sure the infrastructure material is finalized then move on to the next task.
Concerns

None

Week Ending April 2nd, 2012

Task
  • Friday: Read logs
  • Saturday: Read logs
  • Sunday: Updated Information page
  • Monday: Finished Information page
Results

Posted on Information page

Plan

Not get locked out of class anymore.

Concerns

Not sure what I will be working on next week.

Week Ending April 9th, 2012

Task
  • Tuesday: Work on paragraphs for information pages. Emailed Aaron to figure out time for Skype meeting.
  • Friday: Skype meeting was conducted at 5:30pm.
  • Saturday: Read logs
  • Monday: Read logs or any other needed work.
Results
  • Tuesday: Met with group minus Aaron to figure out what time would work best and emailed Aaron. Worked on Speech System Information page and Backup page.
  • Friday: Skype meeting with Aaron and Michael. We got most of it to work using our own train numbers. We got up to "Run make_feats.pl". This where we all received the following error:

Configuration (e.g. etc/sphinx_train.cfg) not defined Compilation failed in require at ./scripts_pl/make_feats.pl line 43. BEGIN failed--compilation aborted at ./scripts_pl/make_feats.pl line After working on solutions for a while Aaron ended up doing the remaining steps out of train2 instead of our individual ones. He was using Teamviewer so we were able to see his screen and what was being done.

  • Saturday: Read logs.
  • Monday: Read logs.
Plan

Next week: Work as part of Group 1 using Experiment #0001 to get experiment to run correctly. Work on infrastructure section of poster and finish information pages.

Concerns

That we received the above errors when running.

Week Ending April 16th, 2012

Task
  • Tuesday: Work on information pages and infrastructure section of poster.
  • Friday: Skype meeting.
  • Sunday: Capstone Poster
  • Monday: Finished information pages and read logs.


Results
  • Friday: Skype meeting to figure out steps we need to take. Downloaded PSFTP so I was any to view the train1.html to see what steps had been completed for train1.
  • Sunday: Worked on inftastructure section of the poster for URC. Posted basic information about openSUSE and Sphinx. Posted some information about the other speech tools that are in use as well. Found the openSUSE logo which may be able to be used on the poster, so I uploaded the logo to the wiki.
  • Monday: Finished information pages.
Plan
  • Work with group to get experiment to run.
Concerns
  • I'm still a bit confused about what we currently have on automatix and what needs to be changed to get it to run.

Week Ending April 23rd, 2012

Task
  • Tuesday: Work in class with Jon and Brice to run direction from Summer 2011.
  • Friday: Skype meeting with Jon and Brice. Read logs to see if anyone else has encountered the errors that we received.
  • Sunday: Read logs.
  • Monday: Read logs.
Results
  • Tuesday: See Group log for results. Files were all copied and moved. Ran genTrans.pl.
  • Friday: See Group log for results. Ran genPhones.csh with no errors. Ran make_feats.pl and encountered major errors (see Group 1 wiki page). Posted to Google Group to see if anyone else got this error after searching online and changing scripts did not work.
Plan

Get make_feats.pl working and continue on.

Concerns

That no one responsed to our group's issue in Google Groups.

Week Ending April 30th, 2012

Task
  • Tuesday: Do a QA Check on Network Bridge information page. Decided in group what tasks would be assigned to everyone.
  • Saturday: Read logs.
  • Sunday: Read logs.
  • Monday: Worked on report.
Results
  • Tuesday: Edited Network Bridge page and uploaded images directly to page. Created outline on Report page with assignments listed.
  • Monday: Worked on Results section and reviewed sections of report.
Plan

Finish Report!

Concerns

The results are not really finalized yet so it is difficult to write them.

Week Ending May 7th, 2012

Task
  • Tuesday: Work on results section of report and help on other sections as needed.
  • Saturday: Read logs.
  • Sunday: Read logs.
  • Monday: Finalizing report.
Results

Finished Results section based upon what results currently are.

Plan

Make sure report is finished for Tuesday.

Concerns

Finishing report.