The winner of the real Iditarod Sled Dog Race is the first team to Nome. Since each team leaves the starting line at different times, the staggered start is equalized by corrections elsewhere on the trail.
The IditaType™ Race teams likewise do not start at the same time; they don’t even start on the same day. Additionally, due to holidays and other schedule disruptions, grade levels may not have the same number of class meeting each week.
To equalize the differences, the Race Marshall will log actual time spent working by each team with the Racing Time Google sheet shown above. In this way, the shortest elapsed time working among all the grade levels will determine the first team to Nome.
Your most efficient implementation of this project is for me to provide all the daily trail positions for your typing test data.
The project is scalable, so teachers can start with the basics; the 14 one-minute typing tests through typing.com. Teachers create an account (free), then add their students to the class.
Teachers establish minimum accuracy standards. Students have to have 14 tests at or above the standard. I use 90% accuracy for my 3rd through 6th grade classes.
Students do all the tests in one class session. Teachers export the results from the Reports page and email the file to me. I’ll run the data through my macros and build two evenly matched teams, then turn their tests into 14 days of Iditarod trail progress. I’ll return the results as PDF’s and they can take it from there, as much as they are comfortable with. I’ll charge a nominal fee, say a buck per student.
The Trail Time and Resting Time Calculator can be found through the Idita-Type 2016 article in the Musher section. It is a simple Google Sheets page that the Mushers use to find out important information for the Trail Log.
Mushers enter the number of miles their team traveled in a day. The spreadsheet divides that number by an average rate of 5 mph to determine the number of running hours. The resting time is the difference between a 24 hour day and the number of running hours on the trail.
If you’ve used the Excel workbook macros to generate teams, forward progress is going to be closely matched throughout the race. At some point, one of the teams is going to win and one is going to come in second. Making it all of the way to Nome in this project is an accomplishment in itself, so the students will need to be prepared ahead of time for the dynamics of a competitive atmosphere in the computer lab. Good sportsmanship opportunities will abound.
For the 2016 race, I’ve pre-plotted the positions for each day’s run. For one of my classes, a team that led most of the race falls short of the finish line by three miles. This happened because one of the particularly good typists failed to complete 14 days of 95% or better one-minute tests. I will be discussing this with the musher during the race and offering a solution.
The aforementioned student will have to leave the team during the race and complete at least one more timed typing test. I’ve included an Additional Mile calculator on the Rate sheet to determine exactly the minimum wpm needed to get the team across the finish line. Nobody fails or quits three miles from the finish.
Setup: Race Marshal uses three terminals: one for Team 1, one for Team 2, and one for the Race Marshal’s predetermined team positions for each day of the race.
All students gather in the instructional area for briefing.
Display seating assignments as per Team Profile sheets.
Review Team Position Roles and display Documents
• Trail Log: Hard-copy to Wheels to Musher and through the Team to Lead
• Excel Workbook: in Musher’s Google Drive
• Official Google Map: Lead’s Google My Maps; editing privileges with whole team.
Explain and demonstrate: Using the Ruler tool in Google Maps to measure exact distance from the last checkpoint. Display and use both teams’ actual numbers to show pins for Day 1. Wheels record data on Trail Log.
Explain and demonstrate: Team members adding pins with text and photos to the shared map.
Explain that once Musher okays Lead’s position on the map, Musher brings Trail Log to Race Marshal for approval.
Explain that Race Marshal compares Team’s Google Map position with Race Marshal’s own map. If they match, Race Marshal will release the data for Day 2, and so on throughout the race.
Race Marshal gives 10 second countdown. Team members disperse to positions and begin. Race Marshal displays timer.
In order to be able to quickly verify that the Leads have accurately pinned the location of each day’s run, the Race Marshal needs to know where those locations are and be able to instantly compare the team’s map with the correct locations.
The Race Marshal transfers numbers from the Team 1 and Team 2 sheets one day at a time, consults the Trail Position sheet for the exact mileage passed the last checkpoint, and pins it on the Race Marshal’s Google Map.
On Race Day, the Race Marshal will use three computer terminals: one for Team 1’s Google Map, one for the Race Marshal’s Google Map, and one for Team 2’s map.
When the Musher brings the Trail Log from the Leads to the Race Marshal, the Marshal will be able to instantly compare the position that the Lead pinned with that of the official position. If the Team position matches the Race Marshal’s map, the Race Marshal will release the next day’s data to the Wheels.
The 5th and 6th graders have completed their typing tests in preparation for the race next week. After running the team-generating macros, this is how the teams compare:
Some of the students were not able to complete fourteen timed typing tests with a minimum 95% accuracy. This will result in a sharp decline in trail progress toward the end of the race.
After running a macro to populate the test scores on the Data sheets, it became evident that in both grades, one of the teams would arrive in Nome before the other. However, team progress will also be determined by the efficiency and accuracy with which the teams’ official online maps are completed.
Race Marshal opens each team’s official online map and Daily Data file.
Race Marshal sets rate.
Musher enters value on Rate sheet.
Race Marshal releases Day 1 wpm values for each team member via shared read-only Daily Data file to Wheels.
Wheels communicate individual miles to Musher.
Musher enters values on Data sheet, communicates Trail Position to Wheels.
Wheels relays exact Trail Position to Teams.
Teams relay Trail Position to Swings. Teams determine approximate location on online map and begin editing Checkpoint icons and placing pictures of progress-to-date. Swings determine exact position on official online map.
Swings and Lead pin exact position on online map. When completed, Musher approaches Race Marshal for verification. When Race Marshal verifies location, team has successfully completed Day 1.
Race Marshal releases Day 2 wpm values, and procedure repeats.
First team to Nome wins.
Information | Automation | Innovation | Instruction