Expand dask support

[flying-sheep]

What kind of feature would you like to request?

Additional function parameters / changed functionality / changed defaults?

Please describe your wishes

Meta issue tracking scanpy functions without dask support

Related #921

First we should test things more generically:

• add global array_type fixture to use in all tests for features below
  • Make helpers work with dask #2595

@ivirshup came up with places where we should prioritize dask support:

• normalize_total
  • seems to work: Fix normalize_total for dask #2466
  • has tests: Allow dask arrays to propagate through _normalize_data() #1663
• log1p, normalize_per_cell, filter_cells/*_genes:
  • accept Dask arrays: Support running on distributed compute engines like Dask, and Spark via Zap #283
  • Test that they are kept as Dask arrays throughout: Test full Dask support for log1p, normalize_per_cell, filter_cells/filter_genes #2814
• sc.pp.pca: Dask PCA support #2563
• sc.pp.calculate_qc_metrics
• sc.pp.highly_variable_genes:
  • Dask support for pp.highly_variable_genes (default "seurat" flavor) #2777
  • Dask support for pp.highly_variable_genes ("cellranger" flavor) #2807
  • Dask support for pp.highly_variable_genes ("seurat_v3" flavor(s)) #2808
  • experimental “pearson_residuals” flavor
• sc.tl.rank_genes_groups: Handle Dask arrays in some utilities #2621
• Subsample
• Aggregate

Later:

• scale
• nearest-neighbors
• umap
• metrics

[mumichae]

For the highly_variable_genes dask support, are you also considering cases where the dask chunks are scipy sparse matrices?

[flying-sheep]

Not currently, but since the scope of that PR got reduced, it shouldn’t be too much work.