NASA Jet Propulsion Laboratory California Institute of Technology JPL HOME EARTH SOLAR SYSTEM STARS & GALAXIES SCIENCE & TECHNOLOGY JPL Email News RSS Mobile Video
Follow this link to skip to the main content
JPL banner - links to JPL and CalTech
left nav graphic Overview Science Technology The Mission People Spotlights Events Multimedia All Mars
Mars for Kids
Mars for Students
Mars for Educators
Mars for Press
+ Mars Home
+ Rovers Home
Mars for Students
Athena Student Interns Program
Mars Exploration Student Data Team
Athena Student Interns Program

These journal entries were written by the William Allen High School team during their week at JPL.


1/13/04 (notes from CJ): My trip to JPL has been quite interesting. The first night at work, I started to feel fatigued and sleep deprived rather rapidly. I was not used to working from 8:30 at night to 3:30 in the morning. The next night I returned to work with my colleague CJ and advisor Mr. Stouch. With a little help from our mentor, Dr. Wolff, CJ and I began to find the temperature of the surface and atmosphere of Mars. During the first and second night working, I attended several Science Operations Working Group (SOWG) meetings. These meetings were assembled mainly to plan out the operations that the rover is going to perform during every sol (martian day). The SOWG meetings are extremely interesting, as well as informational. Even though I have only been here for two nights, the information I have obtained is incredible. I could not tell you how much this experience means to me. Overall it is a good experience, good fun, good people, good night.

1/14/04 (notes from Josh): For the past two days, we've been crunching numbers for the Mini-TES instrument using Dr. Mike Wolff's AirTemp application and data from sols 3 through 8. After sitting in front of the computer, the job quickly became tedious. So Josh and I put our heads together and decided to automate our own student process using the Perl scripting language. We thought it was all fine and dandy, until we hit the 14th line of our program. The data we were inputting ended up confusing the program; causing it to crash. Four hours and many sodas later, our mentor found the problem! The culprit was a trailing line break after the user enters data at the first prompt. Problem fixed, we decided it was time to punch out for the night. More programming tomorrow!
PRIVACY    |     FAQ    |     SITEMAP    |     CREDITS