-
Notifications
You must be signed in to change notification settings - Fork 1
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
Pool Estimation - Zero variance metabolites #75
Comments
Hi, As you probably noticed i am just going trough some issues to close them up and write you were I do not remember the progress. |
No this was not done, but I did write the zero variance check as a function which could be used whereever its needed. I paste it here:
|
Ok, thanks :) To sum this up, you planned to add this check to the pool estimation function prior to calcuclating CV?
1 and 2 would basically result in messages/warnings and refer to cases (=metabolites) where we can not calculate CV either because we have zero variance or because we have not-normal distribution. Where there other cases where you would have added the zero variance function? I recon we probably should do this prior to the shapiro test as this would also be impacted by zero variance (?). |
yes, 1-2-3 are correct and I would add the check prior to when we use the variance or sd like CV tests and also PCAs. |
Thanks, then I will do the above :) About PCA: Do we need to check for normailty also prior to PCA? Cause within PCA, we recommend scaling=TRUE. |
PCA simply does not work if you input features with zero variance, you have to remove them prior using it. About normality no need to check before PCA, it shouldnt play a role. |
MetaProViz: fetch error if a metabolite column only has 0s! @ Error: Error in prcomp.default(as.matrix(InputData), scale. = as.logical(Scaling)) : cannot rescale a constant/zero column to unit variance |
Need to add the zero variance check in Pool estimation because it could cause error in the PCA in certain scenarios
The text was updated successfully, but these errors were encountered: