Quote:
Originally Posted by Elgin Clock
I think at the end of the day (and I've been through quite a many of these days going to 3 competitions, and one pre-season scrimmage) the top detail I personally (not my team per say, I won't speak for them) want to know from a scouting report is how many tubes a team scored.
If that was publically accessible as a hard data final number, and very accurate, I think we will see this data will help in scouting immensely.
...
I sense some long nights of hard number crunching. Oh wells.
|
(That stat was mentioned elsewhere.) So (a)there should be a computer or network where anyone can view the data collected, and (b)We need to make sure that the program used to share the data can take averages? I believe MARRS is web-based, so not too much of a problem on (a). Come to think of it, sundial might be a good option, but I can't imagine how the heck we "plug into it". As for (b), the programmers can speak for themselves. Worst case scenario, I've got the half-designed web app.
Quote:
Originally Posted by tjcasser
My thought is likely CSV or an XML format would probably be the easiest to use between the systems, as opposed to an INI. Both are fairly easily read or written with almost any software language. (CSV might be the easiest, since in theory it would also be readable directly in Excel.)
|
Quote:
Originally Posted by themagic8ball
An XML format would probably be the most readable but CSV would be the quickest to implement.
We need to decide what information we are going to have consistent becuase MARRS stores data on a match by match basis and I would have to implement an export/import option to just export the vital stats.
My vote is CSV.
|
Readability will be an issue. From what I've seen, any program that uses whatever format will need to handle extra info and missing info. Or everyone arbitrarily decides to use the same program and re-design the scouting system around the new program. That's why I prefer a well-labeled file format; so the programmers know that the data isn't getting mixed up. If that's a non-issue, then I'll start laying out the columns for CSV.
As for what data is the same, I thought I was going to be stuck with that since the post went "If you'd like to make a standard format..."? All I need is the relevant forms. I've got 768's already, just need to make sure I get the right one for MARRS.