Corrections to Molecular Docking in the AI Era. Back to the hub.
A page that has been printed cannot be patched, so this is where corrections live. Entries name the printing they apply to, because a correction made in the second printing is not an error in the second printing.
| Printing | Page | Description | Correction |
|---|---|---|---|
| No errata recorded. This page is where they will appear. | |||
Please report anything that looks wrong, including in the code. Two ways, and neither is preferred:
It helps to include the printing, if the copyright page gives one, and the page number. For code, the chapter folder and the failing command are enough.
Where a correction affects code rather than prose, the repository is fixed as well, and the commit is the record. Every measured value the book prints is asserted by a test in the repository, so a divergence between page and code shows up as a failing build rather than as a reader's afternoon.
Every dock.nexagenlabs.com/chNN address in the book is a redirect
rather than a destination, and it is served as a 302, not a
301. That single digit is what keeps those addresses correctable. A
301 is cached by the browser and by intermediaries indefinitely: a reader who
followed one once would go on being sent to the old target no matter what was
changed at this end — unreachable by any later correction, with nothing
on screen to say so. A 302 is looked up every time, so where a chapter points
can still be changed after the book is printed.
Software moving on is not an erratum. Tool versions and model licences that have changed since the book was written are on the versions page.