|
| 1 | +Minutes from OpenVDB TSC meeting, April 30th, 2024 |
| 2 | + |
| 3 | +Attendees: *Ken* M., *Dan* B., *Greg* H., *Rich* J., *Andre* P |
| 4 | + |
| 5 | +Additional Attendees: |
| 6 | +Matthew Cong (NVIDIA), Alexandre Sirois-Vigneux (SideFX), |
| 7 | +Efty Sifakis (Univ. Wisconsin), Francis Williams (NVIDIA), |
| 8 | +Jonathan Schwartz (NVIDIA), Michiel Hagedoorn |
| 9 | +Dhruv Govil (Apple), Tom (Sidefx), Rayhaan Tanweer, |
| 10 | +Rabih, Youmna, Shahan N |
| 11 | + |
| 12 | +Regrets: *Jeff* L., *Nick* A. |
| 13 | + |
| 14 | +Agenda: |
| 15 | + |
| 16 | +1) Confirm quorum |
| 17 | +2) Secretary |
| 18 | +3) Migration from PyBind11 to NanoBind |
| 19 | +4) Greg's ASWF membership |
| 20 | +5) FVDB |
| 21 | +6) Next meeting |
| 22 | + |
| 23 | +------------ |
| 24 | + |
| 25 | +1) Confirm quorum |
| 26 | + |
| 27 | +Quorum is present. |
| 28 | + |
| 29 | +2) Secretary |
| 30 | + |
| 31 | +Secretary is Andre Pradhana. |
| 32 | + |
| 33 | +3) Migration from PyBind11 to NanoBind |
| 34 | + |
| 35 | +Matthew Cong presented a solution to handle NanoBind dependency |
| 36 | +by using pip. He has done work on the NanoBind-side to allow this workflow. |
| 37 | +The solution with Git-subtree/submodule is brittle because it |
| 38 | +can run into firewall issues. |
| 39 | + |
| 40 | +It was re-iterated that NanoBind is preferred because of zero-interop |
| 41 | +on the GPU side. |
| 42 | + |
| 43 | +Dhruv Govil pointed out that PyBind is used by other projects |
| 44 | +for its support for multiple inheritance (which NanoBind doesn’t |
| 45 | +support). |
| 46 | + |
| 47 | +4) Greg's ASWF membership |
| 48 | + |
| 49 | +Greg will follow up with John Mertic to be added to ASWF organization. |
| 50 | + |
| 51 | +5) FVDB |
| 52 | + |
| 53 | +NVIDIA team presented a presentation on fVDB, a project that is for |
| 54 | +consideration to be adopted by OpenVDB project. It is a framework to |
| 55 | +do spatial reasoning on 3D volumetric dataset, which includes deep- |
| 56 | +learning. |
| 57 | + |
| 58 | +The main dependencies is pytorch. The project will live in its own |
| 59 | +directory, parallel to the `openvdb` directory. |
| 60 | + |
| 61 | +Ken will bring up the need for GPU-support in the CI in the TAC meeting. |
| 62 | +TSC members will be added to the private fVDB repository for further |
| 63 | +investigation. Jonathan Schwartz provided us with documentation. |
| 64 | + |
| 65 | +6) Next meeting |
| 66 | + |
| 67 | +Next meeting is on May 7th, 2024. 2pm-3pm EDT (GMT-4) |
0 commit comments