I'm wondering if in the off-season we expand/rewrite some of the capabilities of f1dataR to match the new capabilities of FastF1, and also be more capable of implementing changes to reflect the changes there (#198).
For example, right now, for us to add and fully use pick_drivers instead of using pick_driver takes a rewrite of our get_session_laps() (#78). Had pick_driver() instead been a standalone function (as part of a class or otherwise) it'd be much easier to just accept a vector of character strings or numbers instead of a single value.
I also wonder if having an interface that more closely matches the workflow of FastF1 will make it easier for people to duplicate or expand on analysis they otherwise see happening in Python?
Thoughts?
I'm wondering if in the off-season we expand/rewrite some of the capabilities of f1dataR to match the new capabilities of FastF1, and also be more capable of implementing changes to reflect the changes there (#198).
For example, right now, for us to add and fully use
pick_driversinstead of usingpick_drivertakes a rewrite of ourget_session_laps()(#78). Hadpick_driver()instead been a standalone function (as part of a class or otherwise) it'd be much easier to just accept a vector of character strings or numbers instead of a single value.I also wonder if having an interface that more closely matches the workflow of FastF1 will make it easier for people to duplicate or expand on analysis they otherwise see happening in Python?
Thoughts?