Skip to content

Conversation

@ryan-odea
Copy link
Member

Despite the mostly misnamed branch, this PR offloads models out of memory once they are built.
Additionally, in my testing, I found a bug with pre-expansion bootstrapped models - this has been fixed.

I've noticed that the tests have been failing due to runner failure. I'm unsure if this is repeatedly on GH's end (since this started as they've changed runners), or if we should change/skip the test.

@ryan-odea ryan-odea requested a review from remlapmot December 26, 2025 21:09
@ryan-odea ryan-odea self-assigned this Dec 26, 2025
Copy link
Contributor

@remlapmot remlapmot left a comment

Choose a reason for hiding this comment

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

Very nice Ryan

I have run the tests locally under Python 3.10, 3.11, 3.12, 3.13, and 3.14 and all pass.

@remlapmot
Copy link
Contributor

I think let's leave the GitHub Actions tests workflow for now - hopefully GitHub will fix whatever is going on with their runners once folk return after the break.

When:

* treatment_level=[0, 1] (binary control vs treatment)
* method="censoring"
* weighted=True
@remlapmot
Copy link
Contributor

In converting our short course practical from R to Python I found a tiny bug related to needing to use smf.logit() when the treatment is 0,1.

I have implemented this in the commit I've added to this branch (I have checked all tests pass locally under Python 3.10 and 3.14) - if you prefer I could remove it and send as a separate PR after you've merged this one (but given it's just you and me atm, hopefully ok to do this).

@remlapmot
Copy link
Contributor

Maybe I should move my commits to another branch - I'm having all sorts of trouble with converting our practical - I think the problem is with the categorical variables.

@remlapmot
Copy link
Contributor

Also in the bootstrapping I am getting alot of problems with perfect separation, which somehow we didn't seem to encounter in R.

@remlapmot
Copy link
Contributor

remlapmot commented Jan 1, 2026

(Even with these commits our example still fails -- will continue tomorrow or at w/e or next week)

@ryan-odea
Copy link
Member Author

At least in it's current iteration, seems to be only 3.14 which consistently fails.
Let's merge this branch and work on the other errors you've pointed out in a new one.
Being:

  1. Hazard ratio creation
  2. bootstrap separation
  3. NaN predictions

@ryan-odea ryan-odea merged commit b335c56 into main Jan 2, 2026
4 of 5 checks passed
@ryan-odea ryan-odea deleted the compevent-fix branch January 2, 2026 14:29
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.

3 participants