You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I don't know if this makes sense for the output format, but I was wondering if CoLoRd could output a plaintext format? I am so used to manually inspecting files as a sort of sanity check that having a bespoke binary format might get in the way of our workflow. Or also if the compressed binary file makes its way to another computer without CoLoRd, it is possible that there will be no way to inspect the file.
I understand that it might not be possible with however it's structured and also that it will not be as compressed just like sam vs bam.
So anyway, is there a way to see what's under the hood? A way to pass around plaintext?
The text was updated successfully, but these errors were encountered:
Not sure if I understand your needs, but unfortunately, CoLoRd archives are pure binary files in our internal format. This is different than BAM which contains text header followed by gzip-decompressable blocks. It could be possible to add some modes for checking archive integrity, but this would require CoLoRd to be installed.
Hi, I don't know if this makes sense for the output format, but I was wondering if CoLoRd could output a plaintext format? I am so used to manually inspecting files as a sort of sanity check that having a bespoke binary format might get in the way of our workflow. Or also if the compressed binary file makes its way to another computer without CoLoRd, it is possible that there will be no way to inspect the file.
I understand that it might not be possible with however it's structured and also that it will not be as compressed just like
sam
vsbam
.So anyway, is there a way to see what's under the hood? A way to pass around plaintext?
The text was updated successfully, but these errors were encountered: