Closed lrg-bhoefle closed 6 years ago
Definitely. This is on my list since a long time already. It didn't have high priority for me, since I'm usually testing HELIOS with rather small scene files, but the advantage for larger scenes is obvious. Actually I'm already surprised about what huge scenes some people use with HELIOS without going crazy :D.
This option has been implemented. The scene will be written into a binary file after its first creation (in the same folder that the scene's .xml but with the .scene extension). Following simulations will read this binary file when available instead of creating the scene again. If the scene definition is modified, the binary file will be ignored as is not up-to-date anymore and it will be re-written after the execution.
For large datasets the building of the KD-tree takes large parts of the total runtime. Several use cases exist where a re-use of the KD-Tree is possible. You build it only once and can re-use it inother simulations as scene input (e.g. reading it direclty from a binary compressed image on disk). This issue requests for an input/export option for the KD-tree.