Skip to main content

State what would happen when an incident ray is equal to 90 degrees.

If the incident ray is equal to 90 degrees, nothing would reflect off of the mirror. That would be the result because the incident ray is travelling parallel to the surface of the mirror.  


The angle of incidence is measured from the normal, and the normal extends perpendicular from the surface of the mirror.  The angle of incidence is measured from that line.  


I believe that the question might be incorrectly assuming that the normal is 90 degrees instead of 0 degrees.  A line drawn straight up from the surface of the mirror could cause people to assume that the line represents 90 degrees.  Mirror rules are different.  The mirror itself is 90 degrees from the normal.  


The resulting reflection from an incoming ray of light can be explained using the law of reflection.  The law of reflection states that when a ray of light reflects off of a surface, the angle of incidence is equal to the angle of reflection.  For example, if the incident ray is at an angle of 37 degrees, then the reflected ray also has an angle of 37 degrees.  An incident ray of 0 degrees would reflect straight back at the same 0 degrees.  90 degrees wouldn't interact with the mirror at all.  

Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...