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’d like to implement an auto-detection module to automatically identify the chemistry type for scRNA-seq libraries. This feature would help address scenarios where multiple library chemistries are mixed. By selecting "auto" for the chemistry parameter, the pipeline could perform internal detection to assign the appropriate chemistry type for downstream processing.
Since CellRanger already has an internal function for this, it could also benefit tools like Alevin, Kallisto, and STAR. I’ve developed an internal version based onv2.7.1. Would it be possible to push this as a new branch, or would it be preferable for me to make the updates on the current dev branch to support a future release?
Sincerely
Winnie Zheng
The text was updated successfully, but these errors were encountered:
if you push this into a branch and make a (draft) PR, I am happy to take a look.
In principle I am open to such a feature, but in the end I'll need to decide if the additional complexity is worth it. It's always a trade-off between adding new features and ensuring the pipeline is maintainable long-term.
Description of feature
Hi,
I’d like to implement an
auto-detection module
to automatically identify the chemistry type for scRNA-seq libraries. This feature would help address scenarios where multiple library chemistries are mixed. By selecting "auto" for the chemistry parameter, the pipeline could perform internal detection to assign the appropriate chemistry type for downstream processing.Since
CellRanger
already has an internal function for this, it could also benefit tools likeAlevin
,Kallisto
, andSTAR
. I’ve developed an internal version based onv2.7.1
. Would it be possible to push this as a new branch, or would it be preferable for me to make the updates on the currentdev
branch to support a future release?Sincerely
Winnie Zheng
The text was updated successfully, but these errors were encountered: