Friday, February 26, 2010

links for 2010-02-26: Killing innovation; KLM and Google Apps; Smartphones vs Notebooks

Lysacek vs Plushenko: A look at the numbers and data

In the wake of Evan Lysacek's gold medal upset in the mens figure skating at the Vancouver Olympics, silver medalist and pre-event favorite Evgeni Plushenko came out and said it: He was robbed.  His contention is that mens skating needs quadruple jumps, and that he did one, Lysacek didn't, and thus he should win.
"We need quadruples ... that is the future of figure skating," Plushenko said. "Without the quadruple, [it's] not men's figure skating. Now it's dancing."
The scoring system in figure skating has changed and is no longer the subjective 6 point scoring system where you had the mysterious "Russian judge" giving scores one couldn't understand, but is now a much more objective, particularly on the technical side, system where each element has a base score and the competitor is judged on how well they performed it.  Further, jumps performed late in the program earn a 10% bonus to give credit for performing them when more difficult and to encourage skaters to not front load their routines making them somewhat boring.  Add this all up and you have the technical score.

Now, a quad jump is indeed given a higher base score and so Plushenko's claim does have some merit, but it is only 1 of 13 elements that are scored, so since I love looking at data, I couldn't help diving in to the detailed scoring of their two routines to see how they stacked up.

In the table below, I've listed the programs for both skaters with the base value for their elements, their grade of execution, and running total along with the difference of their running totals through the programs.  I've also put in bold those jumps that occurred in the second half of the programs and received a 10% bonus for the base value.  Note, since both skaters had identical program components scores, analyzing the technical score is all that is needed to compare them.

LysacekBaseGoETotalPlushenkoBaseGoETotalLysacek Lead
3Lz+3T101.411.44T+3T13.80.814.6-3.2
3A8.20.620.23A8.2-0.3622.44-2.24
3S4.5125.73A+2T9.5132.94-7.24
CiSt43.91.230.83Lo50.638.54-7.74
FSSp430.834.6FSSp32.60.1441.28-6.68
3A+2T10.45-0.5644.493Lz60.647.88-3.39
3Lo5.5150.99CSSp430.751.58-0.59
3F+2T+2Lo9.13-0.459.72CiSt33.30.855.684.04
3Lz6.61.467.723Lz+2T8.03063.714.01
2A3.850.872.373S4.950.869.462.91
FCSSp430.575.872A3.85174.311.56
SlSt33.30.980.07SlSt33.3178.611.46
CCoSp43.5184.57CCoSp43.50.682.711.86

From this we can see that Plushenko did take an early lead with his quad/triple combination and extended it with his early triple axel combination and triple loop, but then the lead began to shrink and ultimately became a lead for Lysacek when he threw his triple/double/double combination.  The way the lead varies is really due to the order of the elements as we aren't comparing apples to apples in the rows.  To do that, I've reordered Plushenko's program to match the rows of similar elements of Lysacek's below and the Diff column is the difference for that row/element.  The 10% bonus items still appear in bold.

LysacekBaseGoEPlushenkoBaseGoEDiff
3Lz+3T101.44T+3T13.80.8-3.2
3A8.20.63A8.2-0.360.96
3S4.513S4.950.8-0.25
CiSt43.91.2CiSt33.30.81
FSSp430.8FSSp32.60.141.06
3A+2T10.45-0.563A+2T9.51-0.61
3Lo5.513Lo50.60.9
3F+2T+2Lo9.13-0.43Lz+2T8.0300.7
3Lz6.61.43Lz60.61.4
2A3.850.82A3.851-0.2
FCSSp430.5CSSp430.7-0.2
SlSt33.30.9SlSt33.31-0.1
CCoSp43.51CCoSp43.50.60.4

Now we can more clearly see how they compare.  Looking at just the jumps to start, as expected, Plushenko's quad does give him a big advantage, but Lysacek executed his triple axel better eating into nearly a 3rd of that advantage.  Plushenko got a bit back with his triple axel combination being better executed (even though Lysacek got the 10% bonus here), but the 10% bonus and better execution got Lysacek nearly a point for his triple loop.  They both did a third combination getting the 10% bonus but Lysacek threw in the extra double loop giving him a 0.7 advantage.  But the big difference was Lysacek throwing his triple lutz late in the program got him a 0.6 advantage that he extended to 1.4 with his execution.

In the end, for the jumps, Lysacek had a base value of 58.23 (3.23 from the 10% bonus) and 5.24 for execution for a total of 63.47 to Plushenko's 59.33 base (but only 1.53 from the 10% bonus) and 4.44 for execution for a total of 63.77.  Plushenko's big lead from the quad was nearly completely lost due to poorer execution (0.8 point diff) and not maximizing his 10% bonus (1.7 point diff).  Also, due to doing the quad toe loop, Plushenko wasn't able to fit a triple flip in his program which is more difficult than the triple salchow and triple loop that he did perform.

Lysacek also performed more difficult footwork and spins having a base value of 16.7 with 4.4 for execution to Plushenko's 15.7 and 3.24 for a difference of 2.16.  This results in, from a technical mark standpoint, Plushenko's 3.8 point base point advantage for his quad being lost and Lysacek actually beating him on the technical mark by 1.86.

Now, if Plushenko has simply paid more attention to putting elements where they get more bonus, say moving the triple axel (0.82 bonus) and triple lutz (0.6 bonus), the margin would have been narrowed to 0.44.  That is less than the difference from his poorer execution meaning that ultimately his winning or losing was due to how he arranged his program and his execution, particularly his triple axel where he had -0.36 grade of execution.

So from the data, it does not appear Plushenko was robbed, rather his assertion that the winner needs to try a quad is only one part of the story.

But what do you think?  Do you think Plushenko was robbed?

Thursday, February 25, 2010

links for 2010-02-25: Amazon SimpleDB; SOA and the Cloud; Dual Licensing

Wednesday, February 24, 2010

Blog entries from the past

I had posted quite a few entries on my blog at Sun, some of them actually interesting!  As I don't have access to that blog any more, in an effort to preserve the entries and provide some continuity and a single place to go for them, I've started importing some of them to this blog.

They should appear to be posted on the date they originally were so won't show up as new entries at the top of the blog, so for those that may be interested, here is a sampling of those I've imported:

Tuesday, February 23, 2010

links for 2010-02-23: Stuck with Oracle or IBM?; Amazon most trusted; Apple in the enterprise

Monday, February 22, 2010

Boeing's Future of Flight

I'm a bit embarrassed to say I'd never been until yesterday, but I finally visited Boeing's facility at Paine Field and went on the Future of Flight tour they have there.  And I have to say, it is impressive.

Boeing has been building a number of planes at the facility for years, starting with the original 747 in the late 1960's.  They presently build the 747-8, 767, 777, and 787 there.  Given that all of these planes are large, a large building is required to house the assembly lines for them.

The building was built originally for the 747 manufacturing and subsequently expanded and has some staggering numbers associated with it as it is the worlds largest building in the world by volume:
  • 472 million cubic feet.
  • 4.3 million square feet, enough room for 75(!) football fields and you could fit Disneyland inside and have 12 acres to spare.
  • There are 6 Tully's coffee shops inside, including the highest volume Tully's in the world.
  • There are 2.33 miles of pedestrian tunnels below the factory.  The "short" direction they have tunnels running 1/6 of a mile.
  • Boeing has 1,300 bicycles in the factory to help employees get around.
  • There are 1 million light bulbs in the factory.
 There are more astounding numbers, too many to list here.  And inside, to see how the assembly lines work and see 6 assembly lines, each long enough to hold 5-6 complete or in progress aircraft is amazing.  Unfortunately they don't allow cameras inside so I don't have pictures, but you can see a few on Boeing's site.

I did take pictures outside as it was a absolutely gorgeous day (it doesn't rain all winter in Seattle) and Paine Field is a fantastic location with views of the Cascades (including Mt. Baker and Mt. Rainier) and Olympics from the same spot.  I also managed to show several new planes on the flight line including some 787's and a new 777 for FedEx, and 2 of Boeing's Dream Lifters, which are used to fly in many of the already built components for the 787 so that the plane isn't so much built as it is assembled and can be done in only 3 days.  The Dream Lifters are the largest cargo planes in the world.

All in all, it was a great tour and I'm glad I went.  If you are interest in planes and flight and happen to be in the Seattle area, I highly recommend taking the tour.

Thursday, February 18, 2010

Oracle and Sun's Open Source Projects

When I wrote my Analysis of Oracle's Strategy for Sun's Middleware, I made mention of Oracle's somewhat vague statements about the future of several open-source communities and projects.  GlassFish is a special case and I covered it as such, but a couple key projects that did not have clear plans articulated were OpenESB and OpenSSO.

For OpenESB at least, and perhaps this is an indication of what will happen with OpenSSO, we do have more clarity from an e-mail sent on the users alias a couple days ago.  Thanks to Frank for sending it, and he highlights a few key things about OpenESB and GlassFish ESB:
  • Oracle does not intend to let the project disappear and will keep it on java.net/Kenai.
  • Oracle has scaled down the investments in OpenESB from what they were at Sun.
  • There is a hope the community will step up to fill the void left by the reduced investment.
  • Existing GlassFish ESB customers will be supported and can buy more licenses, but there is no intent to sell licenses to new customers.
There is also an updated governance document that continues to require a Sun Contributor Agreement (SCA) to be signed to contribute and outlines Oracle's special role in the project as steward and reserves the right to:
  • Accept/reject committers
  • Veto the roadmap
  • Veto changes to the OpenESB website
  • Accept / reject changes to this governance document
So in effect, they will continue to provide the infrastructure for the project but also maintain strict control of the project.  The question then is how these rights will be exercised.  My guess is that as long as what is proposed/contributed is an evolution of what exists they will remain fairly hands off.  However, should anything that is there become competitive to or a threat to an Oracle product, I'd expect the rights above to be exercised to some degree to address that.

It is also very important to note that by continuing to require the SCA to contribute, Oracle maintains copyright to all the code and thus the right to use anything developed and contributed in Oracle commercial product under a non-open-source license.  I don't think folks should be scared away by this alone, but it is something to remember and not be surprised by should features or code from OpenESB show up in Fusion Middleware.

This is good news for several of the companies that have formed around the development of components and implementation using OpenESB like Logicoy, ForgeRock, Pymma, Imola, Adjoovo, and more, as it means they don't have to create their own fork(s) and can continue to collaborate together in the community.

It is now up to the community to step up and contribute and see how this plays out for real, but the opportunity for them to do so is great news.  Will this same model be applied to OpenSSO?  We'll have to wait and see.

links for 2010-02-18: Oracle's Cloud; Windows vs Mac; JBoss AS 6 M2

Wednesday, February 17, 2010

links for 2010-02-17: NY Times and iPad; Facebook Harvested