User Tools

Site Tools


haas:fall2020:discrete:projects:dcf2

Differences

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

Link to this comparison view

Next revision
Previous revision
haas:fall2020:discrete:projects:dcf2 [2019/10/21 11:48] – external edit 127.0.0.1haas:fall2020:discrete:projects:dcf2 [2020/09/30 16:36] (current) – [Other specification details] wedge
Line 122: Line 122:
   * end of file bytes should no longer be tricky in v3, simply treat them as unencoded data   * end of file bytes should no longer be tricky in v3, simply treat them as unencoded data
   * your program should be mindful of data reads/writes that may hit the end of file marker   * your program should be mindful of data reads/writes that may hit the end of file marker
 +  * ALL variables must be well and pertinently named, and be no fewer than 4 symbols in length
   * your program also should avoid writing the EOF byte as a data byte (or reading it and processing it as anything other than a marker to stop reading).   * your program also should avoid writing the EOF byte as a data byte (or reading it and processing it as anything other than a marker to stop reading).
   * Since we are using single bytes to store our counts, one needs to be mindful not to allow the byte value to "roll over"; limit your counts to 255.   * Since we are using single bytes to store our counts, one needs to be mindful not to allow the byte value to "roll over"; limit your counts to 255.
Line 250: Line 251:
 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:
  
 +<cli>
 +234:dcf2:final tally of results (234/234)
 +*:dcf2:encode.c compiles cleanly, no compiler messages [13/13]
 +*:dcf2:encode.c consistent indentation throughout code [13/13]
 +*:dcf2:encode.c relevant how and why comments in code [13/13]
 +*:dcf2:encode.c implementation flexible, not hardcoded [13/13]
 +*:dcf2:encode.c implementation free from restrictions [13/13]
 +*:dcf2:encode.c conforms to project specifications [13/13]
 +*:dcf2:encode runtime output conforms to specifications [13/13]
 +*:dcf2:encode verification tests succeed [13/13]
 +*:dcf2:decode.c compiles cleanly, no compiler messages [13/13]
 +*:dcf2:decode.c consistent indentation throughout code [13/13]
 +*:dcf2:decode.c relevant how and why comments in code [13/13]
 +*:dcf2:decode.c implementation flexible, not hardcoded [13/13]
 +*:dcf2:decode.c implementation free from restrictions [13/13]
 +*:dcf2:decode.c conforms to project specifications [13/13]
 +*:dcf2:decode runtime output conforms to specifications [13/13]
 +*:dcf2:decode verification tests succeed [13/13]
 +*:dcf2:project committed and pushed to lab46 repository [26/26]
 +</cli>
 +
 +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/dcf2.1571658481.txt.gz · Last modified: 2019/10/21 11:48 by 127.0.0.1