[User story proposal] Xarray for Electrophysiology
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Estancado
- Stack tecnológico
- markdown
- Área
- documentation
Línea de trabajo
Start by reading existing posts in src/posts and follow the blog's Markdown and front-matter conventions. Draft a short electrophysiology user story using the proposed outline, then confirm that the post includes any useful images, code blocks, links, and references before it is ready for publication.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
This is a proposal for a electrophysiology use case story for Xarray. The story will be published on Xarray's blog (https://xarray.dev/blog).
Why?
Xarray has seen a bit of use in electrophysiology (see @gweindel's recent tweet or this older post from @choldgraf). A user story blog post showing how Xarray can be used to represent and analyze electrophysiology data would help socialize the concept across the Xarray developer and electrophysiology communities.
What?
We are targeting a short and non-technical post that illustrates how Xarray is (or could be) used in your electrophysiology 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-electrophysiology or whatever makes sense for your application.
xref: #272
- Lenguaje dominante
- JavaScript
- Estrellas
- 14
- Forks
- 30
- Merge medio
- 6 h 47 min
- PR fusionados (30 d)
- 1
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de xarray-contrib/xarray.dev
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
xarray-contrib/xarray.dev#796 · 1 comentario ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 35/100
xarray-contrib/xarray.dev#790 · 1 comentario · 1 reacción ·
-
numbagg blogpost Abierto
Dificultad 2/5 Medio día Aptitud para principiantes 45/100
xarray-contrib/xarray.dev#776 · 1 comentario ·
-
Website down Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
xarray-contrib/xarray.dev#757 · 21 comentarios ·
-
blogpost on xrlint Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
xarray-contrib/xarray.dev#756 ·
Todos los issues de xarray-contrib/xarray.dev
Issues similares
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Improve Title Support Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
georgestephanis/p2026#40 ·
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Margaret-Petersen/food-delivery-app-clone-react-native#1981 ·