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
The logic stored in booleanFilters (deparse slot) refers to nodes that exist within the GatingHierarchy/GatingSet. When we extract a booleanFilter from a GatingHierarchy/GatingSet we do not get a filter that can be applied to the data because the reference to the gates in the logic is lost (booleanFilters only store names of the gates and not coordinates).
Would it be possible to automatically parse the booleanFilter logic when extracting it from the GatingHierarchy/GatingSet to produce a valid filter? See example below:
It would be great if gh_pop_get_gate/gs_pop_get_gate could extract the required gates by extracting the nodes from bool@deparse and then apply the required operators !|& to produce a valid filter that can be applied to the data.
The text was updated successfully, but these errors were encountered:
Hi @mikejiang,
The logic stored in booleanFilters (
deparse
slot) refers to nodes that exist within the GatingHierarchy/GatingSet. When we extract a booleanFilter from a GatingHierarchy/GatingSet we do not get a filter that can be applied to the data because the reference to the gates in the logic is lost (booleanFilters only store names of the gates and not coordinates).Would it be possible to automatically parse the booleanFilter logic when extracting it from the GatingHierarchy/GatingSet to produce a valid filter? See example below:
It would be great if
gh_pop_get_gate
/gs_pop_get_gate
could extract the required gates by extracting the nodes frombool@deparse
and then apply the required operators!|&
to produce a valid filter that can be applied to the data.The text was updated successfully, but these errors were encountered: