-
Notifications
You must be signed in to change notification settings - Fork 21
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
Wrapped continuous spatial messaging #185
Comments
Changelog: Adds 3D spatial messaging, with Circles example Adds 2D spatial messaging Adds FGPU1 behaviour, whereby outputting to a message list twice in an iteration causes the message list to be appended. Adds exceptions, thrown when incorrect message type is bound Adds exceptions, thrown if min/max/radius for spatial messages are invalid Thorough unit testing Documentation Note: This does not support wrapped spatial communication (as found in FLAMEGPU1). Closes #30 Opens #185
Changelog: Adds 3D spatial messaging, with Circles example Adds 2D spatial messaging Adds FGPU1 behaviour, whereby outputting to a message list twice in an iteration causes the message list to be appended. Adds exceptions, thrown when incorrect message type is bound Adds exceptions, thrown if min/max/radius for spatial messages are invalid Thorough unit testing Documentation Note: This does not support wrapped spatial communication (as found in FLAMEGPU1). Closes #30 Opens #185
Also add a reserved distance variable for warpped spatial messages. Either a branch or templated specialisation. |
To match array messaging, this would be accessed via For 2D and 3D spatial, providing partially wrapped iterators for cyclindrical / toridal environments may be required (but potentailly be a separate issue / feature, see #593 for reference) |
Some thoughts on continuing this;
We have discounted the idea of a separate messaging type due to the amount of shared code that would be required. |
Following #30, spatial messaging was added, however unlike FGPU1 new spatial doesn't currently support wrapping over environment bounds.
Wasn't added at the time as it doesn't fit well alongside strips optimisation, and best implementation would require a whole new version, rather than a device side flag/branch. This could be written within an hour or so, but seems overkill unless required.
The text was updated successfully, but these errors were encountered: