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
We currently log every output produced by the autograder when the student runs it in a .logs directory for further analysis. It may be useful to log the code as well, both for pedagogical analysis and for detection of collaboration, help, and so on -- a sort of version-control-lite.
The text was updated successfully, but these errors were encountered:
This sounds very useful. Especially for the similarity detection -- could run moss on intermediate versions.
Presumably if students are just uploading their whole psXX directory, we would transparently get access to those versions without any sort of extra network effort.
We currently log every output produced by the autograder when the student runs it in a
.logs
directory for further analysis. It may be useful to log the code as well, both for pedagogical analysis and for detection of collaboration, help, and so on -- a sort of version-control-lite.The text was updated successfully, but these errors were encountered: