Skip to content

Separate input and grid data from solver #68

@mknaranja

Description

@mknaranja

In a future adaptation, the GMGPolar solver should only handle solver information and we should think of better separation of responsibilities.

GMGPolar seems to be a very big class, it would be clearer if it just takes care of the solving part. Someting like gmgpolar.solve(lhs, rhs, tol, maxIt). You could also consider a templated class to avoid several switch statements and code repetition inside the class : GMGPolar<SmootherOpLevel0, RestrictionOpLevel0, ProlongationOpLevel0, SmootherOp, RestrictionOp, ProlongationOp, MGCycle> ( just an idea )

Originally posted by @ds-aakash in #65 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions