To implement a programmatic solution (ie simulation) of a real life process- the mental math trick of determining what day of the week January 1 of any given year (in the 21st century) falls on.

To assist you in completing this project, you may make the following assumptions:

• all requests will be for days in the 21st century (2000-2099)

In addition to the new skills required on previous projects, to successfully accomplish/perform this project, the listed resources/experiences need to be consulted/achieved:

• ability to construct and use selection statements (if)
• ability to distinguish between integer types and floating point types

Mental Math constitutes an intersection of mental tricks and math- instead of utilizing a purely math-only solution, textual manipulations or simplifications in the computational process may take place enabling an individual to, once having learned the process, solve such problems in their head, and typically without the use of a calculating device.

The process in this case is one of simple (reduced) multiplication and mapping against a table. To wit:

For this trick to work, we need to be familiar with the following table (a map of days to numeric values):

NOTE: Depending on how you implement your algorithm, you may find your approach prefers 7s OR 0s… you aren't necessarily going to be encountering them at random. Once you work through your approach, you will discover which one you end up with.

Okay, time for the magic.

Let us try it on January 1st, 2014.

In our example, we're working with 2014, the last two digits are therefore: 14

You should be able to come up with a means of extracting this information in your program.

Even this is something we can do in our heads. I can think of two approaches right off the bat:

10% percent of anything is merely moving the decimal over one place to the left. 10% of 54 is 5.4

For our 2014 example, 10% of 14 is therefore 1.4

So we need two 10 percents… 1.4 + 1.4 = 2.8

Finally, 5% is half of 10% (half of 1.4 is 0.7), so 1.4 + 1.4 + 0.7 = 3.5

But, since we do not care about the decimal, we drop it and are left with just 3.

25% is a convenient value for us with respect to 100, allowing this optimized approach to work.

• Half of 100 is 50 (50%)
• Half of 50 is 25 (25%) – hence the “half of half”

So, 14 cut in half is 7.

7 cut in half is 3.5.

Once again, dropping the decimal yields 3.

Once we have our 25% value, go and add it back to our two-digit year value:

14 + 3 = 17

Some multiples of 7:

So, with a value of 17, what is the largest multiple of 7 that is still less than (or equal to) 17?

Hopefully you identified the 14 as the likely candidate.

17 - 14 = 3

We ended up with a 3 as the result for January 1st, 2014.

Go and reference the 3 from that table… what day do we get? Does it match the actual day of the week for January 1st, 2014?

lab46:~$ cal 01 2014
    January 2014
Su Mo Tu We Th Fr Sa
          1  2  3  4
 5  6  7  8  9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31

lab46:~$ 

Pretty neat, eh?

In the event of a leap year, we simply subtract 1 from the 25% value, and continue on as usual.

Makes sense, right? Leap years add a day, so something ends up being “off by one”.

It is your task to write the program that will use the above method to determine the day of the week any given January 1st in the 21st century falls on.

Your program should:

• prompt the user for the four digit year (input)
• perform the task (process)
• display the final value (output)

lab46:~/src/SEMESTER/cprog/dow0$ ./dow0
Which year: 2014
January 1st, 2014 falls on: Wednesday
lab46:~/src/SEMESTER/cprog/dow0$ 

The execution of the program is short and simple- obtain the input, do the processing, produce the output, and then terminate.

Your program must output as follows:

• Input prompts, and everything else except the actual day of the week should be output to STDERR
• The calculated day of the week needs to be displayed to STDOUT
• The output MUST contain the “January 1st, YEAR” string
  • YEAR must be all 4 digits, exactly as input by the user
• The calculated day of the week must be fully spelled out and correct, with the first letter capitalized, remaining letters lowercase.

Be sure to provide any commentary on your journal regarding realizations had and discoveries made during your pursuit of this project.

• Try this algorithm on some years in the 20th century and see how it fares.
  • Is it correct? Is it correct for any of them?
  • If it isn't correct, is it consistently off by a value?

This isn't just about implementing a particular algorithm, it is about understanding an algorithm- its domain of correctness, and its limitations.

To successfully complete this project, the following criteria must be met:

• Code must compile cleanly (no warnings or errors)
• Executed program must display a total of 2 lines, one for input, one for output.
• Input must be in the form of a complete (i.e. four-digit) year
  • input must be a number, NOT a string
• Output must be correct, and match the form given in the sample output above.
• Code must be nicely and consistently indented (you may use the indent tool)
• Code must be commented
• Output Formatting (including spacing) of program must conform to the provided output (see above).
• Track/version the source code in a repository
• Submit a copy of your source code to me using the submit tool.

To submit this program to me, use the submit rule to the Makefile; run the following command at your lab46 prompt:

lab46:~/src/SEMESTER/cprog/dow0$ make submit

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.

What I'll be looking for:

52:dow0:final tally of results (52/52)
*:dow0:obtained via grabit by Sunday before deadline [4/4]
*:dow0:program compiles successfully, no errors [4/4]
*:dow0:program compiles with no warnings [4/4]
*:dow0:program performs stated task/algorithm [4/4]
*:dow0:program output conforms to formatting expectations [4/4]
*:dow0:proper error checking and status reporting performed [4/4]
*:dow0:code implements solution using relevant concepts [4/4]
*:dow0:code updates committed/pushed to lab46 semester repo [4/4]
*:dow0:code uses correct variable types and name lengths [4/4]
*:dow0:project is submitted with relevant and complete source [4/4]
*:dow0:project is submitted on lab46 using 'make submit' [4/4]
*:dow0:project is submitted with pi and lab46 binaries [4/4]
*:dow0:runtime tests of submitted program succeed [4/4]

Additionally:

• Solutions not abiding by SPIRIT of project will be subject to a 25% overall deduction
• Solutions not utilizing descriptive why and how COMMENTS will be subject to a 25% overall deduction
• Solutions not utilizing INDENTATION to promote scope and clarity will be subject to a 25% overall deduction
• Solutions lacking ORGANIZATION and are not easy to read (within 90 char width) are subject to a 25% overall deduction