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

Small inconsistency in the `lmBenchmark.R` file?

Open
#126 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, r
Domain
documentation

Research direction

Compare the method mapping in lmBenchmark.R with the documented RcppEigen::fastLm method values, starting from the shown exprs["LDLt"] entry and the fastLm documentation. Verify which value represents LDLT and update the inconsistent source or documentation; done when the benchmark and documentation agree.

Written by the indexing model from the issue text.

Description

In the lmBenchmark.R file I read

    ## LDLt Cholesky decomposition with rank detection
    exprs["LDLt"] <- alist(RcppEigen::fastLmPure(mm, y, 2L))

but in the documentation for RcppEigen::fastLm the method is described as

an integer scalar with value [...] 3 for the LDLT Cholesky,

Is this correct?

> sessionInfo()
R version 4.2.0 (2022-04-22)
Platform: aarch64-apple-darwin20 (64-bit)
Running under: macOS 13.3.1

Matrix products: default
LAPACK: /Library/Frameworks/R.framework/Versions/4.2-arm64/Resources/lib/libRlapack.dylib

locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods  
[7] base     

other attached packages:
[1] bench_1.1.3         RcppEigen_0.3.3.9.3 speedglm_0.3-5     
[4] biglm_0.9-2.1       DBI_1.1.3           MASS_7.3-58.1      
[7] Matrix_1.5-3       
Dominant language
C++
Stars
118
Forks
43
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 RcppCore/RcppEigen

All issues in RcppCore/RcppEigen

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.