occupation schedule should be customizable through yaml

[alexandrecuer]

ladybug_codes/generate_hvac.py

Line 199 in ab72fa3

consigne_heat = basic_compact_schedule(20, schedule_name="heating_schedule")

[alexandrecuer]

stay simple, assume opening hours are 7 to 17h on M, T, W, T, F

for example :

schedules:
  heating:
    type: compact
    temperature: 20
  cooling:
    type: compact
    temperature: 25

type could be compact or constant

[alexandrecuer]

update the doc : https://github.com/Open-Building-Management/ladybug_codes/tree/main/conf

[alexandrecuer]

maybe a dedicated file hvac24_1_0_schedule.py for schedules should be more clear

[alexandrecuer]

most schedule methods are in hvac24_1_0.py so no dedicated file is needed

• basic_compact_schedule
• constant_schedule

there is also 3 type_limits objects

schedule_typelimits name	description
temperature	created in hvac24_1_0
Fractional	created in generate_hvac
control_types	discrete integers between 0 and 4, created in generate_hvac

possible constant schedules :

• Always On, created by honeybee, why ???
• const_temp_sched_25deg if cooling is a constant 25°C schedule
• const_temp_sched_-10deg, for the borehole
• AlwaysDualSetPoint using control_types and always equal to 4, so that dual set point (cooling and heating is used)

possible compact schedules :

• heating_schedule
• cooling_schedule
• control_type_schedule, not sure it is really usefull, as right now we always go for AlwaysDualSetPoint with heating_schedule and cooling_schedule

actually we need a Always Off constant schedule to be used when using a FourPipeFanCoil as a two pipe fan coil....

[alexandrecuer]

there is also a schedule_control method in hvac24_1_0_secondary.py so that ems control can be done through availability schedule

this schedule_control method creates a compact schedule using the type_limits Fractional

Nota :
Fractional is mentioned as a string. A const should be better