Merged
Conversation
MrBurmark
reviewed
Jan 16, 2026
docs/13_rajaperf/rajaperf.rst
Outdated
|
|
||
| * *Comm* group (directory src/comm) | ||
|
|
||
| #. **HALO_EXCHANGE_FUSED** packing and unpacking MPI message buffers for point-to-point distributed memory halo data exchange for mesh-based codes *(overhead of launching many small kernels, GPU variants use RAJA::Workgroup concepts to execute multiple kernels with one launch)* |
Member
There was a problem hiding this comment.
Suggested change
| #. **HALO_EXCHANGE_FUSED** packing and unpacking MPI message buffers for point-to-point distributed memory halo data exchange for mesh-based codes *(overhead of launching many small kernels, GPU variants use RAJA::Workgroup concepts to execute multiple kernels with one launch)* | |
| #. **HALO_PACKING_FUSED** packing and unpacking MPI message buffers for point-to-point distributed memory halo data exchange for mesh-based codes *(overhead of launching many small kernels, GPU variants use RAJA::Workgroup concepts to execute multiple kernels with one launch)* |
Member
Author
There was a problem hiding this comment.
Changed. Thanks for that. I forgot about it.
MrBurmark
reviewed
Jan 16, 2026
docs/13_rajaperf/rajaperf.rst
Outdated
| depends on the problem size run for the kernel; thus, each checksum is | ||
| computed at run time. Validation criteria is defined in terms of the checksum | ||
| difference between each kernel variant and problem size run and a corresponding | ||
| reference variant. Typically, the ``Base_Seq`` variant is used to define the |
Member
There was a problem hiding this comment.
Suggested change
| reference variant. Typically, the ``Base_Seq`` variant is used to define the | |
| reference variant. The ``Base_Seq`` variant is used to define the |
MrBurmark
reviewed
Jan 16, 2026
| Whether the checksum for each kernel is considered to be within its expected | ||
| tolerance is reported as checksum ``PASSED`` or ``FAILED`` in the output files. | ||
|
|
||
| **Show an example of this for the EL Capitan baseline runs!!** |
Member
There was a problem hiding this comment.
Reminder to add more accurate Base_Seq summation tunings (left fold is inaccurate for large problem sizes).
pearce8
approved these changes
Jan 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
We are working to finalize the last bits about generating the baselines and how the FOM quantities are calculated. So there is more to come.
Closes #31