|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: [FRC Blog] Event Results and API Data
First opensourcing all the code they own would increase the quality of a lot of things.
|
|
#2
|
||||
|
||||
|
Re: [FRC Blog] Event Results and API Data
Quote:
Open source is essentially useless in an environment with forced deadlines. |
|
#3
|
||||
|
||||
|
Re: [FRC Blog] Event Results and API Data
Please tell us more about how allowing more about how the code getting more scrutiny ahead of time would make it worse. Can I sign up for your newletter?
|
|
#4
|
|||||
|
|||||
|
Re: [FRC Blog] Event Results and API Data
Quote:
If I put a document in a PDF and send it to you for you to review, that is open for scrutiny. If, however, I simply put the same document in GDocs and send you the link--with full editing permissions--that is open source. In code, open source could be pretty bad, DEPENDING on a number of factors. Particularly, comments and other documentation, work breakup, and even "code styles". But having the code open for scrutiny--that might help. |
|
#5
|
||||
|
||||
|
Re: [FRC Blog] Event Results and API Data
Quote:
|
|
#6
|
||||
|
||||
|
Re: [FRC Blog] Event Results and API Data
Quote:
|
|
#7
|
|||||
|
|||||
|
Re: [FRC Blog] Event Results and API Data
Quote:
|
|
#8
|
|||
|
|||
|
Re: [FRC Blog] Event Results and API Data
Quote:
|
|
#9
|
|||
|
|||
|
Re: [FRC Blog] Event Results and API Data
Looks like some of the data is online at the http://frc-events.usfirst.org/ website now.
However at least 2 of the districts that I've looked at the data is showing up for the wrong alliance. (Red is Blue, and Blue is Red). The 2 that I have looked at are FiM - Southfield and FiM - Standish. I was trying to watch a few matches of teams so looked them up to find out what matches they played in on FRC Events. Then watched the video on youtube and they are on the opposite alliance in the video. Not sure if they just transposed these the colors or what. But thought I would give everyone else a heads up. I also did not look at the Finals data or scores yet as I was just trying to do some scouting on teams that will be at our next event and see what they are capable of doing. |
|
#10
|
||||
|
||||
|
Re: [FRC Blog] Event Results and API Data
Isn't there a pretty swell alternative to the FMS that is open source, or am I going crazy?
|
|
#11
|
||||
|
||||
|
Re: [FRC Blog] Event Results and API Data
So, if they make the real FMS open source, does that mean everyone is going to run out and spend thousands (probably 10's of thousands) of dollars on servers, touch panels, routers, displays and all the other hardware required to make it actually work? As an experienced Software engineer, I can tell you that the system is most likely too complicated to accurately and reliably reproduce on a simple computer, at least to the point where someone could contribute to updating it. Isn't that why they released FMS Lite? It's a simple, low cost alternative to the FMS that actually CAN be run on a normal computer with no specialised equipment.
|
|
#12
|
||||
|
||||
|
Re: [FRC Blog] Event Results and API Data
Quote:
Quote:
|
|
#13
|
||||
|
||||
|
Re: [FRC Blog] Event Results and API Data
No, it's not open source, but I wasn't saying it was. I was saying it was designed to be used on cheap, easy to obtain hardware, unlike the real FMS.
And also, it hasn't been years since it was updated. It was updated just last year for the 2014 season, and I would assume it will be again this year. http://www.usfirst.org/roboticsprogr...lite-available |
|
#14
|
||||
|
||||
|
Re: [FRC Blog] Event Results and API Data
Quote:
|
|
#15
|
|||
|
|||
|
Re: [FRC Blog] Event Results and API Data
Allow me clarify my statement:
Given the talent of our community, I know putting the FMS and STIMS/VIMS on Github would result in useful, bug fixing, and feature adding pull requests. It wouldn't take away control from FIRST but would allow motivated mentors and students to help. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|