User Tools

Site Tools


haas:spring2017:cprog:projects:mbe0

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:spring2017:cprog:projects:mbe0 [2017/02/07 21:52] – [STDOUT verification of answer] wedgehaas:spring2017:cprog:projects:mbe0 [2017/02/15 15:42] (current) – [Total output comparison] wedge
Line 8: Line 8:
 ======Project: MENTAL MATH - MULTIPLY BY 11 (mbe0)====== ======Project: MENTAL MATH - MULTIPLY BY 11 (mbe0)======
  
 +=====Errata=====
 +
 +  * Added verification section to facilitate project output specification compliance (20170207)
 +  * Added automatic verification subsection to verification section (20170208)
 =====Objective===== =====Objective=====
 To implement a programmatic solution (ie simulation) of a real life process- the mental math trick of multiplying any two- or three-digit number by eleven. To implement a programmatic solution (ie simulation) of a real life process- the mental math trick of multiplying any two- or three-digit number by eleven.
Line 356: Line 360:
  
 You can repeat this for the other data files (output.73 for an input of 73, etc.) You can repeat this for the other data files (output.73 for an input of 73, etc.)
 +
 +===Isolate just the STDOUT or the STDERR===
 +Additionally, you may want to specifically look at your program's STDOUT or STDERR independent of each other.
 +
 +To do this, you can do the following.
 +
 +To isolate STDOUT and STDERR into separate files, you can do the following:
 +
 +<cli>
 +lab46:~/src/cprog/mbe0$ ./mbe0 <<< 37 1>stdout.37 2>stderr.37
 +lab46:~/src/cprog/mbe0$ 
 +</cli>
 +
 +You can then compare those particular collections of information against my copies (located in the **mbe0** subdirectory of the CPROG Public Directory, by the same file names).
 +====automated verification====
 +I have rigged up **pchk** to work for this project; it will check for differences and compare MD5sum hashes for stderr, stdout, and total (combined) output.
 +
 +Once you have everything complete, this is a good final check to do to ensure everything is in order.
 +
 +<cli>
 +lab46:~/src/cprog/mbe0$ pchk cprog mbe0
 +===================================================
 +=          mbe0 output validation check           =
 +===================================================
 +      stderr diff: MATCH    stderr md5sum: MATCH
 +[ 37] stdout diff: MATCH    stdout md5sum: MATCH
 +      output diff: MATCH    output md5sum: MATCH
 +
 +      stderr diff: MATCH    stderr md5sum: MATCH
 +[ 73] stdout diff: MATCH    stdout md5sum: MATCH
 +      output diff: MATCH    output md5sum: MATCH
 +
 +      stderr diff: MATCH    stderr md5sum: MATCH
 +[128] stdout diff: MATCH    stdout md5sum: MATCH
 +      output diff: MATCH    output md5sum: MATCH
 +
 +      stderr diff: MATCH    stderr md5sum: MATCH
 +[480] stdout diff: MATCH    stdout md5sum: MATCH
 +      output diff: MATCH    output md5sum: MATCH
 +
 +      stderr diff: MATCH    stderr md5sum: MATCH
 +[907] stdout diff: MATCH    stdout md5sum: MATCH
 +      output diff: MATCH    output md5sum: MATCH
 +
 +      stderr diff: MATCH    stderr md5sum: MATCH
 +[933] stdout diff: MATCH    stdout md5sum: MATCH
 +      output diff: MATCH    output md5sum: MATCH
 +===================================================
 +=     matches: 36, mismatches:  0, total: 36      =
 +===================================================
 +lab46:~/src/cprog/mbe0$ 
 +</cli>
 +
 +Since your project submission will be evaluated in part by compliance to output specifications, you probably want to check to see how you are doing before submitting.
 =====Reflection===== =====Reflection=====
 Be sure to provide any commentary on your journal regarding realizations had and discoveries made during your pursuit of this project. Be sure to provide any commentary on your journal regarding realizations had and discoveries made during your pursuit of this project.
Line 367: Line 425:
  
   * Code must compile cleanly (no warnings or errors)   * Code must compile cleanly (no warnings or errors)
 +    * Again, I will be compiling as follows: gcc -Wall -o mbe0 mbe0.c
   * Submit the program in a file called **mbe0.c**   * Submit the program in a file called **mbe0.c**
   * Output must be correct, and match the form given in the sample output above.   * Output must be correct, and match the form given in the sample output above.
haas/spring2017/cprog/projects/mbe0.1486504331.txt.gz · Last modified: 2017/02/07 21:52 by wedge