Lunt stretches out to try and put the ball down, loses control and it hits lomaxs leg?

Hohaia didn't even play the ball because the hooter went. A voluntary tackle only occurs if said player plays the ball.

Have you ever considered it stinks because you want it to?

Agree with both those, but the ball steal equalising penalty was very contentious.

It was, but the hand was in there even if it was a soft one.

That penalty was very similar to the one Savelio was pinged for against Leeds. I don't think either warranted a penalty.

This. For me, the only decision Huddersfield can feel aggrieved by is the Walsh incident (who played the situation like a pro) - but stuff like that goes on every week!

I disagree, that was a clear penalty for me.

McGilvary tackles Walsh, the ball comes free but Walsh regathers it before it hits the ground. McGilvary then tries to rip the ball off Walsh after the tackle has been completed which is a clear penalty. If anything he was lucky not to get sent to the bin for a professional foul due to it being after a break.

I'll throw it in there as we are questioning the ref. I did not think the Huddersfield first try was a try. If you watch the first replay. The huddersfield players left arm comes off the ball as it is stuck between his knee and the Saints player.

But when they go to the reverse angle it shows the ball on the deck and the video ref says he can see his left arm on the ball. He can't it's a Saints players arm.

Now it may have been a try but there are only 2 things for certain. His left arm was not on the ball. The ball did get on the floor but there was no definitive evidence of whether he kept his right arm on the ball. If he did not then he lost the ball as his left arm comes off when the ball is above the ground.

As for the Lunt no try, can't understand why anyone would question that, he losses the ball on lomax's leg. Therefore knock on.

Agree totally.

Didn't Lomax also get pinged for a ball steal in the second half which was 1 on 1?

What about the blatant forward pass in the build up to your 3rd try?

Decisions go for and against you.

Stop whinging like a b!tch about it. I've lost respect for Huddersfield this week after the comments coming out of the club including a pathetic statement.

Yupp!!

As always only the last dubious call is taken as the key call. That ball steal could have lead to a try for us and so the drop goals would be irrelevant.

Fans always go on about the last call and miss the 200 calls that are questionable before it.

All taken in isolation can be seen as key to the game. Take Saints v Leeds our penalty try that was never looked at, for a dubious knock on call. But it was not key in that we took control and continued to play to the final whistle.

Huddersfield could have won had they made 6 tackles and took it to golden point. They instead switched off and did not pin us down. Even if they took the drop goal there were 120 seconds left, plenty of time for a short kick off and our own try or drop goal.

I've had time to analyse the footage now and after running it through some software that is very similar to the hawkeye software you see used in cricket and tennis, the correct decision was given. The ball did miss the uprights, here's the images of the exact moments the ball crossed level with the crossbar.

Behind the stickshttps://i1069.photobucket.com/albums/u465/BackrowSaint/BehindSticks_zpsc7a0e08b.png" >rl

In front of the stickshttps://i1069.photobucket.com/albums/u465/BackrowSaint/FrontSticks_zpsfb851a13.png" >rl



I believe the issue with the behind angle looking like it went over is depth perception. Upon analysing the results I found that it looks like the ball crossed the point of the posts much earlier than it actually did. The ball when it left Brough's foot was travelling in the correct direction to go over the posts, when it reached halfway between brough's foot and the posts it had actually drifted enough to clip the posts 1/3 of the way across. By the time it reached the point of the posts it had drifted wide. This drift coupled with the false depth perception was the reason the ball looked like it went over when in actual fact at the real point of the ball reaching the try line it has drifted wide.

People wanted conclusive evidence, it doesn't come much more conclusive than that. I understand a lot of fans probably won't accept it out of blind ignorance because it doesn't suit them but the correct call was given.

Their "protest" thread is equally amusing. It's the claim that they're a "small club" so get victimised by refs against the "big clubs" ... Remind me where they finished last year?

Their ultimate argument is saints would be like this if it were the other way around. I'd be more concerned about why with 2 minutes to go we let them get from a 20 metre tap to within dropgoal range! Control your controlables and all that

Whatever software it is, (what is it?) it bears no relation to Hawkeye because you simply do not have the different camera angles to combine, GPS like, into a position in 3D space. There is no way to triangulate in three dimensional space from 2D images especially with no side on view, with any degree of accuracy and certainly not to pinpoint the position of this ball.

Secondly even if you were able to work out the precise frame in which the ball crossed the plane of the posts, you could not tell from the reverse view image which side of the post the ball was on unless the camera was precisely in line with posts and original kicking position, which we know it is not.

Finally, your shot from behind the kicker does not take into account that the camera is to the right of the vertical plane of the ball. Therefore you are entirely reliant on having correctly guessed the exact frame when ball and plane of posts co-incided. The evidence I have posted tends strongly to suggest your estimate is not correct.

I have no axe to grind and am just interested in this as an academic exercise (you may have noticed ) and I am afraid that your evidence is flawed and therefore not conclusive at all.

Let's put this to bed now. It was 100% a drop goal as we won by a drop goal. It's getting boring now.

There's three images, the two replay images and the original side on image of the live in play which is used to triangulate the images, though 3 angles is not ideal I completely agree, it's all I had to work with. The software isn't published and is something I'm working on in conjunction with a field leader at my institution so I can completely understand people not considering it credible if you wish to do so!

I can't go into too much detail (as I'm sure you understand, with it not being published) but it works, in a very basic form, by pin pointing an object and following it's path from differing angles, of which there was 3 but ideally could have done with 4.

In this circumstance the object was the ball, the front and reverse angles provided the trajectory in an 'x plane' whilst the side on angle provided a 'z plane', I had no 'y plane' to work with due to no angle from the top (spider cam would have been perfect in mapping any mid air movement the ball made and I could have actually provided a clear projection of the ball).

As it were I could only work out the frame in which the object passed a certain point. By analysing the flight of the ball from the side angle, until it went out of view, I could apply a simple SDT algorithm and find a time frame of which the object would have passed the point. By then comparing it against the front and rear angles and applying the same SDT algorithm you can get this point more accurately (I had to speed the replays up into real time by comparing the flight of the ball against the real time side angle which was a massive pain).

When I had found the frame which the ball crossed the plane of the points I plotted the line of the posts indefinitely and compared the relative position of the ball, which was outside the line of the posts. I completely understand what you're saying about the relative position of the camera but I don't think it makes too much difference in this circumstance, unless my calculations are way out and the ball is at least a couple of metres before or past the point of where I think it should be, which I don't think any error would be that large.

When I say the software is like hawkeye, it's in that it uses differing angles to analyse flight of an object, it doesn't use the same algorithms and as you've quite rightly pointed out a flight projection isn't possible due to the lack of angles but you can perform an accurate SDT object analysis from the 3 available angles.

Please do point out anything that you think may be wrong in the analysis as it'll help to hopefully get a more accurate and conclusive result. I just wish there was an angle from the other side or top as well as I could map that without any problem!