NatLabRockies / NatLabRockies/EnergyPlus

Incorrect Interval value in SQLite Time table for multiple reporting frequencies exist

Open
#8,367 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.6k
Forks
490
Avg merge
6d 21h
Merged PRs (30d)
22

Description

Issue overview

Details

Some additional details for this issue:

  • Platform (Operating system, version): Windows 10
  • Version of EnergyPlus (if using an intermediate build, include SHA): V9.4

Using the example file 1ZoneEvapCooler.idf without any changes. There are two meters Facility:Electricity and HVAC:Electricity reported in both Monthly and Run Period. However, in the SQLite Time table, the Interval column only contains value 60, which is the reporting frequency for the output variables.

image
image

My first thought is that only the smallest reporting frequency will be reported. So I did some experiments. I removed all output variables and only included those two meters with various reporting frequency combinations and found that:

  1. With Hourly & Daily: Both 60 and 1440 are reported in the Interval column.
  2. With Daily & Monthly: Both 1440 and 44640 are reported in the Interval column.
  3. With Monthly & Annual: Only 44640 (Monthly) is reported in the Interval column.

I have no idea why this inconsistency comes from. This behaviour makes it hard to use the SQLite to extract data with certain reporting frequency.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with 1ZoneEvapCooler.idf on EnergyPlus 9.4, configuring the two meters with the Monthly and Annual frequencies. Inspect how the SQLite Time table is populated and compare the Interval values for each reporting frequency. Done means the table consistently includes the expected intervals and SQLite extraction can distinguish the configured frequencies.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, sqlite
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.