This PR makes the following changes following discussion in issue #22.
Rather than using an integer field to indicate end-of-year or mid-year compounding, we define timestepComp to be a Django ChoiceField, that user can choose to be either "EndOfYear", "MidYear", "Continuous". timestepVal will be independent from timestepComp.
The present value computation method in e3_django/compute/api.py was changed to use mid-year discounted costs (t-0.5) instead of (t).
Motivation and Context
Previously, E3 assumed end-of-year (EOY) discounting. However, some third parties would be interested in mid-year discounting (or continuous compounding) rather than EOY. We need a way to track which discounting we are using, and incorporate this into our calculations.
Description
This PR makes the following changes following discussion in issue #22.
Rather than using an integer field to indicate end-of-year or mid-year compounding, we define
timestepCompto be a Django ChoiceField, that user can choose to be either "EndOfYear", "MidYear", "Continuous".timestepValwill be independent fromtimestepComp.The present value computation method in
e3_django/compute/api.pywas changed to use mid-year discounted costs (t-0.5) instead of (t).Motivation and Context
Previously, E3 assumed end-of-year (EOY) discounting. However, some third parties would be interested in mid-year discounting (or continuous compounding) rather than EOY. We need a way to track which discounting we are using, and incorporate this into our calculations.
Closes #22