Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • Nektar Nektar
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 73
    • Merge requests 73
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Nektar
  • NektarNektar
  • Merge requests
  • !1385

Draft: Disable use of SetRhsMagnitude for iterative static cond.

  • Review changes

  • Download
  • Patches
  • Plain diff
Open Chris Cantwell requested to merge neptune/nektar-preconditioners:fix/disable-rhs-mag-staticcond into master Aug 23, 2022
  • Overview 1
  • Commits 1
  • Pipelines 0
  • Changes 1

Issue/feature addressed

When using IterativeStaticCond with a highly anisotropic elliptic solve, the iterative solver would no converge. This behaviour was inconsistent with other solvers (e.g. IterativeFull). The SetRhsMagnitude function appears to be the culprit.

Proposed solution

Disable SetRhsMagnitude for the IterativeStaticCond solver.

Implementation

Currently just commented out.

Tests

Notes

None

Checklist

  • Functions and classes, or changes to them, are documented.
  • User guide/documentation is updated.
  • Changelog is updated.
  • Suitable tests added for new functionality.
  • Contributed code is correctly formatted. (See the contributing guidelines).
  • License added to any new files.
  • No extraneous files have been added (e.g. compiler output or test data files).

Warning

On the 19.07 the code formatting (code style) was standardised using clang-format, over the whole Nektar++ code. This means changes in your branch will conflict with formatting changes on the master branch. To resolve these conflicts , see #295

Closes #123 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: fix/disable-rhs-mag-staticcond