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

[PR #48] [MERGED] Adding Exercise Motion/Anomaly Detection #2507

New Issue
Closed
opened 2026-04-13 13:09:34 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 13:09:34 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/harvard-edge/cs249r_book/pull/48
Author: @Mjrovai
Created: 11/3/2023
Status: ✅ Merged
Merged: 11/3/2023
Merged by: @profvjreddi

Base: main ← Head: hands-on-exercises

📝 Commits (2)

  • 6131a76 Adding Exercise Motion/Anomaly Detection
  • 71ef842 Rename the files for consistency + learning objectives

📊 Changes

36 files changed (+421 additions, -1 deletions)

View changed files

📝 _quarto.yml (+1 -0)
➕ cs249r_book.Rproj (+13 -0)
➕ images/imgs_motion_classif/Parameters_definition.jpg (+0 -0)
➕ images/imgs_motion_classif/anom_det_train.jpg (+0 -0)
➕ images/imgs_motion_classif/anomaly-boat.jpg (+0 -0)
➕ images/imgs_motion_classif/anomaly_detect.jpg (+0 -0)
➕ images/imgs_motion_classif/anomaly_detect.png (+0 -0)
➕ images/imgs_motion_classif/case.jpg (+0 -0)
➕ images/imgs_motion_classif/classes.jpg (+0 -0)
➕ images/imgs_motion_classif/classes_mov_def.jpg (+0 -0)
➕ images/imgs_motion_classif/collect_data.jpg (+0 -0)
➕ images/imgs_motion_classif/data-forw.jpg (+0 -0)
➕ images/imgs_motion_classif/data_explorer.jpg (+0 -0)
➕ images/imgs_motion_classif/dataset.jpg (+0 -0)
➕ images/imgs_motion_classif/deploy.jpg (+0 -0)
➕ images/imgs_motion_classif/device.jpg (+0 -0)
➕ images/imgs_motion_classif/feature_generation.jpg (+0 -0)
➕ images/imgs_motion_classif/idle_result.jpg (+0 -0)
➕ images/imgs_motion_classif/impulse-block.jpg (+0 -0)
➕ images/imgs_motion_classif/impulse.jpg (+0 -0)

...and 16 more files

📄 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.
    • [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

    • All references are correctly listed at the end of the chapter.
    • 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

    • All group members have reviewed and approved the chapter.
    • 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.
    • 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

    • [ x] The chapter is pushed to the correct branch on the repository.
    • [x ] 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/48 **Author:** [@Mjrovai](https://github.com/Mjrovai) **Created:** 11/3/2023 **Status:** ✅ Merged **Merged:** 11/3/2023 **Merged by:** [@profvjreddi](https://github.com/profvjreddi) **Base:** `main` ← **Head:** `hands-on-exercises` --- ### 📝 Commits (2) - [`6131a76`](https://github.com/harvard-edge/cs249r_book/commit/6131a76ba0e625e5ef341d40da97de09014573f9) Adding Exercise Motion/Anomaly Detection - [`71ef842`](https://github.com/harvard-edge/cs249r_book/commit/71ef842c37188330cdebe22e8eddb77ccb5647a2) Rename the files for consistency + learning objectives ### 📊 Changes **36 files changed** (+421 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `_quarto.yml` (+1 -0) ➕ `cs249r_book.Rproj` (+13 -0) ➕ `images/imgs_motion_classif/Parameters_definition.jpg` (+0 -0) ➕ `images/imgs_motion_classif/anom_det_train.jpg` (+0 -0) ➕ `images/imgs_motion_classif/anomaly-boat.jpg` (+0 -0) ➕ `images/imgs_motion_classif/anomaly_detect.jpg` (+0 -0) ➕ `images/imgs_motion_classif/anomaly_detect.png` (+0 -0) ➕ `images/imgs_motion_classif/case.jpg` (+0 -0) ➕ `images/imgs_motion_classif/classes.jpg` (+0 -0) ➕ `images/imgs_motion_classif/classes_mov_def.jpg` (+0 -0) ➕ `images/imgs_motion_classif/collect_data.jpg` (+0 -0) ➕ `images/imgs_motion_classif/data-forw.jpg` (+0 -0) ➕ `images/imgs_motion_classif/data_explorer.jpg` (+0 -0) ➕ `images/imgs_motion_classif/dataset.jpg` (+0 -0) ➕ `images/imgs_motion_classif/deploy.jpg` (+0 -0) ➕ `images/imgs_motion_classif/device.jpg` (+0 -0) ➕ `images/imgs_motion_classif/feature_generation.jpg` (+0 -0) ➕ `images/imgs_motion_classif/idle_result.jpg` (+0 -0) ➕ `images/imgs_motion_classif/impulse-block.jpg` (+0 -0) ➕ `images/imgs_motion_classif/impulse.jpg` (+0 -0) _...and 16 more files_ </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** - [ ] All references are correctly listed at the end of the chapter. - [ ] 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** - [ ] All group members have reviewed and approved the chapter. - [ ] 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. - [ ] 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** - [ x] The chapter is pushed to the correct branch on the repository. - [x ] 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-04-13 13:09:34 -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#2507
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?