Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support remap for adaptive refinement with incrementally appended source/target sites #52

Open
kuberry opened this issue Jun 4, 2019 · 2 comments
Labels
idea Idea for future research/implementation TOOLKIT

Comments

@kuberry
Copy link
Collaborator

kuberry commented Jun 4, 2019

  • Ability to add a single or set of source sites, using these sites with a neighbor search among target sites to find which target sites need their neighbor list updated (then update the neighbor lists).
  • Add ability to recompute solution for all target sites affected by the source site appending.
  • Similar functionality for dropping source sites, equivalent to coarsening.
@kuberry kuberry added idea Idea for future research/implementation TOOLKIT labels Jun 4, 2019
@kuberry
Copy link
Collaborator Author

kuberry commented Jun 5, 2019

  • Also consider a reorder function that takes a map that is the size of the current target sites. It can then migrate any solution data, target coordinates, and neighbor lists, from the previous state to the reordered state (with the ability to have a reordered state that has more or less target sites than existed before reordering).
  • Could be a 2D array so that the first column could be 0 or 1 (whether reordering changes the value), and the second column is the designated new index after reordering. This would permit creating a 2D array of zeros and then only modifying entries desired.
  • Batch removal of target sites could be written as a helper that calls the above function and creates this 2D array for removing target sites.

@kuberry
Copy link
Collaborator Author

kuberry commented Jun 23, 2020

NeighborLists class is now a compressed row format.

  • While alpha calculation is in GMLS class, it may make sense to extract the solution and any relevant information needed to do a reconstruction into a GMLS solution class.
  • Then, if a single additional site needs a reconstruction, the solution can be stored separately.
  • GMLS solution merges could work like a std::vector, allocating extra space (if desired) so that appending one extra solution could fit without reallocation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
idea Idea for future research/implementation TOOLKIT
Projects
None yet
Development

No branches or pull requests

1 participant