Skip to content

A little suggestion of update to make ROGUE suitable for large dgCMatrix data#8

Open
mimi3421 wants to merge 2 commits intoPaulingLiu:masterfrom
mimi3421:patch-1
Open

A little suggestion of update to make ROGUE suitable for large dgCMatrix data#8
mimi3421 wants to merge 2 commits intoPaulingLiu:masterfrom
mimi3421:patch-1

Conversation

@mimi3421
Copy link
Copy Markdown

@mimi3421 mimi3421 commented Jun 3, 2022

Dear author,

I have used ROGUE in place of the default HVG algorithm for feature sellection in the fastMNN pipeline and found that it returned a more concise UMAP graph and a more reasonable result in functional analysis after clustering.

I make a little change to reduced the RAM footprint and summit here if someone need it.

As log(0+1)=0, I make a little change in the Entropy function so that only the non-zero log result will be updated when dgCMatrix is supplied as the input data matrix, which would greatly reduce the RAM consumption.

mimi3421 added 2 commits June 4, 2022 04:08
Make ROGUE suitable for large dgCMatrix data
Update the old ROGUE to new
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant