combineBCR - chain argument is not accepted by function

[colin-leeyc]

In combineBCR(), specifying chain = "both"/"IGH" etc. (or any other parameter) results in Error in combineBCR(..., : unused argument (chain = "both")

Error was present in v2.2 and updated v2.6.

Thank you

[ncborcherding]

Hey @colin-leeyc,

This is not a bug-the chain argument was added in v2.5.0. It should be noted, there has been recent changes in the underlying clustering coming out as well - more info at #557 - including fixes on handling light chains.

Nick

[colin-leeyc]

Hi Nick, Thanks for the quick response. We suspected that was the case and installed the latest version (v2.6) but had the same issue.. Any suggestions? Thank you! Colin

…

On 7 Dec 2025 at 16:55 +0000, theHumanBorch ***@***.***>, wrote: ncborcherding left a comment (BorchLab/scRepertoire#565) Hey @colin-leeyc, This is not a bug-the chain argument was added in v2.5.0. It should be noted, there has been recent changes in the underlying clustering coming out as well - more info at #557 - including fixes on handling light chains. Nick — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ncborcherding]

That likely points to something like not restarting your R session after updating - the chain argument is present in 2.6 which makes me think the update was not properly loaded on your R environment.

Nick

[colin-leeyc]

Hi Nick, Thank you. I will check! I’d be absolutely mortified if it’s as simple as that and have wasted your time! Colin

…

On 7 Dec 2025 at 17:02 +0000, theHumanBorch ***@***.***>, wrote: ncborcherding left a comment (BorchLab/scRepertoire#565) That likely points to something like not restarting your R session after updating - the chain argument is present in 2.6 which makes me think the update was not properly loaded on your R environment. Nick — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>