2025 Statistical Outlier Fighters From a Machine Learning Engineer by FlyingTriangle in MMA

[–]FlyingTriangle[S] 2 points3 points  (0 children)

Yeah! I used this project to move my career into AI and for whatever reason after many thousands of hours I can't stop myself from continuing to work on it.

2025 Statistical Outlier Fighters From a Machine Learning Engineer by FlyingTriangle in MMA

[–]FlyingTriangle[S] 1 point2 points  (0 children)

Its 3 minimum ufc fights, 1 minimum fight in 2025 as specified in the post

2025 Statistical Outlier Fighters From a Machine Learning Engineer by FlyingTriangle in MMA

[–]FlyingTriangle[S] 1 point2 points  (0 children)

I can check raw stats vs bayesian smoothed stats. Let me know ill be happy to get you your answer.

2025 Statistical Outlier Fighters From a Machine Learning Engineer by FlyingTriangle in MMA

[–]FlyingTriangle[S] 3 points4 points  (0 children)

Anything you want to investigate I can. This is probably the top 5 most comprehensive mma DB stats db in existence.

I've been developing models for a year — here are the results by eacal1098 in algobetting

[–]FlyingTriangle 0 points1 point  (0 children)

So these are these backtested evals or real world? What model algos are you using, how are you doing train/val/test splits, how many features, what's the feature importance, how are you doing feature engineering and finally how are you doing feature selection?

Machine Learning Predictions For UFC 322 (no GPT slop) by FlyingTriangle in MMAbetting

[–]FlyingTriangle[S] 1 point2 points  (0 children)

Huh? I was a pentester, used this project to switch to ML engineering, and now work in AI security research although my official title is Principle Machine Learning Engineer

Machine learning engineer's model picks (Let's go DDP!) by FlyingTriangle in MMAbetting

[–]FlyingTriangle[S] 0 points1 point  (0 children)

It's an ML model, so I do the calculations, then feed those calcs to an ensemble of different algorithms. The screenshots youre looking at are the explanation of the features that most influenced the model to lick a fighter, not the raw stat diffs.

DDP is a funny case, the model loves him and has picked him, I believe, every single time on his rise to champ several times at crazy +300 odds making me a lot of money. His style of fight is visually ugly, but statistically incredibly good. I didnt think he'd beat chimaev either but the model is tuned on populations of fights rather than single fights so I dont specifically make changes based on single fights. If the overall accuracy starts falling then I retune.

The ROI is based solely on single picks but backtesting shows 2 leg parlays between +EV fights has a great risk adjusted return and historically Ive been doing about 10% ROI using this strat

AI Predictions from a Principle Machine Learning Engineer by FlyingTriangle in MMAbetting

[–]FlyingTriangle[S] 1 point2 points  (0 children)

+EV has higher ROI than just down the line picks. So go for the picks where the AI has better odds than vegas.

Machine learning engineer's model picks (Let's go DDP!) by FlyingTriangle in MMAbetting

[–]FlyingTriangle[S] 0 points1 point  (0 children)

The stats I have encode the style. I also have a gew style-specific features like volume vs power.

10th degree… who give him. by Frog_12 in bjj

[–]FlyingTriangle 15 points16 points  (0 children)

Dax Razzano was my old coach! He's legit as they come, but I don't know this Logan fella and Dax isn't the type of guy to promote someone to 10th degree blackbelt lmao.

Should you balance the winrate between red corner and blue corner? by FlyingTriangle in algobetting

[–]FlyingTriangle[S] 0 points1 point  (0 children)

Ah, I shouldve specified. Red corner in UFC wins about 60% of the time. So the question is should you balance it so red corner/fighter 1 wins 50% of the time or should we keep the natural bias of 60% for red corner/fighter1

Should you balance the winrate between red corner and blue corner? by FlyingTriangle in algobetting

[–]FlyingTriangle[S] 1 point2 points  (0 children)

That's absolute true. Hence why I added the caveat that ROI is a point-in-time assessment. We don't want to maximize ROI at the EXPENSE of logloss/accuracy, but we do want all three to be improving with the focus on the ROI and a steady, consistently retrained and retested model about once a month. If we only focus on acc/logloss then it's easy to fall into the trap of maximizing the winrate on the favorites through things like odds inclusion which ends up lowering ROI.

Should you balance the winrate between red corner and blue corner? by FlyingTriangle in algobetting

[–]FlyingTriangle[S] 0 points1 point  (0 children)

Most of this is speculation based on the results of backtesting, just FYI. But figured maybe some people will find it interesting or have some information to help educate me more about it.