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
{{ message }}
This repository was archived by the owner on Jan 24, 2024. It is now read-only.
which complicates passing argument future.seed = TRUE to future.apply::future_sapply(); it can of course be done, but it requires more work.
Suggestion
Note that the future framework supports progress updates with the progressr package - when running in sequential and parallel. This way, you don't use pbapply::pbsapply() in one case and future.apply::future_sapply() in another. You can simply use future_sapply() everywhere. See https://progressr.futureverse.org/#future_lapply---parallel-lapply for how to implement it.
Background
Related to my comment in #140 (comment), I see you use:
CellChat/R/utilities.R
Lines 491 to 495 in 9dae540
which complicates passing argument
future.seed = TRUEtofuture.apply::future_sapply(); it can of course be done, but it requires more work.Suggestion
Note that the future framework supports progress updates with the progressr package - when running in sequential and parallel. This way, you don't use
pbapply::pbsapply()in one case andfuture.apply::future_sapply()in another. You can simply usefuture_sapply()everywhere. See https://progressr.futureverse.org/#future_lapply---parallel-lapply for how to implement it.