Thursday, October 4, 2012

October 1st - 5th



Week's Plan:
Continue working on the graph related work, continue making edits.
Work on polishing the proposal based on edits.
Get more reviewers.

Week's Accomplishments:
Added more content to graph section.

Problems:
Spent three days in the Children's Hospital with Wakako.

Next Week's Plan:

Continue working on the graph related work, continue making edits.
Work on polishing the proposal based on edits.
Get more reviewers.


Other Pieces of Work: (I just don't want to forget these ideas, not sure how necessary / important they are)

We should export the frequency data for the stoichiometry data and load that into yEd and see what see.

We should write some type of data loader that lets load in "hint-actions" so we can see where students request hints.

I should develop a Data-Properties class to more appropriately manage the different functions we have available depending on what type of data is read in. Basically the object just stores a dozen or so flags that are set based on what columns are read in, in the data-import stage of the program.

September 29th - October 2nd



Week's Plan:
Work on the related work section for graphs
Finish the first draft
Address the feedback received from Dr. Barnes.

Week's Accomplishments:
Made some edits.
Moved the document to google docs.
Worked on graph related work.

Problems:
Wakako was sick all week and so I had to stay home with her many days.

Next Week's Plan:
Continue working on the graph related work, continue making edits.

Other Pieces of Work: (I just don't want to forget these ideas, not sure how necessary / important they are)

We should export the frequency data for the stoichiometry data and load that into yEd and see what see.

We should write some type of data loader that lets load in "hint-actions" so we can see where students request hints.

I should develop a Data-Properties class to more appropriately manage the different functions we have available depending on what type of data is read in. Basically the object just stores a dozen or so flags that are set based on what columns are read in, in the data-import stage of the program.

September 17th - 21st


Week's Plan:
Add motivation to introduction section.
Read and write the rest of the sequence mining section.

Week's Accomplishments:
Added some motivation. Finished off the sequence mining section. Wrote up the interaction Network Section. 

Problems:
No problems, accomplished quite a bit.

Next Week's Plan:
Work on the graph section of the related work. Finish the first "rough draft" of the proposal.

Other Pieces of Work: (I just don't want to forget these ideas, not sure how necessary / important they are)

We should export the frequency data for the stoichiometry data and load that into yEd and see what see.

We should write some type of data loader that lets load in "hint-actions" so we can see where students request hints.

I should develop a Data-Properties class to more appropriately manage the different functions we have available depending on what type of data is read in. Basically the object just stores a dozen or so flags that are set based on what columns are read in, in the data-import stage of the program.

Monday, September 17, 2012

September 10th - 14th


Week's Plan:
Add motivation to introduction section.
Read and write the rest of the sequence mining section.

Week's Accomplishments:
Put my computer back together, so I can work from home again. Installed windows, etc.
Read some work on sequence mining.

Problems:
Had no internet.
Had no PC at home, but had parts come in.

Next Week's Plan:
Write up the interaction network section.
Finish the sequence mining related work section.
Add motivation to introduction.

Other Pieces of Work: (I just don't want to forget these ideas, not sure how necessary / important they are)

We should export the frequency data for the stoichiometry data and load that into yEd and see what see.

We should write some type of data loader that lets load in "hint-actions" so we can see where students request hints.

I should develop a Data-Properties class to more appropriately manage the different functions we have available depending on what type of data is read in. Basically the object just stores a dozen or so flags that are set based on what columns are read in, in the data-import stage of the program.

Tuesday, September 4, 2012

August 27th - 31st


Week's Plan:
Write a lot of my dissertation proposal. Focusing on combining like sections and filling out the proposed contributions section. Also add some more specific examples of the tables, diagrams, etc. so that it is more clear.

Week's Accomplishments:
I wrote a lot. I combined necessary sections and was able to make a concrete direction in the text. The proposed contributions chapter is more directed and concrete. The related work has the appropriate sections and direction, though lacks the text needed.

I submitted the work to Tiffany on Thursday night, for the Friday train ride. Also fixed our issues with dropbox.

Problems:
I was not able to address Entropy example. I worked on this but ran into two issues. For entropy  to work, we want to separate based on students that make it to a goal state and students that do not. If we use a simple data-set with less than 10 students, overlap is pretty rare, meaning most states have a frequency of 1. By default all frequency 1 states have an entropy of zero, meaning they are uninteresting. After you remove those states, the overall contribution of entropy is pretty low. However with a much larger graph, like 100 or 200 students, the number of states with a non-zero entropy should be significantly higher. 

I should graph the percent of non frequency one states, to case count (ie. sample size of students) to show the relationship of growth between these two variables. For large samples it seems roughly 50% of the states are frequency one. For smaller samples as much as 80 or 90 percent of states can be frequency one.

Next Week's Plan:
Read the feedback on my draft, make changes as necessary. Continue writing.
1) Add motivation to the introduction chapter.
2) Add content to related work.


Other Pieces of Work: (I just don't want to forget these ideas, not sure how necessary / important they are)

We should export the frequency data for the stoichiometry data and load that into yEd and see what see.

We should write some type of data loader that lets load in "hint-actions" so we can see where students request hints.

I should develop a Data-Properties class to more appropriately manage the different functions we have available depending on what type of data is read in. Basically the object just stores a dozen or so flags that are set based on what columns are read in, in the data-import stage of the program.

Sunday, August 26, 2012

August 20th - 26th

Week's Plan:
Do a literature review on modelling problem solving.
Do a literature review on sequence mining.
Do some writing for graph-layouts, proposing the idea, edit the chapter on sequence mining, based on my findings for this week.

Week's Accomplishments:
I read a number of works on sequence mining and became more familiar with their goals, focus, and nomenclature. I also read up on modelling problem solving, which went much further away from logging tutors and states of problems and much more towards the state of the mind and ACT-R. It seems there is a significant gap between the states we can generate from tutors and data and the states modeled in psychology research. 

In the case of sequence mining that challenge is the very act of identifying the sequences. The problems have long target strings and really long data-strings, in the thousands of characters. In our case the challenge isn't discovering the sequences, though the algorithms developed from that field would be useful in our tool. Our challenge is to identify which sequences are most meaningful. For this, we need to look at the community structure and discoveries we can make from the networking field. By investigating the graph-invariants of the problem-solution space we can gain insight to which states are important.

I also wrote up my arguments and proposed ideas for investigating these aspects mentioned above.

Problems:
No problems these week.

Next Week's Plan:
Meet with Tiffany on Monday and discuss my proposed arguments. Continue writing up my proposal in a more concrete manner. I need to organize the text I have into a single consistent document. Where all the related works from each of the papers appear in the same related work section, combine the introductions, etc. and remove redundancy in the text. Specifically I will focus on the proposed research section and provide the necessary related works for those sections. I will have some text for proof-reading at the end of the week.

Other Pieces of Work: (I just don't want to forget these ideas, not sure how necessary / important they are)
We should export the frequency data for the stoichiometry data and load that into yEd and see what see.

We should write some type of data loader that lets load in "hint-actions" so we can see where students request hints.

I should develop a Data-Properties class to more appropriately manage the different functions we have available depending on what type of data is read in. Basically the object just stores a dozen or so flags that are set based on what columns are read in, in the data-import stage of the program.

Monday, August 20, 2012

August 12th - 19th


Week's Plan:
Finish step-based sequence work for presenting to Dr. Barnes. Discuss what to do next.

Week's Accomplishments:
Finished the step-based sequence work.

Problems:
The trivial case of calculating all sequences did not provide useful feedback. Naturally we need a more intelligent way of identifying important sequences, much like identifying important states.

Next Week's Plan:

Do a literature review on modelling problem solving.
Do a literature review on sequence mining.
Write a chapter for for graph-layouts, proposing the idea.
Edit the chapter on sequence mining, based on my findings for this week.


Other Pieces of Work: (I just don't want to forget these ideas, not sure how necessary / important they are)
We should export the frequency data for the stoichiometry data and load that into yEd and see what see.

We should write some type of data loader that lets load in "hint-actions" so we can see where students request hints.

I should develop a Data-Properties class to more appropriately manage the different functions we have available depending on what type of data is read in. Basically the object just stores a dozen or so flags that are set based on what columns are read in, in the data-import stage of the program.

Hours Worked:
Unrecorded, a bunch.

Tuesday, August 7, 2012

July 29th - August 4th


Week's Plan:
Write a bunch of code so that our Step-Based graph can be generated correctly. There is a lot of work to be done in order to get our Step-Based states to be generated correctly. In addition to that I need to hook it up to the plumbing of the project, with the visual editor so we can apply layouts to the new graph, and the Network-viewer module so we can have access to the corresponding Nodes-API infrastructure.

Week's Accomplishments:
Monday/Tuesday - Read up on Entropy and information gain to see if this could be used for determining which states are worth collapsing and which should be focused. This seem promising and I believe we will use it as our metric for collapsing nodes, at the very least it should be useful to directing the attention of our users to important states. I also made a handful of improvements to how the tool works as I've become more familiar with the NB-Platform.

Wed/Thurs/Fri - Designed and implemented the Step-Based graph which was a substantial amount of work and a lot of code. Wrote between 1000 to 1500 lines of code, made a number of new classes and connected the step-based graph to Nodes-API.

Problems:
No real problems, just a bit slow going, building the Step-Based graph was not very straight-forward when I started. I had to spend some design time to figure out how to get all of the pieces to go together and work smoothly with one another. After I discovered an assumption I could make about the action parameters, the pieces went in place nicely.

Next Week's Plan:
Finish off the step-based graph work. Hook up the edges of the step-based graph to the underlying pipe-works of the program. Build sequences out of the step-based graph data.

Other Pieces of Work: (I just don't want to forget these ideas, not sure how necessary / important they are)
We should export the frequency data for the stoichiometry data and load that into yEd and see what see.

We should write some type of data loader that lets load in "hint-actions" so we can see where students request hints.


I should develop a Data-Properties class to more appropriately manage the different functions we have available depending on what type of data is read in. Basically the object just stores a dozen or so flags that are set based on what columns are read in, in the data-import stage of the program.



Hours Worked:
Sun - 0
Mon - 8
Tues - 10
Wed - 8
Thurs - 14
Fri - 9
Sat - 0
Total: 49

Friday, July 27, 2012

July 22nd - July 28th


Week's Plan:
Work on the "abstract" state  representation, which will be some type of clustered state of our original states, using some type of grouping policy.

Week's Accomplishments:
Monday we finished up the work for Stephanie's poster. To do this we wrote an exporter that creates a edge-table for a graph and separates the frequencies based on the Case_Group_Id of the students. A strictly Excel based approach introduced errors into the data.

Tuesday I created a visual editor to control some of the display properties for customization purposes, which will be useful for creating images and makes the interface more usable. Also got screwed around by the action sequences.

Wednesday/Thursday - I worked on constructing the "abstract" state. The abstract state is our typical states, somehow clustered or grouped in some way. On the implementation side of the work, there are a handful of considerations to have in order to keep data-integrity. The issues I addressed included the software design of handling these "abstract" nodes. The next significant issue is properly generating the needed data out of parsed data file we created from Deep Thought. Our original parser did not consider, or generate some necessary pieces of data, impart because of how Deep Thought logs the data, so it was necessary to calculate some elements of the data. Excel was insufficient for handling these issues.

Friday - Confirm that our data converter properly calculates the new elements of the data we are interested in. We now have access to a Pre and Post Condition, the solution attempt via start-overs, and goals.

Problems:
No real problems. My biggest concern is that just reducing the number of nodes or edges is not a good metric for measuring the graph-reduction rate. The problem is, with that definition, a single node with no edges is best. I would put forth that, the derived graph must be generated strictly from the original Interaction Network, meaning only values from those nodes and edges and their relevant derived values are the only available input values for creating our new abstract-state network. This will insure that our new network is structurally sound. The spectrum approach for abstract-states may be the most appropriate approach.

Next Week's Plan:
1) I need to make a new Node-Table on the data-object class (see below) that will store our ClusterNodes and ClusterEdges which will be the back bone of our new abstract states.

2) I need to make a DataObject class, which will be similar to the data-parser, but will be used for displaying derived graphs, specifically our more "abstract" state representations.


Semi Distant 3) I should develop a Data-Properties class to more appropriately manage the different functions we have available depending on what type of data is read in. Basically the object just stores a dozen or so flags that are set based on what columns are read in, in the data-import stage of the program.


Other Pieces of Work: (I just don't want to forget these ideas, not sure how necessary / important they are)
We should export the frequency data for the stoichiometry data and load that into yEd and see what see.

We should write some type of data loader that lets load in "hint-actions" so we can see where students request hints.

Hours Worked:
Sun - 0?
Mon - 8
Tues - 9
Wed - 6
Thurs - 14
Fri - 9
Sat - 5 (planned)
Total: 51

Monday, July 23, 2012

July 15th - July 20th


Week's Plan:
Work with Aaron and find out what sequences we are able to detect.

Write up the alternative directions to research, ie. the tweaked research questions, with methodologies, introductions and expected results.

Friday I'll meet with Dr. B. and discuss the proposed directions for my research.

Week's Accomplishments:
Sunday I worked on combining the work that Aaron did, into the project with the pieces I have done, so that  InVis has all its pieces connected, specifically the sequence detecting components. I also wrote a data-exporter for the InVis project so we can load in the frequencies for the Stoichiometry data into yEd, to look at that data.

Monday I met with Dr. Croy and finished my PhD paper work. We tried a handful of different tweaks in order to detect "better" sequences. We had some success, clearing out less meaningful discoveries, specifically subsets of longer sequences.

I also met with Dr. Wartell to look at the concept of Data / Ink Ratio but it doesn't seem that this is the direction we should go. Though he did provide helpful conversation which lead me to current direction. The Data / Ink Ratio is not so much a testable metric to compare against and measuring insights is not well defined in the field of info-vis. It is more of a comparison, being that Graph A showing some data, and Graph be showing the same data but having a multi-colored background, uses more ink but doesn't add to the value of the graph. Edward Tufte made the argument, in his book - without evidence, that this should be done. Later research papers on the issue showed that with "chart-junk" pretty pictures helped people remember the graphs, though accuracy of the data was not affected.

Tuesday I made some necessary fixes to the data parser, so that we would have more clean data, for both looking at in the tool, and also for performing our sequence detection on. I also continued to work with Aaron to fine tune our algorithm for detecting sequences, and it does find "things" but its hard to say if they are the most interesting or least interesting things.

Wednesday I read Biswas best paper from EDM-12, and was able to draw a decent idea out of it. I also updated my research questions towards questions which will be easier to test and have a greater differentiation between the two. I've written a section in my proposal to reflect this proposed ideas.

Thursday & Friday I worked on reading dealing with the hint and non-hint groups of data from the 2009 semester. So we can display what the two differences between the two groups which is the focus of Stephanie's end of summer report. To do this there were a handful of changes that needed to be made to the program. I also worked with Aaron and Stephanie to help get their reports in order.

Problems:
Making the tabbed pane able to show multiple types of sequences in cohesion with the ExplorerManager of the Netbeans platform is a giant pain in the butt. I'll likely ignore the "proper" solution and just get something that works for the time being.

Next Week's Plan:
Tuesday I will go to Evie's Dissertation Defense.

I need to incorporate some trivial means of incorporating grouping-data into InVis. We often want to look at  the difference between hint groups and non-hint groups. The next would be students that solve the problems versus students that don't solve the problems.

Definitely need to spend some time working on an overview of the states, in an abstract sense. Rather than a graphical overview, re-work the description of state, to have a graph represent the more abstract states that people visit when solving a problem.

Other Pieces of Work:
We should export the frequency data for the stoichiometry data and load that into yEd and see what see.

We should write some type of data loader that lets load in "hint-actions" so we can see where students request hints.

Hours Worked:
Sun - 10
Mon - 7
Tues - 12
Wed - 8
Thurs - 8
Fri - 6
Sat - 0
Total: 51

Friday, July 13, 2012

July 9th - July 13th


Week's Plan:
Look at the Stoichiometry data to see what might be common between it and data from our other tutors.

Read up on works in Graphs, that might show me some ways of determining some ground truths to compare against.
Graph Reduction
Graph Complexity
Graph Filtering

Considered new research questions to address the similarity between the questions I have right now.
1) How do we discover important features of problem solutions in domain independent data driven ways?
2) How can graph visualization be leveraged to identify useful aspects of student solutions?

Week's Accomplishments:
Loaded the Stoichiometry data into yEd, to see if there were similarities in student behaviors with data we have from other tutors. Was hoping some similar graph structures between Deep Thought data and Stoichiometry data would stick out.

I read a handful of papers on different graph works. There is one paper by Conati who made graphs out of student solutions in the physics domain. It wasn't domain independent but I should be citing this work. They then used domain knowledge to generate hints. Papers on mathematical graphs didn't seem to offer to much help, mainly because we are more interested in graph-interpretation, and in turn actually data-interpretation, we just happen to represent it in a graph.

I also spoke with Mike and he suggested looking at the Ink / Information ratio, a concept in Information Visualization, that measures how effectively one uses screen real-estate when presenting some amount of information.

Problems:
After looking at the Stoichiometry data, there was nothing of particular interest that "jumped" out at me. One issue is that excel could not handle cell's with string lengths longer than 255 characters, which meant I couldn't "excel" my way to incorporating frequencies into this data for yEd. By not showing the frequencies, this made it significantly more difficult to identify interesting or important structures.

Looking at the two questions, it is trivial to convert one into the other. Change identify to discover, and change problem solutions to student solutions, or visa-versa, and it becomes clear they do not differ. This is even more clear, when trying to design an experiment that solves one question but not the other. I feel that there is only one contribution here.

Not having yFiles, will begin to impedes our work very soon, the evaluation period is almost expired. Aaron has a select nodes and create group-cluster implemented with y, but our sequence detection is written using Jung. To combine these we need to convert to y.

Next Week's Plan:
Monday I will meet Dr. Croy, to complete the necessary paper-work.

I absolutely must define my final questions for my dissertation. This is my biggest obstacle that hinders progress.

I want to read up how people measure the ink / information ratio in the info-vis literature. Ideally I can perform the same activity on a graph-node / information situation, to determine a metric for when combining or collapsing nodes is a good thing to do. Simply counting nodes and edges as the metric is not sufficient, because a single node, with no edges would then be shown to be the best. The problem of course is that a single node, no edge graph contains no information.

I want to read in the Stoichiometry data into the vis-tool and then export the states and edges with their frequencies. The output format will be pretty simple, tab-delminated list, of source, edge, target, frequency, where the frequency will be the edge frequency. For some of the problems in the deep thought data, distinct strategies were visible, mainly two, one of which is discussed in our case-study work. With frequencies being  shown in the Stoichiometry data, my hope would be that we could see similar strategy structures - which could warrant building a strategy detector for the Interaction-Network. I estimate I can have this work done in just a few hours, potentially even by Saturday.

Additional Thoughts:
--- The Strategy-detector for the data from Deep Thought would be rather simple. As early as the first action being performed, identifies the strategy. Among the two strategies present in that particular data-set, the frequencies are the first highest and the second highest in frequencies. The issue here, is that the definition of a strategy for this Deep Thought data is, the actions that have the highest frequencies. The argument would be that if a lot of people perform a similar set of actions, that would identify a strategy. If on the other hand, the action, or set of actions, did not have high frequency, could that set of actions be identified as a strategy?

--- The issue with this would be, we are implying that there are no uncommon strategies, and in order to be classified as a strategy, your solution must be common, which isn't exactly brilliant, or even necessarily accurate. We want to create a strategy detector, not a common-set-of-actions detector.

--- In order to better detect strategies, even uncommon ones, we probably need more dimensions in our data, like time, perhaps hint usage, or "attempts". Strategies should not contain people starting over in the middle of the strategy. Another theory, would be that you wouldn't have a lot of hint requests in a strategy, if a student is thinking three steps ahead, they should kind-of have a thought on how they would get there. A boundary between low hint request to high hint request might identify the end of a sequence or strategy.

--- Another potential method for detecting sequences would be to look at the time data of the actions. Th theory would be that the variance of the time of the actions would be small in sequences. When a sequence ends, the variance in the time data would increase, depicting more thinking-time for how to proceed, once the set of actions in the sequence were complete.

The Biggest Problems:
With a strategy detector, or a sequence detector, how do we determine if we have identified the correct sequences or correct strategies? What makes one strategy detector better or worse than another one? What makes a sequence detector better or worse than another one?

We must provide evidence that the sequences or strategies detected are legitimate. Expert review and scoring would be one potential method.

If one detector worked across multiple domains, or more domains, that would support its strength over another detector which didn't work as well over multiple domains.

Hours Worked:
Mon - 10
Tues - 12
Wed - 12
Thurs - 5
Fri - 7
Sat - 8
Total: 54

Monday, April 9, 2012

April 2 - April 6


Week's Plan:
Work on InVis and make polish some of the features based on the task list document.

Week's Accomplishments:
Acquired the documents necessary for proposal and dissertation committee, started to complete them.
Met Dr. Barnes and worked out scheduling for next year.
Wrote a module for calculating statistics of an Interaction Network.
Included error and goal data into the DataProcessor module. -- this took awhile =(
Polished up some other code in the project and added a fair amount of documentation, including Java-doc documentation.

Problems:
None.

Next Week's Plan:
Move some sections around in my proposal. Get the actual proposal template and move my text over to the appropriate template. Write the IRB for my hint study.

Hours Worked:
Mon - 3
Tues - 8
Wed - 3
Thurs - 8
Fri - 5
Total: 26

Tuesday, March 20, 2012

March 12 - March 16


Week's Plan:
Finish the ITS Camera ready.
Finish the sequence distribution, to include actions.
Investigate linking Jung-graph Nodes to the NB-Platform Nodes Api

Week's Accomplishments:
Submitted the camera-ready.
Finished the Sequence Distribution.
Linked the Jung-Graph nodes to the NB-Platform Nodes.

Problems:
I had to make a new model object for linking the Graph-nodes data to the NB-Platform Nodes. Though the data is linked, I need to edit the viewer module to use the new model object. Overall this issue wasn't as simple as I was hoping, but it makes sense now in regards to how it works and how the pieces fit together. I had to make a new class the Network-Visualization-viewer and extend Jung's VisViewer.

Next Week's Plan:
Build an implementation for the new state-model that I created, specifically for the viewer-module. I want the viewer to expand students into interactions, and interactions expand to actions and states. States and actions should be visualized in the network visualization-viewer.

Hours Worked:
Mon - 2
Tues - 8
Wed - 3
Thurs - 8
Fri - 5
Total: 26

March 5th - March 9th (Spring Break)


Week's Plan:
Join dissertation boot-camp and work on my proposal.

Week's Accomplishments:
Wrote a lot of content for my proposal and completed a first semi-rough draft.
Wrote a list of tickets for future development of InVis. Similar to a Software Design Doc or TDD.

Problems:
None.

Next Week's Plan:
Expand the sequence distribution module to include actions.
Link the nodes in the Jung Graph to the nodes of the NB-Platform Node API.

Hours Worked:
Mon - 8
Tues - 8
Wed - 8
Thurs - 8
Fri - 8
Total: 40

Saturday, March 3, 2012

February 27th - March 2nd

Week's Plan:
Meet with Dr. Barnes to discuss first round of Hypothesis questions.
From the meeting, move some of the "previous work" I've done into InVis.
     * Brute force sequence, and distributions module.
     * Girvan-Newman implementation for Java

Week's Accomplishments:
Met with Dr. Barnes, received good feedback on next steps necessary to continue progress on dissertation.
Made good progress on Invis
     Made Open / Close Actions for data (toolbar and menu icons)
     Implemented a brute force approach to Determine Sequence Distributions
     Included Interaction numbers in the properties sheets and viewer-module.
Loaded some Deep Thought data into the project, to confirm data is loaded correctly.
Found the Girvan-Newman implementation of Community Detection in JUNG
House keeping on the project, to organize the files and added comments for the java doc.

Problems:
None.

Next Week's Plan:
Barnes is out of town, communicate with her before Haiti, find the next step.
Write a bunch while at Dissertation Boot camp
Expand the SequenceDistributions Module to include Action Sequences, not just state sequences.
Continue adding Javadoc comments to InVis
Draft a design document, to include a requirements document, similar to GDD & TDD.
    -- Do I want to use Assembla for this...

Hours Worked:
Mon - 2
Tues - 8
Wed - 3
Thurs - 8
Fri - 5
Total: 26

Thursday, February 23, 2012

February 20th - 24th


Week's Plan:
Meet with Dr. B. to discuss IGIC, EDM extension work, most importantly proposal
Work on the above 3 topics.

Week's Accomplishments:
Had a very productive meeting with Dr. Barnes.
Worked with Mike on the next steps of the EDM work.
Started to process the Deep Thought data to fit the Y-ed format we used in the EDM paper.

Problems:
It's hard to define good hypotheses questions.
Need to define my questions, so I can have a game plan from here on out for this year.

Next Week's Plan:
Submit a first round of hypotheses questions to Dr. Barnes.

Hours Worked:
25

Sunday, February 19, 2012

February 13th - 17th


Week's Plan:
Submit an EDM paper.
Catch up on the work I have been putting off.

Week's Accomplishments:
Used edge betweenness to identify sub-goals.
Made a hint method for strategies
Wrote a paper for EDM based on strategy based hints.
Submitted our EDM paper.
Kind of caught up, still some residual items that will be cleared up on the weekend.

Problems:
3 days of hardcore work schedule started to take it out of me.

Next Week's Plan:
Continue some work on our EDM paper, to make a full paper for the next conference
Start some preliminary work with the BOTS data, for the International Game Innovators Conference (IGIC) Deadline in April.

Hours Worked:
40+

February 6th - 10th

Week's Plan:
Work on EDM paper.

Week's Accomplishments:
Submitted UMAP paper
Worked on EDM paper.

Problems:
None.

Next Week's Plan:
Work on proposal
Add a module for calculating different hint metrics.

Hours Worked:
30

Monday, February 6, 2012

January 30th - February 3rd

Week's Plan:
Work on potential EDM papers
Work on UMAP paper
Code some of InVis

Week's Accomplishments:
Worked on the UMAP paper.
Received some Data form Drew on Bots
Received tools from Biswas group
Worked on the EDM paper with Mike

Problems:
None.

Next Week's Plan:
Finish and Submit UMAP paper.
Work on EDM paper.
Work on proposal.

Hours Worked:
25

Thursday, January 26, 2012

January 23 - 27

Week's Plan:
Work on the ITS full paper by Wei.
Finish and submit my own ITS YRT paper.
Work with Drew on EDM possibilities.

Week's Accomplishments:
Worked on the ITS full paper.
Worked on my own ITS YRT paper, and submitted.
Worked on the UMAP paper.
Submitted the UMAP abstract
Collaborated with Drew about EDM paper using BOTS data he is collecting.

Problems:
Still haven't received any feedback on the UMAP paper.
Got zero input, feedback or interest in regards to the ITS YRT paper.
Wasted my time on ITS full paper.

Next Week's Plan:
Reduce the size of the UMAP paper to fit the 12 page, page-limit.
Submit UMAP paper

Convert the BOTS data to fit the InVis format.
Work on dissertation proposal. Start working on the related work and background.

Hours Worked:
40+

Papers & Conferences:
Conference, Due Date, Title:
UMAP - Abstracts Jan. 24th, Full papers Jan. 31st - Full Paper: InVis: An Interactive Visualization Tool for Exploring Behavior Networks
ITS - Full Papers Jan. 23rd - YRT: The Gamification of a Japanese Language Vocabulary Tutor
EDM - Abstracts Feb. 5th, Full papers Feb. 12th - Reducing Clutter in Behavior Networks through Clustering Sequences

Wednesday, January 18, 2012

January 17 - 20


Week's Plan:
Finish the rough outline of my proposal.
Write a first draft of he ITS YRT.

Week's Accomplishments:
Proposal outline is finished.
Draft of ITS paper...(pending)

Problems:
Need to receive feedback on the UMAP paper. Necessary to reduce 7 pages. What parts should go?

Next Week's Plan:
Submit ITS paper.
Submit Umap abstract.
Code sequence detection in InVis.
Work on dissertation proposal. Start working on the related work and background.

Hours Worked:
15 (25)

Papers & Conferences:
Conference, Due Date, Title:
UMAP - Abstracts Jan. 24th, Full papers Jan. 31st - Full Paper: InVis: An Interactive Visualization Tool for Exploring
Behavior Networks
ITS - Full Papers Jan. 23rd - YRT: The Gamification of a Japanese Language Vocabulary Tutor
EDM - Abstracts Feb. 5th, Full papers Feb. 12th - Reducing Clutter in Behavior Networks through Clustering Sequences