Skip to content

Feasibility of solving problems with locally field-aligned non-conforming mesh (and more generally what is required for a solver). #20

@asnodin

Description

@asnodin

Not sure if a more general issue is needed about what mesh information a solver requires and what type of input it understands (we have so far been passing meshes round as opaque objects without thinking about this too much). I've worked out requirements for most cases with Trixi.

It would be nice to find out if there is any framework that could rapidly deal with the locally field-aligned mesh. Reading the overview of most frameworks one might be convinced that it will just work, since they can do curvilinear, unstructured, hybrid elements, [h|r]-nonconforming, parallel etc. It seems to me that the connectivity information is not supported in most or all cases.

Is there a proof-of-concept that one can study and compare requirements with meshing frameworks and solver?

Discuss.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions