Do you want help to develop this gem?

[RafaelMCarvalho]

Hello @gareth , If you are still engaged with this project, let me help you =)

To start, I have some questions:

How to use? What do has already been done? What do remains to be done? How can I help?

Cheers,

[wpp]

Yeah would be great to get a status update from you :+1:

[gareth]

Hey guys,

Thanks for the offer, I haven't had too much time to work much on it this season.

To be honest the best thing to do is just to try using it in some code and see if anything's missing that is needed. Take a look at my repo at gareth/live_f1-stream for a simple example that just takes the packets from the library and echoes them to screen. There's not a lot in this gem that I want to add without a specific reason, so what I need is to find out how people want to use it.

I'm pretty keen on not putting too much "analysis" into this gem. My original plan was that this library would just mirror the live timing servers, and then additional libraries could filter and process that data to provide different levels of analysis.

But like I say, check that you can get this going by trying something like https://github.com/gareth/live_f1-stream/blob/master/bin/live_f1-stream#L80 during a session and then tell me about any problems you have :)

Thanks again!

[psychemedia]

"so what I need is to find out how people want to use it"

I'm quite keen to use the live timing to log sector times so that I can do charts showing progression over the session.

For the race, a log of position info would also make it east to plot real time/fine grained lap charts (how quickly does the position information on live timing change? Does it update as cars pass between sectors?)

Ideally I'd be dropping the records into eg a mongo database (or even just a handy logfile), though I guess I'd need to think how the data would be stored there? Maybe a record that identifies:

• the session;
• the car number;
• the current lapcount;
• the sector times for a given lap;

Maybe one collection per session?

Off the top of my head, something like:

{"car":14, 'laps":3, "sector":{"sectorNum":1, "sectorTime":25.2}}

every time a new sector time appears would have the minimum overhead? That way I can get the sector times from a given lap, or the times across the session for a particular sector.

I guess other useful logfiles/database collections might be:

• commentary, with timestamp
• list of position updates {timestamp:, car:, position:}
• list of fastest lap times as they are made {'car': , 'timestamp':, fastlaptime:, lap:}
• list of laptimes {'car': , 'timestamp':, laptime:, lap:}