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
As long as nPhase doesn't make efficient use of heuristics to drastically speed up prediction time, users will run into issues with trying to run it on large genomes and could benefit from a guide to help reduce the time it takes to obtain results and how to interpret them.
The text was updated successfully, but these errors were encountered:
Those are some really large files, I imagine you have very high coverage?
Unfortunately this will require you to make some manual modifications to reduce the computational burden.
My recommendations would be to do the following:
Reduce the coverage of your input files to 10X/haplotype (60X total)
Run nPhase one chromosome at a time (you can do so by using a different reference fasta for each chromosome, there are other possibly better ways though)
You can save time by using nphase partial and reusing the same VCF file each time (which will have been run on the entire genome)
You can also save time by reusing the same long read SAM file if you have one with the reads fully mapped to the genome. nPhase will only look at positions in the VCF file.
If you'd like, you can email me at [email protected] and we can set up a call to talk about your use case for nPhase. It's possible that nPhase isn't going to give you the data that you're looking for. For example, it shouldn't be capable of giving you a chromosome-scale phasing. But there are things it can do well, like phase individual genes and regions in a ploidy agnostic way. It depends what information you're trying to get.
As long as nPhase doesn't make efficient use of heuristics to drastically speed up prediction time, users will run into issues with trying to run it on large genomes and could benefit from a guide to help reduce the time it takes to obtain results and how to interpret them.
The text was updated successfully, but these errors were encountered: