Closed alisterburt closed 1 year ago
Merging #29 (81a556e) into main (554b1fe) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## main #29 +/- ##
=======================================
Coverage 67.24% 67.24%
=======================================
Files 26 26
Lines 922 922
=======================================
Hits 620 620
Misses 302 302
Impacted Files | Coverage Δ | |
---|---|---|
src/microvis/core/nodes/node.py | 70.32% <0.00%> (ø) |
|
src/microvis/backend/vispy/_canvas.py | 62.85% <0.00%> (ø) |
|
src/microvis/core/_base.py | ||
src/microvis/core/_vis_model.py | 93.90% <0.00%> (ø) |
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
Thanks for taking a look and the positivity! comments were useful for my own thinking, have hopefully cleared things up a bit... merging! will start thinking about slicing
I've put together some thoughts on a potential nD data model in which the
navigable world
is explicitly separated from therendered world
orscene
which must be 2D or 3D. If your data is higher dimensionality than the scene then you start adding 'navigable world dimensions' which can be navigated with sliders. There's also an explicit mechanism for both dynamic projections on the CPU and for handling potentially RGB(A) dataPlease let me know what you think and definitely ask any clarifying questions - this is a bit of a departure, I purposefuly haven't thought specifically about how the 'slicing' should be done but I like being able to think about the data model separately from that :)