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
Thanks for your work on this package! I've run into the following issue: the read.gatingML.cytobank appears to fail when I attempt to read in an exported cytobank gatingML file with the following error message: (I'd be happy to share the gatingML file, but I'm not sure how to add attachments to github).
Error in addGate(gateInfo, flowEnv, g, thisPopId, gateID) :
multiple gates found for Gate_1590224_dmlhYmxl
This gate corresponds to a polygon gate drawn against FSC and Ax700.
On inspecting the gatingML file, there appears to be only one Gate_1590224_dmlhYmxl defined.
It appears that the issue is that one of the gating axis is compensated (Ax700) while the other one is not (FSC-A), which the function interprets at there being two versions of the gate drawn on different compensation matrices.
The text was updated successfully, but these errors were encountered:
Thanks for your work on this package! I've run into the following issue: the
read.gatingML.cytobank
appears to fail when I attempt to read in an exported cytobank gatingML file with the following error message: (I'd be happy to share the gatingML file, but I'm not sure how to add attachments to github).This gate corresponds to a polygon gate drawn against FSC and Ax700.
On inspecting the gatingML file, there appears to be only one
Gate_1590224_dmlhYmxl
defined.The
flowUtils::read.gatingML
function is able to read the gatingML file, and also only finds a single version of the gate in question:In my attempt to debug it, I believe the duplication is occurring within the
parse.gateInfo()
function: as can be seen here:It appears that the issue is that one of the gating axis is compensated (Ax700) while the other one is not (FSC-A), which the function interprets at there being two versions of the gate drawn on different compensation matrices.
The text was updated successfully, but these errors were encountered: