User Tools

Site Tools


haas:fall2017:cprog:projects:pnc0

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:fall2017:cprog:projects:pnc0 [2017/09/24 16:50] – [algorithm] wedgehaas:fall2017:cprog:projects:pnc0 [2017/10/15 20:51] (current) – [Evaluation Criteria] wedge
Line 3: Line 3:
 <WRAP><fs 150%>CSCS1320 C/C++ Programming</fs></WRAP> <WRAP><fs 150%>CSCS1320 C/C++ Programming</fs></WRAP>
 </WRAP> </WRAP>
- 
-~~TOC~~ 
  
 ======Project: ALGORITHMS - PRIME NUMBER CALCULATION (pnc0)====== ======Project: ALGORITHMS - PRIME NUMBER CALCULATION (pnc0)======
Line 105: Line 103:
     * and remember, the baseline brute force algorithm (**primereg**) may well identify a value as composite, but won't terminate the loop.     * and remember, the baseline brute force algorithm (**primereg**) may well identify a value as composite, but won't terminate the loop.
   * your timing should start before the loop (just AFTER argument processing), and terminate immediately following the terminating output newline outside the loops.   * your timing should start before the loop (just AFTER argument processing), and terminate immediately following the terminating output newline outside the loops.
-  * you may **NOT** split **qty** and **range** functionality into two separate code blocks (ie have two sets of two loops). Only the one set as indicated.  
  
 =====prime algorithm implementation===== =====prime algorithm implementation=====
Line 154: Line 151:
     * each program is to have no fewer and no more than 2 loops in this prime processing section.     * each program is to have no fewer and no more than 2 loops in this prime processing section.
   * display identified primes (space-separated) to **STDOUT**   * display identified primes (space-separated) to **STDOUT**
-  * stop your stopwatch immediately following your prime processing loops (and terminating newline display to **primelist**). Calculate the time that has transpired (ending time minus starting time).+  * stop your stopwatch immediately following your prime processing loops (and terminating newline display to **STDOUT**). Calculate the time that has transpired (ending time minus starting time).
   * output the processing run-time to **STDERR**   * output the processing run-time to **STDERR**
   * your output **MUST** conform to the example output in the **execution** section below. This is also a test to see how well you can implement to specifications. Basically:   * your output **MUST** conform to the example output in the **execution** section below. This is also a test to see how well you can implement to specifications. Basically:
Line 689: Line 686:
  
 <code> <code>
-39:pnc0:final tally of results (39/39)+78:pnc0:final tally of results (78/78)
 </code> </code>
  
Line 695: Line 692:
  
 <code> <code>
-*:pnc0:primeALGO.c compiles cleanly, no compiler messages [3/3+*:pnc0:primeALGO.c compiles cleanly, no compiler messages [9/9
-*:pnc0:primeALGO.c implements only specified algorithm [6/6+*:pnc0:primeALGO.c implements only specified algorithm [11/11
-*:pnc0:primeALGO.c consistent indentation throughout code [3/3+*:pnc0:primeALGO.c consistent indentation throughout code [9/9
-*:pnc0:primeALGO.c relevant comments throughout code [3/3+*:pnc0:primeALGO.c relevant comments throughout code [9/9
-*:pnc0:primeALGO.c code conforms to project specifications [3/3+*:pnc0:primeALGO.c code conforms to project specifications [9/9
-*:pnc0:primeALGO.c runtime output conforms to specifications [4/4+*:pnc0:primeALGO.c runtime output conforms to specifications [6/6
-*:pnc0:primeALGO.c make checkqty test times within reason [2/2+*:pnc0:primeALGO.c make checkqty test times within reason [6/6
-*:pnc0:primeALGO.c make checkrange test times within reason [2/2]+*:pnc0:primeALGO.c make checkrange test times within reason [6/6]
 *:pnc0:primeALGO.c make verifyall tests succeed [13/13] *:pnc0:primeALGO.c make verifyall tests succeed [13/13]
 </code> </code>
  
 As the optimizations improve upon others, some evaluations will be based upon differences between a baseline (in some cases, primereg) and the optimization. As the optimizations improve upon others, some evaluations will be based upon differences between a baseline (in some cases, primereg) and the optimization.
haas/fall2017/cprog/projects/pnc0.1506271857.txt.gz · Last modified: 2017/09/24 16:50 by wedge