The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Version |
Location |
Description |
Submitted By |
Date submitted |
Date corrected |
|
Page figure 2-3
figure 2-3 |
Sorry there are no page numbers in the O'Reilly app which is what I am using.
The content in this table, third row and forth column (The AG_ Cell) is incorrect. It should be AGU, AGC, AGA, AGG, not CGU, CGC, CGA, CGG.
Thank You,
Nancy
Note from the Author or Editor: This is correct -- the figure 2-3 needs to be updated. The error and how it should be fixed is described clearly in the report.
|
Nancy Lao |
May 19, 2020 |
Sep 11, 2020 |
Other Digital Version |
The Reference Genome as Common Framework
The Reference Genome as Common Framework (section) |
I'm so sorry but - in this section - are we not comparing each to the synthetic hybrid? In the hybrid the last word is "doge", but it says for 1 "deleted e" (but it's the same as hybrid) and for 2 "added e" - again same as hybrid, and for 3 - it doesn't mention the deleted e. Therefore, I don't think this example lines up perfectly but I get the meaning.
______________________
The quick brown fax jumped over the lazy doge.
The quick _ fox jumped over their lazy doge.
The quick brown fox jumps over the lazy brown dog.
We’d like to inventory their differences in a way that is not biased toward any single one of them, and is robust to the possibility of adding new mutant sentences as we encounter them. So we create a synthetic hybrid that encapsulates what they have most in common, yielding this:
The quick brown fox jumped over the lazy doge.
We can use this as a common reference coordinate system against which we can plot what is different (if not necessarily unique) in each mutant:
Fourth word, o → a substitution; ninth word, deleted e
Third word deleted; seventh word, added ir; ninth word, added e
Fifth word ed → s substitution; duplication of the third word located after the eighth word
____________________________
Note from the Author or Editor: This report is correct, I think I tweaked the example at some point and failed to adapt some of the text. Here is what should change:
Original:
1. Fourth word, o → a substitution; ninth word, deleted e
2. Third word deleted; seventh word, added ir; ninth word, added e
3. Fifth word ed → s substitution; duplication of the third word located after the eighth word
Update:
1. Fourth word, o → a substitution; ninth word ends with e
2. Third word missing; seventh word ends with ir; ninth word ends with e
3. Fifth word, ed → s substitution; duplication of the third word located after the eighth word; ninth word does not end with e
|
Nancy Lao |
May 19, 2020 |
Sep 11, 2020 |
Printed, Other Digital Version |
Page 142
Under figure 5-6 |
There is an extra "in" in the first line after figure 5-6 (page 142 in the ebook from google).
"Some of the first reads, those shown in in one shade at the top of the pile in Figure 5-6......"
Note from the Author or Editor: This report is correct, the error is present also in the printed version so I assume it's in all of them. The line should read "Some of the first reads, those shown in one shade at the top of the pile in Figure 5-6......"
|
Nawar Dalila |
Jun 09, 2020 |
Sep 11, 2020 |
|
Page 165
4th paragraph (just above fig 6-11) |
The file "sandbox/trioGGVCF.vcf" doesn't exist. Instead the file should have been "sandbox/trio-jointcalls.vcf.gz".
Also, in order for the correct file to be open successfully in IGV, the file needs to be transferred to a google cloud bucket. So, a reference needs to be provided to page #128 and page #129 of the book for creating a google bucket, moving the correct file to google bucket and then opening it in IGV.
Note from the Author or Editor: Report is correct; refer to the section on running HaplotypeCaller and viewing results in IGV for detailed instructions (All fixed in Atlas)
|
Amit |
Jan 16, 2021 |
|
|
Page 195
Mid-page: "The GATK team provides a set of resources..." |
The link to functional annotation resources (https://oreil.ly/LDGdM) gives a 404 error. I believe the correct documentation page is located here:
https://gatk.broadinstitute.org/hc/en-us/articles/360035531732-Funcotator-Annotation-Specifications
Note from the Author or Editor: The report is correct, the https://oreil.ly/LDGdM shortlink should be reassigned to https://gatk.broadinstitute.org/hc/en-us/articles/360035531732-Funcotator-Annotation-Specifications
|
KT Pickard |
Jan 18, 2021 |
|
Printed, Other Digital Version |
Page 224
task ReadItBackToMe |
`String = read_string` is missing the variable name.
`echo "${original_greeting} [...]` differs from (the correct) snippet on page 225.
Note from the Author or Editor: It's actually a bit worse than reported, there's also a line missing. Here's what should change (by page).
Page 224 (print) Original:
input {
String = read_string(written_greeting)
}
Fixed:
input {
File written_greeting
String original_greeting = read_string(written_greeting)
}
Page 225 (print) Original:
command {
echo "${greeting} to you too"
}
Fixed:
command {
echo "${original_greeting} to you too"
}
|
Leonhard Gruenschloss |
May 15, 2020 |
Sep 11, 2020 |
|
Page 251
Right after title "Reverse Engineering the Conditional Switch" |
double space after the first word "At "
Note from the Author or Editor: (Fixed in Atlas)
|
Matthieu J. Miossec |
Jan 28, 2021 |
|
Printed, Other Digital Version |
Page 258
Figure 9-2 |
Dear Authors,
Figure 9-2 (page 258). I can't see exactly how does it correspond to table 9-2 (page 260). I mean the tasks in the graph are different than the ones highlighted in the table. Was the graph only a part of the whole workflow?
Best regards,
Nawar Dalila
Note from the Author or Editor: The figure shown as 9-2 in this edition of the book is the wrong figure, it's actually a duplicate of figure 9-3. Let me know if I need to resend the correct figure.
Also, wasn't sure how to classify this erratum so I pegged it as a formatting problem. It sure is important…
Adding the correct figure 9-2 link from our GCP bucket: https://console.cloud.google.com/storage/browser/_details/genomics-in-the-cloud/figures/v1/gitc_0902.png --Brian
|
Nawar Dalila |
Jun 09, 2020 |
Sep 11, 2020 |
|
Page 284
4th paragraph |
The link to the blog post about dynamically sizing resources (https://oreil.ly/P9Vxg) gives a 404 error. The documentation is in flux, but the current page is located here:
https://support.terra.bio/hc/en-us/articles/360037493451-Can-runtime-parameter-values-be-generated-dynamically-
Note from the Author or Editor: The report is correct but there is a newer resource that is better than the one suggested. The shortlink https://oreil.ly/P9Vxg should be pointed to https://terra.bio/reduce-computing-costs-by-tailoring-resource-allocations-in-workflows/
|
KT Pickard |
Feb 07, 2021 |
|
|
Page 372
Paragraph prior to Wrap-Up and Next Steps |
genome-wide association studies (rather than analysis studies). This mistake also appears at the end of the Jupyter notebook.
Note from the Author or Editor: (Fixed in Atlas and github)
|
Matthieu J. Miossec |
Feb 20, 2021 |
|