Repository navigation
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
CI follow-up for d8d642c: the Lint jobs stop on KPSS's duplicate |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #954 +/- ##
=======================================
Coverage 99.01% 99.01%
=======================================
Files 134 135 +1
Lines 29563 29605 +42
Branches 2290 2293 +3
=======================================
+ Hits 29271 29313 +42
Misses 239 239
Partials 53 53
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
d8d642c to
df9ca56
Compare
|
Rebased onto a93ff73 in df9ca56, preserving #957's complex-statistic support and real-only interval checks. Added reusable-complex-output covariance cases as well. All 264 recorded-data callback pairs agree with their allocating/reference results, and the full bootstrap suite passes. The covariance dtype and live-docstring cases that previously failed also pass against the new upstream base; this head still needs its hosted CI run. |
|
The remaining Intel macOS wheel failure is test_valid_results_are_unchanged_by_numpy_scalars: an exact equality differs by about 1e-15. The same test fails on unchanged base a93ff732 and current head df9ca564; both the test and unitroot implementation are unchanged here. The other three wheel-test jobs and both lint jobs pass. Codecov reports 100% patch coverage. Project coverage is currently 98.93% versus 99.01% on the base, with one fewer reported file; other coverage/pipeline jobs are still pending. |
|
This feels a bit like protecting a user against things they shouldn't be doing. The other path would be to simply document this as a requirement for the output of the statistic function. I'm going to call this an ENH since I don't think it is a BUG. |
|
Agreed, ENH fits. This adds support for callbacks that reuse an output buffer. A documented requirement that returned arrays remain unchanged is a reasonable alternative. |
A statistic can reuse an output array, for example with NumPy's
out=argument. Subsequent calls then overwrite the saved original-sample estimate and the stored jackknife estimates. This shifts confidence intervals and non-recentered covariances; BCa can incorrectly raise a zero-jackknife-variance error.Before:
[3.37564149, 6.62435851]versus[2.87564149, 6.12435851]. After, both give the second interval.Copy the original-sample result and each jackknife result when retaining them. Bootstrap replication rows already copy through assignment. The regression cases cover scalar and vector outputs, all six interval methods (including nested studentization), covariance, variance and jackknife estimates.
The refreshed change preserves the complex-statistic support and real-only interval validation added in #957. The covariance regression also covers reusable complex outputs.
Validation on current main a93ff73:
The earlier KPSS docstring and covariance dtype failures are resolved by current upstream. The new head still needs its hosted CI run; other platforms and a full repository run are not claimed locally.