hckrnws

Curious how you generate the maps. OpenStreetMap turns out to have most golf course features mapped by volunteers, so it's possible to pull that data (see here for a fairly rudimentary example: https://github.com/npilk/hacker-yardage). But you may have a better source.

I see you mention looking for topographical data at a good resolution. I'll follow that with interest. There are US public datasets (IIRC) at more like 3m or 5m resolution... not bad but not really good enough for golf, especially greenside. I couldn't figure out how to pull that info programmatically in the past, though.

Overall this is super cool work, will be watching for more!

I’m barely halfway through the post, but I am already compelled to advocate the author to start pitching the USGA on using this to replace manual course ratings. Also, OP runs a labor of love in golfcoursewiki that democratizes basic info like green contours that are usually locked away behind annual subscriptions. They deserve a shoutout.

Some info for non-golfers: every golf course has a “course rating” and a “slope.” Course rating is essentially the “true par” of the course for a “scratch golfer” (a golfer who normally shoots par). The “slope” is a measure of how much worse less-talented golfers score compared to a scratch golfer. These numbers are used to compute a golfer’s “handicap,” which lets them compete fairly against more- or less-skilled players in tournaments.

Course ratings are currently assigned by people measuring distances from the tee box to various points of trouble and then to the green. This makes course length the dominant factor by far in terms of course rating. If we adopted something like scoofy’s inverse strokes gained metric, course ratings would become far more accurate, and they would become much cheaper (asymptotically approaching free) for courses to obtain. (Currently courses must pay to have their course rated.)

My previous best idea for fixing this was just to use the scores reported by players every day to nudge the rating toward its “true” value. But that would be subject to a lot of conflation that this simulated approach is not.

My immediate thought is that OP is reinventing dynamic programming/RL from first principles. The final visualization looks exactly like a standard value estimate heatmap. Golf is a MDP over all the physical points on the course, with stochastic probabilities of transition to each one based on golfer skill and physical randomness. Strokes are the cost to be minimized, the colors are the value estimate at each state, and his difficulties with the different maps is because a value function is defined as the expected value of being in that state assuming you will follow a particular policy thereafter (ie. be a golfer of a particular skill level, playing optimally for that skill). This lets you formalize 'strategicness' of a golf course: it is how much the value estimates differ on average across the full range of golf skills; a non-strategic course looks identical for the beginner and pro, while an incredibly strategic course might have completely different values for every point for every bracket of skill. (You could probably automate creation of pathological golf courses this way, where even a slight increase in skill makes the new strategy different.)

So, yes, OP here and you're effectively right on the money. Mark Broadie's strokes gain approach is literally dynamic programming applied to golf. He even discusses a bit of the history of dynamic programming in Every Shot Counts.

The point of what I'm doing here is pointing that strokes gained approach at the golf course instead at the player. Ideally, I'd like to continue working on it to build something that can help clubs make minimal, inexpensive changes while maximally improving the strategic interest if the way the course plays.

OP doesn't seem to explain what the lines are radiating out from the hole? I assume they're some sort of artefact from the simulations. There's no obvious reason for me why it's harder to chip in from these specific, evenly spaced directions.

Hey, yea, these are an artifact from the fact that I used a modified golden spiral as a way to regularly distribute the shot pattern within the probability density function. But yes, there are quite a few artifacts and shortcomings from the model. I do appreciate the attention to detail here.

This is sick. But also i think that stuff like this is making us less human. Before tournaments good players take a book with then and their caddie and do this themself. A model takes all the fun and strategy out of it imo. Like if i suck at 7-9 irons but am good with my 4-6 irons this type of work doesnt take that into account. Also likee the optimal way to play a course isnt very fun. We play at a course where on the fourth hole we always play to the fairway to the left cause of all the trees. If a player were to use this they wouldnt have been able to come up with such a fun way to play the game

This is my project and after publishing it today, and while I'm very flattered that so many folks have read it already. Still, I've found myself pushing back against this 'unweaving the rainbow' narrative.

The maps, importantly, don't tell you how to play the hole. They just show where the hole is easier to play from, if you're already in that location. Whether or not you ought to attempt to reach those areas is the choice the player makes, and it's going to be different based on what the strategy the player uses is. I allude to this in later image of Talking Stick O'odham #2, which has the internal aiming system tuned up to be aggressive (say, for a skins game), and another image where it is tuned down for safety (say, for a derby or defending a lead in a stroke play tournament).

The maps really just kind of "show the idea" behind the strategic design. The best use case would be for helping golf course architects communicate the changes they want to make to potential memberships, who might be hesitant to change they don't understand.

It's very much not a system like Decade, or ones that companies like Arccos can provide to improve performance.

https://golfcourse.wiki/ is down / degraded FYI (frequent 500/503). What is the best way to contact you? I have a related project you might enjoy.

It's mostly bots causing the 502 errors by overwhelming a the server that I don't want to pay much money for. Every few day I'll get 20K bots from Singapore and China banging the site all day.

I'll eventually spend time fixing the issue, but it works fine if you just refresh the page. I really should a "you broke reddit, please refresh" page to the 500 error page.

If you need to contact me, just use this tally link: https://tally.so/r/7R2Bla

Not a golfer but I'm a big fan of the pretty plots.

Someone get this in front of Tom Doak immediately

THIS IS THE COOLEST THING I'VE READ IN YEARS EVEN THOUGH I DON'T PLAY GOLF!

cheers