Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Allow non-exportable objects in workspaces #214

@wlandau

Description

@wlandau

Prework

  • Read and agree to the code of conduct and contributing guidelines.
  • If there is already a relevant issue, whether open or closed, comment on the existing thread instead of posting a new issue.
  • For any problems you identify, post a minimal reproducible example so the maintainer can troubleshoot. A reproducible example is:
    • Runnable: post enough R code and data so any onlooker can create the error on their own computer.
    • Minimal: reduce runtime wherever possible and remove complicated details that are irrelevant to the issue at hand.
    • [ ] Readable: format your code according to the tidyverse style guide.

Description

A known weakness of error = "save" is workspaces cannot have torch or keras objects (or any non-exportable object). But #209 and #210 taught me that we can fix that. We just need to use the subpipeline instead of the cache as the structure to hold dependencies. We should probably also make a formal new workspace class to hold the target object and the subpipeline object.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions