-
Notifications
You must be signed in to change notification settings - Fork 4
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: seqcode/seqcode-core
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: dc7ffe3
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: seqcode/seqcode-core
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: aaa5e5b
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 9 files changed
- 3 contributors
Commits on Sep 18, 2023
-
Fixing a doozy of a bug in ReadDB. Full description follows to document.
This issue became apparent when the readFloats method in Bits.java started throwing Socket timeouts after ReadDB was set up on a new data server (and after a move to Java 11). Upon investigation, the bug was only happening when bytesLeftover was non zero and when only a few bytes remained to be read from the stream (typically less than 4). It turned out that both readInts() and readFloats() had lines as follows to calculate how many bytes to read from the stream: int toread = Math.min(((count - outputpos) * 4), buffer.length - bytesLeftover); This did not account for a non-zero bytesLeftover value. The lines should have been: int toread = Math.min(((count - outputpos) * 4)-bytesLeftover, buffer.length - bytesLeftover); (fixed now) The effect of this bug was that readInts was occassionally reading too many bytes from the stream, reading into the bytes sent by sendFloats by the relevant ServerTask. This left too few bytes for readFloats(). The data read by readFloats was probably nonsense too. Why didn't we notice this before? It seems like this was only an issue in situations where bytesLeftover was non-zero, and that seems to mostly happen when the Client is reading data faster than the ServerTask can send it. The new data server has low latency, so this may be why we only noticed it now (note that the bug was not occurring as frequently from a home connection). Furthermore, the buffer on ServerTask was mistakenly hardcoded as 8192 bytes, whereas the Client had a buffer size of 8192*16. Thus, this also contributed to the Client reading faster than ServerTask was writing. I don't think this issue would have contributed to erroneous analyses, unless folks were ignoring Socket timeout errors.
Configuration menu - View commit details
-
Copy full SHA for 126e4f4 - Browse repository at this point
Copy the full SHA 126e4f4View commit details
Commits on Nov 17, 2024
-
Adding rpm option to wig exporter
Shaun Mahony committedNov 17, 2024 Configuration menu - View commit details
-
Copy full SHA for 2c76410 - Browse repository at this point
Copy the full SHA 2c76410View commit details -
Merge branch 'master' of github.com:seqcode/seqcode-core
Shaun Mahony committedNov 17, 2024 Configuration menu - View commit details
-
Copy full SHA for 0c3e903 - Browse repository at this point
Copy the full SHA 0c3e903View commit details
Commits on Jun 26, 2025
-
Bug fix: count start coord in fragment length
1-based coordinates should be end - start + 1 when computing fragment length
Configuration menu - View commit details
-
Copy full SHA for 5b86aa2 - Browse repository at this point
Copy the full SHA 5b86aa2View commit details -
This file loader fetch both reads of a pair to determine 5' position, it avoids the issue that we couldn't infer CIGAR string of read2 given only read1 in SAMFileHitLoader
Configuration menu - View commit details
-
Copy full SHA for 9f2682a - Browse repository at this point
Copy the full SHA 9f2682aView commit details
Commits on Jul 18, 2025
-
Adding a CPM normalization to the meta-maker
Shaun Mahony committedJul 18, 2025 Configuration menu - View commit details
-
Copy full SHA for 09fcd84 - Browse repository at this point
Copy the full SHA 09fcd84View commit details -
There was a bug where the if clause for SAM/BAM was not connected to everything else
Shaun Mahony committedJul 18, 2025 Configuration menu - View commit details
-
Copy full SHA for aaa5e5b - Browse repository at this point
Copy the full SHA aaa5e5bView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff dc7ffe3...aaa5e5b