Run EJAM analysis for several radii and numbers of sitepoints, recording how long each step takes

Run EJAM analysis for several radii and numbers of sitepoints, recording how long each step takes

Usage

speedtest(
  n = 10,
  sitepoints = NULL,
  weighting = "frs",
  radii = c(1, 3.106856, 5, 10, 31.06856)[1:3],
  avoidorphans = FALSE,
  test_ejamit = FALSE,
  test_getblocksnearby = TRUE,
  test_doaggregate = TRUE,
  test_batch.summarize = FALSE,
  logging = FALSE,
  logfolder = ".",
  logfilename = "log_n_datetime.txt",
  honk_when_ready = TRUE,
  saveoutput = FALSE,
  plot = TRUE,
  getblocks_diagnostics_shown = FALSE,
  ...
)

Arguments

n

optional, vector of 1 or more counts of how many random points to test, or set to 0 to interactively pick file of points in RStudio (n is ignored if sitepoints provided)

sitepoints

optional, (use if you do not want random points) data.frame of points or path/file with points, where columns are lat and lon in decimal degrees

weighting

optional, if using random points, how to weight them, such as facilities, people, or blockgroups. see testpoints_n()

radii

optional, one or more radius values in miles to use in creating circular buffers when findings residents nearby each of sitepoints. The default list includes one that is 5km (approx 3.1 miles)

avoidorphans

see getblocksnearby() or ejamit() regarding this param

test_ejamit

whether to test only ejamit() instead of its subcomponents like getblocksnearby(), doaggregate(), etc

test_getblocksnearby

whether to include this function in timing - not used because always done

test_doaggregate

whether to include this function in timing

test_batch.summarize

whether to include this function in timing

logging

logical optional, whether to save log file with timings of steps. NOTE this slows it down though.

logfolder

optional, name of folder for log file

logfilename

optional, name of log file to go in folder

honk_when_ready

optional, self-explanatory

saveoutput

but this slows it down if set to TRUE to save each run as .rda file

plot

whether to create plot of results

getblocks_diagnostics_shown

set TRUE to see more details on block counts etc.

...

passed to plotting function

Value

EJAM results similar to as from the web app or ejamit() and also creates a plot

Details

This is essentially a test script that times each step of EJAM for a large dataset

• pick a sample size (n) (or enter sitepoints, or set n=0 to interactively pick file of points in RStudio)

• pick n random points

• pick a few different radii for circular buffering

• analyze indicators in circular buffers and overall (find blocks nearby and then calc indicators)

• get stats that summarize those indicators

• compare times between steps and radii and other approaches or tools

See also

speedtest_plot()

Examples

if (FALSE) { # \dontrun{
  speedseen_few <- EJAM:::speedtest(c(50,500), radii=c(1, 3.106856), logging=FALSE, honk=FALSE)

  speedseen_nearer_to1k <- EJAM:::speedtest(n = c(1e2,1e3,1e4 ), radii=c(1, 3.106856,5 ),
    logging=TRUE, honk=FALSE)
  save( speedseen_nearer_to1k, file = "~/../Downloads/speedseen_nearer_to1k.rda")
  rstudioapi::savePlotAsImage(        "~/../Downloads/speedseen_nearer_to1k.png")

  speedseen_all <- EJAM:::speedtest(
    n = c(1e2,1e3,1e4),
    radii=c(1, 3.106856, 5, 10, 31.06856),
    logging=TRUE, honk=TRUE
  )
 } # }