OnScreen QB Stats: A New iPhone App for Evaluating Quarterbacks During and After a Game

December 30th, 2009

OK, having spent several weeks working on OnScreen QB Stats™, a sports-category iPhone app that just made it to the iTunes App Store about a week ago, I want to say something about it and how it came to be. As its name will probably imply to most readers, the app concerns American football (I’d forgotten the field has a different length in Canada, so Canadian football must wait), specifically the player that is most important on most teams, the quarterback (QB). He’s the player that handles the ball on virtually every play and has the biggest chance of deciding who wins the game through his ability to move the ball down the field in big jumps by completing passes, including some that score touchdowns. Of course the quarterback can also squander a down by throwing a pass that can’t be caught or, much worse, he can give the ball to the other team by throwing a pass that’s intercepted. Naturally people would like to quantify quarterback performance, so, in addition to being a very important player, the quarterback is the player for which there are the most statistics recorded and calculated. OnScreen QB Stats enables one to record a quarterback’s raw passing results during the course of a game and review the derived stats such as completion percentage as well. It can be used to record and display on an iPhone or iPod Touch the passing stats of every quarterback in the game for each team.

The full set of quarterback statistics recorded and calculated by OnScreen QB Stats is shown below.

details
The User’s Guide for OnScreen QB Stats is available as a pdf file. There every button and display is briefly explained.

After finishing my first app, OnScreen Pitch Count™, I had begun to think about making a version for the iPhone of OnScreen DNA (my virtual model of the double helix molecule of life, which runs on Macs and Windows PCs). I had already started experimenting with OpenGL ES toward that end, when it occurred to me that a lot of the nitty gritty coding I’d already done for OnScreen Pitch Count, which allows a user to record and review the results of baseball pitchers’ pitches, could be easily adapted to an app that followed quarterbacks’ passing results. That is, the machinery for saving and restoring the passing results, for reviewing those results, and for setting up the data storage for the results of individual quarterbacks on the two opposing teams, would be but a minor change from that already developed for the pitchers in OnScreen Pitch Count. That actually turned out to be pretty true. One modification was that I had to allow for the possibility that a quarterback might re-enter the game after being replaced for a time, which is not something that happens in baseball.

I had also assumed that the actual data entry by tapping buttons on the screen would be at least as simple for the pass results as for the pitch results. I thought the bookkeeping involved would be simpler for football, since I wouldn’t have to worry about strikeouts, walks, outs, base runners, and innings (not to mention complications such as charging runs to pitchers after they’d left the game). I thought I’d be able to write the football app in three weeks or so, finishing it in time to justify working on it for the current season. Since every high school, peewee, and non-bowl college game in the country (as far as I know) had been played before the app finally became available, I obviously misjudged the complexity of the task. All in all, when I consider things like the extra choices that had to be coded for undoing an action (e.g. completely wipe out a touchdown pass, call it incomplete, or place the ball short of the goal line), and the numerous states to which the app might need to be restored after an interruption (e.g. awaiting line of scimmage determination after a pass completion) the quarterback app seems to have been more work than the pitching app.

There is less to record for a quarterback than for a pitcher. We need to record attempted passes, completed ones, and intercepted ones. Then we need to keep track of the yards gained passing and the number of touchdown passes. Those are the basics. I added quarterback sacks and longest completed pass for good measure, but from the basic pass statistics we can calculate derived quantities such as yards gained per passing attempt and the rather arcane numbers called quarterback rating in the NFL and passing efficiency in the NCAA. Both of these rating methods use pass completion percentage, yards per attempt, interceptions, and touchdown passes to come up with a number that serves as a basis for comparison among quarterbacks. Although, the number is much less meaningful in a single game than in a season, it can be of interest to know what it is for a game, and OnScreen QB Stats will calculate and display whichever measure of quarterback performance the user desires.

Although the data to be recorded might seem at first glance to be simple, in practice it is more complicated. Someone sitting in a press box with a spotter to provide the details of each play could get by with an app that recorded completions, incompletions, yards gained, interceptions, and touchdowns. But for someone watching a game from the sidelines or stands or even on television, there is the problem of determining how many yards were gained on a given play. The only way to do that with full confidence is to keep track of where the ball is after each play, since one doesn’t know in advance which plays are going to be passes. Once a play is underway, it is difficult to note the line of scrimmage from which play started and then calculate yards gained by noting where the receiver was brought down. It’s a lot to take in and keep straight in a short time, even assuming one has a good view of the sideline yard markers, which is often not the case when watching a game on television. The additional challenge is to do all the data entry on the iPhone without recourse to pencil and paper or on-the-spot mental calculations.

OnScreen QB Stats solves the problem of passing yardage calculation by making it easy to record the new line of scrimmage after each play; and if the play leading to the change of field position is a completed pass, the app automatically calculates the corresponding gain in yards and adds it to the total for the game, while adjusting all other stats that depend on passing yardage as well.

It took me a lot of trial and error to come to this easy way of recording the new line of scrimmage after each play (or penalty). At one point I had thought that using a slider control to just slide a pointer along a representation of the 100 yards of the field to mark the current line of scrimmage would be both intuitive and fast. I ran into two problems with the slider method. For one thing it was hard to quickly obtain the precision I needed down to the yard, which is only 1% of the length of the control. So, I added a second fine-tuning slide control to move the pointer just within plus or minus a couple of yards of where the full-field control pointed. This solution worked, but frequently required using both controls, which was a nuisance. I might have decided to live with it, given the intuitiveness of the slider, but the controls turned out not to be reliably responsive on an actual device. Sometimes the sliders were easy to drag, sometimes they seemed in need of a squirt of WD-40. It was hard to ditch all the work that I had put into that method of yard line setting, but I decided I had no choice but to code a new method.

The solution I came up with can be seen below.
yardset
The screen above shows how one enters the new line of scrimmage after a play has been completed. This screen appears whenever the user taps a button to record a play from scrimmage or a penalty (or simple need to adjust the current setting for the line of scrimmage). In the example shown the team with the ball has reached its opponent’s eleven yard line. Note that the “Defense’s End” is highlighted in the top control to indicate which end of the field the ball is in. That control also adjusts so that the ends of the field in the sense of right and left correspond to what the user sees, assuming the initial setup has been made correctly and the correct quarter has been maintained. Whenever the ball goes to the other team (currently called Defense), the labeling of the top control reverses (Offense becomes Defense and vice versa), so that the field situation is correctly mirrored. At the end of the first quarter, for example, the same switch takes place.

The yard marker for the current line of scrimmage is shown to be 11, and that choice has been made by tapping the tens place control (blank to 5) on its “1” and the ones place control (0 to 9) also on its “1”. There is no keyboard to deal with, and for short yardage plays only the ones place control needs to be adjusted in many cases.

The number 24 beside the “Check Gain” button shows that the user has tapped that button in order to see how many yards will be recorded as having been gained, assuming the ball is marked at the 11 yard line. The previous line of scrimmage must have been the opposing team’s 35. The “Record Pass” button is to be tapped once the user is satisfied with the choice of yard line (here the 11) and need not be tapped until the final spot has been made to minimize the need for adjustments. The button’s title being “Record Pass” indicates that the play just over was a completed pass. On a running play (or pass by someone other than the quarterback), it would be reading “Record Gain” (or “Record Loss”). The “Touchdown” button’s use is obvious, and in the case of a touchdown pass, there is no need to set the yard line button by hand.

The screen below shows the most basic results of the quarterback’s passes and also contains the buttons for registering which type of play has occurred. The pass results shouldn’t need description. The four buttons stacked in the lower right are for recording pass results or for canceling out the previously recorded play (”Undo”). We are especially interested in eliminating the chance for accidental recording by unconscious taps for these four buttons, so they all require a double tap to work. Double-tapping the “Incomp” button just increments the number of passes and the Down, which is displayed in the yellow area along with the yards needed to make a first down and the current location of the ball, which is the opponent’s 42-yard-line. The display of the “42” in red indicates the team with the ball has crossed midfield into the other team’s territory.
basics
The down and yard marker are kept up to date by the app as a way of providng a check on whether the user has entered any data incorrectly. For example, if the user had failed to register that the team had crossed midfield, and had chosen the 42 yard line in the quarterback’s team’s end of the field, the display would be in black instead of red. As a further means of insuring ball movement is recorded in the proper direction, the user has two buttons to choose between for plays from scrimmage other than quarterback passes—”Other Loss” and “Other Gain”. If a gain has been chosen, then the new line of scrimmage must be in the right direction for a gain. The other buttons are to be used for what you’d expect given their titles. Kicks and turnovers lead to the other team having the ball, as do touchdowns. The “Go on Def.” button also gives the other team the ball, but shouldn’t be used except to correct a user mistake or when there’s been a fumble lost after a turnover of some kind not on a play from scrimmage (e.g. fumble lost on punt return).

Using OnScreen QB Stats just amounts to keeping track of the line of scrimmage and recording pass results. The app does all the calculations, including yards gained on passes. Recording pass results for a game on television can be challenging because so few announcers now state where the ball is after every play (I’d guess less than 25%). The line of scrimmage is often not shown until right before the snap, and it can often be difficult to see where a runner was tackled due to the camera angle when the tackle occurred (followed by the three replays with no view of the sideline markers). Even a televised game can be followed smoothly, though, after a little practice.

I think I can safely say that as of now there is not another app that allows one to record all of these passing results and view these stats for quarterbacks during the course of a game. So I’m hoping word gets out to those crazy folks (like me) that might like to have that power. If you know one, pass the word. It’s on the iTunes App Store here.

IPhone App Updates and Experiences

December 22nd, 2009

The biggest news on the app front is that OnScreen Science’s second iPhone app, OnScreen QB Stats, an app for recording, calculating, and reviewing the passing statistics of quarterbacks during and after football games, is now available on the iTunes App Store. I’ll devote another post to that soon, maybe tomorrow, but I want to catch up here on app number one, OnScreen Pitch Count.

OnScreen Pitch Count went on sale from the iTunes Apps Store August 26. I won’t go into the details of the typo I had in the press release I sent out or dwell on how the video I posted to show the app in action worked fine on a Mac or Windows PC, but not an iPhone. That’s all in the distant past, fixed and forgotten.

Once the app had made it to the iTunes App Store, I was looking to find reviewers for it to help get the word out. I’d had magazine reviews of my science education software in the past, all of them quite favorable (a four-star Macworld review of OnScreen Particle Physics caused a major uptick in sales years ago), but not in a long time and never, of course, for an iPhone app. My number one hope was that the Macworld web site would post a review. As luck would have it, Macworld had not long ago reviewed another pitch count app. That showed they had someone sufficiently interested and knowledgeable to do a review, but it might also make it less likely they’d want to devote space to another example in this little niche, even one that was better than the first, especially so late in the baseball season.

Apple provides every developer of an app forty “promo codes” for the free downloading of each new app or update. I sent a promo code with a review request to the email address of the Macworld reviewer, but never got so much as an acknowledgement. I hadn’t counted on a Macworld review anyway and had found other iPhone review sites (a good number of which are devoted solely to games) and approached a few of them. One or two review sites responded with the suggestion that I expedite a review by paying them. That I wasn’t about to do, and I wouldn’t really trust their reviews after knowing how they operate. A couple of reviewers took the trouble to download the app, test it thoroughly, and write a review of it, for which I am grateful.

The two iPhone app review sites that reviewed OnScreen Pitch Count were AppGirlReviews and JustAnotherMobileMonday (JAMM). I ran across the AppGirl on Twitter, and she was happy to take on the review (actually to pass it on to someone on her staff). I learned of the JAMM site via Google. JAMM had reviewed iScore, a baseball scorebook app, for the iPhone. This review showed the reviewer to be a baseball fan who liked to keep score during a game, which I thought, correctly as it turned out, made him a good candidate to review OnScreen Pitch Count.

Even though I felt the app was solid, and it had passed Apple’s review, I still felt some anxiety over the possibility, however unlikely, that a reviewer would uncover a crashing or data-scrambling bug. On that score I was quite relieved, as both reviewers had nothing but good experiences to report. There was plenty of agreement on the performance and power of the app and its ease of use, really, despite complaints about interface. The JAMM reviewer in particular disliked its looks, and I can’t blame him. I had used Apple’s Interface Builder’s oddly minimalist, totally two-dimensional rounded-rect default buttons for the interface.

My hope was that someone wanting to track a kid’s pitches wouldn’t be totally repelled by the looks, and I didn’t want to delay the app’s launch any more than I had to. Of course an unappealing interface can indicate overall lack of care, which by assumption might carry over to the actual functioning of the app. Fortunately, the reviewers used the app enough to see how well it worked. The JAMM reviewer couldn’t stand the app’s looks, but acknowledged that “like the story of the Ugly Duckling, there really is a fantastic and robust app hidden inside there.” In addition to general aesthetic objections, he wanted a more graphical interface (instead of labeled buttons presumably), but I confess I don’t know how to come up with something that would convey “ball” as well as the word. And so on. A great deal of experimentation went into button placement in fact during development.

For opposite reasons, which is interesting, both reviewers emphasized the limited market for OnScreen Pitch Count. The (male) AppGirl reviewer, in particular, seemed downright offended that I suggested in the app’s description that a normal fan might enjoy tracking pitches in a game he or she was watching. My claim was based on my own experience in testing the app, but the reviewer really took exception to the idea, noting that nonetheless he would let it pass and only report on how the app functioned. That is basically what he did, and he had plenty of good things to say, recommending it without qualification for coaches and parents of pitchers. But in closing he came back to say that otherwise it was of interest only to “fanatics,” and that it was “burdensome” to record pitch results. Despite all the positive things he’d said in the middle of the review (the only serious complaint was lack of email capability, which he thought was a “glaring” defect), he gave the app a mediocre numerical score.

The JAMM reviewer, on the other hand, felt the app would be of limited interest because a regular (not a fanatical) baseball fan wants to record much more than pitching data, as in a full scoring of batting and baserunning results. Clearly there is a wide range of fan interest in keeping personal track of what’s happening in a baseball game, from nothing to everything. I still think there are some that may want pitching stats in particular, since pitching is so important, especially when it comes to managers’ decisions.

I was so happy that both reviewers (real world people I’d never met) had found the app to work perfectly and to be of great potential use to its primary audience that I didn’t let any negative comments bother me. Really.

A little after the reviews appeared someone posted a user review on the iTunes App Store, which gave OnScreen Pitch Count five stars, but also mentioned the need for email. My first update would add email. This update (version 1.1) was approved and posted for sale on the iTunes App Store on September 17. After the update had been posted, I noticed the iTunes summary said that iPhone OS 3 was required for my app. Since I had gone to quite a bit of work (following Apple’s guidelines faithfully) to use the improved emailing capability of version 3, while providing downward compatibility with OS 2.2 (through use of weak binding and conditional execution, for the cognoscenti), I was not happy about this. My query to Apple was unanswered. I decided to live with it and move on to requiring OS 3 or greater for future updates. This affects iPhone customers almost not at all, but about half the iPod Touch users have yet to upgrade the OS, since they have to pay to do so. I recently discovered an iPhone developer discussion thread about this very problem of OS-requirement change as being due to an Apple bug.

Another user rating led to version 1.2. This user expressed the desire to see pitch results expressed in percentage form as well as total numbers. The update incorporating this new feature was posted for sale October 15. Finally, I addressed the ugliness issue and made the minimal, but significant, change to the use of better-looking buttons. The new buttons, while not photo-realistic, are pleasing I think, looking a bit like they’ve been rendered by colored pencil shading. Version 1.2.1 with the new look was approved as I wrote this.
basic
basic

Belichick Is Not a Gambler: He Played the Percentages Last Night

November 16th, 2009

What got into Bill Belichick, coach of the New England Patriots, last night to make him suddenly become a reckless gambler? That’s the question stunned New England Patriots fans have been asking themselves after he seemed to throw caution to the winds by deciding to go for a first down rather than punting in a key situation last night. The Patriots had the ball on their own 28 yard line in a fourth and two situation with about two minutes to play and a six-point lead in their game against the Indianapolis Colts. The Patriots went down to a crushing defeat when they failed to make the first and the Colts then scored 7 points to win 35-34. Naturally, Dan Shaughessy of the Boston Globe was pulling out all stops to express the monumental stupidity of the coach’s decision, saved from eternal ignominy (perhaps) only by its not having been made in a post season game.

I was as surprised as anyone when I saw the Patriots were going for the first down, but on further review, I am going to argue that Belichick made the right call. The timing of the call is crucial because the first down will be decisive if made. With lots of time to play, of course you punt. And for a random game picked out of a hat, this situation would seem to require a punt without a second thought. Get the ball away from your goal line and play prevent defense. What are the odds the other team can move 75 yards in two minutes in a high pressure situation? What are the odds you’re going to pick up two yards against a team geared to stop a short gain?

But this was not a random game between random teams. First of all, the two best quarterbacks in football were playing in it, and that has a strong bearing on the likely outcomes of different scenarios in the last two minutes of a game. One has to consider all the specific personnel of the teams and their current state of exhaustion, the crowd factor, and that real psychological edge people called “momentum.” No, this is not a question that has a universal answer, though Belichick may be one of the few coaches who would realize that.

In addition to Brady, the Patriots have other veterans of Super Bowl Championship teams, including the invaluable Kevin Faulk. These are players that actually get better in pressure situations. The starting point in a decision has to be what are the odds that Tom Brady will be able to complete a two yard pass to Kevin Faulk on third and two from the Patriots’ thirty? From what I’ve seen of these two clutch performers, I’d say about 80%. I’m sure Belichick has a better estimate. What if it’s fourth and two? The odds could go up a little because the Colts have to be thinking that the whole thing may be just a ruse to draw them offside. The Colts must be holding back until they are sure of the snap, thus giving Brady a fraction of second more time to make a decision and an unhurried throw. On the other hand, they aren’t going to be worried about deep coverage. Lets say the odds are that the Pats make the first down 75% of the time.

If they make the first down, the victory is basically cinched, game over. Thus the pass play gives the Pats a 75% chance of winning the game. True, if they don’t make it, based on the way the Colts have been moving the ball, the odds are great that they will lose the game. But of course that is not the comparison to make at this stage of the game with only two minutes to go. The chance of winning if the Pats go for the first down has to be compared with the chance of their winning if they give the ball back to the Colts, at say (best case scenario of negligible runback) the Colts’ 25 yard line. But what had just happened? The Colts had taken the ball 79 yards in 1:44. Manning had been sharp as could be. That means as sharp as anyone could be. The receivers had been sure-handed and were getting open. The Patriot pass rushers seemed tired. The game is in Indianapolis.

The decision formula is simple. Let the probability of making the first down be F, and the probability of a Colt touchdown after a punt be T. Then if F > (1-T), the Patriots should go for the first down. What were the odds that Peyton Manning would be able to get a touchdown in 2 minutes with 3 timeouts and the 2 minute warning to play with? Were the odds of a Colt touchdown greater than 25%? That’s the calculation Belichick had to make on the spot in a short time. If the answer to that question is a definite yes, then the Patriots should go for the first down.

One may argue about the chances of success with Brady throwing to Faulk to pick up a 2 yard first down. I think 75% is a reasonable number. I also think that the odds of Manning getting the Colts into the end zone after a punt were over 50%, which means Belichick’s decision, far from being crazy, was in fact the reasonable one. The main point is that the odds to compare are the odds of the Patriots making the first down and thus assuring the victory versus the odds of Colts scoring after a punt (not after getting the ball on downs). The decision formula F > (1-T) would still say go for the first down even if the chance of success was 60%, so long as the chance of the Colts scoring after a punt was greater than 40%.

Did Brady choke and overthrow Faulk? No, the pass was perfect. Did Faulk drop the ball even when hit? No, but he did take a split second to gain full possession of it after being hit right at the first down spot. Just enough to make the spot short of the first down marker. The Colts defense did just enough to get the ball back. But it was a close as could be, and the call could have gone the other way. Home field advantage may have helped there. The fact that it was so close just points out to me how likely success was.

Would I as coach have gone for the first down? No, like all normal human beings I would have punted and hoped. I wouldn’t have thought to make the proper analysis in the excitement of the game in the first place, and I wouldn’t have had the guts to go against what first glance intuition said if I had. But I now see that Belichick was both smart and courageous. It’s not as though he didn’t know the consequences of failure. He wanted to win more than he feared what the media and fans would say if he didn’t. Yep, the guy is one of a kind.

This is my first (and probably last) topical sports post, but it’s been so long since I’ve posted anything (tied up with iPhone app development again) that I thought I’d better go with something that caught my attention. Back to “normal programming” soon. Maybe.

August 6, 1945: Just Another Day in the War?

October 6th, 2009

Freeman Dyson is a man I admire as one of the physics greats from the early days of quantum electrodynamics and as an original thinker and writer on diverse subjects. I recently heard him speak at Tufts University, or rather read, as he announced he would do at the beginning, in order, as he put it, to avoid going on for two hours. Such is the effect of his physical presence and his economical, straightforward writing and reading style that I have a feeling I wasn’t the only member of the rapt audience thinking: “This may be the smartest person I’ve ever encountered.”

Dyson’s talk was divided into two basically unrelated sections. The first part was devoted to the topic of abolishing nuclear weapons and some of the obstacles, particularly psychological obstacles based on misconceptions, to achieving that desirable end. The second part provided a glimpse into a dangerous but exciting future in which home biotechnology is as wide-spread as home computing today. There would be no point in my trying to summarize the many thought-provoking ideas Dyson presented. I saw a video camera, presumably for the benefit of the overflow crowd mentioned to be in another room, so I’m hoping Tufts will make the talk available to the public. I will only mention one of the ideas from the second part: bio-engineered plants with silicon-based, black leaves to serve as living solar cells, ten times more efficient at solar energy conversion than natural, chlorophyll-utilizing plants.

Much of the first part of Dyson’s talk was devoted to the task of exploding a number of widely believed “myths” that, according to Dyson, stand in the way of progress in eliminating nuclear weapons. One such important myth being that unilateral actions of disarmament are to be avoided and that only multilateral agreements with cheat-proof safeguards should be pursued, Dyson cited a number of significant unilateral steps to limit or eliminate weapons taken in the past by American Presidents (all Republicans, as it turns out, perhaps not surprisingly), which were later reciprocated. I confess that I didn’t remember them all, and the list was quite impressive.

While I share Dyson’s belief that the continued existence of large nuclear arsenals by major world powers is a great danger, probably the greatest danger, to the world’s future, I have to question the importance of some of the “myths” he enumerated. If all Dyson’s myths must first be overcome, I am not optimistic, for not all his myth-busting arguments were to my mind convincing. The one that struck me as least plausible when he made it was his claim that Hitler’s acquisition of nuclear weapons would not have enabled Germany to win the war. As a counter to this Dyson just asserted that had London and Moscow been leveled in nuclear attacks, then the allies would have been motivated to reach Berlin all the faster, possibly triumphing sooner than they actually did. I would hate to have the case for getting rid of nuclear weapons depend on that argument.

The shakiness of that argument made me start to wonder about Dyson’s ability to objectively analyze historical questions of this type. I’m not sure why he feels that dispelling what he sees as a false belief about a hypothetical outcome to past history is essential, though I suppose he thinks it necessary to correct the idea that the development of nuclear weapons was ever in any sense a good thing and to expunge whatever prestige they may retain from having possibly served a useful purpose in the past.

One of Dyson’s myth-busting arguments did in fact make me question what I thought I knew about what had prompted the Japanese surrender in World War II. I of course had read and wondered about the question of whether the nuclear bombings had been necessary to bring about the surrender, leaving aside the moral issue involved in deliberately destroying whole cities. Dyson’s assertion went well beyond arguing that Japan would have surrendered without the bombings of Hiroshima and Nagasaki. He maintained that, contrary to the accepted view, the bombings had not been seen at the time as significant enough to initiate a crisis, or even special concern. He presented some historical evidence for the view that it was the Soviet Union’s entry into the war, and especially its invasion of Manchuria, that had prompted the Japanese surrender, with the nuclear bombings essentially being viewed by Japanese leaders as tolerable and not particularly noteworthy, only coincidentally having taken place at about the same time as the Soviet invasion, which had actually prompted a rapid surrender.

I don’t agree that destroying the belief that American nuclear weapons were taken to be a serious new threat by the Japanese war leadership is a prerequisite for convincing people of the undesirability of nuclear weapons today. The truth or falsity of that belief is certainly of historical interest, though, and Dyson’s surprising assertion that Japanese leaders had basically shrugged off the Hiroshima bomb led me to do some research on the topic. Yes, my “library” was Google.

I found that Dyson credits his current view on the Japanese surrender to the argument presented by Ward Wilson in an article called The Winning Weapon? Rethinking Nuclear Weapons in Light of Hiroshima published in International Security (Spring 2007) and available online as a pdf file. Dyson read his “myth-busting” argument about the Japanese surrender to the Tufts audience, and I believe what he read was very similar to the text of an earlier piece by him posted on the internet, though in his presentation at Tufts he elaborated much more on the psychological significance of the similarities of historical situations fifty years apart alluded to in point 5 below. I am going to discuss the way in which I think Wilson and Dyson have stretched and “cherry-picked” the evidence they present to fit their conclusion. I will bring in some outside evidence gleaned from my online research now and then.

Here follow Dyson’s basic (numbered) points from his online article along with my responses.

1. Members of the Supreme Council, which customarily met with the Emperor to take important decisions, learned of the nuclear bombing of Hiroshima on the morning of August 6, 1945. Although Foreign Minister Togo asked for a meeting, no meeting was held for three days.

I can’t see how any firm conclusion can to be drawn from this. It may be that Togo was just more perceptive than others. The singular nature of this attack, which had come as a complete surprise, not to mention President Truman’s promise to continue dropping atomic bombs until Japan capitulated, may have taken time to sink in. And of course the second attack of August 9 on Nagasaki, which demolished the wishful thinking which held the Americans couldn’t have made more than one atomic bomb, had not yet occurred. I read elsewhere that the meeting requested by Togo did not take place because the military members of the Council were unavailable. Given the split on the Council between advocates of peace and hardliners, there was perhaps some deliberate stalling involved.

Togo made an urgent personal report to the Emperor on the Hiroshima bombing on August 7, and came away feeling he had convinced Hirohito that surrender with only one condition (maintenance of the Imperial throne) was now a necessity. This in itself would seem to be sufficient proof that the Hiroshima bomb was being viewed as qualitatively different from conventional bombing raids.

2. A surviving diary records a conversation of Navy Minister Yonai, who was a member of the Supreme Council, with his deputy on August 8. The Hiroshima bombing is mentioned only incidentally. More attention is given to the fact that the rice ration in Tokyo is to be reduced by ten percent.

The diary that records the conversation is that of Takagi, the deputy, not Yonai’s. In it occurs the following (Takagi speaking), quoted by Wilson:

“I used to think that by September or October the domestic situation would rapidly deteriorate while you said it would start deteriorating in mid-August. Actually, the situation is getting steadily worse in many respects during these couple of days, especially after Hiroshima.”

“Especially after Hiroshima” seems more than an “incidental” mention. Rather it seems to be an acknowledgment by Takagi that the Hiroshima bombing may have been a tipping point in the populace’s willingness to continue the war. Yonai replies, “Bad news continues and the ration of rice in Tokyo will be reduced by ten percent after the 11th of this month.” Yonai, already convinced that surrender was necessary, and living in fear of a popular uprising if the war went on much longer, may have been less attuned than Takagi to the significance of Hiroshima, but I wouldn’t call this exchange one that gives “more attention” to the rice rationing, which came up in the context of discussing the ever worsening popular mood, Yonai’s ongoing concern.

Perhaps post-war recollections are not to be trusted as much as wartime diaries, but I did note in my online reading that Kido, Emperor Hirohito’s most trusted adviser, related that on August 7, after it had been confirmed that the Hiroshima bomb was indeed an atomic bomb, the significance of which was not lost on the Japanese, Hirohito had told him, “No matter what happens to my safety, we should lose no time in ending the war so as not to have another tragedy like this.”

3. On the morning of August 9, Soviet troops invaded Manchuria. Six hours after hearing this news, the Supreme Council was in session. News of the Nagasaki bombing, which happened the same morning, only reached the Council after the session started.

Let me quote the opening remarks of Prime Minister Suzuki at this meeting:

“We have been hit hard by the atomic bombing of Hiroshima. Now we have the Soviet entry into the war. It has become almost impossible to continue the war any longer.”

So the first words out of the Prime Minister’s mouth in this first meeting after Hiroshima refer to Hiroshima, putting the atomic bombing on a par with the Soviet attack. In other words, it is the combination of these two heavy blows that has brought them to the point where surrender is necessary. This was indeed before news of the Nagasaki bombing came.

The meeting time may have been changed as a result of the news of the Soviet attack, but we read in Wilson’s article that Yonai spoke of this meeting with his deputy the day before it occurred, thus it had been scheduled before the Manchurian news, I think it is clear that Hiroshima would have been a topic of serious discussion in any case.

4. The August 9 session of the Supreme Council resulted in the decision to surrender.

Here is a concise statement, which could make it appear that the Council came to quick agreement due to the startling development of the Soviet invasion. In fact, as I learned in my online history reading, despite news of both the Nagasaki bomb and the Manchurian invasion, the vote split 3-3 with three military members of the Council voting to go on fighting unless several unrealistic conditions were agreed to by the Americans. Unanimity was not reached by the Council until they were invited along with the rest of the Cabinet to an extraordinary midnight session by the Emperor, who did not, as point 1 implied, regularly meet with them.

It should be noted that HIrohito stepped far beyond his normal role and used his prestige to gain reluctant agreement to sue for peace with only the condition of maintaining the Emperor on his throne, which makes Hirohito’s reason for choosing surrender most important.

5. The Emperor, in his rescript to the military forces ordering their surrender, does not mention the nuclear bombs but emphasizes the historical analogy between the situation in 1945 and the situation at the end of the Sino-Japanese war in 1895. In 1895 Japan had defeated China, but accepted a humiliating peace when European powers led by Russia moved into Manchuria and the Russians occupied Port Arthur. By making peace, the emperor Meiji had kept the Russians out of Japan. Emperor Hirohito had this analogy in his mind when he ordered the surrender.

There are a number of things that need to be said about this point. First of all, it deals with what Hirohito said in the rescript to the military issued on August 17, 1945. True enough, this rescript makes no mention of the atomic bomb attacks, and it does refer to the Soviet Union’s entry into the war, though not to the invasion of Manchuria, which according to the analysis related by Dyson is supposed to have had a special resonance with an earlier historical event in the minds of those in the Japanese military. One can of course speculate on the significance of Hirohito’s approach, and I will join in the speculation below.

Now I want to mention a very important event which Dyson’s point 5 and Wilson’s article fail to take into account, which might be called an inconvenient fact for their theory. On August 15, two days before his rescript to the armed forces, Hirohito had caused to be broadcast to the nation a recorded radio address announcing his decision to surrender. In that message there is no mention of the Soviet Union, except in passing as one of the allied countries to which Japan was surrendering. But within that address occurs the following justification for surrender:

“…the war situation has developed not necessarily to Japan’s advantage, while the general trends of the world have all turned against her interest.

Moreover, the enemy has begun to employ a new and most cruel bomb, the power of which to do damage is, indeed, incalculable, taking the toll of many innocent lives. Should we continue to fight, it would not only result in an ultimate collapse and obliteration of the Japanese nation, but also it would lead to the total extinction of human civilization.”

Is there any doubt what this passage in the Emperor’s message is referring to? Is there any mincing of words about the results of continuing to fight? No, no nation without nuclear weapons could stand against one that had them. The Emperor saw the reality and spelled it out plainly, in his own voice, thus undercutting any future attempt to rally a defense to the last person of the homeland, before he’d even addressed the military.

At the very least Wilson and Dyson need to discuss this message to the Japanese people. Wilson acknowledges (though only in a footnote) that the nuclear bombs were “mentioned” in the Emperor’s message, failing to note that the Soviet entry into the war was not mentioned there or that the rescript to the nation preceded the one to the military by two days. Nor does the word “mentioned” do justice to the decisive way in which the new weapons were described in their “incalculable power” as making resistance futile. Dyson ignores the Emperor’s message to the people entirely. I suppose Wilson and Dyson might say that the common people wouldn’t have understood the argument about the Soviet Union, so that something closer to their experience, as the ones subject to bombing, had to be used as justification for surrender; but the fact remains that Wilson and Dyson chose to avoid the issue, as it clearly doesn’t fit their thesis that the atomic bomb attacks were barely noteworthy within the context of many devastating conventional bombing attacks and the paramount importance of the Soviet invasion of Manchuria.

The question Hirohito and others must have asked themselves was would the message of surrender broadcast to the nation be enough to induce the laying down of arms by the military, which for many months had been gearing up for a last-ditch defense of the Japanese Islands, with death before national dishonor the mind-set and with kamikazes already a major part of the defense effort? Here is where the Soviet entry may become very significant from the psychological standpoint. The Japanese military could still take pride in its initial successes against the Americans and the British and French empires, and it had made the Americans pay dearly for every small island they captured. But add to the forces already arrayed against them those of the Soviet Union, how could they be expected to win? They had started the war against the others, and so couldn’t surrender to them without admitting the war to have been a mistake from the start. Surrendering to the Americans after such a long and bitter struggle must have seemed particularly odious. Here is the Emperor’s reference to the Soviet Union.

“Now that the Soviet Union has entered the war against us, to continue the war under the present internal and external conditions would be only to increase needlessly the ravages of war finally to the point of endangering the very foundation of the Empire’s existence.”

That’s it. Contrary to what point 5 all but declares there was no allusion of “the historical analogy between the situation in 1945 and the situation at the end of the Sino-Japanese war in 1895.” Whether or not this historical analogy was really something the Japanese military would have seen and found soothing or is only a fantasy of this particular analysis, I can’t say. Barring some testimony from the Emperor that I haven’t seen, I think it is going beyond what is known to say “Emperor Hirohito had this analogy in his mind when he ordered the surrender.” In any case, this only speaks to the words chosen to get the military to comply with the surrender order.

There is certainly material in this history for a Rashomon sort of story about how the war really ended. I can imagine Truman’s telling, Hirohito’s telling, Stalin’s telling, just for starters. Obviously there are open questions. With the Soviet Union about to enter the war, why couldn’t Truman wait and see what impact that event had before dropping the bombs? Was there a rush to make sure the bombs ended the war and at the same time send a message to Stalin?

Would the two atomic bombs (or just one) alone have been sufficient to have ended the war without Soviet entry into the war? That is impossible to know since the bombing and Soviet declaration of war occurred so closely together. But had the Soviets decided to let the Americans continue the war alone, is there anyone (except perhaps Wilson and Dyson) that believes Japan would have held up long against still more nuclear bombs? Let us all be thankful that the end came when it did.

6. The Japanese leaders had two good reasons for lying when they spoke to Robert Butow. The first reason was explained afterwards by Lord Privy Seal Kido, another member of the Supreme Council: “If military leaders could convince themselves that they were defeated by the power of science but not by lack of spiritual power or strategic errors, they could save face to some extent”. The second reason was that they were telling the Americans what the Americans wanted to hear, and the Americans did not want to hear that the Soviet invasion of Manchuria brought the war to an end.

Well, I suppose some leaders may have lied to Butow (who interviewed many after the war and wrote a gripping history of the events leading to the surrender in Japan’s Decision to Surrender), though Kido only speaks here of military leaders convincing themselves that they were not at fault, which can be taken as an interpretation of events as much as a falsification of history. Where is the quote from the Japanese leader that the atomic bombs entered not at all into the decision for Japan’s capitulation? Is there not a single such truth teller? Speaking of Kido, quoted by Dyson above, he is also the source of my earlier quote about Hirohito having decided on August 7 that the war must now end as a result of the Hiroshima bombing.

The continued intransigence of the military members of the Supreme Council all through the events of August 9, would seem to make it clear that Hirohito’s intervention was essential to the decision for surrender, and from what I have now read I believe that what finally pushed this man to act in a decisive way was the threat of continued atomic bombing of his country. While this is speculation, it is a fact that the Emperor gave the atomic bombs as the reason in his message of surrender delivered directly to his people.

Back when I was a physics student there were certain kinds of arguments in physics that were called “swindles” because they skipped over difficulties to arrive at a desired result without really having proved what they claimed to. I doubt Freeman Dyson has ever had recourse to a swindle in a matter of physics, even by accident, but I feel he has let his worthy goal of eliminating nuclear weapons lead him into accepting and now promulgating a significant swindle on the question of the importance of the atomic bombings in the minds of the Japanese decision makers at the end of World War II.

Thinking of One Who Died on September 11, 2001

September 10th, 2009

A number of my posts here have noted the way my memory of past events is quite restricted. Only memories of certain events in my life—exceptional in the impression they made on me—have survived the decades, and even then in fragment and mist. I talked about this phenomenon in Something on Memories. I’ve actually become much more aware of it through my writing here, and I can’t say how typical it is.

As the fatal date September 11 approaches, I’m moved to write of one of those memories from my childhood that is dreamlike and without clarity of detail, yet definitely grounded in real events and with strong, undefinable feelings and impressions attached.

I know the setting, though not the exact date, of this memory. It was at my Uncle Herman’s house in rural Northeast Texas. Herman was one of my maternal grandfather’s younger brothers, perhaps the youngest. Although the two brothers lived only a short distance apart, there wasn’t much social intercourse between the two families, at least whenever I was there for summer vacation and holiday visits. The little community’s Methodist church was very important to my grandfather, but I don’t recall seeing Herman there, even though he and his wife lived close to it, on the same road. It could be that they went to a different church, but their failure to attend the same church as my grandfather would have made them seem less a part of the family and the community. In any case, we would see Uncle Herman in my uncle’s general store on a fairly regular basis. Almost everyone in the surrounding area would be there sometime or other during the week if only for the society.

As I recall him, my uncle Herman was a lively, outgoing man who liked to kid a lot. But in my memories of him from childhood a couple of things stand out more than his personality. One is that he had had his larynx removed due to cancer, which made his appearance quite singular and rather disturbing to a child that only saw him occasionally. I can remember him before the operation though, and before that alteration in his appearance and speech, the main thing that made him stand out in my mind was his hound dogs. On the few occasions I went with my grandfather to visit Herman, it seems we always saw him outside the house instead of going inside, as one would do on a normal visit. He had numerous coon hounds which he kept in an enclosure not far from his house, and the dogs were always part of the picture when we were there. I suppose he kept the dogs for his own hunting pleasure, but for all I know he bred them for sale. They were a noisy and undisciplined lot, and I did not like being close to them. I don’t know how many there were of them, but there were more than enough to intimidate a town boy who wasn’t used to semi-wild canines who lived for the thrill of the hunt in the company of men experiencing the same primal pleasure. I don’t know if they became agitated at the sight of strangers or from seeing my uncle, with whom I imagine they shared delicious memories of hunts and kills.

The event I am now seeking to recall was a large family gathering at Uncle Herman’s house. Perhaps it was a family reunion, though I have a vague feeling it might have been a wedding anniversary. It may be the only time I was actually inside the house. Large gatherings with relatives that one barely knows are not a great pleasure to children. This one was exceptional though, because among those present was a cousin I had never met before, a boy about my age named Jimmy, one of Uncle Herman’s grandsons, presumably just visiting for this special occasion. Jimmy and I hit it off immediately. Perhaps he had inherited something of Uncle Herman’s exuberance. All I’m sure of is that Jimmy and I had a great time playing together and that I liked him a lot. I think we must have run through the unfamiliar house a few times, because I have a tantalizing sense of what it felt like to jump onto and off the porch and can vaguely picture the room that opened to the porch. Cousins of my generation were not numerous in my family, and the unexpected discovery of a new one my own age was exciting, with its implicit promise that we would have many more days of fun together.

That was not to be the case. As far as I know, this was the first and only time I ever saw Jimmy. I have no memory of what he looked like. I’m not sure how old we were when we met; my guess is about ten. The very singularity of our meeting and the thrill of discovery must have preserved from that day a small pool of feelings and impressions deep in the cavern of my memory, long after the details of the event had evaporated. I know I would have wanted to see more of Jimmy, but I don’t remember wondering about him. Perhaps such fleeting encounters are not unusual in childhood, as grownups determine the where and when of our lives. Given the loose connection between our grandfathers, Jimmy and I may well have been in the same small area at the same time both before and after that day without being aware of it.

Now I need to say how the September 11 attacks brought me back to that day long ago when I met a new cousin. Talking to my mother on the telephone sometime after 911, I was surprised to learn that one of my cousins, whose existence was news to me, Jimmy Nevill Storey, a Houston businessman, had been killed in the World Trade Center, a trip to New York City having been timed with the worst possible luck. He was one of Uncle Herman’s grandsons. It was quite some time later that the memory of the family gathering at which I had met a delightful new cousin came creeping into my consciousness. Yes, he was the one, it had to be so.

There’s a lot to ponder in this: the way we led our separate lives, only crossing paths once, my presence at his grandfather’s on just that day being almost as much a matter of chance as his being a victim in the events of September 11, 2001; and the way my recalling our single meeting was only the result of the circumstances of his death, which made me search my memory for some recollection (for if I’d heard that a cousin I didn’t know had died of a heart attack it probably would barely have registered and wouldn’t have set the wheels of my memory into motion).

I wonder what it would have been like to have met Jimmy as an adult? Would we have remembered our first encounter from so long ago? Would we have had enough in common to have felt even a small fraction of the rapport we’d felt our first meeting? He was a businessman and a graduate of Texas A&M, whose students—”Aggies” then and forever after—have traditionally viewed and defined their school as the polar opposite of my alma mater, the University of Texas (with its “tea-sip” students). I think A&M at that time was still all male, with military training a requirement for everyone. That was definitely not my cup of tea. Given that we were roughly the same age, we would have been cheering for opposite sides in the big rival games between our two schools. Scratch “cheering.” Aggies make a point of saying they don’t cheer; they yell, and have yell leaders. Jimmy and I probably would not have agreed on the Vietnam War had we met while it was going on. Perhaps those accidental facts of our lives would have been insurmountable barriers to connection. Such thoughts can make me long for the simple days of boyhood.

As with other victims, a few details of Jimmy’s life can be found on the internet. I came across a web page that had the text of an article from the Houston Chronicle, which had details I found touching. It was transcribed on September 26, 2001, but the actual date of publication wasn’t stated. The memorial service for Jimmy reported in the article was held only after the family had given up any hope that he could have survived. He had been on the 99th floor that morning. The article implies that he must have lost his father at a rather early age; and a cousin of mine has told me Jimmy’s father died at around the age of forty. Jimmy’s mother is quoted in the article as saying “He was kind of thrown from boy to man real fast, but he handled it well. He was a very devoted son, a very, very good father to his children.” Jimmy Storey was just one of many who died that day, but he’s the one I’ll be thinking about this September 11.

OnScreen Pitch Count Now On Sale on iTunes App Store!

August 29th, 2009

OnScreen Pitch Count, my iPhone “app” for recording pitch results in a baseball or softball game has been approved for placement on the iTunes App Store and is now available for purchase, in the Sports department, naturally. The past couple of posts here (OnScreen Pitch Count: An iPhone App Preview and How I Made a Quick-and-Dirty Six-Minute Demo Video of My iPhone App) have been devoted to describing the app and my efforts to get it ready.

The only way to sell an app for the iPhone and iPod Touch is through the App Store, and Apple has to approve individually every app that goes on sale there. The estimated time for this approval had been quoted as about two weeks when I submitted OnScreen Pitch Count on the night of August 12. I hurried to get it done then because I was going to be out town for five days, visiting family.

I spent the next couple of weeks wondering if I’d somehow introduced a fatal bug at the last minute (“impossible,” but still one thinks about the impossible sometimes) or if the reviewer at Apple might be someone that didn’t know the first thing about baseball. The evening of August 26 arrived, and OnScreen Pitch Count still hadn’t been approved. Then, almost two weeks to the hour since I’d submitted my app, I got the email saying it was now on sale on the iTunes app store.

Sure enough, within an hour or so the link embedded in my email worked to take me to the OnScreen Particle app’s display on the iTunes App Store. Sure, it’s too late in the baseball season to make many sales now, but it’s still a good feeling to know the app has been approved.

Let me quote a couple of paragraphs from the iTunes app description:

OnScreen Pitch Count from OnScreen Science, Inc. is an app for anyone wanting to have the pulse of a baseball or softball game at his or her fingertips. Pitching is the key to the game, and with OnScreen Pitch Count you’ll have data that even the tv analysts don’t. You’ll know how many pitches each pitcher in the game has thrown and exactly what the net results of those pitches have been.

Whether you’re watching your favorite team play, listening to a game on the radio, sitting in the stands at your child’s Little League game, or coaching a game in which extra pitching data could help you make the right decision, you’ll find OnScreen Pitch Count enhances your enjoyment of the game as it increases your understanding of it.

If you enjoy following baseball or softball, and especially if you coach it at any level, you should check OnScreen Pitch out. Even if you don’t really need it until next spring, you might as well get it and learn it now. I welcome comments and questions. See the email address in the right hand column.

How I Made a Quick-and-Dirty Six-Minute Demo Video of My iPhone App

August 24th, 2009

My iPhone app OnScreen Pitch Count (submitted to Apple, but not yet approved for App Store placement) is easy to use. Even so, describing how it works, using only words and still images can be tedious and may give the impression that it’s more complicated than it is. The draft user’s guide for OnScreen Pitch Count details what every screen button is for. Most of them should be immediately obvious, but the sheer number of buttons might make learning seem an unpleasant task, at first glance.

I clearly needed a video presentation of OnScreen Pitch Count that showed both how to use the app and what it was to be used for. Not knowing either the timetable or the exact procedure for the Apple review, I also felt the need to get something online as soon as possible, just in case an Apple reviewer, with the app’s fate in his or her hands, came to the web site looking for help in using it. I originally thought that a video of me or someone else tapping the buttons on the screen would be best, as being more realistic and possibly making the viewer want to start doing the same thing. That may be true, but given my resources and my impression of some rather pathetic online videos of iPhone game play, where the player’s fingers really got in the way, and the focus was poor, I decided to opt for making a screen recording of the app running in the iPhone Simulator, which Apple provides for testing apps under development.

Since most button taps lead to the tapped button’s being highlighted, it should be easy for the viewer to follow the action, imagining the invisible finger or thumb of the user. I already had used a Macintosh program iShowU for making a screencast demo of OnScreen Particle Physics, OnScreen Science’s modern physics teaching software, so my first thought was to try iShowU. First I went to its web site to see if there was a new version. There was, one that required Mac OS 10.5. This raised the question of whether the version I had would run under 10.5 at all. Since there was a discounted upgrade price I decided to look into the upgrade. Unfortunately to get to the upgrade page, one had to enter a password, the meaning of which was not explained anywhere I could see. I decided to launch the older version to see if the password might be found there. The good news was that the older version launched OK under 10.5, but the serial number turned out to be extremely long and with no way to copy it. Perhaps some old email would have it, but that was enough to deter me from the upgrade, since I wasn’t even sure the serial number was in fact the required password. I decided to see how well version 1.7.2 would work before revisiting the upgrade or alternative software question.

iShowU provided an easy, intuitive way to capture just the portion of the screen I wanted. There was a draggable, resizable rectangle, which I could put exactly over the iPhone Simulator’s on-screen representation of the iPhone device. The on-screen instructions said to hit return to set the recording area. Nothing happened to indicate that the capture rectangle had been registered when I did that (several times). It seemed this might be an incompatibility with 10.5, as I had feared. What else to do but try quitting and relaunching? That did the trick, though as usual in such cases, I’ll never know why. I did a couple of short practice runs. It was working, saving a QuickTime mov file to the desktop, each time. I then plugged in my USB microphone, the Blue Snowflake, and tested it with commentary enough to see that the audio worked. About a megabyte seemed to be required for each minute of recording, which I thought was within reason.

Clearly, though, I could not just improvise my way all the way through a demonstration. I would have to script it, and try to keep it around five minutes. It was immediately apparent to me that methodically going through the use of each button would be boring, and probably impossible to do without a context for the button usage. At the risk of sounding dumb, I decided to use a made-up game scenario, which I would narrate sparingly, to illustrate the app. I typed the script as fast as I could, thinking of it as a first draft. Looking at it now, I can see a couple of things I might have added, and a couple of places where the order might be improved, but it covers most aspects of the app’s usage to record pitch results in a game. When I do it again, I’ll probably include a runner caught stealing and a batter reaching base after a dropped third strike. I definitely should have shown the use of the Undo button, but its visible presence hopefully makes the point that it is possible to undo actions.

Now, how to do it physically? The script went beyond one page, but I didn’t want to have paper rustling sounds recorded, and I needed to have my hands free to use the trackpad and keyboard on my MacBook Pro anyway. I should note that I turned off the mouse cursor recording feature of iShowU since I didn’t want the movement of a mouse pointer across the screen to be highlighting continually that this was a simulation on a computer screen. I didn’t try to get a visual display of mouse clicks (simulated button taps) since the mouse clicks almost always highlighted the button anyway. One place where the simulation didn’t match the standard iPhone screen was when I typed in names. The iPhone keyboard appeared in the simulation, but I would have had to click with the mouse pointer on each letter in order to show the big letter that appears beside the tapped key. This would have been much too slow, so I just typed on the computer keyboard, which accomplished the job much faster, but without the usual visual display.

I decided to lay the two pages of the script out side by side to avoid the paper handling problem. It was still challenging to go back and forth between the screen and the script, and I lost my place a couple of times and had to do some improvising. The result was bad enough in one six-second interval that I decided to edit the audio track, which I’ll tell about below. I may do more editing later. The method I used for script page display wouldn’t work for anything longer than what I recorded. Maybe I could use a page turner the way pianists do.

Despite the less-than-perfect delivery and the deviation from the script in places, I went ahead and posted the demo as recorded, copying the javascript code I had used previously to play the OnScreen Particle Physics QuickTime demo. One place where my voice trailed off while I obviously searched for what I wanted to say seemed worse and worse the more I thought of it (played it, actually). I wasn’t sure how to edit the audio part of the mov file, but I knew there had to be a way to replace the flawed section. I had Audacity, the free audio recording and editing software distributed under the GNU General Public License, on my hard drive, so I thought I’d give it a try. Audacity imported the mov file via the Open command. I was able to locate the problematic section without any trouble and see that it was six seconds long.

Now what? I had to record a replacement for the bad section. I considered doing it with Audacity, but for some reason I don’t recall now I didn’t succeed immediately, so I decided to use QuickTime Player (Pro) as my recording software. Recording with QuickTime Player proved easy once I realized I had to set the input source as the Blue Snowflake microphone via the Preferences panel, just as with Garage Band. I recorded what I thought was a major improvement both in wording and diction. I then opened the file with Audacity and located the beginning of the substitute sentence. Since it was spoken without hesitation or searching for words, it took a considerably shorter time than the original one had. In order to keep the rest of the audio in synch with the video, I just selected six seconds from the new recording, which included a good bit of silence at the end. I then went to the old mov file audio track, which still had the undesirable six seconds selected, and did a paste. Would it combine the two, insert the new audio before the old, or replace the original as one would expect? It replaced the original. I could now play right through the edited section without hearing any obvious “splicing” effects. I did regret not having given a little silence at the beginning of the new segment, but the result was well within the Guy Kawasaki “Don’t worry, be crappy” standard. I have a feeling anyone that knows there was an edit done somewhere will be able to pick out where it occurred, but it is definitely an improvement over the original.

I still didn’t have the new audio inserted into the video. A straight save from Audacity would only give me an Audacity project file rather than a mov file with a video track, so I did an export to AIFF, an Apple audio format I knew QuickTime could handle. It took a little bit of searching through the QuickTime Player Help, but I found the procedure for adding a soundtrack to a mov file. I opened the new AIFF file I’d exported from Audacity and chose Edit->Select All, then Edit->Copy. Then I opened the mov file with the original sound track and selected Edit->Add to Movie. I played through the “bad” spot and discovered I had just added a second track, so that both versions played in the six-second interval I wanted to change. No big surprise, but I had thought it might just replace the soundtrack. Revert. Then I rediscovered that Window->Show Movie Properties revealed the video and audio tracks of the movie. I selected the audio track and deleted it. Then I repeated the procedure for adding the new sound track and ended up with what I was after. I then replaced the online mov file with the newly edited one. The next edit will be much easier. One of the reasons for writing this is so that I’ll have it for future reference.

So, is a something-less-than-professional, hand-rolled video better than nothing? I have no doubt that it is. There really is no easy way to convey the app’s usage with text and still images. I plan to improve on this first video effort; and, as I await Apple’s approval, I may be moved to do the whole thing over, but I feel it is an asset already. You can see and hear the results here.

OnScreen Pitch Count: An iPhone App Preview

August 5th, 2009

I’ve been explaining the infrequency of my postings here as due to the time I’ve spent working on an iPhone “app.” Now that it’s about to be submitted to the iTunes App Store for inclusion on that exclusive online site for selling (or even giving away) iPhone apps, it seems I should give my devoted readers a preview of the app: OnScreen Pitch Count, the first iPhone app from OnScreen Science, Inc.

Pitch Count? “How could you take that long to make a pitch counter?” you may be thinking (and perhaps “How is it better than the mechanical clicker kind you can buy at the hardware store?”). Hopefully a description of what the app can do will answer both those questions.

The screenshot below shows the main display and the buttons one taps to record pitch results. Incidentally, I considered naming the app OnScreen Pitch Results since it more accurately describes what the app keeps track of, but that name is two characters longer than allowed before being truncated in the App Store listings, so I’m going with Pitch Count, which may be better anyway. The name of the current pitcher is displayed at the top. This example is from a moment in this year’s MLB All Star game.

The buttons in the lower green area are the ones that record each pitch result. One of my first tasks was to determine just what I wanted to keep track of. I referred to my own experience as a Little League coach and also as an interested baseball fan. I rejected the level of detail that would include pitch location and pitch type (curve ball, fast ball, etc.) as being more than anyone but a pitching coach or scout would probably want or be able to handle, not even considering the difficulty in coming up with a user-friendly way of recording that much information for each pitch.

basic
Using a basic knowledge of baseball and some trial and error, I came up with the buttons that are displayed above. In keeping track of strikes thrown we need not only to record pitches that add to the strike total in a given at bat but also the pitches that result in foul balls after two strikes have already been recorded or that result in balls being put into play, leading either to an out being recorded or to the batter reaching base. A great deal of thought and experiment went into choosing the size and placement of the buttons, which I have found to be easy to use in the actual flow of a game.

The bottom two rows of buttons are for recording pitches not put into play: balls and the three kinds of strikes. The Walk and Strikeout buttons are not enabled until four balls or three strikes have been registered. I found from experience that putting in the extra step of recording a walk or strikeout reduced the chance of error and made the situation that much clearer. The Undo button can be tapped to undo the results of as many as two pitches, for example for changing a ball into a called strike after a hasty tap made before the umpire had spoken. It can also, of course, be used to cancel an accidental tap of any button. When three strikes have been recorded, the Strikeout button is highlighted to indicate the next step, and all other ball and strike buttons are disabled until the strikeout is recorded or the strike call is undone. At any time, only the buttons that have meaning are enabled. For example, if there are no runners on base, the Basepath Out and Run buttons are disabled. At important steps such as recording the third out, the next button to be tapped is indicated by highlighting (as mentioned previously for recording a strikeout).

Above the two lower rows of buttons are those relevant to balls put into play and possible results with runners on base. As currently programmed, hits and errors are recorded but without the specific type of hit (single etc.). The Out button is tapped whenever a ball hit by the batter results in the batter being put out before reaching base or in a baserunner being forced out. A basepath out is recorded when a runner is put out not as the result of a hit ball, say caught stealing. In the case of a double play, both an out and a basepath out are recorded. This system of buttons keeps the hits, errors, outs, and current baserunners straight. The Other OB button is used to record batters reaching after being hit by a pitch and so on. It even has the option of the batter reaching first base after a dropped third strike, properly recording the strikeout while removing the out.

The middle yellow section above shows the current situation in the inning: outs, runners on base, and the ball and strike count on the hitter. The cumulative game totals of balls and strikes (including balls put in play etc.) for the current pitcher are shown above that section. A tap of the Details button brings up the cumulative game totals for pitch results, runs allowed, baserunners, etc. for the current pitcher, as shown in the screen shot below.

review

The pitcher whose results are shown above pitched only one inning as closer, but the same totals for every pitcher in the game can be brought up for inspection by a tap of the Review button followed by a scroll and a tap to select the pitcher from the list of those recorded (see below). All pitchers appearing in the game for either team can be recorded. Or, a single pitcher appearing at any point in the game can be followed alone, depending on the user’s interest. All of the data recorded in a given game is saved on the iPhone or iPod Touch and can be reviewed at any time with the OnScreen Pitch Count app.

list

When I started to work on this project there were no competing apps that I was aware of, but since then a few have appeared. OnScreen Pitch Count lies in between some that seem to be really barebones counters of balls and strikes (with limitations on the number of pitchers) and much more detailed “pitching scout” type apps that record more data but are aimed at tracking individual pitchers over time. I think OnScreen Pitch Count should find  a comfortable place in this niche of pitch recording apps. I’m pretty confident it can more than hold its own in usability and usefulness. As far as I’ve been able to tell from scanning app descriptions, OnScreen Pitch Count is the only app that properly charges runs to the pitcher that allowed the scoring runner to reach base even when the run scored after a relief pitcher had come into the game.

Of course, interrupting the pitch-recording to answer the iPhone or to play a game between innings has no effect on OnScreen Pitch Count, and it will resume right where it left off whenever it’s pressed into service again. This happens automatically for pauses of up to an hour, but you can resume any unfinished game at any time, whether after a long rain delay or after you’ve paused a game tape for days.

How much will it cost? I’m leaning toward $2.99. It would be worth a lot more than that to some people, but the way mass appeal apps have been forced to fight for attention on the App Store has led to popular games being sold for 99¢. OnScreen Pitch Count is not competing in the popular game market, but the depression in game prices has led to iPhone users’ expecting very low prices on anything they buy.

I should mention that I found in my testing of OnScreen Pitch Count, watching both local softball games and televised major league games, that the spectator experience was enhanced by following with such close attention and having so much information literally at my fingertips. I would have loved to have had the information when I was coaching Little League. It was a lot of work to program OnScreen Pitch Count, though the development tools Apple supplies are excellent. Further improvements and my next app (I have an idea!) will be easier, assuming I get on with it before I forget what I’ve learned.

In a day or two after I post this I should have more information about OnScreen Pitch Count up at this link: http://nondummies.com. I plan to have a video demonstration.

Sudden Death for Thirty Classmates

July 20th, 2009

Thirty of my high school classmates wiped out in a few seconds! Did disaster strike a class reunion? No, in truth they have been dying one by one over the years, while I was unaware of it, just as I was unaware of any details of their lives. But reading the list of the names of the deceased, as I did recently, was like reading in the paper that they had all been mowed down at the same time, and I was shaken.

This experience has made me realize how my life, divorced from contact with anyone from that time in my past, has been unrealistic in a certain way, shielded from the strongest material evidence of mortality, the numerous deaths of those my own age with whom I shared the rather unhappy years of my adolescence. Suicide and heart attacks and causes unknown to me—accident? AIDS? cancer?—have brought them down. The total represents roughly ten percent of our class, which seems reasonable, though the list is probably incomplete. Of the thirty dead, twenty-two were male.

Some of the names on the list I merely recognize as belonging to a classmate but associate with no face or personality. A couple of names are even below that level of recognition. A few names evoke phantoms I can almost but not quite make out clearly. Some names are attached to persons or events that have survived in my memory. Here are some I remember, without mentioning names.

The girl and boy whom I and the rest of the class gathered around to watch dance the “dirty bop” at the seventh grade Christmas party—they’re both dead. That girl whose ass caught my attention with such curious force (as I watched her walk out of the room one time in the seventh grade) that the event seems to have marked the beginning of a new phase in my life, as if some dormant primate instinct came to life at that moment—she’s not moving now, or ever again. The senior football player, whom I saw brutally put a sophomore player in his place (I picked a tooth up off the ground)—he’s no longer commanding respect on this Earth. The catcher that threw me out at third base in “Show Me Where It Hurts: Memory Illuminates a Few Moments of My Baseball Career” is gone as well. Our exuberant male cheer leader—silent now as old Marley. Dead also is the boy I envied as he related how a neighbor kid’s older sister had called him into her bedroom for an initiation I could only dream of.

My friend with the Ford convertible, one of only a couple of boys with whom I could talk about books, God, life, and death, now knows nothing—or perhaps everything—about what we pondered then. My fellow unexpected National Merit Finalist—he’s been dead some twenty years. A girl whom I imagined to have suffered, as one deemed so unattractive must, feels neither suffering nor joy anymore in this life. A boy that later served voluntarily in Vietnam and survived the war, now rests in endless peace. Another who went to West Point (and Vietnam too?)—also dead. An odd fellow I really didn’t like, who once in the ninth grade invited me to meet him after school for a “friendly fight,” is now among those I’ll never meet again in this life. How could that boy I knew as such a lively, smiling kid in junior high, before he slipped into the background for me, have come to such a static, stolid end? The boy I resembled superficially, whose name a friend would tease me with, owes any current resemblance to the embalmer.

Also on the list of the dead is the guy I heard relating matter-of-factly in the school cafeteria—not really as a confession, but not exactly as a boast either—the story of how well an older gay man had treated him, buying him expensive gifts. “Gay” not being part of our everyday language then, I’m pretty sure he called him “queer,” but with appreciation and affection that came through as he referred to his benefactor by first name. I didn’t know how to evaluate his experience then, and I still don’t. I have the feeling he didn’t either. I remember an earlier hair-raising ride home from an out-of-town football game with the same boy as he drove at high speed on the city streets; we stopped to retrieve beer from the back of a building, the site where he had earlier in the evening used the full beer cans as missiles in a battle with someone encountered on the way to the game. Had he tried to escape there, only to find himself cornered? Or had he and a different passenger been the pursuers? I never understood what had happened. The chance for him to clarify has passed away with his existence.

I’ve written this piece to convey the shock that I experienced on learning of all these deaths at once and then the contemplation I fell into about this new knowledge. I remembered some of the dead and have presented a few images of them, just to cast the light of memory on a moment or two of their lives. The moments I remember are by the nature of memory—mine anyway—ones that stand out because of something out of the ordinary in my experience, and thus they are not at all of the sort to give a full and undistorted picture of the person. Should any of my surviving classmates read this (and I know at least one will), I request you not to ask me about the identity of any of the people in these memories. Read the names and see what images your own memory pulls up. As far as relevance to the lives of those dead classmates goes, I could have made up my memories. To me these memories made the people real again, though, and let me experience more intensely the knowledge that they have left this world forever, trailblazers for the rest of us in the class, whose names will all surely join theirs on the list of the departed within the next three decades.

Some Google Search Examples to Start Off July

July 6th, 2009

“I’m shooting for one entry a week.” That’s what I stated when I first put this blog on the internet. The past couple of months I have fallen pathetically short of this. The main reason is that I have been spending time and mental energy programming an iPhone (and iPod Touch) “app.” It’s neither earth-shaking nor a potential fortune-maker, but I think it will be useful to baseball coaches (and the parents of pitchers) at all levels and to fans who might like to keep better track of how a pitcher is doing than they can from the statistics typically displayed during a game. The app is a pitch counter that allows one to record, not just balls and strikes, but also the kinds of strike (swinging, called, foul, or ball hit in fair territory), as well as the number of strikeouts (and what kind of strike the third one was), base runners (and how they reached base), runs allowed, batters faced, outs recorded, and of course total pitches thrown; all for any number of pitchers in a game. I’ll have more to say about it later when it’s finished. Anyone interested in being notified when it’s done should send me an email (address in upper right).

In lieu of writing one of my usual long posts, I’m going to share with you a few more of the Google search strings that have led people to this tiny spot in the great blogoverse. They will illustrate comical misdirections, obvious intention to come here, and ambiguous intention; sometimes giving me a glimpse into how the blog is perceived. I enjoy seeing them.

Even more so than before, the people coming here for advice on how to get their Macs to run at a lower temperature greatly outnumber all others combined. I’m just happy that I finally have a solution for most of these frustrated seekers of relief, as I related in “What a Relief! MacBook Pro Overheating Problem Cured—Really” and “Too Good to Be True? My MacBook Pro: First Cool, Now Quiet.

As an example of a mistaken visit, I’m pretty sure the person that searched Google for “pulled pork lowell ma delivery” was a Lowell, Massachusetts, resident who wanted barbecue brought to his or her door. Yet Google, a word matcher without the ability to judge intent, just noticed that I had recorded buying a pulled pork sandwich at a Lowell Riptide pro softball game where I had also noted a peculiarity in a pitcher’s delivery, and thus suggested this blog as a possible destination; which suggestion was, surprisingly enough, taken.

The writeup of that softball game (An Evening in Lowell: Mixing in a Changeup) also brought to this blog someone looking for “jocelyn forest left power line.” Not remembering who Jocelyn Forest was, I at first drew a total blank on the meaning of the phrase. I had to do the Google search myself to solve the mystery. Google put the Lowell Riptide game post at the top with:

‘On-Screen Scientist » National Pro Fastpitch Jul 30, 2008… effort to learn how to coach softball pitching, Jocelyn Forest, the Riptide pitcher, instead of landing with her stride foot on the “power line” … always landed well to the left of it—yet another example of someone …’

So the match was a good one, and it had been a technical comment on that particular pitcher’s delivery that had stuck in someone’s mind. Had it been Ms. Forest herself, worrying much later that she might need to change her pitching form a little if a casual observer was making comments about it?

The story of the dying and death of our guinea pig named Chestnut (Last Days of Chestnut, Guinea Pig) continues to bring a few people here every week. Some are looking for information on pet euthanasia or guinea pig health, but a few must have somehow learned of the specific story, as witness their searches for “chestnut the guinea pig” and (probably) “guinea pigs last days.”

It’s hard to guess what the searcher for “ginipig war pitchures” had in mind; really hard, unless he or she remembered having read both the story of Chestnut and another of my posts called “Souvenirs of the Pacific War” and just wanted to find the way back here to the blog. I give Google a good deal of credit for coming back with “Did you mean: guinea pig war pictures?” That searcher did come here or I wouldn’t know about it. Still I have trouble reconciling the spelling in that search string with the act of reading either of those two rather long pieces. Maybe the searcher meant “New Guinea” instead of “ginipig” (plausible) and had no inkling of this blog’s existence.

Some Google searches seem to be clearly aimed at a particular post of mine. “Dante’s Heavenly Vision and the Physics of the Proton” is almost certainly what the people looking for “protons god,” “holy trinity hydrogen atom,” “dante paradisio dark matter,” and “dante’s quantum physics” had in mind. On the other hand, a Presbyterian minister came to it after some sort of search on the Trinity and (perhaps) physics without prior knowledge of it. I know this because she emailed me to ask permission to quote from it in a Trinity Sunday sermon she was preparing. I’m still hoping to read the sermon.

There’s no doubt what the string “on screen scientist perfect italian woman” was meant to find, as there is a post archived here called “The Perfect Italian Woman.” However, “dna of italian women” is a puzzle to me, even though I can see how Google might suggest this blog, given the DNA software I sell, in addition to the presence of the post about my Italian experience previously mentioned. If the searcher for “italian woman are not good looking” was hoping to find confirmation here for his mistaken idea, he was disappointed. However, the search string “the perfect american woman” is actually pretty good, even if the searcher probably didn’t tarry here long enough to read the post and see that. I won’t rule out the possibility that it was a deliberate search for the Italian Woman post by someone who had already read it and just got mixed up on the name.

I can’t deny that it’s gratifying to see that a few people have sought this blog out using the phrase “on screen scientist” explicitly. Whether they were returning or had somehow heard the name from someone else, I’ll never know. Those that mention the name seem mainly to be interested in questions of science and religion. For example, I have noted searches for “theist on screen scientist,” “on screen scientist moral non religious,” “on screen scientist god no bible,” and “on screen scientist recognize god.” I’m a little surprised that I’ve come across to some as being irreligious or rejecting the Bible, because I wouldn’t characterize myself that way, though I am certainly not a Biblical literalist, and I would have some difficulty in saying exactly how my belief in God translates into Christian terms. Finally, I can’t imagine where the deluded searcher for “famous on screen scientist” got his or her information. If there were another one out there, and famous to boot, wouldn’t I know about it?