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

Postprocessing meta #238

Closed
3 tasks done
Tracked by #206
athowes opened this issue Aug 9, 2024 · 6 comments
Closed
3 tasks done
Tracked by #206

Postprocessing meta #238

athowes opened this issue Aug 9, 2024 · 6 comments
Labels
meta Summarises issues

Comments

@athowes
Copy link
Collaborator

athowes commented Aug 9, 2024

Tagging @seabbs @kgostic @parksw3 for feedback:

Background

The existing issues we have about postprocessing are as follows:

We have already implemented some postprocessing functionality, including including

By extension of the all_strata_newdata function I can see a path to achieving the postprocessing functionality that we intially agreed for 0.1.0 of the package. However, it'd be better if we don't have to write this functionality outselves. Therefore:

Plan

My plan going forward is to follow Plan A until it seems like there are roadblocks that make it not possible or too difficult for some reason. At that point I'll follow Plan B.

Plan A

Plan B

  • Return to Issue 213: Create functionality for passing in newdata #231 in order to implement the functionality that we need for 0.1.0
  • To be determined: after how much effort on Plan A should I decide it's not possible?
    • I have quite a strong expectation that Plan A is possible
    • Postprocessing in some ways blocks figure creation
@athowes athowes added the meta Summarises issues label Aug 9, 2024
@athowes athowes mentioned this issue Aug 9, 2024
18 tasks
@seabbs
Copy link
Contributor

seabbs commented Aug 9, 2024

Agree with the proposed roadmap

@athowes
Copy link
Collaborator Author

athowes commented Aug 11, 2024

I have done some initial light investigation into tidybayes and it has updated me further towards Plan A being possible and desirable.

@seabbs
Copy link
Contributor

seabbs commented Aug 22, 2024

There is also https://marginaleffects.com/

@seabbs
Copy link
Contributor

seabbs commented Sep 9, 2024

Can we safely delete sensible-newdata-input or does it contain work we need?

@athowes
Copy link
Collaborator Author

athowes commented Sep 9, 2024

Can we safely delete sensible-newdata-input or does it contain work we need?

We can delete it. I will do so.

@athowes
Copy link
Collaborator Author

athowes commented Sep 10, 2024

I think that with the Ebola vignette up we have now demonstrated how to do the postprocessing tasks that we had scope / previously talked about, and this can be closed as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Summarises issues
Projects
None yet
Development

No branches or pull requests

2 participants