Skip to content

Ignoring user-defined solverType in the FSI module #363

@MakisH

Description

@MakisH

At least in the FSI module, defining a custom solver type is ignored, at least when in a known type can be deduced.

To reproduce, add a custom solver type in the tutorial quickstart/fluid-openfoam/system/preciceDict:

FSI
{
  rho rho [1 -3 0 0 0 0 0] 1000;
  solverType basic;
}

I encountered this while checking the error handling in the constructor of ForceBase. The solver type is determined in FSI/FSI.C (functions readConfig and configure). Compare with CHT/CHT.C.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugUnexpected problems (crashes, numerical issues, etc)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions