Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First part of "robust_ai.qmd" #440

Closed
BravoBaldo opened this issue Sep 9, 2024 · 1 comment · Fixed by #441
Closed

First part of "robust_ai.qmd" #440

BravoBaldo opened this issue Sep 9, 2024 · 1 comment · Fixed by #441

Comments

@BravoBaldo
Copy link
Contributor

  • 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

@profvjreddi
Copy link
Contributor

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 profvjreddi linked a pull request Sep 9, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants