That seems to be a bug. It looks like error messages are not propagated to stdout. I'll file a bug and check into it. Conrad On 11/13/2014 2:24 AM, Mungo Carstairs wrote:
Hello,
I am working on ​driving Chimera from Jalview using the stdin/stdout mechanism (expecting to migrate to REST in future).
I have a case where a 'match' command fails, but the stdout response does not show this.
Using the Chimera command line I can see a message (I guess to stderr)
'Unequal numbers of atoms chosen for evaluation'
but in stdout I just see the same message as for a successful match e.g.:
'Executing match ['#1:1-69.B,96.B@CA', '#0:1-69.A,96.A@CA'], no iteration'
Is there a way to detect that the match has failed and/or capture the stderr output?
Thanks,
Mungo Carstairs
The University of Dundee is a registered Scottish Charity, No: SC015096
_______________________________________________ Chimera-users mailing list Chimera-users@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users