From bd31eb05c4f14718064e0f1a8e8208ef6d276167 Mon Sep 17 00:00:00 2001 From: Mark Saroufim Date: Fri, 15 Nov 2024 18:23:50 -0800 Subject: [PATCH 1/8] upgrade ruby version, lockfile and edge blog --- .ruby-version | 2 +- Gemfile | 4 +- Gemfile.lock | 333 +++++++++++++++++++++++++++--------------------- README.md | 23 ++-- _config.yml | 2 +- edge.html | 57 --------- executorch.html | 59 +++++---- 7 files changed, 236 insertions(+), 244 deletions(-) delete mode 100644 edge.html diff --git a/.ruby-version b/.ruby-version index 6a81b4c83794..0fa4ae489037 100644 --- a/.ruby-version +++ b/.ruby-version @@ -1 +1 @@ -2.7.8 +3.3.0 \ No newline at end of file diff --git a/Gemfile b/Gemfile index 166b9e4fa750..9f752984ada0 100644 --- a/Gemfile +++ b/Gemfile @@ -1,9 +1,9 @@ source "https://rubygems.org" -ruby "2.7.8" +ruby "3.3.0" group :jekyll_plugins do gem "github-pages" gem "jekyll-paginate-v2" - gem 'jekyll-autoprefixer' gem 'jekyll-feed' end + diff --git a/Gemfile.lock b/Gemfile.lock index f0011c355d87..dc117c294a04 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -1,51 +1,72 @@ GEM remote: https://rubygems.org/ specs: - activesupport (6.0.6.1) - concurrent-ruby (~> 1.0, >= 1.0.2) - i18n (>= 0.7, < 2) - minitest (~> 5.1) - tzinfo (~> 1.1) - zeitwerk (~> 2.2, >= 2.2.2) - addressable (2.8.0) - public_suffix (>= 2.0.2, < 5.0) - autoprefixer-rails (9.8.6.5) - execjs + activesupport (8.0.0) + base64 + benchmark (>= 0.3) + bigdecimal + concurrent-ruby (~> 1.0, >= 1.3.1) + connection_pool (>= 2.2.5) + drb + i18n (>= 1.6, < 2) + logger (>= 1.4.2) + minitest (>= 5.1) + securerandom (>= 0.3) + tzinfo (~> 2.0, >= 2.0.5) + uri (>= 0.13.1) + addressable (2.8.7) + public_suffix (>= 2.0.2, < 7.0) + base64 (0.2.0) + benchmark (0.4.0) + bigdecimal (3.1.8) coffee-script (2.4.1) coffee-script-source execjs - coffee-script-source (1.11.1) + coffee-script-source (1.12.2) colorator (1.1.0) - commonmarker (0.17.13) - ruby-enum (~> 0.5) - concurrent-ruby (1.2.0) - dnsruby (1.61.5) - simpleidn (~> 0.1) - em-websocket (0.5.2) + commonmarker (0.23.10) + concurrent-ruby (1.3.4) + connection_pool (2.4.1) + csv (3.3.0) + dnsruby (1.72.2) + simpleidn (~> 0.2.1) + drb (2.2.1) + em-websocket (0.5.3) eventmachine (>= 0.12.9) - http_parser.rb (~> 0.6.0) - ethon (0.12.0) - ffi (>= 1.3.0) + http_parser.rb (~> 0) + ethon (0.16.0) + ffi (>= 1.15.0) eventmachine (1.2.7) - execjs (2.7.0) - faraday (1.3.0) - faraday-net_http (~> 1.0) - multipart-post (>= 1.2, < 3) - ruby2_keywords - faraday-net_http (1.0.1) - ffi (1.15.0) + execjs (2.10.0) + faraday (2.12.1) + faraday-net_http (>= 2.0, < 3.5) + json + logger + faraday-net_http (3.4.0) + net-http (>= 0.5.0) + ffi (1.17.0-aarch64-linux-gnu) + ffi (1.17.0-aarch64-linux-musl) + ffi (1.17.0-arm-linux-gnu) + ffi (1.17.0-arm-linux-musl) + ffi (1.17.0-arm64-darwin) + ffi (1.17.0-x86-linux-gnu) + ffi (1.17.0-x86-linux-musl) + ffi (1.17.0-x86_64-darwin) + ffi (1.17.0-x86_64-linux-gnu) + ffi (1.17.0-x86_64-linux-musl) forwardable-extended (2.6.0) - gemoji (3.0.1) - github-pages (214) - github-pages-health-check (= 1.17.0) - jekyll (= 3.9.0) - jekyll-avatar (= 0.7.0) - jekyll-coffeescript (= 1.1.1) - jekyll-commonmark-ghpages (= 0.1.6) - jekyll-default-layout (= 0.1.4) - jekyll-feed (= 0.15.1) + gemoji (4.1.0) + github-pages (232) + github-pages-health-check (= 1.18.2) + jekyll (= 3.10.0) + jekyll-avatar (= 0.8.0) + jekyll-coffeescript (= 1.2.2) + jekyll-commonmark-ghpages (= 0.5.1) + jekyll-default-layout (= 0.1.5) + jekyll-feed (= 0.17.0) jekyll-gist (= 1.5.0) - jekyll-github-metadata (= 2.13.0) + jekyll-github-metadata (= 2.16.1) + jekyll-include-cache (= 0.2.1) jekyll-mentions (= 1.6.0) jekyll-optional-front-matter (= 0.3.2) jekyll-paginate (= 1.1.0) @@ -54,49 +75,51 @@ GEM jekyll-relative-links (= 0.6.1) jekyll-remote-theme (= 0.4.3) jekyll-sass-converter (= 1.5.2) - jekyll-seo-tag (= 2.7.1) + jekyll-seo-tag (= 2.8.0) jekyll-sitemap (= 1.4.0) jekyll-swiss (= 1.0.0) - jekyll-theme-architect (= 0.1.1) - jekyll-theme-cayman (= 0.1.1) - jekyll-theme-dinky (= 0.1.1) - jekyll-theme-hacker (= 0.1.2) - jekyll-theme-leap-day (= 0.1.1) - jekyll-theme-merlot (= 0.1.1) - jekyll-theme-midnight (= 0.1.1) - jekyll-theme-minimal (= 0.1.1) - jekyll-theme-modernist (= 0.1.1) - jekyll-theme-primer (= 0.5.4) - jekyll-theme-slate (= 0.1.1) - jekyll-theme-tactile (= 0.1.1) - jekyll-theme-time-machine (= 0.1.1) + jekyll-theme-architect (= 0.2.0) + jekyll-theme-cayman (= 0.2.0) + jekyll-theme-dinky (= 0.2.0) + jekyll-theme-hacker (= 0.2.0) + jekyll-theme-leap-day (= 0.2.0) + jekyll-theme-merlot (= 0.2.0) + jekyll-theme-midnight (= 0.2.0) + jekyll-theme-minimal (= 0.2.0) + jekyll-theme-modernist (= 0.2.0) + jekyll-theme-primer (= 0.6.0) + jekyll-theme-slate (= 0.2.0) + jekyll-theme-tactile (= 0.2.0) + jekyll-theme-time-machine (= 0.2.0) jekyll-titles-from-headings (= 0.5.3) - jemoji (= 0.12.0) - kramdown (= 2.3.1) + jemoji (= 0.13.0) + kramdown (= 2.4.0) kramdown-parser-gfm (= 1.1.0) - liquid (= 4.0.3) + liquid (= 4.0.4) mercenary (~> 0.3) minima (= 2.5.1) - nokogiri (>= 1.10.4, < 2.0) - rouge (= 3.26.0) + nokogiri (>= 1.16.2, < 2.0) + rouge (= 3.30.0) terminal-table (~> 1.4) - github-pages-health-check (1.17.0) + webrick (~> 1.8) + github-pages-health-check (1.18.2) addressable (~> 2.3) dnsruby (~> 1.60) - octokit (~> 4.0) - public_suffix (>= 2.0.2, < 5.0) + octokit (>= 4, < 8) + public_suffix (>= 3.0, < 6.0) typhoeus (~> 1.3) - html-pipeline (2.14.0) + html-pipeline (2.14.3) activesupport (>= 2) nokogiri (>= 1.4) - http_parser.rb (0.6.0) - i18n (0.9.5) + http_parser.rb (0.8.0) + i18n (1.14.6) concurrent-ruby (~> 1.0) - jekyll (3.9.0) + jekyll (3.10.0) addressable (~> 2.4) colorator (~> 1.0) + csv (~> 3.0) em-websocket (~> 0.5) - i18n (~> 0.7) + i18n (>= 0.7, < 2) jekyll-sass-converter (~> 1.0) jekyll-watch (~> 2.0) kramdown (>= 1.17, < 3) @@ -105,29 +128,30 @@ GEM pathutil (~> 0.9) rouge (>= 1.7, < 4) safe_yaml (~> 1.0) - jekyll-autoprefixer (1.0.2) - autoprefixer-rails (~> 9.3) - jekyll-avatar (0.7.0) + webrick (>= 1.0) + jekyll-avatar (0.8.0) jekyll (>= 3.0, < 5.0) - jekyll-coffeescript (1.1.1) + jekyll-coffeescript (1.2.2) coffee-script (~> 2.2) - coffee-script-source (~> 1.11.1) - jekyll-commonmark (1.3.1) - commonmarker (~> 0.14) - jekyll (>= 3.7, < 5.0) - jekyll-commonmark-ghpages (0.1.6) - commonmarker (~> 0.17.6) - jekyll-commonmark (~> 1.2) - rouge (>= 2.0, < 4.0) - jekyll-default-layout (0.1.4) - jekyll (~> 3.0) - jekyll-feed (0.15.1) + coffee-script-source (~> 1.12) + jekyll-commonmark (1.4.0) + commonmarker (~> 0.22) + jekyll-commonmark-ghpages (0.5.1) + commonmarker (>= 0.23.7, < 1.1.0) + jekyll (>= 3.9, < 4.0) + jekyll-commonmark (~> 1.4.0) + rouge (>= 2.0, < 5.0) + jekyll-default-layout (0.1.5) + jekyll (>= 3.0, < 5.0) + jekyll-feed (0.17.0) jekyll (>= 3.7, < 5.0) jekyll-gist (1.5.0) octokit (~> 4.2) - jekyll-github-metadata (2.13.0) + jekyll-github-metadata (2.16.1) jekyll (>= 3.4, < 5.0) - octokit (~> 4.0, != 4.4.0) + octokit (>= 4, < 7, != 4.4.0) + jekyll-include-cache (0.2.1) + jekyll (>= 3.7, < 5.0) jekyll-mentions (1.6.0) html-pipeline (~> 2.3) jekyll (>= 3.7, < 5.0) @@ -149,129 +173,146 @@ GEM rubyzip (>= 1.3.0, < 3.0) jekyll-sass-converter (1.5.2) sass (~> 3.4) - jekyll-seo-tag (2.7.1) + jekyll-seo-tag (2.8.0) jekyll (>= 3.8, < 5.0) jekyll-sitemap (1.4.0) jekyll (>= 3.7, < 5.0) jekyll-swiss (1.0.0) - jekyll-theme-architect (0.1.1) - jekyll (~> 3.5) + jekyll-theme-architect (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-cayman (0.1.1) - jekyll (~> 3.5) + jekyll-theme-cayman (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-dinky (0.1.1) - jekyll (~> 3.5) + jekyll-theme-dinky (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-hacker (0.1.2) + jekyll-theme-hacker (0.2.0) jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-leap-day (0.1.1) - jekyll (~> 3.5) + jekyll-theme-leap-day (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-merlot (0.1.1) - jekyll (~> 3.5) + jekyll-theme-merlot (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-midnight (0.1.1) - jekyll (~> 3.5) + jekyll-theme-midnight (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-minimal (0.1.1) - jekyll (~> 3.5) + jekyll-theme-minimal (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-modernist (0.1.1) - jekyll (~> 3.5) + jekyll-theme-modernist (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-primer (0.5.4) + jekyll-theme-primer (0.6.0) jekyll (> 3.5, < 5.0) jekyll-github-metadata (~> 2.9) jekyll-seo-tag (~> 2.0) - jekyll-theme-slate (0.1.1) - jekyll (~> 3.5) + jekyll-theme-slate (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-tactile (0.1.1) - jekyll (~> 3.5) + jekyll-theme-tactile (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) - jekyll-theme-time-machine (0.1.1) - jekyll (~> 3.5) + jekyll-theme-time-machine (0.2.0) + jekyll (> 3.5, < 5.0) jekyll-seo-tag (~> 2.0) jekyll-titles-from-headings (0.5.3) jekyll (>= 3.3, < 5.0) jekyll-watch (2.2.1) listen (~> 3.0) - jemoji (0.12.0) - gemoji (~> 3.0) + jemoji (0.13.0) + gemoji (>= 3, < 5) html-pipeline (~> 2.2) jekyll (>= 3.0, < 5.0) - kramdown (2.3.1) + json (2.8.2) + kramdown (2.4.0) rexml kramdown-parser-gfm (1.1.0) kramdown (~> 2.0) - liquid (4.0.3) - listen (3.5.1) + liquid (4.0.4) + listen (3.9.0) rb-fsevent (~> 0.10, >= 0.10.3) rb-inotify (~> 0.9, >= 0.9.10) + logger (1.6.1) mercenary (0.3.6) - mini_portile2 (2.8.1) minima (2.5.1) jekyll (>= 3.5, < 5.0) jekyll-feed (~> 0.9) jekyll-seo-tag (~> 2.1) - minitest (5.17.0) - multipart-post (2.1.1) - nokogiri (1.14.3) - mini_portile2 (~> 2.8.0) + minitest (5.25.1) + net-http (0.5.0) + uri + nokogiri (1.16.7-aarch64-linux) + racc (~> 1.4) + nokogiri (1.16.7-arm-linux) racc (~> 1.4) - octokit (4.20.0) - faraday (>= 0.9) - sawyer (~> 0.8.0, >= 0.5.3) + nokogiri (1.16.7-arm64-darwin) + racc (~> 1.4) + nokogiri (1.16.7-x86-linux) + racc (~> 1.4) + nokogiri (1.16.7-x86_64-darwin) + racc (~> 1.4) + nokogiri (1.16.7-x86_64-linux) + racc (~> 1.4) + octokit (4.25.1) + faraday (>= 1, < 3) + sawyer (~> 0.9) pathutil (0.16.2) forwardable-extended (~> 2.6) - public_suffix (4.0.6) - racc (1.6.2) - rb-fsevent (0.10.4) - rb-inotify (0.10.1) + public_suffix (5.1.1) + racc (1.8.1) + rb-fsevent (0.11.2) + rb-inotify (0.11.1) ffi (~> 1.0) - rexml (3.2.5) - rouge (3.26.0) - ruby-enum (0.9.0) - i18n - ruby2_keywords (0.0.4) - rubyzip (2.3.0) + rexml (3.3.9) + rouge (3.30.0) + rubyzip (2.3.2) safe_yaml (1.0.5) sass (3.7.4) sass-listen (~> 4.0.0) sass-listen (4.0.0) rb-fsevent (~> 0.9, >= 0.9.4) rb-inotify (~> 0.9, >= 0.9.7) - sawyer (0.8.2) + sawyer (0.9.2) addressable (>= 2.3.5) - faraday (> 0.8, < 2.0) - simpleidn (0.2.1) - unf (~> 0.1.4) + faraday (>= 0.17.3, < 3) + securerandom (0.3.2) + simpleidn (0.2.3) terminal-table (1.8.0) unicode-display_width (~> 1.1, >= 1.1.1) - thread_safe (0.3.6) - typhoeus (1.4.0) + typhoeus (1.4.1) ethon (>= 0.9.0) - tzinfo (1.2.11) - thread_safe (~> 0.1) - unf (0.1.4) - unf_ext - unf_ext (0.0.7.7) - unicode-display_width (1.7.0) - zeitwerk (2.6.7) + tzinfo (2.0.6) + concurrent-ruby (~> 1.0) + unicode-display_width (1.8.0) + uri (1.0.2) + webrick (1.9.0) PLATFORMS - ruby + aarch64-linux + aarch64-linux-gnu + aarch64-linux-musl + arm-linux + arm-linux-gnu + arm-linux-musl + arm64-darwin + x86-linux + x86-linux-gnu + x86-linux-musl + x86_64-darwin + x86_64-linux + x86_64-linux-gnu + x86_64-linux-musl DEPENDENCIES github-pages - jekyll-autoprefixer jekyll-feed jekyll-paginate-v2 RUBY VERSION - ruby 2.7.8p225 + ruby 3.3.0p0 BUNDLED WITH - 1.17.2 + 2.5.23 diff --git a/README.md b/README.md index f3cad9ccd536..33f23698a743 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ Install the following packages before attempting to setup the project: On OSX, you can use: -``` +```bash brew install rbenv ruby-build nvm ``` @@ -22,29 +22,26 @@ brew install rbenv ruby-build nvm #### Install required Ruby version: -``` +```bash #### You only need to run these commands if you are missing the needed Ruby version. - rbenv install `cat .ruby-version` -gem install bundler -v 1.16.3 +gem install bundler -v 2.5.23 rbenv rehash -#### - bundle install rbenv rehash ``` -#### Install required Node version +#### Install Node -``` +```bash nvm install nvm use ``` #### Install Yarn -``` +```bash brew install yarn --ignore-dependencies yarn install ``` @@ -53,19 +50,15 @@ yarn install To run the website locally for development: -``` +```bash make serve ``` Then navigate to [localhost:4000](localhost:4000). -Note the `serve` task is contained in a `Makefile` in the root directory. We are using `make` as an alternative to the standard `jekyll serve` as we want to run `yarn`, which is not included in Jekyll by default. - -### Building the Static Site - To build the static website from source: -``` +```bash make build ``` diff --git a/_config.yml b/_config.yml index 22b1329d0e21..ff078d955cba 100644 --- a/_config.yml +++ b/_config.yml @@ -10,7 +10,7 @@ baseurl: "" plugins: - jekyll-paginate-v2 - jekyll-redirect-from - - jekyll-autoprefixer + # - jekyll-autoprefixer - jekyll-feed sass: load_paths: diff --git a/edge.html b/edge.html deleted file mode 100644 index a94862e306ab..000000000000 --- a/edge.html +++ /dev/null @@ -1,57 +0,0 @@ ---- -layout: default -title: PyTorch Edge -body-class: announcement -background-class: announcement-background -permalink: /edge ---- - -
-
-
-

PyTorch Edge

-

Build innovative and privacy-aware AI experiences for edge devices

-
-
-
-
-
- -
-
-
-
-

PyTorch Edge

-

The AI landscape is quickly evolving, with AI models being deployed beyond server to edge devices such as mobile phones, wearables, AR/VR/MR and embedded devices. PyTorch Edge extends PyTorch's research-to-production stack to these edge devices and paves the way for building innovative, privacy-aware experiences with superior productivity, portability, and performance, optimized for these diverse hardware platforms.

-

Introducing ExecuTorch

-

To advance our PyTorch Edge offering, we developed ExecuTorch, our new runtime for edge devices. ExecuTorch facilitates PyTorch inference on edge devices while supporting portability across hardware platforms with lower runtime and framework tax. ExecuTorch was developed collaboratively between industry leaders including Meta, Arm, Apple, and Qualcomm.

-

With ExecuTorch, we’ve renewed our commitment to on-device AI. This extends our ecosystem in a much more “in the spirit of PyTorch” way, with productivity, hackability, and extensibility as critical components. We look forward to supporting edge and embedded applications with low latency, strong privacy, and innovation on the edge.

-
-
-
- -
-
-
-
-

Learn more about PyTorch Edge

-
-
-
-
-

What’s New in ExecuTorch

- - ExecuTorch - -
-
-

Try ExecuTorch

- - ExecuTorch Documentation - -
-
-
-
- - diff --git a/executorch.html b/executorch.html index f4b1f932aa85..595b58d1087e 100644 --- a/executorch.html +++ b/executorch.html @@ -1,17 +1,16 @@ --- layout: default -title: PyTorch ExecuTorch +title: PyTorch Edge & ExecuTorch body-class: announcement background-class: announcement-background permalink: /executorch-overview -excerpt: Learn about executorch, a mobile machine learning framework within PyTorch for deploying deep learning models on mobile and embedded devices. ---
-

ExecuTorch

-

End-to-end solution for enabling on-device inference capabilities across mobile and edge devices

+

PyTorch Edge with ExecuTorch

+

Build innovative and privacy-aware AI experiences for edge devices with Executorch

@@ -22,8 +21,11 @@

ExecuTorch

-

What is ExecuTorch?

-

ExecuTorch is an end-to-end solution for enabling on-device inference capabilities across mobile and edge devices including wearables, embedded devices and microcontrollers. It is part of the PyTorch Edge ecosystem and enables efficient deployment of various PyTorch models (vision, speech, Generative AI, and more) to edge devices. Key value propositions of ExecuTorch are:

+

PyTorch Edge

+

The AI landscape is quickly evolving, with AI models being deployed beyond servers to edge devices such as mobile phones, wearables, AR/VR/MR and embedded devices. PyTorch Edge extends PyTorch's research-to-production stack to these edge devices and paves the way for building innovative, privacy-aware experiences with superior productivity, portability, and performance, optimized for diverse hardware platforms.

+ +

What is ExecuTorch?

+

ExecuTorch is an end-to-end solution for enabling on-device inference capabilities across mobile and edge devices including wearables, embedded devices and microcontrollers. It is part of the PyTorch Edge ecosystem and enables efficient deployment of various PyTorch models (vision, speech, Generative AI, and more) to edge devices.

@@ -52,23 +54,36 @@

What is ExecuTorch?

-

Explore ExecuTorch

- -

ExecuTorch is currently powering various experiences across AR, VR and Family of Apps (FOA) products and services at Meta. We are excited to see how the community leverages our all new on-device AI stack. You can learn more about key components of ExecuTorch and its architecture, how it works, and explore documentation pages and detailed tutorials.

- -

- - ExecuTorch Documentation - - - ExecuTorch on GitHub - -

- -

Why ExecuTorch?

- -

Supporting on-device AI presents unique challenges with diverse hardware, critical power requirements, low/no internet connectivity, and realtime processing needs. These constraints have historically prevented or slowed down the creation of scalable and performant on-device AI solutions. We designed ExecuTorch, backed by our industry leaders like Meta, Arm, Apple, and Qualcomm, to be highly portable and provide superior developer productivity without losing on performance.

+

Why ExecuTorch?

+

Supporting on-device AI presents unique challenges with diverse hardware, critical power requirements, low/no internet connectivity, and realtime processing needs. These constraints have historically prevented or slowed down the creation of scalable and performant on-device AI solutions. ExecuTorch was developed collaboratively between industry leaders including Meta, Arm, Apple, and Qualcomm to be highly portable and provide superior developer productivity without compromising performance.

+

Explore ExecuTorch

+

ExecuTorch is currently powering various experiences across AR, VR and Family of Apps (FOA) products and services at Meta. You can learn more about key components of ExecuTorch and its architecture, how it works, and explore documentation pages and detailed tutorials.

+
+ +
+
+
+
+

Learn More

+
+
+
+
+

ExecuTorch on GitHub

+ + View Repository + +
+
+

Documentation

+ + Get Started + +
+
+
+
\ No newline at end of file From fb83c14bcb2365574ca2b831dcd176a9c88f1411 Mon Sep 17 00:00:00 2001 From: Mark Saroufim Date: Fri, 15 Nov 2024 18:36:56 -0800 Subject: [PATCH 2/8] Remove edge dropdown --- _includes/main_menu.html | 16 +++------------- 1 file changed, 3 insertions(+), 13 deletions(-) diff --git a/_includes/main_menu.html b/_includes/main_menu.html index d5668973aa4c..04926b7b3483 100644 --- a/_includes/main_menu.html +++ b/_includes/main_menu.html @@ -61,20 +61,10 @@
  • -
    • From adff346c153b389be9020c82be02f2af2a27fa93 Mon Sep 17 00:00:00 2001 From: Mark Saroufim Date: Fri, 15 Nov 2024 18:42:19 -0800 Subject: [PATCH 3/8] update --- Gemfile | 3 +-- _config.yml | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/Gemfile b/Gemfile index 9f752984ada0..1bcc4cbe9248 100644 --- a/Gemfile +++ b/Gemfile @@ -5,5 +5,4 @@ group :jekyll_plugins do gem "github-pages" gem "jekyll-paginate-v2" gem 'jekyll-feed' -end - +end \ No newline at end of file diff --git a/_config.yml b/_config.yml index ff078d955cba..22b1329d0e21 100644 --- a/_config.yml +++ b/_config.yml @@ -10,7 +10,7 @@ baseurl: "" plugins: - jekyll-paginate-v2 - jekyll-redirect-from - # - jekyll-autoprefixer + - jekyll-autoprefixer - jekyll-feed sass: load_paths: From 484f7723f9a5dbbbef81b6706058db91b2d25bbe Mon Sep 17 00:00:00 2001 From: Mark Saroufim Date: Fri, 15 Nov 2024 18:43:59 -0800 Subject: [PATCH 4/8] Trigger CI From 82943632f8e465627d8d71b2f91ab9498adc568f Mon Sep 17 00:00:00 2001 From: Mark Saroufim Date: Tue, 26 Nov 2024 11:14:49 -0800 Subject: [PATCH 5/8] update --- edge.html | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 edge.html diff --git a/edge.html b/edge.html new file mode 100644 index 000000000000..558fa3e602ce --- /dev/null +++ b/edge.html @@ -0,0 +1,8 @@ +--- +layout: default +title: PyTorch Edge +body-class: announcement +background-class: announcement-background +permalink: /edge +redirect_to: /executorch-overview +--- \ No newline at end of file From 58ffda1b803c72a1bf032b8494380224ae9f562d Mon Sep 17 00:00:00 2001 From: Mark Saroufim Date: Tue, 26 Nov 2024 13:31:19 -0800 Subject: [PATCH 6/8] fix mobile menu --- _includes/mobile_menu.html | 3 --- 1 file changed, 3 deletions(-) diff --git a/_includes/mobile_menu.html b/_includes/mobile_menu.html index d3ff1f46b700..522ce94d49d3 100644 --- a/_includes/mobile_menu.html +++ b/_includes/mobile_menu.html @@ -67,9 +67,6 @@ Edge
      -
    • - About PyTorch Edge -
    • ExecuTorch
      • From 8d720c3cae982143e21f1edd70736019d49c3084 Mon Sep 17 00:00:00 2001 From: Mark Saroufim Date: Tue, 26 Nov 2024 13:49:41 -0800 Subject: [PATCH 7/8] update --- _includes/mobile_menu.html | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/_includes/mobile_menu.html b/_includes/mobile_menu.html index 522ce94d49d3..7473beab3bae 100644 --- a/_includes/mobile_menu.html +++ b/_includes/mobile_menu.html @@ -64,12 +64,8 @@
  • - Edge + ExecuTorch
    • -
  • Docs From 0fdb9457ac47789c4e33d6884b30906ab316f71a Mon Sep 17 00:00:00 2001 From: Mark Saroufim Date: Tue, 26 Nov 2024 13:53:45 -0800 Subject: [PATCH 8/8] revert changes to edge page --- _includes/main_menu.html | 16 +++++++++-- _includes/mobile_menu.html | 9 +++++- edge.html | 53 ++++++++++++++++++++++++++++++++-- executorch.html | 59 ++++++++++++++------------------------ 4 files changed, 94 insertions(+), 43 deletions(-) diff --git a/_includes/main_menu.html b/_includes/main_menu.html index 04926b7b3483..d5668973aa4c 100644 --- a/_includes/main_menu.html +++ b/_includes/main_menu.html @@ -61,10 +61,20 @@
  • -
    - - Edge +
    • diff --git a/_includes/mobile_menu.html b/_includes/mobile_menu.html index 7473beab3bae..d3ff1f46b700 100644 --- a/_includes/mobile_menu.html +++ b/_includes/mobile_menu.html @@ -64,8 +64,15 @@
  • - ExecuTorch + Edge
    • +
  • Docs diff --git a/edge.html b/edge.html index 558fa3e602ce..a94862e306ab 100644 --- a/edge.html +++ b/edge.html @@ -4,5 +4,54 @@ body-class: announcement background-class: announcement-background permalink: /edge -redirect_to: /executorch-overview ---- \ No newline at end of file +--- + +
    +
    +
    +

    PyTorch Edge

    +

    Build innovative and privacy-aware AI experiences for edge devices

    +
    +
    +
    +
    +
    + +
    +
    +
    +
    +

    PyTorch Edge

    +

    The AI landscape is quickly evolving, with AI models being deployed beyond server to edge devices such as mobile phones, wearables, AR/VR/MR and embedded devices. PyTorch Edge extends PyTorch's research-to-production stack to these edge devices and paves the way for building innovative, privacy-aware experiences with superior productivity, portability, and performance, optimized for these diverse hardware platforms.

    +

    Introducing ExecuTorch

    +

    To advance our PyTorch Edge offering, we developed ExecuTorch, our new runtime for edge devices. ExecuTorch facilitates PyTorch inference on edge devices while supporting portability across hardware platforms with lower runtime and framework tax. ExecuTorch was developed collaboratively between industry leaders including Meta, Arm, Apple, and Qualcomm.

    +

    With ExecuTorch, we’ve renewed our commitment to on-device AI. This extends our ecosystem in a much more “in the spirit of PyTorch” way, with productivity, hackability, and extensibility as critical components. We look forward to supporting edge and embedded applications with low latency, strong privacy, and innovation on the edge.

    +
    +
    +
    + +
    +
    +
    +
    +

    Learn more about PyTorch Edge

    +
    +
    +
    +
    +

    What’s New in ExecuTorch

    + + ExecuTorch + +
    +
    +

    Try ExecuTorch

    + + ExecuTorch Documentation + +
    +
    +
    +
    + + diff --git a/executorch.html b/executorch.html index 595b58d1087e..f4b1f932aa85 100644 --- a/executorch.html +++ b/executorch.html @@ -1,16 +1,17 @@ --- layout: default -title: PyTorch Edge & ExecuTorch +title: PyTorch ExecuTorch body-class: announcement background-class: announcement-background permalink: /executorch-overview +excerpt: Learn about executorch, a mobile machine learning framework within PyTorch for deploying deep learning models on mobile and embedded devices. ---
    -

    PyTorch Edge with ExecuTorch

    -

    Build innovative and privacy-aware AI experiences for edge devices with Executorch

    +

    ExecuTorch

    +

    End-to-end solution for enabling on-device inference capabilities across mobile and edge devices

    @@ -21,11 +22,8 @@

    PyTorch Edge with ExecuTorch

    -

    PyTorch Edge

    -

    The AI landscape is quickly evolving, with AI models being deployed beyond servers to edge devices such as mobile phones, wearables, AR/VR/MR and embedded devices. PyTorch Edge extends PyTorch's research-to-production stack to these edge devices and paves the way for building innovative, privacy-aware experiences with superior productivity, portability, and performance, optimized for diverse hardware platforms.

    - -

    What is ExecuTorch?

    -

    ExecuTorch is an end-to-end solution for enabling on-device inference capabilities across mobile and edge devices including wearables, embedded devices and microcontrollers. It is part of the PyTorch Edge ecosystem and enables efficient deployment of various PyTorch models (vision, speech, Generative AI, and more) to edge devices.

    +

    What is ExecuTorch?

    +

    ExecuTorch is an end-to-end solution for enabling on-device inference capabilities across mobile and edge devices including wearables, embedded devices and microcontrollers. It is part of the PyTorch Edge ecosystem and enables efficient deployment of various PyTorch models (vision, speech, Generative AI, and more) to edge devices. Key value propositions of ExecuTorch are:

    @@ -54,36 +52,23 @@

    What is ExecuTorch?

    -

    Why ExecuTorch?

    -

    Supporting on-device AI presents unique challenges with diverse hardware, critical power requirements, low/no internet connectivity, and realtime processing needs. These constraints have historically prevented or slowed down the creation of scalable and performant on-device AI solutions. ExecuTorch was developed collaboratively between industry leaders including Meta, Arm, Apple, and Qualcomm to be highly portable and provide superior developer productivity without compromising performance.

    +

    Explore ExecuTorch

    + +

    ExecuTorch is currently powering various experiences across AR, VR and Family of Apps (FOA) products and services at Meta. We are excited to see how the community leverages our all new on-device AI stack. You can learn more about key components of ExecuTorch and its architecture, how it works, and explore documentation pages and detailed tutorials.

    + +

    + + ExecuTorch Documentation + + + ExecuTorch on GitHub + +

    + +

    Why ExecuTorch?

    + +

    Supporting on-device AI presents unique challenges with diverse hardware, critical power requirements, low/no internet connectivity, and realtime processing needs. These constraints have historically prevented or slowed down the creation of scalable and performant on-device AI solutions. We designed ExecuTorch, backed by our industry leaders like Meta, Arm, Apple, and Qualcomm, to be highly portable and provide superior developer productivity without losing on performance.

    -

    Explore ExecuTorch

    -

    ExecuTorch is currently powering various experiences across AR, VR and Family of Apps (FOA) products and services at Meta. You can learn more about key components of ExecuTorch and its architecture, how it works, and explore documentation pages and detailed tutorials.

    -
    - -
    -
    -
    -
    -

    Learn More

    -
    -
    -
    -
    -

    ExecuTorch on GitHub

    - - View Repository - -
    -
    -

    Documentation

    - - Get Started - -
    -
    -
    -
    \ No newline at end of file