Updated to use v63 of the EWB network database schema.
Changes to support extracting aggregation mappings on network models with LV network (no EquivalentBranches in place of LV):
Network model databases are now loaded into NetworkServices to extract meter-to-transformer mappings, instead of just queried. These mappings are cached
the first time they are extracted, so subsequent reads are performant. In the case of one network model per day, the process of extracting and caching
each day's mapping may take a long time, but subsequent aggregations for backfilled data will be fast.
The criteria for whether a transformer is a valid aggregation point is now whether it is the head of an LvFeeder, rather than whether it has meters under
it.
Similarly, only meters under equipment in an LvFeeder will be aggregated.
Meters are no longer associated directly with their aggregation point in the network model.
The configuration option previousDaysToSearchForNetwork has been deprecated in favour of daysToSearchForNetwork.
There has been no functional change, the
updated name simply gives a better representation of the search functionality which searches both forwards, and
backwards, for the closest network model.
Changed the aggregation of each PowerTransformer to use a virtual UsagePoint with a connectionCategory of LV_AGGREGATION rather than aggregating
directly against the PowerTransformer. This requires the removal and reprocessing of the entire load backlog (see note).
If you do not want to reprocess the entire backlog you can manually remove (or mark as un-cached) each of the cached readings from each days' load database,
but there are no tools or instructions on how to do this.
The configuration option previousDaysToSearchForNetwork has been deprecated in favour of daysToSearchForNetwork.
There has been no functional change, the
updated name simply gives a better representation of the search functionality which searches both forwards, and
backwards, for the closest network model.