User Tools

Site Tools


haas:fall2020:discrete:projects:bdt2

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:fall2020:discrete:projects:bdt2 [2020/09/29 22:03] – [Access variables in your C program] wedgehaas:fall2020:discrete:projects:bdt2 [2020/09/30 16:35] (current) – [Implementation Restrictions] wedge
Line 63: Line 63:
     * **justification** implies some thoughtful why/how style comments explaining how a particular use of one of these statements is effective and efficient (not: "I couldn't think of any other way to do it").     * **justification** implies some thoughtful why/how style comments explaining how a particular use of one of these statements is effective and efficient (not: "I couldn't think of any other way to do it").
   * absolutely **NO** infinite loops (**while(1)** or the like).   * absolutely **NO** infinite loops (**while(1)** or the like).
 +  * ALL variables must be well and pertinently named, and be no fewer than 4 symbols in length
   * no forced redirection of the flow of the process (no seeking to the end of the file to grab a max size only to zip back somewhere else: deal with the data in as you are naturally encountering it; no telling; no "ungetting" data back into the file).   * no forced redirection of the flow of the process (no seeking to the end of the file to grab a max size only to zip back somewhere else: deal with the data in as you are naturally encountering it; no telling; no "ungetting" data back into the file).
   * All "arrays" must be declared and referenced using ONLY pointer notation, NO square brackets.   * All "arrays" must be declared and referenced using ONLY pointer notation, NO square brackets.
Line 166: Line 167:
  
 You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches. You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.
 +
 +What I will be looking for:
  
 <code> <code>
-182:bdt2:final tally of results (182/182)+195:bdt2:final tally of results (195/195)
 *:bdt2:bdt2.c compiles cleanly, no compiler messages [13/13] *:bdt2:bdt2.c compiles cleanly, no compiler messages [13/13]
 *:bdt2:bdt2.c implements only specified algorithm [26/26] *:bdt2:bdt2.c implements only specified algorithm [26/26]
Line 177: Line 180:
 *:bdt2:bdt2 runtime output conforms to reference [26/26] *:bdt2:bdt2 runtime output conforms to reference [26/26]
 *:bdt2:bdt2 runtime output matches reference [26/26] *:bdt2:bdt2 runtime output matches reference [26/26]
-*:bdt2:bdt2 committed, pushed to lab46 repository [13/13]+*:bdt2:bdt2 committed, pushed to lab46 repository [26/26]
 </code> </code>
 +
 +Additionally:
 +  * Solutions not abiding by spirit of project will be subject to a 25% overall deduction
 +  * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
 +  * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction
 +  * Solutions not organized and easy to read are subject to a 25% overall deduction
haas/fall2020/discrete/projects/bdt2.1601417013.txt.gz · Last modified: 2020/09/29 22:03 by wedge