-
Notifications
You must be signed in to change notification settings - Fork 64
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
Query Regarding Paired Sample Analysis with trans_diff
Function
#379
Comments
Hi. Sorry for the unclear description in the help document.
As the function select the feature abundance table and sample table sequentially, so to do paired test, you just need to prepare sample infomation table to be well-organized like this.
Or
Please have a try and feel free to tell me if it is not solved. |
Hi! Thank you very much for your reply! I would like to further confirm which methods provided by the trans_diff function support differential testing for paired design samples? |
Hi. "ALDEx2_t" and "t.test". For t.test, the by_ID parameter should be provided. |
Hi @ChiLiubio , Just wanted to confirm that the Wilcoxon test also allows for paired testing using the Thanks, |
Hi @motroy Chi |
Dear Author,
I am currently using your R package for analyzing paired microbial sample data, where each pair consists of two samples from the same patient. I noticed that the
trans_diff
function provides thegroup_choose_paired
parameter, which supports the "metastat" or "metagenomeSeq" methods for selecting the required groups for paired testing. However, I could not find any examples or documentation in the help page or tutorial on what input should be provided for this parameter.Additionally, I would like to know if other methods, such as
ALDEx2_kw
,lefse
, andmaaslin2
, have parameters that support paired testing.Could you please provide some guidance or examples on how to properly use the
group_choose_paired
parameter and clarify if paired testing is supported for the other methods provided intrans_diff
function?Thank you very much for your assistance.
The text was updated successfully, but these errors were encountered: