Skip to main content

If i'm given the lengths of two similar rectangles but not the width, such as lengths x^2 and xy, how do you go about finding the ratio of thier...

Similar figures have the same "shape", but not necessarily the same size. For polygons in particular, the corresponding angles are congruent and corresponding side lengths are proportional. The constant of proportionality is called the scale factor. (This is also the dilation factor as similar figures can be considered as dilations of a preimage to an image.)


If the scale factor is a:b then all corresponding lengths are in the ratio of a:b. (e.g. lengths of corresponding sides, lengths of corresponding diagonals, radii, apothems, chords, etc...)


If the scale factor is a:b then the ratio of corresponding areas is a^2:b^2. (e.g. area, lateral area, etc...)


** For polyhedra, if the scale factor is a:b corresponding volumes are in the ratio a^3:b^3. **


We are given similar rectangles whose lengths are x^2 and xy. Since the rectangles are similar, all corresponding lengths are proportional and the scale factor is x:y. (Write the proportion x^2:xy in simplest form; this is the scale factor.)


All corresponding lengths, including perimeters, are in the same proportion. All corresponding areas are in the ratio x^2:y^2.


The ratio of their areas is x^2:y^2.


 

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...