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
I checked the docs just to make sure that this is not expected behavior and it also suggests that the expected behavior is for the values to be relative to the (dataset) queried:
n_measured_obs — the “measured” cells for this gene, effectively the number of cells for which this gene was measured in their respective dataset.
We are tracking this, and it looks related to #1284. But I think your interpretation is correct, just checking in with the schema owners on internal channels to make sure.
@khughitt, apologies, but I completely misread this issue when I first responded.
What you are seeing is actually the expected behavior. The summary statistics you are seeing in .var are calculated across the whole census object, and are statically stored. That means for any query within an Measurement you will get the same values for var.
It sounds like what you are expecting is for these values to be calculated dynamically for each query. You will need to recalculate the values on your side for this.
Describe the bug
The
nnz
andn_measured_obs
fields report the same (global?) values foradata.var.nnz
andadata.var.n_measured_obs
regardless of the dataset queried.Tested for different dataset ids, but presumably this applies to all queries and not just those pulling a single dataset.
To Reproduce
Expected behavior
Query/dataset-specific values should be returned.
Environment
Arch Linux (64-bit)
Additional context
I checked the docs just to make sure that this is not expected behavior and it also suggests that the expected behavior is for the values to be relative to the (dataset) queried:
source: https://chanzuckerberg.github.io/cellxgene-census/articles/2023/20231012-normalized_layer_precalc_stats.html
--
Thanks for all of your work on this!
It's appreciated.
The text was updated successfully, but these errors were encountered: