Opened 10 years ago

Closed 9 years ago

Last modified 9 years ago

#253 closed defect (fixed)

ribbon 3j3f gives error

Reported by: Elaine Meng Owned by: Conrad Huang
Priority: blocker Milestone:
Component: Depiction Version:
Keywords: Cc:
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description

Opening rna structure 3j3f gives an error apparently related to ribbon representation. This is part of a ribosome and the entry is obsolete since now the whole structure is entry 4v6x. However, if you use command "ribbon nucleic" on 4v6x the same error is obtained. Seems like it's due to some missing atoms. I tried some other DNA and RNA structures and they didn't have this problem.

Error processing trigger "graphics update"
Traceback (most recent call last):
File "/Users/chimera/Applications/ChimeraX_Daily.app/Contents/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/chimerax/core/triggerset.py", line 114, in invoke
return self._func(self._name, data)
File "/Users/chimera/Applications/ChimeraX_Daily.app/Contents/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/chimerax/core/atomic/structure.py", line 233, in _update_graphics_if_needed
self._create_ribbon_graphics()
File "/Users/chimera/Applications/ChimeraX_Daily.app/Contents/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/chimerax/core/atomic/structure.py", line 370, in _create_ribbon_graphics
ribbon = Ribbon(coords, guides)
File "/Users/chimera/Applications/ChimeraX_Daily.app/Contents/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/chimerax/core/atomic/ribbon.py", line 12, in init
raise ValueError("different number of coordinates and guides")
ValueError: different number of coordinates and guides

Change History (2)

comment:1 by Elaine Meng, 9 years ago

Resolution: fixed
Status: newclosed

apparently fixed, neither 3j3f or "ribbon nucleic" on 4v6x generate the error and nucleic ribbons are shown

comment:2 by Elaine Meng, 9 years ago

was probably the same issue as #229

Note: See TracTickets for help on using tickets.