Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue a "filtered input" warning if input looks like it's not the raw file #99

Closed
sjfleming opened this issue May 3, 2021 · 1 comment
Closed

Issue a "filtered input" warning if input looks like it's not the raw file #99

sjfleming opened this issue May 3, 2021 · 1 comment
Assignees
@sjfleming
Labels
enhancement New feature or improvement
Milestone
v0.3.0

Comments

@sjfleming
Copy link
Member

Use some heuristic (number of droplets? UMI count of smallest droplet? something about the UMI curve?) to issue a warning to the user if the input file looks like it may have been filtered.

Also include this "filtered" file information as a possible source of the

AssertionError: There are no empty droplets with UMI counts over the lower cutoff of 4800.  Some empty droplets are necessary for the analysis.Reduce the --low-count-threshold parameter.

error, which has popped up for a few users.
@sjfleming sjfleming added the enhancement New feature or improvement label May 3, 2021
@sjfleming sjfleming added this to the v0.2.1 milestone May 3, 2021
@sjfleming sjfleming self-assigned this May 3, 2021
@sjfleming sjfleming mentioned this issue May 3, 2021
Closed
@sjfleming sjfleming mentioned this issue Mar 28, 2023
Closed
@sjfleming sjfleming mentioned this issue Aug 6, 2023
Merged
@sjfleming
Copy link
Member Author

Closed by #238

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sjfleming sjfleming

Labels
enhancement New feature or improvement
Projects
None yet
Milestone
v0.3.0
Development

No branches or pull requests
1 participant
@sjfleming