You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey guys, great job with the scoreboard... one little question: in the runs.json file what does the timestamp field represent? the time between two consecutive requests to the feed-server or something else?
And BTW, where is the feed-server?
Bests!
The text was updated successfully, but these errors were encountered:
The time.timestamp field in runs.json represents a snapshot number (revision) of the internal contest database. This is undocumented and originates from a legacy (original) design, hence the wrong and inappropriate name. Its intended usage is to keep track to which revision the last data update has been performed. If the feedserver is capable of deliver the changes only between the last revision (specified in that field) and the latest (e.g. changed_runs.json). However, I believe it is not mandatory as the scoreboard will also work if full run information runs.json is available (instead of partial deltas only).
BTW, In the following development version, I will fix the confusing name; some of compatibility might break.
I regret to inform that feedserver is not currently publicized. I should have released it earlier, but I have had no enough time to wrap it up. Hope I can make it soon.
Hey guys, great job with the scoreboard... one little question: in the runs.json file what does the timestamp field represent? the time between two consecutive requests to the feed-server or something else?
And BTW, where is the feed-server?
Bests!
The text was updated successfully, but these errors were encountered: