forked from vispy/vispy
-
Notifications
You must be signed in to change notification settings - Fork 0
Vispy code camp @ESRF
Almar Klein edited this page Jan 23, 2014
·
29 revisions
- Dates: 19 February (morning) - 21 February (evening) 2014
- Location: ESRF, Grenoble, France. CTRM Meeting room.
- Participants:
- Core developers (AK, CR, NR, LC)
- ESRF staff
- Potential users
Presentation of the developers (field, interest to scientific graphics, previous work in graphics, interest in vispy). (5 min each)
- AK
- LC
- CR
- NR
- What is Vispy? (AK, 10 min)
- Why?
- What users are we targeting? (scientists, engineers, game developers...)
- Possibilities and use cases? (scientific plotting, computer art/demo scene, data visualization, games...)
- Rough overview of the different layers (which ones have been done, which ones remain to be done?)
- Introduction to modern OpenGL (NR or AK?, 20 min)
- shaders, GLSL, VBOs, PyOpenGL, importance of batch calls
- GLOO. (NR or AK?, 10 min)
- Visuals. (CR, 10 min)
- Transforms, shader chaining, scenegraphs, Qt GraphicsView. (LC, 20 min)
- High-level interfaces. (CR, 10 min)
Lighting talks (a few minutes each).
- gl-agg, antialiasing. (NR, 5-10 min)
- MPL backend. (NR, 5-10 min)
- WebGL backend. (CR, 10 min)
- Visualization of HDF5 files. (CR, 5 min)
- GUIs, traits, MVC & visuals... (CR, 5 min)
- ...
Any participant can come and expose its use case in 5-10 min.
- Visualization and manipulation of electrophysiological recordings. (CR, 5 min)
- ESRF staff?
- ...
- Design, discussions, coding.
- Design, discussions, coding.
We set a few goals that we hope to achieve during this code camp. We distinguish between implementation, design, and discussion.
- visuals (design & implementation)
- scene layer (design & implementation) When this layer is established, it becomes much easier for other people to use vispy.
- webgl interface (discussing & design, maybe implementation)
- out-of-core plotting (discussion & design, maybe implementation)