User Pass
Home Sign Up Contact Log In
Forum > Suggestions > Make weight not such a gigantic factor in realized speed
Page:
 
TrevJo
offline
Link
 
This next game I'm going to put them on the kick return team instead, so there is no weirdness with the kickoff. I believe kickoff coverage team is slowed down to stay onsides before the kick, and I've also heard they can't go faster than a certain speed until the ball is caught. (These guys probably weren't fast enough to hit that limit.) But I think the return guys just go.

BW1 MaxWT SS (225#) http://goallineblitz.com/game/player.pl?player_id=1950530
BW2 MinWt TE (220#) http://goallineblitz.com/game/player.pl?player_id=1950524
BW3 MaxWt TE (266#) http://goallineblitz.com/game/player.pl?player_id=1950521

OU1 MinWt SS (199#) http://goallineblitz.com/game/player.pl?player_id=1950531
OU2 MaxWt CB (202#) http://goallineblitz.com/game/player.pl?player_id=1950515
FW1 MinWt CB (180#) http://goallineblitz.com/game/player.pl?player_id=1950517
FW2 MaxWt DT (340#) http://goallineblitz.com/game/player.pl?player_id=1950504
FW3 MinWt DT (270#) http://goallineblitz.com/game/player.pl?player_id=1950510
OU3 MaxWt OT (320#) http://goallineblitz.com/game/player.pl?player_id=1950536
OU4 MinWt OT (270#) http://goallineblitz.com/game/player.pl?player_id=1950539
Edited by TrevJo on Feb 6, 2010 18:07:55
 
Warlock
offline
Link
 
Originally posted by TrevJo
This next game I'm going to put them on the kick return team instead, so there is no weirdness with the kickoff. I believe kickoff coverage team is slowed down to stay onsides before the kick, and I've also heard they can't go faster than a certain speed until the ball is caught. (These guys probably weren't fast enough to hit that limit.) But I think the return guys just go.

BW1 MaxWT SS (225#) http://goallineblitz.com/game/player.pl?player_id=1950530
BW2 MinWt TE (220#) http://goallineblitz.com/game/player.pl?player_id=1950524
BW3 MaxWt TE (266#) http://goallineblitz.com/game/player.pl?player_id=1950521

OU1 MinWt SS (199#) http://goallineblitz.com/game/player.pl?player_id=1950531
OU2 MaxWt CB (202#) http://goallineblitz.com/game/player.pl?player_id=1950515
FW1 MinWt CB (180#) http://goallineblitz.com/game/player.pl?player_id=1950517
FW2 MaxWt DT (340#) http://goallineblitz.com/game/player.pl?player_id=1950504
FW3 MinWt DT (270#) http://goallineblitz.com/game/player.pl?player_id=1950510
OU3 MaxWt OT (320#) http://goallineblitz.com/game/player.pl?player_id=1950536
OU4 MinWt OT (270#) http://goallineblitz.com/game/player.pl?player_id=1950539


Sounds like a plan, but I would also swap the players out on coverage unit... reversing their placement from the first test, then you can compare/contrast the first set of results. This way you can look and see the minimum weight SS playing in the OU#3 slot vs the maximum weight SS in the OU#3 slot, as opposed to comparing the OU#2 slot vs the OU#3 slot. I think it's a necessary control to get accurate data.
 
TrevJo
offline
Link
 
I can try something like that on a day 1 scrimmage that we have scheduled.
But I believe the return team is going to give us purer results than the coverage team for the reasons I mentioned in my previous post. Also, I personally don't believe that the slots matter. The only difference IMO is what kind of cuts they make and how they end up pursuing and getting blocked after the ball is caught--which is the data you pretty much want to ignore anyway because it's very random.

P.S. These dots will be cut at the end of day 1, but I can keep them unretired probably through the end of the season if someone has an idea they want to sign them for.
Edited by TrevJo on Feb 7, 2010 00:22:09
Edited by TrevJo on Feb 7, 2010 00:17:27
 
nano4288
offline
Link
 
This may sound like an ignorant question, but isn't this whole pixel measuring stuff only going to work if the graphic representation of the script is actually that - an acurate graphic representation of the script? If you're trying to calculate differences in player speeds based on how those players are represented graphically you need to be 100% sure that those little dots are actually representing exactly what the script is doing. Are you 100% sure?
 
TrevJo
offline
Link
 
The graphical representation is definitely not perfectly accurate. We'll never know any answers to a very small margin of error. It's one reason to measure longer distances... the margin of error becomes relatively less significant.
 
nano4288
offline
Link
 
Yeah.. it just seems like you would need a lot of data to account for that error. In some of these cases were talking under 10 pixels and for all we know the dot that is shown to be 10 pixels ahead of the other is actually 3 pixels behind... or 18 ahead.
Edited by nano4288 on Feb 7, 2010 00:21:46
 
TrevJo
offline
Link
 
Originally posted by nano4288
Yeah.. it just seems like you would need a lot of data to account for that error. In some of these cases were talking under 10 pixels and for all we know the dot that is shown to be 10 pixels ahead of the other is actually 3 pixels behind... or 18 ahead.


I think the graphical data is reasonably accurate. I don't think it will show a guy behind who is actually ahead. It goes off the play's x,y data which is in increments of 0.25, where the length of the field is 360, so 1 = 1 foot and 0.25 = 3 inches. Anything less than 3 inches cannot be represented, and it's possible that two dots 4-5 inches apart could be represented the same. That's my understanding of it anyway.

BTW I think the page source (x,y positions) is the best way to analyze, it's easier than taking screenshots and counting pixels, but not by a lot, and it's probably no more accurate than the graphical display.
Edited by TrevJo on Feb 7, 2010 00:34:33
Edited by TrevJo on Feb 7, 2010 00:33:56
Edited by TrevJo on Feb 7, 2010 00:24:58
 
mwindle
offline
Link
 
There's a greasemonkey SPD script you really don't need to count pixels.
 
nano4288
offline
Link
 
Originally posted by TrevJo
I think the graphical data is reasonably accurate. I don't think it will show a guy behind who is actually ahead. It goes off the play's x,y data which is in increments of 0.25, where the length of the field is 360, so 1 = 1 foot and 0.25 = 3 inches. Anything less than 3 inches cannot be represented, and it's possible that two dots 4-5 inches apart could be represented the same. That's my understanding of it anyway.

BTW I think the page source (x,y positions) is the best way to analyze, it's easier than taking screenshots and counting pixels, but not by a lot, and it's probably no more accurate than the graphical display.


Thanks for the explanation. Never really looked at where the graphics come from.
 
DarkPraetor
This!
offline
Link
 
I think that weight is a very relevant factor to determine speed, but not by itself. There is another factor that we should consider and it is the % of body fat.

For example: we take two "identical" guys, that means same position, height, weight, build, SAs and VAs. If "Player A" has 20% body fat and "Player B" has 45% or more body fat, then who would have a better acceleration and top speed? I'll definitively bet for "Player A".

So, what is my point? Well, I believe that a system to determine the amount of body fat should be implemented. Maybe when you create a player you could choose the % of body fat you want just like you do with height/weight. And that % could be modified latter, pherhaps with training? or a new feature could be implemented for this: food. Food could cost in-game money (to have something to spend it in besides training) and it could work like this:

1) "Food A" (for example: salad) will be the cheapest and will eventually decrease your weight and % of body fat.
2) "Food B" will be a little expensive and will eventually decrease your weight but the % of body fat won't change.
3) "Food C" will be more expensive and won't modify your weight nor your % of body fat.
4) "Food D" will be more expensive and will eventually increase your weight but not your % of body fat.
5) "Food E" will be the most expensive and will eventually increase both weight and % of body fat.
 
Dr. E
offline
Link
 
Is someone trying to apply real life to a game again? This game like others has it's parameters and the only reason I've seen in this thread to change them is because someone want's them changed to reflect a perception of speed in real life. Speed to size isn't broken so I see no reason to make a change.
 
KingDan23
offline
Link
 
My WR was fat and it made him teh suck

+1 to OP.
 
Warlock
offline
Link
 
Originally posted by TrevJo
I can try something like that on a day 1 scrimmage that we have scheduled.
But I believe the return team is going to give us purer results than the coverage team for the reasons I mentioned in my previous post. Also, I personally don't believe that the slots matter. The only difference IMO is what kind of cuts they make and how they end up pursuing and getting blocked after the ball is caught--which is the data you pretty much want to ignore anyway because it's very random.

P.S. These dots will be cut at the end of day 1, but I can keep them unretired probably through the end of the season if someone has an idea they want to sign them for.


It's not that I think the slots matter, but in scientific testing, you want to remove as many factors as possible. Things like slot vs slot and KoC vs KoR are things you really want to have removed when comparing and contrasting data... just in case they do matter.
 
w_alloy
offline
Link
 
Originally posted by Dr. E
Is someone trying to apply real life to a game again? This game like others has it's parameters and the only reason I've seen in this thread to change them is because someone want's them changed to reflect a perception of speed in real life. Speed to size isn't broken so I see no reason to make a change.


The reason is because it is an arbitrary and therefor unfair criteria for success. None of the current high level players could have known the large difference weight made when they created their players.
 
Dr. E
offline
Link
 
Originally posted by w_alloy
The reason is because it is an arbitrary and therefor unfair criteria for success. None of the current high level players could have known the large difference weight made when they created their players.


Are you proposing that any time changes are made we didn't anticipate it's unfair and the game should be changed?
Edited by Dr. E on Feb 7, 2010 20:58:45
 
Page:
 


You are not logged in. Please log in if you want to post a reply.