Open annisiren opened 1 year ago
In the typical setup for our datasets (at least as currently understood), an aER requires the iER that comes before it, but next week's iER comes_after the aER. In order to keep the graph in this view connected, the visualizer must infer a comes_after relation between the two aERs and visualize that.
to be more precise at the moment, these relationships are inferred from comes_After for all three views (the green path). therefore all the chronological relationships are coming from comes_After. this relationship happens between start, aER, iER, and end nodes that have the corresponding type attributes.
in the Summative assessment view while adding relationships between nodes, if the current node has a node Id x in its comes_After field, we find the node x and make the connection if the node is aER, start, or end. otherwise, we obtain the node ID y from node x's comesAfter field and move to node y, check for the condition and so on.
In this process, if comesAfter is empty/ null for any of aER, iER, start, and end types (or there are two values there at the moment) then connection will not be made.
I hope this helped :)
That's what I thought was indeed the case. Based on the definition of these relations as outlined in the AIR model doc, that will not be sufficient for the summative assessment view, as there will not be a connected graph. The visualizer must add the relations as I described in my previous message. Happy to discuss on zoom if further clarification is needed (or on Friday).
Dataset: 2311 View 1: Summative assessment only
There are many empty nodes within the summative assessment. Taking the first week activity data as an example, when looking at the dataset itself
these are every single time week 1: activity (ID: 5) is mentioned within the whole dataset. The only other connection is the iER attached which in this view should be ignored.