First time here? Check out the Help page!
1 | initial version |
1) The Node::addSetpointManager overloads have been deprecated in favor of addToNode. You can also determine the setpoint node associated with an SPM with the setpointNode method.
2) If you have a setpoint manager, wpm
.
spm.setpointNode.get.nameString
3) Technically every OpenStudio ModelObject has the method object.setString(index,value)
but this is entirely unsupported and we strongly discourage doing it. These methods may even become private and inaccessible in the future as it is possible to corrupt your OpenStudio model using them.
2 | No.2 Revision |
1) The Node::addSetpointManager overloads have been deprecated in favor of addToNode. You can also determine the setpoint node associated with an SPM with the setpointNode method.
2) If you have a setpoint manager,
.wpmspm
spm.setpointNode.get.nameString
3) Technically every OpenStudio ModelObject has the method object.setString(index,value)
but this is entirely unsupported and we strongly discourage doing it. These methods may even become private and inaccessible in the future as it is possible to corrupt your OpenStudio model using them.
4) If you want to add a setpoint manager to a StraightComponent...
```
spm.addToNode(comp.outletModelObject.get.to_Node.get) ```
3 | No.3 Revision |
1) The Node::addSetpointManager overloads have been deprecated in favor of addToNode. You can also determine the setpoint node associated with an SPM with the setpointNode method.
2) If you have a setpoint manager, spm
.
spm.setpointNode.get.nameString
3) Technically every OpenStudio ModelObject has the method object.setString(index,value)
but this is entirely unsupported and we strongly discourage doing it. These methods may even become private and inaccessible in the future as it is possible to corrupt your OpenStudio model using them.
4) If you want to add a setpoint manager to a StraightComponent...
```
spm.addToNode(comp.outletModelObject.get.to_Node.get) ```
4 | No.4 Revision |
1) The Node::addSetpointManager overloads have been deprecated in favor of addToNode. You can also determine the setpoint node associated with an SPM with the setpointNode method.
2) If you have a setpoint manager, spm
.
spm.setpointNode.get.nameString
3) Technically every OpenStudio ModelObject has the method object.setString(index,value)
but this is entirely unsupported and we strongly discourage doing it. These methods may even become private and inaccessible in the future as it is possible to corrupt your OpenStudio model using them.
4) If you want to add a setpoint manager to a StraightComponent
```
#
assuming comp is a spm.addToNode(comp.outletModelObject.get.to_Node.get) ```
5 | No.5 Revision |
1) The Node::addSetpointManager overloads have been deprecated in favor of addToNode. You can also determine the setpoint node associated with an SPM with the setpointNode method.
2) If you have a setpoint manager, spm
.
spm.setpointNode.get.nameString
3) Technically every OpenStudio ModelObject has the method object.setString(index,value)
but this is entirely unsupported and we strongly discourage doing it. These methods may even become private and inaccessible in the future as it is possible to corrupt your OpenStudio model using them.
4) If you want to add a setpoint manager spm
to a StraightComponent comp
.
# assuming comp is a StraightComponent
spm.addToNode(comp.outletModelObject.get.to_Node.get)
6 | No.6 Revision |
1) The Node::addSetpointManager overloads have been deprecated in favor of addToNode. You can also determine the setpoint node associated with an SPM with the setpointNode method.
2) 2.a) If you have a setpoint manager, spm
.
spm.setpointNode.get.nameString
2.b) If you want to add a setpoint manager spm
to a StraightComponent comp
.
# assuming comp is a StraightComponent
spm.addToNode(comp.outletModelObject.get.to_Node.get)
3) Technically every OpenStudio ModelObject has the method object.setString(index,value)
but this is entirely unsupported and we strongly discourage doing it. These methods may even become private and inaccessible in the future as it is possible to corrupt your OpenStudio model using them.
4) If you want to add a setpoint manager spm
to a StraightComponent comp
.
# assuming comp is a StraightComponent
spm.addToNode(comp.outletModelObject.get.to_Node.get)
7 | No.7 Revision |
1) The Node::addSetpointManager overloads have been deprecated in favor of addToNode. You can also determine the setpoint node associated with an SPM with the setpointNode method.
2.a) If you have a setpoint manager, spm
.
spm.setpointNode.get.nameString
2.b) If you want to add a setpoint manager spm
to a StraightComponent comp
.
# assuming comp is a StraightComponent
spm.addToNode(comp.outletModelObject.get.to_Node.get)
2.b) If you have a setpoint manager, spm
.
spm.setpointNode.get.nameString
3) Technically every OpenStudio ModelObject has the method object.setString(index,value)
but this is entirely unsupported and we strongly discourage doing it. These methods may even become private and inaccessible in the future as it is possible to corrupt your OpenStudio model using them.
8 | No.8 Revision |
1) The Node::addSetpointManager overloads have been deprecated in favor of addToNode. You can also determine the setpoint node associated with an SPM with the setpointNode method.
2.a) If you want to add a setpoint manager spm
to a StraightComponent comp
.
# assuming comp is a StraightComponent
spm.addToNode(comp.outletModelObject.get.to_Node.get)
2.b) If you have a setpoint manager, spm
.
spm.setpointNode.get.nameString
3) Technically every OpenStudio ModelObject has the method object.setString(index,value)
but this is entirely unsupported and we strongly discourage doing it. These methods may even become private and inaccessible in the future as it is possible to corrupt your OpenStudio model using them.