umd instructure.com Project 1 | Two Truths and a Lie: Ideas, Examples and Instructions - 3 Prompts You are expected to use conditional functions, and loops in all three of these prompts. Please ask if you're not sure how you would use one of those tools in your program Rock Paper Scissors A classic game or tie breaker, the rules to rock-paper-scissors are: Rock beats Scissors Scissors beats Paper Paper beats Rock The user of your program is playing a game of rock-paper-scissors against the computer. 1. The user is prompted to type in "rock", "paper", or "scissors 2. The user's choice is compared to the game's choice (randomly generated). And a winner is determined. 3. The program notifies the user of the winner or the tie. 4. The user is prompted to play again 5. The process repeats until the user types 'stop' Random Number Guesser The user is playing a guessing game with the computer. The computer has randomly chosen an integer between 1 and 25. The user is trying to guess the number correctly and the program tells them how many tries it took to get the right number 1. The computer chooses a number 2. The user is prompted to guess and enter a number. 3. When the guess is incorrect, the computer counts it as a try and prompts for another guess. 4. When the guess is correct the program displays that the user got it right and how many guesses it took 5. The program ends when the guess is correct nd What to Turn In 1. You must tum in two Python files. You can pick 2 of the 3 prompts to complete. You must comment key aspects of code (function definition, explain your logic before conditionals, comment Inner and outer loops). You should briefly explain your logic and what's happening where you're commenting. 2. You must turn in 2 stack traces for your first program AND 2 stack traces for your second program. They do not med to be separate files if you can fit them on 1 sheet of paper. This is stack traces total, . You will complete stack traces for 2 unique sets of test data, o Where something is randomly generated, pick something yourself that is within scope (So if randomly enerated between 1-25, you can just pick 8 for the stack trace, etc.) Try to consider edge cases What's andre case These programs repeat until the user determines to stop. For your stack traces you can assure that the user repeats at least twice Slendar DO