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
In most of the SOMA API, column_names handling is consistent -- the returned result for a DataFrame read will include the union of:
columns requested via column_names
plus, any columns referenced in the value_filter string
This is true for DataFrame.read(), ExperimentAxisQuery.obs(), and ExperimentAxisQuery.var().
There is a bug in ExperimentAxisQuery.to_anndata(), which does not include the columns referenced in the value_filter. It should work the same as the other interfaces.
The bug is in ExperimentAxisQuery._read_axis_dataframe(), which is overly aggressive in throwing away columns.
johnkerl
changed the title
column_names handling inconsistent in ExperimentAxisQuery.to_anndata
[python] Handling of column_names is inconsistent in ExperimentAxisQuery.to_anndata
Jan 19, 2023
In most of the SOMA API,
column_names
handling is consistent -- the returned result for a DataFrame read will include the union of:column_names
value_filter
stringThis is true for
DataFrame.read()
,ExperimentAxisQuery.obs()
, andExperimentAxisQuery.var()
.There is a bug in
ExperimentAxisQuery.to_anndata()
, which does not include the columns referenced in the value_filter. It should work the same as the other interfaces.The bug is in
ExperimentAxisQuery._read_axis_dataframe()
, which is overly aggressive in throwing away columns.Example:
The text was updated successfully, but these errors were encountered: