Fix scaling: take chromsizes from header #239
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
pairtools/tests/test_scaling.py Line 27 in 8c41a26 Are single unmapped pairs somehow supposed to contribute to scaling? I think this might be why the test fails... |
Member
|
nah, they are never counted.
…On Fri, 3 May 2024 at 15:34, Ilya Flyamer ***@***.***> wrote:
https://github.com/open2c/pairtools/blob/8c41a26b3f3a3905e307f3baa4b547203394dca1/tests/test_scaling.py#L27
Are single unmapped pairs somehow supposed to contribute to scaling? I
think this might be why the test fails...
—
Reply to this email directly, view it on GitHub
<#239 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG64CVEOSBP5SA34U4CKWLZAOG7NAVCNFSM6AAAAABHFQMVTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJTGAZTKMJSG4>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
Member
Author
|
Then why does the test assert 9 total pairs? It doesn't make sense to me, but somehow I guess this test was passing before? |
Member
Author
|
(As an aside, in the file there is a pair with both sides beyond the end of the chromosome... should that actually error or warn at least?) |
Member
Author
|
OK, I think I know where the problem is: when not chromsizes are provided, internally they are created from the data, and then there is a fake chrom "!" which I guess just behaves like any other chromosome... pairtools/pairtools/lib/scaling.py Line 143 in 8c41a26 So I would say the test is wrong in this case? |
Phlya
commented
Jun 4, 2024
|
|
||
| elif isinstance(pairs, str) or hasattr(pairs, "buffer") or hasattr(pairs, "peek"): | ||
| pairs_df, _, _ = pairsio.read_pairs(pairs, nproc=nproc_in, chunksize=chunksize) | ||
| pairs_df, _, chromsizes = pairsio.read_pairs( |
Member
Author
|
@golobor can we merge this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Scaling without a view was broken! Docs said it would use the chromsizes from the header, but there was no code that was doing it...