<div dir="ltr"><div class="gmail_extra">On Wed, Apr 10, 2013 at 3:05 PM, James Stroud <span dir="ltr"><<a href="mailto:xtald00d@gmail.com" target="_blank">xtald00d@gmail.com</a>></span> wrote:<br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">
<div>=<font face="Monaco">% cctbx.python ./tst_sa.py</font></div><div><div><font face="Monaco">CifParserError: /Applications/ccp4-6.3.0/lib/data/monomers/list/mon_lib_list.cif(line 1) : error 4 : Unexpected token, at offset -1</font></div>
</div><div><div><font face="Monaco"> near global</font></div></div><div><div><font face="Monaco"> : unexpected input...</font></div></div><div><div><font face="Monaco"> expected one of : Actually dude, we didn't seem to be expecting anything here, or at least</font></div>
</div><div><div><font face="Monaco">I could not work out what I was expecting, like so many of us these days!</font></div></div></blockquote></div></blockquote><div><br></div><div style>The monomer library does indeed contain many files that don't conform to the official CIF standard, but that usually isn't a problem because the strict parsing is supposed to be disabled. Is the script you're running mmtbx/dynamics/tst_sa.py? Try setting the environment variable LIBTBX_DISABLE_TRACEBACKLIMIT and re-run, and send us the traceback.</div>
<div style><br></div><div style>-Nat</div></div></div></div>