updated scoreboard of dallas regional

[ronlottem]

Originally Posted by twetherbee

Rankings read off by the announcer at the end of the day:

1) 987 101.5 avg
2) 148 81.4 avg
3) 118 77.2 avg
4) 1477 76 avg
5) 4300 (only gave the top 4 averages)
6) 4499
7) 2950
8) 647
9) 704
10) 457
11) 3350
12) 5431

thats what i was looking for actually.
thanks

[plnyyanks]

Updates from FIRST this morning:

Hi Dave,

I understand your frustration. We are working to resolve the issues with the API, but also must focus on supporting the
events at the same time.

The issue we are working through involves the data sync between the local computers at the events and our Azure database
which is the data source for the event web pages and the API.

Regards,
-Matt

...So I would guess we're not getting data this weekend

[Eugene Fang]

Hi Dave,

I understand your frustration. We are working to resolve the issues with the API, but also must focus on supporting the
events at the same time.

The issue we are working through involves the data sync between the local computers at the events and our Azure database
which is the data source for the event web pages and the API.

Regards,
-Matt

I don't get how a data sync issue between events and Azure causes the timeouts/500 errors we're seeing. If there is an issue with data sync, wouldn't the data served by the API just be stale?

[Ether]

Originally Posted by plnyyanks

I hope the data is being safely archived in the local computers, and not lost forever (like the Twitter data in previous years).

[Mike Soukup]

Originally Posted by Eugene Fang

I don't get how a data sync issue between events and Azure causes the timeouts/500 errors we're seeing. If there is an issue with data sync, wouldn't the data served by the API just be stale?

It would explain why some events have updated rankings, but not matches. It wouldn't explain the massive timeouts & 500 errors. They should be serving empty data. Unless they shut it down today because there were sync problems that only showed up when the DB was under a massive reading load. All speculation.

Until then I'll just reply to all the 1 star ratings for Spyder with a boilerplate "FIRST screwed this up, not us" message.

[Eugene Fang]

Originally Posted by Mike Soukup

Until then I'll just reply to all the 1 star ratings for Spyder with a boilerplate "FIRST screwed this up, not us" message.

Yeah, the ratings are rough

[plnyyanks]

No data from Week 1...

http://www.usfirst.org/roboticsprogr...s-and-API-Data

Event Results and API Data
Blog Date:
Saturday, February 28, 2015 - 13:29

Today’s brief blog is from the FRC software team:

We are aware of tournament data not publishing consistently for all events. The root cause has not been determined, and at this point, we don’t expect resolution for week 1 events. Because of this, developers relying on this data for their own applications will not be able to relay the data on our behalf. This issue only inhibits the data being reported out by events, and the results and rankings reported at events are unaffected. Please accept our apologies for any frustrations.

[Ether]

"developers relying on this data for their own applications will not be able to relay the data on our behalf"

Will the Week1 data remain unavailable even after the datalink problem has eventually been fixed?

"This issue only inhibits the data being reported out by events, and the results and rankings reported at events are unaffected"

But has the data been stored locally, and will it be made available retroactively? Or has the data been permanently lost (like Twitter data in 2014)?

[Swan217]

RoboVisionOD.com has match data for South Florida. I believe we're the only regional to do so.

[magnets]

This is very pathetic that Team 254 mentors can develop a superior field management system in several months outside of their regular jobs while FIRST, which is being paid, fails to have a working system for two years in a row.

The robots are held to a much higher standard than the field software.

[Bryan Herbst]

Originally Posted by Ether

But has the data been stored locally, and will it be made available retroactively? Or has the data been permanently lost (like Twitter data in 2014)?

The data is stored locally on the FMS.

However, I don't know if there are plans to make that data available to the API.

[Ether]

Originally Posted by Tanis

The data is stored locally on the FMS.

May I ask what is your source for that info?

And is that something new for 2015, or was it also being done in previous years?

[plnyyanks]

Originally Posted by Ether

May I ask what is your source for that info?

And is that something new for 2015, or was it also being done in previous years?

Ether,

I've been a Scorekeeper in previous years (so this feature may or may not exist this year, but I'd be pretty surprised if it weren't) and FMS would store results locally after every match. It would back up locally and to a flash drive, if one was plugged in. A full backup database would be triggered every 5 matches, or manually by the scorekeeper.

Additionally, at the end of the event, the Scorekepper would export a good amount of data (including match results) to excel format and give it to the FTA. I don't remember if that was standard procedure, or just good practice from the FTAs I've worked with.

I think it's a pretty safe bet the data exists somewhere, but it's a much bigger question if somebody will go through and take all that data off the field manually.

[plnyyanks]

Also, I've created a Google Spreadsheet to crowdsource match results from this week, in case we don't get week 1 data officially.

If you have any data, please enter it here:
https://docs.google.com/spreadsheets...6t4/edit#gid=0

[ATannahill]

Originally Posted by plnyyanks

Ether,

I've been a Scorekeeper in previous years (so this feature may or may not exist this year, but I'd be pretty surprised if it weren't) and FMS would store results locally after every match. It would back up locally and to a flash drive, if one was plugged in. A full backup database would be triggered every 5 matches, or manually by the scorekeeper.

Additionally, at the end of the event, the Scorekepper would export a good amount of data (including match results) to excel format and give it to the FTA. I don't remember if that was standard procedure, or just good practice from the FTAs I've worked with.

I think it's a pretty safe bet the data exists somewhere, but it's a much bigger question if somebody will go through and take all that data off the field manually.

This is still standard practice. Also standard practice is FIRST using a file transfer system, completely outside FMS, to pull the database from the field to HQ after the event.