Due: Friday Aug. 30 by 11:59pm. Upload both your code and sample output to Canvas.

Beginning with the Fortune Teller program make the following additions and modifications:

• Change the program so that it accepts one more input from the user. You can make up what the new input is, examples include shoe size, age, etc.
• Change the expression used to generate the "mystic number" or "lucky number" (line 19 of the original program in the textbook), so that it uses all three numbers to compute the "mystic number".
• Add at least one more conditional so that there is an additional possible message to the user.

Include a block of comments at the beginning of the program (or add to the existing block) that lists your names, section number, date, and the assignment number. Also include comments on any parts of the assignment you didn't finish or on any extra work you did. Include this comment block at the beginning of every assignment and lab.

If you can't get all of the modifications done (and for some of the assignments you probably won't) be sure to list which ones you've completed in the comment at the beginning of your program. On the other hand, if you did extra work on the assignment (and sometimes you will want to) also describe the extra work in the comment at the beginning of your program.

For now we are going to assume that the user enters the right type of data (e.g. a number when a number is expected). Later we will start to look at detecting and correcting user input errors, which is a big topic.

To print the program output do the following:
1) Type script output1.txt
2) Run the program and enter your numbers.
3) When the game is over type exit. This stops the script command.
4) Look for a file called output1.txt. Use nano or vim to open the file and look at it. It should contain a 'transcript' of your game.
5) Once this is working - i.e. generating a file that shows a 'transcript' of what took place - redo these steps, but run the program several times using different inputs to show the different possible messages. This is an important step in testing that the program works for a variety of inputs.

Turn in: Turn in both the program and the sample output showing how the program works to Canvas.