future::values given its
deprecation.glmnet to package Suggests
since used in the vignette.future.apply by including
future.seed = TRUE, as per
https://github.com/tlverse/origami/issues/48.folds_rolling_origin_pooled and
folds_rolling_window_pooled, as per
https://github.com/tlverse/origami/pull/50.lapply.folds_rolling_origin_pooled,
folds_rolling_window_pooled,
folds_vfold_rolling_origin_pooled,
folds_vfold_rolling_window_pooled) now allow for
variability in the number of observations for each independent unit
(i.e., the subject).folds_rolling_origin_pooled,
folds_rolling_window_pooled,
folds_vfold_rolling_origin_pooled,
folds_vfold_rolling_window_pooled.tests/testthat/test-overall.R to use appropriate
hard-coded values that depend on the R version. Note that these differ
between R < 3.6.0 and R > 3.6.0 due to an important change in the
default PRNG.folds2foldvec for easy conversion
between the folds structure used by origami and other
packages (e.g., glmnet).lapply instead of
future_lapply, for compatibility with other packages in a
custom parallelization framework.future_lapply from the new more modular package
future.apply rather than from future, matching
the author’s recommendation.origami_SuperLearner functionality
temporarily.
Need a high-speed mirror for your open-source project?
Contact our mirror admin team at info@clientvps.com.
This archive is provided as a free public service to the community.
Proudly supported by infrastructure from VPSPulse , RxServers , BuyNumber , UnitVPS , OffshoreName and secure payment technology by ArionPay.