Problems when concatenating trajectories. #4653
Unanswered
FezokaTurbo
asked this question in
Q&A
Replies: 2 comments
-
|
I also had a similar problem when trying to join the trajectories in another program such as VMD, for some motive the time of the frames changes from what it was originally. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Looks like a corrupted file to me or your assumption
is wrong.
This may depend on the code that you're using. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I don't know if my trajectories are, in any way, corrupted, so i tried to work with then to understand how they are responding:
When I try to select the 964th frame of the trajectory, although the trajectory has 1500 frames, a error appers:
https://prnt.sc/zPBiKxNPhten
However, when I try to read the Vignaangularis_all.dcd, the len(u.trajectory) the output is 946:
Am I the only one who has this issue? Where should I start to look to solve this?
Also, there's another problem:
Why does the time change when I write another trajectory file?
When I read the trajectory as such:
The output is in picoseconds(ps), however, when it's read as such:
The output in is (ps/100). Why?
Beta Was this translation helpful? Give feedback.
All reactions