rapidsurveys/oldr

An Implementation of the Rapid Assessment Method for Older People (RAM-OP)

oldr's Issues

workflow graphics needs higher resolution

add option to view or not view report output

issue with unit testing when tests for report_op_pdf added

Seems there is a problem creating PDF on all machines - probably a LaTex issue

Possible solution is to instal TinyTex using tinytex

change save.chart to save_chart

to unify syntax and grammar

Chart functions unusable in report generation

add CITATION

Reporting function to produce PDF or HTML of RAM-OP results

draw inspiration from functions that have this reporting approach.

add a mini-Shiny app into the package?

add a Shiny app that accepts input of a standard RAM-OP dataset and then outputs a report

rub issues with Windows

r-hub/rhub#374

appveyor unit testing fails with the new reporting function

pandoc version 1.12.3 or higher is required and was not found.

update project development structure

HHS chart is wrong

HHS chart only shows no hunger.

Create tests for new functions and untested functions

Name of chart functions not consistent with rest of functions

The predominant naming convention in oldr is verb_descrptor. Whilst the chart functions use the same sequence, the format is different using camel case rather than underscore.

convert master to main

create_op_all outputs data.frame instead of tibble when gender is specified

remove travis and appveyor; add GHA

new can comments

A CRAN package check should not take longer than 10 minutes. Please
considerably reduce the check time of your package to stay below the
threshold of 10 minutes. This can for example be achieved by:

• Omitting the less important and lengthy tests by only running them
  conditionally if some environment variable is set that you only define
  on your machine.

• Using precomputed results for the computational intensive parts in
  vignettes.

Ensure that even after this change the package still includes
illustrative examples of the use of the user-facing functions. Please
aim at trying to test and also illustrate the use of as much
functionality of the package as possible while making considerate use
of the computational resources.

Please omit the redundant "An Implementation" and "in R" from the title.

\dontrun{} should only be used if the example really cannot be executed
(e.g. because of missing additional software, missing API keys, ...) by
the user. That's why wrapping examples in \dontrun{} adds the comment
("# Not run:") as a warning for the user.
Does not seem necessary.
Please unwrap the examples if they are executable in < 5 sec, or replace
\dontrun{} with \donttest{}.

Please ensure that your functions do not write by default or in your
examples/vignettes/tests in the user's home filespace (including the
package directory and getwd()).
In your examples/vignettes/tests you can write to tempdir().

report_op_pdf still failing on rhub and on win-builder