Feature/fix espi parser reading types

philngo commented 8 years ago

Changed how the ESPIUsageParser handles multiple reading types by:

grouping IntervalBlock by ReadingType (assumes IntervalBlocks correspond to sibling ReadingType above)
summing forward and (negative) reverse flow direction timeseries if they have identical timestamps, and if reverse direction is available, to get a net flow (this is likely the best we can do without some bigger changes to the consuption data/project single-electricity, single-natural gas timeseries setup)
indicating presence of solar by presence of "reverse" flow direction ReadingType, because we need to be careful not to report "savings" due to solar, which is a separate methodological/regulatory beast.

coveralls commented 8 years ago

Coverage remained the same at 0.0% when pulling a82e08d81414a4a1da584d75da96cdd4792c1c2c on feature/fix-espi-parser-reading-types into 1df0dc352838c0581ef2c1d55d4d061f46c6c998 on develop.

marcrecurve commented 8 years ago

LGTM. Though all I really looked at was to see if there were some unit tests written.

mcgeeyoung commented 8 years ago

@philngo Do you have any raw data examples of "reverse" flow ReadingType data? I would be looking for a full day's worth of the raw data that would have included a few hours of reverse flow.

impactlab / eemeter

Feature/fix espi parser reading types #126