Skip to content

Commit 1ec77d1

Browse files
committed
docs on lossy
1 parent 5e57447 commit 1ec77d1

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

docs/archive-lossy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# A Guide for Archiving Lossy Data
22

3-
Lossy compression of raw nanopore signal data can be a great way to save disk space without significantly impacting basecalling and modification calling accuracy. This makes it particularly suitable for archiving, especially if you are running short of available disk space. For instance, we were running out of disk space in our in-house storage systems at Garvan Institute long read sequencing service. So we lossy compressed all our historical datasets, the original BLOW5 files that consumed X TB, reduced to Y after compressed to BLOW5s with lossy compression.
3+
Lossy compression of raw nanopore signal data can be a great way to save disk space without significantly impacting basecalling and modification calling accuracy. This makes it particularly suitable for archiving, especially if you are running short of available disk space. For instance, we were running out of disk space in our in-house storage systems at Garvan Institute long read sequencing service. So we lossy compressed all our historical datasets, the original BLOW5 files that consumed 275 TB, reduced to 172 TB after compressed to BLOW5s with lossy compression.
44

55
Naturally, one may be concerned that this conversion would significantly deteriorate the quality of their data. Extensive benchmark results on the negligible impact of lossy compression strategy is presented in our [Genome Research publication](https://genome.cshlp.org/content/35/7/1574). To further remedy any concerns, this guide outlines a number of sanity checks which when successful give confidence in the lossy conversion.
66

docs/archive.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -227,4 +227,4 @@ However, note that sometimes this test diff will cause false errors due to base-
227227

228228
---
229229

230-
As of 2025, now you can further reduce the size of BLOW5 by 30-40% by using lossy compression which has neglagle impact on basecalling/modcalling accuracy. Please refer to the page ["A Guide for Archiving Lossy Data"](archive-lossy.md) for more information.
230+
As of 2025, now you can further reduce the size of BLOW5 by 30-40% by using lossy compression which has negligible impact on basecalling/modcalling accuracy. Please refer to the page ["A Guide for Archiving Lossy Data"](archive-lossy.md) for more information.

docs/bits-lossy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ In the table below, slow5tools version column indicates from which version the p
1616
| dna | sqk-lsk110 | MinION | 4000 | 1.3.1 | 3 |
1717
| dna | sqk-lsk110 | PromethION | 4000 | 1.3.1 | 2 |
1818
| dna | sqk-lsk110 | PromethION  p2_solo | 4000 | 1.3.1 | 2 |
19-
| dna | sqk-lsk112 | GridION | 4000 | 1.3.0 | 3 |
19+
| dna | sqk-lsk112 | GridION | 4000 | 1.3.1 | 3 |
2020
| dna | sqk-lsk112 | MinION | 4000 | 1.3.1 | 3 |
2121
| dna | sqk-lsk112 | PromethION | 4000 | 1.3.1 | 3 |
2222
| dna | sqk-lsk112 | PromethION  p2_solo | 4000 | 1.3.1 | 3 |

0 commit comments

Comments
 (0)