-
-
Notifications
You must be signed in to change notification settings - Fork 557
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
robust=True estimation doesn't work on Ubuntu? #1253
Comments
Hi @konradsemsch - hm, I don't know what's going on here. I'm guess the difference between the Ubuntu and Mac is if numexpr is installed (lots of libs, like pandas, have an optional dependency on numexpr, and will use it if available in the OS). Can you try pip intstalling numexpr in the Docker image and rerunning? That would give me some hint as to what might be going on. |
Hi @CamDavidsonPilon! Ok, so I can come back with some further info. Adding
Please note, that all comparisons were done on exactly the same trained model object, just the OS was different. |
Are you able to share the two |
Hi @CamDavidsonPilon! Yes, let me report back on this: So from the logs I can confirm that So from here you can already see that And here's part of the summary which is executed on the container by sphinx, on the very same model object. Please notice that I would also expect to see the same Any clue what could be causing this? Would there be any way to enforce a consistent behaviour? |
Hi!
I've been using the
LogLogisticAFTFitter
withrobust=True
estimation on my Mac and I could see during during the procedure the following message coming from the logger that is attributes to this settings (at least I presume so, as I haven't seen it before without it):also, the result of
print_summary()
clearly indicates that the SE show now different values as expected.However, after packaging this code into a Docker image (Ubuntu), and running the container, I couldn't see the same logger output, and the SE were as if robust estimation did not take place.
Question: could it be that this setting silently fails on a different OS? Could you provide a bit more insights into this?
The text was updated successfully, but these errors were encountered: