<div dir="ltr"><div>=== This Week ===</div><div>After including the openvdb library in Blender, I added 3 classes for interfacing with the library. OpenVDB API calls will be restricted to these classes.</div><div>So this is where we currently stand:</div>
<div><span class="" style="white-space:pre">        </span>- Added the OpenVDBVolume struct to hold an open file handle for .vdb files and header info (metadata) on the grids contained in the file;</div><div><span class="" style="white-space:pre">        </span>- Added the OpenVDBUtil class for basic operations, such as checking for valid vdb file, all vdb-related I/O operations, and others will be added as needed;</div>
<div><span class="" style="white-space:pre">        </span>- Finally, the OpenVDBVolumeAccessor was created to hold one vdb grid, and perform lookups. The idea here is that grids can't really be shared (although internal trees can, where one grid = one tree + metadata collection), so an OpenVDBVolume will contain as many accessors as there are grids in its file.</div>
<div><span class="" style="white-space:pre">        </span>- Added an executable target containing a version of the openvdb utility vdb_print to cycles/app, to be used for testing out the created classes and methods, and printing performance stats.</div>
<div><br></div><div>Additionally, since I'm in Anaheim for Siggraph already, I got a new Mac laptop. Since I was working on Windows, I've been doing some configuration fixes: one example is I had added the tbb library (openvdb's dependency) under a if(MSVC), and it took me sometime to figure it out why the symbol wasn't being loaded.</div>
<div><br></div><div>Right now, I'm fighting a linker error on XCode - it seems the library isn`t being linked, but the lib path and library names are configured. Anyway, I'll post this separately so as not to clutter the report.</div>
<div><br></div><div>As Ton requested on the list, I'll commit less changes, more often, and I'm pretty sure I'll make tons of code style mistakes, but I'll just go ahead for some time and then come back and fix them, since the technical challenge of the project itself, for me, is already very significant.</div>
<div><br></div><div>=== Next Week ===</div><div>Since midterm evaluations are coming, and I started considerably late because of college, I'll focus on doing enough to demonstrate where we're headed, and what lies ahead.</div>
<div><span class="" style="white-space:pre">        </span></div><div>To be done this week: </div><div><span class="" style="white-space:pre">        </span>- finish the minimum requirements for the interface classes to work, and perform a texture lookup on OSLRenderServices::texture3d when called with a vdb file; </div>
<div><span class="" style="white-space:pre">        </span>- create a basic cycles node for vdb, with limited functionality at this time, but that'll serve as the base for future work (future = post midterm crisis).</div><div>
<br></div><div>=== Questions ===</div><div>As of now, the plan is clear on the coding side, but I'm facing a configuration problem on mac that'll post separately to allow for discussion out of the report.</div><div>
<br></div><div><br></div><div><br></div></div>