Skip to content

Priority queue of changes #2

Description

@tom-dq

Should be able to interleave the element additions and removals such that the most advantageous to the global objective function get priority. This will be important if we want to use the "dirty patch" feature.

I guess this will involve:

  • Make a class to track the mesh and changes to it (and makes sure no connectivity or dirty patch stuff is violated).
  • Having a lightweight "changes" datatype which is passed through the objective function.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions