-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloning building doesn't bring over thermostatSetpointDualSetpoint #978
Comments
This is made particularly tricky because both the thermal zones and the thermostats each get new UUID's when cloned in vs. preserving the original ones. Issue #870 is directly related to this. It also isn't ideal that thermostats and setpoint schedules use UUID's for names, both for readability in app, and in E+ errors/warnings. Plus it also makes diffing files with each other because every time I generate it the names are different. Thermostat and setpoint schedules should be named after thermal zone they serve (when used as non-shared thermostat as they are in reverse translation) OS:ThermostatSetpoint:DualSetpoint, |
Not pretty, but this works for now to address both issues.
I'll have to do something similar for SHW, but that doesn't even make it trough reverse translation, so I'll have to extract it directly out of the IDF file and then make OSM objects with the same water use demand. |
@kbenne is this fixed? Can you close it? |
@kbenne nevermind, I accepted the pivotal ticket I will close |
Cloning building from one model to another doesn't bring over thermostats. Directly cloning thermal zones has the same results. @kbenne is this the desired behavior? It makes it tricky for me to bring in ref buildings because I need to bring in and re-wire zones to thermostats manually, (FYI my workflow is to translate ref IDF to model2, and then clone that building into the original model.
Water use equipment doesn't come in either, but that is how I expect that worked, but still isn't ideal.
cc: @asparke2
The text was updated successfully, but these errors were encountered: