@mostapha May I know what “Story” is for? I looked into the idf file after energy simulation, but Story is nowhere in the idf file. Is it used only for the room sorting purpose in Rhino and OpenStudio?
Yes. Sorting is one of the obvious use cases in the Rhino interface. And you are correct that it will not be exported to an IDF file.
That said, the story is an important feature in certain cases. These are the two that I can remember:
If the model is exported to eQuest (INP), Dragonfly (DFJSON), or IDA ICE (IDM) we use stories to group the rooms for each level.
Many of OpenStudio measures rely on the story property to work correctly.
If you want to check the
RoomOverlapOnlywhen you run the
PO_ValidateModelcommand, you must set up the stories in Rhino for the command to work.
You pretty much summarized the main use cases there, @mostapha , and I can’t remember any other reasons. I think this may not be 100% correct though:
None of the validation commands check for whether the model has stories and Honeybee/Pollination models are considered valid without them. But, when we export the model to OpenStudio, we usually auto-generate the stories based on the floor elevations of the Rooms if no existing Story definitions were found. You can see that this happens in the Model To OSM component:
If stories are important for some of the other translators like INP or IDA-ICE, maybe we should perform a similar check as part of the translation process in those packages.
I just remembered actually. If you want to check the
RoomOverlapOnly when you run the
PO_ValidateModel command, you must set up the stories in Rhino for the command to work.
A post was split to a new topic: Can I automatically rename the rooms to include the story name?