-
Notifications
You must be signed in to change notification settings - Fork 60
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
Error in sprintf("Error: there are %d sample ids in common ") : too few arguments #27
Comments
HI Develynw I am stuck with the same issue. Did you get any solution for your issue, if yes can you please let me know |
Do the sample ids in the metadata match the row names in the count matrix? Best, |
Hello, I have also had the same problem and was wondering if there had been an solution? My SampleIDs in the metadata and rownames in the count table are identical. Thanks |
Hello, Which package does the "feast" function originate from? |
Hello! I am facing the same problem. Is there any solution for it? |
Dear Celia, This error means that the out table (denoted ‘C = out_test’ in the FEST function) and your metadata (‘metadata_test’) don’t have shared sample ids. Please check your files and re-run. I hope this helps. Best, |
For anyone else facing this issue, I discovered that the documentation on the Github page doesn't match the R FEAST function; notably, the R help docs state: "The rownames of both C and the metadata table are the unique sample ids," while the Github documentation shows the sample ids as the column names for the counts table and implies that the sample ids should be a separate column in the metadata table. Once I changed the counts table and metadata so that the rownames in both were the sample ids, it functioned correctly. |
I have been using FEAST on a microbiome analysis, but recently have come across the following error despite previously successful runs:
I went through my code and input files, but don't see anything outstanding (screenshots below). I am stumped.
Does anyone have insight on what could be causing this error?
The text was updated successfully, but these errors were encountered: