Yan Gao
Yan Gao
Hi, the HPC-kmer mode does not give us much improvement in our data, so it is not never carefully evaluated. Can you share the data that lead to the fault?
Hi, sorry for the late reply. Just fixed a bug that is due to very short input sequence. It should work now!
Can you upload your sample data here?
Hi, Can you share the sequence? Yan
I think the latest commit will just work. Try this: ``` git clone --recursive https://github.com/yangao07/TideHunter.git cd TideHunter; make ./bin/TideHunter ```
TideHunter was designed to detect tandem repeats from sequencing long reads, instead of assemblies. For your case, the total length of chr22 is too long for TideHunter to deal with....
The number of input sequences should have no limitation. Which version of TideHunter are you using? Did you use the latest v1.5.1? A bug in v1.5.0 was fixed recently. Yan
Thanks for your comments and questions. * For the issues related to the `subPos` column, I updated the README file and added examples to illustrate how the coordinates are defined....
Not sure if I understand your question correctly. You could align one consensus to another consensus sequence, see if they have enough matched bases. Since each consensus sequence may start...
Check out the `-u/--unit-seq` option in the latest release: [v1.4.0](https://github.com/yangao07/TideHunter/releases/latest). It will give you all the unit sequences of each tandem repeat.