Skip to content

censored data (survival) #126

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

Closed
OriolAbril opened this issue Apr 5, 2021 · 3 comments
Closed

censored data (survival) #126

OriolAbril opened this issue Apr 5, 2021 · 3 comments
Assignees
Labels
tracker id Issues used as trackers in the notebook update project, do not close!

Comments

@OriolAbril
Copy link
Member

File: https://github.com/pymc-devs/pymc-examples/blob/main/examples/survival_analysis/censored_data.ipynb
Reviewers:

The sections below may still be pending. If so, the issue is still available, it simply doesn't
have specific guidance yet. Please refer to this overview of updates

Known changes needed

Changes listed in this section should all be done at some point in order to get this
notebook to a "Best Practices" state. However, these are probably not enough!
Make sure to thoroughly review the notebook and search for other updates.

General updates

ArviZ related

Changes for discussion

Changes listed in this section are up for discussion, these are ideas on how to improve
the notebook but may not have a clear implementation, or fix some know issue only partially.

General updates

ArviZ related

Notes

Exotic dependencies

Computing requirements

@OriolAbril OriolAbril added the tracker id Issues used as trackers in the notebook update project, do not close! label Apr 5, 2021
@drbenvincent
Copy link
Contributor

I'm happy if you want to assign this one to me

@OriolAbril
Copy link
Member Author

Done, thanks!

@drbenvincent
Copy link
Contributor

TODO: Add a link to the "Bayesian regression with truncated or censored data" notebook (#162). At the moment it is not clear what the URL will be. @OriolAbril suggests...

"We should probably find a way to use custom anchors for links instead of relying on the url. Therefore, if we reorgnize the examples or we update the base url (i.e. adding a /stable/ /3.11.2/ verision indicator)... we only need to regenerate the documentation instead of hunting down all urls"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tracker id Issues used as trackers in the notebook update project, do not close!
Projects
Development

No branches or pull requests

2 participants