Skip to content
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

Some question about the result of deephit_competing_risks #166

Open
ymhyumenghan opened this issue May 30, 2023 · 2 comments
Open

Some question about the result of deephit_competing_risks #166

ymhyumenghan opened this issue May 30, 2023 · 2 comments

Comments

@ymhyumenghan
Copy link

First of all,thank you very much for your work.
I would like to know that the result ev1 and ev2 of the synthesized data in "deephit_competing_risk.ipynb" is 0.3 different from that of the original author(Deephit: A deep learning approach to survival analysis with competing risks. In Thirty-Second AAAI Conference on Artificial Intelligence, 2018). May I ask why this is?
Thank you for your answer.

@ymhyumenghan
Copy link
Author

'm sorry if I didn't describe my question well, but my question is not about the content of the data set. What I mean is that using composite data, your deephit_competing_risks presents a c_index result that is 0.3 points worse than the one the author wrote in the paper. Not sure how to solve this problem?

@Raymvp
Copy link

Raymvp commented Apr 26, 2024

'm sorry if I didn't describe my question well, but my question is not about the content of the data set. What I mean is that using composite data, your deephit_competing_risks presents a c_index result that is 0.3 points worse than the one the author wrote in the paper. Not sure how to solve this problem?

Please note that in the example ipynb, "The survival function obtained with predict_surv_df is the probability of surviving any of the events, and does, therefore, not distinguish between the event types.
This means that we evaluate this "single-event case" as before."

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

No branches or pull requests

2 participants