Plagiarism Checks - Githubissues

reed-college / vrfy

the (bare bones) beginnings of the cs hw project for the sds

0 stars 1 forks source link

Plagiarism Checks #3

Open grantal opened 8 years ago

grantal commented 8 years ago

From @AlexV348 on November 24, 2015 18:58

Check if student files look the same
- also check for things like variable name changes
Also check against solutions found on google

Copied from original issue: ifjorissen/vrfy#193

grantal commented 8 years ago

From @Gastove on November 24, 2015 19:5

Curious: who/what is motivating this? The notion of plagiarism is well understood for, say, essays -- but for code, I think this might get problematic in a hurry.

grantal commented 8 years ago

Adam said on a recent assignment that some student people had similar solutions to a problem and one even commented that he copied the solution from the internet. He also said this is more of a long term goal since the semester is almost over anyways.

grantal commented 8 years ago

From @jimfix on November 24, 2015 21:10

I think code similarity checks have become a common thing in this kind of software project. There may also be existing packages/systems. For example:

https://theory.stanford.edu/~aiken/moss/

-j