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.

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

use of future package integration doesn't load libraries #14

Open
davidtedfordholt opened this issue Feb 3, 2020 · 2 comments
Open
Labels
bug Something isn't working

Comments

@davidtedfordholt
Copy link
Owner

davidtedfordholt commented Feb 3, 2020

In the following example, the dtwclust library is explicitly loaded into each worker. I'm not sure how to explicitly load things like rlang into the workers when using the implementation of the future packages in fable. @mitchelloharawild , I assume I'm just failing to put the required packages someplace appropriate, to ensure that they get called?

require("doParallel")
# Create parallel workers
workers <- makeCluster(2L)
# Preload dtwclust in each worker; not necessary but useful invisible(clusterEvalQ(workers, library("dtwclust")))
# Register the backend; this step MUST be done registerDoParallel(workers)
@mitchelloharawild
Copy link
Collaborator

For now I approach parallel at the batch modelling level (via model()) and avoid any parallelisation within the model estimator itself. Later I hope to also allow parallelisation within the model estimation (further splitting up the compute), however I haven't thought about the best way to do this yet.

I would expect that within-estimation parallelisation should use the same method as model() parallelisation, and that fabletools should provide some helpers for this. But again, I haven't thought about this problem much yet.

@davidtedfordholt
Copy link
Owner Author

No problem. That's definitely on the lower end of importance, even in terms of implementing parallelisation (probably below both refit and stream).

@davidtedfordholt davidtedfordholt added the bug Something isn't working label Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants