Greetings, I am the author of Genozip, a compression software for BAM/FASTQ/VCF etc (www.genozip.com). One of our users opened a support ticket regarding a failing compression of a FADE-generated BAM file. After much investigation, it turned out that the issue was a single alignment (out of half a billion) which had an ab:Z field that appears to be entirely corrupted - many non-printable characters.
ab:Z:^L!"^!"! !^"""^K^^
^^M^]^R^Z"^L^M!^N"""^M!^N^]^\ESC""^L ^N^O^]^H^P"""^^^^"^^!ESC!^R ^]!!#^^\ ^O
In addition, you might want to consider adding a @ PG line for FADE in the SAM header - this will make it easier for other software packages (like ours) to understand the properties of data with which we are interacting.
Greetings, I am the author of Genozip, a compression software for BAM/FASTQ/VCF etc (www.genozip.com). One of our users opened a support ticket regarding a failing compression of a FADE-generated BAM file. After much investigation, it turned out that the issue was a single alignment (out of half a billion) which had an ab:Z field that appears to be entirely corrupted - many non-printable characters.
ab:Z:^L!"^!"! !^"""^K^^
^^M^]^R^Z"^L^M!^N"""^M!^N^]^\ESC""^L ^N^O^]^H^P"""^^^^"^^!ESC!^R ^]!!#^^\ ^O
In addition, you might want to consider adding a @ PG line for FADE in the SAM header - this will make it easier for other software packages (like ours) to understand the properties of data with which we are interacting.