github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-05-22 14:03:46 -05:00
Code Issues 114 Packages Projects Releases 24 Wiki Activity

[PR #93] [MERGED] Adding fig to embedded_ml cloud ml #579

New Issue
Closed
opened 2026-03-22 15:46:24 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-22 15:46:24 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/harvard-edge/cs249r_book/pull/93
Author: @zishenwan
Created: 12/5/2023
Status: ✅ Merged
Merged: 12/5/2023
Merged by: @profvjreddi

Base: main ← Head: fig_add

📝 Commits (3)

  • bef471d Adding fig to embedded_ml cloud ml
  • b305a99 Adding fig to embedded_ml cloud ml
  • 8b51765 Fixed image source

📊 Changes

2 files changed (+2 additions, -0 deletions)

View changed files

📝 embedded_ml.qmd (+2 -0)
➕ images/imgs_embedded_ml/cloud_ml_tpu.jpg (+0 -0)

📄 Description

Before submitting your Pull Request, please ensure that you have carefully reviewed and completed all items on this checklist.

  1. Content

    • The chapter content is complete and covers the topic in detail.
    • All technical terms are well-defined and explained.
    • Any code snippets or algorithms are well-documented and tested.
    • The chapter follows a logical flow and structure.

  2. References & Citations

    • All references are correctly listed at the end of the chapter.
    • In-text citations are used appropriately and match the references.
    • All figures, tables, and images have proper sources and are cited correctly.

  3. Quarto Website Rendering

    • The chapter has been locally built and tested using Quarto.
    • All images, figures, and tables render properly without any glitches.
    • All images have a source or they are properly linked to external sites.
    • Any interactive elements or widgets work as intended.
    • The chapter's formatting is consistent with the rest of the book.

  4. Grammar & Style

    • The chapter has been proofread for grammar and spelling errors.
    • The writing style is consistent with the rest of the book.
    • Any jargon is clearly explained or avoided where possible.

  5. Collaboration

    • All group members have reviewed and approved the chapter.
    • Any feedback from previous reviews or discussions has been addressed.

  6. Miscellaneous

    • All external links (if any) are working and lead to the intended destinations.
    • If datasets or external resources are used, they are properly credited and linked.
    • Any necessary permissions for reused content have been obtained.

  7. Final Steps

    • The chapter is pushed to the correct branch on the repository.
    • The Pull Request is made with a clear title and description.
    • The Pull Request includes any necessary labels or tags.
    • The Pull Request mentions any stakeholders or reviewers who should take a look.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/harvard-edge/cs249r_book/pull/93 **Author:** [@zishenwan](https://github.com/zishenwan) **Created:** 12/5/2023 **Status:** ✅ Merged **Merged:** 12/5/2023 **Merged by:** [@profvjreddi](https://github.com/profvjreddi) **Base:** `main` ← **Head:** `fig_add` --- ### 📝 Commits (3) - [`bef471d`](https://github.com/harvard-edge/cs249r_book/commit/bef471d531e28e796e1d570ce4fc2c60f2a46b57) Adding fig to embedded_ml cloud ml - [`b305a99`](https://github.com/harvard-edge/cs249r_book/commit/b305a997dc614f8bd0b1a5ca345315551e4f1afb) Adding fig to embedded_ml cloud ml - [`8b51765`](https://github.com/harvard-edge/cs249r_book/commit/8b51765d7b9b672954b320953f5208719736adf8) Fixed image source ### 📊 Changes **2 files changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `embedded_ml.qmd` (+2 -0) ➕ `images/imgs_embedded_ml/cloud_ml_tpu.jpg` (+0 -0) </details> ### 📄 Description Before submitting your Pull Request, please ensure that you have carefully reviewed and completed all items on this checklist. 1. **Content** - [x] The chapter content is complete and covers the topic in detail. - [x] All technical terms are well-defined and explained. - [x] Any code snippets or algorithms are well-documented and tested. - [x] The chapter follows a logical flow and structure. 2. **References & Citations** - [x] All references are correctly listed at the end of the chapter. - [x] In-text citations are used appropriately and match the references. - [x] All figures, tables, and images have proper sources and are cited correctly. 3. **Quarto Website Rendering** - [x] The chapter has been locally built and tested using Quarto. - [x] All images, figures, and tables render properly without any glitches. - [x] All images have a source or they are properly linked to external sites. - [x] Any interactive elements or widgets work as intended. - [x] The chapter's formatting is consistent with the rest of the book. 4. **Grammar & Style** - [x] The chapter has been proofread for grammar and spelling errors. - [x] The writing style is consistent with the rest of the book. - [x] Any jargon is clearly explained or avoided where possible. 5. **Collaboration** - [x] All group members have reviewed and approved the chapter. - [x] Any feedback from previous reviews or discussions has been addressed. 6. **Miscellaneous** - [x] All external links (if any) are working and lead to the intended destinations. - [x] If datasets or external resources are used, they are properly credited and linked. - [x] Any necessary permissions for reused content have been obtained. 7. **Final Steps** - [x] The chapter is pushed to the correct branch on the repository. - [x] The Pull Request is made with a clear title and description. - [x] The Pull Request includes any necessary labels or tags. - [x] The Pull Request mentions any stakeholders or reviewers who should take a look. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-03-22 15:46:24 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: labs
area: socratiq
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
javascript
link-health
link-rot
priority-high
pull-request
Mirrored from GitHub Pull Request
 staffml
type: bug
type: citation
type: code
type: errata
type: improvement
type: new
type: question
vault-sli
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#579
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?