this is just a teaser. I would like to really really thank Thunderoo for showing me his tool, and getting me started down the path. without his work, I wouldn't have even thought about or started working on this.
Currently, it grabs a full list of plays from the box score, then i iterate through each play, grabbing the full details from the json(link pabst posted). This gives me almost a complete list of all details. I currently am able to tell the down/distance, yardline (opp 24; own 48), current score (off pts / def pts) this way you can look things in a more complicated matter. knowing field position, score, etc.
I have all this going into a local db. I have also parsed the complete playbook (off is completed, def is 75% done) and put them into the db. So, when you look at plays(via id) you know the formation and the play, so you can have separated hb slams, etc.
This will also allow the ability to see what formation is run most for run vs pass, or on 1st down, 2nd, etc.
My game parser, as it stands right now, will scout a complete game, and store it in the database in < 90 seconds.
this shows an alpha version of the scouting process with the tool. I still have some work to go, but I'm getting close.
http://youtu.be/zUsja8zquAE?hd=1
I am also in the process of trying to get this working with an online DB, so everyone won't be taxing the glb2 site scouting the same games over and over. it will look in the shared online DB for the game id first, if its there, it will pull the info from there, instead of run the scout (which would take about 2 seconds instead of 90). the more people that use it, the quicker the scouting effort becomes
as a side note, since i have all the plays parsed, and am building a way to update those (if any new plays are added), this should lead to the ability for a user to export their playbooks, and share(import [HOPEFULLY]). I should be able to export/import tactics also. This is a distant future part of my tool, as I want to wrap up the scouting and then REALLY blow out the analysis engine. After that gets stable enough, I will start working on import/export.
Currently, it grabs a full list of plays from the box score, then i iterate through each play, grabbing the full details from the json(link pabst posted). This gives me almost a complete list of all details. I currently am able to tell the down/distance, yardline (opp 24; own 48), current score (off pts / def pts) this way you can look things in a more complicated matter. knowing field position, score, etc.
I have all this going into a local db. I have also parsed the complete playbook (off is completed, def is 75% done) and put them into the db. So, when you look at plays(via id) you know the formation and the play, so you can have separated hb slams, etc.
This will also allow the ability to see what formation is run most for run vs pass, or on 1st down, 2nd, etc.
My game parser, as it stands right now, will scout a complete game, and store it in the database in < 90 seconds.
this shows an alpha version of the scouting process with the tool. I still have some work to go, but I'm getting close.
http://youtu.be/zUsja8zquAE?hd=1
I am also in the process of trying to get this working with an online DB, so everyone won't be taxing the glb2 site scouting the same games over and over. it will look in the shared online DB for the game id first, if its there, it will pull the info from there, instead of run the scout (which would take about 2 seconds instead of 90). the more people that use it, the quicker the scouting effort becomes
as a side note, since i have all the plays parsed, and am building a way to update those (if any new plays are added), this should lead to the ability for a user to export their playbooks, and share(import [HOPEFULLY]). I should be able to export/import tactics also. This is a distant future part of my tool, as I want to wrap up the scouting and then REALLY blow out the analysis engine. After that gets stable enough, I will start working on import/export.
