hts wide maxdepth limit check #1965
Draft
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.
This is a draft, to fix samtools/samtools#2238
htsFile updated to hold extra data, when max depth check is enabled.
The max depth check is set using input-fmt-option, seq_max_depth.
Extra data to hold are, buffer to track depth on a window of positions, tid, start/end of window and max depth above which reads can be discarded.
This check is made only for data sorted on position and for others this shall not be used.
A buffer is allocated, which holds depth against positions in read. New reads update the depth, for all positions it spans, and if depth is below the limit for any position, it is passed to user and discarded otherwise. Read continues and another read covering a position with lower depth, if found is passed to user and read finishes with end of file if nothing else is found.
As a new higher start position is found, depth up to that position is discarded and window is updated to hold data from that position onwards.
Pair reads are not considered in this.