Mech Warfare MWScore Scoring System

[Upgrayd]

We do not really have a general scoring system discussion thread so I figured I would start one...

For the 2012 season we have worked very hard to provide a solid scoring system for this year and years yet to come.

Scoring System New Features:

Data Logging
Data from all matches is now logged and saved in a text format. We will now have a history of all match results.

Team Match Support
The scoring system now allows team matches to be scored. Any number of teams of any size are supported. 2v2? 1V1V1? 5V10V2? Yes yes and yes!

Match Data Broadcast
The most exciting new feature that we will demo this year is the ability of the scoring server to broadcast match data to other computers connected to the same network as the scoring server PC. Official score and time remaining can now be integrated into competitor's control systems.

Watch this short video demonstrating some of these new features:

http://www.youtube.com/watch?v=DIu0MV4z6gE

Open Design:

Scoring system source code, transponder firmware and transponder board design are all available to download now from my website (scroll to the bottom). Source will be added to a google code website sometime after RoboGames.

Questions, Comments and Concerns relevant to the MWScore system all belong here!

[Tyberius]

Absolutely fantastic job all around on the scoring system. Seriously people, we owe Ryan a lot for all the hard work and effort he put forth into this revamp.

[Mitch]

HUD question:

I don't know too much about python networking sadly...

Is your "SocketClient" over UDP or TCP?

Looks great and very simple to use Thanks for the hard work!

[Upgrayd]

Is your "SocketClient" over UDP or TCP?

IPv4 TCP

[Mitch]

IPv4 TCP

Gracias.




Up n' running in .NET (ala Unity in this case).

Lemme know if anyone wants source; i'll clean it up a bit.

Something I was wanting: The ability to tell how many teams there are, and which team they're on
I'm assuming for the case of Mech Warfare its going to be even teams (or just fill in a dummy bot) or something like that; but if we ever had a 3-team match or what not that "VS" symbol would be impossible to place without a liiiittle bit more info coming over the stream

[Upgrayd]

Something I was wanting: The ability to tell how many teams there are, and which team they're on
I'm assuming for the case of Mech Warfare its going to be even teams (or just fill in a dummy bot) or something like that; but if we ever had a 3-team match or what not that "VS" symbol would be impossible to place without a liiiittle bit more info coming over the stream

.Net!?

Match data is sent as a single string delimited by colons and includes the team each mech is on.

Example: MatchTime:MatchType:NumberMechs:Mech1Name:Mech1HP: Mech1Team:Mech2Name:Mech2HP:Mech2Name: ... MechNName:MechNHP:MechNTeam

MatchTime - Time remaining in match in seconds * 10
MatchType - 1 = Team Match, 2 = Free For All
NumberMechs - Number of mechs participating in the current match
Mech#Name = Name of mech
Mech#HP = HP total of the mech
Mech#Team = Team mumber mech is registered with in the match

So with that info you can determine how many teams are in the match and what mechs belong with what team. Teams can be unbalanced without filler "dummy" mechs.

[Mitch]

Awesome - so THATS what that third entry was for :P

I read your comments and your parser, but not your builder heh. Thats what I get for not being thorough :P

# MechName and MechHP for each mech in the modules MechList
for m in self.MechList:
data += ":" + str(m.Name) + ":" + str(m.HP) + ":" + str(m.Team)

Also, .NET!? Dont be hatin :P

[Upgrayd]

We are starting to make plans for canges to the scoring system transponder for 2013.

So far we have identified the following items:

• Reverse polarity input protection.
• Clear silk screen markings for input polarity, target panel inputs, and led indicator output terminals.
• Settable/Selectable transponder ID via onboard dip switches removing the need for each transponder to be programmed with a unique ID.
• Voltage regulator with larger input range and greater output current capacity.
• Decoupling capacitors on target panel inputs to help with the EMI some users are still experiencing.

Does anyone have any other changes they would like to see made or can share any other issues they had with last year’s transponder?

[gdubb2]

Sooo.. we're not going to be required to change them out again are we??

[Upgrayd]

Sooo.. we're not going to be required to change them out again are we??

I would think not but it is not totally up for me to decide.