-
Notifications
You must be signed in to change notification settings - Fork 6
Scene data storage
Assets and scene data are currently stored in the directory /share/wandell/data/NN_Camera_Generalization (on gray, or other Wandell lab machines).
We anticipate moving these data sets to Flywheel. Maybe by October 1, 2018.
3-D models of objects used in the simulation.
Assets are composed of multiple meshes. The may come from a variety of sources, say Blender or Maya. When we run RenderToolbx4 we read these files, convert them into Assimp, and from there to the PBRT format. The top level *.pbrt file references these component files.
We now have ways to convert these assets into PBRT files using cinema4d plugin with PBRT V3. A new approach. That should get described in iset3d and linked to from here.
HB used this approach. We need to update the story.
Each data<>.zip files contain all the files needed to re-render a scene on the Google Cloud. The zip file includes several hundred different scenes.
Each individual scene includes a top-level PBRT files as well as all of the mesh and material components required by PBRT to render. For a realistic car scene there may be 10s of thousands of these textures, materials and mesh component files.
Each data<>.zip file contains hundreds of these scenes. In principle we can extract a single scene from the data<>.zip file and run PBRT-V2-SPECTRAL on that scene. We should do this to check.
When we transfer to run on the Cloud, we send multiple scenes. All the scenes in the data<>.zip file are moved up together at once.
To reproduce the rendering, you only need these data<> files.
Top level directories of the output files from the render toolbox working directory. It is given a name according to the recipe and many things are put in the output working directory.
Contains the textures and resources needed to render a particular scene.
This folder contains ONLY the mesh files for the scene components. These component files are in the scenes directory. We can probably delete these because they are already in the data<>.zip file. But we are being conservative and keeping them for now.
PBRT produces a
- <>.dat file that contains the multispectral data
- <>.txt file maps an integer (first column) to a specific mesh (second column), or a particular material name (2nd column)
The contents of the txt file are for meshes or materials depending on a parameter that you set in the PBRT flags.
The <>.mat is the matlab version of the <>.dat file. RenderToolbox reads the dat file and adds some information to produce the <>_radiance.mat file. In principle, you could write out the <>.dat file from the <>.mat file. The function that converts the <>.dat to the <>_radiance.mat file is ???>.
The <>_mesh.mat file