-
Notifications
You must be signed in to change notification settings - Fork 5
add point groups docs #26
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
base: main
Are you sure you want to change the base?
Conversation
modeling/point-groups.md
Outdated
|
|
||
| ## Migration Notes | ||
|
|
||
| - Existing models where controllers hosted individual points should introduce Point Groups and shift the `brick:hosts` relationship to target the group. Equipment such as VAV boxes can continue to reference their points through `brick:hasPoint`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since brick:hosts wasn't merged yet, I think we can remove this point.
|
Looks good for me, just have a minor comment. Thank you @gtfierro! |
Clarify the role of Point Groups in modeling and emphasize their relationship with `brick:hasPoint`.
| Avoid inferring semantics from group membership alone. For example, adding a setpoint and its min/max limits to the same Point Group does *not* mean those limits constrain that setpoint. Model explicit relationships if you need to express functional ties. | ||
| ``` | ||
|
|
||
| This is *not* a replacement for `brick:hasPoint`! You should still use `brick:hasPoint`/`brick:isPointOf` to relate points to their equipment. This modeling construct focuses on the networking/instrumentation of the system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it help to give a few examples?
- a
VAVcould have aSupply_Air_Flow_Sensor, but this point is hosted by aController - a
Controllercould have anOn_Off_Status, which is hosted also on the sameController
No description provided.