-
Notifications
You must be signed in to change notification settings - Fork 55
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
Check random seed #47
Comments
Hi, I was about to open an issue related to this problem. I am repeating the # Estimate optimal number of clusters using SC3
sc <- sc3_estimate_k(object = sc)
# Check estimated optimal number of k
# Output is 10
(k.use <- metadata(sc)$sc3$k_estimation)
# Add feature_symbol column in rowData(sc)
rowData(sc)$feature_symbol <- rownames(counts(sc))
# Perform SC3 clustering
sc <- sc3(object = sc, ks = k.use, gene_filter = TRUE,
pct_dropout_min = 10, pct_dropout_max = 90, d_region_min = 0.04,
d_region_max = 0.07, svm_num_cells = NULL, svm_train_inds = NULL,
svm_max = 5000, n_cores = 4, kmeans_nstart = 1000,
kmeans_iter_max = 1e+09, k_estimator = FALSE, biology = TRUE,
rand_seed = 1) Any idea when this issue can be fixed? Best, |
Hi @leonfodoulian , thanks! This is a known bug, I started working on it but at the moment it is very slow since I moved jobs and doing it at free time. Sorry for the inconvenience. |
Still working, but now there is another person who is dramatically improving |
Hi, I am wondering if k estimates vary between runs. Could k estimates be affected by this issue? Thanks! |
Hi, no, k estimation algorithm is deterministic and should not change between runs. |
Hi, I am also having this problem that multiple runs of SC3 produce different results even when rand_seed is set to a fixed value. Is this still a known problem? I have just re-installed SC3 from Bioconductor (https://bioconductor.org/packages/release/bioc/html/SC3.html). Best wishes, |
Hey, yes, it's still a known problem, but, unfortunately, no one is working on it at the moment. |
Looks like the seed is changed somewhere in the code, so sometimes results cannot be reproduced...
The text was updated successfully, but these errors were encountered: