Solyris83

Hi, I have the same "Segmentation fault (core dumped)" message processing the 400 million reads demo data from the Dovetail Omni-C webpage (https://omni-c.readthedocs.io/en/latest/data_sets.html). This dataset analysis has been successfully completed...

@haowenz I have tried both --SAM and without and it gave the same segmentation fault for this data. On a side note, I am assuming the default pair output are...

Segfault happens after mapping some reads, I do not see any logs, do you mean the stderr output? If so attached herein [errorr.txt](https://github.com/haowenz/chromap/files/7929851/errorr.txt) The segmentation fault error is not printed...

that is great to hear, my configuration is found below 1) AWS C5A.4XLARGE 2) Ubuntu Server 18.04 LTS

hi @haowenz , you mentioned that you managed to get the Omni-C 400 mil reads data mapped successfully on your machine, might I ask what is your machine OS and...

I would like to add on to this topic, in particular how the reported unique reads can be extracted fully. I have the run below `chromap --preset hic -t 32...

I see, thanks for the prompt reply. Is there absolutely no way to just output uniquely-mapped results then? I have tried a demo dataset from Omni-C (https://omni-c.readthedocs.io/en/latest/data_sets.html ) with both...

Hi Hannes, Thanks for the quick reply, the Graphtyper version used is VERSION 2.5.1. Reads captured with the below line can be found above, as said the actual bases are...

Hmmm, I sent it in the email, must have been cut off. Sorry about that, attached herein from Github page [example.zip](https://github.com/DecodeGenetics/graphtyper/files/5955333/example.zip)

Hi Hannes, Thanks for the comment above, I had a quick look at the CRAM file header and indeed it is as what you have said the header reference sequence's...