Skip to content

Conversation

lynnmunday
Copy link
Contributor

ref #31614

@lynnmunday lynnmunday force-pushed the xfem3Dcutter branch 2 times, most recently from 300d96c to 5c64b34 Compare September 26, 2025 18:44
@moosebuild
Copy link
Contributor

moosebuild commented Sep 26, 2025

Job Documentation, step Docs: sync website on 9c4f14b wanted to post the following:

View the site here

This comment will be updated on new commits.

lynnmunday added a commit to lynnmunday/moose that referenced this pull request Sep 26, 2025
…rObject read fatigue values from this reporter. I think stress corrosion cracking can be created by parsed Reporter.

ref idaholab#31615
lynnmunday added a commit to lynnmunday/moose that referenced this pull request Sep 26, 2025
…rObject read fatigue values from this reporter. I think stress corrosion cracking can be created by parsed Reporter.

ref idaholab#31615
lynnmunday added a commit to lynnmunday/moose that referenced this pull request Sep 26, 2025
…rObject read fatigue values from this reporter. I think stress corrosion cracking can be created by parsed Reporter.

ref idaholab#31615
lynnmunday added a commit to lynnmunday/moose that referenced this pull request Sep 26, 2025
…rObject read fatigue values from this reporter. I think stress corrosion cracking can be created by parsed Reporter.

ref idaholab#31615
lynnmunday added a commit to lynnmunday/moose that referenced this pull request Oct 1, 2025
…rObject read fatigue values from this reporter. I think stress corrosion cracking can be created by parsed Reporter.

ref idaholab#31615
@moosebuild
Copy link
Contributor

Job Precheck, step Clang format on a70c9b5 wanted to post the following:

Your code requires style changes.

A patch was auto generated and copied here
You can directly apply the patch by running, in the top level of your repository:

curl -s https://mooseframework.inl.gov/docs/PRs/31615/clang_format/style.patch | git apply -v

Alternatively, with your repository up to date and in the top level of your repository:

git clang-format 23927d0dc7a66eccf59bbb36953ba4c8ff321a01

lynnmunday added a commit to lynnmunday/moose that referenced this pull request Oct 2, 2025
…rObject read fatigue values from this reporter. I think stress corrosion cracking can be created by parsed Reporter.

ref idaholab#31615
@moosebuild
Copy link
Contributor

moosebuild commented Oct 2, 2025

Job Coverage, step Generate coverage on 9c4f14b wanted to post the following:

Framework coverage

236997 #31615 9c4f14
Total Total +/- New
Rate 85.93% 85.93% -0.00% -
Hits 122919 122918 -1 0
Misses 20122 20123 +1 0

Diff coverage report

Full coverage report

Modules coverage

Xfem

236997 #31615 9c4f14
Total Total +/- New
Rate 82.56% 82.62% +0.07% 100.00%
Hits 7057 7133 +76 174
Misses 1491 1500 +9 0

Diff coverage report

Full coverage report

Full coverage reports

Reports

This comment will be updated on new commits.

@lindsayad
Copy link
Member

#31621 is a prereq for this. @lynnmunday please bring out of draft once that PR is merged

@lindsayad lindsayad marked this pull request as draft October 2, 2025 21:08
@lindsayad lindsayad marked this pull request as ready for review October 3, 2025 16:01
…as the 2D mesh.

Also adding verbosity to some error messages.
Cleaning up some other stuff not used.
Getting vectorpostprocessors in constructor and adding a param to get them by name.
@lynnmunday lynnmunday force-pushed the xfem3Dcutter branch 2 times, most recently from 49f5e08 to e210254 Compare October 6, 2025 19:06
@moosebuild
Copy link
Contributor

Job Python 3.13 (Apptainer) on c4a6907 : invalidated by @lynnmunday

@moosebuild
Copy link
Contributor

Job CUDA GPU on c4a6907 : invalidated by @lynnmunday

@moosebuild
Copy link
Contributor

Job Python 3.13 (Apptainer) on c4a6907 : invalidated by @lynnmunday

1 similar comment
@moosebuild
Copy link
Contributor

Job Python 3.13 (Apptainer) on c4a6907 : invalidated by @lynnmunday

@lynnmunday
Copy link
Contributor Author

@bwspenc Will you review? The broken test is not from this.

@lynnmunday
Copy link
Contributor Author

@codex

@lynnmunday
Copy link
Contributor Author

@codex
Are you reviewing my code?

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting

Comment on lines +82 to +83
Real max_growth_rate = *std::max_element(growth_rate.begin(), growth_rate.end());
_corrosion_time_step = _max_growth_size / max_growth_rate;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Guard against zero growth rate in SCC reporter

When every entry in growth_rate stays at zero (for example when the user supplies growth_rate_low = growth_rate_high = 0 or there are no active crack-front nodes), max_growth_rate evaluates to 0 and _corrosion_time_step divides by zero. This produces inf/NaN values in _growth_increment, which will be consumed by the mesh cutter and can corrupt node coordinates. Consider short‑circuiting when the maximum rate is non‑positive and leaving the increments at zero instead of computing a ratio.

Useful? React with 👍 / 👎.

Comment on lines 62 to 67
Real _max_k = *std::max_element(effective_k.begin(), effective_k.end());
_dn = _max_growth_size / (_paris_law_c * std::pow(_max_k, _paris_law_m));

for (std::size_t i = 0; i < _ki_vpp.size(); ++i)
if (index[i] != -1)
_growth_increment[i] = _max_growth_size * std::pow(effective_k[i] / _max_k, _paris_law_m);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge ParisLaw reports NaNs when fracture integrals are zero

If all KI/KII values are zero for a step, effective_k remains zeros so _max_k becomes 0. The subsequent division _max_growth_size / (_paris_law_c * pow(_max_k, _paris_law_m)) and normalization of effective_k[i] / _max_k therefore divide by zero, yielding infinite or NaN cycle counts and growth increments. This can occur on initial timesteps before loads are applied. A guard for _max_k <= 0 that returns zero growth (and zero cycles) would avoid generating invalid numbers.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants