You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
In the following example, the
dtwclust
library is explicitly loaded into each worker. I'm not sure how to explicitly load things likerlang
into the workers when using the implementation of thefuture
packages infable
. @mitchelloharawild , I assume I'm just failing to put the required packages someplace appropriate, to ensure that they get called?The text was updated successfully, but these errors were encountered: