Speech:Spring 2013 Michelangelo Bianchi Log


 * Home
 * Semesters
 * Spring 2013
 * Proposal
 * Report

Week Ending February 5th, 2013

 * Task:
 * Research if the new OpenSUSE will work and is worth updating to.
 * Research if Sphinx will work with new OpenSUSE and if that needs to be updated as well.
 * Familiarize self with Unix/Linux commands.


 * Results:

1/29
 * Found out that OpenSUSE is up to version 12.2 and that Sphinx is up to version 4.
 * Got familiarized with the hardware and what system Caesar is running.
 * Practiced basic unix commands listed on class wiki
 * Looked at wiki from Spring '12 to see what version of Sphinx is running on the current OpenSUSE.

2/1
 * Found Hardware specs for OpenSUSE 12.2 and for the server (Caesar) and Client drives.
 * We can possibly update the system as we meet the required specs (the drives have the memory to run it w/o the current OpenSUSE). I'll need to see what Sphinx works on though.
 * Looked for Sphinx system specs. Found in forums that if we were to update and reinstall Sphinx 3, we would need a newer version of the base or pocketsphinx.

2/3
 * Found website for Sphinx-4, which states that we would need to install Java on current system in order to use it. I believe that we wanted to stay with Sphinx 3 as that uses C, which allows us to use write Perl scripts for it. So for now, I say we stay with Sphinx-3.
 * Also found forum topic about Sphinx-4 vs. Sphinx 3 that says that Sphinx-3 has an easier time recognizing phonemes.
 * Sphinx's official site also states that 4 is best with bigger servers and cloud computing as well.
 * Sphinx 4 documentation shows that error rate of bigger words with Sphinx 4 doesn't differ much from Sphinx-3. I further believe that we should stay with Sphinx 3, especially since the Sphinx creators say that is the more accurate one for the work we want to do.
 * Side note: If anyone reading this needs help with Sphinx, this forum may help you: http://sourceforge.net/p/cmusphinx/discussion/
 * Researched whether Sphinx 3.7 (the current version we are using) would work on OpenSUSE 12.2. Found documentation by one of the developers on Google (http://svn.code.sf.net/p/cmusphinx/code/trunk/sphinx3/ReleaseNotes) that states that it works on any Linux system that uses an x86-64 instruction set/processor, which according to OpenSUSE is used on our processor (Intel Xeon).
 * Further research (http://turing.suse.de/~coolo/opensuse_12.3/) into OpenSUSE states that 12.3 will be released in a month, which may make update to 12.2 pointless. I'll make a note to discuss this with the class and my team on Wednesday.

2/4
 * Read logs

2/5
 * Read logs
 * Plan:Currently the plan is to report back on the date of this log (Feb. 5) on what I have found in the past week for whether we should upgrade or not.
 * Concerns:

Week Ending February 12, 2013

 * Task:
 * Continue research on OpenSUSE and whether it would be worth to just update to a new"er" (read:12.0) system
 * Practice unix commands that Brian listed on his log

2/6
 * Results:
 * Looked up differences between OpenSUSE 11.3 and newer versions.
 * Found that OpenSUSE 11.3 runs on a i586 Linux processor, if I remember correctly from my research last week 12.2 uses x86. There's the first change but is it better?
 * OpenSUSE 11.3 also uses Linux 2.6.3.4 kernel while 12.2 uses Linux 3.4 kernel. I'll keep in mind to research the difference between Linux 2 and 3 in the coming days.
 * Found Linus Torvald's blog post about Linux 3 stating that there are no big changes b/w 2 and 3. (http://permalink.gmane.org/gmane.linux.kernel/1147415)
 * What do we care about is the question (Do we care about just the core and security? or should we consider other things like speed, filesys and graphics?).

2/8
 * Added OS Updates proposal that I typed up on Thursday, February 7th to Proposal wiki.
 * Read over Brian's Memory session log
 * Researched difference between Linux 2.6 and 3.4 (what OpenSUSE 12.2 uses).
 * 3.4 utilizes an x86 processor that has more available than the one we have (http://kernelnewbies.org/Linux_3.4).
 * Drivers have also been updated as well as fixed bugs in the filesystem.
 * This may be helpful to refer to as well when making update decision: http://kernelnewbies.org/Linux_3.4_DriverArch
 * It looks there is a sizable difference between 2.6 and 3,4 as 3.4 has more than minor changes according to the research on both kernelnewbies and here: http://www.h-online.com/open/features/Linux-Kernel-3-4-Tracking-1563971.html
 * OpenSUSE offers backup service, I'll make a note to notify Brian on this (he's researching backups).
 * OpenSUSE 12.2 offers better memory management than 11.3 or 11.4.
 * On that note, 11.4 offers more security and uses a newer kernel that has better memory mgmt for large tasks should we decide to just update to a newer system.
 * OpenSUSE also has a new, faster startup program (starting with 12.1).

2/9
 * Read logs
 * Practiced the commands Brian listed in his log.
 * Note to self, top command runs indefinitely, press q to get back to command prompt.
 * Netstat on network shows that LDAP networks are in time_wait state. Interesting.
 * exit gets you out of nslookup.
 * Responded to Brian about an email I sent him yesterday about possible backup option for system that I found on OpenSUSE's website.
 * Tyler seems have found another option (Clonezilla) that may work better though.
 * Clonezilla needs a x86 processor (which we don't have), maybe virtualization through the system will work?

2/10
 * Read logs

Have a better idea of whether we should consider updating or not next week.
 * Plan:
 * Concerns:

Week Ending February 19, 2013

 * Task:
 * Over next two weeks, make document to convince team to upgrade OS.
 * Look up system specs for newer systems.

2/13:
 * Results:
 * Worked with team to restore Caesar drive.
 * Verifying the drive using disk utility somehow removed the error from the machine display.
 * Restarted server and got to OpenSUSE login screen, after choosing the normal startup it crashed. Eric from the Modeling team is in the process of downloading a new system to test.
 * Luckily, only the OS is having problems. It would seem like the filesystem that the documents for the project is on is OK.
 * Feb. 14 update: Forgot to add yesterday that I suggested they try to load OpenSUSE 12.2 after Eric asked which system I was thinking of upgrading Caesar too (due to the fact a new OS needed to be installed).

2/14:

<3


 * Received email from Tyler last night that the newest OpenSUSE (12.2) that was installed on the Caesar drive (due to the fact that the old OS somehow got corrupted after the drive fail) actually did not work as some programs plus other items didn't and it ran slower. He also noted that everything ran better with 11.3 (which was what we had and what the project manager likes as well). It would also seem that the idea of upgrading to a newer OS has been trashed for the time being because of this issue.
 * Seeing as that seems to not be happening, I will help the team with whatever else needs to be researched while reading up on Clonezilla and OpenSUSE 11.3.
 * Read up on basics of Clonezilla and how to install it onto a USB drive (which I believe is how we plan to backup the system) (http://clonezilla.org/liveusb.php).
 * Read Tyler's log to see what else happened after I left class yesterday.

2/15:
 * Read the other logs
 * Received an "OK" response from Project Mgr and Tyler for idea about making temp filesys on Marathon while trying out new systems on swappable drives for Caesar.

2/17:
 * Read logs
 * Research and make list of differences between alternative Linux OSs. This will help my team and I decide on which system to try when we decide to install a new system on the other drives.
 * Found that Fedora is up to version 18, uses a more recent Linux kernel than the new OpenSUSE does and may also be more secure (http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html)
 * We may need more memory on the drives if we want to install Fedora 18 though (it needs 768MB RAM)
 * It also looks like Fedora supports RAID backups as well.(http://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/sn-partitioning-raid-x86.html)
 * Sounds like it runs on x86 (we have i586, may need to update).
 * (http://www.linuxquestions.org/questions/linux-newbie-8/what-does-i386-i586-and-x86-64-mean-254872/) This says that i586 is an x86 processor. Good to know.
 * Found that Ubuntu is up to version 12.10 and claims that is also very secure and easy to install. However, it comes in two versions (Desktop and Server). Need to make note to discuss with team (and Matt) which we should try.
 * Here's what I found about the requirements an Ubuntu server: https://help.ubuntu.com/12.10/serverguide/preparing-to-install.html


 * Plan:


 * Concerns:

Week Ending February 26, 2013

 * Task:
 * Continue researching alternative systems
 * Edit proposal to reflect changes
 * Document how alternative systems work (what programs they use etc.)


 * Results:

2/20:
 * Helped Mike T. with finding extra memory in the unused drives that were in the System room.
 * Read any log updates made since Monday.

2/21:
 * Updated proposal wiki with the new plan for OS Updates. Also contacted my team members to see if we are in agreement of updating the system or not so that I can either write a proposal for OS Updates for next week as well (seeing as we stated on the proposal wiki that we'd decide on this by next week) or postpone the decision by a week (so that we can test the new systems next week).

2/22:
 * Talked with Tyler yesterday about updating the system for Caesar, he says that we should push back the date on the wiki by week so that we can test Fedora on the swappable drives for Caesar after backing up the info on the current drives.
 * We agreed on testing Fedora first as UNHM has a membership and special deal with Fedora's creators RedHat.
 * Received email from group saying that they were planning to back up Caesar after the next status meeting on Wednesday, responded to email saying that depending on how long the backup takes I would like to try to test an update of Fedora during that time too.
 * Will plan to draft a proposal for an update in the coming days as well.

2/24:
 * Drafted Proposal for OS Update
 * Did not need to research alternate systems as we agreed to test Fedora on Caesar using hot-swappable drives.
 * 1st draft of proposal is up on Systems group wiki. Team has been notified of this.
 * Methodology of how this will be done will be added before midnight Tues.
 * Read logs
 * Noticed that Joseph Gallagher was having issues on installing Sphinx on Fedora 17. Should talk to him next week about whether that was a VM issue or if it doesn't work on Fedora (as the documentation states that it should work on any version of Linux).

2/25:
 * Added the Methodology to the first draft of my proposal. It is based on the installation guide that can found here: http://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/ch-guimode-x86.html
 * Received feedback from Brian on other parts of the proposal, he suggested that I add a spreadsheet into my 2nd draft comparing the different Linux OSs. Will do for next week.


 * Plan:


 * Concerns:

Week Ending March 5, 2013

 * Task:
 * Fix up proposal for Project Manager


 * Results:

2/27:
 * Since class was cancelled due to the 3rd round of winter weather, I used what have been the status report time to utilize Brian's suggestion and create a brief spreadsheet on the differences between the 3 selected Linux OSs. This spreadsheet has been added to the Systems group wiki under the "Additional Info" category in my proposal. The team will be notified of this via email after I write this log entry.

3/1:
 * Read System Team logs
 * Noticed that Tyler is not having good luck with getting Fedora 18 to install correctly on a virtual machine.
 * Would suggest Fedora 17 but Joseph was having issues getting Sphinx to work on a virtualized version of that as well.
 * Read Ubuntu's install guide in case we decide to try that system next. However with the luck we've been having, I might suggest to just stay with OpenSUSE 11.3 as that seems to be the only OS that is working perfectly.
 * Should also ask team if we would install the desktop or server version of Ubuntu should we pick that.
 * Updated Ubuntu's "Security Features" on my OS Updates Proposal spreadsheet.
 * Found a guide on how to virtualize Fedora 18: http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Getting_Started_Guide/index.html
 * Conducted further research on maybe just upgrading to either OpenSUSE 11.4 or 12.1
 * Learned that AppArmor (OpenSUSE's main security feature) works BETTER on 11.4.
 * Emailed team asking about their thoughts of whether we should update to Ubuntu or just stick with OpenSUSE 11.3.

3/2:
 * Read the other logs
 * Noticed that the other teams are using Perl to write scripts to make the process of training and decoding faster, I'll make a note to myself to add the updates to Perl to my update proposal.
 * Received response from Tyler that Fedora does work on his home machine but he can't test the LDAP/Active Directory capabilities as he can't VPN into Caesar.
 * This gives me hope that maybe Fedora 18 will be worthwhile to test on Caesar during the next class period.
 * I also responded that this is good news and sent him a page from the release notes that discusses how LDAP is used in Fedora 18.

3/3:
 * Updated proposal to correct spelling and grammatical errors and add which version of Perl each Linux OS is using. (http://fedoraproject.org/wiki/Features/perl5.16), (http://askubuntu.com/questions/80672/what-perl-version-will-be-in-12-04-lts)
 * E-mailed team about update.

3/4:
 * Read logs
 * Nick Regan asked for SpEAK testers and feedback, so I left feedback on the Experiment group wiki page stating that I could not log in for some reason.
 * Created a more official proposal on GoogleDocs by moving the wiki draft onto a new document and fixing up more errors that I didn't notice when it was on the Systems group wiki. Team will notified of this via e-mail.
 * Finalized Proposal and sent it to the project manager.


 * Plan:


 * Concerns:
 * With class being cancelled, I will need to see if the team has any plans for the coming week via email. Thank goodness for the logs!

Week Ending March 12, 2013

 * Task:

-Read about running a train

3/6:
 * Results:
 * Tested Fedora 18 on Caesar using swappable drives. Test had a rocky start as the resolution was horrible and the on-screen text was unreadable. Luckily, these issues were fixed after we updated the drivers. It is currently running better and is able to be accessed from outside the server room.
 * Learned a bit about Clonezilla from a tutorial that Tyler gave us during the update process.
 * Updated Proposal on Systems group wiki.

3/11:
 * Read System Team logs


 * Plan:


 * Concerns:

Week Ending March 26, 2013
- Read wiki on how to run a train.
 * Task:


 * Results:

3/20:
 * Discussed plan for next week with Drew.
 * Set up time to learn how to do a train next week (either Wednesday or Thursday).
 * Asked if I needed to install anything on my machine for train, the answer was no as everything I need should be on Miraculix.

3/22:
 * Moved Wednesday's log from last week to this week (oops).
 * Added task for this week.
 * Read logs
 * Read that Justin and Jake are trying make the wiki on trains easier to follow. Good to know!
 * Scott says he's having trouble getting a virtual machine to work. I don't know why he needs a virtual machine when Drew says that everything you need to run a train is on the machine you are logging into.

3/23:
 * Read the wiki on how to run a train
 * Note to self: ask Drew what "Insert SIL in the appropriate alphabetic-ordered spot" means.
 * emailed question to Drew.
 * Read the quick reference on the VI Editor
 * Happy to know I remember most of the commands from Network Fundamentals class.
 * Read the wikipedia page on the Arpabet
 * I seem to understand that better than how to run a train at this point in time.
 * Read the script for updatedict.pl that was uploaded to the wiki.
 * Read the updated version of the "Create a language model" wiki and the current revision of the decode wiki.

3/24
 * Read logs
 * Received response from Drew about SIL, I understand it better now.


 * Plan:


 * Concerns:

Week Ending April 2, 2013

 * Task:
 * Run a Train and decode it.

3/27:
 * Results:
 * Learned how to run a train.
 * Also learned how to set up a dictionary (task and word) as well as a phone list.
 * Added feats data as well.
 * Will run a train at 4PM or later tonight.
 * Train at 4PM failed within a min. Drew sent us an email to try an eval instead of a train as that might go faster and will be more successful since none of us were able to successfully run a train today. Will try an eval later tonight.

3/28:

From 3/27 between 9-11PM For today: 3/29:
 * Tried to run an eval last night and it failed, even after I added all of the missing words.
 * Emailed Drew about this issue, he's stuck on the same problem too.
 * Bumped into Eric while observing the new emerging technology center, he helped to me understand how to fix the error that was keeping me from running a successful train (which was adding a missing phone by adding the lexical spelling of a word into the dictionary). Eric also answered my question on how to fix the "duplication" issue in the dictionary (vi Exp#.dict, delete duplcates).
 * Was able to run a successful train during meeting with Drew, Jake, and Justin.
 * Built language model, will decode later.
 * Added my task for the week
 * Started decoding process.
 * Emailed Jake and Drew to see if anything is supposed to happen during the decode process, because nothing is happening at the moment.
 * Set up Experiment page w/ the words I added to the dictionary.
 * Updated page with results up until 11:11pm
 * Read logs and edited a grammatical mistake I made on yesterday's log.
 * Reading Scott's log reminds that I should note what Exp# I have 0052
 * Should maybe also be more descriptive on Train and decode statuses next week too.
 * Emailed Eric about Decoding as well.
 * Decode was successful! YAY!
 * At least I think it was because it ended after 30 or so mins (start 10:11PM End: 10:50-ish).
 * Email all of the aforementioned classmates about successful decode [I really need to read these wikis more closely].
 * will finish off learning exercise tomorrow (3/30) with Scoring

3/30: -methusalix 0052/etc> uniq hyp.trans >> hyp.trans.uniq -methusalix 0052/etc> sclite -r 0052_train.trans -h hyp.trans.uniq -i swb >> scoring.log -methusalix 0052/etc> I did not see any chart or info.
 * Scored the eval and met with the same errors that were discussed in the guide.
 * Nothing happened at the end. I entered exactly what was in the guide :
 * Emailed Eric and Drew about whether it's been written to "scoring.log" or whether it failed again, although I assume that it would tell me if I was missing something again.
 * got a quick response from Drew saying that the chart is in "scoring.log", meaning that the scoring was a success! YAY!
 * Posted results in Experiment log 0052 (listed in yesterday's log).
 * Edited Scoring to fix an error in the coding (trains.trans doesn't exist, train.trans does).


 * Plan:


 * Concerns:

Week Ending April 9, 2013

 * Task:


 * Results:

4/3:
 * Helped Jake and Justin set up new corpus that we can run a 5hr train with.
 * We are following Cedric's instructions on how to set up a corpus and seem to stuck on the CopySPH.pl step as Verleihnix cannot find the file that we have edited (train_unedited.trans) for the purpose of running a train. The system keeps saying the file we want doesn't exist.
 * Somehow the file we have been editing has become Read-Only, we are looking at the new Corpus guide in order to find out how to fix this.
 * At 2:30PM after unsuccessfully trying to fix the CopySPH.pl problem, we have decided to start the process over and try again.
 * I have attempted to see if this will work on Methusalix, It did not as I received the same error that Jake and Justin received on Verleihnix.
 * Added this log entry into the Group D's log as well.
 * Found out that Group A has created the corpus for us.
 * Watched Mat create corpus and work through issue of making an organized list of SPH files.

4/4:
 * Read Logs. Apparently according to Tyler's log, Mat was able to find a way to set up a 5hr corpus that the rest of us can try to set up and run at some point. That's good to know.

4/6:
 * Read logs and emailed the Group D leader (Drew) to see if any more progress has been made on creating and running a 5hr. corpus and if there's anything I should do.
 * Eric seems to have figured out how to get a corpus set up as well based on what Mat did.
 * All other logs are blank or only discuss how they've successfully learned how to run a train, decode and score.
 * Also agree with Sam on how everyone who has learned to run a train is "reading logs" at this point is not a good sign.
 * Also Emailed Mike T on the information for the URC poster because he wasn't sure what to do for it on Wednesday.

4/7:
 * Emailed Drew again on updates as he hasn't responded to the last email I sent him yesterday
 * Emailed other team members to see if they've heard anything about the status of the 5hr. Train Corpus
 * Sent email to Systems group about URC Poster, since I forgot to yesterday.


 * Plan:

4/6: It didn't seem like anyone knew what they were doing on Wednesday and it still doesn't seem like many people know what's happening or what to do since then besides Tyler (who worked with Mat on setting up the corpus in class), Eric and Mat (who set up the corpus for team AD).
 * Concerns:

4/7: With no response from Group leader, I'm not sure what I can do for this week's portion of the project. Normally, I'd take initiative and find something but with one person doing the corpus and no words to find or trains to run. I'm not sure what to do at this point.

Week Ending April 16, 2013

 * Task:

4/11:
 * Results:
 * Read Logs
 * Found out that Tyler successfully ran a train and decode of the 5hr train. May consider trying this myself over the weekend using the dictionary he completed.
 * Discussed with Charles about what to do since Tyler completed the train we were going to work on.
 * Will be meeting with Mike T via Hangout to plan out and create poster tomorrow, also sent him my contact info.

4/12:
 * Mike T and I met over Google Hangout and discussed how to organize the poster as well what parts Mike and I would tackle ourselves.
 * will create my half of poster today and possibly finish it off tomorrow.
 * will also contact him about meeting via Hangout on Sunday for a follow up meeting.
 * Emailed Brian and Tyler on proceedings from Hangout session.
 * Emailed team to see if we should run a train using the same data that Tyler used in his train.

4/13:
 * Finished my part of the URC poster today. Will also make edits to the paragraph on OS Upgrades and then email the systems group members about the update.
 * Received email back from Charles about running the 5hr. train that Tyler ran. He's not sure what to do either.
 * No response from the other 8 group members yet (not including Tyler, who's at a coding contest in NY till Sunday night) as well.

4/14:
 * Read logs
 * It looks like Eric and his group have taken the next logical step and improved the error rate of the train.
 * It would also seem that Group AD may be doing that in a hangout at some point as well.
 * Brian states in his log that he's gathering information for the Systems group URC poster. Good to know seeing as I've emailed him our plan on Friday.
 * Received email from Tommy that he wants to organize a Hangout to run the 5hr train in as well.
 * see entry under Read logs for additional note
 * Emailed Mike T on if he wanted to do a Followup Hangout today on the poster seeing as Tyler and Brian may not be available.
 * Mike T doesn't think we need one, so we had a quick follow up on Google Chat instead.


 * Plan:

4/13: Group AD doesn't seem to know what to do again since Tyler ran EXP 0078 (the one Charles suggested we debug this weekend). My fear of backpedaling in the project is also what's preventing me from running the train again as well.
 * Concerns:

4/14: Group AD is taking the next step in running the 5hr train, which is great but I'm not sure if I can attend the Hangout if it is scheduled for tomorrow (unless it's scheduled earlier) or Tuesday because I have to be at an Internship tomorrow and early Tuesday morning (and at a job on Tuesday night). I suppose if I'm not available I can ask what to do in lieu of this issue.

Week Ending April 23, 2013

 * Task:


 * Results:

4/17:
 * Worked on Poster with Systems group.

4/18:
 * Read logs

4/19:
 * Finished poster on 4/17 and wrote up abstract for poster as well. Have sent email about this to the systems group in case they want to look at it before sending it in as THE abstract for the poster.
 * Received email from Charles stating that people in Group AD stil are not sure what to do next with the 5hr train.

4/21:
 * Read logs
 * No one has done anything besides work on the poster (or nobody is filling out their logs with any accomplished activities).
 * Would like to note that I read logs on 4/18 at 11:50pm, despite the wiki stating that my log was updated twice on 4/19.
 * Sent in abstract to Ellen Ruggles after receiving no additional suggestions or feedback from Systems group.
 * Sent off another email to Group AD about what we should do next for the 5hr train.
 * Recieved email from Tyler about finding word pronunciations for the next 5hr train.
 * Added a few words to his Google Drive Doc.

4/22:
 * Emailed team with suggestions on how to find pronunciations on CMU site.
 * Read logs.


 * Plan:


 * Concerns:

Week Ending April 30, 2013

 * Task:
 * Work on final report


 * Results:

4/24
 * Read logs to see if I missed anything on Tuesday. Doesn't look like I did.
 * Received email from Tyler about the results of the trains and scores that he ran, apparently they were worse than the last attempts with the results coming in at 47%.
 * Discussed plan for what to write on the final report and who writes what.
 * I'm covering the hardware and System update sections of the final report.

4/25:
 * Added a rough draft of my OS Upgrades report to the final report Google Docs. Will also email team about this as well.

4/26:
 * Updated task since group AD is officially working on the final report.
 * Read logs
 * Mike M. and Marc are the only ones who have made any entries since class on Wednesday.
 * I find this surprising seeing as Wednesday's class was spent divvying up the tasks for both training and the final report.
 * Received email from Tyler saying that rough draft of final report is due next Wednesday. Good thing I plan to do a write up on Hardware tomorrow.
 * Also updated Mike T. on what's been happening in class via Google chat [he was apparently out sick this week].

4/27:
 * Wrote the rough draft for the Hardware final report.
 * Also edited my draft of the OS Upgrades as well and added a suggestion to future project classes as well.
 * Emailed team about updates.
 * Plan:


 * Concerns:

Week Ending May 7, 2013

 * Task:

5/1:
 * Results:
 * fixed up my portion of the final report based on feedback that Scott left for me on the Google Doc.

5/2:
 * Left feedback comments on final report Google Doc.

5/3:
 * On Friday night at 11:30 PM, I read logs.
 * Not much really new at this point, A lot of my teammates seem to have written their sections of the report on 4/30.
 * I haven't seen any movement with Group BC's train though.

5/5 (Cinco De Mayo):
 * Left feedback on Google Doc version of Final Report for my teammates.
 * A majority of it was mostly about grammatical fixes and improvement suggestions.
 * The content of the report looked very detailed, The only suggestion I had was to maybe expand the intro section a bit.
 * Fixed up my hardware improvements section and added it to the wiki.
 * Added my name to the OS Updates section of the wiki.
 * Notified team of comments on Google Docs via email.
 * Read logs for updates since Friday
 * Not much seems to have happened, I've seen very little updates about the 5hr train.

5/6 (Final log post!)
 * Read logs
 * Good to see that there are more updates on both the final paper and 5 hr. Train.


 * Plan:


 * Concerns: