Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save only selected edges in graph learner #968

Open
MislavSag opened this issue Sep 26, 2023 · 4 comments
Open

Save only selected edges in graph learner #968

MislavSag opened this issue Sep 26, 2023 · 4 comments
Assignees

Comments

@MislavSag
Copy link

When we banchmark graph learnes, we can choose to save models or backends or not to save:

  store_models = FALSE,
  store_backends = TRUE,

Is it possible to save only some step in the graph but discard others?
For example, if I want to save only features selected in the filter phase, I don't want to save all other steps.

It comes to my mind, I can add saveRRD function somewhere in the pipeline, but maybe you can request some other way?

@sebffischer
Copy link
Member

sebffischer commented Oct 11, 2023

I don't think that this is currently possible.
One way to achieve this would be to allow running callbacks in the workhorse function (that runs train and predict).
There you could then arbitrarily discard parts of the model.
What do you think @mllg?

@MislavSag
Copy link
Author

I have add readRDS in my custom pipeline, but I was pretty sure this was not the right way. Also in that way, it was hard to add some metadata (cv, fold, taks etc).

Can you send a link where I can read more on callbacks?

@sebffischer
Copy link
Member

sebffischer commented Oct 11, 2023

So currently it is not yet possible to solve your issue with callbacks and I am waiting for feedback whether we want to enable this here.

We already have the mechanism in place in other areas though, you can read about it here: https://mlr3misc.mlr-org.com/reference/Callback.html

@mb706 mb706 transferred this issue from mlr-org/mlr3 Nov 9, 2023
@mb706 mb706 transferred this issue from mlr-org/mlr3pipelines Nov 9, 2023
@mb706
Copy link
Collaborator

mb706 commented Nov 9, 2023

Sorry for transferring twice. I thought this might be an mlr3pipelines issue, but upon thinking about this, what you really want is something like a store_models = function() option that selects the things you want to keep.

@be-marc be-marc self-assigned this Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants