Open jwdebelius opened 3 years ago
In the comment on this issue, collapse
is mentioned, and there is a discussion of that under #104. Let's focus this issue on the filter-table
action, which should accept other FeatureTable
types as input. PresenceAbsence
is one that I need right now, and is an easy one (because all values remain independent). RelativeFrequency
(and I think Composition
) are harder, because the values in the table would need to be recomputed after features are removed.
To achieve this, we'll need to allow FeatureTable[PresenceAbsence]
as an input, and add a TypeMap
such that the output FeatureTable
subtype matches the input FeatureTable
subtype.
@hagenjp Just did something like this for q2-taxa so she is going to take a stab at this issue!
Seems like we had two github issues for this on our release board.
relative frequency
compositional
tablesrelative frequency
aligned seqs
FeatureTable[PresenceAbsence]
as an input to filter, and add a TypeMatch
such that the output FeatureTable
subtype matches the input FeatureTable
subtype
Current Behavior Currently, q2-taxa only allows you to operate on a Frequency feature table semantic type, and you can only perform taxonomic filtering on Sequences.
Proposed Behavior I'd like to be able to collapse relative frequency and compositional tables. (I think it would be harder to manage with presence/absence), filter relative frequency and presence/absent tables, and filter aligned sequences.