Check development glmmTMB and brms compatibility - #38
Closed
Pascal-Kueng wants to merge 5 commits into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Development releases of glmmTMB or brms can change model objects before the next stable release. This adds separate weekly and manual checks against both development backends, plus a small real fitted-model check of
recover_exchangeable_covariance().The brms fit uses one chain with 100 warmup iterations and 20 retained draws. These draws exercise covariance extraction and transformation; they are not intended for inference or parameter recovery. Each backend also runs the package checks. Development checks are not required merge checks. The workflow installs the headers needed to compile the brms model, and the pkgdown workflow declares its missing
svgliterendering dependency.This preserves the exact implementation from #35, including its previously passing checks. No new implementation changes have been made. No AI canary or AI contribution policy is included.
This draft targets
revert-dependency-canariestemporarily so the full three-file implementation diff remains reviewable while #37 awaits human review. After the maintainer authorizes and merges #37, this PR can be retargeted tomainfor a separate review and merge decision.This is a draft for human review. It must not be merged without the maintainer's explicit instruction.