15:43:32drmeisterMy phone died last night - I've been dealing with it this morning.
15:44:10drmeisterscymtym: I am making contact with the Open Force Field folks to see what this SMARTS syntax means.
15:46:44drmeisterThey have a more detailed description of the force field file but they link to the SMARTS and SMIRKS documentation that we already have for details on those.
21:06:38drmeister::notify scymtym It's exactly as painful as I thought it would be to try and get hold of these people to ask them how this is implemented. They refer me to the SMARTS links that we have already read and then they tell me to look in the rdkit code. I don't think the answer is in there.
21:06:38Colleendrmeister: Got it. I'll let scymtym know as soon as possible.
21:09:19drmeister::notify scymtym I think the answer is buried in the OpenEye library. I am starting to think that the `@1` is redundant. The numbers are used to indicate rings, the `@` indicates a ring. I think `@1` and `1` are equivalent.
21:09:19Colleendrmeister: Got it. I'll let scymtym know as soon as possible.
21:14:16drmeister::notify scymtym I'm really rusty with esrap - if I want to optionally allow an `@` in `(defrule atom-pattern ...)` how would I do that? Instead of `(and acyclic-atom-pattern (? parser.common-rules:integer-literal/decimal))` to allow an optional `@` before the integer?
21:14:16Colleendrmeister: Got it. I'll let scymtym know as soon as possible.
21:14:26yitziIn other words, they don't know where the parser is?