Fix chunk extraction and subsequent GBWT generation #4436
Merged
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.
Changelog Entry
To be copied to the draft changelog by merger:
vg chunk
andvg find
now generate subpaths with subrange metadata when cutting up paths.vg gbwt
will accept subranges on fragment 0 and discard the fragment number.Description
This should let you do:
But it changes a lot of how chunk extraction on reference paths names things, so it might break a bunch of CLI tests. And it needs some unit tests to make sure that subpath start offsets are accurately computed.