Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » spring2017 » unix » projects » gfo0
haas:spring2017:unix:projects:gfo0

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
haas:spring2017:unix:projects:gfo0 [2017/03/17 21:28] – [Background] wedgehaas:spring2017:unix:projects:gfo0 [2017/03/18 13:32] (current) – [Submit] wedge
Line 33: Line 33:
 You'll recall from the syllabus that the grading policy for the class is divided into three areas: You'll recall from the syllabus that the grading policy for the class is divided into three areas:
  
-  * participation (your "presence", hopefully consistently of the mental variety, but I lower the bar so as not to overly ding anyone on an off day), which is worth a total of 28% of the final grade. +  * participation (your "presence", hopefully consistently of the mental variety, but I lower the bar so as not to overly ding anyone on an off day), which is worth a total of 13% of overall grade. 
-  * journal/blog/opus (your personal reflections / informational composition of your experience in the course, which some have already been reaping great value from), worth a total of 36% of the final grade. +  * journal (your personal reflections / informational composition of your experience in the course, which some have already been reaping great value from), worth a total of 13% of the overall grade. 
-  * projects (the assigned activities you've been enjoying each week), which rounds out the remaining 36% of your final grade.+    * in certain scenarios, you can earn bonus points by going above and beyond in your journal entries. Look for the "extra" attribute. This value gets added onto the journal total. 
 +  * projects (the assigned activities you've been enjoying each week), which rounds out the remaining 52% of your final grade.
     * the majority of reported bonus points are earned in relation to the projects, and are therefore applied exclusively to the projects component of your grade.     * the majority of reported bonus points are earned in relation to the projects, and are therefore applied exclusively to the projects component of your grade.
 +  * Added up, these three components come out to a value of 78. So at this point in the course, you will be calculating your grade out of that value.
 +  * Once there, you can determine the letter grade.
 +
 +Letter grades are on the following scale:
 +
 +  * A  (100.00+)
 +  * A- (94.00-99.99)
 +  * B+ (88.00-93.99)
 +  * B  (82.00-87.99)
 +  * B- (76.00-81.99)
 +  * C+ (70.00-75.99)
 +  * C  (64.00-69.99)
 +  * D  (58.00-63.99)
 +  * F  ( 0.00-57.99)
  
 Each component needs to be calculated separately to gain the total number of points, and then those points summed together to get your final result. Each component needs to be calculated separately to gain the total number of points, and then those points summed together to get your final result.
  
-Of course, we're not done yet, so new data is being added all the time (with each passing week, journal entry, and evaluated assignment), which means whatever value you may come up with today would potentially be obsolete come tomorrow.+Of course, we're not done yet, so new data is being added all the time (with each passing class, journal entry, and evaluated project), which means whatever value you may come up with today would potentially be obsolete come tomorrow.
  
 The algorithms and the process for determining your grade based on the available data, however, remain the same. The algorithms and the process for determining your grade based on the available data, however, remain the same.
Line 50: Line 65:
  
 ====Participation==== ====Participation====
-The participation data is in more of a binary representation (it is either there for a particular class day, or not; historically, I had 'X''s appear, but due to a logic bug in one of my scripts, it now just omits missed values-- same difference difficulty-wise, and doesn't impact the correctness of your data at all).+The participation data is in more of a binary representation (it is either there for a particular class day, or not; if not, 'X''s appear, growing from the right side). Due to a logic bug in one of my scripts, any 'X' values will NOT appear underneath the actual day missed. Instead, they will form up from the right end of this data.
  
 <code> <code>
     [UNIX] 019 021 026 028 033 035 040 042 054 056 061 063 068 070 075 077 082 084 096 098      [UNIX] 019 021 026 028 033 035 040 042 054 056 061 063 068 070 075 077 082 084 096 098 
-[username] 019 021 026 033 035 040 042 054 063 068 070 075 077 084 096 098+[username] 019 021 026 033 035 040 042 054 063 068 070 075 077 084 096 098  X   X   X   X
 </code> </code>
  
Line 60: Line 75:
  
 ====Journal==== ====Journal====
-The opus/blog/journal data is recorded, currently, in two categories per week:+The journal data is recorded, currently, in three categories per week, eligible to earn up to 8 points per weekly entry:
  
-  * did you make an **entry**, and is it in accordance with general posting criteria (I've been somewhat softer on the evaluation than the posted requirements otherwise indicate, but I do occasionally crack down on prolific abusers). +  * <nowiki>*:weekX:entry made before deadline [2/2]</nowiki> 
-  * is your entry **relevant**: is the content in some substantive way related to class, your journey into computing, etc. +    * was your entry in place by the time I ran my journal processing script? 
- +  * <nowiki>*:weekX:filler text removed from entry [2/2]</nowiki> 
-You won't be disqualified by incorporating prose, song lyrics, pictures of cats, etc., provided they enhance the necessary core content. If they are there as zero-avoidance filler. well... +    * there's some default text in each new entry that you remove for credit 
 +  * <nowiki>*:weekX:met minimal word count (262/256) [4/4]</nowiki> 
 +    * each entry must be at least 256 words to be counted for full credit
  
 Data can look something like this: Data can look something like this:
  
 <code> <code>
-    1:opus:week1entry +    8:week1:final tally of results (8/8) 
-    1:opus:week1relevant +    6:week2:final tally of results (6/8) 
-    0:opus:week2entry +    8:week3:final tally of results (8/8) 
-    0:opus:week2relevant +    8:week4:final tally of results (8/8) 
-    1:opus:week3entry +    5:week5:final tally of results (5/8) 
-    0:opus:week3relevant +    6:week6:final tally of results (6/8) 
-    1:opus:week4entry +    3:extra:final tally of results (3/0)
-    1:opus:week4relevant +
-    1:opus:week5entry +
-    0:opus:week5relevant +
-    1:opus:week6entry +
-    1:opus:week6relevant +
-    1:opus:week7entry +
-    0:opus:week7relevant +
-    0:opus:week8entry +
-    0:opus:week8relevant +
-    1:opus:week9entry +
-    1:opus:week9relevant+
 </code> </code>
  
Line 154: Line 160:
  
 <cli> <cli>
-lab46:~/src/unix/gfo0$ ./mygrade.sh +lab46:~/src/unix/gfo0$ ./gfo0.sh 
-===============================================================================+==================================================================================
 UNIX      uxi0 pbx0 cus0 pbx1 arc0 wpa0 udr0 sfp0 bns prjct+ptcpn+jrnal= result UNIX      uxi0 pbx0 cus0 pbx1 arc0 wpa0 udr0 sfp0 bns prjct+ptcpn+jrnal= result
-=============================================================================== +================================================================================== 
-username: 100  86   91   79   99   0    0    83   3   23/36+28/28+31/36= 82/100 +username: 100  86   91   79   99   0    0    83   3   41/52+11/13+12/13= 82/100 B 
-===============================================================================+==================================================================================
 lab46:~/src/unix/gfo0$  lab46:~/src/unix/gfo0$ 
 </cli> </cli>
Line 166: Line 172:
  
 And note that the actual scores are left justified underneath the column heading listing the project name. And note that the actual scores are left justified underneath the column heading listing the project name.
-====Bonus==== 
-As a bonus opportunity, I offer you the following: 
- 
-Despite how much automation I may have on the backend of things to generate all this data, there is still a considerable amount of manual interaction on my part (as much as I'd love to entirely script the process, evaluation still very much requires that human element), and that means there's always the chance of errors creeping in. 
- 
-I will consider for bonus points the implementation of a "check" argument, which if provided on your script's command-line, will perform necessary tallys and sanity checks (for example, if a project is out of 39 points, do all your values check out; similarly, do all the line-by-line point items add up to the reported total you have?), and nicely displays any inconsistencies (so that you can report them to me for potential correction). 
  
 =====Useful tools===== =====Useful tools=====
Line 224: Line 224:
  
 <cli> <cli>
-lab46:~/src/unix/gfo0$ submit unix gfo0 mygrade.sh+lab46:~/src/unix/gfo0$ submit unix gfo0 gfo0.sh
 Submitting unix project "gfo0": Submitting unix project "gfo0":
-    -> mygrade.sh(OK)+    -> gfo0.sh(OK)
  
 SUCCESSFULLY SUBMITTED SUCCESSFULLY SUBMITTED
 lab46:~/src/unix/gfo0$  lab46:~/src/unix/gfo0$ 
 </cli> </cli>
 +
 +Things I'll be looking for:
 +
 +<code>
 +78:gfo0:final tally of results (78/78)
 +*:gfo0:gfo0.sh submit via submit tool [1/1]
 +*:gfo0:gfo0.sh is well and consistently commented [4/4]
 +*:gfo0:gfo0.sh is well and consistently indented [4/4]
 +*:gfo0:gfo0.sh generates no errant output during run [4/4]
 +*:gfo0:gfo0.sh caches and references status output at run [13/13]
 +*:gfo0:gfo0.sh output matches project specifications [13/13]
 +*:gfo0:gfo0.sh generates results live through calculations [13/13]
 +*:gfo0:gfo0.sh has no line exceeding 80 characters in length [13/13]
 +*:gfo0:gfo0.sh is a fully automated script, no interaction [13/13]
 +</code>
haas/spring2017/unix/projects/gfo0.1489786107.txt.gz · Last modified: 2017/03/17 21:28 by wedge

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki