Speech:Spring 2013 Sam Workman Log


 * Home
 * Semesters
 * Spring 2013
 * Proposal
 * Report

Week Ending February 5th, 2013
-Form communication with Matt and Kevin.
 * Task:
 * 1/31/13

-Find missing transcripts
 * 2/2/13

-Read the wiki and see what it's about.
 * 2/3/13

-Read wiki information.
 * 2/4/13

-Exchanged e-mails and phones.
 * Results:
 * 1/31/13


 * Plan:

-Not really sure what our task is about.
 * Concerns:
 * 1/31/13

Week Ending February 12, 2013

 * Task:


 * Results:


 * Plan:


 * Concerns:

Week Ending February 19, 2013
-Download all the CDs that worked on my flash drive to be scanned for the audio informaion
 * Task:
 * 2/13/13

-Read other users logs to see what people are doing.
 * 2/14/13

-I've got nearly a full flash drive of audio files now.
 * Results:
 * 2/13/13


 * Plan:

-two CDs weren't loading all of the files, and there is no way to know whats missing yet.
 * Concerns:
 * 2/13/13

Week Ending February 26, 2013
-Read logs.
 * Task:
 * 2/22/13

-Found way more hours of audio than Mike expected us to. More than 250 hours actually.
 * Results:
 * 2/20/13

-Read logs. (read vs read)
 * 2/22/13


 * Plan:

-Not sure how mikes million dollar CDs would have more audio than he knew about. So maybe the ceasar transcripts have a lot of white space that isn't removed in Matt's script.
 * Concerns:
 * 2/20/13

Week Ending March 5, 2013

 * Task:


 * Results:


 * Plan:


 * Concerns:

Week Ending March 12, 2013

 * Task: Inform the new members of what we're doing to find all the transcripts.


 * Results: I missed last week, and this week was spring break.


 * Plan: Try to catch up on reports for the project. Talk with matt and kevin about new group combination.


 * Concerns: I'm two weeks behind now.

Week Ending March 26, 2013

 * Task:
 * Regroup with new data team.
 * Get in contact with Matthew to see if he has the data in a readable text file. If not we should.
 * Update previous logs

New data team is pretty lost as well. We'll work under the assumption that there isn't a readable text file made yet and write one up in class.
 * Results:
 * 3/20/13


 * 3/22/13

Meet with group C to explain tasks relating to trains and go over questions. Read all the logs for my group and extended group mates. Run first 5 minute train. Gain access to the program.
 * Plan:
 * 3/22/13
 * 3/26/13
 * 3/27/13


 * Concerns:

Week Ending April 2, 2013
Follow directions on the making a trains page to create dir and set up sphinx etc...
 * Task:
 * 4/2/13


 * Results:

Read more logs
 * Plan:
 * 3/31/13

Read logs. I may have forgotten how to use linux. Mostly because I'm more comfortable with emacs than vi, but who knows.
 * 4/1/13
 * Concerns:

Week Ending April 9, 2013
Ran mini train and being work on decoding. Read those logs. Satisfying my log reading desire. Was supposed to sign up for 5 hour train experiment, but see 4/9 concerns.
 * Task:
 * 4/3/13
 * 4/4/13
 * "4/8/13"

Train ran successfully, but see concerns.
 * Results:
 * 4/3/13


 * Plan:

Not sure what output I should have gotten. It wrote out no errors so that means it worked in Linux I assume. Rapidly running out of logs to read. Also all the "read logs" logs is meta. My email puts the group C stuff in junk so I missed the 5 hour experiment sign up. The train still executed though.
 * Concerns:
 * 4/3/13
 * 4/4/13
 * 4/9/13

Week Ending April 16, 2013
-Begin meeting with the group to see what can be done about getting everyone working on he same 5 hour train.
 * Task:
 * 4/13/13

-Fix the transcripts to greatly reduce errors. -Availability is the problem for everyone but I'll move ahead anyway by Monday with a new train. -Watch the putty session and provide input -Create the group poster for data group with the proposal group helping.
 * 4/14/13
 * 4/16/13
 * 4/17/13

-I'm in AD successfully now and reading the progress so far. -Group meeting planned for during the week. -Finished the poster and emailed the final product to the other group members to see if they had any input or changes that they would like to make. I plan on changing it according to their specifications, but unlikely because it is perfect.
 * Results:
 * 4/13/13
 * 4/14/13
 * 4/17/13


 * Plan:


 * Concerns:

Week Ending April 23, 2013
-Submit the abstract for the poster to Ellen Ruggles.
 * Task:
 * 4/19/13

-Read Logs
 * 4/20/13

-Review poster ideas, no one has had any complaints and the poster got forwarded to the entire class. So I guess it was pretty good in it's beta version. I changed it anyway because I thought it made more sense without the bananas.
 * 4/23/13

-Sent the poster off to staples and they had it ready in about an hour. Picking it up Thursday afternoon and dropping it off with Mike.
 * 4/24/13

-The group has the proposal in hand and it should be in her inbox today. I sent her another copy just to be sure.
 * Results:
 * 4/19/13

-Poster is finalized, we missed the submission date however.
 * 4/23/13

-Got poster, cost like 60 dollars, but I covered the cost because it was our fault anyway for missing the deadline.
 * 4/24/13


 * Plan:

-Might fail the poster if we don't HAVE a poster.
 * Concerns:
 * 4/24/13

Week Ending April 30, 2013

 * Task:


 * Results:


 * Plan:


 * Concerns:

Week Ending May 7, 2013

 * Task:
 * 5/2: Read Logs.


 * 5/4: Read logs.


 * 5/5: Read logs.


 * 5/8: Read logs of everyone in prep for pier evaluations. Try to remember names. Also do some post updates on my own logs for weeks missing and back-fill with information.


 * Results:
 * 5/8: Have at least 7 or 8 names memorized and related to work I know they did.


 * Plan:


 * Concerns:
 * 5/8: Doing most of the missing weeks is difficult when the missing ones are all the really old ones. Not sure if we did that much the first to second week of class.