-
Notifications
You must be signed in to change notification settings - Fork 45
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
UX Bug: beta
allows RelativeFrequency, Type errors on RF with unsupported metrics
#296
Comments
The bray curtis implementation doesn't currently support |
Good eye, @jkibilds! Thanks for bringing this to our attention. As @thermokarst mentioned, Bray-Curtis does not currently support relative frequency tables, but other metrics do. In order to allow So... I think it's good that I think this should be moved over to |
beta
allows RelativeFrequency, Type errors on RF with unsupported metrics
@ChrisKeefe - Constraining the types via |
In QIIME2-2020.8.0, the description of
qiime diversity beta
function says it acceptsFeatureTable[Frequency | RelativeFrequency | PresenceAbsence]
artefacts as input. In reality, if aFeatureTable[RelativeFrequency]
artefact is passed as input, an error is generated.The command I used:
The error I got:
I noticed that in previous version (QIIME2-2020.6), the description of
qiime diversity beta
function only listedFeatureTable[Frequency]
as an input option. Apparently, the description has been updated, but not the function itself.The text was updated successfully, but these errors were encountered: