github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-05-08 09:57:21 -05:00
Code Issues 81 Packages Projects Releases 24 Wiki Activity

First part of "robust_ai.qmd" #212

New Issue
Closed
opened 2026-03-22 15:30:38 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-22 15:30:38 -05:00
Owner
Copy Link

Originally created by @BravoBaldo on GitHub (Sep 9, 2024).

  • In "Introduction",
    • Search "in the presence of hardware, software, and errors." --> maybe "in the presence of hardware[, human] and software errors."
    • The 'introduction' of the list refer to errors Hw, Sw and Human but next 'human' is missing and appears 'Model Robustness' !
  • Search "SDCS" the first occurrence must be "SDCs" (s in lowercase)
  • The link about fault of "Boeing 787" ("https://www.engineering.com/story/vzrxw") is broken
  • Search "Show a real-world example from" ---> "S" must be in lowercase
  • Please review titles of sub-section of "17.5 Software Faults" they are not numbered
  • "17.4.1 Adversarial Attacks" is almost the same as "14.4.3 Adversarial Attacks" in "privacy_security.qmd". Please review.
  • in "robust_ai.qmd", search "---" please verify result.
  • Search "fall under black black-box box grey-boxes." please review sentence.
  • "17.4.2 Data Poisoning" is almost the same as "14.4.2 Data Poisoning" in "privacy_security.qmd". Please review.

P.S.:
In "sustainable_ai", "design systems hardware with environmental impact in mind." ---> first D in uppercase

Originally created by @BravoBaldo on GitHub (Sep 9, 2024). - In "Introduction", - Search "in the presence of hardware, software, and errors." --> maybe "in the presence of hardware[, human] and software errors." - The 'introduction' of the list refer to errors Hw, Sw and Human but next 'human' is missing and appears 'Model Robustness' ! - Search "SDCS" the first occurrence must be "SDCs" (s in lowercase) - The link about fault of "Boeing 787" ("https://www.engineering.com/story/vzrxw") is broken - Search "Show a real-world example from" ---> "S" must be in lowercase - Please review titles of sub-section of "17.5 Software Faults" they are not numbered - "17.4.1 Adversarial Attacks" is almost the same as "14.4.3 Adversarial Attacks" in "privacy_security.qmd". Please review. - in "robust_ai.qmd", search "\-\--" please verify result. - Search "fall under black black-box box grey-boxes." please review sentence. - "17.4.2 Data Poisoning" is almost the same as "14.4.2 Data Poisoning" in "privacy_security.qmd". Please review. P.S.: In "sustainable_ai", "design systems hardware with environmental impact in mind." ---> first D in uppercase
GiteaMirror added the area: book label 2026-03-22 15:30:38 -05:00
GiteaMirror commented 2026-03-22 15:30:40 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Sep 9, 2024):

Thanks @BravoBaldo for the feedback!

"17.4.2 Data Poisoning" is almost the same as "14.4.2 Data Poisoning" in "privacy_security.qmd". Please review.

Ah, good catch! We were trying to move content out of the privacy and security chapter when writing this chapter, so that makes sense!

  • Search "in the presence of hardware, software, and errors." --> maybe "in the presence of hardware[, human] and software errors."

Ah I thought I had removed the human element, but you are right its still there. It gets too messy with human errors. Too many to focus on, but I suppose we should keep it for coverage perspective because that is a real form of error.

I updated this... and the rest! 🙏

@profvjreddi commented on GitHub (Sep 9, 2024): Thanks @BravoBaldo for the feedback! > "17.4.2 Data Poisoning" is almost the same as "14.4.2 Data Poisoning" in "privacy_security.qmd". Please review. Ah, good catch! We were trying to move content out of the privacy and security chapter when writing this chapter, so that makes sense! > * Search "in the presence of hardware, software, and errors." --> maybe "in the presence of hardware[, human] and software errors." Ah I thought I had removed the human element, but you are right its still there. It gets too messy with human errors. Too many to focus on, but I suppose we should keep it for coverage perspective because that is a real form of error. > * The link about fault of "Boeing 787" ("https://www.engineering.com/story/vzrxw") is broken I updated this... and the rest! 🙏
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 area: book
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#212
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?