|
| 1 | +Minutes from 97th OpenVDB TSC meeting, June 29th, 2021, (EDT) |
| 2 | + |
| 3 | +Attendees: *Ken* M., *Jeff* L., *Dan* B., *Andre* P. |
| 4 | + |
| 5 | +Additional Attendees: JT Nelson (Blender), Bruce Cherniak (Intel), |
| 6 | +Sergio Rojas, Johannes Meng (Intel) |
| 7 | + |
| 8 | + |
| 9 | +Regrets: *Nick* A. |
| 10 | + |
| 11 | +Agenda: |
| 12 | + |
| 13 | +1) Confirm Quorum |
| 14 | +2) Secretary |
| 15 | +3) Google Forum |
| 16 | +4) NanoVDB |
| 17 | +5) 9.0 |
| 18 | +6) String Grids |
| 19 | +7) Example Hip File |
| 20 | +8) Next meeting |
| 21 | + |
| 22 | + |
| 23 | +1) Confirm Quorum |
| 24 | + |
| 25 | +Quorum is present. |
| 26 | + |
| 27 | +2) Secretary |
| 28 | + |
| 29 | +Secretary is Dan Bailey. |
| 30 | + |
| 31 | +3) Google Forum |
| 32 | + |
| 33 | +JT has pointed out that the Google Forum is now longer embedded in the |
| 34 | +openvdb.org website. Having discussed the options, it was decided that the best |
| 35 | +route is to enable GitHub discussions with a general and a Q&A section as a |
| 36 | +replacement for the Google Forum. The Google Forum will not be made read-only, |
| 37 | +as there is still a community there which can post and answer questions. |
| 38 | +However, there should be a pinned thread highlighting that the TSC members would |
| 39 | +be primarily monitoring and responding to questions asked using GitHub |
| 40 | +Discussions. It may also be worth posting replies to new topics in the Google |
| 41 | +Forum to encourage people to re-post using GitHub Discussions. There is no known |
| 42 | +mechanism to extract content from Google Forum and migrate it to GitHub |
| 43 | +Discussions. The forum tab of the website should also be updated to provide |
| 44 | +clearer guidelines of how to ask questions and to include a link to the old |
| 45 | +Google Forum for searching old content. |
| 46 | + |
| 47 | +4) NanoVDB |
| 48 | + |
| 49 | +A couple of big changes have been introduced - a move to 64-bit addressing and |
| 50 | +native compression. PNanoVDB is almost ready and has a key benefit that it |
| 51 | +supports many more graphics APIs than CNano such as OpenCL. |
| 52 | + |
| 53 | +Autodesk requested relative error bounds instead of absolute error bounds. There |
| 54 | +are certain cases where this is useful, so this is being worked on. |
| 55 | + |
| 56 | +Ken to present an overview of NanoVDB at the TSC meeting on Tuesday 13 July and |
| 57 | +answer any questions about the library and API. The intention is to submit only |
| 58 | +the core library for review initially and not the viewer. |
| 59 | + |
| 60 | +Ken also looking at point quantization currently. |
| 61 | + |
| 62 | +5) 9.0 |
| 63 | + |
| 64 | +The VFX Reference Platform has decided on a final deadline of 1st September as |
| 65 | +cut-off for inclusion in the VFX Reference Platform 2022. Intention is to |
| 66 | +release OpenVDB 9.0 around Siggraph time in order to meet that deadline. There |
| 67 | +is discussion ongoing in the TAC meetings about changes that have been made in |
| 68 | +how software gets included. Unlikely that NanoVDB would be reviewed and |
| 69 | +integrated in time, so may target 9.1. |
| 70 | + |
| 71 | +Dan to reach out to VFX Reference Platform and ask for clarification. |
| 72 | + |
| 73 | +6) String Grids |
| 74 | + |
| 75 | +Ken ok with deleting string grids, believe it was mainly included in the first |
| 76 | +place as an example of a non-trivial value type, not a realistic production |
| 77 | +type. |
| 78 | + |
| 79 | +7) Example Hip File |
| 80 | + |
| 81 | +Everyone agreed that putting the binary hip file in the openvdb_website Git repo |
| 82 | +is acceptable. It's not really best practice of how to use Git, but given that |
| 83 | +it changes infrequently and GitHub has restrictions on enabling Git LFS for |
| 84 | +hosted websites, there's no suitable alternative. |
| 85 | + |
| 86 | +8) Next meeting |
| 87 | + |
| 88 | +Next meeting is July 13th, 2021. 12pm-1pm EST (GMT-5). |
0 commit comments