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

New packages: ucminfcpp & optimizr

Open
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Open the Optimization task view and locate the existing ucminf entry. Review where ucminfcpp should be referenced alongside it, and check the request concerning optimizr. Done means the task view accurately reflects the package references, subject to the maintainers' decision about optimizr.

Written by the indexing model from the issue text.

Description

Package 'ucminfcpp' provides an Rcpp integration for 'ucminf' that is part of this task view since long. I suggest to add a reference to this package in the same entry as 'ucminf', thus not opening another entry.
I have tested 'ucminfcpp' with the 'Historize' procedure, it returns absolutely identical intermediate and end results as 'ucminf' and is faster, as expected.

  • Package ucminf implements an algorithm of quasi-Newton type for nonlinear
    unconstrained optimization, combining a trust region with line search approaches.
    The interface of ucminf() is designed for easy interchange with optim().
    Package 'ucminfcpp' reimplements the UCMINF algorithm as C++ code using Rcpp. [QN]

Package 'optimizr' provides a reimplementation of the 'SANN' option of R Base' 'optim' function. 'SANN' is kind of deprecated anyway. I am not in favor of adding 'optimizr' to the task view, but probably there is no choice.

Dominant language
No language data
Stars
6
Forks
6
Avg merge
7d 7h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 cran-task-views/Optimization

All issues in cran-task-views/Optimization

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.