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
FlowJo allows users to add gates on both the compensated and uncompensated values of any channel (as well as the transformed and untransformed values). The current design of cytolib and flowWorkspace is to have a single column for each channel to which compensation and transformation are applied (although that column can be inverted or decompensated on-the-fly if need be). The fact that we do not hold on to the uncompensated channel values causes parsing failures for any workspace that has gates on the uncompensated values of a channel that has been compensated.
I am putting this issue in CytoML, but depending on how we tackle it, the work may end up being more in cytolib and flowWorkspace. This may be another reason to consider switching to storing values on raw scale and then applying compensation or transformation when necessary.
I've attached a very simple workspace to demonstrate the issue and use for testing purposes. uncompensated_issue.tar.gz
The text was updated successfully, but these errors were encountered:
This is fixed by cdb3b5e, but required some additions to cytolib (RGLab/cytolib@b7dd39e). I'm leaving this open for a bit to allow for updates in the near term.
FlowJo allows users to add gates on both the compensated and uncompensated values of any channel (as well as the transformed and untransformed values). The current design of
cytolib
andflowWorkspace
is to have a single column for each channel to which compensation and transformation are applied (although that column can be inverted or decompensated on-the-fly if need be). The fact that we do not hold on to the uncompensated channel values causes parsing failures for any workspace that has gates on the uncompensated values of a channel that has been compensated.I am putting this issue in
CytoML
, but depending on how we tackle it, the work may end up being more incytolib
andflowWorkspace
. This may be another reason to consider switching to storing values on raw scale and then applying compensation or transformation when necessary.I've attached a very simple workspace to demonstrate the issue and use for testing purposes.
uncompensated_issue.tar.gz
The text was updated successfully, but these errors were encountered: