Return variable features directly if you have set them yourself #213
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This has a corresponding fix in seurat-private: PR. s/o @longmanz for identifying and helping fix this issue.
The issue occurred when we tried to pull out
VariableFeatures
from an object in which we first ranFindVariableFeatures()
, and then set our ownVariableFeatures
after. If we tried to pull out the re-set variable features, it pulled out the features previously calculated withFindVariableFeatures
beforeThe issue was that we have a check that we skip to the calculated variable features if nfeatures != Inf or the # of variable features. The solution is to almost always return the variable features directly if you have set them yourself.
Documented more here: https://github.com/orgs/satijalab/projects/1/views/1?pane=issue&itemId=51523433