That is why I was asking because enabling the recipes to accept multiple .pkl inputs would not be time-saving. It essentially means that each file would have to get loaded up and joined into one .pkl file before being sent to the rest of the simulation, which could significantly increase the run time.
Conversely, all of the current Radiance recipes start by translating the Model file (either in the form of a HBJSON or HBPKL) into a Radiance folder. So, if we allowed you to plug the path to a Radiance folder into the recipe instead of a model file, this could actually save some time in the first step of the recipe. Moreover, you could drop whatever extra files you want into this folder as long as you put them in the right place according to the Radiance Folder Structure.
We already have a component that can translate your Honeybee Model to a Radiance folder and we can easily add another that just serializes lists of objects into individual .rad/.pts/.vf files. So, then, you can write or coy these files into this Radiance folder. Or, better yet, we just add an input on the “Model to Rad Folder” component for _add_files, which senses the file extension and drops the extra objects into the correct subfolder.
I guess I’m just uncertain if this whole effort is really worth it because being able to create honeybee objects from meshes in LBT is already pretty fast. We had been thinking that this essentially replaces the speed that you got with “scene files” and “additionalRadFiles” that you had in older versions.
I would just want to be sure that it’s the creation of these files that is really THE pain point and not some other issue that arises when you create models like yours, which must have hundreds of thousands of polygons. For example if this is the bigger pain point, maybe we should be focusing our efforts elsewhere.