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

オープン
#1,929 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 6 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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時間
マージ済み PR(30日)
42

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

BlueQuartzSoftware/simplnx のほかの issue

BlueQuartzSoftware/simplnx の issue をすべて見る

似ている issue

C++ の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。