Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #5079

Closed
Open
Created May 03, 2019 by James Willenbring@jmwilleMaintainer

Piro: 'Rythmos' vs 'Rythmos Solver'

Created by: bartgol

Question

@trilinos/piro @trilinos/rythmos

Can someone explain me the difference? It seems the two syntaxes are almost equivalent (mutatis mutandis), however, during some refactor in Albany, I came upon an example in which using Rythmos Solver causes an exception to be thrown inside some Thyra model evaluator that Rythmos creates, with a message sayng that both W and W_op are present, and that case is not supported. Switching the input file to Rythmos syntax works. The details are the same (integrator type, stepper, nonlinear solver (NOX)...).

So to make the question short: is there a reason why one should use the 'Rythmos' list syntax instead of 'Rythmos Solver' inside Piro (or viceversa)?

Assignee
Assign to
Time tracking