haas/spring2026/unix/projects/fwg0.md
... ...
@@ -178,7 +178,7 @@ mismatches.
178 178
I'll be evaluating the project based on the following criteria:
179 179
180 180
```
181
-260:260:final tally of results (260/260)
181
+260:fwg0:final tally of results (260/260)
182 182
*:fwg0:code modified to meet project specifications [52/52]
183 183
*:fwg0:screenshot or video posted to class DISCORD of game running [52/52]
184 184
*:fwg0:source file, XML file, build script, and cartridge submit [52/52]
haas/spring2026/unix/projects/gtf0.md
... ...
@@ -0,0 +1,103 @@
1
+# CSCS1730 UNIX/Linux Fundamentals
2
+
3
+# PROJECT: GRADE TO FIGURE OUT (gtf0)
4
+
5
+## OBJECTIVE
6
+
7
+Throughout the semester, you have been, through the use of the text-based
8
+`sc` spreadsheet, computing your current grade in the class based on snap
9
+shots of data at the 4-, 8-, and 12- week intervals.
10
+
11
+Your aim with this project is to take your familiarity with manually
12
+performing that process, and automate it through the use of a shell
13
+script.
14
+
15
+## TASK
16
+
17
+Take one of your existing gfoX assignments and look at the spreadsheet
18
+file created. Not through `sc` itself, but instead, in a *text editor*
19
+(such as `vi`/`vim`).
20
+
21
+Take in the structure of the information, the format. The patterns of how
22
+the data progresses.
23
+
24
+Can you predict how things will progress and work? Can you automate those
25
+steps?
26
+
27
+Your aim is to create a **bash shell script** that will perform the work
28
+of reading from the **status** command output (be sure to be familiar
29
+with **grep**(1)), and have it construct a spreadsheet (in accordance
30
+with gfoX submission criteria) of your progress in the class, based on
31
+the particular gfoX instance (or week number given).
32
+
33
+You will want to make use of:
34
+
35
+ * variables
36
+ * command-line argument (via `$1`, etc.)
37
+ * if statements / the `test` command (via `[`)
38
+ * loops
39
+ * I/O redirection
40
+ * command expansion
41
+ * regular expressions
42
+
43
+Again, the `sc`-compatible spreadsheet your script produces should be
44
+viewable in `sc`, and be in accordance with gfoX submission criteria (the
45
+idea is that you will be able to use it to submit `gfo2` when its time
46
+comes).
47
+
48
+## SUBMISSION
49
+
50
+To be successful in this project, the following criteria (or their
51
+equivalent) must be met:
52
+
53
+ * Project must be submit on time, by the deadline.
54
+ * Late submissions will lose 33% credit per day, with the submission window closing on the 3rd day following the deadline.
55
+ * Executed programs must display in a manner similar to provided output
56
+ * output formatted, where applicable, must match that of project requirements
57
+ * Processing must be correct based on input given and output requested
58
+ * Output, if applicable, must be correct based on values input
59
+ * Code must be nicely and consistently indented
60
+ * Code must be consistently written, to strive for readability from having a consistent style throughout
61
+ * Code must be commented
62
+ * Any "to be implemented" comments **MUST** be removed
63
+ * these "to be implemented" comments, if still present at evaluation time, will result in points being deducted.
64
+ * Sufficient comments explaining the point of provided logic **MUST** be present
65
+ * No global variables (without instructor approval), no goto statements, no calling of main()!
66
+ * Track/version the source code in your private semester repository
67
+ * Submit a copy of your source code to me using the **submit** tool by the deadline.
68
+
69
+### SUBMIT TOOL USAGE
70
+
71
+Let's say you have completed work on the project, and are ready to
72
+submit, you would do the following:
73
+
74
+```
75
+lab46:~/src/SEMESTER/unix/gtf0$ submit unix gtf0 gtf0.sh
76
+```
77
+
78
+You should get some sort of confirmation indicating successful submission
79
+if all went according to plan. If not, check for typos and or locational
80
+mismatches.
81
+
82
+### RUBRIC
83
+
84
+I'll be evaluating the project based on the following criteria:
85
+
86
+```
87
+286:gtf0:final tally of results (286/286)
88
+*:gtf0:script operates with no warnings or errors [26/26]
89
+*:gtf0:script produces sc compatible spreadsheet [26/26]
90
+*:gtf0:spreadsheet produce is conformant with gfoX submission criteria [26/26]
91
+*:gtf0:spreadsheet calculations are accurate based on week range [26/26]
92
+*:gtf0:script accepts and uses either a gfoX assignment or week number [26/26]
93
+*:gtf0:script uses variables, commandline args, if statements, and loops [52/52]
94
+*:gtf0:script uses regex, IO redirection, command expansion [52/52]
95
+*:gtf0:committed script to private semester repo [52/52]
96
+```
97
+
98
+Additionally:
99
+
100
+ * Solutions not abiding by spirit of project will be subject to a 50% overall deduction
101
+ * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
102
+ * Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
103
+ * Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction