Speech:Spring 2012 Aaron Green Log


 * Home
 * Semesters
 * Spring 2012
 * Proposal
 * Report

Week Ending February 6th, 2012

 * Task:


 * (Tuesday) Set Up Skype Meeting for Friday 11am to discuss Hardware expectations and tasking with Professor


 * (Wednesday) Read other students posts to this site and spoke with team over email. Competed wiki read of the Speech Project


 * (Friday) Held Skype conference call with team and professor to discuss expectations for the "Hardware Teams" overall project objectives. Outlined individual team member assignments with team mates. Damir and I will work on the documentation, analysis, and systematic approach to updating the software of the Caesar Server and the 9 machines it supports. Evan and Sky will work on a long term solution to installing a bridge/switch for the system so future updates can be facilitated easier. All of us will work on our individual wiki logs, team collaboration and updating the "Project General Info" wiki.


 * (Sat) emailed back and forth with Sky on setting up his wiki log. Updated my wiki log. Emailed Damir on our part of the project. He returned my email and noted that on Sunday we would look into our section of the project.


 * (Sun) Worked on Updating the Class wiki page. Emailed the the team about reviewing and adding to the class info page.


 * Results:


 * Plan:


 * Team meeting via Skype for Friday


 * Concerns:


 * Finishing the Proposal

Week Ending February 13th, 2012

 * Task:


 * (Wed) Updated my Wiki Site following the new guidelines. Corresponded with my team mates about our Skype meeting planned for this Thursday. Read logs and posts.


 * (Fri) Conducted online meeting with the team 11am.
 * (Sunday) Read logs


 * (Monday) Spoke with Damir and exchanged emails. Both of us are worked on hardware proposal and will submit it tonight,
 * Results:
 * Completed Hardware proposal and uploaded to wiki site. Proposal is a three phase approach to updating the software and will need some input from the team before implementation.


 * Plan:
 * Meet with team after class on Tuesday to scope out the server and see if our proposal is sound in functionally and within our time line.
 * Phases one and two can be completed within one week from the time that the proposal is approved.
 * Concerns:
 * Google site for class communication is still not up... I think this is a key factor in us completing this class project. Our team has used Skype to complete our meetings and such, which has worked well. However, we need the whole class online and marching in the same direction.

Week Ending February 20th, 2012

 * Task:
 * (Tuesday) Meet with team and discussed hardware update proposal and possible challenges. We need to update our proposal passed on the information that was noted during today's class. We plan to email each other during the week and come up with a better proposal.
 * (Wednesday) Read Class logs.


 * (Friday) Read Logs.


 * (Monday) So over the past two days Damir and I have gone back and forth about the pros and cons of upgrading the SUSE software of the server. In part, we seem to be hitting a road block with being able to identify actual diferences of the current system and the potential update. The integration and upgrade possibly has several benefits, but identifying how those benefits will interact with the other system software is where we seems to be hitting a road block. We have requested a meeting with the professor after class to discuss this issue.
 * Results:
 * Researched Open SUSE 13.1 and the available versions for our proposal.

http://en.opensuse.org/Portal:Project http://software.opensuse.org/121/en


 * Plan:
 * Continue to work with the team and the class on the project proposal and define our plan for SUSE update.
 * Concerns:
 * Is upgrading necessary and how will it affect the other parts of the project.

Week Ending February 27th, 2012

 * Task:
 * (Wednesday) Researched and found the following sites to help me finalize my project proposal.
 * http://www.cyberciti.biz/tips/linux-command-to-gathers-up-information-about-a-linux-system.html
 * http://en.opensuse.org/Terminal
 * http://www.cyberciti.biz/faq/check-ram-speed-linux/
 * http://www.cyberciti.biz/tips/top-linux-monitoring-tools.html
 * (Friday) Read Logs of other classmates and proposal from Spring 2011.
 * (Saturday) Finalized Hardware project. Will upload final version Sunday.
 * (Sunday) Made final edits to the Hardware Proposal and uploaded to the proposal site. If any classmates have any suggestions I would be happy to make the changes. Made updates to this wiki site.
 * (Monday) Read other classmates contributions to the proposal. Edited the introduction and made a first draft for others to review.
 * Results:
 * Final Hardware Proposal complete and uploaded to the Class Proposal Site. I spent most of my time this week investigating how to pull system information of the server from home. There are multiple Linux Commands that can help to pull this data from Caesar. The organization of the system components are relatively straight forward, however extracting the system data will take some command line savviness. The final proposal outlines my plan of attack for the final project.


 * Plan:
 * 1) Research Caesar/System calls that will allow me to create my proposal (Wednesday)
 * 2) Start Proposal outline and make first draft for proposal (Friday)
 * 3) Finalize Proposal and seek any input from class (Sunday)
 * 4) Read logs (Monday)
 * Concerns:
 * Running the command line in the most efficient manner possible to quickly pull the data from the database without out having to run multiple queries on the system.

Week Ending March 5th, 2012

 * Task:
 * Get my part of the project going
 * Results:
 * None


 * Plan:
 * Catch up
 * Concerns:
 * Falling behind

Week Ending March 19th, 2012

 * Task:
 * Get my part of the project going
 * Results:
 * None


 * Plan:
 * Catch up
 * Concerns:
 * Falling behind

Week Ending March 26th, 2012

 * Task:
 * (Tuesday) Read all the logs for my classmates for the past two weeks to get up to speed on class' progress on the project. I made sure my PC works with Caesar SVN/SSH to be able to read all the information of the machines at home.
 * (Saturday) Read logs
 * (Sunday) Read logs and worked on hardware configuration table
 * (Monday Finalized the Hardware table with the information and uploaded to wiki
 * Results:
 * Completed the Hardware table within the wiki page. Made numerous changes to the table after spend time analyzing the hardware.


 * Plan:
 * 1) Read logs
 * 2) Conduct phase two and three of my project proposal to include SSH information and machine information for all the nodes on Caesar.

Week Ending April 2nd, 2012
-What is the maximum that Caesar can take in memory? -Can we grab memory from the batch to fill that? -What chunks are the memories in and can we normalize such that most batch systems have similar memory and the file server has the most? http://www.dell.com/downloads/global/products/pedge/en/2650_specs.pdf
 * Task:
 * (Friday) Read Logs and emails with professor about amendments to my report. I need to look at the following elements.
 * (Sunday)Read logs and looked at the maximum memory that Caesar will take.
 * (Monday)Read logs and looked at the memory issue with Caesar and the batch files.
 * (Tuesday)Found all the information we could ever want about Caesar.


 * It looks like Caesar has a lot of room to grow with up to 12GB of memory expandability for better functionality in our system. The specs sheet at the pdf file above really provides the best information about our system.


 * I recommend that we expand the memory vice grab memory from the batch files to meet the increased capabilities. An increase in memory would be less cumbersome than slicing up the batch files.


 * Results:
 * Completed tasks


 * Plan:
 * 1) Describe Table Components
 * 2) Add upgrade options to table
 * 3) Read Logs
 * Concerns:
 * None at this time

Week Ending April 9th, 2012

 * Task:
 * (Tuesday) Wrote out my weekly plan. Downloaded sample abstract for poster board
 * (Friday) Worked on Abstract and upload the final version to the wiki page. I also worked in Caesar to run the mini train per Brice's instructions and also the template that the summer 2011 class outlined. We have a Skype meeting at 230pm which we discuss this process in further detail. I've ran into a few snags with the setup so the meeting will be helpful and create some dialog on running the min train properly.
 * (Sunday) Read logs
 * (Monday) Worked in Caesar to run a training per Training with Brice over Skype
 * (Tuesday) Uploaded new abstract to wiki after input from professor


 * Results:
 * Completed the abstract as discussed in class
 * Skype meeting and training with Brice on running the training/speech tool inside caesar
 * Worked on my own to run the speech tools inside Caesar
 * Read logs


 * Plan:
 * 1) Write Abstract for poster(see sample below)
 * 2) Fill out the comments section on my Hardware Info Page
 * 3) Work with Group1 (Brice, Chad, Brennan, Sky, Matt and I) to run Train 5 (DUE 10 April)
 * 4) Work with mini Group4 (Ted, Brennan, and I) on experiment 0004, attempt to run train as envisioned by proposal
 * Concerns:
 * None

"The goal of the Internship Program at the University of New Hampshire at Manchester is to provide students with hands-on work experience that will enhance their degree and help prepare them for successful careers. Tasks of the UNHM internship program involve managing over one hundred internship opportunities. This includes adding, deleting, viewing, generating reports, and assigning internships. Currently the staff needs to interface manually between a Microsoft Access database and the UNH Blackboard site. The Internship2Career team is designing a web application in a model view controller architecture to solve the staff's problems using an open source software approach. This will allow any person or organization to adapt the software to their needs. Internship2Career has setup an online project hosting on the Google Code website, which allows for easy version control and for other users to view the project and potentially contribute. The web application is being designed using the programming languages MySQL to develop the database, HTML to be able to view in a web browser, and PHP for application logic control. Results of the Internship2Career project include a near operational prototype system that will be ready for usability testing; a wiki site that describes how the system was built; and a project hosting site which allows users to continue to contribute to the project. In conclusion, this program will save valuable time and money for the Internship Program, and create a more efficient method for students to research the internship opportunities." (From last years class)
 * Sample Abstract

The goal of the Internship Program at the University of New Hampshire at Manchester is to provide students with hands-on work experience that will enhance their degree and help prepare them for successful careers. Major employers consider a "Capstone" project a key part of gaining knowledge and preparing students for future job positions. The class will use the Sphinx Speech Recognition Toolkit and further the research and development of pervious semesters work. The goal is to execute a "mini train set", however, the team intends to improve upon many other areas including organization of the hardware and software of the system, documentation of work progress, and creating backup mechanisms. In conclusion, the Spring 2012's class should leave future groups in position to pursue the execution of the "full train set" and improve upon the acoustic model. This will improve the accuracy of decoding with Speech software and improve overall speech recognition technology.
 * Speech Poster Abstract

The goal of the Capstone Program at the University of New Hampshire at Manchester is to provide students with hands-on experience that will enhance their degree and help prepare them for successful careers. Employers consider Capstone a key part of a student’s educational background in gaining knowledge and preparing for future job positions. The class will use CMU’s Sphinx Speech Recognition Toolkit and further the research and development of previous semester’s work. The goal is to learn and apply speech recognition technology as well as to improve upon many other areas including organization of hardware and software of the system, documentation of work progress, and creation of backup mechanisms. In conclusion, the 2012 spring semester class should leave future groups in position to pursue further research to improve upon the overall quality of speech recognition with its primary goal of improving the accuracy of the technology.
 * New Abstract

Week Ending April 16th, 2012

 * Task:
 * (Tuesday) Met with Experiment 004 team to discuss our plan of attack. We plan to work independently and meet up on skype on Friday to discuss our progress.
 * (Thursday) I worked with Brice via email about the poster abstract.
 * (Friday) Skype meet never happen - I had some family matters to attend to. Brandon and I exchanged emails and plan to meet over the weekend. We haven't heard from Ted.
 * (Sunday) Brandon and I met on Skype to discuss the experiment progress and process. We both were still finishing up taskers from last week. I plan to copy the files from Caesar down to our assigned machine on Monday and start running though the experiment process. After the Skype meeting I traded emails with some of the team and sent our updated abstract to Ellen at Durham. Updated Hardware Configuration Description.
 * (Monday) Upload file to assigned server from Caesar and run experiment process (planned)


 * Results:
 * Updated Hardware Configuration Paragraph
 * Abstract completed and sent to Ellen at UNH Durham
 * Skype meeting with Brandon to discuss the experiment process
 * Looked at Caesar and the files we need to move onto our machine for the experiment.


 * Plan:
 * 1) Update Hardware section with descriptive paragraph


 * Concerns:

Week Ending April 23rd, 2012
See below from Experiment 004
 * Task:
 * Results:

Experiment number: 0004 Ted copied the necessary files from Caesar to Miraculix using the following steps:
 * (Tuesday) Emailed with team
 * (Wednesday) Skype meeting with team to and discuss Experiment status and needed progress.
 * (Friday) Skype meeting with team
 * (Saturday/Sunday) Following steps in the install guide since we thought everything had already been installed, but realized it was not.
 * (Monday) Cracking down on getting this all to work. Worked with Brandon and Jonny installing Sphinx on Miraculix,,,but!,, the permissions are messed up on that machine so we couldn't move anything around. We spent a while trying to make it work with no luck. We are going to seek help in tomorrows class.

Ted - Moved all the needed files from Caesar to Miraculix Brandon - Found missing file and tried to get one of the scrips to run, edited log for the weekend. Aaron - Wrote the group log and followed progress within Miraculix providing QA input if needed.

No real plan this week, just get in and get to work. Getting the mini train to run.
 * Plan:
 * Concerns:

Week Ending April 30th, 2012

 * Task:
 * (Tuesday) In class we outlined the project report and assigned tasks for the QA checks of all the sections on the information page.
 * (Wednesday) Gave informative presentations and answered questions at the URC (3-330). Completed software setup QA check and made changes were needed.
 * (Friday)Completed a rough draft of the project conclusion and uploaded it to the project wiki. I made a post to the Google group and asked for feedback on my write-up as well as reminded the team to complete their pieces of the report before next class. Additionally, I looked over the QA progress that we had made on the information page and reviewed the teams notes. Lastly, I made a post to the class discussion board about needing to complete the QA checks before Monday to show our teams progress.
 * (Saturday) read over the changes on the report and checked the status of the QA checks. I also looked at the discion board for any comments.
 * (Sunday) read over QA report 6 of 9 have been completed. I hope the stragglers get their part done before tuesday. I read over the draft report and there is still a lot of work that needs to be done - I sent a google group message a few days ago, but no one have replied or made an recommendations to my contribution. I hope everyone chips in and we can seek input from the other group about our report on Tuesday and get this thing DONE!!!


 * Results:
 * Rough Draft of Conclusion completed and waiting for team feedback.
 * Completed QA checks and made improvements to the S/W setup information page.
 * Made two posts to the class discussion forum and I will monitor the board for feedback and any concerns.


 * Plan:
 * Complete my sections of the report and review others contributions. I will also provide any feedback via the message board or wiki.
 * Concerns:
 * None at this time.

Week Ending May 7th, 2012

 * Task:
 * (Tuesday) Led the project team in a discussion about wrapping up the project report. I sought input from Prof Jonas about our progress and any area's we need to improve. We got input from the other team and assigned them with some tasks on the report. Everyone in the class knows what needs to be done and we all need to finish everything ASAP! We included Mike who was absent in class by emailing him some tasks to be completed by next week. I REALLY hope everyone start putting the pedal to the metal and finishing up their part of the report!!
 * (Wednesday) Looked over the report and also QA checks - It's not moving as fast as I'd like to see it, but there is small glimmers of progress. I hope to see more progress over the weekend.
 * (Thursday) Read over QA checks and Report - no progress, which is not good...
 * (Friday) Read over QA checks and Report - wow good progress and it looks like the report is coming together. I hope that the final sections get finished up asap so we can review and make final edits on Tuesday. I made a post to the google group to remind people to finish their sections of work.
 * (Sunday) Reviewed the project report progress and also read over the google groups log.
 * (Monday) Reviewed logs, QA reports, and report.
 * Results:
 * Provided feedback and guidance for the team in finishing the project report.
 * Plan:
 * On the fly
 * Concerns:
 * Finishing the report before this Tuesday

Week Ending May 14th, 2012

 * Task:
 * (Tuesday) Read over the report. I finished up the conclusion with the teams input from the the class meeting. I also added the un edited text from Brice's log to the report. This needs to be edited. I emailed Mike so he can make the final edits to the report. I'm going to be out of town starting Thursday so it anyone needs me please email me at "aarongreencg@yahoo.com"
 * (Thursday) Read over the report and made one last post to the Google Group to try and get everyone to finish up there parts...At this point I have completed my part of the report and can't FORCE everyone to finish their parts, so I have to "cut bait" and move on...This will be my last contribution to the Capstone Class.

It's been a great semester! Thanks Professor Jonas and Team Capstone!!! See you in the real world.

Aaron Green aarongreencg@yahoo.com

Thanks for the great semester guys!!!