I’m excited to have made progress on D3 Sunburst Model. My main focus this week was mostly involved with speaking to Brendan about the project thus far, going through the code review and explaining how the whole thing works, as well as making some decisions going forward on how I should precede with the model.
Although there were no immediate issues to work on, a lot of design constraints were made very apparent that need to be fixed soon. Among them were:
the definition of coverage and % completion (is it based off parent or child nodes?)
how to properly colorize the model to show completion simply based on first glance
how to separate the API into more understandable portions rather than basing it off url and discarding 97% of the data.
Finally, I’m concerned about these upcoming or outstanding issues, which may block progress or impose design constraints: the only thing I'm really waiting on is for @b5 to update his API and basically check those results to see if the model looks like something we want.
I’m excited to have made progress on D3 Sunburst Model. My main focus this week was mostly involved with speaking to Brendan about the project thus far, going through the code review and explaining how the whole thing works, as well as making some decisions going forward on how I should precede with the model.
Although there were no immediate issues to work on, a lot of design constraints were made very apparent that need to be fixed soon. Among them were:
the definition of coverage and % completion (is it based off parent or child nodes?) how to properly colorize the model to show completion simply based on first glance how to separate the API into more understandable portions rather than basing it off url and discarding 97% of the data.
Finally, I’m concerned about these upcoming or outstanding issues, which may block progress or impose design constraints: the only thing I'm really waiting on is for @b5 to update his API and basically check those results to see if the model looks like something we want.