Speech:Spring 2018 Faruk Durakovic Log


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

Week Ending February 5th, 2013

 * Task:

1/30 - Logged In

1/31 - Read Logs and Read Decoder Script

2/1 - Log in to Caesar and look for the decoder, it's scripts, and other relevant files that can help me better understand what I'm doing in the decoder. Will also try to search for the decoder's source code, because the sooner we can get our hands into the code and see how it runs, while also splitting the code segments between people, the faster we can all pool our resources and understand what the decoder is doing and how to make changes/improvements to it as the projects goes on. 2/3 - Now that I have a better understanding of what our team is looking for, my task is to comb through all the files and search for anything that has a "main" in it, while also keeping an eye out for anything that might look relevant and useful for us to understand or that might be of use to use later on. I'm going to take some time right now and later after work to go through all these files in these sub-directories.


 * Results:

1/30 - Logged In and Read Logs

1/31 - Familiarized myself with the paths to the decoder. Looked at all the files in Caesar to know what we have access to and to see if it is useful to the team.

2/1 - Looked into the Caesar server and looked into each one of it's sub-directories. Took some time to view what each directory held inside of it and only stopped when I couldn't dive any deeper into the files. I found the training scripts and multi-hour lengths of the audio snippets that are to be trained, or at least I think that's what I found. I also found several text files and perl scripts in the the sub-directories.

2/3 - As I looked through the files on Caesar, I took the time to chat with my teammates in our private discord server (which is a really easy and convenient as it's both a chat server and a voice chat server) and saw that one of my teammates had posted where the bulk of the "main" Sphinx3 files were located. At the time of this being written, I still do not have the command that allows me to open the source code in my terminal and I have been looking for it online and from my teammates, but have yet to find the answer. Hopefully by tomorrow they will get back to me so that I can progress further into Sphinx3.


 * Plan:

1/30 - Read More Logs and Learn What I need to Know for optimal Capstone Research

1/31 - Log in tomorrow to be able to dive into the Caesar server and locate and understand how everything is linked together. I will also try to find where the decoder is located and other relevant files/scripts and try to understand (or at least try to understand) what they are used for.

2/1 - I want to find where the decoder code is, because I still haven't found it, or rather I haven't figured out what it is where I'm looking, and want to open it up so I can get a glimpse into it's code. From what my other partners have found out, the decoder is written in C+, so it will be a familiar programming language to get into. I plan on getting back on tomorrow and combing through what files might be most important in the sphinx3 and other sub-directories and write them down and where they are so that when we meet up for our next meeting this Tuesday, we can all share what we have found and learned and then divi up the work and get down to cracking the decoder!

2/3 - Look through log files when I get the commands to open their source code. From there, jotting down anything that seems like it would be beneficial to the team. Hopefully I will be able to find something in the code that can help us better grasp Sphinx3's decoding process and maybe might give us an idea on how we can upgrade it.
 * Concerns:

1/30 - Complexity of the system and how difficult it might be to learn the software.

1/31 - Concerns are that I am not going to have the greatest time slots in order to do my fair share of the research for the first few weeks. I don't want to let my team down as I know they are all trying their best to understand Sphinx3 and how it works.

2/1 - My only real concerns right now are to A.) making time to be able to contribute decently into this project so that I'm not dragging my team behind, and B.) trying to get an idea of what I need to be doing for the group. As it stands, aside from the looking through the files on the Caesar server, I'm not very well versed in unix shell commands and might need a bit of a helpful nudge when I get stuck and don't know how to proceed. What I mean by this is if there is a command to view a txt file, then I would like to be able to ask someone for what that command is so that I may start using to know what some README and other such files contain.

2/3 - Because I still don't have the commands that allow me to access the source code, I feel like I am lagging behind where my team might be. If can get those commands by tomorrow or Monday at the latest, then I feel like I will be able to actually start learning what is inside the Sphinx3 Decoder instead of being forced to stop once I've reached as far as the file will let me.

Week Ending February 12, 2013
2/6 - Running my first train today. We all went to a prior years wiki page and found the codes we need to run in order to run a train. We are all now currently running our trains and waiting to see what happens after they finish. Hopefully, as professor Jonas has said before, they don't crash!
 * Task:

2/9 - Log on to read logs.

2/10 - My team will be meeting up tomorrow on the 11th for group session to discuss our proposal first draft. Unfortunately I will not be able to attend this meeting due to work conflicts, but to make up for it, I will try to include some important files that I believe have some importance to the decoder and the project. I will look for files that will be able to help us understand the decoder and the other files it uses and how to connect together.

2/11 - As of today, my team has supposedly met at their derived time and have stitched a rough draft of our proposal for our group. When we meet up in class on the 13th, we will go over it more and talk about or stances on what else we should add or change to the proposal. I need to start allocating more time to research as I fear I am falling behind a bit, but that might also be due to my current sickness that has been making me more sluggish and complacent. Regardless, after our next class meeting, I will take it upon myself to provide at least 1 important idea to our groups conversation as well as look for guides and other online media that can help us understand the sphinx decoder. That will be my mission.


 * Results:

2/6 - Train Pending, Will update when complete.

2/9 - Read Logs.

2/10 - I have been looking through some of the files and none are really catching my eye that haven't already been suggested by my teammates. I will keep looking into the other files to figure out if there are any files that will be relevant. I know there has to be something here that's going to be useful to us.

2/11 - Along with our teams draft proposal being completed, every other groups proposal has been added to the foss.unh.edu wiki page and it outlines the general idea of what each group is going to be doing for the most part. We can all thank Camden for that!


 * Plan:

2/6 - Run a train and see what it does exactly.

2/9 - Read Logs.

2/10 - As I look through the files for my input into tomorrows meeting that I won't be able to attend, I want to touch back on the code train that I ran earlier in the week. So far, I'm not completely sure what it had accomplished at all. I wasn't able to stay connected to the server for the full duration of the train, and I'm not entirely sure if my train was completed or not. Before I left class that day, as I was packing up for my next class, I noticed something along the lines of my train either stopping or my computer telling my that I left the Asterix server. I might redo a train, though a 5 hour one in this case because I want to see what the output will be and what I can use from it. I'll also get in touch with my team and review what they got after their trains concluded and see if I'm on the right track.

2/11 - With the draft proposal "finished", we can now set our sites onto making a detailed mapping of how the decoder works and what other files + code it is connected with so that we can better visually understand it's procedure. I will try my best to be the one to be able to discern which routes each file takes and where the origin code for each script starts and ends. This is going to be a long and drawn out process, but I believe that my team and I are more than ready for the task.


 * Concerns:

2/6 - Running trains takes a long time to complete. I have to make sure to use either shorter trains for quicker response times when trying to test things.

2/9 - None at the moment.

2/10 - Work and other classes are going to start getting more intense. Projects and Tests will be given out soon enough and I want to be prepared for them while also making a good effort on the Capstone. As things are right now, I believe that we are collectively going smoothly, or at least until until the first big hurdle hits us. As it stands, I'm not as much concerned for anything more than I am interested in how all this code works together. More details to come in future logs.

2/11 - I'm a little bit lost on the decoding as I'm still not sure what I'm supposed to do with the output that the previous weeks code trains did. When we meet up in group this following Tuesday, I am going to need to ask my team what they were doing with the outputs and try to figure out what I should do with them after the fact. The days are going to get more complex as they go by. Let's hope we can make a breakthrough in our research!

Week Ending February 19, 2013

 * Task:

2/13 - Today I will Run the full 5 hour train, Decode the train, and finally view the scoring output by the decoder. I have already completed the train, so the decoding is all that is left, which should be quick.

2/15 - Today my team and I are going to be having a voice chat session at around 9:30 PM to discuss our current proposal and go over exactly what we are going to be doing and how we are going to be doing it. We are also going to try and locate the main_decode.c file and map it out or at least get a basis of understanding for it for this week.

2/16 - Read logs.

2/18 - My team will be meeting up again today to discuss to following week as well as to complete the final portions of our proposal that will be submitted to Professor Jonas. I also would like to try to actually start tackling some code reviews this Tuesday with professor Jonas as that is what he is going to have scheduled for us. I hope that I will be sufficiently able to make it all work.


 * Results:

2/13 - I have completed the decode and the scoring has been created. These are the results that I had gotten from that scoring:

SYSTEM SUMMARY PERCENTAGES by SPEAKER

,-.     |                            hyp.trans                            | |-|     | SPKR    | # Snt # Wrd | Corr    Sub    Del    Ins    Err  S.Err | |-+-+-|     | sw2001b |    1      3 |100.0    0.0    0.0   66.7   66.7  100.0 | |-+-+-|     | sw2005a |    2     42 | 76.2   11.9   11.9    7.1   31.0  100.0 | ...................................................................     ...................................................................      | sw2082b |    1     14 | 35.7   57.1    7.1    0.0   64.3  100.0 | |-+-+-|     | sw2083a |    2     25 | 60.0   16.0   24.0    4.0   44.0  100.0 | |-+-+-|     | sw2085b |    2     30 | 70.0    6.7   23.3    6.7   36.7  100.0 | |=================================================================|     | Sum/Avg |  101   1530 | 70.0   21.8    8.2    7.3   37.3   89.1 | |=================================================================|     |  Mean   |  1.4   21.0 | 72.8   20.2    6.9   12.9   40.0   87.9 | | S.D.   |  0.5   17.5 | 20.4   17.7    9.3   21.5   25.4   30.7 | | Median |  1.0   16.0 | 74.4   19.0    3.3    5.3   37.1  100.0 | `-'

Successful Completion

2/15 - Our team just concluded today's meeting for the proposal, we will keep in touch for the next to days to be able to work with the other groups so that we may make one cohesive proposal draft that encompasses everything from all the teams and has a single narrative that is easy to follow and that is considered valid and worthy of funding!

2/16 - Read logs.

2/18 - Took the time to fill in my portion of the main_decode.c file and to converse with my group about what we are planning on doing this Tuesday. At this steady rate, we will each be able to realistically take one file at a time and go through it per week!


 * Plan:

2/13 - Our teams plan for this week is to locate a few files that are important with the Sphinx3 decoder and each run code reviews of these files so we can understand and share our results with the group. This is going to be a long and arduous process, but hopefully we will pull through. We have found the main file where the Sphinx3 Decoder starts, so now we are going to need to analyze it and see how it works.

2/15 - For the next few days, our team will be double checking on the proposal sheet until it is completed to make sure that we can make everything cohesive between all the groups and to add a narrative. Aside from the proposal, we will all take the time to research everything inside of the main_decode.c file and try to fully flesh out all of it's functionality and files it uses. Westley also made an interesting find that using Visual studio for this project seems to be a fantastic idea as after some tinkering with the files (more info on what he did to them later) he was able to open the project in Visual Studio and was able to he all the files be shown in one comprehensive place with everything linking up together as it currently is. Once he gives the directions for us to be able to do this, we should have virtually no issues in creating the physical model!

2/16 - Read more logs and to continue decoding when I have the time.

2/18 - For the rest of this week, I will be looking through more of the main files and trying to summarize them the same way we have done with the main_decode.c file.
 * Concerns:

2/13 - My only real concerns right now are my availability outside of class. As it stands right now I only have early mornings to help out or to do research, but after the morning, I am usually at work until 9 o'clock at night. So for the final proposal, we need to meet at a time after 9 o'clock, which we can do, but won't be that simple.

2/15 - Concerns about understanding the Sphinx3 decoder are nonexistent, I don't think it's going to be hard looking over the code and piecing everything together. What I do have concerns with are availability and time when I will be able to work on the project at hand. I need to get a set schedule for working on capstone and working on other classes. Life's gonna be complicated for the next few weeks.

2/16 - I wasn't able to do much of anything today. I need to put some time in tomorrow to make up for today!

2/18 - So far, we as a team have no concerns. I also don't have any pressing concerns for this week. Something that is on my mind is that I want to make sure that I am making these logs more new-user friendly so that I can make it more useful as a learning tool. I will use next week to add revisions to older posts so that I can show code and commands that I've dealt with for that week.

Week Ending February 26, 2013

 * Task:

2/22 - Read Logs.

2/23 - Last Tuesday, I had been late and spent the majority of the meeting time out in the break area for students. So while I missed a large portion of the meeting, my team reassured me that not much importance had gone down while I was out there. Anyways, The task for this week is for me to look at every single line of code connected to the main and create the physical mapping of it. I have until May 8th to create it, which is honestly more than enough time to do so. Since I plan on getting it done quickly, I'll also like to try and assist my team with whatever else they need in their own tasks.

2/24 - I was able to get out of work early today and was able to log into Caesar and browse through some files in the directories to add to the list of files I need to work with for the mapping.

2/25 - Tonight, it seems that my team will be meeting, and I just happen to be out of work at the most opportune time to attend it. We will be going over our team goals for the start of this week. Hopefully we will be able to get a better understanding of what we are going to be doing for the rest of the semester.


 * Results:

2/22 - Read Logs.

2/23 - It's been quite a busy week for me, not in the sense that I've been making headway into the mapping, but more that I haven't had a single minute of daylight to use towards my task. my job is taking most of my days, and being the late riser that I am, kind of makes me have to do any meaningful work near midnight. I'll need to change my sleep schedule in order to make the time to be more productive!

2/24 - Today I mostly just looked at the files in between the main_decode.c file. I need to start getting an idea of what files connect to each other and make a physical connection with them so that I can use it to show others how the process works. This will take some time, but shouldn't be too hard.

2/25 - It seems that each of the teams in the class need to create a poster for the URC that is going to be happening in the next few days/weeks. I believe we will be creating a breakdown of the main_decode.c file or at least trying to create something that is easy to read and shows what the software team is up to.


 * Plan:

2/22 - Read More Logs.

2/23 - For the most part, our teams proposal and goals are understood and clear. Each of us has been tasked with a specific goal to achieve for the end of the semester as well as exactly what the team as a whole will accomplish for the semester. For the most part, we will be breaking down the code with code reviews, trying to implement the code with SVN and RCS, and eventually disconnect a drone, to apply the prior, and make everything work and then reconnecting the drone and loading it's hopeful success to Caesar.

2/24 - My plan for the next few days is to continue looking through the files and keep writing those paths together on a notepad so that I can connect them all together in a web and show the other teams so they get a better understanding of it.

2/25 - The plan right now, for me at least, is to get together with my team next week and figure out what we are going to do for the URC poster as well as see what we are going to do in terms of our team goals towards decoding the main_decode.c file. We haven't been super vocal to each other this week, or at least haven't had many lengthy conversations on discord. So as it stands right now, I'm not sure what we're going to be doint this Tuesday.


 * Concerns:

2/22 - Time constraints are always my greatest concerns right now.

2/3 - As of right now, I don't have any concerns with our assignments. What I do worry about is that I am not as fluent in the decoder as the rest of my team appear to be. Who knows, maybe I'm just paranoid, but I should start taking at least an hour a day to just learn what I can about it and write it down in one of these logs!

2/24 - No concerns as of today. I was able to get out a little bit earlier today which gave me enough time to get some work done.

2/25 - No concerns as of today. I just want to start the new week guns blazing and hopefully get something of worth done in class. I can't wait to see what the code reviews we are going to do will entail!

Week Ending March 5, 2013
3/1 - Read Logs.
 * Task:

3/2 - Yesterday our group met on google hangouts with Professor Jonas and he was able to show us a little bit about the decoder and gave us a clearer understanding of what the files looked like and what we should be focusing on with our research. I will need to use the internet as well as the notes in each of the files to figure out what the files and commands do in them.

3/3 - My task for this week is to research the "kb_init..." command and it's file and the "config = ..." command and it's file and understand them and how they work. I should also take the next few weeks to go around and ask my fellow team mates what they are up to with their portions of the project and see if I can learn anything new from them.


 * Results:

3/1 - Read Logs.

3/2 - It is going to take some time, especially with my busy schedule, to be able to sit down and focus on which files will be most useful to look at. I guess I'll just have to pick a root directory and see from there.

3/3 - During the Google Hangouts our team had with Professor Jonas, I had taken down some notes based on what he was explaining to us. I will post them here, even though they are a tad simple. Sphinx_fe (Feature Extraction) Sphinx3_... (Sphinx3 Decoder stuff) qstuff (Torque?Tork?)

Is CFG_SPHINXTRAIN_DIR = "/root/speechtools/SphinxTrain-1.0" being used anywhere? grep (something) *   or */*/* Makefile compile your program which is distributed among source files.

Java Money cash; cash = new Money; cash.amount;

C++ Money cash; cash = new Money; doStuff (&cash); ...    	public doStuff(Money *c) {    		(*c).ammount;		/same thing   i.e. (*st).tm c->amount;		/same thing  i.e. st->tm }

kb_init(&kb, config)	!!!Important!!! Research This config = cmd_ln_get;	Then This


 * Plan:

3/1 - Read more Logs. 3/2 - Today, I will be looking at two specific commands: kb_init(&kb, config); and config = cmd_ln_get; and trying to figure out what exactly they do and call upon and how they interact with the rest of the decoder.

3/3 - My plan for right now is to dig deep into the decoder and finally try to learn something new from it. I feel like I still don't know much about it, nor do I know how to operate it sufficiently. I've only done the train and even then, I'm not sure what else, if anything, I should do with the data.


 * Concerns:

3/1 - Not enough Logs :)

3/2 - So far, I have no concerns. Everything is going well

3/3 - My only concerns this week are with my other classes. I have a speech outline to right and an exam to prepare for. Aside from that, the week looks promising.

Week Ending March 12, 2013
3/7 - Yesterday, Professor Jonas took us into the library did an honest to goodness code review with us. He showed us the how to search through the file and find where the commands originate. I will take the time to use this new knowledge to finally map out the full mapping of the command process.
 * Task:

3/8 - Read Logs.

3/10 - This week I haven't really done much. I just haven't had the time to be able to adequately work on anything that I would need to work on. My Task for this week is to prepare for next week as I will have 3 full days to work on anything related to the capstone. I'm looking forward to the available time!


 * Results:

3/7 - We learned a lot from Professor Jonas. We are going to be able to traverse these files SO much easier now. And now that he has showed off how to use most of the commands, it will be easy to replicate them now.

3/8 - Read Logs.

3/10 - As I wait for next week to roll by, I can't help but feel eager to get to mapping all the paths for the commands. Ever since Professor Jonas did that code review with us, I feel like I'm ready for it!


 * Plan:

3/7 - Starting in the next few days, I will be going through the main, in it's entirety and writing all it's path names and file names for ever line of code in the main. When I'm done, I'm going to have a large tree like structure which will be able to lead you to where and how everything is located together.

3/8 - Read Logs.

3/10 - My plan for now is to wait until Monday of next week where I will be able to start mapping the paths of everything with relative ease!
 * Concerns:

3/7 - My only real concern is just how big the undertaking will be... :)

3/8 - Read Logs.

3/10 - My only concern for this week is that I hope I can have some uninterrupted work time for this, as I am usually called away from my computer to do other mundane tasks...

Week Ending March 26, 2013

 * Task:

3/20 - We have just finished our code review for the day and are being tasked with understanding what a specific portion of the code block does. Aside from that, we are also meeting our Avengers group today to collaborate on what our goals are going to be.

3/22 - Today I will be going into Caesar and doing my own code review to better understand the commands as well as to see where the code he designated to us resides and what it does.

3/24 - Read logs, specifically Lamia's as she's putting in a lot of detail into hers!


 * Results:

3/20 - The code that we are going to be looking for will be: utt_res_set_uttfile(ur, uttfile) | utt_res_set_lmname(ur, lmname) | utt_res_set_regmatname(ur, regmatname) | utt_res_set_cb2mllrname(ur, cb2mllrname).

3/22 - I have looked into a few of the files. I have found that the first "utt_res_set_uttfile" command is located in /mnt/main/root/sphinx3/src/libs3decoder/libcommon/corpus.c. I will try to find the remainder of locations of the files and to see what they look for.

3/24 - Read logs.


 * Plan:

3/20 - I'll take the next few days after today to go through the files and find what they do. After that, I will also try to prepare for the code review so that I can be somewhat proficient in it.

3/22 - It's been a busy few days so far, and haven't had the greatest time getting onto Caesar in order to look through the code base. I'll have to make some time later in the week in order to finish the code review.

3/24 - Finish reading some other logs and start code mapping and code review stuff.
 * Concerns:

3/20 - My concerns right now, are more on the speech that I am going to be giving in the next 45 minutes. It's psyching me out right now!

3/22 - My only concerns right now are to make sure to finish these logs and to start my portion of the software group which is to create the physical mapping for future classes. I'll need to take the next few weeks to do this and leave it behind the server room.

3/24 - Only concerns right now are to be prepared for the code review.

Week Ending April 2, 2013

 * Task:

3/29 - Today, after I get back from work, I will be doing a decode on either seen or unseen data, based on Stephen's Experiment log so that I can help our Team see if our decode in general is the better one!

3/30 - Today I finished the decode on seen data (I think) and have the scoring completed (I think)... I followed the directions that were provided to us by our resident genius Stephen. However as I was following them, there wasn't any way for me to tell if the last 2 steps which where to run PARSE and then have the scoring printed into a log. I'll have to get Filezilla in order to see the scoring, if it worked at all.

3/31 - Read Logs

4/1 - Helped Lamia with her testing of Rome and Caesar and if the trains/decodes would be identical.


 * Results:

3/29 - I have gotten the steps needed to preform a successful decode from Stephen from our Discord server. I will get right on this as soon as I get out of work and will then post my findings in the available chat server where everyone else is posting theirs.

3/30 - I have finished the decode and am going to see and post the scoring results on discord when I get home from work today. Hopefully everything is exactly the same as everyone else's for it to be consistent.

3/31 - Read Logs

4/1 - Unfortunately due to Rome not having the ability to run addExp.pl, I was not able to create a path to it in the Exp folder which would have allowed me to test each server.


 * Plan:

3/29 - Following the above, I will also be working on two other things, which are the URC Poster for our group and the mapping for our next code review on this coming Tuesday. I'm not really sure what I can add to the URC poster, but I'm sure I'll be able to find something of relevance that will make it stand out just that bit more.

3/30 - My plan now is to assist Lamia with the URC Poster and to continue focusing on the mapping for the code review.

3/31 - Read Logs

4/1 - I will not be able to help Lamia like she wanted until she gets emailed back from Professor Jonas on how to proceed/fix the issue.


 * Concerns:

3/29 - My concerns for today are that I want to make sure that I am doing what I can to assist both my team and our chances of winning our friendly competition.

3/30 - My only concerns for today are if the decodes are the same so that means everything is consistent!

3/31 - Read Logs

4/1 - My only real concerns right now are looking into the code review as I haven't had much time to go and look into them/

Week Ending April 9, 2013

 * Task:

4/4 - My task for this week is to continue with our code review for next week. It feels like these logs get shorter and shorter as they go on.

4/5 - My task for today is to focus on studying for the code review.

4/7 - Today and tomorrow I have to focus on studying for an exam in my regional geography class. It’s going to take up a lot of time.

4/8 - Read logs


 * Results:

4/4 - I think I know a bit more of how the code works, but it’s still a mash of code to sift through...

4/5 - there is a lot to look at in the sphinx3/base code and there’s only so much I can grep though.

4/7 - Today I’m more focused on studying for my regional geography exam.

4/8 - Read logs.


 * Plan:

4/4 - Review code for our code review next week.

4/5 - Keep reviewing code so that I can lead Professor Jonas through it.

4/7 - Study for my exam!

4/8 - Read logs.
 * Concerns:

4/4 - None at the moment

4/5 - None at the moment

4/7 - Gotta study for that exam!

4/8 - Read logs.

Week Ending April 16, 2013
4/10 - Today we got into groups and were given the option of choosing if we wanted anyone from the other team and whom we were going to safeguard. In the end it didn't matter though as both teams didn't want to take anyone from the opposing team! Yay for friendship!
 * Task:

4/11 - Stephen asked me to take a look through the past 2 years worth of logs and find anything that would be able to give any insight on anything they did that would be able to help with the trains, decodes, etc. I'll have to take a long while to look through and read any that have any good info.

4/13 - Read Logs.

4/15 - Today I have to finish up some assignment from other classes, but I also need to start looking into the code review and jotting down anything important I see. I can't have Josh being the only one doing all the work now can I!


 * Results:

4/10 - We got into groups and discussed are game plans for the rest of the semester and how we are going to continue with our research.

4/11 - I looked through all of the logs from the past 2 years and honestly there wasn't much that could be used. I was able to find 3 specific logs that had a bit of information regarding parameters used and such, but whether or not it is actually useful will be something we have to see!

4/13 - Read Logs.

4/15 - I'll look into the code and see what I can deduce from it.


 * Plan:

4/10 - Our team is going to split up into 2 teams that are going to be working on 2 different areas for our research. Unfortunately I can't divulge anything on this, but know that we have some interesting things in the works.

4/11 - Our teams plan is still to split into 2 groups and work on our tasks that will help us achieve a better error rate. Only time and a lot of research will tell if we are getting anywhere!

4/13 - Read Logs.

4/15 - Get into the code for our next code review and see if I can get a good understanding of it.


 * Concerns:

4/10 - None, though I am interested in how everything is going to play out in the end!

4/11 - None so far with Capstone, though this is going to be a busy week for me...

4/13 - Read Logs.

4/15 - None at the moment.

Week Ending April 23, 2013

 * Task:

4/17 - After class and our code review, we got together with our teams and discussed a few things that we needed to take care of in the decode and trains.

4/18 - Read Logs.

4/20 - Today I was asked by Lamia to run a 145hr Experiment on seen data to see if it matches up with her results.

4/21 - I am running the new Experiment now and need to make sure that I don't get anything wrong. The commands are going to take a while to complete so I will have to score everything once I get home tonight.


 * Results:

4/17 - We'll need to get in touch with professor Jonas and let him know what we know and see what we can do about it.

4/18 - Read Logs.

4/20 - Due to an error with some of the commands, some of the requisite files necessary were not created so I was not able to to finish the Experiment.

4/21 - Everything is finished and the scoring has been created and I posted it to our discord.


 * Plan:

4/17 - We have to wait for instruction from Professor Jonas before we can continue effectively.

4/18 - Read Logs.

4/20 - I will create a new experiment tomorrow doing everything exactly the same only changing a few things based on Daniels suggestions.

4/21 - All I need to do now is finish my research into the code review which I will lead tomorrow.


 * Concerns:

4/17 - No major concerns at the moment.

4/18 - Read Logs.

4/20 - No concerns at the moment.

4/21 - No concerns at the moment.

Week Ending April 30, 2013

 * Task:

4/25 - These are the final two weeks for capstone. We are all trying to finish up our individual tasks and are striving for a low W.E.R. (Word Error Rate). I helped Lamia by running a quick 5 hour experiment to make sure that everything we had matched up with what she was getting for results.

4/26 - Read Logs.

4/29 - Today I was asked by Jaden to help out and look at the proposal and see if I could edit it and make it look a tad more professional.

4/30 - With only one more week of classes, there isn't much else to add. It's mostly just tidying up the experiments and make last minute adjustments.


 * Results:

4/25 - My scoring log finished and I posted it to the discord.

4/26 - Read Logs.

4/29 - Whenever more information is put into the proposal, I will take the time to neaten it up and make sure it sounds coherent.

4/30 - we are effectively just waiting the rest of the semester out and supplying out results from our experiments.


 * Plan:

4/25 - The plan for the rest of the week is effectively just trying to be as useful to whomever needs the most help right now. Aside from our code reviews, we have so much time to help with whatever else our group needs.

4/26 - Read Logs.

4/29 - The plan is to wait for others to input the data that they have gathered and then for me to tidy up the proposal.

4/30 - Just waiting for all the results to come in.
 * Concerns:

4/25 - There are no concerns here!

4/26 - Read Logs.

4/29 - None at the moment.

4/30 - There are no more concerns!

Week Ending May 7, 2013
5/3 - This is the last week for Capstone. Our team has prepared all of our strategy and all of the experiments that we could have fit in.
 * Task:

5/4 - Not much left to do as it's the end of the semester, now we wait!


 * Results:

5/3 - All that's left to do this week is have everyone of our experiments and our teams strategy ready for the end of the semester.

5/4 - Not much left to do, just compounding the results and adding them to our proposal and end of semester stuff!


 * Plan:

5/3 - Getting all of our experiments and our strategy ready for the final day of the semester.

5/4 - Nothing left to plan, now we just wait!
 * Concerns:

5/3 - Hopefully we win!

5/4 - Hopefully we win!