openpilot
Kedro
Our great sponsors
openpilot | Kedro | |
---|---|---|
838 | 29 | |
47,150 | 9,288 | |
2.0% | 1.4% | |
10.0 | 9.7 | |
1 day ago | 6 days ago | |
Python | Python | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
openpilot
- I need some help understanding video uploads.
-
Thomas Massie Failed to Stop "Kill Switch" Mandate That Could Disable Vehicles
Indeed. Comma.ai [1] does this [2] in a very open way.
Unfortunately existing manufacturers are unlikely to implement this in a complete local-first way.
[1] https://comma.ai
[2] https://github.com/commaai/openpilot/blob/master/selfdrive/m...
-
Ask HN: Who is hiring? (November 2023)
See our open source driving agent on GitHub: https://github.com/commaai/openpilot
- Beginners Guide: Subaru Vehicles with Eyesight
-
cv.c: experimental computer library in C; A Robot's guide to seeing the world -- introductory guide to CV
Hello! I was absolutely enthralled by Computer Vision when I came across some of Geohotz's streams about developing Comma.ai (a self-driving company) and I decided to delve into Computer Vision about a week back. I began by working on Aadv1k/cv.c which was meant to "imitate" OpenCV, as the phrasing goes "You Learn by building" I would be lying if I said this program is decent, it is not. I havent optimized much of it and this is like my 3rd C project :P Here is what all I got working (I will continue work on this), the only dependency here is STB * Smoothing * Gaussian blur * Median filter * Bilateral Filter * Box Filter * Edge detection * Unsharp mask * Laplacian Filter (Difference of Gaussian) * Sobel operator * Color * Greyscale * Thresholding * Global * Otsu's Method
-
Can I use my Galaxy S10+ with my 2016 CR-V to run Flowpilot?
1.) Will this system work with my car? 2016 CR-Vs show up under the list of cars, but it says touring trim and I do not have the touring trim. I have found resources that state that any trim will still work with this and I am wondering if my car still has the actuators or ability to work with these systems.
-
2020 Sierra/GMC CAN ids
Finally, worse comes to worse, manually extracting the DBC and parsing it using Cabana.
-
Best Setup for Remote Control?
It's probably best you search for the Retropilot Discord. This is beyond what the normal comma.ai people or community try to do.
- If you have a Comma Three and a 2023 Corolla or 2023 Prius, comma is looking for testers for a "Toyota B Harness"
Kedro
-
Nextflow: Data-Driven Computational Pipelines
Interesting, thanks for sharing. I'll definitely take a look, although at this point I am so comfortable with Snakemake, it is a bit hard to imagine what would convince me to move to another tool. But I like the idea of composable pipelines: I am building a tool (too early to share) that would allow to lay Snakemake pipelines on top of each other using semi-automatic data annotations similar to how it is done in kedro (https://github.com/kedro-org/kedro).
-
A Polars exploration into Kedro
# pyproject.toml [project] dependencies = [ "kedro @ git+https://github.com/kedro-org/kedro@3ea7231", "kedro-datasets[pandas.CSVDataSet,polars.CSVDataSet] @ git+https://github.com/kedro-org/kedro-plugins@3b42fae#subdirectory=kedro-datasets", ]
-
What are some open-source ML pipeline managers that are easy to use?
So there's 2 sides to pipeline management: the actual definition of the pipelines (in code) and how/when/where you run them. Some tools like prefect or airflow do both of them at once, but for the actual pipeline definition I'm a fan of https://kedro.org. You can then use most available orchestrators to run those pipelines on whatever schedule and architecture you want.
-
Futuristic documentation systems in Python, part 1: aiming for more
Recently I started a position as Developer Advocate for Kedro, an opinionated data science framework, and one of the things we're doing is exploring what are the best open source tools we can use to create our documentation.
-
Python projects with best practices on Github?
You can also check out Kedro, it’s like the Flask for data science projects and helps apply clean code principles to data science code.
- What are examples of well-organized data science project that I can see on Github?
-
Dabbling with Dagster vs. Airflow
An often overlooked framework used by NASA among others is Kedro https://github.com/kedro-org/kedro. Kedro is probably the simplest set of abstractions for building pipelines but it doesn't attempt to kill Airflow. It even has an Airflow plugin that allows it to be used as a DSL for building Airflow pipelines or plug into whichever production orchestration system is needed.
-
What are some good DS/ML repos where I can learn about structuring a DS/ML project?
For the lazy ones out there, here's the link to their github repo.
- Kedro – Creating reproducible, maintainable and modular data science code
-
[Discussion] Applied machine learning implementation debate. Is OOP approach towards data preprocessing in python an overkill?
I'd focus more on understanding the issues in depth, before jumping to a solution. Otherwise, you would be adding hassle with some - bluntly speaking - opinionated and inflexible boilerplate code which not many people will like using. You mention some issues: non-obvious to understand code and hard to execute and replicate. Bad code which is not following engineering best practices (ideas from SOLID etc.) does not get better if you force the author to introduce certain classes. You can suggest some basics (e.g. common code formatter, meaningful variables names, short functions, no hard-coded values, ...), but I'm afraid you cannot educate non-engineers in a single day workshop. I would not focus on that at first. However, there is no excuse for writing bad code and then expecting others to fix. As you say, data engineering is part of data science skills, you are "junior" if you cannot write reproducible code. Being hard to execute and replicate is theoretically easy to fix. Force everyone to (at least hypothetically) submit their code into a testing environment where it will be automatically executed on a fresh machine. This will mean that at first they have to exactly specify all libraries that need to be installed. Second, they need to externalize all configuration - in particular data input and data output paths. Not a single value should be hard-coded in code! And finally they need a *single* command which can be run to execute the whole(!) pipeline. If they fail on any of these parts... they should try again. Work that does not pass this test is considered unfinished by the author. Basically you are introducing an automated, infallible test. Regarding your code, I'd really not try that direction. In particular even these few lines already look unclear and over-engineered. The csv format is already hard-coded into the code. If it changes to parquet you'd have to touch the code. The processing object has data paths fixed for which is no reason in a job which should take care of pure processing. Export data is also not something that a processing job should handle. And what if you have multiple input and output data? You would not have all these issues if you had kept to most simple solution to have a function `process(data1, data2, ...) -> result_data` where dataframes are passed in and out. It would also mean to have zero additional libraries or boilerplate. I highly doubt that a function `main_pipe(...)` will fix the malpractices some people may do. There are two small feature which are useful beyond a plain function though: automatically generating a visual DAG from the code and quick checking if input requirements are satisfied before heavy code is run. You can still put any mature DAG library on top, which probably already includes experience from a lot of developers. Not need to rewrite that. I'm not sure which one is best (metaflow, luigi, airflow, ... https://github.com/pditommaso/awesome-pipeline no idea), but many come with a lot of features. If you want a bit more scaffolding to easier understand foreign projects, you could look at https://github.com/quantumblacklabs/kedro but maybe that's already too much. Fix the "single command replication-from-scratch requirement" first.
What are some alternatives?
sunnypilot - sunnypilot is a fork of comma.ai's openpilot, an open source driver assistance system. sunnypilot offers the user a unique driving experience for over 260 supported car makes and models with modified behaviors of driving assist engagements. sunnypilot complies with comma.ai's safety rules as accurately as possible.
Airflow - Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
luigi - Luigi is a Python module that helps you build complex pipelines of batch jobs. It handles dependency resolution, workflow management, visualization etc. It also comes with Hadoop support built in.
Dask - Parallel computing with task scheduling
carla - Open-source simulator for autonomous driving research.
opendbc - democratize access to car decoder rings
cookiecutter-pytorch - A Cookiecutter template for PyTorch Deep Learning projects.
ploomber - The fastest ⚡️ way to build data pipelines. Develop iteratively, deploy anywhere. ☁️
dragonpilot - dragonpilot - 基於 openpilot 的開源駕駛輔助系統
BentoML - Build Production-Grade AI Applications
lightning-bolts - Toolbox of models, callbacks, and datasets for AI/ML researchers.
Pinball