Joshua Kim

I think this is to prevent ambiguity as described [here](http://docs.seqan.de/seqan/3-master-dev/group__alphabet.html) under "Assigning and retrieving values". For a one line initialization you could do this: ```cpp using namespace seqan3::literals; seqan3::phred42 quality_value{'A'_phred42};...

Minimal example: ```cpp seqan3::sam_file_input input_file{input_path}; for (auto & record : input_file) { seqan3::debug_stream

Hello, can I ask about an update to this? I'd be happy to work on this myself if nobody else is currently doing so. I'd also like "valid" BAM files...

@h-2 I'm not sure what all of the seqan2 stuff is for... But I'm sure it makes sense!

Hello @AzothAmmo! Thanks for your suggestion and sorry for the late response. What I'm currently doing is the following: ```cpp class X { private: std::streampos position{}; public: template void serialize(Archive...

Hi @AzothAmmo, I'm still dealing with this issue and was wondering if you could offer any more insight. The workaround I proposed earlier doesn't actually work. It writes fine, by...

Hey Daniel! I do mean secondary alignments. Supplementary alignments are also important for variant calling, but as you mention they use the SA tag. Crucially, for supplementary alignments, all positions...

The other nice side effect is that the files will be much smaller, as a BED/wig file with values of just 1's can be written much more succinctly than a...

Not urgent at all. Interesting point about bitvectors not being able to be read/written in parallel. I didn't know that! Is that a seqan3 limitation or a hardware thing?

```r all(rownames([email protected])==colnames(data_seurat_115)) all(rownames([email protected])==colnames(data_seurat_135)) ``` Both yield TRUE.