DavisVaughan/furrr

Issues

• `future_map` not obviously faster than `map` in simple linear regression setting

  #267 opened 6 months ago by wbvguo
  1

• Understanding memory usage and performance of `furrr::future_apply`

  #260 opened a year ago by alessandro-peron-sdg
  5

• How to pass to .f, character vectors in .x that reference global values?

  #266 opened 7 months ago by delt87
  0

• Identical RNG state for each task, despite setting different seeds in different tasks

  #265 opened 10 months ago by wlandau
  10

• Error when plotting a {sf} object

  #264 opened a year ago by dicorynia
  0

• Progress bar showing 100% even if not completed

  #263 opened a year ago by bakaburg1
  0

• Use of variables in glue() inside furrr loops

  #262 opened a year ago by MS-equinom
  1

• Implement map_vec

  #261 opened a year ago by latot
  0

• terra::rast() doesn't return a variable with workers > 1

  #259 opened a year ago by twest820
  3

• error: external pointer is not valid is not a particularly user actionable message

  #258 opened a year ago by twest820
  5

• when large matrix or df split into list, does furrr workers only access list element?

  #257 opened a year ago by alperyilmaz
  1

• Getting the same random result across `purrr::map()` and `furrr::future_map()`

  #251 opened a year ago by DanChaltiel
  3

• mgcv::gam(~s(pc = object not found)) when future::plan(multisession, workers > 1)

  #256 opened a year ago by twest820
  1

• Carrier

  #255 opened a year ago by instantkaffee
  2

• Setting `seed = TRUE` / `.progress=TRUE` globally in the R session

  #254 opened a year ago by elgabbas
  1

• Export a wrapper around purrr `map()` to workers rather than `map()` itself

  #253 opened a year ago by DavisVaughan
  0

• `furrr` much slower than `purrr` (on Windows)

  #252 opened a year ago by alex-lauer
  2

• Error indices from purrr() are misleading in furrr()

  #250 opened a year ago by alexpghayes
  0

• future_walk work in parallel in script function, but not in R package function

  #236 opened a year ago by jinyancool
  13

• parse() error with future_map2 but not map2

  #235 opened a year ago by karchern
  9

• Resume after interruption

  #249 opened a year ago by rfsaldanha
  1

• Unbalanced Load distribution on first run

  #247 opened 2 years ago by mfakaehler
  0

• REVDEP: How to disable breaking lifecycle_warning_deprecated warning?

  #213 opened 2 years ago by HenrikBengtsson
  7

• future_map does not work with output from modelr::permute

  #246 opened 2 years ago by rorytboyle
  2

• furrr::future_map could not find function

  #245 opened 2 years ago by 13479776
  3

• Release furrr 0.3.1

  #243 opened 2 years ago by DavisVaughan
  0

• Confused about furrr_options globals

  #240 opened 2 years ago by IanWorthington
  3

• future_map raise an error when .f contains a call to a python function imported via the reticulate package

  #241 opened 2 years ago by abdellah19jan
  1

• Operator '<<-' inside a function invoked by future_map

  #239 opened 2 years ago by abdellah19jan
  1

• future_pmap_dbl resulted exactly the same value for each row of a tibble

  #238 opened 2 years ago by zhengchencai
  2

• Would future::plan() work if embedded in a function?

  #237 opened 2 years ago by EvoLandEco
  2

• `furrr` much slower than `purrr` on nested data

  #234 opened 2 years ago by elgabbas
  2

• How to locate errors and debug when using furrr?

  #233 opened 2 years ago by melonki
  2

• Error on modifying by reference with `data.table::set()` in the context of `future.apply::future_apply()` or `furrr::future_map()`

  #232 opened 2 years ago by ramiromagno
  1

• Release furrr 0.3.0

  #229 opened 2 years ago by DavisVaughan
  1

• Error with custom methods in UNIX/HPC environment

  #231 opened 2 years ago by stephenashton-dhsc
  4

• Upkeep for furrr

  #228 opened 2 years ago by DavisVaughan
  1

• Return `NULL` from each function call when using `future_walk()`

  #205 opened 2 years ago by albert-ying
  18

• Remove `future_options()`

  #225 opened 2 years ago by DavisVaughan
  0

• UPCOMING: future(... stdout = structure(TRUE, drop = TRUE))

  #216 opened 2 years ago by HenrikBengtsson
  2

• furrr problem - managing tryCatch inside function of interest

  #212 opened 2 years ago by psalguerog
  4

• Globals bug using future_map

  #211 opened 3 years ago by abdellah19jan
  1

• Parallel map_depth

  #210 opened 3 years ago by frederikvand
  1

• future_map with .f = ~ eval(parse(text = .))

  #209 opened 3 years ago by abdellah19jan
  3

• invoke_map nested in future_map

  #207 opened 3 years ago by abdellah19jan
  1

• Suggestion: improving progress reporting, particularly in nested futures?

  #208 opened 3 years ago by angel-bee2018
  1

• How to use ellipsis (...) with future_map?

  #206 opened 3 years ago by kbzsl
  3

• work with a list of data frames

  #204 opened 3 years ago by EvoLandEco
  4

• Add easy function for grouped df processing

  #203 opened 3 years ago by orgadish
  2

• Appreciation for furrr

  #202 opened 3 years ago by JZL
  1