-
Notifications
You must be signed in to change notification settings - Fork 17
/
gradescope.html
109 lines (107 loc) · 5.42 KB
/
gradescope.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>CS3100 - Information about Gradescope and Submitting Assignments</title>
<style>
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
</style>
<link rel="stylesheet" href="../markdown.css" />
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<h1
id="cs3100---information-about-gradescope-and-submitting-assignments">CS3100
- Information about Gradescope and Submitting Assignments</h1>
<p><a href="./index.html">Back to Homeworks</a></p>
<p><a href="../index.html">Back to Main Page</a></p>
<h2 id="gradescope"><a name="introduction"></a>Gradescope</h2>
<p>For this course, we will be using <a
href="https://gradescope.com">Gradescope</a>, a platform for submitting
programming assignments, grading paper-based exams, and other similar
things. You should have an account on Gradescope, linked to your UVa
email address. This page summarizes notes related to getting your code
submitted correctly on Gradescope.</p>
<h2 id="programming-assignments"><a name="introduction"></a>Programming
Assignments</h2>
<p>Your assignments can be completed in one of three programming
languages: Java, C++, or Python. When you submit your code, you MUST
submit the following:</p>
<ul>
<li><strong>Individual Code Files:</strong> You must submit all of your
code as individual code files with no folder structure. You can submit
multiple files, but they cannot be in folders (no Java packages for
example).</li>
<li><strong>Makefile:</strong> Gradescope will expect you to submit a
Makefile. Don’t be frightened by this. They are very simple and there
are examples provided below. The makefile MUST be named “Makefile”
exactly (capital M).</li>
</ul>
<p>Once your code is uploaded, the autograder will do the following
things:</p>
<ul>
<li><strong>Invoke ‘make’</strong>: The unix command ‘make’ will be
called. This will use your provided Makefile to figure out how to
compile your code. You can adjust your makefile to the particulars of
your project if necessary.</li>
<li><strong>Invoke ‘make run’</strong>: The unix command ‘make run’ will
be invoked to execute your code on several test cases. Your Makefile
will define what command is executed to run your code. Gradescope will
use the unix diff command to compare your output to the correct
output.</li>
<li><strong>Response given</strong>: Once the test cases have been run,
you will get one of several responses: If your code doesn’t compile,
you’ll get a message to that effect. If your code does compile, you’ll
see individual test cases, each of which will say that your code either
passed, had a runtime error (we won’t be able to tell you what it is
though), or time limeout exceeded (your code was too slow).</li>
</ul>
<p><strong>SMALL NOTE:</strong> You can test your make file by using a
unix terminal and running the following commands:</p>
<pre><code># compile the code
make
# run the code
# cat sampleInput.in just outputs the contents of the input file you want to test
# make run takes that input and runs your code on it (as if you are typing it in yourself)
# tail -n +2 removes the first line of output from your code (because it will always be the command that executed, not the real output of the program)
# > outputFile.out writes the output of your solution to a file called yourOutputFile.out
cat sampleInput.in | make run | tail -n +2 > yourOutputFile.out
# test if your program worked correctly. Compares your output file to expected one. -w means ignore differences in whitespace.
# If your program worked, you will see no output at all from this command.
diff -w yourOutputFile.out sampleOutput.out</code></pre>
<h2 id="meaning-of-gradescope-scores"><a name="grademeaning"></a>Meaning
of Gradescope Scores</h2>
<p>Graded assignments in Gradescope will have a numeric score which will
map onto one of the two levels of homework grade possible in our course:
<em>Incomplete</em> and <em>Pass</em>.</p>
<ul>
<li>A grade of <strong>0</strong> means the assignment does not meet our
minimum expectations and/or does not show sufficient effort and
engagement with the material.</li>
<li>A grade of <strong>1</strong> means the assignment meets our minimum
expectations even if there are still problems or flaws with the work.
This is considered passing, but the student should still reflect on and
work through additional problems that exist in their homework.</li>
</ul>
<h2 id="example-makefiles"><a name="introduction"></a>Example
Makefiles</h2>
<p>Below are example makefiles for each language. You should look at
these and make slight tweaks if necessary. The comments in the Makefile
will give you some information about this.</p>
<ul>
<li><a href="./makefiles/java/Makefile">Java Makefile</a></li>
<li><a href="./makefiles/cpp/Makefile">C++ Makefile</a></li>
<li><a href="./makefiles/python/Makefile">Python Makefile</a></li>
</ul>
</body>
</html>