doFuture (Q54217): Difference between revisions
From MaRDI portal
Created claim: source code repository (P339): https://github.com/cran/doFuture, #quickstatements; #temporary_batch_1711029738451 |
Swh import (talk | contribs) SWHID from Software Heritage |
||||||||||||||
| Property / Software Heritage ID | |||||||||||||||
| Property / Software Heritage ID: swh:1:snp:19780266f3949c29a24054ab15e4d1141f0065a7 / rank | |||||||||||||||
Normal rank | |||||||||||||||
| Property / Software Heritage ID: swh:1:snp:19780266f3949c29a24054ab15e4d1141f0065a7 / qualifier | |||||||||||||||
| Property / Software Heritage ID: swh:1:snp:19780266f3949c29a24054ab15e4d1141f0065a7 / qualifier | |||||||||||||||
point in time: 5 January 2024
| |||||||||||||||
Latest revision as of 03:56, 22 March 2024
Use Foreach to Parallelize via the Future Framework
| Language | Label | Description | Also known as |
|---|---|---|---|
| English | doFuture |
Use Foreach to Parallelize via the Future Framework |
Statements
20 December 2023
0 references
The 'future' package provides a unifying parallelization framework for R that supports many parallel and distributed backends. The 'foreach' package provides a powerful API for iterating over an R expression in parallel. The 'doFuture' package brings the best of the two together. There are two alternative ways to use this package. The recommended approach is to use 'y <- foreach(...) %dofuture% { ... }', which does not require using 'registerDoFuture()' and has many advantages over '%dopar%'. The alternative is the traditional 'foreach' approach by registering the 'foreach' adapter 'registerDoFuture()' and so that 'y <- foreach(...) %dopar% { ... }' runs in parallelizes with the 'future' framework.
0 references
expanded from: LGPL (≥ 2.1) (English)
0 references
