Radar graph view data in table format and bad user experience of the graph

[markkuriekkinen]

The graph view in Radar is useful for finding student pairs that have similar submissions in several exercises. However, the data should also be available in a table format in addition to the visual graph. When the course has over a thousand students, the graph grows too much and it is hard to read it. It is particularly difficult to traverse through all the suspicious student pairs. The teacher can start traversing the edges of the graph, but over time it is hard to know which edges have been investigated and which ones are still left. The graph may also shuffle itself when you accidentally move the mouse or click something, in which case it is impossible to know which edges have already been investigated.

[markkuriekkinen]

One idea for improving the readability of the graph:
splitting the graph to independent and separately drawn subgraphs

From the autumn 2021 project:
https://wiki.aalto.fi/display/EDIT/Radar+development+and+productization+2021

[markkuriekkinen]

There is a screenshot of the problematic graph view here:
#5 (comment)