You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All PCAs used as examples have slight differences when running the computations using the latest API version (v8.8.0), e.g. two samples pull PCAs instead of 1, and different samples are acting as outliers. Although the overall dynamic of the PCAs is similar, individual samples are looking quite different, see examples below.
These PCAs were originally run with v4.2.0 & checked with v4.3.0.
As we cannot revert to those versions (due to python incompatibility in Colab) & it is quite confusing to follow along the video & the current explanations, I will pin the API version on this NB to v7.15.0, where these PCAs look the same.
We should take a deeper look at which v8.x.x change has caused this. We'll have to take into account the authentication updates, if we want to check the API, before W3.
region = "3L:15,000,000-41,000,000"
n_snps = 100_000
sample_sets=["AG1000G-BF-A", "AG1000G-BF-B", "AG1000G-BF-C"],
sample_query="taxon in ['gambiae', 'coluzzii'] and country == 'Burkina Faso'"
v8.8.0
v7.15.0
The text was updated successfully, but these errors were encountered:
@alimanfoo This patch is tested in bespin/collab, and all PCAs are in line with the videos. Will keep this issue open until we have a chance to take a deeper look.
All PCAs used as examples have slight differences when running the computations using the latest API version (v8.8.0), e.g. two samples pull PCAs instead of 1, and different samples are acting as outliers. Although the overall dynamic of the PCAs is similar, individual samples are looking quite different, see examples below.
These PCAs were originally run with v4.2.0 & checked with v4.3.0.
As we cannot revert to those versions (due to python incompatibility in Colab) & it is quite confusing to follow along the video & the current explanations, I will pin the API version on this NB to v7.15.0, where these PCAs look the same.
We should take a deeper look at which v8.x.x change has caused this. We'll have to take into account the authentication updates, if we want to check the API, before W3.
For reference, some examples below:
The text was updated successfully, but these errors were encountered: