![]()
"America's future demands investment in our people, institutions, and ideas. Science is an essential part of that investment. . . ." So states the Clinton administration's policy statement, "Science in the National Interest." NASA has accepted the responsibility to contribute to this figurative "call to arms" and has challenged its Centers and its individual projects to develop programs which use the thrill of discovery to better capture the imagination of our elementary and secondary school students and teachers. Called "educational outreach," these programs involve the development of various products which are designed to help make existing math and science curricula more exciting and relevant. Galileo is very actively contributing to this endeavor in several ways: for example, a curriculum module, lithographs, the first in a series of Educator's Slide Sets, an Arrival Day poster, and a wealth of on-line resources (on the World-Wide Web) are all available. Some of the upcoming products and activities include another session of "Online From Jupiter" (an on-line interactive view into mission operations) starting in mid-February and continuing through the end of March, an informational CD-ROM about Jupiter and the Galileo mission, and a lithograph brochure for each orbit of the tour. In addition, our World-Wide Web site is updated almost daily as new images and other data are returned from the spacecraft.
The accompanying information sheet, "The Galileo Resource Guide," provides a list of resources and includes information on how to obtain them.
We're especially interested in finding ways for teachers to incorporate these materials and activities into their classrooms and in getting feedback from teachers as to how Galileo can best serve their needs. To start your brainstorming, here are some proposed activities for the classroom that incorporate Galileo educator's resources. Many of these activities are similar to the actual type of work performed (or the techniques used) by scientists and engineers working on the project. Similarly, the suggested discussion topics reflect the types of questions that scientists and engineers would raise in the course of their work.
One of the most important contributions to making the most of outreach products is teacher feedback. Suggestions and criticism are always welcome, either by mail (Galileo Educational Outreach, JPL, 4800 Oak Grove Drive, MS 264-419, Pasadena, CA 91109), email (askgalileo@galileo.jpl.nasa.gov), or fax (818)354-6256.
Note: for information on obtaining the resources used in these activities, please refer to "The Galileo Resource Guide."
Resource used: Educator's slide set
Activity description: Students must guess (or figure out from clues) where in the solar system each picture was taken.
Make it easier:
Activity description: Students try to reconstruct what an asteroid looks like in 3-d from two-dimensional images (very similar to the work that scientists perform, although they use image processing software)
Using modeling clay , try to "reconstruct" each asteroid in 3-d.
Easier:
Resource used: Educator's slide set or lithographs
Activity description: There's really no up or down in outer space, but that's not always easy for students to see (or believe).
Background: Asteroids may well crash and bump into each other. They may fracture into smaller bodies. Or they may get lucky and continue, unmolested, along their orbits. Can we find any differences in Galileo's flyby images of Gaspra and Ida that would suggest they are different ages? (answer as of July 1995: preliminary evidence is that Ida's surface is older, but scientists are still checking data that will tell them what the surfaces of the two asteroids are made of, which may modify the answer).
Activity description:
Activity description: Here is one suggestion for expanding the curriculum module into a math unit that shows that all this base 2 addition isn't just busywork:
It's 20 years in the future, and, instead of having to carry textbooks back and forth to class, students read them on their home computers. This means that at the start of each class, or at home you don't keep the entire book stored on your computer (it takes up too much room, and crowds off the games), but instead, you "download" just the chapters that you're working on.
The computer can only communicate in a limited fashion: it can only recognize something as being a "on" or "off" (much like Morse code, which recognized short "dots" and long "dashes"). So, we have to come up with a "code" that will tell the computer "this is an a" or whatever. However, we want to be able to send the data back and forth as quickly as possible, so we also want to minimize the number of "on" and "offs" that have to be sent.
Have the students come up with a code that will cover each letter. For example,
a = (on)
b = (on)(on)
c = (on)(on)(on)
etc.
with "off" signifying the end of a letter.
Spell out the words "zebra" and "milk" in your code. How many bits of information does this take?
zebra = 26 + 5 + 2 + 18 + 1 + 5 offs = 57 bits
milk = 13 + 9 + 12 + 11 + 4 offs = 49 bits
How many bits of information, on average, will it take to identify each letter? (14)
Is there any way to minimize the number of bits that will get used on average? (some letters occur more frequently (e.g. e, s, t); assign those letters to a smaller number of "ons")
Also, we must account for capital letters, punctuation, and numerals. How many characters total do we need?
a-z = 26
A-Z = 26
numbers, punctuation, etc. (count keys on keyboard) = 42
94 characters needed, total.
Having to write out 94 (on)s is going to get tedious! Let's try another possibility. Make each letter exactly 7 bits of information long. Then, you could have (for example)
a = (off) (off) (off) (off) (off) (off) (off)
b = (off) (off) (off) (off) (off) (off) (ON)
c = (off) (off) (off) (off) (off) (ON ) (off)
d = (off) (off) (off) (off) (off) (ON ) (ON)
and so on; moving from the right, we keep turning on little switches. This scheme has some nice advantages: every letter or bit of punctuation only takes up seven bits of data.
Why seven bits?
If we had a code that said that each letter can only be one bit long, the computer would only receive two possible letters: (on) would be one letter, and (off) would be the other letter. If your entire vocabulary consists of the word "og," this is no problem, but it would definitely hinder conversation in English.
If each letter could be 2 bits long, then we would have these possibilities:
(on)(on)
(on)(off)
(off)(on)
(off)(off) = 2 possibilities x 2 possibilities = 4 possible letters
If letters could be 3 bits long, what would the possibilities be?
(on)(on)(on)
(on)(on)(off)
(on)(off)(on)
(on)(off)(off)
(off)(on)(on)
(off)(on)(off)
(off)(off)(on)
(off)(off)(off) = 2 possibilities x 2 possibilities x 2 possibilities = 8 possible letters
If we allow each letter to be 7 bits long, 2 x 2 x 2 x 2 x 2 x 2 = 128 possibilities, more than we really need (but 2 x 2 x 2 x 2 x 2 x 2 = 64, which is too few). Actually, computers assume 10 bits per letter: this allows for additional characters that aren't used in all languages (e.g. the British pound symbol) and for error checking (a way to ensure that the transmission is received without garbling).
Instead of writing (on) and (off), let's write 1 and 0. In this type of shorthand, the thirteenth number, for example, is written as 1101, where each "place" further from the right side increases by a factor of 2, compared with the numbers we're used to writing (where each place increases by a factor of 10). This is why we call normal numbers "base 10" and the other system "base 2;" we also see here that systems other than base 10 can have real-world uses (base 16 is also used for computer purposes, as is base 8).
What is meant by "bit rate?"
Have students come up with a list of different ways to send a message to a friend living 50 miles away (e.g. smoke signals, pony express, letter, telegraph, phone call, fax). Which ways are fastest? Which are slowest? How can we measure how fast each of these sends the data?
Spacecraft engineers (and computer engineers, too), talk about "bit rate," which measures how many bits of information can get sent by the computer each second. A home modem can easily send over 14,000 bits per second (bps). Let's see what bit rate really means:
a) Pick out a book, and count the words on one page. Have one student read the page out loud at "normal" speed while another student acts as timer. Try doing this as fast as possible, too, while making sure that the other person can actually understand WHAT you're saying. How fast can YOU read and still be understandable? (one JPL engineer, trying this, got out 4.4 words per second.).
Change this to a bit rate. Assume that there are 5 letters per word, and 10 bits per letter, so there are 50 bits per word. If you can read 4.4 words per second, that's 220 bits per second.
How long would it take you to read the entire book?
Now, let's make the problem harder. Go outside on a noisy street (or in front of a loud fan, or in the middle of a lunchroom), and, once again, read the page out loud. Notice how, if you read very quickly, the words get lost in the noise--you have to be careful and make sure that each word is clearly pronounced, which makes you slow down. What is your bit rate now? How low does your bit rate drop if you move 10 feet away from the person who is listening to you?
Just as your "bit rate" drops when you get further away, or when other noise interferes with your "signal," so too Galileo's bit rate drops when its signal weakens with distance, or when it has to overcome interference (such as when its signal has to pass near the Sun, which can generate a great deal of radio noise). Galileo will be communicating back to earth at a top rate of 160 bits per second. How long would it take Galileo to read the book?
Activity description: Viewing the solar system from Jupiter looks quite different than seeing it from Earth. Here's how to orient your students:
Activity description -- Junior High: put the spacecraft's speed into perspective.
Look at Galileo's WWW page, and find out how fast the spacecraft is traveling at the current time. How fast is this really? (either supply the data below, or have the students guesstimate, or have them add other examples)
Graphing all of this might make it easier to see in a glance how these speeds vary.
Easiest: have the students make up a linear graph that will show all of the speeds, using a long piece of butcher paper (which may need to wrap around several walls!). Cut out pictures to illustrate the data points (e.g. a woman walking or a drawing of a satellite).
More advanced (introducing logarithms): Have the students try three different methods (see attached illustration). Which graph makes it easiest to "read off" the actual speed of each object? Which graph makes it easiest to compare the speeds of each object?
Linear graph: Each tick mark indicates an equal number of kilometers per hour. Drawn on a sheet of notebook paper, differences between running, walking, and a car are easy to see, but nothing else fits on the graph.
Linear graph with expanded scale: Each tick mark indicates an equal number of kilometers per hour. Drawn on a sheet of notebook paper, humans, cars and planes all appear to move at the same speed.
Log graph: Each tick mark indicates a factor of 10 increase in the number of kilometers per hour. This makes it easy to tell that, for example, Galileo was moving roughly 100 times faster fight after the second Earth flyby than it will be moving right before arriving at Jupiter.
Activity description --Senior High: acceleration and deceleration
Monitor Galileo's speed (from the Galileo WWW page) over several days. What is happening to its speed? Is it changing or staying stable?
Once the spacecraft arrives at Jupiter, monitor the spacecraft's speed with respect to Jupiter for an entire orbit (roughly 4050 days). Plot the speed versus distance from Jupiter. When is the spacecraft traveling fastest (near Jupiter)? Slowest (furthest from Jupiter)? Does the spacecraft ever "stop" moving (i.e. does its velocity ever reach 0)? Is there ever a major change in speed (right at the time of the satellite flyby--this is the so-called gravity assist)?
The spacecraft speeds up and slows down as it orbits around Jupiter; as it moves closer to Jupiter, the gravitational force that Galileo feels increases. When Galileo is traveling further from Jupiter, the gravitational force decreases. The greater the gravitational force, the stronger the acceleration that Galileo feels.
To see this in action, plot the Galileo's acceleration as a function of distance from Jupiter. Just as velocity is the change in distance that occurs in a given time, acceleration is the change in velocity that occurs in a given time. Calculate the (average) acceleration that Galileo feels for each day using the formula (if you want to use the velocity changes on an hourly basis, adjust the time you're dividing by appropriately). What units do you want to express the acceleration in? kilometers per second per second? kilometers per second per day?
For comparison, have the students call up an auto dealership and find out how fast the dealer's cars can accelerate or decelerate (if the dealer gives the numbers as "goes 0 to 60 in 10 seconds," this can be converted to acceleration by the dividing speed change by time interval). You can also compare this to the acceleration due to the Earth's gravity when standing on the Earth's surface (9.8 meters per second per second).
![]()
![]()