Replies: 3 comments 3 replies
|
Try using |
0 replies
|
I would like to add that I do not have this same error with IGL data processed in the same manner with v4.6.0. I have tried to go back and export the clones with the feature you suggest and the following error: |
2 replies
|
This fixed the output such that the |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
When I use a custom IG library and run the following command using v4.7.0, I get erroneous 'region_not_covered' outputs for the majority of sequences in the 'nMutationsVRegion' when I have exported only functional clones:
mixcr analyze generic-amplicon -t 20 \ --floating-left-alignment-boundary \ --floating-right-alignment-boundary C \ --rna \ --species Bos_taurus \ --library Bostaurus-IGH.json.gz \ --assemble-clonotypes-by VDJRegion \ /home/tpursell/BulkIgFastqs/B18-FLU247-Leader-IGH_S7_L001_R1_001.fastq.gz \ /home/tpursell/BulkIgFastqs/B18-FLU247-Leader-IGH_S7_L001_R2_001.fastq.gz \ /home/tpursell/BulkIgFastqs/mixcr.outs.bota.20260107/bota.B18.FLU247.FSleaderAttached is the alignment report for one of the samples; it shows that 93% of sequences cover the VDJregion so I should not have the error exporting the mutations for the VRegion.
bota.B18.FLU247.FSleaderq.align.report.txt
All reactions