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

v1.15.0.0 release notes + TensorFlow docs #806

Merged
merged 12 commits into from
Oct 15, 2024
Merged

v1.15.0.0 release notes + TensorFlow docs #806

merged 12 commits into from
Oct 15, 2024

Conversation

adrianstevens
Copy link
Contributor

No description provided.

@adrianstevens adrianstevens changed the title Merge to main to publish TensorFlow docs v1.1.50 release notes + TensorFlow docs Oct 15, 2024
@adrianstevens adrianstevens changed the title v1.1.50 release notes + TensorFlow docs v1.15.0.0 release notes + TensorFlow docs Oct 15, 2024
* **Sensory Input** - ML training pipelines and modern LLMs are gobbling up data at an unprecedented pace. The edge provides a wealth of data from the real world that can only be gathered from field-deployed devices. Digital twins would be impossible without the edge sensory input that feeds them, and the insights from not only individual devices, but in aggregate, they can unlock insights that can massively increase overall efficiency and productivity.
* **Local Model Execution** - While it’s generally not practical to train models on edge, these devices have outsized capabilities to execute models locally. For instance, realtime defect detection via an attached camera can run easily on a microcontroller (MCU), and object detection in multi-channel video can be done on a multi-GPU Jetson NX rather efficiently. This seminal post by Pete Warden (Useful Sensors) explains why non-LLM AI/ML models run so efficiently on low-powered devices.

# Benefits of Running @ the Edge
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We still need these to not be H1 level headers for SEO friendliness, but should be fine for now.

Copy link
Collaborator

@patridge patridge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple things that should change, but not sure they should be blockers.

@adrianstevens adrianstevens merged commit fc1ab4a into main Oct 15, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants