-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Store Row Names in exprs slot of cytoframe #354
Comments
check out the latest BTW, if you are on mac or windows, cytoinstaller will help you install the more up-to-date binary packages than bioc devel. |
Fantastic! Thanks so much @mikejiang! This will make my life a lot easier. I will update the CytoExploreR docs to use One last thing, do you think it would be possible to make |
|
Thanks @mikejiang. Perhaps, rather than attaching this at the level of Out of curiosity, is there a shortcut to install all packages with Thanks again for your help! |
Thanks @mikejiang, happy to close this now and I will implement this on my end. |
@mikejiang, this works well, but since I still have to go through a
Current workaround involves coercion to
|
Hi cytoverse team,
I was wondering if it would be possible to store information in the
rownames
of theexprs
slot of acytoframe
. I am working on refining the plotting behavior withincyto_plot()
and I would like to ensure that the same events are plotted when populations are overlaid. In order to do this I will need to reference each row based on its position within theroot
node (i.e. assign an index to each row withinexprs(cf)
ideally inrownames(exprs(cf))
). I need to store this information at thecytoframe/cytoset
level. I can easily write a wrapper for this usinggh/gs_pop_get_data()
andgh_pop_get_indices()
to assign the indices to each row in eachcytoframe
but this does not get updated:This is because there is currently no replacement method for
rownames
in flowCore. Is this deliberate or would it be possible to add support for this?Thanks for your help!
Dillon
The text was updated successfully, but these errors were encountered: