Octree files are a reusable representation of the Radiance scene. We need to create an reuse them for all the different Radiance recipes.
I most cases creating the octree is pretty quick but it can add up for parametric runs, matrix-based slides and most importantly large scenes. It might be a good idea to consider a way for users to share/reuse octree files next to rad files.
The first option is that we include the octree file in scene folder. In that case we have to assume that the rad files that are used to generate the octree are not included in the scene anymore to avoid double counting.
Another options is to create a new folder for octree and enforce a naming convention for the files. For instance scene.oct, scene_no_aperture.oct, scene_black_no_aperture.oct. In this case, if the octree is available we can reuse it and if it is not created we will create one.
The second approach can also be mixed with the first one. In this scenario user can include an octree in the scene folder which will be considered as part of the scene which is not included in the rad files and will be added to the octree files. This will be very useful for not recreating the octree for a large context and share it between different simulations.
I'm still figuring out how the naming should work and what will be the best organization of the octree files which I will know once I start writing the workflows.
Octree files are a reusable representation of the Radiance scene. We need to create an reuse them for all the different Radiance recipes.
I most cases creating the octree is pretty quick but it can add up for parametric runs, matrix-based slides and most importantly large scenes. It might be a good idea to consider a way for users to share/reuse octree files next to rad files.
The first option is that we include the octree file in scene folder. In that case we have to assume that the rad files that are used to generate the octree are not included in the scene anymore to avoid double counting.
Another options is to create a new folder for
octreeand enforce a naming convention for the files. For instancescene.oct,scene_no_aperture.oct,scene_black_no_aperture.oct. In this case, if the octree is available we can reuse it and if it is not created we will create one.The second approach can also be mixed with the first one. In this scenario user can include an octree in the
scenefolder which will be considered as part of the scene which is not included in the rad files and will be added to the octree files. This will be very useful for not recreating the octree for a large context and share it between different simulations.I'm still figuring out how the naming should work and what will be the best organization of the octree files which I will know once I start writing the workflows.