Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Warn when lag-1 columns are entirely missing

Open Beginner friendly
  • Is something wrong?
#83 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Pascal-Kueng is already working on this.

Since Oct 7, 2026.

  • #88 by @Pascal-Kueng — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
r
Domain
data

Research direction

Start from prepare_dyad_data(), the function named in the issue, and locate where lag-1 columns are generated by matching on exactly time - 1; that is where the new check belongs. Add a warning (wording supplied in the issue) emitted when a generated lag-1 column is NA on every row, plus one test reproducing a non-consecutive time scale (e.g. 0, 6, 12) in the package's test suite. Done when the warning fires for all-missing lag columns, stays silent for healthy data, and the new test passes alongside existing ones.

Written by the indexing model from the issue text.

Description

prepare_dyad_data() matches lags at exactly time - 1. Validation only checks that time is whole-numbered, so time coded in its natural unit silently produces lag columns that are NA on every row:

  • months: 0, 6, 12
  • years with two-year waves: 2008, 2010, 2012

Models with lags then drop all rows, without any hint why.

Proposal: warn when a generated lag-1 column is NA on every row, e.g.

All lag-1 values of health are missing. Lags match observations at exactly time - 1; if time counts months or years with steps larger than 1, recode it as a consecutive occasion index (1, 2, 3, …).

Plus one test. Independent of the singleton work in dev/partner-exists-spec.md.

Dominant language
R
Stars
1
Forks
2
Avg merge
2d 3h
Merged PRs (30d)
23

Getting set up

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.

More from Pascal-Kueng/dyadMLM

All issues in Pascal-Kueng/dyadMLM

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.