Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Question about UMI information in the output files vdjca and clns #1468

Closed
silvia1234567890 opened this issue Dec 4, 2023 · 1 comment
Closed

Comments

@silvia1234567890
Copy link

silvia1234567890 commented Dec 4, 2023

Hello,

for the alignment, I ran this code:

mixcr align --preset generic-amplicon \
> --library Scophthalmus_maximus-IGH.json \
> --species Scophthalmus_maximus \
> --rna \
> --rigid-left-alignment-boundary \
> --rigid-right-alignment-boundary C \
> -OsaveOriginalReads=true \
> seqs.fasta \
> alignments.vdjca

for the clonotype:
mixcr assemble alignments.vdjca clones.clns

and to export:

mixcr exportAlignments alignments.vdjca alignments.tsv
mixcr exportClones clones.clns clones.tsv

In my clonotype table there is no "UMI count" column, and when I want to check the barcode coverage statistics with:
mixcr exportQc tags clones.clns tags.pdf
it gives me this message in the terminal:
No tag refinement report for clones.clns; did you run refineTagsAndSort command?

My question is: is there any parameter i forgot to put in the mixcr align code to get this information?

Thank you in advance!

@mizraelson
Copy link
Member

Hi,

The commands you used do not include UMI parsing and processing, which is why that information is not appearing in the output. Could you please share the library structure and the protocol used for your data so I can assist you with the appropriate set of commands.

Sincerely,
Mark

@milaboratory milaboratory locked and limited conversation to collaborators Dec 4, 2023
@mizraelson mizraelson converted this issue into discussion #1470 Dec 4, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants