You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I can not answer about the filter function, I think that filtering is usually done using %in%. Have you try the following command? It works nicely. But Mike will provide you a better answer.
There is a unresolved design problem of tmixFilterResultList class.
here shows that flowCore::filter method invokes %in% method before trying to coerce the result to filterResult
When K is of length 1, %in% method returns a tmixFilterResult, which corresponds to multipleFilterResultand thus compatible with filterResult.
However, when K has length >1, %in% method returns a tmixFilterResultList, which is simply a list of tmixFilterResult and there is no equivalent class existing in flowCore. Thus the coerce method defined here is problematic.
The workaround will be looping through different K value and calling flowClust inside of the loop. e.g.
I find that the flowCore glue fails where flowClust succeeds.
The following, using your example data, demonstrates the issue
All done with librarys from github
with
The text was updated successfully, but these errors were encountered: