Gregor Sturm
Gregor Sturm
I had in mind something like this ✅ = supported ❌ = not supported ⚡= supported in dask | Function | numpy.ndarray | csr_array | csr_matrix | csc_array | csc_matrix...
The table leads to horizontal scrolling for me Also not sure if the top of the API page is the best place to place it? Maybe even have a dedicated...
somewhat related: https://github.com/nf-core/differentialabundance/issues/471
Having separate functions for separate NN-flavors would also make it easier to use algorithms optimized towards a specific flavor. E.g. for radius based NN, much faster implementations exist than KDTree,...
Probably this is related? https://github.com/nf-core/differentialabundance/issues/514 It is intended that variable/reference/target/blocking are empty in presence of a formula and constrasts string. However the contrast should still end up in the report.
I'm happy to review a PR
Thanks! Yes, please update the nf-core module first.
@VladimirShitov, how is the speed if you do a `.copy()` on the subset, i.e. ```python sc.pl.dotplot( adata[adata.obs["louvain"].str.contains(["T cells"]).copy(), var_names=cd_4_t_cell_markers, groupby="louvain" ) ``` I think I also [noticed in the past](https://github.com/icbi-lab/atlas_protocol/blob/270b58dbb033c5e4bb91c814961d5a7463ccc114/src/atlas_protocol_scripts/tl/_pseudobulk.py#L39-L41)...
Depends on #361
But what if you have one formula contrast?