scverse / scverse/spatialdata

User documentation on different methods of benchmarking with SpatialData

Open
#763 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
394
Forks
95
Avg merge
4d 3h
Merged PRs (30d)
7

Description

Is your feature request related to a problem? Please describe.
A lot of documentation is focused on one dataset or method. Method developers need to benchmark multiple datasets or methods e.g.

Benchmarking functions

  • compare two segmentation models creating a Labels element
  • compare two methods outputting a SpatialData object

Benchmarking pipelines

  • working towards larger benchmarks
  • how to benchmark on large infrastructure, HPC
  • link to openproblems.bio

Describe the solution you'd like
A tutorial documentation with just text on benchmarking pointing to the right resources or documentation for each type of benchmarking method.

Describe alternatives you've considered
A lot of existing material exists, but there is no overview or examples specifically using SpatialData.

Additional context
Benchmarking or performance analysis for developers contributing to SpatialData is out-of-scope for this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No target file or test is named. Start by reviewing the existing benchmarking material and openproblems.bio, then create a SpatialData-focused tutorial covering function and pipeline benchmarking, including large-infrastructure and HPC guidance. Done means the overview points readers to the appropriate resources and examples.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.