Adjust doublet score calculation according to sequencing technology

[saracastel]

Description

Details

URL to issue

This PR addresses an issue where the existing method for calculating doublet scores tends to overestimate doublets in Parse datasets. This overestimation could lead to the unintended exclusion of high-quality cells. The root of this problem lies in the difference in expected doublet rates between Parse and 10x datasets, with Parse data generally having a lower rate.
To rectify this, the PR proposes an adjustment to the doublet score calculation specifically for Parse data. It involves modifying the dbr parameter in the scDblFinder function to align with the empirical doublet rates observed in a mixed species experiment conducted using Parse technology.

Note: the code has been prepared to modify the dbr value based on the specific Parse kit used. However, we have decided to maintain the value associated with the WT kit as the default for now. The reason for this decision is that implementing the UI component to input information about the Parse kit is not a priority at this moment.

Link to staging deployment URL (or set N/A)

N/A

Links to any PRs or resources related to this PR

Integration test branch

master

Merge checklist

Your changes will be ready for merging after all of the steps below have been completed.

Code updates

Have best practices and ongoing refactors being observed in this PR

• Migrated any selector / reducer used to the new format.

Manual/unit testing

• Tested changes using InfraMock locally or no tests required for change, e.g. Kubernetes chart updates.
• Validated that current unit tests for code work as expected and are sufficient for code coverage or no unit tests required for change, e.g. documentation update.
• Unit tests written or no unit tests required for change, e.g. documentation update.

Integration testing

You must check the box below to run integration tests on the latest commit on your PR branch.
Integration tests have to pass before the PR can be merged. Without checking the box, your PR
will not pass the required status checks for merging.

• Started end-to-end tests on the latest commit.

Documentation updates

• Relevant Github READMEs updated or no GitHub README updates required.
• Relevant Wiki pages created/updated or no Wiki updates required.

Optional

• Staging environment is unstaged before merging.
• Photo of a cute animal attached to this PR.