v8.1 to v8.2
Modelling
YAML
LTP
Result
Operational settings used is now 1-based
Consumer systems will now refer to the first operational setting as 1 instead of 0. 0 means that "No setting was used", indicating that none of the operational settings was able to handle the stream. This will make it easier for users to find the corresponding operational setting that is/was active for the different timesteps.
Resampling of rates changed from forward filling to average rates
All calculations are performed on a global time vector, which is the union of all dates found in the input resource files (csv files) where INFLUENCE_TIME_VECTOR is set to True, dates found in the eCalc model yaml-file (temporal models), and dates in the requested output frequency.
If the global time vector and the dates in the requested output frequency does not coincide fully, a resampling of the results needs to be performed. Previously this was done by simply picking the first available rate in the time interval (forward filling). The rates are thought to be constant in a period between two dates, hence the forward filling will disconnect the rates and the cumulative volumes. This has now been changed to calculating the average rate from all dates in the global time vector within a date range in the requested output frequency, to keep the rate and cumulative consistent with each other. This average will take into account the lengths of the periods and the regularity within each period. The figure below shows a comparison of how the resampling would previously have been done compared to how it is done now when making quarterly output from monthly results.
TLDR; this change will make it possible to use the rate output data (rate from a point in time) from eCalc correctly.
LTP .tsv file
- Column Total CO2 is removed from LTP output (both for fixed & mobile installations)
- Add relevant columns in ltp-file for the two new consumer categories
HEATER
andBOILER
- Re-order some of the columns in the ltp-file, for more logical order
- Turbine-columns are now filtered on the two consumer categories
TURBINE-GENERATOR
andGAS-DRIVEN-COMPRESSOR
, as it is no longer only turbines that are consumers of FUEL-GAS
STP .tsv file
- Report CO2 emissions for both fixed- and mobile installations
- Report CH4 emissions for fixed installations
Emissions, structure and order
The JSON result file has changed format for emissions. Emissions were previously listed in a list, but is now listed in a map:
"emissions":
[
{
"name": "co2"
...
to
"emissions":
{
"co2":
{
"name": "co2"
...
This will/may also affect the order of which emissions are presented in the result file, but should from now on be consistent.
Behaviour
Conditions
eCalc will now consistently NOT evaluate and run calculations if a CONDITION is not fulfilled. Conditions can be set on most energy consumers, to indicate whether the consumer is active or not at a given timestep. Previously the consumer was evaluated even though a condition was not fulfilled to reflect "what would have happened if it was active". However this has proven to be difficult for users to understand and remember when the overall model result is being evaluated and analyzed. In order to prevent user errors, we have decided to consistently NOT evaluate a consumer for timesteps where it is disabled (conditions evaluated to true).