让总量相加一致
阅读约需 47分钟 分钟,7节中含2个示例。
你将用两种方法预测三十个客户的总需求,在决策窗口上比较这两种方法并做出选择,然后仅使用每个截止时间之前的历史数据,把总量拆分为各客户的份额。
供应商对次日电力的采购只有一次,依据的是其所有客户的总需求,而不是任何单个客户的需求。第 6 章预测了每个客户的需求,总量既可以由这些预测汇总得到,也可以单独预测。本章要问的是:这两种结果是否一致,又该信任哪一种。两者都在与之前相同的窗口上评分,因此比较是公平的。本章的示例沿用第 6 章的客户、窗口和尺度,所以这里的每个数字都由一个你可以运行的示例输出。
为什么总量需要核对
同一个量的两个预测可能彼此不一致,因为它们经由不同的路径得到。这里的量是三十个客户(ALL30)在每小时的总需求。一条路径是把三十个客户的预测相加,另一条路径是对总量序列拟合一个模型。两者读取的是同样的读数,但各有各的失误方式。求和会把每个客户的误差都带入总量。总量模型只看到总量自身的模式,各客户各自的模式可能在其中消失。
这项核对之所以重要,是因为供应商按总量而不是按各个客户采购。即使每个客户都预测得很好,只要各客户的误差在同一小时偏向同一方向,总量也可能出现偏差。因此,本章按顺序提出两个问题。第一,数据中各部分之和是否等于整体?第二,在关键的窗口上,总量预测是否优于各部分预测之和?
相加一致的预测称为协调预测(coherent forecasts)。Hyndman 和 Athanasopoulos 的 Forecasting: Principles and Practice,第 3 版,第 11 章 列出了几种使预测协调的方法,其中有两种与此处相关。自下而上(bottom-up)先预测最底层,这里是各个客户,再把结果求和。自上而下(top-down)先预测顶层,即总量,再按比例把它向下拆分。本章只在这两种意义上使用这两个名称。
协调性是一种约束,而不是对准确度的度量。相加一致的总量预测仍可能比不一致的更差。因此,本章对总量和每个客户分别评分,绝不因为各部分一致就接受某个预测。
本书用 pandas 手工构建这两种总量,而不使用 hierarchicalforecast。该层级结构只有一层,所以每条路径只是一次求和或一次拆分,运行开销也很小。确实存在一种能以最优方式结合两条路径的方法。MinT 在无偏性假设下,选取使协调预测的均方误差最小的协调预测,并使用预测误差的协方差矩阵(Wickramasuriya、Athanasopoulos 和 Hyndman,2019;公开的工作论文见 robjhyndman.com/papers/mint.pdf)。估计该矩阵本身就是一个独立的课题,本章不涉及。
工作准则: 只要决策依赖总量,就用两种方式预测总量。在相同的窗口上为两者评分,既针对总量,也针对每个客户。保留在决策窗口上表现更好的方法,绝不因为各部分相加一致就接受某个总量预测。
对各客户的预测求和
自下而上的总量预测,是把第 6 章得到的三十个客户的预测逐小时相加。在每个截止点,一个全局模型使用滞后 24 和 168,以及第 6 章保留的客户标识,对每个客户预测未来 24 小时。总量在某一小时的预测,等于该小时三十个预测值之和。设 c 为某个客户,t 为某个小时,则规则为 total(t) = sum over c of forecast(c, t)。
这个求和在构造上必然成立,所以真正需要检查的是数据。总量序列在每个小时都必须等于三十个客户读数之和,否则所有评分所依据的数值都是错的。例外是时钟变更的小时。时钟变更标记会把客户的读数设为缺失,因此总量在 2013 年 3 月 31 日和 2014 年 3 月 30 日的 01:00(跳过的小时)缺失,在 2013 年 10 月 27 日和 2014 年 10 月 26 日的 01:00(重复的小时)也缺失。
下面的每个评分都是相对于总量计算的,所以必须先确认总量与各部分相符。第一个示例构建两种总量并为其评分,其最后几行在每个无时钟变更的小时检查这种相符。
1"""Forecasts the total of the thirty clients two ways, bottom-up (the sum of the client forecasts) and direct (one model on the2total), and chooses between them on the four decision windows by MAE on the total. The choice rests on the two decision-window3MAE lines; the standard cutoffs then report both beside seasonal naive, and the last two lines check the total and the scale."""4import pandas as pd56from lib.baselines import seasonal_scale7from lib.electricity import load8from lib.panel import ALL30, DECISION_CUTOFFS, check_decision_hours9from lib.scoring import actual_hours, score_windows10from lib.settings import EVAL_CUTOFFS, show11from lib.totals import (DIRECT_SCALED, METHODS, TOTAL, direct_windows, plain_mae, pooled_mae, total_checks,12 total_forecasts, total_frame, total_scale_rows)1314raw = load(ALL30)15total = total_frame(raw) # the hourly sum of the thirty clients, after the start rule; missing in a clock-change hour16dec, cut = pd.to_datetime(DECISION_CUTOFFS), pd.to_datetime(EVAL_CUTOFFS)1718dec_actual = actual_hours(total, dec)19# the direct model here uses the target setting the book chose: DIRECT_SCALED is False, so the direct total is unscaled20dec_mae = pooled_mae(dec_actual, total_forecasts(raw, dec), ["bottom-up", "direct"])21# the direct model's MAE with its target scaled (True) and unscaled (False)22direct_setting = {s: pooled_mae(dec_actual, direct_windows(raw, dec, scaled=s), ["direct"])["direct"]23 for s in (True, False)}24# stops the run if the constant no longer names the setting with the lower MAE25if direct_setting[DIRECT_SCALED] != min(direct_setting.values()):26 raise ValueError("DIRECT_SCALED is not the target setting with the lower MAE on the decision windows")27show("decision cutoffs", len(dec))28# raises if a decision hour is a Portuguese holiday or reaches the held-out week; the count is printed for the record29show("decision holiday hours", check_decision_hours(dec_actual))30show("MAE bottom-up, decision windows", dec_mae["bottom-up"])31show("MAE direct, decision windows", dec_mae["direct"])32show("MAE direct with a scaled target, decision windows", direct_setting[True])33show("chosen direct target", "unscaled" if not DIRECT_SCALED else "scaled")34# the bottom-up total without the client identifier, which Chapter 6 also tried35show("MAE bottom-up without identifier, decision windows", plain_mae(raw, dec))36show("chosen total method", dec_mae.idxmin())3738# the scale reads the readings before the first standard cutoff, and no later ones39scale = total_scale_rows(raw, cut[0])40scored, per_client = score_windows(actual_hours(total, cut), total_forecasts(raw, cut), METHODS, scale)41show("scored hours", len(scored))42# seasonal_scale returns one value per unique_id, so [TOTAL] picks the total's43show("MASE scale of the total", seasonal_scale(scale)[TOTAL])44for model in METHODS:45 show(f"MAE {model}", (scored["y"] - scored[model]).abs().mean())46for model in METHODS:47 show(f"MASE {model}", per_client.loc[TOTAL, model])48show("MAE bottom-up without identifier", plain_mae(raw, cut))49# the first cutoff is passed as first_cutoff; the scale check then runs on every cutoff in cut50for label, value in total_checks(raw, cut[0], cut).items():51 show(label, value)
python total-bottom-up-and-direct.pydecision cutoffs: 4
decision holiday hours: 0
MAE bottom-up, decision windows: 1267.47
MAE direct, decision windows: 1678.62
MAE direct with a scaled target, decision windows: 1705.71
chosen direct target: unscaled
MAE bottom-up without identifier, decision windows: 1383.29
chosen total method: bottom-up
scored hours: 72
MASE scale of the total: 2689.26
MAE SeasonalNaive: 3639.41
MAE bottom-up: 2985.88
MAE direct: 3423.11
MASE SeasonalNaive: 1.35
MASE bottom-up: 1.11
MASE direct: 1.27
MAE bottom-up without identifier: 2837.66
clock-free hours where the total differs from the sum of the thirty clients: 0
scale changes after poisoning readings from each scored cutoff: 0
在每个没有时钟变更标记的小时,总量都等于三十个客户之和。该检查统计出有 0 个小时不一致。
时钟变更的小时还需要另一条规则。这些小时的总量缺失,但预测并不缺失。每个预测窗口仍会为每个带标签的小时给出一个值,因此输出网格中没有空洞,下游的表无需再去填补。评分会拒绝没有读数的预测小时,所以被屏蔽的小时不会被当作零来评分。本章中没有任何参与评分的窗口包含这样的小时。
起始规则在求和之前对每个客户应用。起步较晚的客户在首个读数之前的零并不是需求,所以该规则会将其丢弃,正如第 4 章对一个客户所展示的那样。该规则不会改变总量,因为零对求和没有贡献,尚未起步的客户同样没有贡献。上面的检查说明了这一点。该规则确实会改变每个客户自己的预测,因为在这些零上拟合的模型会把它们当作低用量来学习。
自下而上的总量会继承各客户的误差,无论好坏。第 6 章发现,在标准截止点上,该模型在三十个客户中有 23 个优于季节性朴素法,其余客户则表现更差。本章后面的比较将衡量这些误差有多少传递到了总量上。
只有均值可以相加。和的均值等于均值之和,因为期望是线性的。和的中位数一般并不等于中位数之和,其他分位数也是如此。它们只在特殊情形下才相加,例如各误差完全同向变动。因此,自下而上的总量是一个点预测。总量的区间不能通过把各客户的区间相加得到。第 8 章在讨论区间时会回到这一点。
工作准则: 先检查总量序列在每个没有时钟变更标记的小时都等于其读数之和,然后逐小时对各客户的预测求和。在求和之前对每个客户应用起始规则,使任何客户的模型都不在其零值上拟合。将求和结果视为点预测,不要把各客户中位数之和当作总量的中位数。
直接预测总量
直接法的总量由一个模型给出,该模型拟合的是总量序列本身。它的历史就是截止点之前的总量历史:即截止点之前 1,344 小时的读数,也就是 8 周,与各客户的历史长度相同。每个客户的历史按起始规则截取,其中时钟调整所涉及的小时用该客户自身相邻的读数填补,做法与第 3 章相同,然后按小时对读数求和。因此,总量的历史中没有缺失的小时。
该模型使用与各客户相同的特征。它的输入是总量在 24 小时前和 168 小时前的读数,所以没有任何输入来自被预测的那一天。它的目标是未经缩放的总量。第 6 章对每个客户的目标做了缩放,因为用一个模型拟合规模各异的客户时,模型否则会偏向拟合规模大的客户。单一的总量不存在这种混合,所以这一理由不再适用。在决策窗口上,未缩放的目标误差更低,为 1678.62 kWh,而缩放目标后为 1705.71 kWh,见第一个示例,因此直接模型采用未缩放的目标。模型在每个截止点各拟合一次,只使用该截止点的历史,并预测随后的 24 小时。它是 mlforecast 1.1.0 中的一个 LightGBM 回归器,设置沿用第 5 章。
两种总量的构造方式不同。自下而上的总量来自一个预测所有客户的全局模型,直接法的总量则来自一个预测总和的模型。滞后项和其他设置相同。目标缩放不同,决策窗口只为直接模型选定了它。
总量通常比任何一个客户都平滑,因为各客户的峰值在求和时会部分抵消。拟合到较平滑序列上的模型需要学习的自身噪声较少,这可能有利于直接法的总量。本章后面的比较会检验在这些窗口上是否如此,而结果并不是平滑性所暗示的那样。
模型只通过历史来观察总量。它看不到某个读数来自哪个客户,也看不到是哪个客户使总量发生了变动。这正是直接法所做的取舍:得到一条平滑的序列,却失去了各客户各自的形状。自下而上的方法保留了这些形状,但必须把三十个误差加在一起。
对总量做季节性朴素预测,是两种方法都必须超过的基线。它把每个小时预测为前一天的同一小时,如第 2 章所述,只是应用于总量的历史。它在相同的窗口上评分,并采用相同的尺度。
工作准则: 用各客户的特征,根据每个截止点之前总量自身的历史直接预测总量,并在决策窗口上选定目标的缩放方式。两种方法使用相同的窗口,并各自与总量上的季节性朴素预测比较评分。两种方法都要报告,不要只报告自己构建的那一种。
这部分尚未翻译,因此以英文显示。
Compare the two totals
On the four decision windows, the bottom-up total has the lower error, so it is the method chosen. Those windows are Chapter 5's four ordinary days before the held-out week, used only to choose: Nov 25, Nov 26, Dec 2 and Dec 3, 2014. Chapter 6 chose the client identifier on the same days. Each method is scored by MAE on the total, and bottom-up's MAE there is 1267.47 kWh, against 1678.62 kWh for the direct total. The example refuses to run if a decision hour falls on a Portuguese holiday, and it counts 0 such hours.
The standard cutoffs, Dec 29 to Dec 31, 2014, are the report. They are not used to choose. On these three windows the total has 72 scored hours. Its MASE scale is the mean absolute change between readings a day apart, taken over every reading before Dec 29, 2014, with the clock-change hours masked. That is the rule for a MASE scale from Chapter 2, as Chapter 6 applies it to each client, here applied to the total, and it comes to 2689.26 kWh.
| Method | MAE (kWh) | MASE |
|---|---|---|
| Seasonal naive | 3639.41 | 1.35 |
| Bottom-up | 2985.88 | 1.11 |
| Direct | 3423.11 | 1.27 |
MAE and MASE rank the methods alike here. MAE is in kilowatt hours, so it reads as the average cost of an hour's error. MASE divides each error by the same scale, so on one series it is only a constant multiple of MAE. Its use is across series. Chapter 6 needs it to compare clients of very different sizes, and the total sits beside them on the same footing.
On the standard cutoffs the direct total beats seasonal naive on the total, but by a smaller margin than the bottom-up total does, as the MASE column of the table shows.
A method wins on the decision windows when its error is lower there, and the standard cutoffs then either confirm that or contradict it. For the total, the standard cutoffs confirm the choice, since bottom-up is lower on both window sets. That agreement is why the chapter recommends bottom-up for the total, with some confidence. Agreement counts only when the two sets are separate, and they are. The four decision windows all fall before Dec 25, 2014, the first day of the held-out week, and the standard cutoffs are the last three days of that week. No decision reads a standard cutoff.
The identifier is where the two window sets disagree. On the decision windows, the bottom-up total without the identifier has an MAE of 1383.29 kWh, against 1267.47 kWh with it, so the identifier lowers the total's error there, as the per-client MASE in Chapter 6 does on the same windows. On the standard cutoffs the plain total has an MAE of 2837.66 kWh, and the total with the identifier has 2985.88 kWh. The standard cutoffs therefore favour the plain total. The book reports that and does not act on it, because Chapter 6 kept the identifier on per-client MASE, and the decision windows are the ones that choose. A supplier that doubts four decision windows should add decision windows before Dec 25, 2014, and decide again on those, not on the standard cutoffs.
Working rule: Choose a method on the decision windows, by the measure you will report. Report the same measure on the standard cutoffs beside seasonal naive, with the scored hours and the scale. When two window sets disagree, report both, say how far apart they are, and do not pick the one that reads better.
按份额拆分总量
自上而下的拆分以直接预测的总量为起点,再给每个客户分配其中的一份。客户的份额,等于它在自身历史(即截止点之前的 1,344 小时)内的读数,除以总量在同一时段内的读数。某个客户在某一小时的自上而下预测,等于直接总量在该小时的预测值乘以它的份额。一个客户若在过去 8 周内提供了总量的十分之一,就预期它在第二天也占总量的十分之一。
这 8 周是一种选择,而不是调优得到的值。它是本章其他每个模型所读取的历史长度,因此拆分使用的记忆长度与各客户模型相同。更短的窗口能更快跟上客户份额的变化,但噪声也更大。本章没有衡量这一取舍。供应商若想了解,应在决策窗口上测试。
这种拆分的弱点在于一天的形状。它让每个客户都采用总量的日内曲线,因此,若某个客户的峰值出现在不同的时刻,那么无论总量预测有多准,它在每个小时得到的曲线都是错的。在这些客户上,即使手中有真实的总量,拆分仍然落败。本章称为“先知检验”的一项检查,把份额应用到实际总量上(这是任何预测都无法得知的),其每客户平均 MAE 为 171.80 kWh。这只是一个参照,而不是一种方法:它表示总量完全准确时拆分所具有的误差。自下而上的预测需要逐个预测客户,其每客户平均 MAE 为 122.81 kWh。
份额也不均匀。在第一个截止点,即 2014 年 12 月 29 日,最大客户占总量的份额为 0.56。
定义 MinT 的工作论文引用 Hyndman 等人(2011)指出,即使基础预测无偏,自上而下的拆分也会使各层级的协调预测产生偏差(Wickramasuriya, Athanasopoulos and Hyndman, 2017)。本章不重新推导这一结果。本章在这些客户上衡量拆分的表现,先知检验则为拆分自身的误差提供了参照。
在相同窗口上,逐个客户地把拆分与自下而上进行比较,可以看出拆分是否对某个单独的客户占优,这是均值无法显示的。第二个示例完成这项比较,并对份额运行泄漏检验。它先在决策窗口上做出选择,再报告标准截止点的结果。
1"""Splits the direct total forecast into client forecasts, each client taking its share of the history before each cutoff2(top-down), and compares them with bottom-up on the same windows. The point rests on the mean per-client MASE and MAE lines;3the last line is a leak check that no share reads a reading after its cutoff."""4import pandas as pd56from lib.electricity import load7from lib.panel import ALL30, DECISION_CUTOFFS, check_decision_hours8from lib.settings import EVAL_CUTOFFS, show9from lib.totals import SPLIT_METHODS, client_mae, oracle_split_mae, shares, split_checks, split_scored1011raw = load(ALL30)12dec, cut = pd.to_datetime(DECISION_CUTOFFS), pd.to_datetime(EVAL_CUTOFFS)1314# the third value, the hours the top-down clients don't add up to the direct total (none, by construction), is unused15dec_scored, dec_per, _ = split_scored(raw, dec)16show("decision holiday hours", check_decision_hours(dec_scored))17show("mean per-client MASE bottom-up, decision windows", dec_per["bottom-up"].mean())18show("mean per-client MASE top-down, decision windows", dec_per["top-down"].mean())19show("chosen client method", dec_per.mean().idxmin())2021# the third value is discarded, as above22scored, per_client, _ = split_scored(raw, cut)23show("scored hours", len(scored))24mae = pd.DataFrame({m: client_mae(scored, m) for m in SPLIT_METHODS})25for model in SPLIT_METHODS:26 show(f"mean per-client MAE {model}", mae[model].mean())27for model in SPLIT_METHODS:28 show(f"mean per-client MASE {model}", per_client[model].mean())29show("clients where top-down has the lower MAE", int((mae["top-down"] < mae["bottom-up"]).sum()))30# the split applied to the actual total: a reference, since no forecast can know the total in advance31show("mean per-client MAE with the true total split by share", oracle_split_mae(raw, cut))32# the first standard cutoff, Dec 29, 2014; its shares read only the history before it33# shares read the 1,344 hours (8 weeks) before the cutoff34show("largest client share of the total, first cutoff", shares(raw, cut[0]).max())35# each cutoff's readings from the cutoff on replaced by zero, then by a very large value36for label, value in split_checks(raw, cut).items():37 show(label, value)
python total-split-by-share.pydecision holiday hours: 0
mean per-client MASE bottom-up, decision windows: 0.75
mean per-client MASE top-down, decision windows: 2.37
chosen client method: bottom-up
scored hours: 2160
mean per-client MAE bottom-up: 122.81
mean per-client MAE top-down: 218.95
mean per-client MASE bottom-up: 0.91
mean per-client MASE top-down: 2.59
clients where top-down has the lower MAE: 0
mean per-client MAE with the true total split by share: 171.80
largest client share of the total, first cutoff: 0.56
shares changed after poisoning readings from their cutoff: 0
在决策窗口上,自下而上对这些客户占优,其每客户平均 MASE 为 0.75,而自上而下为 2.37,因此选择自下而上。
在标准截止点上,以千瓦时计的误差,拆分同样更差。在 2160 个客户小时上,其每客户平均 MAE 为 218.95 kWh,自下而上为 122.81 kWh;在三十个客户中,自上而下的 MAE 更低的有 0 个。
自上而下的每客户平均 MASE 为 2.59,自下而上为 0.91。第 6 章对相同预测的汇总 MAE 为 122.81 kWh,与自下而上的均值 122.81 kWh 相同。这并非巧合,因为每个客户都有相同的 72 个评分小时,所以各客户误差的均值等于汇总误差。
没有任何份额发生变动。份额只能读取其截止点之前的历史,因此泄漏检验把从每个截止点起的所有读数改动,一次改为零,一次改为极大值,然后重新计算份额。在六次比较(三个截止点乘以两个值)中,有 0 次改变了份额。若有任何份额读取了截止点之后的读数,那个极大值就会进入其中。份额之和为 1,而且按构造,自上而下的各客户之和在每个小时都等于直接总量。这样的恒等式不可能失败,所以本章只计入泄漏检验,它是这里唯一可能失败的测试。
工作准则: 仅在作为基线,或各客户的日内曲线相近时,才按份额拆分总量。每个份额都由其截止点之前的历史计算,检查截止点之后的读数改变时没有份额发生变动,并在相同的尺度上将每个客户与自下而上进行比较。只有当拆分在决策窗口上对某个客户获胜时,才对该客户保留这种拆分。
这部分尚未翻译,因此以英文显示。
What goes wrong in production
Most failures in this chapter are silent.
The first is a quietly short total. If one client drops out of the sum, the total is smaller than the demand, and its scores still look reasonable. The bottom-up total in this book raises an error when an hour has fewer than thirty client forecasts. The start rule refuses a client with too little history instead of skipping it, as Chapter 6 explains. In production, a run that builds fewer forecasts than clients should stop and name the missing client.
The second is the raw sum. The October repeat hour holds the energy of two (Chapter 3), so a total built from raw readings can count that hour at roughly twice its neighbours. The result is a demand spike that is not there. The book's total masks the hour instead, and the check in the first example excludes the clock-change hours for the same reason.
The third is a split that reads the future. A split whose shares use the window's own readings scores better in a backtest than it will in production. The poisoning check is the test. A share must not move when readings after its cutoff change. A production run should keep both checks, the share check in the second example and the scale check in the first, as tests that fail loudly.
The fourth is a decision and a report that disagree. The identifier lowers the total's error on the decision windows and raises it on the standard cutoffs. A monitor that watches only one set of windows will miss the other's failure. On every refit, log the total's error with and without the identifier on the same windows, beside the per-client MASE that Chapter 6 uses to decide.
The fifth is a share that goes stale. A share is a fact about the past 8 weeks, so when a client's habits change, its share lags the change for as long as the window is long. A top-down forecast of that client is then wrong in a steady direction, not at random, and the error does not show in the total at all, because the shares still add to one. A monitor should therefore watch each client's share over time, not only the total's error. The per-client MASE in the second example is the measure that sees it.
The sixth is a scale that moves with the window. The total's MASE scale is read once, from the history before the first scored cutoff. A scale refreshed for each window reads that window's own readings, and every score on the total then changes for reasons that have nothing to do with the forecast. The first example checks, for each scored cutoff, that the scale for that window does not move when readings from the cutoff on are replaced. No scale moves: 0 of the six comparisons (three cutoffs by two values) changes it.
Working rule: In production, check the total against the sum of its readings on every refit, stop when a client is missing from a total, and run the poisoning check on each share and on the scale for each window. Log the total's error with and without the identifier on the same windows. When the windows disagree, report both and do not choose the one that flatters the model.
本章做出的决定
- 总量是
ALL30的逐小时加总。 加总之前,每个客户先按起始规则截取;若某个客户在某一小时的读数被作为时钟调整小时屏蔽,则该小时缺失。加总结果不随起始规则变化,第一个示例中的检验可以说明这一点。 - 每个预测小时都有取值,评分则拒绝已屏蔽的小时。 输出网格在时钟调整小时处也是完整的,缺失的读数绝不按零计分。
- 两种总量都在 pandas 中手工构建。 层级只有一层,因此每条路径只是一次加总或一次拆分。文中提到了
hierarchicalforecast和 MinT,但都没有使用。 - 总量采用自下而上的方式预测。 在四个决策窗口和标准截止点上,它的 MAE 都更低。直接预测的总量列在旁边作为对照。
- 直接预测总量的目标不做缩放。 在决策窗口上,它的 MAE 更低,因此与客户模型不同,直接模型不对其目标做缩放。第一个示例会打印这两种设置。
- 标识符保留在自下而上的总量中,与第 6 章对客户的决定一致。 它在标准截止点上给总量带来的代价已在前文报告,并未予以撤销。
- 拆分方法不是客户所用的方法。 在决策窗口上,自下而上的每客户 MASE 更低;在这些客户上,即使使用真实总量,拆分的结果也更差。
- 份额取自每个截止点之前的 1,344 小时,与客户使用的历史相同。 污染检验表明,没有任何份额读取了较晚的读数。
- 总量的 MASE 尺度沿用第 2 章的规则,并应用于总量: 取首个被评分截止点之前所有读数的季节性朴素误差,屏蔽时钟调整小时,并先对每个客户应用起始规则。
- 窗口沿用第 6 章的窗口。 决策窗口与标准截止点是相同的日期,因此两章的数字可以逐行比较。
- 第 8 章接收点预测: 每个客户和总量的自下而上预测,并以直接预测的总量作为备选。总量的区间无法由各客户的区间构建。
本章,在本版次中
版次 2026.11.11示例于 2026年11月20日 通过本章 2个示例 个示例中有 2 个通过
译自英文版图书,版次 2026.11.11。