Unofficial alternative @FRCFMS Twitter feed

[Dave Flowerday]

It seems that a lot of people are interested in the old @FRCFMS Twitter feed which appears not to be available this year. In the interest of supporting people who rely on that feed, we've developed an alternative feed as part of FRC Spyder that you may use. This is very last-minute so there may be a few hiccups, but we'll do our best.

You can find the alternative feed at https://twitter.com/frcspyderfrcfms

The format we'll be using is

#FRC{code} TY {matchtype} MC {matchnum} RF {redFinal} BF {blueFinal} RA {redTeam1} {redTeam2} {redTeam3} BA {blueTeam1} {blueTeam2} {blueTeam3} RFP {redFoul} BFP {blueFoul} RAP {redAuto} BAP {blueAuto}


We hope this helps some of you out.

[s_forbes]

Cool! I'm a bit curious though; I thought that the FRCFMS twitter feed was the only source for autonomous and foul point information. Do you have some other way of finding those numbers?

[plnyyanks]

Cool! I'm a bit curious though; I thought that the FRCFMS twitter feed was the only source for autonomous and foul point information. Do you have some other way of finding those numbers?

The new FMS API includes this data. You can see it in the documentation, here (http://docs.frcevents.apiary.io/#matchresults)

[Dave Flowerday]

We had to completely rebuild our FRC Spyder server infrastructure to connect to the new FRC FMS API:

http://docs.frcevents.apiary.io/

We've already implemented all the logic in our server to determine when changes occur - since this function used to be provided by @FRCFMS but is no longer available through their new API. So, we have the logic on our end now and it is fairly trivial for us to tweet out this information. As you can see from that API, auto and foul points are provided in the match results API.

[Dave Flowerday]

Just to be clear, if you're writing something new, you're better off going to the official API. We thought we'd put this out there as a stop-gap for anyone who had existing solutions coded against @FRCFMS on Twitter and who may not have time or desire to update their code to use a whole new API. Anyone in that category should be able to just point to our Twitter feed instead and hopefully things should just work.

[heuristics]

Has FIRST released any information on how to get a Token to use the API?

[Zach O]

Thank you Dave :)

[iLloyd]

Has FIRST released any information on how to get a Token to use the API?

I was already in the TeamForge (https://usfirst.collab.net/sf/projects/first_community_developers/) project before they sent out the keys. I'm guessing if you sign up for the project through TeamForge they will send you a key.

[Brandon Martus]

Thanks for this, Dave.

FRC-Spy (http://www.chiefdelphi.com/forums/frcspy.php?) on ChiefDelphi has been updated to point to that new twitter feed until I can move over to the FRC API.

As Week 2 events start up, I'll tweak the FRC-Spy output for this years game.