easystats / easystats/performance

[Proposal] Support for glmtoolbox glmgee objects (glmgee or gnmgee models) / interim warnings

Open
#901 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Docs :books: Enhancement :boom:
Dominant language
R
Stars
1.2k
Forks
109
Avg merge
6h 34m
Merged PRs (30d)
8

Description

Performance does a fantastic job of bringing model checks under one hood. I'd be very pleased to see support expanded towards glmgee objects from the glmtoolbox package. The benefits of this GEE implementation have been highlighted by @adrianolszewski in discussions over at marginaleffects/issues/1148, and some performance functions already work with it (for example, check_collinearity). However, other aspects are either unsupported, or run but may not actually be doing what the user might expect. For example, check_outliers runs, but it's not clear whether this is taking into account the cluster correlation aspects of the model. There are some useful residuals and influence methods already implemented in glmtoolbox, residuals.glmgee with Mahalanobis and Pearson options, and cooks.distance.glmgee, and it would be great to have specific support within performance. An interim warning in the same manner as #95 could be applied in the meantime, if this functionality is not yet included.

Thanks again for this awesome tool!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing existing glmgee handling in check_collinearity and check_outliers, then inspect glmtoolbox's residuals.glmgee and cooks.distance.glmgee methods. Compare the current behavior with the cluster-correlation requirements described in this issue. Done means either adding reliable glmgee diagnostics or documenting the unsupported cases and adding an interim warning like #95.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.