You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2023. It is now read-only.
I have a project in which the movies present different number of frames (1st movie 6 frames, 2sd movie 7 frames, 3rd movie 8 frames,...) Most of the movies have 7 frames. The import movies works properly, and Scipions shows that the output is SetOfMovies 8000x8000x7.
However, when I run the xmipp correlation alignment then the protocol fails. My guess is that the number of frames is fixed in the "import movies". And my questions is: How should this problem be fixed? Defining and arbitrary number of frames in the import movies? making that each protocol that work with movies analyze the number of frames of each movie?...
If we are moving towards tomography, I think this issue might be relevant
Kind regards
The text was updated successfully, but these errors were encountered:
My solution was to fix the number of frames to align from 1-6, because 6 is the minimum number of frames of the set the set of movies. But I think this should not be the solution because a lot of information is rejected....
@Vilax , what is happening in tomography? Each series of a tilt series might have a different number of frames. Sorry, I'm not that familiar with tomography.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dear All,
I have a project in which the movies present different number of frames (1st movie 6 frames, 2sd movie 7 frames, 3rd movie 8 frames,...) Most of the movies have 7 frames. The import movies works properly, and Scipions shows that the output is SetOfMovies 8000x8000x7.
However, when I run the xmipp correlation alignment then the protocol fails. My guess is that the number of frames is fixed in the "import movies". And my questions is: How should this problem be fixed? Defining and arbitrary number of frames in the import movies? making that each protocol that work with movies analyze the number of frames of each movie?...
If we are moving towards tomography, I think this issue might be relevant
Kind regards
The text was updated successfully, but these errors were encountered: