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

Support the ability for extra benchmark params to be detected based on sample result #524

Open
atheurer opened this issue Jul 19, 2024 · 0 comments
Assignees
Labels

Comments

@atheurer
Copy link
Contributor

There are some benchmarks which have a very large number of possible params, of which the defaults may not be known (or they might change) or these params are defined by the benchmark based on other input. These params are not always provided by the user when doing a run, but these params need to be known for comparison of results later.

After post-processing of a sample is complete, rickshaw should check for an optional param-script for the benchmark, and if defined, run it with the same params as done with the benchmark post-process script. A json of params should be generated, and these should be added by rickshaw-run to the run object (and what becomes rickshaw-run.json).

@k-rister k-rister removed the status in Crucible Tracking Jul 19, 2024
@k-rister k-rister moved this to Queued in Crucible Tracking Jul 19, 2024
@atheurer atheurer self-assigned this Aug 1, 2024
@k-rister k-rister moved this from Queued to Todo in Crucible Tracking Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Development

No branches or pull requests

1 participant