check_models ncv explanation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- r
- Domain
- documentation
Research direction
Start by locating the check_models output or documentation that describes ncv as an alias for linearity. Clarify how ncv differs from linearity and whether it combines linearity with homogeneity; done means the explanation accurately describes ncv without calling it an alias for linearity.
Written by the indexing model from the issue text.
Description
ncv is not an "alias" for linearity, since it does something different. I think it's an alias for linearity plus homogeneity maybe? Could this be clarified?
- Dominant language
- R
- Stars
- 1.2k
- Forks
- 108
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 33
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from easystats/performance
-
Consistency :green_apple: :apple:
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
easystats/performance#986 ·
Maintainers usually reply within 1 day
-
`check_outliers()`: Cook's distances land on the wrong rows when the model skips or reorders rowsOpen3 investigators :grey_question::question: Bug :bug:
Difficulty 4/5 3-5 days Newbie friendliness 22/100
easystats/performance#981 ·
Maintainers usually reply within 1 day
-
Docs :books: Enhancement :boom:
Difficulty 5/5 Over a week Newbie friendliness 45/100
easystats/performance#901 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Enhancement :boom:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
easystats/performance#891 ·
Maintainers usually reply within 1 day
-
3 investigators :grey_question::question: Enhancement :boom:
Difficulty 4/5 3-5 days Newbie friendliness 45/100
easystats/performance#849 · 9 comments ·
Maintainers usually reply within 1 day
All issues in easystats/performance
Similar issues
-
gdsa opencode: keep-alive cleanup trap fails with 'keepalive_pid: unbound variable'Possibly taken @darribas claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
sportsdataverse/sportyR#76 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
joshwlivingston/shinyfilters#155 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 71/100