dataenforce
YOLOv4
dataenforce | YOLOv4 | |
---|---|---|
2 | 1 | |
208 | 12 | |
- | - | |
0.0 | 3.6 | |
about 3 years ago | over 3 years ago | |
Python | C# | |
Apache License 2.0 | MIT License |
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.
dataenforce
-
Swift for TensorFlow Shuts Down
The dependence on library authors is always a challenge in any language. You might have one author using `[a]` where another uses `PositiveNumeric a, Fin n => NonEmptyList n a` for the same thing. You can always just annotate whatever the library author used (e.g. they return a list of strings, so you use List[str]).
There are some interesting further add ons that seem very python, allowing you to go further. For example, with a pandas dataframe you can just say your type is a dataframe which isn't so useful, but it's possible to hack your own types onto it in the vein of https://github.com/CedricFR/dataenforce, or use things like https://smarie.github.io/python-vtypes/ to get smarter typing on things the authors didn't type. I expect that trend will continue.
What fascinates me about python's types is actually the very fact that they are bolted on. You have a language that lets you do crazy things and a type system trying to catch up and make it convenient to verify those crazy things. It's a nice complement to the usual developments of verifying all of the things and slowly extending the set of things you can do.
-
[D] Question: Do you enforce a data format in Pandas? When collecting data over a long period of time, wouldn't it be useful to use a system with versioned schemas that specify how various data entries must be formatted? Give me feedback on this Open Source idea:
https://github.com/CedricFR/dataenforce enforces column names and types, no versioning though. My first instinct is that important data should be stored in databases which enforce schemas, and that should be separate from the python code that reads it.
YOLOv4
-
Swift for TensorFlow Shuts Down
[3] https://github.com/losttech/YOLOv4
What are some alternatives?
swift - Swift for TensorFlow
yolov7 - Implementation of paper - YOLOv7: Trainable bag-of-freebies sets new state-of-the-art for real-time object detectors
PythonNet - Python for .NET is a package that gives Python programmers nearly seamless integration with the .NET Common Language Runtime (CLR) and provides a powerful application scripting tool for .NET developers.
yolov5 - YOLOv5 🚀 in PyTorch > ONNX > CoreML > TFLite
MLJ.jl - A Julia machine learning framework
yolov7_d2 - 🔥🔥🔥🔥 (Earlier YOLOv7 not official one) YOLO with Transformers and Instance Segmentation, with TensorRT acceleration! 🔥🔥🔥
julia - The Julia Programming Language
py2many - Transpiler of Python to many other languages
Enzyme.jl - Julia bindings for the Enzyme automatic differentiator