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.

Sign up for GitHub

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

Jump to bottom

Store timings for each pipeline step #536

Open
mllg opened this issue Nov 4, 2020 · 2 comments · May be fixed by #541
Open

Store timings for each pipeline step #536

mllg opened this issue Nov 4, 2020 · 2 comments · May be fixed by #541
Labels
predict time state change Status: Needs Discussion We still need to think about what the solution should look like Type: Enhancement workshop

Comments

@mllg
Copy link
Member

mllg commented Nov 4, 2020

@bommert requested that we record the execution time for each step in the GraphLearner. I agree that this would be helpful and suggest introducing a flag to turn this on or off.
@mb706
Copy link
Collaborator

mb706 commented Nov 5, 2020

why would we want to turn it off?

@mllg
Copy link
Member Author

mllg commented Nov 5, 2020

IDK... Ignore the suggested flag.

@sumny sumny linked a pull request Nov 6, 2020 that will close this issue
Draft
@mb706 mb706 added Type: Enhancement Status: Needs Design Needs some thought and design decisions. labels Sep 29, 2021
@mb706 mb706 mentioned this issue Sep 29, 2021
Closed
@mb706 mb706 added Status: Needs Discussion We still need to think about what the solution should look like workshop predict time state change and removed Status: Needs Design Needs some thought and design decisions. labels Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
predict time state change Status: Needs Discussion We still need to think about what the solution should look like Type: Enhancement workshop
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

encapsulate train and predict of PipeOps mlr-org/mlr3pipelines
2 participants
@mllg @mb706