Live data from Hacker News

Show HN: Undercutf1 – F1 Live Timing TUI with Driver Tracker, Variable Delay

github.com

41–50 of 76 posts

Re: Show HN: Undercutf1 – F1 Live Timing TUI with Driver Tracker, Variable Delay

#43
post #42

Looks great! However, I'd appreciate an easier way to run it: binaries for Linux aren't standalone -- they require 3rd party dependencies to be installed. Static binaries (or maybe container image?) would be nice.

Are you not able to compile this as "self-contained"?

Re: Show HN: Undercutf1 – F1 Live Timing TUI with Driver Tracker, Variable Delay

#44

TUI for sports reminds me that in Finland, teletext is still very popular for following sports (football, ice hockey, even F1) TUI gets you straight to the point, no ads, etc. So the teletext format is now outliving TVs and people read the teletext pages on their mobile phones (via we of dedicated apps) https://yle.fi/aihe/tekstitv?P=207

Oh that's fantastic, way better than searching for results on modern sports news sites. Definitely bookmarking this, maybe I'll accidentally learn a bit of Finnish.

>maybe I'll accidentally learn a bit of Finnish.

Your chances are slim, or mahdollisuutesi ovat niukat.

Re: Show HN: Undercutf1 – F1 Live Timing TUI with Driver Tracker, Variable Delay

#45

This is really very cool and as a geek who loves F1, I can't wait to play with this over this weekend and beyond. I'm curious where the live/static data is coming from and how freely available it is. Most sports are very protective of their data rights in the betting era (I know of one guy who spends six figures on tennis data a year - and yes, he makes a profit from it), so I'm wondering if/how F1 sees all this. Reg…

Thank you! The data comes from a SignalR data stream that F1 provides. It's not exactly public, but also not protected. There are some other projects (like FastF1) which have done a lot of working understanding this data, so all kudos go to them.

There's also static API endpoints which contain .json and .jsonStream files after a session ends, so you can process all the data and run some analytics on it.

I assume they don't mind too much about the usage - on the basis that some of these projects have existed for quite a while. I'm pretty sure everything who performs F1 analysis (like journalists, YouTubers etc) with charts and the like and getting their data via these feeds (either directly or via packages like FastF1.

If you want to learn more about the implementation itself, I'd recommend checking out the DataImporter.cs and LiveTimingClient.cs files in the UndercutF1.Data project of the repo. Although fair warning, my codes not that beautiful :).

Re: Show HN: Undercutf1 – F1 Live Timing TUI with Driver Tracker, Variable Delay

#46
post #37

Looks enticing! Regrettably a quick install (using the dotnet tool method, Win10) installs without error, but running the app results in an unresponsive window (both terminal and console), logs show no error... None of the key commands work (not even Q). Import data woks, but does not change the unresponsive window. Not looking for tech support, just making you aware that some additional steps might be required in th…

Thanks for the heads up. I think there might be some intricacies with different terminals and OS's which I hasn't fully appreciated (I've only been testing this on a arm64 Mac unfortunately). I have made a new release (https://github.com/JustAman62/undercut-f1/releases/tag/v3.0....) which might help fix the issue - but I'll need to get my hands on a windows machine again to validate, which I should be able to do in the next couple of days.

Re: Show HN: Undercutf1 – F1 Live Timing TUI with Driver Tracker, Variable Delay

#47
post #32

Earlier quoted context omitted.

Thank you! I'm very proud of the track map and lap charts. I mulled over for months about rewriting the app into a native app or website so that I could do proper graphics etc, but then one day earlier this year I suddenly realised I could use Terminal Graphics protocols to achieve inline graphics in the TUI itself, giving me the best of both worlds!

Is there any reason you couldn’t render the pixels to the screen as opposed to a constantly updated image (which as the docs note is terminal choice limiting)

I'm not personally aware of a method of doing so via a TUI, but I'd be very happy to be corrected. I was under the impression that sending images was the best way to handle non-character based output.

Re: Show HN: Undercutf1 – F1 Live Timing TUI with Driver Tracker, Variable Delay

#48
post #42

Looks great! However, I'd appreciate an easier way to run it: binaries for Linux aren't standalone -- they require 3rd party dependencies to be installed. Static binaries (or maybe container image?) would be nice.

Are you not able to compile this as "self-contained"?

I have compiled as self-contained, however I missed some configs to make sure that all native binaries were included in the final executable. I've made a new release recently (https://github.com/JustAman62/undercut-f1/releases/tag/v3.0....) which should resolve this issue.

As noted in https://github.com/JustAman62/undercut-f1/issues/3#issuecomm..., I think there's still more work to do to make the single-file executable work properly on Linux, due to the intricacies of the native Skia libs.

Re: Show HN: Undercutf1 – F1 Live Timing TUI with Driver Tracker, Variable Delay

#49
this looks pretty cool, but I can't get delay working properly. Trying to watch the qualifying session on about a 25 minute delay, the clock indicates the correct time (17:05 or so a few minutes into the session) but the driver times aren't showing, and the radio and race control messages are current (like, I can see all of the race control messages and radio messages for all of Q1).

Re: Show HN: Undercutf1 – F1 Live Timing TUI with Driver Tracker, Variable Delay

#50

this looks pretty cool, but I can't get delay working properly. Trying to watch the qualifying session on about a 25 minute delay, the clock indicates the correct time (17:05 or so a few minutes into the session) but the driver times aren't showing, and the radio and race control messages are current (like, I can see all of the race control messages and radio messages for all of Q1).

Ah, so unfortunately the delay is only applied to new data coming in. When you start a live session, we only get the current state and new data coming from the F1 feed, so we can't delay back to a point before you started listening to the feed. You also can't "rewind" the session, so any data that has been shown won't be removed, only new data will be added (after the delay you've set).

Currently the delay is designed for a minute or two's worth of delay for a live TV feed, or for replaying old sessions. I don't currently have a good way to support a long delay during a live session, without you starting the app before the session starts, and applying the 25 minute delay immediately so that all the data is queued up to be displayed in 25 minutes time.

Post reply on HN