Opened 10 years ago
Closed 9 years ago
#102 closed defect (fixed)
Strange atom spec parsing of model ids with commas
Reported by: | Tom Goddard | Owned by: | Conrad Huang |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Command Line | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | chimera |
Description
An atom spec "#1.1,2" is giving no models although there are open models #1.1, #1.2 and #2. The error message that prints str(spec.evaluate(session)) lists the spec as #1.1.2 with the comma replaced by a period. Not sure what is going on.
fitmap #1.1,2 inmap #2
......................
No atoms or maps for #1.1.2
Does #1.1,2 mean #1.1 and #2 or is it supposed to mean #1.1 and #1.2. Neither interpretation is working.
Note:
See TracTickets
for help on using tickets.
Fixed in e26d659.
There was a copy-and-paste error where a field was not properly renamed.
The interpretation of "#1.1,2" is #1.1 and #1.2.