future.apply (Q45068): Difference between revisions
From MaRDI portal
Removed claim: depends on software (P342): Item:Q13519 |
Changed an Item |
||
Property / depends on software | |||
Property / depends on software: R / rank | |||
Normal rank | |||
Property / depends on software: R / qualifier | |||
software version identifier: ≥ 3.2.0 |
Revision as of 12:51, 4 March 2024
Apply Function to Elements in Parallel using Futures
Language | Label | Description | Also known as |
---|---|---|---|
English | future.apply |
Apply Function to Elements in Parallel using Futures |
Statements
21 December 2023
0 references
Implementations of apply(), by(), eapply(), lapply(), Map(), .mapply(), mapply(), replicate(), sapply(), tapply(), and vapply() that can be resolved using any future-supported backend, e.g. parallel on the local machine or distributed on a compute cluster. These future_*apply() functions come with the same pros and cons as the corresponding base-R *apply() functions but with the additional feature of being able to be processed via the future framework.
0 references
expanded from: GPL (≥ 2) (English)
0 references