I’m excited to have made progress on D3 Sunburst Sequence Model. My main focus this week was fully integrating this model with the Archiver's API and general maintenance. After figuring out how to make it work with a JSON file instead of CSV, I modified my visualization to fully work with the Archiver's API. Upon some discussion on the slack channel it was decided that percentages would be calculated based on numLeavesArchived/numLeaves and that any node with a parent would have it's percentage based on it's numLeavesArchived/ it's parents numLeaves. I also modified the visualization to remove nodes that could not be seen (ie: anything with a percentage < 0.1%) so the model now overall renders much faster.
I worked on the following Issues:
Integrated with the Archivers API
Improved efficiency of rendering the model (and general interaction)
Started working on making colors appear sequentially throughout the arc (they get lighter as you increase depth)
Started working on overall animation of the model.
Finally, I’m concerned about these upcoming or outstanding issues, which may block progress or impose design constraints:
just need some final help from @b5 and maybe the rest of the mentors working out how the model is going to interact with the API (such as how deep should I render the tree before I redirect to a link and how am I constructing URL's).
I’m excited to have made progress on D3 Sunburst Sequence Model. My main focus this week was fully integrating this model with the Archiver's API and general maintenance. After figuring out how to make it work with a JSON file instead of CSV, I modified my visualization to fully work with the Archiver's API. Upon some discussion on the slack channel it was decided that percentages would be calculated based on
numLeavesArchived/numLeavesand that any node with a parent would have it's percentage based onit's numLeavesArchived/ it's parents numLeaves. I also modified the visualization to remove nodes that could not be seen (ie: anything with a percentage < 0.1%) so the model now overall renders much faster.I worked on the following Issues:
Finally, I’m concerned about these upcoming or outstanding issues, which may block progress or impose design constraints:
just need some final help from @b5 and maybe the rest of the mentors working out how the model is going to interact with the API (such as how deep should I render the tree before I redirect to a link and how am I constructing URL's).