-
Notifications
You must be signed in to change notification settings - Fork 321
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
Compute ground-truth optimization trace on BenchmarkProblem #2704
Conversation
This pull request was exported from Phabricator. Differential Revision: D61404056 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2704 +/- ##
=======================================
Coverage 95.39% 95.40%
=======================================
Files 492 492
Lines 47920 47952 +32
=======================================
+ Hits 45715 45747 +32
Misses 2205 2205 ☔ View full report in Codecov by Sentry. |
This pull request was exported from Phabricator. Differential Revision: D61404056 |
93c84f2
to
27332b6
Compare
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Reviewed By: saitcakmak Differential Revision: D61404056
This pull request was exported from Phabricator. Differential Revision: D61404056 |
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Reviewed By: saitcakmak Differential Revision: D61404056
27332b6
to
92b8414
Compare
This pull request was exported from Phabricator. Differential Revision: D61404056 |
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Reviewed By: saitcakmak Differential Revision: D61404056
92b8414
to
5d9beaf
Compare
This pull request was exported from Phabricator. Differential Revision: D61404056 |
5d9beaf
to
8bdecb6
Compare
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Reviewed By: saitcakmak Differential Revision: D61404056
This pull request was exported from Phabricator. Differential Revision: D61404056 |
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Reviewed By: saitcakmak Differential Revision: D61404056
8bdecb6
to
38c6b2a
Compare
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Differential Revision: D61404056 Reviewed By: saitcakmak
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Reviewed By: saitcakmak Differential Revision: D61404056
38c6b2a
to
b4e8655
Compare
This pull request was exported from Phabricator. Differential Revision: D61404056 |
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Differential Revision: D61404056 Reviewed By: saitcakmak
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Differential Revision: D61404056 Reviewed By: saitcakmak
This pull request was exported from Phabricator. Differential Revision: D61404056 |
b4e8655
to
200349f
Compare
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Reviewed By: saitcakmak Differential Revision: D61404056
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Differential Revision: D61404056 Reviewed By: saitcakmak
…#2704) Summary: Pull Request resolved: facebook#2704 This currently doesn't change behavior, but enables more flexibility by redefining `Problem.get_ground_truth_opt_trace` or `BenchmarkRunner.get_Y_true`. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results. Reviewed By: saitcakmak Differential Revision: D61404056
This pull request was exported from Phabricator. Differential Revision: D61404056 |
200349f
to
3d39c1e
Compare
This pull request has been merged in 05fd370. |
Summary: This currently doesn't change behavior, but enables more flexibility by redefining
Problem.get_ground_truth_opt_trace
orBenchmarkRunner.get_Y_true
. This is currently duplicative with the tracking metrics setup, which will be reaped in D61432000; these should be combined. This diff has both ways of computing the optimization trace running, along with an assertion that they give the same results.Reviewed By: saitcakmak
Differential Revision: D61404056