Not a logical operator, but a control operator
Lately in my PhD research, I have been using SMARTS notation within queries for substructure matching.
In SMARTS, the ampersand ‘&’ character is used as a logical operator to form expressions combining so-called atom and bond primitives.
Put simply: an ampersand combines properties specified for an atom or bond into one expression.
For a very simple example, let’s say I wanted to find all C’s bonded to a specific number of hydrogen atoms. I would express my query as the following SMARTS string:
where x is the no. of hydrogen atoms.
All well and good while prototyping code in Jupyter notebooks.
However I started executing my scripts in the command line using Python’s
argparse module, and I wanted to specify SMARTS strings as inputs.
These SMARTS contain ampersands. In my haste, I ran it in the CL like this:
$ python myscript.py -smarts [#6&H2] > -bash: H2]-: command not found
Of course, the ampersand has its own meaning in
bash. More specifically, it is a control operator for job execution, as explained in the GNU Bash Reference Manual:
“If a command is terminated by the control operator ‘&’, the shell executes the command asynchronously in a subshell. This is known as executing the command in the background, and these are referred to as asynchronous commands.”
The very simple solution of course is to simply add quotation marks around the SMARTS string CL input:
$ python myscript.py -smarts '[#6&H2]'
A timely reminder to get more coffee…
Share onTwitter Facebook LinkedIn
Leave a comment
Your email address will not be published. Required fields are marked *