Hi Everyone,

I am trying to convert thermostat schedules written using Schedule:Ruleset to using Schedule:File, so, I can have my own temperature setpoint profiles across the 8760 hours. Before I made any adjustment on the setpoint values, I took a test to compare the model performance using either method and with the same setpoint profiles. My workflow was by running a single run on Schedule:Ruleset to produce the hourly temperature setpoint values and modify the model to use Schedule:File by reading a .csv files containing the setpoint values.

The model-run using Schedule:File changes the components' sizing. It looks it is because the model does not include the design day schedules that were originally part of the Schedule:Ruleset. Is there any way to go around it? Alternatively, I can use Schedule:Compact with the designdays schedules and the hourly setpoint profiles.

Thanks,

Hi Everyone,

I am trying to convert thermostat schedules written using Schedule:Ruleset to using Schedule:File, Schedule:File, so, I can have my own temperature setpoint profiles across the 8760 hours. Before I made any adjustment on the setpoint values, I took a test to compare the model performance using either method and with the same setpoint profiles. My workflow was by running a single run on Schedule:Ruleset Schedule:Ruleset to produce the hourly temperature setpoint values and modify the model to use Schedule:File Schedule:File by reading a .csv files containing the setpoint values.

The model-run using Schedule:File Schedule:File changes the components' sizing. It looks it is because the model does not include the design day schedules that were originally part of the Schedule:Ruleset. Schedule:Ruleset. Is there any way to go around it? Alternatively, I can use Schedule:Compact Schedule:Compact with the designdays schedules and the hourly setpoint profiles.

Thanks,

Hi Everyone,

I am trying to convert thermostat schedules written using Schedule:Ruleset to using Schedule:File, so, I can have my own modify the hourly temperature setpoint profiles across the 8760 hours. Before I made any adjustment on the setpoint values, I took a test to compare the model performance using either method and with the same setpoint profiles. My workflow was by running a single run on Schedule:Ruleset to produce the hourly temperature setpoint values and modify the model to use Schedule:File by reading a .csv files containing the setpoint values.

The model-run using Schedule:File changes the components' sizing. It looks it is because the model does not include the design day schedules that were originally part of the Schedule:Ruleset. Is there any way to go around it? Alternatively, I can use Schedule:Compact with the designdays schedules and the hourly setpoint profiles.

Thanks,

Hi Everyone,

Everyone, I am trying to convert thermostat schedules written using Schedule:Ruleset to using Schedule:File, so, I can modify the hourly temperature setpoint across the 8760 hours. Before I made any adjustment on the setpoint values, I took a test to compare the model performance using either method and with the same setpoint profiles. My workflow was by running a single run on Schedule:Ruleset to produce the hourly temperature setpoint values and modify the model to use Schedule:File by reading a .csv files containing the setpoint values.

The model-run using Schedule:File changes the components' sizing. It looks it is because the model does not include the design day schedules that were originally part of the Schedule:Ruleset. Is there any way to go around it? Alternatively, I can use Schedule:Compact with the designdays schedules and the hourly setpoint profiles.

Thanks,