<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Sun, Jul 11, 2010 at 5:36 PM, Mark A Saper <span dir="ltr"><<a href="mailto:saper@umich.edu" target="_blank">saper@umich.edu</a>></span> wrote:<br>
</div><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">When running phenix.refine from the GUI, definitions for rigid body groups in phenix.refine that are syntactically wrong, causes the job to just hang with "running" status but no CPU is used. �It would be nice if either the GUI checked for valid selections, or if phenix.refine returned an appropriate error code that would be recognized by the GUI.</div>
</blockquote><div><br></div></div><div>Actually, the latter is exactly what should happen - the only reason why it wouldn't is if you've stumbled across a low-level C++ error that can't be propagated. �I already modified the code to handle one such error a couple of months ago (it should be in 1.6.2) but there may be others I don't know about.</div>
</div></blockquote><div><br></div><div>Okay, after a quick experiment, it seems that this is almost exactly what was happening. �Next build will have the fix.</div><div><br></div><div>-Nat</div></div>