Stereoseq expected directory structure

Open Beginner friendly
#161 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Half a day
Newbie friendliness
65/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
documentation

Research direction

Start by locating the Python stereoseq reader and reviewing the directory structure it expects, then compare it with the results-folder example in the issue. Document the expected folder names and which files belong in each folder so users can manually reorganize their results to match the reader.

Written by the indexing model from the issue text.

Description

documentation

Hi Team,

Would it be possible to document the expected directory structure for the stereoseq reader? The results we got from the stereoseq team don't follow the directory structure being assumed by this implementation. So, if it's properly documented, like the folder names to expect and which files should be put in which folder, then we can manually restructure our directories to conform to this stereoseq reader implementation.

As an example, this is the results folder we receive from the Stereoseq team:
image

Thanks a bunch.

Dominant language
Python
Stars
103
Forks
65
Avg merge
1h 8m
Merged PRs (30d)
3

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.

More from scverse/spatialdata-io

All issues in scverse/spatialdata-io

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.