Skip to content
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

Deletions at start of CIGAR sequences #4204

Closed
huzuner opened this issue Jan 8, 2024 · 8 comments · Fixed by #4223
Closed

Deletions at start of CIGAR sequences #4204

huzuner opened this issue Jan 8, 2024 · 8 comments · Fixed by #4223

Comments

@huzuner
Copy link

huzuner commented Jan 8, 2024

Hello,

Thank you for your contribution to the field with your tool.

I have been using vg giraffe and I came across some aligned reads with CIGAR strings that start with deletions, leading a downstream process crash. So I was wondering if this behavior has an intended purpose and how it should be perceived in terms of using soft/hard clips?

@jeizenga
Copy link
Contributor

jeizenga commented Jan 8, 2024

I think that's unexpected behavior. Could you be more specific about the commands and data that you used?

@huzuner
Copy link
Author

huzuner commented Jan 9, 2024

I used a prebuilt index provided here: https://github.com/human-pangenomics/hpp_pangenome_resources/blob/d5fb63e3e824f11b202caafe8768a67db3e99910/hprc-v1.0-mc.md and used the following command:

vg giraffe -x hprc-v1.0-mc-grch38.xg -f reads_1.fq -f reads_2.fq --output-format BAM > alignment.bam

@huzuner
Copy link
Author

huzuner commented Jan 15, 2024

Any other information that is required on this issue?

@jeizenga
Copy link
Contributor

Are you able to share the reads that you used as well? If you know which read had the issue from error logging output, that would also be helpful to know.

@huzuner
Copy link
Author

huzuner commented Feb 5, 2024

Sorry for the delay in my reply, I was on vacation.

Here is the corresponding read alignment together with the pair:

SRR233141.2837738       83      GRCh38.chr14    69324672        48      25D76M  =       69324551        -222    CATCTGTGCCCTCCCCCGCGGACCTGCCAGCCCCCAGCGTCATCATCCCCTTCCACAATGAGGCCCGTTCCACCCT    ###############################A*EEDBE?DE>B@@:@3BC<EFEBEEEEEBFFFEFDCCBD<CBBB        AS:i:26
SRR233141.2837738       163     GRCh38.chr14    69324551        48      76M     =       69324672        222     GCGGGGCCTCTGGCCTGGCTGTTGGTGTGCCTTCTCTGCCTGGCAGAAGTATTCTCAGGCACAAGACTGGACAAAG    EGDEHG=GGGFG=DEGGDFGC@CBB@C3B@@CC<BE?DEE:BE>D<4><4DCDCD;4?C@FFBFE>9@D@@=CBC=        AS:i:86

Please let me know if you require more information.

@jeizenga
Copy link
Contributor

jeizenga commented Feb 9, 2024

If you rebuild off the master branch, this problem should now be resolved. Thanks for bringing it to our attention!

@huzuner
Copy link
Author

huzuner commented Feb 11, 2024

Happy to help, thanks for taking care of the issue!
Are you thinking of doing a new release soon? So that the tool is updated in Bioconda.

@jeizenga
Copy link
Contributor

We make releases on a regular schedule. The next one is scheduled for Feb. 26.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants