Suggest a change

These fields are all optional and need only
be supplied if you would like a direct reply.

Subject
Your email address
Your real name

You must answer this!

If you don't, my spam filtering will
ensure that I never see your email.

What's 8 plus five (in digits only)?

Please make your changes here and then
Editing tips and layout rules.

File: YouHaveToAdmireTheirOptimism

''' <link rel="alternate" type="application/rss+xml"
'''       href="/rss.xml" title="RSS Feed">

********> width="25%"
|>>
''' <a title="Subscribe to my feed"
'''    rel="alternate"
'''    href="https://www.solipsys.co.uk/rss.xml">
'''    <img style="border-width: 0px;"
'''         src="https://www.feedburner.com/fb/images/pub/feed-icon32x32.png"
'''         align="middle"
'''         alt="" />Subscribe!</a>
_
''' <a href="https://twitter.com/ColinTheMathmo">
''' <img src="https://www.solipsys.co.uk/new/images/TwitterButton.png"
'''      title="By: TwitterButtons.net"
'''      width="212" height="69"
'''      alt="@ColinTheMathmo"
'''     /></a>
<<|
----
My latest posts can be
found here:
  * ColinsBlog
----
Previous blog posts:
  * RepresentativesMatter
  * PythagorasByIncircle
  * APuzzleAboutPuzzles
  * HowNotToDoTwitter
  * Calculating52FactorialByHand
  * SmallThingsMightNotBeSoSmall
  * NotIfYouHurry
  * FactoringViaGraphThreeColouring
  * AnotherProofOfTheDoodleTheorem
  * WhenObviousIsNotObvious
  * GraphThreeColouring
  * TheDoodleTheorem
  * BeCarefulWhatYouSay
  * TheMutilatedChessboardRevisited
  * AMirrorCopied
  * TheOtherOtherRopeAroundTheEarth
  * PhotocopyAMirror
  * ThePointOfTheBanachTarskiTheorem
  * SieveOfEratosthenesInPython
  * FastPerrinTest
  * RussianPeasantMultiplication
  * FindingPerrinPseudoPrimes_Part2
  * FindingPerrinPseudoPrimes_Part1
  * TheUnwiseUpdate
  * MilesPerGallon
  * TrackingAnItemOnHackerNews
  * HackerNewsUserAges
  * PokingTheDustyCorners
  * ThereIsNoTimeForThis
  * PublicallySharingLinks
  * LearningTimesTables
  * GracefulDegradation
  * DiagrammingMathsTopics
  * OnTheRack
  * SquareRootByLongDivision
  * BeyondTheBoundary
  * FillInTheGaps
  * SoftwareChecklist
  * NASASpaceCrews
  * TheBirthdayParadox
  * TheTrapeziumConundrum
  * RevisitingTheAnt
  * TheAntAndTheRubberBand
  * IrrationalsExist
  * MultipleChoiceProbabilityPuzzle
  * RandomEratosthenes
  * WrappingUpSquareDissection
  * DissectingASquarePart2
  * DissectingACircle
  * DissectingASquare
  * AnOddityInTennis
  * DecisionTreeForTennis
  * DecisionTreesInGames
  * AMatterOfConvention
  * DoYouNourishOrTarnish
  * BinarySearchReconsidered
  * TwoEqualsFour
  * TheLostPropertyOffice
  * TheForgivingUserInterface
  * SettingUpRSS
  * WithdrawingFromHackerNews
----
Additionally, some earlier writings:
  * RandomWritings.
  * ColinsBlog2010
  * ColinsBlog2009
  * ColinsBlog2008
  * ColinsBlog2007
  * ColinsBlogBefore2007
''' <img src="/cgi-bin/CountHits.py?YouHaveToAdmireTheirOptimism" alt="" />
********
!! 2016/08/28 - You Have To Admire Their Optimism ...

Coming back from Australia, RachelWright and I landed at Heathrow
(which we usually avoid) and caught trains back home.  Our final leg
was from Chester to home, and I had a look at the live departures
board to see how things were looking.

[[[> https://www.solipsys.co.uk/images/TrainTimes2.jpg ]]]
The live departures boards are amazing. I travel by train a lot, and
I mean a lot, and the live departures boards make things enormously
easier, seeing where I can gain time, will lose time, and planning
stops for refreshments.  I use the live departures boards all the
time, and there's something that I'm finding odd.

Consider the board shown at right.  The first train marked there is
the incoming train that will form the second service indicated.  As
you can see, it as due in at 11:57, and then out again at 12:01.

So far, so good.

But wait! The incoming service is (well, was) running late, not due
to arrive until 12:03, fully two minutes after the outgoing service
is (well, was) due to leave.  And yet that second service is shown
as still being "On time".  Clearly they are expecting that the late
running incoming service will, in the next two minutes (the screen
was captured at 11:55) catch up some 4 minutes to enable it to then
leave on time.

You have to admire their optimism.

So that leads me to my question.  If the live departures board is
updated automatically, why is that second service still shown as
leaving "On time"?  But if it's /not/ updated automatically, it
must be updated "by hand," and that just seems insane.

So what is it?  How can this be?  Perhaps this is a definition of
"On time" with which I was not previously acquainted.

Most curious.
----

|>>
| |>> <<<< Prev <<<< ---- RepresentativesMatter <<| | : | |>> >>>> Next >>>> ---- AnUnexpectedFraction ... <<| |
----
********>
''' <a href="https://twitter.com/ColinTheMathmo">You should follow me on twitter</a>
********
''' <a href="https://twitter.com/ColinTheMathmo">
''' <img src="https://www.solipsys.co.uk/new/images/TwitterButton.png"
'''      title="By: TwitterButtons.net"
'''      width="212" height="69"
'''      alt="@ColinTheMathmo"
'''     /></a>
********<
<<|
----
!! Comments

I've decided no longer to include comments directly via the Disqus
(or any other) system.  Instead, I'd be more than delighted to get
emails from people who wish to make comments or engage in discussion.
Comments will then be integrated into the page as and when they are
appropriate.

If the number of emails/comments gets too large to handle then I
might return to a semi-automated system.  That's looking increasingly
unlikely.

********<