Fixed interval schedule issue

tobiaspedersentsp · May 19, 2021, 9:50am

Hi,

It seems that there is a problem (or maybe I’m using it wrong) with the HB Energy, Ladybug Tools 1.2.0, “HB Fixed Interval Schedule” component. To illustrate the issue I have set up a simple energy simulation, with two different definitions of the same schedule: One using “HB Fixed Interval Schedule” and one using “HB Weekly Schedule”.

When using the fixed schedule ligths, equipment, people are zero, but when using the identical weekly schedule they have the correct values…

With “HB Fixed Interval Schedule”

With “HB Weekly Schedule”

Any feedback is highly appreciated!
/Tobias
Test_energycalc.gh (110.5 KB)

chris · May 20, 2021, 2:18am

Thanks for letting us know @tobiaspedersentsp .

This seems to be a bug in OpenStudio’s Schedule: File object. It seems that OpenStudio SDK is trying to copy the file schedule into the generated_files directory and it just copies a blank file. I think, for now, I’ll just have the components revert back to using Schedule:Compact for the fixed interval schedule instead of Schedule:File. If you want a quick fix for now, you can just delete the schedule_directory=sch_directory from this line of the ModelToOSM component:

github.com

ladybug-tools/honeybee-grasshopper-energy/blob/master/honeybee_grasshopper_energy/src/HB Model to OSM.py#L212



# process any measures input to the component
measures = None if len(measures_) == 0 or measures_[0] is None else measures_
no_report_meas = True if measures is None else \
    all(meas.type != 'ReportingMeasure' for meas in measures)

# collect the two jsons for output and write out the osw file
jsons = [model_json, sim_par_json]
osw = to_openstudio_osw(
    directory, model_json, sim_par_json, additional_measures=measures,
    epw_file=_epw_file, schedule_directory=sch_directory)

# run the measure to translate the model JSON to an openstudio measure
silent = True if run_ == 3 else False
if run_ > 0 and not no_report_meas:  # everything must run with OS CLI
    osm, idf = run_osw(osw, measures_only=False, silent=silent)
    sql, zsz, rdd, html, err = output_energyplus_files(os.path.dirname(idf))
elif run_ > 0:  # no reporting measure; simulate separately from measure application
    osm, idf = run_osw(osw, silent=silent)
    # process the additional strings
    if add_str_ != [] and add_str_[0] is not None and idf is not None:

chris · May 20, 2021, 2:31am

I verified that going back to Schedule:Comapct by deleting that one part of that line works. So I changed the development version to use Schedule:Compact for now:

I’ll investigate the Schedule:File solution more when I get the chance and thanks for reporting.

tobiaspedersentsp · May 20, 2021, 8:54am

Thank you for the quick solution!

I just realized another problem which can be seen from the same model: The lighting and electric_equip doesn’t show from the standard component.

Eventhough they are present in the idf file

It can however be outputtet using the “HB read custom results” component.

chris · May 21, 2021, 4:23pm

The reason why you don’t see lighting and equipment is because you have an outdated version of your Ladybug Tools core libraries for the version of OpenStudio that you have installed. I suggest uninstalling and then reinstalling everything following the installation instructions and the compatibility matrix:

You can use this file to completely uninstall Ladybug Tools:
https://github.com/ladybug-tools/lbt-grasshopper/raw/master/uninstaller.gh

More info about the change that the EnergyPlus team made to create this issue can be found here:

fn · December 6, 2021, 1:58pm

hi @chris What is this FixedIntervalSchedule(.csv) for? This file blocked my running of Ironbug

chris · December 6, 2021, 11:50pm

Hi @fn

We run the FixedInterval schedules as CSV schedules since these are easier to visualize and edit as opposed to dumping the whole list of schedule values into the IDF. I don’t know why your IronBug got blocked but, if you want to avoid the CSV option, you can write all of the values into the IDF by removing the schedule_directory=sch_directory on this line of the “Model To OSM” component.

chris · February 28, 2022, 12:29am

3 posts were split to a new topic: Issues with “Run OSM” and ScheduleFixedInterval (like in Ironbug workflows)