Error with "matching_columns" #41
-
Having a problem with the following error, no matter how I format my metadata Starting the ggpicrust2 analysis... |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hello @KidneyNode, Based on the error message you provided, it seems that there is an issue with subsetting columns in the metadata tibble. The error specifically states that you cannot subset columns using the "matching_columns" argument, which should not contain any missing values. To resolve this issue, please ensure the following:
For example, if the column name for sample names in the metadata is "SampleName", ensure that the abundance data also has a column with the same name ("SampleName") for sample names.
By addressing these points, you should be able to resolve the error related to subsetting columns in the metadata tibble. If you have any further questions or encounter any additional issues, feel free to ask for assistance. |
Beta Was this translation helpful? Give feedback.
-
Hi @cafferychen777, thanks so much for your response. My metadata looks like this: My abundance data is loaded from "R input/KO_pred_metagenome_unstrat.tsv", straight from the picrust2 output from python. I'm unsure what the "matching_columns" argument is, is is the sample_name column? There is no missing values in the dataframe/tibble |
Beta Was this translation helpful? Give feedback.
OK, looks like I sorted it out by reading through your code for the pathway_daa function. The issue was that the metadata and abundance tibbles were of different lengths. Somehow my picrust2 output contained samples that I thought I had previously removed. By removing the extra samples from the abundance tibble, it then matched with the metadata, and the issue was resolved.