From: DeLano, W. <wa...@su...> - 2003-01-23 21:36:42
|
Carsten, You're bumping up against a 63-character limit I currently have for = any one individual argument in PyMOL's internal parser. Obviously I = need to either safeguard that limitation to prevent a crash or eliminate = it. You can still do this in a single selection, as follows select pocket =3D (P_338437 and (resi = 16,17,18,19,54,55,57,58,59,60,61,62,67 or resi = 72,73,74,75,82,86,91,93,95,96,97,99,100,103)) Cheers, Warren -- mailto:wa...@su... Warren L. DeLano, Ph.D. Informatics Manager Sunesis Pharmaceuticals, Inc. 341 Oyster Point Blvd. S. San Francisco, CA 94080 (650)-266-3606 FAX:(650)-266-3501=20 -----Original Message----- From: Schubert, Carsten [mailto:Car...@3d...] Sent: Thursday, January 23, 2003 12:41 PM To: pym...@li... Subject: [PyMOL] Bug in selections Hi,=20 there is a problem in pymol 0.86 under W2K using a long list of residues = in a selection.=20 When I use:=20 select pocket =3D (P_338437 and (resi = 16,17,18,19,54,55,57,58,59,60,61,62,67,72,73,74,75,82,86,91,93,95,96,97,9= 9,100,103)) pymol generates an error and exits.=20 Splitting the selection into 2 parts prevents the crash:=20 select p1 =3D (P_338437 and (resi = 16,17,18,19,54,55,57,58,59,60,61,62,67,72,73,74,75,82,86,91,93))=20 select pocket =3D (p1 or (P_338437 and (resi 95,96,97,99,100,103))=20 Is there a maximum number of elements in a selection statement?=20 BTW the script worked fine in the previous release, 0.82 I guess?=20 Any thoughts?=20 Cheers=20 Carsten=20 |