Skip to content

Add a script that launches a benchmark from a yaml file or a set of parameters#573

Merged
R-Palazzo merged 12 commits intofeature/benchmark_launcherfrom
issue-546-benchmark-generator
Mar 18, 2026
Merged

Add a script that launches a benchmark from a yaml file or a set of parameters#573
R-Palazzo merged 12 commits intofeature/benchmark_launcherfrom
issue-546-benchmark-generator

Conversation

@R-Palazzo
Copy link
Copy Markdown
Collaborator

Resolve #546
CU-86b8h63t2

@R-Palazzo R-Palazzo self-assigned this Mar 11, 2026
@R-Palazzo R-Palazzo requested a review from a team as a code owner March 11, 2026 14:18
@sdv-team
Copy link
Copy Markdown
Contributor

@R-Palazzo R-Palazzo removed the request for review from a team March 11, 2026 14:18
@R-Palazzo R-Palazzo force-pushed the issue-546-benchmark-generator branch from fe78012 to 6913f4f Compare March 11, 2026 14:35
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 11, 2026

Codecov Report

❌ Patch coverage is 98.09524% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.75%. Comparing base (6bdfdae) to head (834c457).
⚠️ Report is 1 commits behind head on feature/benchmark_launcher.

Files with missing lines Patch % Lines
sdgym/_benchmark_launcher/script.py 98.00% 2 Missing ⚠️
Additional details and impacted files
@@                      Coverage Diff                       @@
##           feature/benchmark_launcher     #573      +/-   ##
==============================================================
+ Coverage                       83.30%   83.75%   +0.45%     
==============================================================
  Files                              38       39       +1     
  Lines                            3198     3299     +101     
==============================================================
+ Hits                             2664     2763      +99     
- Misses                            534      536       +2     
Flag Coverage Δ
integration 47.86% <0.00%> (-1.52%) ⬇️
unit 79.02% <98.09%> (+0.59%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@R-Palazzo R-Palazzo force-pushed the issue-546-benchmark-generator branch from e74bae6 to e2abd66 Compare March 13, 2026 16:10
@R-Palazzo R-Palazzo requested a review from pvk-developer March 13, 2026 16:21
return parser.parse_args()


def _parse_csv(value):
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is the input an actual csv file? If not this should be named something else. In general I think with a cli you should specify the input as nargs and then call like this

cli_name --datasets dataset1 dataset2 ...

The parser will automatically turn that into a list

Comment on lines +138 to +150
while len(instance_jobs) < num_instances:
split_index = None
split_size = -1
for index, instance_job in enumerate(instance_jobs):
if (_instance_job_size(instance_job) > 1) and (
_instance_job_size(instance_job) > split_size
):
split_index = index
split_size = _instance_job_size(instance_job)

instance_job = instance_jobs.pop(split_index)
instance_jobs.extend(_split_instance_jobs(instance_job))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does the current set of jobs you have defined in the config require splitting?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No it does not require splitting. I clarified it in b73bafc. If datasets, synthesizers, and num_instances are not provided, we default to the configuration defined for the selected modality in the YAML files. I also added some docstrings to provide clearer explanations.

@R-Palazzo R-Palazzo force-pushed the issue-546-benchmark-generator branch 2 times, most recently from c83d758 to 5589530 Compare March 16, 2026 16:40
@R-Palazzo R-Palazzo requested a review from amontanez24 March 17, 2026 09:38
Base automatically changed from issue-532-define-yaml-files to feature/benchmark_launcher March 17, 2026 12:16
@R-Palazzo R-Palazzo force-pushed the issue-546-benchmark-generator branch from 5589530 to b73bafc Compare March 17, 2026 14:10
timeout: 345600
compute_quality_score: true
compute_diagnostic_score: true
compute_privacy_score: false
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed from the base since it's not supported for multi_table yet

@R-Palazzo R-Palazzo merged commit 44cdd33 into feature/benchmark_launcher Mar 18, 2026
51 checks passed
@R-Palazzo R-Palazzo deleted the issue-546-benchmark-generator branch March 18, 2026 10:57
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.

4 participants