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
Many thanks for the development of Opencyto. Incredible work ! I am here listing some comments for possible improvements in flowWorkspace package, mainly in the plotGate function. My main idea is to be able to drive graphs and output table only by playing with a csv gating template (and not create adhoc plots for each case.
When I plot my gates using the plotGate function, I get an error message on the graph, generated by xyplot from flowViz (which use hexbin package, which I think is giving the error). The error only occur when there is a single point to be plotted (resulting of the gating). When there is more than 1 unique point or when there is no point at all (empty gate with 0% of the data), all is fine. The error you can find on the graph is either:
(This occurs with default binning (xbins =32), which value is not documented but can be found as "xbin=32") in plotGate signature. hexbin is the culprit in this, but I think this can be worked out from plotGate or xyplot from flowViz).
Or I get the following error when xbins=0
These error does not stop the process, and except the writing on the figure, everything looks great. But the fact that it is written "Error" in big is not something scientits would like to see in production. An empty graph would be better. (I did not find any solution by only modifying the flowWorkspace package, so we should go deeper)
There are two possibilities for ranges (xlim and ylim) of the graphs : "Instrument" or "Data". However, a better representation for the non scatter channels would be in the logicle space, which is by default about in the range of [-1 ; -4] (or a little bit larger, like [-1.2 ; -4.2] for the non scatter channels). I modified the plotGate function by doing something like:
to help plotting without binning (which can take a large time on some machine, especially within Rstudio), there is the 'sample.ratio' parameter. However, an improvement would be to make this sample ratio only if the number of event is bigger then a threshold (say, 10000). I added the following parameters 'sample.minsize' in plotGate function
Thanks, these are good suggestions. We haven't been supporting flowViz much lately since we have moved visualization over to the ggcyto package, but we will work on getting these improvements in.
Hello,
Many thanks for the development of Opencyto. Incredible work ! I am here listing some comments for possible improvements in flowWorkspace package, mainly in the plotGate function. My main idea is to be able to drive graphs and output table only by playing with a csv gating template (and not create adhoc plots for each case.
(This occurs with default binning (xbins =32), which value is not documented but can be found as "xbin=32") in plotGate signature. hexbin is the culprit in this, but I think this can be worked out from plotGate or xyplot from flowViz).
Or I get the following error when xbins=0
These error does not stop the process, and except the writing on the figure, everything looks great. But the fact that it is written "Error" in big is not something scientits would like to see in production. An empty graph would be better. (I did not find any solution by only modifying the flowWorkspace package, so we should go deeper)
#try to customize the x, y limits if requested if(!is.numeric(xlim)) { xlim <- match.arg(xlim, c("instrument", "data","autologicle")) if(xlim == "data") { xlim <- .getRange(parentData, xParam) } if(xlim == "autologicle") { cols = parentData@origColnames if(xParam %in% cols[grepl("FSC|SSC|Time",cols)]) { xlim <- .getRange(parentData, xParam) } else { xlim=c(-1.2,4.2) } }
if(!is.null(sample.minsize)) { if( sample.minsize>nrow(parentFrame)) { sample.ratio=1 } }
This is all for now. Small improvements, but I think they can help the process of making the implementation of openCyto in a production environment.
Many thanks again.
The text was updated successfully, but these errors were encountered: