|
| 1 | +Minutes from 167th OpenVDB TSC meeting, April 18th, 2023 |
| 2 | + |
| 3 | +Attendees: *Jeff* L., *Dan* B., *Ken* M., *Dan* B., *Rich* J, |
| 4 | +*Andre* P. |
| 5 | + |
| 6 | +Additional Attendees: Sebastian Gaida |
| 7 | + |
| 8 | +Regrets: *Nick* A., *Greg* H. |
| 9 | + |
| 10 | +Agenda: |
| 11 | + |
| 12 | +1) Confirm quorum |
| 13 | +2) Secretary |
| 14 | +3) Forum |
| 15 | +4) PR-1606: Boost UUID |
| 16 | +5) VFX Reference Platform |
| 17 | +6) Boost::any PR |
| 18 | +7) Discussion on read-only data structure |
| 19 | +8) VDB 11 |
| 20 | +9) Next Meeting |
| 21 | + |
| 22 | +------------ |
| 23 | + |
| 24 | +1) Confirm quorum |
| 25 | + |
| 26 | +Quorum is present. |
| 27 | + |
| 28 | +2) Secretary |
| 29 | + |
| 30 | +Secretary is Andre Pradhana. |
| 31 | + |
| 32 | +3) Forum |
| 33 | + |
| 34 | +Nothing to discuss. |
| 35 | + |
| 36 | +4) PR-1606: Boost UUID |
| 37 | + |
| 38 | +It compiles. We agree to review the PR. |
| 39 | + |
| 40 | +5) VFX Reference Platform |
| 41 | + |
| 42 | +VFX Reference Platform asks for a release draft for 2024. We |
| 43 | +agree to release VDB 11.0 in November. Our plan will be communicated |
| 44 | +to VFX Reference Platform to confirm that we are moving to VDB 11 later |
| 45 | +in the year. |
| 46 | + |
| 47 | +6) Boost::any PR |
| 48 | + |
| 49 | +Once this PR is approved, OpenVDB will optionally depend on boost. It makes |
| 50 | +sense to have a lite-CI for OpenVDB that does not support delayed loading |
| 51 | +nor depends on blosc. |
| 52 | + |
| 53 | +7) Discussion on read-only data structure |
| 54 | + |
| 55 | +Ideas discussed are: |
| 56 | + - Having a read-only tree in OpenVDB, for example utilizing a ring |
| 57 | + buffer, which replaces pages instead of loading new pages. The |
| 58 | + argument against adding a ring-buffer based grid is that the OS |
| 59 | + can do it for us if we use delayed/partial loading. However, this |
| 60 | + approach makes the OS to do the swapping. This approach is similar |
| 61 | + to NanoVDB. The advantage of it is that a user can define the allocated |
| 62 | + memory footprint upfront. |
| 63 | + - A refinement of the idea above is to store the evicted data locally. |
| 64 | + - Another approach discussed is by reading/loading the data per- |
| 65 | + bouding-box. |
| 66 | + - Build a prefectching tools. |
| 67 | + |
| 68 | +Other points raised includes: |
| 69 | + - The need to trim down the core code-base, so that it is easier |
| 70 | + to add a new grid. Currently, there are a lot of virtual methods |
| 71 | + and expected functions that are required to build a new grid type. |
| 72 | + - In terms of workflow, Houdini uses viewport to control which |
| 73 | + data should be loaded in memory. |
| 74 | + - People read-only tree for rendering. |
| 75 | + - Talked about strategy to parallelize an algorithm that delay-load |
| 76 | + leaf nodes using mutex locks. |
| 77 | + |
| 78 | +8) VDB 11 |
| 79 | +What can go to VDB 11: |
| 80 | + - Updates to NanoVDB. |
| 81 | + - Offset to recenter root node. |
| 82 | + - Hollow VDB. |
| 83 | + - VDB Merge needs to work for packed primitives. |
| 84 | + - Example for fluids (due for SIGGRAPH). |
| 85 | + - VDB Fillet. |
| 86 | + |
| 87 | +9) Next Meeting |
| 88 | + |
| 89 | +Next meeting is on April 25th, 2023. 2pm-3pm EDT (GMT-4). |
0 commit comments