-
Notifications
You must be signed in to change notification settings - Fork 358
Remove red p_feasible halos from ArmEffectsPlot #4398
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
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4398 +/- ##
=======================================
Coverage ? 96.20%
=======================================
Files ? 553
Lines ? 56717
Branches ? 0
=======================================
Hits ? 54564
Misses ? 2153
Partials ? 0 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
46f3329 to
56ef899
Compare
|
@mpolson64 has exported this pull request. If you are a Meta employee, you can view the originating Diff in D83864978. |
56ef899 to
46595c0
Compare
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Differential Revision: D83864978
46595c0 to
71a7e9b
Compare
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Differential Revision: D83864978
71a7e9b to
46595c0
Compare
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
46595c0 to
3a5b7cb
Compare
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
3a5b7cb to
57cfa69
Compare
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
… logic (facebook#4396) Summary: Was hardcoded with custom logic before, now we just use the attr on these two Analyses directly. This shaves down custom handling and allows us to override easily when necessary. Reviewed By: lena-kashtelyan Differential Revision: D83869841
Summary: As discussed in chat. This is currently not used, adds complexity, and should be broken out into its own "progression" plot in the future Reviewed By: lena-kashtelyan Differential Revision: D83863709
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
57cfa69 to
c79acfc
Compare
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot. Including it in ArmEffects increases visual density past a useful point, and add significant code complexity. Reviewed By: lena-kashtelyan Differential Revision: D83864978
|
This pull request has been merged in b57d277. |
Summary: p_feasible is very important to express to users and should be promoted to its own dedicated plot
Differential Revision: D83864978