You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/main/resources/inputdefinition/AtomEditor.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@
9
9
"key": "ATOMIDS",
10
10
"casedKey": "atomIDs",
11
11
"type": "<String>",
12
-
"doc": "Defines one or more (0-based) index-based rules for identifying atoms to edit or use to add new atoms. Rules are separated by newline characters (i.e., each rule is defined in a single line). In each line, each space-separated string (i.e., a word) is interpreted as following: each word is considered a single index until a word is found that corresponds to any keyword (see below). Once the first keyword is found no more words will be interpreted as an index. The order of the indexes is retained. Recognized keywords are (case-insensitive):\n--> 'remove': to request the removal of the matched atoms (mutually exclusive with other behavior-controlling keywords, like 'addAtom' and 'element').\n 'element' <newElementalSymbol>: to request the mutation of the elemental symbol of the matched atoms (mutually exclusive with other behavior-controlling keywords, like 'addAtom' and 'remove').\n --> 'addAtom': to request the addition od a single atom (mutually exclusive with other behavior-controlling keywords, like 'element' and 'remove'). The value of this keyword must start with the elemental symbol of the new atom following by details about the relative position and bonding of such atom: '<el> <string_details>'. Where <string_details> may have the following syntax:\n -----> 'CENTROID' to add an atom in the position defined by the centroid of the matched atoms.\n -----> 'INTERNALCOORDS' to specify the position of the new atom relative to the atoms in the matched atom tuple. To this end this keyword should be followed by a string adhering to this syntax: '<idA> <valueA> [<idB> <valueB> [<idC> <valueC>]]' where <id...> are indexes in the matched tuple of atoms and <value...> are numerical values used together with the indexes to define internal coordinates in the order 'distance', 'angle', 'dihedral' (No second angle!).\n --> 'OnlyBonded': limits to tuples of atoms to those that are connected to form a path visiting the tuple in the order given by the order of the SMARTS. For example, a SMARTS-based rule for tuple '[#1] [#6] [#7]' may be limited to match only substructures where the H atom is connected with any bond to the C atom, which is connected with any bond to the N atom."
12
+
"doc": "Defines one or more (0-based) index-based rules for identifying atoms to edit or use to add new atoms. Rules are separated by newline characters (i.e., each rule is defined in a single line). In each line, each space-separated string (i.e., a word) is interpreted as following: each word is considered a single index until a word is found that corresponds to any keyword (see below). Once the first keyword is found no more words will be interpreted as an index. The order of the indexes is retained. Recognized keywords are (case-insensitive):\n--> 'remove': to request the removal of the matched atoms (mutually exclusive with other behavior-controlling keywords, like 'addAtom' and 'element').\n 'element' <newElementalSymbol>: to request the mutation of the elemental symbol of the matched atoms (mutually exclusive with other behavior-controlling keywords, like 'addAtom' and 'remove').\n --> 'addAtom': to request the addition od a single atom (mutually exclusive with other behavior-controlling keywords, like 'element' and 'remove'). The value of this keyword must start with the elemental symbol of the new atom following by details about the relative position and bonding of such atom: '<el> <string_details>'. Where <string_details> may have the following syntax:\n -----> 'CENTROID' to add an atom in the position defined by the centroid of the matched atoms. Without value, this keyword makes the centroid be computed on all the atom tuple, but is a space-separated list of atoms is given, then only the atoms of the tuple which correspond to the given indexes will be used to compute the centroid (e.g., 'centroid 0 3' places the new atom in between the first and fourth atom of the matched tuple)\n -----> 'INTERNALCOORDS' to specify the position of the new atom relative to the atoms in the matched atom tuple. To this end this keyword should be followed by a string adhering to this syntax: '<idA> <valueA> [<idB> <valueB> [<idC> <valueC>]]' where <id...> are indexes in the matched tuple of atoms and <value...> are numerical values used together with the indexes to define internal coordinates in the order 'distance', 'angle', 'dihedral' (No second angle!).\n --> 'OnlyBonded': limits to tuples of atoms to those that are connected to form a path visiting the tuple in the order given by the order of the SMARTS. For example, a SMARTS-based rule for tuple '[#1] [#6] [#7]' may be limited to match only substructures where the H atom is connected with any bond to the C atom, which is connected with any bond to the N atom."
0 commit comments