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

Add PointData class and use it in GMLS class #214

Closed
wants to merge 15 commits into from
Closed

Conversation

kuberry
Copy link
Collaborator

@kuberry kuberry commented Jun 29, 2020

No description provided.

kuberry and others added 8 commits June 24, 2020 06:20
view, same memory space but different layout, and different memory
space.
_target_point_data.getCoordinateDevice().
PointData class.

Added instances of different constructions to UtilityTest.cpp
PointData class.

Added example to UtilityTest.cpp
for PointData class for same template.

Details now mention that with same template, it is a shallow copy,
while when templates are different, it is a deep copy.
@kuberry kuberry self-assigned this Jun 29, 2020
@kuberry
Copy link
Collaborator Author

kuberry commented Jun 29, 2020

This is the beginning of addressing issue #215

kuberry and others added 7 commits June 29, 2020 15:28
or target coordinates.

Data flow management in PointData is now analagous to Tpetra's way
of marking for fill and completion, except ours is now done by
device/host with resumeFillOnHost, resumeFillOnDevice,
fillCompleteOnHost, and fillCompleteOnDevice. This prevents the host
and device from ever getting out of sync.

Switched GMLS_Device test over to using new PointData structures in
the example, with filling of source coordinate data no host and
target coordinate data on device. Not complete yet, as KDtree search
calls in PointCloudSearch still require access to Kokkos view.
Switch PointCloudSearch over to using PointData for trg_pts.

Passes tests on Cuda w/wo UVM.
and target coordinates before setting problem data for GMLS class.

Switched PointCloudSearch over to using PointData rather than a raw
Kokkos view and additionally it is now a const reference object.
is not modified by user between subsequent calls.
@kuberry
Copy link
Collaborator Author

kuberry commented Feb 21, 2022

This PR was to treat point data like the neighbor list accessor class (managing host and device views). Instead, a struct of type PointConnections replaced GMLS class managing source and target coordinates as Kokkos views in #257.

@kuberry kuberry closed this Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant