-
-
Notifications
You must be signed in to change notification settings - Fork 19
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.
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
Fix smasher failing to include all samples in large studies #2365
Conversation
for sample_page in ( | ||
samples[i * page_size : i + page_size] for i in range(0, len(samples), page_size) | ||
): | ||
for sample_page in (samples[i : i + page_size] for i in range(0, len(samples), page_size)): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't love using i
here since i usually think of i
as a loop counter (it looks like whoever implemented this first did as well since they multiplied it by page size). Could we use start
?
Co-authored-by: Casey Greene <cgreene@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now!
This also looks like it would affect quantpendias. I think that between this and #2368 we should probably rerun quantpendia. |
Yeah I agree. The original issue mentioned specifically our mouse and human quantpendia missing samples. |
strong agree on a re-run |
Issue Number
#2211
Purpose/Implementation Notes
It looks like an indexing issue was preventing us from copying over any more than the first 100 quant files for each experiment in the smasher. Since the range's third parameter is
page_size
, on the second iterationi
ispage_size
, so we effectively takesamples[page_size ** 2 : page_size * 2]
which will be empty.Methods
If this pull request has any implications for data or metadata processing or addresses an issue labeled
sci review
, please include an overview of the methods used (e.g., briefly explain how the data gets processed).See #267 for rationale.
Include sufficient detail for reviewers or users that are not expert developers to evaluate the validity of the approach.
Please attach or link to example input and output data if applicable.
It may also be appropriate to include a description of any functional or unit tests in this section depending on their content.
Any pull request with a methods section requires scientific review in addition to code review.
Types of changes
What types of changes does your code introduce?
Functional tests
List out the functional tests you've completed to verify your changes work locally.
Checklist
Put an
x
in the boxes that apply.Screenshots
Please attach any screenshots that illustrate these changes.