CS173: Intro to Computer Science - Kepler's Third Law (100 Points)
Assignment Goals
The goals of this assignment are:- To implement an arithmetic expression into executable code
- To map variables to expression parameters
Background Reading and References
Please refer to the following readings and examples offering templates to help get you started:The Assignment
Kepler’s Third Law relates the orbital period of a body around another body. Due to gravitational forces, bodies in space are attracted to one another; objects in orbit continuously attract one another, forming an orbital pattern that we can predict. In this lab [1], you will compute the orbital period of the planets around the sun, given each planet’s mass and length of its semi-major axis (the semi-major axis is half the length of the longest chord across the orbital ellipse).
The formula relating the orbital period T of a planet to its mass m and semi-major axis length a is:
\(T = \sqrt{\frac{4 \pi^{2} a^{3}}{G(M + m)}}\)
There are constants used in this formula, with values (given below) that you can plug into your program. To use them, you can declare a constant variable as follows:
final double VARIABLE_NAME = 123.456
(note the use of the final keyword, which means that the assigned value cannot be changed, and the capital letters for the variable name, which quickly indicates to a programmer that the value is indeed a constant).
- \(M = 1.989 \times 10^{30} kg\)
- This is represented in Java as 1.989e30
- \(G = 6.6743015 \times 10^{-11} \frac{meters^{3}}{kg \times sec^{2}}\)
- This is represented in Java as 6.6743015e-11
The following table provides your inputs for the planetary mass and semi-major axis length, as well as an approximate length of the year on that planet in Earth Days (to help you check your output). These are approximations, so your values might be a little different because we’re rounding some values, but this should give you a rough idea of the values you’ll get.
| Planet | m: Mass (kg) | a: Semi-major Axis Length (AU) | Approximate Length of Year (Earth Days) |
|---|---|---|---|
| Mercury | 3.285e23 | 0.38710 | 87.9693 |
| Venus | 4.867e24 | 0.72333 | 224.7008 |
| Earth | 5.972e24 | 1 | 365.2564 |
| Mars | 6.39e23 | 1.52366 | 686.9796 |
| Jupiter | 1.898e27 | 5.20336 | 4332.8201 |
| Saturn | 5.683e26 | 9.53707 | 10775.599 |
| Uranus | 8.681e25 | 19.1913 | 30687.153 |
| Neptune | 1.024e26 | 30.0690 | 60190.03 |
| Pluto (a dwarf planet) | 1.309e22 | 39.4821 | 90600 |
Converting Astronomical Units to Meters
Astronomical Units (AU) is a unit of measure approximately defined as the distance from the earth to the sun. However, notice that the units in the constants above use meters. In order to use the axis length value in your formula, you will need to convert the length from AU to meters. One AU is approximately 149,597,870,700 meters, which we will represent as a double (since the value itself is larger than the maximum value of an int), so you can multiply the AU value in the table above by this value, as follows:
final double metersPerAU = 1.49597870700e11;
double mercuryAU = 0.38710;
double mercuryMeters = mercuryAU * metersPerAU;
Some Arithmetic Expression Examples for Reference
Here is a coding example (unrelated to the lab, but for reference), to compute the average of two numbers, you might first add the two numbers, and then multiply by 0.5 (or divide by 2.0), as follows:
int x = 6;
int y = 12;
double average = 0.5 * (x + y);
To take the square root of a number x, you can use the Math.sqrt(x) function, and to raise a number x to a power p, you can use the Math.pow(x, p) function. The constant \(\pi\) is provided to you as Math.PI. Math.sqrt(x) and Math.pow(x, p) accept and return values of type double, and, similarly, Math.PI is a double. For example, the code snippet below computes the area of a circle with radius 6 (note, this code will not appear in your lab directly; it’s just an example!):
double r = 6.0;
double rSquared = Math.pow(r, 2);
double area = Math.PI * rSquared;
Converting the Orbital Period from Seconds to Days
Just as you converted Astronomical Units (AU) to meters, Kepler’s formula yields the orbital period in seconds. In order to output the orbital period in Earth days, you will need to convert it by dividing the number of seconds by the number of seconds in an Earth day. I recommend dividing the orbital period by the product of the number of hours in a day, times the number of minutes in an hour, times the number of seconds in a minute. This will make your program easier to read and understand.
What To Do
I strongly suggest computing the portions of this formula one item at a time, rather than implementing the entire formula as a single line of code. Thus, I would compute the numerator separately from the denominator, then compute the square root of the quotient. You might even compute the division first and then separately take the square root of it. This keeps your code short and your arithmetic concise, and each of these makes your code easier to read, understand, and fix!
- First, begin by declaring a
final doublevariableM, and setting it to the value1.989e30. - Next, declare another
final doublevariableG, with the value6.6743015e-11. - Then, using the table above, declare
doublevariablesmanda, equal to the values in the table for one of the planets. If you choose Venus, I suggest naming the variablesvenusMandvenusA, so that you will know which ones are which later when computing the rest of the planetary orbits! - Multiply
aby1.49597870700e11to convert it from AU to meters. - Implement Kepler’s Formula to compute
T, the orbital period in seconds. I recommend computing each part of the formula as a separate variable to make the code easier to write (and to read!). For example, you might create a variable whose value isM + mfirst, and then multiply that byG. Another variable could hold the numerator, which you might set to4before multiplying itself by Math.PI squared, and multiply that again by a “cubed.” Then you can divide those two variables as a new variable, and take the square root of that resulting variable. There are many correct ways of doing this, though, so you don’t have to follow this plan exactly! This is just one approach that you are welcome to use. - Convert
Tfrom seconds to days by dividing by the number of seconds in a day. If you’d like, you can do this by dividing by the number of seconds in a minute, then dividing that by the number of minutes in an hour, and then dividing that by the number of hours in a day. - Print
T, the orbital period in days. You can check your work using the table above, which provides the approximate period in days for each planet. - Repeat this process for the remaining planets, such that your program prints out all of the orbital periods when you run it. For now, you can copy and paste your code and modify the variable values to do this, but we’ll learn an easier way soon!
- Don’t forget to comment your code to describe what you are doing using
//, and write up a README describing what you have done to accompany your submission. You can save your README file in your project directory. - When you’re done, write a README for your project, and save all your files, before exporting your project to ZIP. In your README, answer any bolded questions presented on this page. Here is a video tutorial describing how to write a README for your project, and how to export it.
-
Developed by Prof. Chris Tralie ↩
Design Questions to Help You Begin
Please answer the following questions in your README file before you begin writing your program.- What code is required to compute the value of
araised to the power of 3? - What code is required to compute the value of
Math.piraised to the power of 2? - What code is required to compute the denominator of Kepler's formula?
- What code is required to compute the numerator of Kepler's formula?
- What variables are different for each planet's computation? Which variables are re-used for all planets?
Submission
In your submission, please include answers to any questions asked on the assignment page in your README file. If you wrote code as part of this assignment, please describe your design, approach, and implementation in your README file as well. Finally, include answers to the following questions:- If collaboration with a buddy was permitted, did you work with a buddy on this assignment? If so, who? If not, do you certify that this submission represents your own original work?
- Please identify any and all portions of your submission that were not originally written by you (for example, code originally written by your buddy, or anything taken or adapted from a non-classroom resource). It is always OK to use your textbook and instructor notes; however, you are certifying that any portions not designated as coming from an outside person or source are your own original work.
- Approximately how many hours it took you to finish this assignment (I will not judge you for this at all...I am simply using it to gauge if the assignments are too easy or hard)?
- Your overall impression of the assignment. Did you love it, hate it, or were you neutral? One word answers are fine, but if you have any suggestions for the future let me know.
- Any other concerns that you have. For instance, if you have a bug that you were unable to solve but you made progress, write that here. The more you articulate the problem the more partial credit you will receive (it is fine to leave this blank).
Assignment Rubric
| Description | Pre-Emerging (< 50%) | Beginning (50%) | Progressing (85%) | Proficient (100%) |
|---|---|---|---|---|
| Algorithm Implementation (60%) | The algorithm fails on the test inputs due to major issues, or the program fails to compile and/or run | The algorithm fails on the test inputs due to one or more minor issues | The algorithm is implemented to solve the problem correctly according to given test inputs, but would fail if executed in a general case due to a minor issue or omission in the algorithm design or implementation | A reasonable algorithm is implemented to solve the problem which correctly solves the problem according to the given test inputs, and would be reasonably expected to solve the problem in the general case |
| Code Quality and Documentation (30%) | Code commenting and structure are absent, or code structure departs significantly from best practice, and/or the code departs significantly from the style guide | Code commenting and structure is limited in ways that reduce the readability of the program, and/or there are minor departures from the style guide | Code documentation is present that re-states the explicit code definitions, and/or code is written that mostly adheres to the style guide | Code is documented at non-trivial points in a manner that enhances the readability of the program, and code is written according to the style guide |
| Writeup and Submission (10%) | An incomplete submission is provided | The program is submitted, but not according to the directions in one or more ways (for example, because it is lacking a readme writeup) | The program is submitted according to the directions with a minor omission or correction needed | The program is submitted according to the directions, including a readme writeup describing the solution |
Please refer to the Style Guide for code quality examples and guidelines.