_            _    _        _         _
      /\ \         /\ \ /\ \     /\_\      / /\
      \_\ \       /  \ \\ \ \   / / /     / /  \
      /\__ \     / /\ \ \\ \ \_/ / /     / / /\ \__
     / /_ \ \   / / /\ \ \\ \___/ /     / / /\ \___\
    / / /\ \ \ / / /  \ \_\\ \ \_/      \ \ \ \/___/
   / / /  \/_// / /   / / / \ \ \        \ \ \
  / / /      / / /   / / /   \ \ \   _    \ \ \
 / / /      / / /___/ / /     \ \ \ /_/\__/ / /
/_/ /      / / /____\/ /       \ \_\\ \/___/ /
\_\/       \/_________/         \/_/ \_____\/
r-workflows 1.1.4
Propagated dependencies: r-cli@3.6.3 r-generics@0.1.3 r-glue@1.8.0 r-hardhat@1.4.0 r-lifecycle@1.0.4 r-modelenv@0.2.0 r-parsnip@1.2.1 r-rlang@1.1.4 r-tidyselect@1.2.1 r-vctrs@0.6.5
Channel: guix
Location: gnu/packages/cran.scm (gnu packages cran)
Home page: https://github.com/tidymodels/workflows
Licenses: Expat
Synopsis: Modeling workflows
Description:

A workflow is an object that can bundle together your pre-processing, modeling, and post-processing requests. For example, if you have a recipe and parsnip model, these can be combined into a workflow. The advantages are:

  1. You don’t have to keep track of separate objects in your workspace.

  2. The recipe prepping and model fitting can be executed using a single call to fit().

  3. If you have custom tuning parameter settings, these can be defined using a simpler interface when combined with tune.

  4. In the future, workflows will be able to add post-processing operations, such as modifying the probability cutoff for two-class models.

Total results: 2