Skip to content

Commit 7399178

Browse files
committed
TSC Meeting notes June 23rd.
Signed-off-by: Jeff Lait <jlait@andorra.sidefx.com>
1 parent ffc71c3 commit 7399178

File tree

1 file changed

+75
-0
lines changed

1 file changed

+75
-0
lines changed

tsc/meetings/2023-06-27.md

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
Minutes from 168th OpenVDB TSC meeting, June 23rd, 2023
2+
3+
Attendees: *Ken* M., *Jeff* L., *Andre* P, *Dan* B., *Greg* H.
4+
5+
Regrets:
6+
Attendees: *Nick* A., *Rich* J.
7+
8+
Additional Attendees: JT Nelson, Karl Marrett
9+
10+
Agenda:
11+
12+
1) Confirm quorum
13+
2) Secretary
14+
3) PR 1626
15+
4) OpenVDB Course
16+
5) Releases
17+
6) Multiresolution
18+
7) Next meeting
19+
20+
------------
21+
22+
1) Confirm quorum
23+
24+
Quorum is present.
25+
26+
2) Secretary
27+
28+
Secretary is Jeff Lait.
29+
30+
3) PR 1626
31+
32+
Legit and will approve. This is a new prime number choice for the
33+
hash.
34+
35+
4) OpenVDB Course
36+
37+
Plan is to submit lecture notes after course. But last week got an email
38+
suggesting we haven't submitted any thing. Will refer back to that
39+
conversation.
40+
41+
We could shorten Ken's intro too. This depends on number of people. Fifteen
42+
minutes per person.
43+
44+
Dan wishes to discuss Explicit Template instantiation.
45+
46+
We probably need an introduction that covers internal nodes.
47+
48+
How to split it up for developers vs users?
49+
50+
Jeff B and Greg Hurst are user facing (Houdini and Mathematica). Others are
51+
more low-level developer. Greg Karr for topology edits on GPU.
52+
53+
Do we have a present, future, and users?
54+
55+
Andre will add to the examples directory the smoke solver & flip solver.
56+
Where should the examples live? In the openvdb/openvdb/examples? Or off the
57+
base level? The latter allows AX to be integrated, but we may not want AX for
58+
a lean example.
59+
60+
5) Releases
61+
62+
We need a 10.1 before we branch to 11, aiming around September. There
63+
is a big NanoVDB dump incoming.
64+
65+
6) Multiresolution
66+
67+
Technical document and repo is availble for discussing. We should read and
68+
then ask questions about it. NanoVTT to be a grid-based multi-res system.
69+
Unlike VDB, this has a meaning: Voxel Tile Trees.
70+
71+
Is VTT an intrinsically different structure, or a variation of VDB?
72+
73+
6) Next meeting
74+
75+
Next meeting is on July 11th, 2023. 2pm-3pm EDT.

0 commit comments

Comments
 (0)