Skip to content
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

AvailabilityManagerNightCycle Manger issue #4020

Closed
DavidGoldwasser opened this issue Jul 20, 2020 · 3 comments · Fixed by #4030
Closed

AvailabilityManagerNightCycle Manger issue #4020

DavidGoldwasser opened this issue Jul 20, 2020 · 3 comments · Fixed by #4030

Comments

@DavidGoldwasser
Copy link
Collaborator

DavidGoldwasser commented Jul 20, 2020

Issue overview

See post and video here
https://unmethours.com/question/45968/simulation-failed-when-adding-night-manager/

Current Behavior

["C:\Users\jenkins\git\OpenStudio\src\model\AvailabilityManagerNightCycle.cpp@243 : Object of type 'OS:AvailabilityManager:NightCycle' and named 'AVM Night Cycle 1' does not have a controlThermalZoneList attached:

Expected Behavior

Steps to Reproduce

  1. m = exampleModel()
  2. Go to AirLoopHVAC, go to Control
  3. Drag an AVM:NightCycle from the Library (do not use the "Use Night cycle" dropdown)

Details

Environment

Some additional details about your environment for this issue (if relevant):

  • Platform (Operating system, version):
  • Version of OpenStudio (if using an intermediate build, include SHA): 3.0.1 ff0e898

Context

@DavidGoldwasser DavidGoldwasser added the Triage Issue needs to be assessed and labeled, further information on reported might be needed label Jul 20, 2020
@DavidGoldwasser
Copy link
Collaborator Author

CC @kbenne @mdahlhausen any thoughts on this

@mdahlhausen
Copy link
Collaborator

Not sure. Maybe some interaction with always on discrete schedule and the night cycle? I haven't tried this in OS 3.0 yet. Seems like a bug for sure.

@tijcolem tijcolem added severity - Normal Bug component - Model and removed Triage Issue needs to be assessed and labeled, further information on reported might be needed labels Jul 31, 2020
@jmarrec
Copy link
Collaborator

jmarrec commented Aug 4, 2020

I was able to reproduce, I edited the OP to include steps to reproduce.

The key is Drag from Library (= Clone) and not use the "Use Night cycle" dropdown (= Constructor).

The Constructor will create the needed ModelObjectList, the clone isn't doing it.

Ideally these would be have children of the AVMNightCycle, I think I didn't do that because of the OSApp (or they would actually show), and I will not do that now either. Either way, the clone/remove need to be overridden

@jmarrec jmarrec assigned jmarrec and unassigned kbenne Aug 4, 2020
jmarrec added a commit that referenced this issue Aug 4, 2020
jmarrec added a commit that referenced this issue Aug 4, 2020
kbenne added a commit that referenced this issue Aug 10, 2020
Fix #4020 - AvailabilityManagerNightCycle: Ensure ModelObjectLists are handled in clone/remove
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants