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

Which models to keep? #15

Closed
seabbs opened this issue May 7, 2024 · 6 comments · Fixed by #28
Closed

Which models to keep? #15

seabbs opened this issue May 7, 2024 · 6 comments · Fixed by #28

Comments

@seabbs
Copy link
Contributor

seabbs commented May 7, 2024

We currently have a range of models that have been ported over from the research code base. @parksw3 we need to decide which of these to keep prior to any work being done on these.

I think my proposal would be keep just the latent truncation and censoring adjusted model and the dynamic backward -> forward models and with the view we will likely have a few more models flavours in the near future (as various improvements on those).

This was referenced May 13, 2024
@athowes
Copy link
Collaborator

athowes commented May 13, 2024

@seabbs @parksw3 @kgostic do you think we have a consensus about which models to keep based on Friday's meeting?

As I understand it, seems like we had mild agreement on deprecating any functions which were close to "pure" brms and writing up a vignette showing how to do that instead (see #9).

Perhaps I could start by making a PR to remove all of these, and in the meantime we can get clarity about which of the others to keep?

@seabbs
Copy link
Contributor Author

seabbs commented May 13, 2024

I thought we had a roadmap which was to strip back to just the latent censoring and truncation model with feature issues to add support for retrospective (so no truncation), and the dynamic method (for edge cases/where only backwards distributions are available).

If we want to keep any other models I think we should make adding them in as features and drop for now (so the current action can be to drop and add a issue review those models for later additions).

@kgostic
Copy link
Collaborator

kgostic commented May 13, 2024

ok, following the updated discussion, I think we're keeping this one:

latent_truncation_censoring_adjusted_delay <- function(

...and planning to drop everything else

@parksw3
Copy link
Collaborator

parksw3 commented May 13, 2024

Sorry, I've been getting emails for all the issues, and I'm just getting to them after work, so I missed that I was tagged in this one... I also agree with Katie that we're only keeping one.

@seabbs
Copy link
Contributor Author

seabbs commented May 13, 2024

(if the emails are annoying you can turn off github emails in the settings and just use github notifications)

@parksw3
Copy link
Collaborator

parksw3 commented May 13, 2024

Thanks, that would be nice... I had to go through ~70 emails just now, which adds a huge mental block for me (more so than the actual task of reviewing issues)...

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 a pull request may close this issue.

4 participants