job:  #25  updating the readme just to make a change to show branching
Merge branch 'issue25_updateGPSWatch' of https://github.com/xtuml/models.git into 27_support_for_goals
#27, #33 - Add MATH support for calculating distance.  This version has
a compile error in UI.java.
#27, #33 - Calculate distance properly.  To do this requires the use of
a square-root function, hence the addition of the MATH EE.  While
rebuilding the project to produce the Math.class file, I hit a
compilation error in UI.java, for a missing constructor, SetData( Float,
Unit ).  For now, I've added that constructor to SetData.java, but it's
not clear precisely when or how this issue was injected.

This commit also includes the following files that were not previously
in the Git index:
Debug/.gitignore
bin/library/UI$GuiConnection.class
bin/library/UI.class
bin/uidatatypes/Unit.class
bin/uiinterfaces/IActionsAndDataFromProvider.class
bin/uiinterfaces/IActionsAndDataToProvider.class
javasrc/lib/MATH.java
bin/lib/MATH.class
I created the final two to provide access to the square-root function,
so I'm confident that adding these into the Git index is correct.
However, I'm less confident about the others, as they may have been
intentionally left out, perhaps because they include path names that are
specific to a particular Eclipse installation.

This version runs fine with Verifier now.
#27, #33 - Calculate current average speed by summing the straight-line
distance between each of the last five track points and dividing by the
elapsed time between the first and last points in the subset.  While
this version runs in Verifier, I still need to:
- determine whether the calculated speed is correct
- fix pace (currently displays as 0)
- test boundary cases (0, 1, 2, and 3 track points)
As part of this work I eliminated the Location structured data type, as
leaving it in place will teach the students bad habits.
#27, #33 - Adjusted initial position and distance increment for
simulated GPS.  Fixed calculation errors (kilometers vs. meters) in
distance calculation.  Boundary conditions mentioned in previous commit
tested successfully.  Speed and pace values appear to be valid.
Speed/pace varies immediately after a paused timer, but for now I'll
leave it as is.  This appears to be due to jitter between the GPS update
rate and the timer rate.  Need to decide what to do on this front.  The
specification indicates the watch stores one track point per second, but
the simulated GPS produces a new location every two seconds.
#27, #33 - Tracking component now obtains location data synchronously
with each tick of the workout timer.  However, there is still a bit of
jitter in the time stamps on track points.
#27, #33 - Made the simulation of movement by the GPS slightly more
realistic by adding some variation into the distance moved during each
update period.  This version runs well in Verifer.