Opened 4 years ago

Closed 4 years ago

#5364 closed defect (duplicate)

ChimeraX Molecular Dynamics Viewer

Reported by: finnegan.73@… Owned by: pett
Priority: normal Milestone:
Component: MD/Ensemble Analysis Version:
Keywords: Cc:
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description

Hi, my name is Tyler Finnegan and I'm a graduate student in the Badjic lab at Ohio State. I recently was trying to visualize an MD trajectory using your Molecular Dynamics Viewer (MDV). What I did was create a pdb file of the trajectory using VMD and upon trying to load this file into the MDV I received the following error:


IndexError: list index out of range

File "C:\My\path\to\chimeral\UCSF\ChimeraX\1.2\site-packages\com\kdiller\dynamics\viewer\gui.py", line 227, in openFile
self.atomStruct.atoms.coords = self.atomLocation[0]

See log for complete Python traceback.


I'm not sure if this error was with the python module, gui.py, or whether I need to format my input PDB differently. Currently it is formatted with AMBER TERs in-between molecules and ENDs between frames--I believe this is the issue. I've attached this PDB for your reference. When it was loaded in manually with the command line,


open 'D:/My/Path/To/File/CAR_traj_testing.pdb' coordset true

It gave an error in the log box which seemed to have issue with the 'END' in the PDB file. Is there another word I should use as a delimiter between frames in my pdb?



Thanks in advance for your help and I look forward to hearing back from you!


Best,

Tyler Finnegan



CAR_traj_testing.pdb

Attachments (1)

CAR_traj_testing.pdb (89.3 MB ) - added by finnegan.73@… 4 years ago.
Added by email2trac

Change History (3)

by finnegan.73@…, 4 years ago

Attachment: CAR_traj_testing.pdb added

Added by email2trac

comment:1 by pett, 4 years ago

Component: UnassignedMD/Ensemble Analysis
Owner: set to pett
Platform: all
Project: ChimeraX
Status: newaccepted

comment:2 by pett, 4 years ago

Resolution: duplicate
Status: acceptedclosed

Duplicate of #5363

Note: See TracTickets for help on using tickets.