You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think I've needed this enough myself, and I more-or-less just got a request for it. It'd be cool to have a way to see the current feedback and execution output for all the students in an assignment. This could be done fairly easily by just grabbing the history logs, but I wonder if we should be more efficient and have a database table that gets updated to the latest version of their output - after all, the history search has been sluggish. This might actually also feed into the need to make the dashboard for tracking feedback logs. If it plays nicely with Pedal, then this could really streamline what we wanted that system to be able to do.
Essentially, I think I'm proposing a new Execution table that maps Submission.id to some fields like output, inputs, compiler errors, pedal feedback message, and pedal feedback objects. The dashboard would have to know to grab all the submissions relevant for a course/assignment/user, but honestly that might be a more efficient query anyway? Which is better, a bunch of IDs or a range query on an indexed table? I need to review some SQL.
The text was updated successfully, but these errors were encountered:
Something like CodingRooms https://codingrooms.com/ "real-time student dashboard" would be amazing. It does not need to be as feature rich as this either. To just see student code by displaying the history logs in a grid style view.
I think I've needed this enough myself, and I more-or-less just got a request for it. It'd be cool to have a way to see the current feedback and execution output for all the students in an assignment. This could be done fairly easily by just grabbing the history logs, but I wonder if we should be more efficient and have a database table that gets updated to the latest version of their output - after all, the history search has been sluggish. This might actually also feed into the need to make the dashboard for tracking feedback logs. If it plays nicely with Pedal, then this could really streamline what we wanted that system to be able to do.
Essentially, I think I'm proposing a new
Execution
table that mapsSubmission.id
to some fields likeoutput
,inputs
,compiler errors
,pedal feedback message
, andpedal feedback objects
. The dashboard would have to know to grab all the submissions relevant for a course/assignment/user, but honestly that might be a more efficient query anyway? Which is better, a bunch of IDs or a range query on an indexed table? I need to review some SQL.The text was updated successfully, but these errors were encountered: