Functionality across sumrep is dependent on which locus the repertoire comes from, and this information is input differently across functions. We will standardize this so that, when locus is important, the function will have a locus argument which expects one of "tra", "trb", "trd", "trg", "igl", "igk", or "igh". This is already implemented in getPartisAnnotations and getIgBlastAnnotations, but compareRepertoires asks for a receptor_type and chain_type separately. I'll look for other cases to standardize as well.
I'll note that there is already a checkForValidLocus function which checks that the locus argument matches one of the above options.
Functionality across sumrep is dependent on which locus the repertoire comes from, and this information is input differently across functions. We will standardize this so that, when locus is important, the function will have a
locus
argument which expects one of "tra", "trb", "trd", "trg", "igl", "igk", or "igh". This is already implemented ingetPartisAnnotations
andgetIgBlastAnnotations
, butcompareRepertoires
asks for areceptor_type
andchain_type
separately. I'll look for other cases to standardize as well.I'll note that there is already a
checkForValidLocus
function which checks that thelocus
argument matches one of the above options.