Closed liu930724 closed 1 week ago
Seems the abundances for the true alleles and the wrong alleles are not very high, so there could be some tricky issues. As before, could you please share the candidate reads, and I can look into it. Thank you!
Meanwhile, the current github v1.0.7-r225 also fixes an issue in the t1k-build regarding the exonization in an HLA-C allele. Could you please recreate the T1K's reference using t1k-build from the hla.dat file, and it may fix this issue.
After recreating the T1K reference, the result for HLA-C with 2M reads is correct now. It's possible that this is the issue, we will test with more samples in the future. Thank you!
Is the abundance estimation comparable between C01:02 and C05:01 in the new run? If they still differ a lot, I think there are still some hidden issues.
The abundances of C01:02 and C05:01 are different but consistent with the trend of different reads amounts. And the abundance of C05:01 is much higher than C08:02.
We amplified the full length of HLA genes, which may be the reason for the large difference in abundance of different alleles. With this in mind, this difference in abundance is acceptable. Thank you.
Hi, while analyzing another HLA reference sample(HLA-C*05:01:01), we observed tha the HLA-C typing results were incorrect at 2M reads (HLA-C*08:02:01). But when we switch to other data sizes of 1-3M, even if we only change it to 2.1M, all of the results are correct.
T1K v1.1.7-r225 was used and different numbers of reads were obtained through the --reads_to_process parameter of fastp.
running command:
log of 2M reads:
It seems different from the last issue about HLA-C typing error, so I open a new issue. Thank you in advance for your time and help.