In this exercise, you are going to make a sample bot conversation. At this point, we don't have too much that we can do, but you are going to ask the user for their name and then use that in the constructor for the bot. After that, you are going to simulate a conversation. You will print questions to the console and answer them by calling methods from the Bot class. (You don't actually prompt the user for any information other then their name).

When you are finished, your output should match the output below (with the exception of your name).

Sample Output:

Hello. What is your name?

Kiara

Hello Kiara! My name is Hal!

How are you today!

You can ask me about the weather,

or how many feet are in a mile.

I can even convert feet to meters!

What's the weather like?

Its always warm and dry inside your computer!

How many feet in a mile?

There are 5280 feet in a mile.

It was nice talking with you!

Have a great day!

Challenge: The bot does have some additional commands included, but we haven't covered these topics yet. Can you figure out how to access some of these methods?

When making changes to optimize part of a processor, it is often the case that speeding up one type of instruction comes at the cost of slowing down something else. for example, if we put in a complicated fast floating-point unit, that takes space, and something might have to be moved farther away from the middle to accommodate it, adding an extra cycle in delay to reach that unit. the basic amdahl's law equation does not take into account this trade-off. a. if the new fast floating-point unit speeds up floating-point operations by, on average, 2ă—, and floating-point operations take 20% of the original program's execution time, what is the overall speedup (ignoring the penalty to any other instructions)? b. now assume that speeding up the floating-point unit slowed down data cache accesses, resulting in a 1.5ă— slowdown (or 2/3 speedup). data cache accesses consume 10% of the execution time. what is the overall speedup now? c. after implementing the new floating-point operations, what percentage of execution time is spent on floating-point operations? what percentage is spent on data cache accesses?