[User story proposal] Xarray for Plasma Physics
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Documentación
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- markdown
- Área
- content, documentation
Línea de trabajo
Start by reviewing the existing posts in src/posts and the linked Xarray user-story issues, then use the proposed outline to shape a short plasma-physics story. Create a Markdown post with front matter for the blog, including the use case, how Xarray helps, surrounding technology, pain points, and relevant links.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
This is a proposal for a plasma physics 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 plasma physics applications today (e.g. OMFIT, xBOUT). A user story blog post showing how Xarray can be used to represent and analyze the types of data frequently used in plasma physics. It would also help socialize the use of Xarray for this use case across the Xarray developer and plasma physics communities.
What?
We are targeting a short and non-technical post that illustrates how Xarray is (or could be) used in your plasma physics 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-plasma-physics or whatever makes sense for your application.
xref: https://github.com/xarray-contrib/xarray.dev/issues/272, #201
- 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
-
code-quality refactoring
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100