User Tools

Site Tools


haas:fall2020:discrete:projects:pnc1

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:pnc1 [2020/09/15 14:24] – [Objective] wedgehaas:fall2020:discrete:projects:pnc1 [2020/10/11 13:27] (current) – [Evaluation Criteria] wedge
Line 19: Line 19:
 =====Objective===== =====Objective=====
 To continue our exploration of algorithms and optimizations applied to them, through further work on the prime number computation programs started in pnc0. To continue our exploration of algorithms and optimizations applied to them, through further work on the prime number computation programs started in pnc0.
 +
 =====Background===== =====Background=====
 In mathematics, a **prime** number is a value that is only evenly divisible by 1 and itself; it has just that one pair of factors, no others. Numbers that have divisibility/factors are classified as **composite** numbers. In mathematics, a **prime** number is a value that is only evenly divisible by 1 and itself; it has just that one pair of factors, no others. Numbers that have divisibility/factors are classified as **composite** numbers.
Line 347: Line 348:
  
   * **make**: compile everything   * **make**: compile everything
-    * any **warnings** or **errors** generated by the compiler will go into a file in the base directory of pnc0 in a file called **errors**; you can **cat** it to view the information.+    * any **warnings** or **errors** generated by the compiler will go into a file in the base directory of the project in a file called **errors**; you can **cat** it to view the information.
   * **make debug**: compile everything with debug support   * **make debug**: compile everything with debug support
     * any **warnings** or **errors** generated by the compiler will be displayed to the screen as the programs compile.     * any **warnings** or **errors** generated by the compiler will be displayed to the screen as the programs compile.
Line 397: Line 398:
  
 <cli> <cli>
-lab46:~/src/discrete/pnc0$ ./primereg 128 1 2 2048+lab46:~/src/discrete/pnc1$ ./primereg 128 1 2 2048
 </cli> </cli>
  
Line 613: Line 614:
  
 <cli> <cli>
-lab46:~/src/discrete/pnc0$ ./primereg 24 1+lab46:~/src/discrete/pnc1$ ./primereg 24 1
 2 3 5 7 11 13 17 19 23 29 31 37 41 43 47 53 59 61 67 71 73 79 83 89  2 3 5 7 11 13 17 19 23 29 31 37 41 43 47 53 59 61 67 71 73 79 83 89 
   0.0001   0.0001
-lab46:~/src/discrete/pnc0+lab46:~/src/discrete/pnc1
 </cli> </cli>
  
Line 625: Line 626:
  
 <cli> <cli>
-lab46:~/src/discrete/pnc0$ ./primerego 32 1 0+lab46:~/src/discrete/pnc1$ ./primerego 32 1 0
 ./primerego: invalid lower bound ./primerego: invalid lower bound
-lab46:~/src/discrete/pnc0+lab46:~/src/discrete/pnc1
 </cli> </cli>
  
Line 636: Line 637:
  
 <cli> <cli>
-lab46:~/src/discrete/pnc0$ ./primeregs 128 1 7 23+lab46:~/src/discrete/pnc1$ ./primeregs 128 1 7 23
 7 11 13 17 19 23 7 11 13 17 19 23
   0.0001   0.0001
-lab46:~/src/discrete/pnc0+lab46:~/src/discrete/pnc1
 </cli> </cli>
  
Line 647: Line 648:
 If you'd like to compare your implementations, I rigged up a Makefile checking rule called "**make checkqty**" and "**make checkrange**" which you can run to get a nice side-by-side runtime comparisons of your implementations. If you'd like to compare your implementations, I rigged up a Makefile checking rule called "**make checkqty**" and "**make checkrange**" which you can run to get a nice side-by-side runtime comparisons of your implementations.
  
-In order to work, you **MUST** be in the directory where your pnc0 binaries reside, and must be named as such (which occurs if you ran **make** to compile them).+In order to work, you **MUST** be in the directory where your pnc1 binaries reside, and must be named as such (which occurs if you ran **make** to compile them).
  
 ====check qty==== ====check qty====
-For instance (running on my implementation of the pnc0 programs, some output omitted to keep the surprise alive):+For instance (running on my implementation of the pnc1 programs, some output omitted to keep the surprise alive):
  
 <cli> <cli>
Line 793: Line 794:
 *:pnc1:primeALGO.c relevant comments throughout code [1/1] *:pnc1:primeALGO.c relevant comments throughout code [1/1]
 *:pnc1:primeALGO.c code conforms to project specifications [2/2] *:pnc1:primeALGO.c code conforms to project specifications [2/2]
-*:pnc1:primeALGO.c runtime output conforms to specifications [1/1]+*:pnc1:primeALGO.c runtime output conforms to specifications [4/4]
 *:pnc1:primeALGO.c make checkqty test times within reason [1/1] *:pnc1:primeALGO.c make checkqty test times within reason [1/1]
 *:pnc1:primeALGO.c make checkrange test times within reason [1/1] *:pnc1:primeALGO.c make checkrange test times within reason [1/1]
-*:pnc1:primeALGO.c make verifyall tests succeed [3/3] 
 </code> </code>
  
haas/fall2020/discrete/projects/pnc1.1600179877.txt.gz · Last modified: 2020/09/15 14:24 by wedge