[visualization] Dashboard for CoCom backend

[inishchith]

This issue thread is for discussion related to visualizations that would be part of the (first) dashboard for the metrics produced with the help of Graal's CoCom backend.

(Currently the analyzer is run at Repository-Level)

• Metrics
  • Overall CCN
  • Overall LOC
  • Overall Comments
• Data Table ([visualization] Dashboard for CoCom backend #11 (comment))
  • File-Wise LOC, CCN, Comments, and Comment-Ratio(Comments/LOC)
  • Overall CCN, LOC, Comments, Blanks, Functions for every project ( Instead of Individual metrics like above )
• Visualizations
  • Pie-Chart:
    • Top Complex Files
    • Files with Most LOC
    • Most Commented Files or Most Comment to LOC Ratio
  • Evolution (Line-Chart): (repository controlled via the in-place selector)
    • Lines of Code
    • Code Complexity
    • Comments
  • XY-Plotting: (controlled via selector)
    • LOC and Comments for every file at each point in time.
    • Mean & Median of LOC and Comments for all the files at each point in time.
• Other ideas
  • Project/Repository/Module Selector

@valeriocos @aswanipranjal Please add some suggestions/ideas in case I've missed something out.
Thanks!

[inishchith]

Overview Data Table

• Overall CCN, LOC, Comments, Blanks, Functions for every project (Instead of Individual metrics like above)
  

---

• Top Complex files in a given software repository (Project)
  • the issue with this visualization is that the latest commit analysis contains results of all the files. hence the changes cannot be tracked down to which commit made it more complex (evolution)

[inishchith]

Overview Other visualizations

• Project-wise CCN(or other metrics) per day
  

---

• After adding a filter for origin = chaoss/grimoirelab-graal for above
  

[inishchith]

Overview Metrics

• TODO: Project-wise segregation

• Overall CCN
  

• Overall LOC
  

[valeriocos]

Good work @inishchith! A couple of questions/remarks:

• Did you check that the results obtained via the visualizations are correct?
• I can address the issue below if you want

the issue with this visualization is that the latest commit analysis contains results of all the files. hence the changes cannot be tracked down to which commit made it more complex (evolution)

[inishchith]

@valeriocos

Did you check that the results obtained via the visualizations are correct?

Yes. All the results produced above are cross-checked except for: Top Complex files in a given software repository (Project). I'm evaluating it again and will update you once done.

I can address the issue below if you want ...

I'll be working on it today. But it'd be of great help if I could have your thoughts on it.

Also if could elaborate on the idea of the derived metrics (based on relations between two attributes) would be helpful :)

Thanks!

[valeriocos]

Thank you for the info @inishchith

I'll be working on it today. But it'd be of great help if I could have your thoughts on it.
I have added a comment at: chaoss/grimoirelab-graal#39

WRT derived metrics, the idea is to add to the enriched items some fields that combine several attributes. For instance, for a file we have LOC and comments, we can add an enriched field that is comments_ratio = comments/LOC. Similar things could be done with functions or other attributes.
What do you think?

[inishchith]

WRT derived metrics, the idea is to add to the enriched items some fields that combine several attributes. For instance, for a file we have LOC and comments, we can add an enriched field that is comments_ratio = comments/LOC. Similar things could be done with functions or other attributes.

The idea sounds good to me and can be easily incorporated in the current implementation. I'll have to think over how we can show this info on the dashboard (once we're ready with an initial one, we can re-iterate and have refined versions :) )