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

Tracking unexported brms functions #420

Open
athowes opened this issue Nov 5, 2024 · 4 comments
Open

Tracking unexported brms functions #420

athowes opened this issue Nov 5, 2024 · 4 comments
Labels
medium Nice to have for next release

Comments

@athowes
Copy link
Collaborator

athowes commented Nov 5, 2024

We use four brms functions:

  • brms:::dpar_bounds
  • brms:::validate_data
  • brms:::validate_family
  • brms:::validate_formula

See:

N  checking dependencies in R code (2.2s)
   Unexported objects imported by ':::' calls:
     ‘brms:::dpar_bounds’ ‘brms:::validate_data’ ‘brms:::validate_family’
     ‘brms:::validate_formula’
     See the note in ?`:::` about the use of this operator.

This issue is a place to track progress on removing dependence on these functions, or them being exposed within brms. Adam to link issue raised in brms repository about this.

@athowes
Copy link
Collaborator Author

athowes commented Nov 13, 2024

Adam to link issue in brms.

@athowes athowes added the medium Nice to have for next release label Nov 13, 2024
@athowes
Copy link
Collaborator Author

athowes commented Nov 14, 2024

paul-buerkner/brms#1676

@seabbs
Copy link
Contributor

seabbs commented Nov 28, 2024

brms:::log_lik_weight and all internal family log_like and posterior predict functions

@athowes
Copy link
Collaborator Author

athowes commented Feb 12, 2025

Note that this issue blocks CRAN submission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
medium Nice to have for next release
Projects
None yet
Development

No branches or pull requests

2 participants