This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
haas:spring2015:cprog:projects:mbe1 [2015/02/06 17:56] – [arrays] wedge | haas:spring2015:cprog:projects:mbe1 [2015/02/07 13:31] (current) – wedge | ||
---|---|---|---|
Line 6: | Line 6: | ||
~~TOC~~ | ~~TOC~~ | ||
- | ======Project: | + | ======Project: |
=====Objective===== | =====Objective===== | ||
Line 209: | Line 209: | ||
====Using loops and arrays together for universal harmony==== | ====Using loops and arrays together for universal harmony==== | ||
- | . | + | To really make the most out of arrays in scaling our algorithms, using them in conjunction with loops gives us the most bang for our buck. The advantage |
- | ====Multiplying any single digit number by 11==== | + | |
- | This may be a pattern | + | |
- | In the case of 1 x 11, we get: 11 | + | ===42 everywhere=== |
- | For 2 x 11, we see: 22 | + | To illustrate, here we will declare an 11 element array (called **data**), and fill each element with the value 42 using a for loop: |
- | For 3 x 11, we have: 33 | + | <code c> |
+ | int data[11], position = 0; | ||
- | and this trick works all the way through 9 x 11, yielding: 99 | + | for(position |
- | + | { | |
- | ====Multiplying any double digit number by 11==== | + | |
- | Here we do a pivot and then perform simple arithmetic to obtain the middle value. | + | } |
- | + | ||
- | In the case of 10 x 11, we take 10 and pivot it, getting | + | |
- | + | ||
- | To get the middle value, we add these two values together: 1+0=1 | + | |
- | + | ||
- | So, the result of 10 x 11 is: 1 (1+0) 0 | + | |
- | or: 110 | + | |
- | + | ||
- | Let's try it with 32 x 11: | + | |
- | + | ||
- | < | + | |
- | 32 x 11 = 3 (3+2) 2 | + | |
- | = 3 5 2 | + | |
- | = 352 | + | |
</ | </ | ||
- | This is almost the entire process, but there' | + | ===Display array contents=== |
+ | What if we wanted | ||
- | For example, let us take the maximum two digit value (99): | + | Important considerations: |
+ | * again, with C, being true to how the computer actually works, we can only access the array one element at a time | ||
+ | * because we know array indices start at 0, we have a known starting point | ||
+ | * because we know how big our array is (11 elements, from previous example), we know how many elements to go for | ||
+ | * each element is located one after the other-- 0 is followed by 1 is followed by 2 etc. | ||
- | Using this process as it has been described thus far, we would (incorrectly) get: | + | ... therefore, we have all the ingredients for a **for** loop: |
- | < | + | < |
- | 99 x 11 = 9 (9 + 9) 9 | + | for (position = 0; position < 11; position++) |
- | = 9 18 9 | + | { |
- | = 9189 | + | |
+ | } | ||
+ | fprintf(stdout, | ||
</ | </ | ||
- | But that would be incorrect mathematically. | + | This should result in the following program output: |
- | To compensate (or, to present the full rules for the trick), we take the sum of this result as the middle digit, and apply the carry to the next digit to the left, so: | + | < |
+ | 42 42 42 42 42 42 42 42 42 42 42 | ||
+ | </ | ||
- | < | + | ===Backwards? |
- | 99 x 11 = 9 (9+9) 9 | + | What if we wanted to display the contents of our array in reverse |
- | | + | |
- | = 10 8 9 | + | |
- | = 1089 | + | |
- | </ | + | |
- | And we now have the correct result. | + | We'd still want to use a loop, but look at how we structure it: |
- | As another example, let us look at 47 x 11: | + | < |
- | + | for (position = 10; position >= 0; position--) | |
- | < | + | { |
- | 47 x 11 = 4 (4+7) 7 | + | fprintf(stdout, "%d ", data[position]); |
- | | + | } |
- | = 5 | + | fprintf(stdout, |
- | = 517 | + | |
</ | </ | ||
- | Got it? Try it with some other examples. | + | Notice how the loop-terminating relational statements differ (comparing the two-- for forward and backward, does it make sense?), and also how we progress between individual elements (in one we are incrementing, |
- | ===sum vs. carry=== | + | That should make sense before |
- | In grade school, when learning to do arithmetic by hand (you still are taught how to do arithmetic by hand, right?), we first learned the concept of sum and carry. This bore value as we were applying this to place values of the number. | + | |
- | Little did you know then, but you were learning the basics of effective numerical and logical problem solving within the domain of Computer Science in grade school! | + | ===Thinking with arrays=== |
+ | Using arrays in your algorithms represents a potential barrier | ||
- | For example, in the case of the number 18, when dissecting | + | Now, with arrays, we have one common name, distinguishable by its element offset. That has been known to cause some conceptual problems due to the mildly abstract nature it creates. It would certainly not hurt to draw some pictures and manually work through some examples, step-by-step... it may be confusing at first, but the more you play with it, ask questions, play, read, etc., the sooner things will start to click. |
- | | + | As some of you have started to realize with **mbe0**, the actual core work of the project wasn't actually that hard, once you saw through the illusion of complexity we had placed in front of it. By using arrays, we can make our solutions even easier (and code even simpler)... but, we will initially have to eliminate self-imposed mental obstacles making the problem appear significantly more difficult than it actually is. |
- | | + | |
- | In single digit terminology, | ||
- | < | + | ====Multiplying a number (of varying digits) by 11==== |
- | 1 <-- carry (to be added to 10s position) | + | In **mbe0**, we specifically looked at 3 usage cases for our mental math problem: |
- | 9 | + | |
- | + 9 | + | |
- | ---- | + | |
- | | + | |
- | </ | + | |
- | See what is happening here? The basis for adding multiple-digit | + | Now that we have those down, we can now apply arrays and loops to optimize and enhance a solution, and to allow it to scale to a wider range of possibilities (why limit ourselves to just 1-, 2-, and 3-digit |
- | < | + | ===3-digits |
- | 1 <-- carry (to be added to 10s position) | + | Again, to review, let's look at a 3-digit example. 123 x 11: |
- | 09 | + | |
- | +09 | + | |
- | ---- | + | |
- | | + | |
- | + | ||
- | </ | + | |
- | Then we have the follow-up addition to determine the value of the 10s place: | + | |
< | < | ||
- | | + | 123 x 11 = 1 |
- | 0 | + | |
- | +0 | + | = 1 |
- | -- | + | |
- | 1 <-- sum (of 10s position) | + | |
- | </ | + | |
- | + | ||
- | and we would technically have a resulting carry of 0 (but adding zero to any values gives us the value itself-- the so-called **additive identity property** we learned in math class). | + | |
- | + | ||
- | Once we are all said and done, we concatenate the tens and ones places together: | + | |
- | + | ||
- | 1 (ten) and 8 (ones): 18 | + | |
- | + | ||
- | ====Multiplying any three-digit number by 11==== | + | |
- | In this case we merely extend the pattern from double digits, rippling through a series of comparing each set of two consecutive digits. | + | |
- | + | ||
- | Let's look at 123 x 11: | + | |
- | + | ||
- | < | + | |
- | 123 x 11 = 1 (1 + 2) (2 + 3) 3 | + | |
- | = 1 3 | + | |
= 1353 | = 1353 | ||
</ | </ | ||
Line 338: | Line 295: | ||
< | < | ||
567 x 11 = 5 (5 + 6) (6 + 7) 7 | 567 x 11 = 5 (5 + 6) (6 + 7) 7 | ||
- | = (5 + 1) (1 + 1) 3 7 | + | = (5)+1 |
= 6 | = 6 | ||
= 6237 | = 6237 | ||
Line 352: | Line 309: | ||
A dual benefit of this project is that in addition to extending your programming experience / understanding of C, you could develop this as a mental ability (that is where it originated), | A dual benefit of this project is that in addition to extending your programming experience / understanding of C, you could develop this as a mental ability (that is where it originated), | ||
+ | ===4-digits=== | ||
+ | Now let us process a 4-digit example (look for similarities to the 3-digit process, specifically how this is merely an expansion, or an additional step-- due to the additional digit): | ||
+ | |||
+ | 4567 x 11: | ||
+ | |||
+ | < | ||
+ | 4567 x 11 = 4 (4 + 5) (5 + 6) (6 + 7) 7 | ||
+ | = (4)+1 | ||
+ | = 5 | ||
+ | = 50237 | ||
+ | </ | ||
+ | |||
+ | Remember, we are processing this from right to left (so that the carry values can properly propagate). While there is no initial carry coming in, we'll add one anyway (0), so we see 13+0 (which is simply 13)... but because we're interested in place values, this is actually a sum of 3, carry of 1... and that one gets sent over to the next place (which has an 11)... so 11+1 will be 12, or sum of 2, carry 1... that carry will propagate to the next position to the left (the 9)... so there' | ||
+ | |||
+ | Can you see how "the same" this process for 4-digit numbers is when comparing to the process for 3-digit numbers? And how the same comparison can be made for 2-digit, and 5-digit, 6-digit, etc.? Please take some time, working through some examples (by hand) to identify and notice the pattern, or essence, of this process. You need to see how it doesn' | ||
+ | |||
+ | That " | ||
+ | |||
+ | (Also, the potential exception here would possibly be 1-digit values... if you cannot easily find a way to make 1-digit numbers work with greater-than-1-digit numbers, that's where an if-statement would come into play-- if 1-digit, do this specific process, else do the regular process). I'm not saying one universal solution isn't possible, but at this stage of your structured programming development, | ||
=====Program===== | =====Program===== | ||
- | It is your task to write the program that will use the above method | + | It is your task to write an optimized version of your multiply by eleven |
Your program should: | Your program should: | ||
* obtain its input from STDIN. | * obtain its input from STDIN. | ||
* input should be in the form of a single integer value | * input should be in the form of a single integer value | ||
- | * determine | + | * determine the number |
* perform the correct algorithm against the input | * perform the correct algorithm against the input | ||
* propagate any carries | * propagate any carries | ||
- | * output | + | * use an array (**digit**) to store individual digits from the number input |
- | * you can display each digit individually, | + | * use another array (**result**) to store the digits of the result number, following manipulations |
+ | * hint: you will want to make the **result** array one element larger. Why is this? | ||
+ | * Display output showing aspects of the process | ||
+ | * output the final value (by iterating through the array, displaying one value at a time) | ||
=====Execution===== | =====Execution===== | ||
Line 373: | Line 352: | ||
Enter value: 31415926 | Enter value: 31415926 | ||
Digits detected: 8 | Digits detected: 8 | ||
- | result[0] = 6 | + | |
- | result[1] = | + | Obtaining unique digits, storing in array... |
+ | digit[0] = 6 | ||
+ | digit[1] = 2 | ||
+ | digit[2] = 9 | ||
+ | digit[3] = 5 | ||
+ | digit[4] = 1 | ||
+ | digit[5] = 4 | ||
+ | digit[6] = 1 | ||
+ | digit[7] = 3 | ||
+ | |||
+ | Applying process... | ||
+ | result[0] = 6 + 0 + 0 (sum of 6, carry out of 0) | ||
+ | result[1] = 2 + 6 + 0 (sum of 8, carry out of 0) | ||
+ | result[2] = 9 + 2 + 0 (sum of 1, carry out of 1) | ||
+ | result[3] = 5 + 9 + 1 (sum of 5, carry out of 1) | ||
+ | result[4] = 1 + 5 + 1 (sum of 7, carry out of 0) | ||
+ | result[5] = 4 + 1 + 0 (sum of 5, carry out of 0) | ||
+ | result[6] = 1 + 4 + 0 (sum of 5, carry out of 0) | ||
+ | result[7] = 3 + 1 + 0 (sum of 4, carry out of 0) | ||
+ | result[8] = 3 + 0 + 0 (sum of 3, carry out of 0) | ||
+ | |||
+ | Displaying result... | ||
31415926 x 11 = 345575186 | 31415926 x 11 = 345575186 | ||
lab46: | lab46: | ||
Line 384: | Line 384: | ||
lab46: | lab46: | ||
Enter value: 7104 | Enter value: 7104 | ||
+ | Digits detected: 4 | ||
+ | |||
+ | Obtaining unique digits, storing in array... | ||
+ | digit[0] = 4 | ||
+ | digit[1] = 0 | ||
+ | digit[2] = 1 | ||
+ | digit[3] = 7 | ||
+ | |||
+ | Applying process... | ||
+ | result[0] = 4 + 0 + 0 (sum of 4, carry out of 0) | ||
+ | result[1] = 0 + 4 + 0 (sum of 4, carry out of 0) | ||
+ | result[2] = 1 + 0 + 0 (sum of 1, carry out of 0) | ||
+ | result[3] = 7 + 1 + 0 (sum of 8, carry out of 0) | ||
+ | result[4] = 7 + 0 + 0 (sum of 7, carry out of 0) | ||
+ | |||
+ | Displaying result... | ||
7104 x 11 = 78144 | 7104 x 11 = 78144 | ||
lab46: | lab46: | ||
Line 393: | Line 409: | ||
lab46: | lab46: | ||
Enter value: 56789 | Enter value: 56789 | ||
+ | Digits detected: 5 | ||
+ | |||
+ | Obtaining unique digits, storing in array... | ||
+ | digit[0] = 9 | ||
+ | digit[1] = 8 | ||
+ | digit[2] = 7 | ||
+ | digit[3] = 6 | ||
+ | digit[4] = 5 | ||
+ | |||
+ | Applying process... | ||
+ | result[0] = 9 + 0 + 0 (sum of 9, carry out of 0) | ||
+ | result[1] = 8 + 9 + 0 (sum of 7, carry out of 1) | ||
+ | result[2] = 7 + 8 + 1 (sum of 6, carry out of 1) | ||
+ | result[3] = 6 + 7 + 1 (sum of 4, carry out of 1) | ||
+ | result[4] = 5 + 6 + 1 (sum of 2, carry out of 1) | ||
+ | result[5] = 5 + 1 + 0 (sum of 6, carry out of 0) | ||
+ | |||
+ | Displaying result... | ||
56789 x 11 = 624679 | 56789 x 11 = 624679 | ||
lab46: | lab46: | ||
Line 398: | Line 432: | ||
The execution of the program is short and simple- obtain the input, do the processing, produce the output, and then terminate. | The execution of the program is short and simple- obtain the input, do the processing, produce the output, and then terminate. | ||
- | =====Reflection===== | ||
- | Be sure to provide any commentary on your opus regarding realizations had and discoveries made during your pursuit of this project. | ||
- | |||
- | * Does this process work for four digit numbers? | ||
- | * How about five digit numbers? | ||
- | * Do you see a pattern for now this trick could be extended? | ||
=====Submission===== | =====Submission===== | ||
Line 409: | Line 437: | ||
* Code must compile cleanly (no warnings or errors) | * Code must compile cleanly (no warnings or errors) | ||
- | * Output must be correct, and match the form given in the sample output above. | + | * Output must be correct, and resemble |
* Code must be nicely and consistently indented (you may use the **indent** tool) | * Code must be nicely and consistently indented (you may use the **indent** tool) | ||
* Code must utilize the algorithm presented above | * Code must utilize the algorithm presented above | ||
Line 415: | Line 443: | ||
* have a properly filled-out comment banner at the top | * have a properly filled-out comment banner at the top | ||
* have at least 20% of your program consist of **< | * have at least 20% of your program consist of **< | ||
- | * Output Formatting (including spacing) of program must conform to the provided output (see above). | ||
* Track/ | * Track/ | ||
* Submit a copy of your source code to me using the **submit** tool. | * Submit a copy of your source code to me using the **submit** tool. | ||
Line 422: | Line 449: | ||
<cli> | <cli> | ||
- | $ submit cprog mbe1 multby11v2.c | + | $ submit cprog mbe1 mbe1.c |
Submitting cprog project " | Submitting cprog project " | ||
- | -> multby11v2.c(OK) | ||
-> mbe1.c(OK) | -> mbe1.c(OK) | ||