Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Test incompatibility of start/stop/step and frames in AnalysisBase.run(...) #4648

Open
marinegor opened this issue Aug 5, 2024 · 0 comments · May be fixed by #4769
Open

Test incompatibility of start/stop/step and frames in AnalysisBase.run(...) #4648

marinegor opened this issue Aug 5, 2024 · 0 comments · May be fixed by #4769
Labels
Component-Analysis parallelization

Comments

@marinegor
Copy link
Contributor

ValueError produced in case when both non-None frames and start/stop/step are specified, must be tested.

          Any reason why this isn't covered by tests? If not, then at the very least please raise an issue for it to be done later.

Originally posted by @IAlibay in #4162 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component-Analysis parallelization
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Addition of pytest case for not None values for frames and start/stop/step talagayev/mdanalysis
2 participants
@orbeckst @marinegor