github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-05-08 02:28:25 -05:00
Code Issues 85 Packages Projects Releases 24 Wiki Activity

[PR #161] [MERGED] adding web scraping colab exercise #615

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

📋 Pull Request Information

Original PR: https://github.com/harvard-edge/cs249r_book/pull/161
Author: @shanzehbatool
Created: 2/2/2024
Status: ✅ Merged
Merged: 4/5/2024
Merged by: @profvjreddi

Base: main ← Head: iss154-add-colab-badges

📝 Commits (10+)

  • 7f9c3a6 adding web scraping colab exercise
  • 1dc5a25 modified callout content
  • cad47cd adding a web scraping exercise after the subsection and also at the end as a separate Exercises part
  • 47a354c updating the data engineering chapter with colab notebooks
  • 301b439 fixed the colab link in Problem Definition section
  • 52e4c59 adding colab notebooks for the frameworks chapter
  • c367a34 updating frameworks.qmd with colab
  • cf2a48b Merge remote-tracking branch 'upstream/main' into iss153-add-colab-badges
  • 6c83867 pulled new updates and trying out exercise callout in embedded_ml.qmd
  • 24ecf2c Merge remote-tracking branch 'upstream/main' into iss154-add-colab-badges

📊 Changes

13 files changed (+335 additions, -47 deletions)

View changed files

📝 _quarto.yml (+5 -5)
📝 contents/benchmarking/benchmarking.qmd (+23 -1)
📝 contents/data_engineering/data_engineering.qmd (+47 -3)
📝 contents/dl_primer/dl_primer.qmd (+34 -17)
📝 contents/embedded_ml/embedded_ml.qmd (+11 -1)
📝 contents/frameworks/frameworks.qmd (+33 -13)
📝 contents/hw_acceleration/hw_acceleration.qmd (+11 -1)
📝 contents/ondevice_learning/ondevice_learning.qmd (+37 -1)
📝 contents/ops/ops.qmd (+11 -1)
📝 contents/optimizations/optimizations.qmd (+40 -1)
📝 contents/privacy_security/privacy_security.qmd (+23 -1)
📝 contents/training/training.qmd (+60 -1)
📝 custom_callout.lua (+0 -1)

📄 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/161 **Author:** [@shanzehbatool](https://github.com/shanzehbatool) **Created:** 2/2/2024 **Status:** ✅ Merged **Merged:** 4/5/2024 **Merged by:** [@profvjreddi](https://github.com/profvjreddi) **Base:** `main` ← **Head:** `iss154-add-colab-badges` --- ### 📝 Commits (10+) - [`7f9c3a6`](https://github.com/harvard-edge/cs249r_book/commit/7f9c3a6ba5a19a49af2ce4fbce352cdf39847834) adding web scraping colab exercise - [`1dc5a25`](https://github.com/harvard-edge/cs249r_book/commit/1dc5a25d24fb43b39fcd83d23739542025bff5b6) modified callout content - [`cad47cd`](https://github.com/harvard-edge/cs249r_book/commit/cad47cdcc78aacf94584f136c2c2ebee38016ba8) adding a web scraping exercise after the subsection and also at the end as a separate Exercises part - [`47a354c`](https://github.com/harvard-edge/cs249r_book/commit/47a354c76819a0513221770f3f16e04087e890ac) updating the data engineering chapter with colab notebooks - [`301b439`](https://github.com/harvard-edge/cs249r_book/commit/301b439723c9eab174458a2e2e8b61f765da6f63) fixed the colab link in Problem Definition section - [`52e4c59`](https://github.com/harvard-edge/cs249r_book/commit/52e4c59f821d897d6d6c5c8061d526d334b939b8) adding colab notebooks for the frameworks chapter - [`c367a34`](https://github.com/harvard-edge/cs249r_book/commit/c367a3498a2c0c305671c61a60fc3a9d6a38f0f6) updating frameworks.qmd with colab - [`cf2a48b`](https://github.com/harvard-edge/cs249r_book/commit/cf2a48bbc8b0abc1dad5ce1025a79db6d53677f1) Merge remote-tracking branch 'upstream/main' into iss153-add-colab-badges - [`6c83867`](https://github.com/harvard-edge/cs249r_book/commit/6c838672fad407e3646a2daf03593eadc1b7a551) pulled new updates and trying out exercise callout in embedded_ml.qmd - [`24ecf2c`](https://github.com/harvard-edge/cs249r_book/commit/24ecf2c2045649395a4233e9c08962310a931174) Merge remote-tracking branch 'upstream/main' into iss154-add-colab-badges ### 📊 Changes **13 files changed** (+335 additions, -47 deletions) <details> <summary>View changed files</summary> 📝 `_quarto.yml` (+5 -5) 📝 `contents/benchmarking/benchmarking.qmd` (+23 -1) 📝 `contents/data_engineering/data_engineering.qmd` (+47 -3) 📝 `contents/dl_primer/dl_primer.qmd` (+34 -17) 📝 `contents/embedded_ml/embedded_ml.qmd` (+11 -1) 📝 `contents/frameworks/frameworks.qmd` (+33 -13) 📝 `contents/hw_acceleration/hw_acceleration.qmd` (+11 -1) 📝 `contents/ondevice_learning/ondevice_learning.qmd` (+37 -1) 📝 `contents/ops/ops.qmd` (+11 -1) 📝 `contents/optimizations/optimizations.qmd` (+40 -1) 📝 `contents/privacy_security/privacy_security.qmd` (+23 -1) 📝 `contents/training/training.qmd` (+60 -1) 📝 `custom_callout.lua` (+0 -1) </details> ### 📄 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. --- <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:47:00 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: socratiq
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
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#615
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?