Tag Archives: typing

Idita-Type™: WPM, Team Strength, and Winners

The strength of the student teams is based on the average wpm of each member of the team (see Team Profiles).  If this were the only factor in the race, then the outcome would be settled before the race even started. The table and chart below show data from the 2016 keyboarding tests and how that affects trail position relative to the other teams.

Screen shot 2016-03-20 at 3.18.13 PM
How Team WPM Affects Race Rankings

The cooperative teams must complete all of their required tasks before trail advancement is awarded. This enables all teams to have a chance to win based on the efficiency that they complete those tasks.

Idita-Type™: Team Talk


Google Docs allows us to share a file amongst all the members of a team for the purpose of communication and record keeping. Shown above is an example of the Musher’s shared Trail Log. All of the team members have editing privileges, as does the Race Marshal.  Interesting possibilities……

I’ve created a multi-page Google Doc that can be viewed here and downloaded as a MS Word file in the Iditarod folder here. It contains a page for every day of the race, a trail map, checkpoint links to Iditarod.com, and bookmarks within the document for easy access to different pages. Each day has a table to be filled out by the members of the team.

Team Members’ Responsibilities

  • Musher: Starting Milepost, Last Checkpoint, Time on Trail, Average mph, Resting Time, # of Dogs, Dog Health, Musher Health, Sled Condition
  • Lead: Finishing Milepost distance and pin
  • Swing: Terrain
  • Team: Weather, Temperature, Points of Interest
  • Wheel: Miles Traveled
  • Pilot: Food Drop, Comments

Position responsible for the information is shown in parentheses:

  • M = Musher
  • L = Lead
  • S = Swing
  • T = Team
  • W = Wheel
  • P = Pilot

NOTE: To compute Resting Time for this race, the Musher will divide the Miles Traveled by an average speed of 5 mph and subtract the quotient from 24.

Starting Milepost (M)
Last Checkpoint (M)
Weather (T)
Temperature (T)
Terrain (S)
Finishing Milepost (L)
Miles Traveled (W)
Time on Trail (M)
Average mph (M)
Resting Time (M)
# of Dogs (M)
Dog Health (M)
Musher Health (M)
Sled condition (M)
Food Drop (P)
Point of Interest (T)
Point of Interest (T)
Point of Interest (T)
Point of Interest (T)
Comments (P)





Idita-Type™ Grade 4


Absolutely awesome performance by both Grade 4 teams today! They listened well during the pre-race briefing, they found their official shared map in their Google My Maps account, Wheels got daily data and passed it on to Mushers, Mushers entered data in the Excel workbook and passed the info on to the Leads who measured trail miles, Swings edited daily position pins, and Team dogs placed pins with pictures and text.

Great job, students!

Idita-Type: All of the excitement of two dog teams in one room

The “second-ever in the history of the world” Iditarod typing race took place today at Eagle Academy Charter School.  Today’s contestants were two teams of 6th graders.

The similarities between the racers’ positions and a real dog team were amazing.

  • The Musher has to keep track of all of the team members, making sure that they are completing their tasks.
  • The Wheel dogs are responsible for getting the team going on each new day’s run.
  • The Team dogs keep track of all of the sights along the trail.
  • The Swing dogs back up and assist the Leader
  • The Lead dogs have to figure out where the trail is and how far the team is getting.
  • The Race Marshal makes sure all of the rules are being followed and verifying official team positions.

The refinements I discussed yesterday made the process much smoother today. I made a new document for the Team Dogs: every one of them had their own Trail Log to keep track of the pins they created on the shared map.

We still had the issue of one person losing the trail map, and it didn’t reappear even with a different browser. Don’t know what to think about that.

Other changes: have the Swing Dogs be in charge of providing pictures and text to each day’s position pin.  Make the text a journal entry of how their team performed.


Ahhh, the bleeding edge of technology…

The Iditarod Typing Race and the Risks of Innovation: What could possibly go wrong?

The first ever in the history of mankind Iditarod Typing Race took place this afternoon at Eagle Academy Charter School in Eagle River, Alaska.  Contestants were two teams of 5th grade technology students. After years of skill development and weeks of planning, the race was a tremendous learning experience in the “We Love Technology” department.


  1. The wireless keyboard for the main instructor’s workstation (which displays on the SMART board) runs on battery power.  Guess when the battery decided to go kaput.
  2. Files that contained crucial data for each day of the race were shared with each team’s Wheel Dogs via Google Apps. They did not show up when the students logged in to their accounts.
  3. No matter what we tried, one team’s official map also did not show up in one of the Swing Dog’s Google Apps account.
  4. Two students’ official map did not show the Common Trail.

I’ll do some troubleshooting and see if the issues are individual workstations, browsers, or sharing privileges. The battery for the keyboard is easy enough.

A parent volunteer who works as a structural engineer was there to help, so we eventually were able to make some forward progress.  He told me afterward that all-digital projects in his line of work are not trusted; hard copies are much more reliable and secure.

The next class to run the race will be the 6th grade tomorrow afternoon. Changes I’m going to make:

  1. Print hard copies pre-race of Daily Data for each team.
  2. Use only one online map for Swing and Lead dogs.
  3. Print hard copy Trail Logs for every Team and Wheel Dog.
  4. Assign specific sections of the trail to each level of the team.

I’m also going to spend more time for pre-race instruction going through a one-day round, showing demonstrating what I expect for every position on the team.

I’m looking forward to a more successful race tomorrow.

Iditarod Typing Race: Preparing for Drama

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.

Iditarod Typing Race: Race Day Events


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.

  1. All students gather in the instructional area for briefing.
  2. Display seating assignments as per Team Profile sheets.
  3. 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.
  4. 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.
  5. Explain and demonstrate: Team members adding pins with text and photos to the shared map.
  6. Explain that once Musher okays Lead’s position on the map, Musher brings Trail Log to Race Marshal for approval.
  7. 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.


First team to Nome wins. Prizes to be determined.