-
Notifications
You must be signed in to change notification settings - Fork 17
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
Metadata state-column can't have a zero value or be non-numeric category #38
Comments
Thanks for reporting and the detailed issue @mestaki! This is a bug and CTF should run for two subject/state tensors. I have put in a specific issue and PR to fix this bug. |
Howdy, just wondering if there are any updates on this fix, or estimated timeline for a fix? I want to gauge if I should wait it out for a project I'm working on or try a different approach (fingers crossed for the former). |
Hi @mestaki Yes, there is a branch with a bug fix waiting for a PR review. You can install and use that branch by running Thanks for the reminder! |
Fantastic, thank you! |
Hey @cameronmartino,
Finally getting around to trying out this awesome tool, huge congrats on the paper btw.
I was trying a dataset with paired-data with just 2 timepoints when I ran into a problem with my metadata state-column.
I tried 2 different columns that could have represented my states:
timepoint <- has numeric values of
0
and6
which correspond to weeks, orEst_status <- categorical values of
Baseline
, and6mosEst
Both represent the same values one is numeric the other categorical. I'm on q2-2020.6, with q2-deicode: 0.2.4, and gemelli: 0.0.6 installed
When I run the below with either of those 2 columns:
I get the following error:
If I add a random 3rd value in either of these columns it runs successfully. So can gammeli not be used on data with only 2 timepoints then? It doesn't fit in the cross-sectional version either, so this would be a big loss since many projects do use only before/after designs.
The text was updated successfully, but these errors were encountered: