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

Warning using algorithm 2 #6

Closed
jbruxaux opened this issue Aug 10, 2023 · 4 comments
Closed

Warning using algorithm 2 #6

jbruxaux opened this issue Aug 10, 2023 · 4 comments

Comments

@jbruxaux
Copy link

Hi!

I am currently using PCAone on a fairly big dataset (195 samples, 4,2 million SNPs), and I get this warning:
WARNING: PCAone converged but the window size did not expand the whole data.
What would you recommend? Using a different algorithm?
I am using the last version of PCAone (v0.3.4) on a linux cluster.

Thanks for your help!

@Zilong-Li
Copy link
Owner

Zilong-Li commented Aug 10, 2023

Hi!

Thanks for trying out PCAone.

Mathmatically, without the warning, we would get A ≈ USV where U matrix is the PCs in pcaone.eigvecs file, S in pcaone.eigvals and V matrix is in the SNP loadings file pcaone.loadings. This warning literately means that PCAone converged in few epochs before the algorithm expands to the whole data, which suggests only U is correct while S and V are not meaningful as what it stands for in the math.

If you care about S and V matrix other than the U , you can force PCAone algorithm2 to run exact 7 epochs where it starts expanding to the whole data A assuming --batches=64 in default

PCAone --bfile plink -m 2 -n 20 -k 10  --svd 2 --tol-rsvd 0 --maxp 7

In fact, you data is quite small :)

Best,
Zilong

@jbruxaux
Copy link
Author

Hi Zilong,

I just re-ran the analysis as you suggested, and it worked without any issue.
Thanks for your help!

@Zilong-Li
Copy link
Owner

Sorry for the confusion. I'll update PCAone in the next release to make algorithm2 running at least 7 epochs although it converges in less epochs.

@Zilong-Li
Copy link
Owner

this is fixed in the latest release v0.3.5

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

2 participants