Or anyone has the notebook of BilliardHertz.nb from Professor Jim Belk? It is appreciated that someone can share the 2014 code once again!

Even if it is a Mathematica 8.0 version is fine! As I have kept a Mathematica 8.0 in an old computer, I can run the Mathematica 8.0 code robustly!

Your article is very informative. As a billiards player I wonder what the best technique to break the rack in order to sink a ball, thus remaining the shooter. I'm assuming your analysis does not include horizontal rotation (english) of the cue ball as it hit the head ball of the rack. Also, can you evaluate a break from the rail at the first diamond as many players shot from this position. Is it the best position to sink at least one ball (not the cue ball)?

Cool, excellent work !

Suddenly, I come up with one interesting question for billiards. As Vitaliy shows the full range of billiard table, is that possible to calculate the possibility, that all balls fall into holes just by one-shot-break. Possible or not possible, for 15 balls, can it be proved or verified by mathematics.

I mean, it’s just from perfect physical and theoretical prospective. It will be very hard for human and need high precision, not for practice. I don't know, if any professional player has ever done before, or any recording for this very rare things.

Maybe, A further question, how many balls (those balls consist of an initial triangular billiard) can be done by one-shot-all-fall.

Anyway, I think the current model can be use to analisys bowling ball as well. Bowling game is simple than billiard, no bounce and no trajectory.

This comment on the reddit thread:

Assuming the two corner balls don't bounce back and interfere, it looks like this break would sink two of the balls in the side pockets on an 8 foot table: https://dl.dropboxusercontent.com/u/27794628/BilliardsHertz2.gif

links to the nice simulation below.

I attached corrected for V9+ notebook to this post.

I think Jim is using earlier versions. To make this work in V9+ the function NDSolve should have corrected method specification

NDSolve[..., Method -> {"DiscontinuityProcessing" -> False}]

and it is better for Manipulate to have SaveDefinitions -> True.

Attachments: