[User story proposal] Xarray for Bioimaging
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- markdown
- Domain
- content, documentation
Research direction
Review existing Markdown posts in src/posts and the related issue #272 before choosing a bioimaging use case. Draft a short post following the proposed outline, adding images, code blocks, links, or references only where they support the story. Done means the user story is formatted for publication on Xarray's blog.
Written by the indexing model from the issue text.
Description
This is a proposal for a bioimaging use case story for Xarray. The story will be published on Xarray's blog (https://xarray.dev/blog).
Why?
Xarray is used in a number of bioimaing applications today (e.g. Allen SDK) and is a candidate data model / toolkit in a number of others (e.g. biohub, napari, etc.). A user story blog post showing how Xarray can be used to represent and analyze bioimaging data would help socialize the concept across the Xarray developer and bioimaging communities.
What?
We are targeting a short and non-technical post that illustrates how Xarray is (or could be) used in your bioimaging context. Below is a template outline that you should feel free to modify:
- Who am I?
- What problem am I trying to solve?
- How does Xarray help?
- Why did I choose Xarray?
- Current pain points (or ways that Xarray could better serve your use case)
- Technology I use around Xarray
- Anything else to know?
- Links and references
Feel free to insert images or short code blocks if they help you tell your story.
How?
Xarray's blog using Markdown with some front-matter. You can copy one of the existing posts to get started or you can write in a google-doc-like-thing and ask us to do the markdown formatting. If you copy a previous post, use a name like user-story-brain-imaging or whatever makes sense for your application.
xref: https://github.com/xarray-contrib/xarray.dev/issues/272
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 30
- Avg merge
- 6h 47m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from xarray-contrib/xarray.dev
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
xarray-contrib/xarray.dev#796 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
xarray-contrib/xarray.dev#790 · 1 comment · 1 reaction ·
-
numbagg blogpost Open
Difficulty 2/5 Half a day Newbie friendliness 45/100
xarray-contrib/xarray.dev#776 · 1 comment ·
-
Website down Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
xarray-contrib/xarray.dev#757 · 21 comments ·
-
blogpost on xrlint Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
xarray-contrib/xarray.dev#756 ·
All issues in xarray-contrib/xarray.dev
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100