`包裹,长文用`
`/`
`划分小节。 3. 列表内容用`
- `,引用用`
`,代码用`
`,重要句子可用``。
4. 保留原文所有信息,不得增删改内容。
5. 不要输出``/``/``等文档级标签。
先看看正文内容。它讲的是数据驱动的天气预报,提到了一个叫做ProtoCast的方法,包含三点具体设计,最后是实验结果和项目页面。
这段文本看起来是一个整体的摘要,没有明显的长文分节。我可以考虑加一个小标题来引入,比如`ProtoCast: 可解释的局部天气预测
`?但等等,规则4说“不得增删改内容”,如果我添加一个原文没有的标题,是不是算增加了内容?为了安全起见,最好不添加原文没有的标题。不过规则2说“长文用/
划分小节”,这段文字长度中等,可以不强制划分小节,或者把列表部分单独作为一个小节?但加小标题还是会引入新文字。
仔细看,原文第一句到“variable groups.”是一个段落,讲的是背景和动机。“To deal with this problem...”到“...before prediction.”是方法的整体描述,然后“Each group's correction...”是补充。“(1)(2)(3)”是具体的三点设计。最后是实验和结论,还有项目链接。
让我重新划分段落。原文是一整块,我需要根据语义拆分成自然段落。
原文:
"Data-driven weather forecasting requires distinguishing local states and their temporal evolution. However, learned patterns remain implicit in neural forecasters, making their influence difficult to interpret. Failing to distinguish local evolution can lead to similar forecasts for locations that develop differently, increasing prediction error. This motivates explicit references for distinguishing and interpreting local patterns."
这是第一段,讲背景和动机。
"Prototypes provide explicit pattern references, but sample- or task-level conditioning leaves open how to adapt to distinct locations and variable groups. To deal with this problem, we design ProtoCast, which uses group-specific prototype banks to adapt local features while accounting for cross-variable dependencies."
这是第二段,介绍ProtoCast的提出。
"Specifically, (1) we combine each group's historical features and temporal change with forecast context from cross-variable attention for evolution-aware prototype matching. (2) Sparse mixtures of prototype-specific low-rank operators tailor corrections to each group and location. A gated attention block then exchanges the corrected features across groups before prediction. Each group's correction decomposes into explicit prototype contributions before this fusion. (3) We jointly train the forecasting network and operators from scratch and refit each group's prototypes before every training epoch. Slot tracking preserves prototype-operator associations, making each prototype's contribution to local corrections more interpretable."
这是第三段,详细介绍三个具体设计。这里有一个列表(1)(2)(3),我可以把它们用`- `呈现,但原文中它们是在段落中连续描述的,而且(2)后面还有一句“A gated attention block...”,(3)后面也有补充。如果拆成列表,可能破坏原文的连贯性。不过规则3说“列表内容用
- ”,这里明确有编号的三点,可以视为列表。但要注意(2)和(3)后面都有额外的句子,如果把它们放进`
- `,可能不太合适,因为那些句子不是列表项的直接内容。 让我想想:原文是"Specifically, (1) ... (2) ... A gated attention block ... (3) ... Slot tracking ..."。如果我用列表,可以这样: - (1) we combine ... - (2) Sparse mixtures ... before prediction. Each group's correction ... fusion. - (3) We jointly train ... more interpretable. 这样每个列表项包含了该点的所有相关描述,逻辑上是合理的,也没有增删改内容。而且规则允许列表内容用`
- `。 那么整体结构: - 第一段:背景动机,用`
` - 第二段:ProtoCast提出,用`
`,其中“ProtoCast”和“group-specific prototype banks”等可以用``强调 - 第三段:“Specifically”作为引导,然后一个`
`列表包含三个`
- ` - 第四段:实验结果和结论,用`
`,项目链接单独处理 项目链接“Project page: https://...”可以放在最后一段,或者单独成段。原文是“This work advances... Project page: ...”,可能在同一段落。我可以保留在同一段落,但链接最好用``?不过规则没有明确要求链接标签,只说保留所有信息。为了简洁,我可以直接放在`
`里,或者用``。用户要求语义化,用``更合适。但链接是纯文本,用``也没问题。不过要小心,规则说“不得增删改内容”,用``只是加标签,内容不变。我觉得可以用``。 现在考虑是否需要用`
`/`
`。这段文字不算很长,原文也没有分节标题,我倾向于不添加额外的标题,以避免增加原文没有的内容。规则2说“长文用
/
划分小节”,这段不算长文,可以不用。 现在具体写HTML: 第一段:
Data-driven weather forecasting requires distinguishing local states and their temporal evolution. However, learned patterns remain implicit in neural forecasters, making their influence difficult to interpret. Failing to distinguish local evolution can lead to similar forecasts for locations that develop differently, increasing prediction error. This motivates explicit references for distinguishing and interpreting local patterns.
第二段:
Prototypes provide explicit pattern references, but sample- or task-level conditioning leaves open how to adapt to distinct locations and variable groups. To deal with this problem, we design ProtoCast, which uses group-specific prototype banks to adapt local features while accounting for cross-variable dependencies.
第三段,列表部分:
Specifically,
- (1) We combine each group's historical features and temporal change with forecast context from cross-variable attention for evolution-aware prototype matching.
- (2) Sparse mixtures of prototype-specific low-rank operators tailor corrections to each group and location. A gated attention block then exchanges the corrected features across groups before prediction. Each group's correction decomposes into explicit prototype contributions before this fusion.
- (3) We jointly train the forecasting network and operators from scratch and refit each group's prototypes before every training epoch. Slot tracking preserves prototype-operator associations, making each prototype's contribution to local corrections more interpretable.
注意:原文中(1)(2)(3)后面是小写字母开头,我在HTML中可以保持原样,或者把首字母大写?规则说不得增删改内容,所以应该保持原文的大小写。原文是"(1) we combine...",我保留"we"。 第四段:
Experiments on GlobalForecast and TyphoonTracking show improved forecasting accuracy, while prototype deletion links local feature contributions to changes in prediction error. This work advances the development of more accurate and interpretable data-driven weather forecasting models. Project page: https://zhixuanli.github.io/projects/li2026protocast
检查一下是否所有信息都保留了。原文最后是“Project page: https://zhixuanli.github.io/projects/li2026protocast”,我加了``标签,内容没变。 关于“重要句子可用”,我选择了一些关键术语和结论,这没问题。 现在,是否需要把“Specifically”单独成段?原文是“To deal with this problem, we design ProtoCast, which uses group-specific prototype banks to adapt local features while accounting for cross-variable dependencies. Specifically, (1) ...”,所以“Specifically
`,代码用``,重要句子可用``。 4. 保留原文所有信息,不得增删改内容。 5. 不要输出``/``/``等文档级标签。 先看看正文内容。它讲的是数据驱动的天气预报,提到了一个叫做ProtoCast的方法,包含三点具体设计,最后是实验结果和项目页面。 这段文本看起来是一个整体的摘要,没有明显的长文分节。我可以考虑加一个小标题来引入,比如`ProtoCast: 可解释的局部天气预测
`?但等等,规则4说“不得增删改内容”,如果我添加一个原文没有的标题,是不是算增加了内容?为了安全起见,最好不添加原文没有的标题。不过规则2说“长文用/
划分小节”,这段文字长度中等,可以不强制划分小节,或者把列表部分单独作为一个小节?但加小标题还是会引入新文字。 仔细看,原文第一句到“variable groups.”是一个段落,讲的是背景和动机。“To deal with this problem...”到“...before prediction.”是方法的整体描述,然后“Each group's correction...”是补充。“(1)(2)(3)”是具体的三点设计。最后是实验和结论,还有项目链接。 让我重新划分段落。原文是一整块,我需要根据语义拆分成自然段落。 原文: "Data-driven weather forecasting requires distinguishing local states and their temporal evolution. However, learned patterns remain implicit in neural forecasters, making their influence difficult to interpret. Failing to distinguish local evolution can lead to similar forecasts for locations that develop differently, increasing prediction error. This motivates explicit references for distinguishing and interpreting local patterns." 这是第一段,讲背景和动机。 "Prototypes provide explicit pattern references, but sample- or task-level conditioning leaves open how to adapt to distinct locations and variable groups. To deal with this problem, we design ProtoCast, which uses group-specific prototype banks to adapt local features while accounting for cross-variable dependencies." 这是第二段,介绍ProtoCast的提出。 "Specifically, (1) we combine each group's historical features and temporal change with forecast context from cross-variable attention for evolution-aware prototype matching. (2) Sparse mixtures of prototype-specific low-rank operators tailor corrections to each group and location. A gated attention block then exchanges the corrected features across groups before prediction. Each group's correction decomposes into explicit prototype contributions before this fusion. (3) We jointly train the forecasting network and operators from scratch and refit each group's prototypes before every training epoch. Slot tracking preserves prototype-operator associations, making each prototype's contribution to local corrections more interpretable." 这是第三段,详细介绍三个具体设计。这里有一个列表(1)(2)(3),我可以把它们用`
- `呈现,但原文中它们是在段落中连续描述的,而且(2)后面还有一句“A gated attention block...”,(3)后面也有补充。如果拆成列表,可能破坏原文的连贯性。不过规则3说“列表内容用
- ”,这里明确有编号的三点,可以视为列表。但要注意(2)和(3)后面都有额外的句子,如果把它们放进`
- `,可能不太合适,因为那些句子不是列表项的直接内容。 让我想想:原文是"Specifically, (1) ... (2) ... A gated attention block ... (3) ... Slot tracking ..."。如果我用列表,可以这样: - (1) we combine ... - (2) Sparse mixtures ... before prediction. Each group's correction ... fusion. - (3) We jointly train ... more interpretable. 这样每个列表项包含了该点的所有相关描述,逻辑上是合理的,也没有增删改内容。而且规则允许列表内容用`
- `。 那么整体结构: - 第一段:背景动机,用`
` - 第二段:ProtoCast提出,用`
`,其中“ProtoCast”和“group-specific prototype banks”等可以用``强调 - 第三段:“Specifically”作为引导,然后一个`
`列表包含三个`
- ` - 第四段:实验结果和结论,用`
`,项目链接单独处理 项目链接“Project page: https://...”可以放在最后一段,或者单独成段。原文是“This work advances... Project page: ...”,可能在同一段落。我可以保留在同一段落,但链接最好用``?不过规则没有明确要求链接标签,只说保留所有信息。为了简洁,我可以直接放在`
`里,或者用``。用户要求语义化,用``更合适。但链接是纯文本,用``也没问题。不过要小心,规则说“不得增删改内容”,用``只是加标签,内容不变。我觉得可以用``。 现在考虑是否需要用`
`/`
`。这段文字不算很长,原文也没有分节标题,我倾向于不添加额外的标题,以避免增加原文没有的内容。规则2说“长文用
/
划分小节”,这段不算长文,可以不用。 现在具体写HTML: 第一段:
Data-driven weather forecasting requires distinguishing local states and their temporal evolution. However, learned patterns remain implicit in neural forecasters, making their influence difficult to interpret. Failing to distinguish local evolution can lead to similar forecasts for locations that develop differently, increasing prediction error. This motivates explicit references for distinguishing and interpreting local patterns.
第二段:Prototypes provide explicit pattern references, but sample- or task-level conditioning leaves open how to adapt to distinct locations and variable groups. To deal with this problem, we design ProtoCast, which uses group-specific prototype banks to adapt local features while accounting for cross-variable dependencies.
第三段,列表部分:Specifically,
注意:原文中(1)(2)(3)后面是小写字母开头,我在HTML中可以保持原样,或者把首字母大写?规则说不得增删改内容,所以应该保持原文的大小写。原文是"(1) we combine...",我保留"we"。 第四段:
- (1) We combine each group's historical features and temporal change with forecast context from cross-variable attention for evolution-aware prototype matching.
- (2) Sparse mixtures of prototype-specific low-rank operators tailor corrections to each group and location. A gated attention block then exchanges the corrected features across groups before prediction. Each group's correction decomposes into explicit prototype contributions before this fusion.
- (3) We jointly train the forecasting network and operators from scratch and refit each group's prototypes before every training epoch. Slot tracking preserves prototype-operator associations, making each prototype's contribution to local corrections more interpretable.
Experiments on GlobalForecast and TyphoonTracking show improved forecasting accuracy, while prototype deletion links local feature contributions to changes in prediction error. This work advances the development of more accurate and interpretable data-driven weather forecasting models. Project page: https://zhixuanli.github.io/projects/li2026protocast
检查一下是否所有信息都保留了。原文最后是“Project page: https://zhixuanli.github.io/projects/li2026protocast”,我加了``标签,内容没变。 关于“重要句子可用”,我选择了一些关键术语和结论,这没问题。 现在,是否需要把“Specifically”单独成段?原文是“To deal with this problem, we design ProtoCast, which uses group-specific prototype banks to adapt local features while accounting for cross-variable dependencies. Specifically, (1) ...”,所以“Specifically