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.

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

"Error: psi values too close each other" with segmented 2.0-1 #14

Closed
benduc opened this issue Jan 10, 2024 · 5 comments
Closed

"Error: psi values too close each other" with segmented 2.0-1 #14

benduc opened this issue Jan 10, 2024 · 5 comments

Comments

@benduc
Copy link

benduc commented Jan 10, 2024

Hi,
Thanks for developing this great tool.
Since the package segmented was updated to 2.0-1, there are several samples that crash when running

valiDrops(seurat, rank_barcodes = FALSE)

due to the error "Error: psi values too close each other. Please change (decreases number of) starting values".

This is solved when reinstalling segmented 1.6.4.

@JesperGrud
Copy link
Contributor

Hi.

Thank you for your interest in using valiDrops. That sounds curious. We will try to reproduce with different versions of segmented and get back to you as soon as possible. However, it may be some time. In the mean time I would advise you to use 1.6.4

@yesitsjess
Copy link

I'm also having this issue but only for 1/5 of my datasets (so far). I will try installing an older version of segmented too

@ashipde
Copy link

ashipde commented Apr 14, 2024

I too encounter this issue, which seems to be solved by reducing npsi to 2 (default is 3). I haven't tried downgrading segmented to 1.6 from the current version, 2.0. I wish the documentation had more information on parameters like npsi and mito.max so one could understand the consequences of changing them from default values.

@ashipde
Copy link

ashipde commented Apr 25, 2024

This issue appears to be fixed in v1.1.0.

@JesperGrud
Copy link
Contributor

Closing as this error is also being evaluated in issue #17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants