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
Thank you so much for your work on this fantastic package, it helped accelerated my work so much! The installation and test data ran smoothly and I just have an additional question based on my analysis--
I am more familiar with MaAsLin2 package and use it all the time with my microbiome taxa differential analyses. For some datasets, I have tailored the model to "CPLM" and adjusted transformation as "NONE" in maaslin, as well as put confounding factors such as age, sex, bmi as fix effects to control. In this case I'd prefer to use the same model setting to test the difference of my predicted pathways. I'm wondering is there an option in the ggpicrust2 package to achieve this?
Thank you so much.
SL
The text was updated successfully, but these errors were encountered:
Thank you for your interest in ggpicrust2 and for your question about MaAsLin2 parameters. Looking at the current implementation in the perform_maaslin2_analysis function (lines 509-566), I can help explain the current options and suggest how to add more flexibility:
Currently, the function uses these default MaAsLin2 parameters:
Hello,
Thank you so much for your work on this fantastic package, it helped accelerated my work so much! The installation and test data ran smoothly and I just have an additional question based on my analysis--
I am more familiar with MaAsLin2 package and use it all the time with my microbiome taxa differential analyses. For some datasets, I have tailored the model to "CPLM" and adjusted transformation as "NONE" in maaslin, as well as put confounding factors such as age, sex, bmi as fix effects to control. In this case I'd prefer to use the same model setting to test the difference of my predicted pathways. I'm wondering is there an option in the ggpicrust2 package to achieve this?
Thank you so much.
SL
The text was updated successfully, but these errors were encountered: