-
Notifications
You must be signed in to change notification settings - Fork 3
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
New NAGL docs take 2 #21
Conversation
ac9a386
to
fb74b25
Compare
c896ade
to
a37c64d
Compare
|
34a08e3
to
64d0870
Compare
Co-authored-by: Matt Thompson <[email protected]>
docs/theory.md
Outdated
|
||
In a molecular graph, atoms are nodes and bonds are edges. A molecular graph can store extra information in its nodes and edges; in a Lewis structure, this is things like an atom's element and lone pairs, or a bond's bond order or stereochemistry, but for a molecular graph they can be anything. Element and bond order are usually somewhere near the top of the list. Envisioning a molecule as a graph lets us apply computer science techniques designed for graphs to molecules. | ||
|
||
Note that a particular molecular species may have more than one molecular graph topology that represents it. This most commonly happens with tautomers and resonance forms. NAGL operates on molecular graphs, and on the OpenFF [`Molecule`] class, and it doesn't try to be clever about whether two molecules are the same or not. If you want tautomers to produce the same charges, you may need to prepare your dataset accordingly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Non-blocking, since the ResonanceEnumerator is not very well documented and hidden in utils) -- this might be a good place to eventually mention the ResonanceEnumerator which will enumerate all resonance forms of a molecule so that properties such as formal charges or hybridisation can be averaged.
OK I think this is ready for review! |
This reverts commit 70d5013.
More docstrings!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The docs look beautiful -- thanks so much for all the work you put into this! LGTM!
Could you please add yourself to the AUTHORS list too?
Co-authored-by: Lily Wang <[email protected]>
This PR adds documentation. Replaces #12 with a branch that has a clean history of not touching the main codebase.
Changes made in this Pull Request:
PR Checklist