Mevo+ vs. Square Omni Head to Head Accuracy Comparison

I was briefly in possession of both units and did a head to head comparison outdoors. I am also a lefty for those that think the Omni is unreliable for left-handed players.

In summary:

  • Both units obtained shot shape and ball data that qualitatively agreed with the shot shapes I saw in real life
  • They share unanimous and close agreement on ball speed, ball direction, and most launch characteristics
  • For club data on irons, they shared excellent agreement on face and path data
  • For club data with driver, they disagreed significantly on face and path data, and I am inclined to think the Mevo+ was more accurate
  • Without a Trackman or GCQuad there is no gold standard for comparison, so “accuracy” in the title may be a misnomer and “agreement” more appropriate, but I found everything to be very close to expectations other than driver face/path data on the Omni

I think there are two ways to look at these — the shot-to-shot differences, as well as the differences when averages are compared to smooth out the noise.

Averaged club data:

The most notable finding in all of this was that the Mevo+ and Square Omni share excellent agreement for irons, but disagreed significantly on woods. As a lefty, I play a cut with my driver and accordingly am used to 2-3 degrees RIGHT for club path, with a face angle somewhere between square to the path or slightly left to path (i.e., 0-2 degrees LEFT to target). The Mevo+ was within what I expected with club path 2.2R with a face to path slightly left of that. The Square Omni felt my path was relatively square with a slightly open face. Ultimately this would also make a fade, so it has not made up false physics for these shots, but it arrived at that conclusion in a different way.

ClubMevo pathSquare pathMevo faceSquare faceNotes
Mini driver2.2 R1.9 L2.6 R3.0 RPath disagreement!!!
8 iron2.6 L4.1 L1.9 L1.5 LGood
Driver2.2 R0.01.6 R0.7 LEverything disagreement!!!
4 iron1.9 L1.8 L0.7 L0.9 LExcellent
7 iron3.3 L3.1 L1.1 L1.1 LExcellent

Averaged data (7 iron):

MeasurementNMevo+ meanSquare mean
Ball Speed11118.02 mph116.82 mph
Club Speed987.89 mph84.68 mph
Launch Direction111.32 L1.52 L
Launch Angle1114.06°14.30°
Carry11164.16 yd163.04 yd
Spin116,221 rpm6,496 rpm
Dynamic Loft1121.29°20.33°
Club Path113.29 L3.13 L
Face Angle111.10 L1.06 L
Attack Angle11-7.31°-3.78°

Averaged data (Driver):

MeasurementNMevo+ meanSquare mean
Ball Speed13152.90 mph151.64 mph
Club Speed11102.04 mph103.41 mph
Launch Direction130.35 L0.68 L
Launch Angle139.62°9.68°
Carry13245.55 yd240.07 yd
Spin133,016 rpm3,362 rpm
Dynamic Loft1311.02°11.37°
Club Path132.22 R0.02 L
Face Angle131.60 R0.73 L
Attack Angle130.46°1.15°

Shot to shot correlation with 7 iron:

MeasurementNMevo+ vs Square r
Ball Speed110.987
Club Speed90.474
Launch Direction110.810
Launch Angle110.974
Carry110.872
Spin110.513
Dynamic Loft110.930
Club Path110.456
Face Angle11−0.015
Attack Angle110.214

Shot to shot correlation with driver:

MeasurementNMevo+ vs Square r
Ball Speed130.968
Club Speed110.785
Launch Direction130.963
Launch Angle130.992
Carry130.862
Spin130.478
Dynamic Loft130.961
Club Path130.048
Face Angle130.729
Attack Angle130.154

Angle of attack had particularly poor correlation on these. The Mevo+ had me at 6-9 degrees down and the Square had me at 1 to 6 degrees down. Off to the right I have pictured the raw data, but with shots where one read -8 and the other read -1, this really killed the correlation.

angle of attack data and its r of 0.214

Methods:

Range balls were used, which run a bit spinnier and launch a bit higher on all shots besides wedges. But my goal is comparison so I don’t think it matters much. All balls were in good shape and I excluded a ball if it was well-worn with smoothed dimples which would affect the real-life aerodynamics, which is something the Mevo+ would pick up on as it is watching the actual launch and trajectory of the ball, while the Square Omni’s physics simulator / calibrated data would not.

I did my best to get a setup where the ball was in the ideal reading zone for both launch monitors.

Excel’s CORREL function was used to get within-club r values for each club and its ball data.

This is r, as in Pearson’s r, which measures only how well two variables move together, not whether they have the exact same values. So if the Square consistently under-reads some Mevo+ metric by 5%, but does so consistently, it can still have a perfect 1.000 correlation. So as alluded to in the first paragraph, this was more about correlation than accuracy, and all I can conclude from this is how well the readings tend to ‘move together’.

Below is an example of how this looked for ball speed for the 5 shots hit with an 8 iron. This was repeated for every metric and every set of paired shots within each club. I used assistance from AI to do this en masse once I confirmed it was doing so correctly for several data, because it was very tedious to do it all in Excel.

generating correlation for the 8 iron ball speed values, as an example
example of the r values being generated for face and path correlation for 7 iron shots. The L/R directions were all changed to +/- for easier analysis. Much like Trackman conventions for direction, POSITIVE is RIGHT and NEGATIVE is LEFT

Raw data for nerds:

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *