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
also Related: Single gene Visualization test (=SGV)
If we choose the top K by log fold change this might still be feasible but for significance, we should probably require the sig ana to have run the comparison?
In SGV we use t-test and should perhaps notify people that this pvalue is different to the pvalue from e.g. deseq
The text was updated successfully, but these errors were encountered:
fine for me to notify user to first run SigAna however we state that the modules work independent from each other & can be done in arbitrary order which would be then slightly violated. Still , would agree to require user to first run stat. analysis if one wants to have top k based on pvalue. To then not only have LFC as choice for Top k we could also have top varying (based on sd) as option
-SGV - agree should notify
If we have outsourced the sigana functions and other functions enough, we can also trigger a significance analysis from the heatmap server that does this, saves it in res_tmp$Sig_Ana and then uses it 🙈
Yes could have some additional choices here. Based on SD sounds good. Will for now only add a warning if the comparison has not been done yet.
also Related: Single gene Visualization test (=SGV)
If we choose the top K by log fold change this might still be feasible but for significance, we should probably require the sig ana to have run the comparison?
In SGV we use t-test and should perhaps notify people that this pvalue is different to the pvalue from e.g. deseq
The text was updated successfully, but these errors were encountered: