User Tools

Site Tools


haas:fall2020:cprog:projects:cnv1

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:cprog:projects:cnv1 [2020/10/08 14:58] – [Reference] wedgehaas:fall2020:cprog:projects:cnv1 [2020/10/15 12:49] (current) – [Determining factor pairs] wedge
Line 89: Line 89:
  
 Because there are 3 factor pairs, 12 would be considered an nary(3) value (or a tertiary number). Because there are 3 factor pairs, 12 would be considered an nary(3) value (or a tertiary number).
 +
 +====Command-line arguments====
 +{{page>haas:fall2020:common:projects:commandlineargs&noheader}}
  
 =====grabit===== =====grabit=====
Line 165: Line 168:
  
  
-=====Reference===== 
-Copied as part of the grabit, inside your **cnv1/** subdirectory, will be a copy of my implementation (in executable form, by the name **ref_cnv1**), which abides by the project specifications. Please compare its output against that of your implementation. You can invoke the reference implementation by running the following: 
- 
-<cli> 
-yourpi:~/src/cprog/cnv1$ make check 
-Enter a number: 6 
-6 is a secondary number 
-yourpi:~/src/cprog/cnv1$  
-</cli> 
- 
-=====Verification===== 
-In addition, I have also placed a **cnv1verify** script in that same subdirectory, which will test your program against a range of values, to determine overall correctness. You can run the verify script using the Makefile, as follows: 
- 
-<cli> 
-yourpi:~/src/cprog/cnv1$ make verify 
-</cli> 
  
 =====Reference===== =====Reference=====
Line 194: Line 181:
 </cli> </cli>
 =====Verification===== =====Verification=====
-In addition, I have also placed a **cnv0verify** script in that same subdirectory, which will test your program against a range of values, to determine overall correctness.+In addition, I have also placed a **cnv1verify** script in that same subdirectory, which will test your program against a range of values, to determine overall correctness. You can run it by doing a "make verify":
  
 <cli> <cli>
-lab46:~/src/cprog/cnv0/var/public/spring2020/cprog/cnv0/cnv0verify+yourpi:~/src/cprog/cnv1make verify
 ERROR CHECK ERROR CHECK
 ================= =================
Line 247: Line 234:
    need: >36 <    need: >36 <
  
-lab46:~/src/cprog/cnv0+yourpi:~/src/cprog/cnv1
 </cli> </cli>
  
Line 265: Line 252:
  
 <cli> <cli>
-$ submit cprog cnv0 cnv0.c +lab46:~/src/cprog/cnv1make submit
-Submitting cprog project "cnv0": +
-    -> cnv0.c(OK) +
- +
-SUCCESSFULLY SUBMITTED+
 </cli> </cli>
 +
 +And make sure you get no error messages.
  
 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.
Line 277: Line 262:
  
 <code> <code>
-78:cnv0:final tally of results (78/78+91:cnv1:final tally of results (91/91
-*:cnv0:proper error checking and status reporting performed [13/13] +*:cnv1:resources obtained via grabit by Sunday before deadline [13/13] 
-*:cnv0:correct variable types and name lengths used [13/13] +*:cnv1:proper error checking and status reporting performed [13/13] 
-*:cnv0:proper output formatting per specifications [13/13] +*:cnv1:correct variable types and name lengths used [13/13] 
-*:cnv0:runtime tests of submitted program succeed [13/13] +*:cnv1:proper output formatting per specifications [13/13] 
-*:cnv0:no negative compiler messages for program [13/13] +*:cnv1:runtime tests of submitted program succeed [13/13] 
-*:cnv0:code is pushed to lab46 repository [13/13]+*:cnv1:no negative compiler messages for program [13/13] 
 +*:cnv1:code is pushed to lab46 repository [13/13]
 </code> </code>
  
haas/fall2020/cprog/projects/cnv1.1602169084.txt.gz · Last modified: 2020/10/08 14:58 by wedge