review operation so it can be a dict or a list#170
Conversation
| Plantequipmentoperationschemes( | ||
| operations = [] | ||
| if isinstance(loop_machines, dict): | ||
| for operation_type, machines in loop_machines: |
There was a problem hiding this comment.
So a possible operation conf in loop can be :
operation:
uncontrolled: [borehole]
cooling : [fcu_RDC_coil_cooling_water, fcu_RPLUS1_coil_cooling_water]
There was a problem hiding this comment.
And
operation: [borehole, fcu_RDC_coil_cooling_water, fcu_RPLUS1_coil_cooling_water]
Still works
But all loop equipments will be classified the same way, as per Loop_Type indication
There was a problem hiding this comment.
documentation to amend if this is merged
There was a problem hiding this comment.
To create a fan coil unit (fcu) using a coil_cooling_water named fcu_RDC_coil_cooling_water, the user just declares fcu_RDC in the yml key equipments
- then
fcu_RDCbecomes a zone equipment - and
fcu_RDC_coil_cooling_watera plant equipment, but referenced under thefcu_RDCkey, that permits not too change much the code but for the user, it can be an intellectual mess
so actually, you cannot declare things like that :
operation:
uncontrolled: [borehole]
cooling : [fcu_RDC_coil_cooling_water, fcu_RPLUS1_coil_cooling_water]
the correct way should be
operation:
uncontrolled: [borehole]
cooling : [fcu_RDC, fcu_RPLUS1]
There was a problem hiding this comment.
CAUTION :
the code is a nice improvment, but coilcoolingwater is not a good use case : the coil cannot go in a plantequipmentlist, it is a consomation object, not a production one, even if you connect it on a plantloop !!!
There was a problem hiding this comment.
Le PlantEquipmentOperation ne pilote que le Supply Side.
1 participant
No description provided.