> As far as I understood Miguel already has located the cause of the
> chain selection problem.
Correct.
Miguel
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile med
>> I have defined several sets and they seem to work for me.
>>
>> Please try to send me a specific example.
>
> When I wrote the above I didn't realize the connection with the chain
> selection problem I detected later. In my set definitions the chain
> usually is also included in the atom express
Quoting Egon Willighagen <[EMAIL PROTECTED]>:
On Monday 27 March 2006 09:24, [EMAIL PROTECTED] wrote:
Example: PDB entry '1DEH'
BROKEN : define het_CLa 601:A & hetero & not water;
WORKING: define het_CLa 601 & hetero & not water;
Are you using mmCIF files? If so, 10.00.49 has CIF reading cod
On Monday 27 March 2006 09:24, [EMAIL PROTECTED] wrote:
> Example: PDB entry '1DEH'
>
> BROKEN : define het_CLa 601:A & hetero & not water;
> WORKING: define het_CLa 601 & hetero & not water;
Are you using mmCIF files? If so, 10.00.49 has CIF reading code a bit in a
flux... I'm in the process of
Quoting Miguel <[EMAIL PROTECTED]>:
Rolf wrote:
The parser doesn't
complain about the set names but with all self-defined sets zero atoms
are selected. The predefined sets still work.
Rolf,
I am not able to reproduce this problem.
I have defined several sets and they seem to work for me.
Rolf wrote:
>> The parser doesn't
>> complain about the set names but with all self-defined sets zero atoms
>> are selected. The predefined sets still work.
Rolf,
I am not able to reproduce this problem.
I have defined several sets and they seem to work for me.
Please try to send me a specific
6 matches
Mail list logo
