You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used abstar 0.6.4 for identifying humanized mouse antibody sequences. I have encountered assignment errors in the CDR1 and CDR2 regions. The sequences were identified as productive, however, the CDR1 and CDR2 regions were wrongly assigned and contains stop condons. I have listed some sequences below for your reference:
Sequence-1 has the same clonotype as Sequence-2, however, when using the humouse database as the reference, Sequence-1 is correctly assigned while Sequence-2 and Sequence-3 have mistakes in CDR1 and CDR2 assignment. When I switched to human as the reference database, both Sequence-1 and Sequence-3 were correctly assigned while Sequence-2 still contain the same error. When I use the IgBlast to test Sequence-2 with the human reference, the sequence was correctly assigned.
I hope these information would be helpful for identifying the cause if the issue. Thank you!
The text was updated successfully, but these errors were encountered:
Hello,
I used abstar 0.6.4 for identifying humanized mouse antibody sequences. I have encountered assignment errors in the CDR1 and CDR2 regions. The sequences were identified as productive, however, the CDR1 and CDR2 regions were wrongly assigned and contains stop condons. I have listed some sequences below for your reference:
Sequence-1 has the same clonotype as Sequence-2, however, when using the humouse database as the reference, Sequence-1 is correctly assigned while Sequence-2 and Sequence-3 have mistakes in CDR1 and CDR2 assignment. When I switched to human as the reference database, both Sequence-1 and Sequence-3 were correctly assigned while Sequence-2 still contain the same error. When I use the IgBlast to test Sequence-2 with the human reference, the sequence was correctly assigned.
I hope these information would be helpful for identifying the cause if the issue. Thank you!
The text was updated successfully, but these errors were encountered: