ENH: Review repeated warnings in out-of-core transfer loops

未关闭
#1,929 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 6 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
cpp

调研方向

Start by reviewing the source locations for the listed out-of-core transfer loops and identify which supported storage providers can emit repeated warnings. Reproduce representative cases, then compare runtime and diagnostic memory while checking that terminal errors and cancellation are preserved. The scope and warning-reporting policy are open decisions, so done requires an agreed policy and tests for the resulting behavior.

由索引模型根据 Issue 内容生成。

描述

enhancement Out-of-Core

Summary

Investigate how repeated storage warnings are retained by out-of-core transfer loops. This work is deferred from simplnx #1764 to a separate branch.

Source review found loops that merge warnings from each block or page. A storage provider that returns a warning for every transfer could make the retained warning list grow with the amount of work; repeated merging could also add time. No such repeated warnings from the normal HDF5 provider, resulting slowdown, or memory exhaustion has been observed in this investigation.

The agreed payload budget excludes Result, warning and error objects, and their message strings. This is therefore a possible diagnostic-memory and performance concern, not a demonstrated violation of that payload budget. Winding-transfer warnings have a separately approved limit on the current branch; that choice does not establish a policy for every other algorithm.

Examples identified during the review include normal and vertex-gather calculations, dihedral angle, smoothing, face orientation and misorientation, shared-feature-face metadata, centroids, triple-line extraction, and Avizo coordinate writing. This is not an exhaustive list. Determine which supported providers can produce repeated warnings and reproduce representative cases before selecting a warning-retention policy. Compare runtime and diagnostic memory, preserve terminal errors and cancellation, and test any proposed reporting behavior. The scope and reporting policy remain open decisions.

主要语言
C++
星标
18
派生
15
平均合并
4 天 23 小时
30 天内合并 PR
42

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

BlueQuartzSoftware/simplnx 的其他 Issue

查看 BlueQuartzSoftware/simplnx 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。