-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simulating reads and misalignments #17
Comments
hi Pesho
thanks for reporting it though! Rayan |
Thank you, Rayan!
Raw data: Generated reads and outputs: Terminal: |
Hi Pesho, please make sure your reference genome is not a multi-line FASTA ( |
Thank you, Rayan! This solves the issue. I got mislead by the supplementary of your paper according to which you run all tools on the same reference file while in reality you seem to modify it. |
yes indeed, sorry about that. I view mapquik as a F1 racecar: very quick prototype but would need many quality of life improvements for real use. |
Thank you for the work you put on reproducibility.
Nevertheless, I am puzzled while trying to:
reproduce your results -- I am stuck with an issue with pbsim+paftools paftools.js pbsim2fq outputs NaN coordinates lh3/minimap2#1121), I am wondering whether you had issues with NaN's in .maf by paftools (as I described in the minimap2 issue) and whether you considered using a newer version of pbsim (v2 or v3).
evaluate mapquik on a simulated HiFi dataset using the Eskemap pipeline --
mapquik
produces unexpectedly many misalignments. I simply ranmapquik
with default parameters on the chm13 Y-chromosome, following the evaluation pipeline ofEskemap
, and produced only 1306 alignments for 6938 reads. Do you think the produced reads are somehow fundamentally different to those by pbsim and should I change the parameters formapquik
for this reason? Here is a distilled version ofEskemap
's pipeline:The text was updated successfully, but these errors were encountered: