You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have seen an issues where when I'm disconnecting components like Area's and Buses from a system the reference of which buses are in each area is lost. Why is this done?, since we do keep the reference of the Bus when disconnecting a Generator from the system. Can we do the same for Areas ?
The text was updated successfully, but these errors were encountered:
What would it mean to have an Area referenced in a Bus that isn't in the system? Also, what would it mean to have a bus in an area that isn't in the system?
The described behavior is as expected IMO. I will close this issue since it seems more of an user problem
@sourabhdalvi I want to ensure that your question is addressed. The logic of your question may be inverted. The specific behavior is the following:
User removes an Area or LoadZone from a system.
PSY loops over all buses in the system and removes any connection to the area or load zone. For example, bus.area will be set to nothing.
If the user removes a Bus, the area and/or load zone is still set on that object. That behavior is identical to removing a Generator. This seems a bit odd to me if generator.bus or bus.area is still attached to the system. Maybe we should require removal of child components before removal of the parent.
I have seen an issues where when I'm disconnecting components like Area's and Buses from a system the reference of which buses are in each area is lost. Why is this done?, since we do keep the reference of the Bus when disconnecting a Generator from the system. Can we do the same for Areas ?
The text was updated successfully, but these errors were encountered: