I have a front ended app that conforms to Floorspace.js and creates a JSON based on user described geometry and input .I have a measure that imports the geometry to OS (Outputs a model). Before the model is imported to OS, I need to modify/update the HVAC system(s) and update the zone parameters based on the user selections. Any help with how I can do that?
If you have not already, you can map the FloorSpaceJS space types to standards space types for DOE or other prototype building types, and then run one of our "create_typical" measures such as this one for DOE building types. This measures expects a model that has stub space types tagged with the standards building type and space type. It has individual switches ti add constructions, internal loads, SWH, elevators, exterior lights, exhaust, refrigeration, internal mass, and HVAC systems. Mechanical systems can be specified or inferred from high level inputs. https://github.com/NREL/openstudio-model-articulation-gem/tree/develop/lib/measures/create_typical_doe_building_from_model
Here is an example OpenStudio Workflow (OSW) that uses a measure to convert FloorSpaceJS to OSM, and then to add constructions loads and systems. I did notice your question talks about adding HVAC before importing from FloorSpaceJS, but what I props here is the opposite. The FloorSpaceJS schema doesn't currently contain inputs for mechanical systems, other than just the thermal zone object.
One Additional note, the FloorSpaceJS schema does have space types and a name field, but doesn't have standards information. You could modify the FloorSpaceJS translator to infer standards space type from the space type name or from a lookup table. In our case we are merging back into an OSM seed that has already identified these space types contained in the floorSpaceJS jason input file.
Sorry, just realized some of my links and suggestions are repetitive to what is here. https://unmethours.com/question/44432...
Thank you David :-) No problem. I guess that I need to explain a little bit more. So the generated JSON should include information about pre-retrofit HVAC equipment/controls and post-retrofit HVAC equipment/controls. I want to import the generated JSON to OS and add the HVAC pre-retrofit choices and generate one model. Then using another measure import the JSON again but with post-retrofit HVAC choices. The final purpose is to export both models to IDF and Run EnergyPlus simulation to output savings based on HVAC equipment/controls retrofit.
You lost me a bit with this comment. The FloorSpaceJS schema doesn't contain any HVAC equipment. It contains spaces surfaces, and then attributes that can be assigned to a space such as zones, building story, space types, etc.
Asked: 2020-05-29 14:03:21 -0500
Seen: 200 times
Last updated: May 29 '20
