-
Notifications
You must be signed in to change notification settings - Fork 3
/
notes.txt
55 lines (40 loc) · 1.52 KB
/
notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
Types are all over the place:
- Subdivision 'index' is uint[], AMR volume 'block.level' uses int[].
- Mesh 'index' needs to be either vec3ui[] or vec4ui[]
- Unstructured volume 'index' needs to be either uint32[] or uint64[],
and its 'cell.type' uint8[]
- Texture2D needs a 2D Data array (i.e. with z=1) but whose values
are vec3f/vec4f/etc.
Python tuple is always converted to a vec<n>f or vec<n>i, as we can't
detect unsigned values, nor the width of the integer/float value.
Using a numpy array gives full control over the data type of the
values.
Could special case a numpy array of 1 to convert to a single value,
but that screws up cases where you really need an array holding a single
value.
Types used in the API:
- bool: value
- int: value and array
- float: value and array
- double: <not used>
- uint: array
- uint8: array
- uint16: <not used>
- uint32: value and array
- uint64: array
- vec2i: value (ospNewFrameBuffer), array (edgeCrease.index)
- vec2ui: <not used>
- vec2f: value and array
- vec3i: value (dimensions)
- vec3ui: array
- vec3f: value and array
- vec4i: <not used>
- vec4ui: array
- vec4f: value and array
https://github.com/pybind/pybind11/issues/1201
--------------------------------------------------------------
- Setting backgroundColor to a float results in alpha=0?
- Some weird behaviour with backgroundColor and volume rendering.
Using backgroundColor 1,1,1,0 and then compositing the resulting
image on a white background gives a greyscale result?
Using 0,0,0,0 as background also seems weird.