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