Caliper modifier #11
Caliper modifier #11
Conversation
| papi: | ||
| externals: | ||
| - spec: [email protected] | ||
| prefix: /opt/cray/pe/papi/7.0.0.2 |
There was a problem hiding this comment.
@becker33 @scheibelp Should we be looking for a system install of PAPI, or is it advisable to build PAPI for each system?
| buildable: false | ||
| elfutils: | ||
| externals: | ||
| - spec: [email protected] |
There was a problem hiding this comment.
@becker33 @scheibelp Same question for elf
| modifiers: | ||
| - name: caliper | ||
| mode: spot | ||
| success_criteria: |
There was a problem hiding this comment.
@rfhaque Do we have to have a success criteria, even if we use the output of this modifier only in post-processing?
There was a problem hiding this comment.
@rfhaque Do we have to have a success criteria, even if we use the output of this modifier only in post-processing?
@pearce8 We still need some way to assess the success/failure of the experiment using "ramble workspace analyze". We use the modifier output in post-processing to extract the FOM and use that in the success criteria.
github-actions
bot
added
experiment
|
@pearce8 Closing this PR as the top-down and cuda modifier implementations have been split into their own branches |
[[DO NOT MERGE]] This commit provides a draft implementation of the caliper modifier for benchpark