Add MemoryLocation {Host, Device}
member in bunch_particles
to keep track of where particles are
#261
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #248 with a broader solution that introduces a new enum member
MemoryLocation { Host, Device }
in thebunch_particles
class to keep track of where the particles reside. This can also be used to track down issues later on, if for instance particle data lives on the host but some function was called with the assumption that data lives on the device.An additional change that occurs due to the above is that any function that moves particles between device/host memories can no longer be
const
.