Set a safe default number of iterations for AMR grid generation#1611
Set a safe default number of iterations for AMR grid generation#1611BenWibking merged 2 commits intodevelopmentfrom
Conversation
Sets a safe default for the number of iterations to perform when tagging and re-gridding AMR levels. See AMReX-Codes/amrex#4903.
Summary of ChangesHello @BenWibking, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the Adaptive Mesh Refinement (AMR) grid generation process by introducing a robust default for the number of iterations. This ensures that the system performs an adequate number of refinement steps, especially critical for complex simulations involving deeply nested AMR levels, thereby preventing potential issues arising from insufficient iteration counts. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
There was a problem hiding this comment.
Code Review
This pull request introduces a sensible default for the number of AMR grid generation iterations, which is important for correctness when using deeply nested grids. The implementation is straightforward. I've found one issue with the use of amrex::ParmParse where the namespace prefix is incorrectly included in parameter names, which would prevent the feature from working as intended. My suggestion corrects this.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d7cc596beb
ℹ️ 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 "@codex address that feedback".
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|



Description
Sets a safe default for the number of iterations to perform when tagging and re-gridding AMR levels.
This is an example of why this is required: https://github.com/BenWibking/amrex-gridgen-test
Related issues
See AMReX-Codes/amrex#4903.
Checklist
Before this pull request can be reviewed, all of these tasks should be completed. Denote completed tasks with an
xinside the square brackets[ ]in the Markdown source below:/azp run.