Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorporating turns into the telemetry data #210

Closed
amritvignesh opened this issue Jan 14, 2024 · 2 comments · Fixed by #211
Closed

Incorporating turns into the telemetry data #210

amritvignesh opened this issue Jan 14, 2024 · 2 comments · Fixed by #211
Labels
enhancement New feature or request

Comments

@amritvignesh
Copy link

Would be great if there can be a function to identify turns as it is hard to derive from coordinates itself!

@pbulsink
Copy link
Collaborator

@SCasanova We could just expose the circuit_info table from FastF1.

@amritvignesh As much as possible we don't reprocess data from the Python package, it leaves this package much more complex. But FastF1 has that info available so you'd be able to put it together as needed (see from the FastF1 examples circuit map with annotated corners and also speed trace with corner annotations).

@pbulsink pbulsink added the enhancement New feature or request label Jan 14, 2024
@SCasanova
Copy link
Owner

Yes I think that could be useful. I will look into incorporating that this week

pbulsink added a commit to pbulsink/f1dataR that referenced this issue Jan 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants