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

Fix spikemonitor #280

Merged
merged 2 commits into from
Apr 3, 2022
Merged

Fix spikemonitor #280

merged 2 commits into from
Apr 3, 2022

Conversation

denisalevi
Copy link
Member

No description provided.

I used thrust vectors, which can be resized based on numbers of events
before calling the monitor kernel. This makes vector sizes available to
the host and doesn't require using our likely much slower CudaVector
implementation and stores the monitor data directly in the format used
in finalization.

Recording from subgroups is broken now, needs fixing the thrust function
calls
@denisalevi denisalevi merged commit 0b52bb1 into paper2022-revision Apr 3, 2022
@denisalevi denisalevi deleted the fix-spikemonitor branch April 3, 2022 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant