Replies: 1 comment
-
The development version has a slightly different file format, which is why some functions will only work if the data was initially analyzed with the same version. We try to maintain backward compatibility, but in some cases, it is not possible. When you analyze the data starting from FASTQ files with the same MiXCR version, do you still see this error? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I used mixcr exportClonesOverlap on .clns files that have been processed with mixcr findAlleles, and I got this following error:
mixcr exportClonesOverlap --criteria "CDR3|AA|V|J" -isotype /home/jumana/Miami_aging/mixcr_miami_output2/allele/*.allelic.clns overlapTable.tsv
The catch is that when I ran exportClonesOverlap on .clns files that have been generated from mixcr analyze it works fine and I get a LARGE .tsv file back. I was wondering what the reason is this is happening. Is it a matter of compatibility? I'm aware that new reference libraries are generated and clonotypes are re-aligned after findAlleles, but I was thinking that it would still work?
Beta Was this translation helpful? Give feedback.
All reactions