Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use future+cli package for computation instead of pbapply #11

Closed
astamm opened this issue Sep 1, 2021 · 2 comments · Fixed by #17
Closed

Use future+cli package for computation instead of pbapply #11

astamm opened this issue Sep 1, 2021 · 2 comments · Fixed by #17

Comments

@astamm
Copy link
Collaborator

astamm commented Sep 1, 2021

No description provided.

@ManonSimonot
Copy link
Collaborator

For parallelisation, the packages pbapply, parallel and optimParallel are all used in the package.
Do we keep some of them, do we only use future?

@ManonSimonot ManonSimonot changed the title Use parallel+cli package for computation instead of pbapply Use future+cli package for computation instead of pbapply Dec 13, 2024
@astamm
Copy link
Collaborator Author

astamm commented Dec 13, 2024

We get rid of {pbapply} and {parallel} for sure in favour of {furrr}.
For {optimParallel}, this is a bit different as it implements parallel versions of optimisation algorithms.

@ManonSimonot ManonSimonot linked a pull request Dec 20, 2024 that will close this issue
Using furrr instead of pbapply and letting the user set the parallelization. #17
Merged
@astamm astamm closed this as completed in #17 Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Using furrr instead of pbapply and letting the user set the parallelization. permaverse/flipr
2 participants
@astamm @ManonSimonot