3D transparency proposal
Los mantenedores suelen responder en 2 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- javascript
- Área
- data-visualization
Línea de trabajo
This is a design proposal for screen-space blue-noise transparency in plotly.js's 3D surfaces, and the payload names no files, tests or entry points. Start by reading the linked issues (#1267, #3243, #4918) to see what has already been tried. Done would mean a maintainer-agreed design and a prototype, so a first-time contributor should discuss the approach in the thread before writing code.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
3D transparency has always been tricky, and has never worked very well in plotly.js. - see eg https://github.com/plotly/plotly.js/issues/1267 https://github.com/plotly/plotly.js/issues/3243 https://github.com/plotly/plotly.js/issues/4918 for just a few examples. Several years ago I played with an approach that seemed promising - treating opacity as a semi-random probability of drawing or not drawing a pixel, then oversampling / averaging to smooth the result. I never got it working well enough to include in the library, but in another project (not using plotly.js) a colleague of mine has refined the concept into what I think is a really beautiful, performant, and useful result so I'm sharing here in case someone wants to bring it into plotly.js
- Each transparent surface gets a repeatable, screen-space random blue noise function that yields values between 0 and 1. This means if you pass through multiple layers of the same surface we will not make it as opaque as it really should be (because they all use the same screen-space function), but because of the next point, the result still looks physically reasonable, and arguably more useful than the full opacity of a complete physical model. If you don't use screen space for the noise function (use full 3D space for example) then there's a distracting amount of motion to the noise as you move the viewport.
- The transparency at each pixel becomes T^(1/cos(theta)) where T is the given transparency and theta is the angle at that pixel between the surface normal and the camera. This makes shallow-incidence areas more opaque, modeling a physical system where you're passing through a greater thickness of the material depending on this angle.
- Only pixels where the final opacity is greater than the blue noise function (and where we haven't already drawn a surface closer to the camera) are drawn. All the same lighting effects used for opaque surfaces can still be used.
- During mouse interactions this is what we display, so it looks grainy but you still see the features and on average they are correct. This is one area I still think the algorithm we're using could be improved, it often looks kind of like those old "Magic Eye" books whereas I think with some experimentation we could get it a bit flatter, but it's entirely usable in this form.
- Once the mouse stops moving we average many frames (in the video below we use 64 frames) of this with different random seeds on the blue noise functions, to smooth away the graininess. In the averaging process it's important to distinguish between sRGB and linear color.
https://github.com/user-attachments/assets/29266885-2745-4077-a7db-33d24d96daee
- Lenguaje dominante
- JavaScript
- Estrellas
- 18.4k
- Forks
- 2.1k
- Merge medio
- 1 d 5 h
- PR fusionados (30 d)
- 12
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
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 plotly/plotly.js
-
[BUG]: `sankey`: `node.x` / `node.y` of `0` is ignoredPosiblemente ocupada @adimalkar la tomó hace 2 días. Abiertobug P3 size: 1
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
plotly/plotly.js#8150 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
[BUG]: `scatterpolargl` drops points between 10000 and 100000 pointsPosiblemente ocupada @Tanishdete333 la tomó hace 2 días. Abiertobug P3 size: 1
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
plotly/plotly.js#8148 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
[BUG]: findEmpties throws "iterated with no new neighbors" for large NaN regions in contour (double-precision underflow)Posiblemente ocupada @davrens101 la tomó hace 1 día. Abiertobug P3 size: 3
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
plotly/plotly.js#8108 · 4 comentarios ·
Los mantenedores suelen responder en 2 días
-
chore P3 plotly-internal size: 3 task
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
plotly/plotly.js#8064 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
chore P1 plotly-internal size: 1 task
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
Los mantenedores suelen responder en 2 días
Todos los issues de plotly/plotly.js
Issues similares
-
bug confirmed js v6
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
BUG
Dificultad 1/5 1-3 horas Aptitud para principiantes 90/100
linuxmint/cinnamon-spices-applets#9223 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
nopSolutions/nopCommerce#8440 ·
Los mantenedores suelen responder en 1 día
-
follow-up
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día