Is it, though? Did you save the simulation model to a Honeybee JSON file and then load up that model in the file that you are using to visualize results? Or, instead, did you re-run the Grasshopper script that creates the model, thereby generating an âequivalentâ model that is actually a new instance?
The former will be match-able to your simulation results but the latter will usually not be unless you have managed to hard-set the unique IDs of all the model elements using the âHB Set Identifierâ component.
Also note that, when you run the simulation with the âHB Model To OSMâ component, you automatically get a .hbjson model JSON within the simulation folder. So you can always load that up and have it match with the sql results. Having the future âLookup Folderâ component return both the hbjson and the sql files seems useful.
Ohhh, Json, Json âŚ
Indeed i was connecting the original model.
Now with the Json it works.
Though, i remember a different topic regarding the shading control that is not yet (well) implemented in the Json file. Right now the models that i create having shading controls canât be imported with the LoadObjects component.
Iâll wait for that.
Thanks for reminding me about the Json @chris,
-A.
Thanks for reporting the issue with WindowConstrucitonShade, @AbrahamYezioro . There were a couple of bugs that I found in the case of schedules being applied to the object. They have all been fixed between the PRs below and I can now say confidently that the schedules for the WindowConstructionShade make it safely thought JSON serialization/re-serialization and they make it into the OSM/IDF.