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

Note on use of tpcp.Algorithm classes #13

Open
AKuederle opened this issue Oct 25, 2024 · 1 comment
Open

Note on use of tpcp.Algorithm classes #13

AKuederle opened this issue Oct 25, 2024 · 1 comment

Comments

@AKuederle
Copy link
Member

I saw that at least in one of the algorithms implemented here (

self.selected_coords = ["x", "y", "z"] # Default coordinates
), have a bunch of loading in the __init__. This is discuraged in the context of tpcp/sklearn and similar frameworks, as the idea is that parameters can be modified even after the init (using set_params) and the assumption is that creating an instance is "cheap" and it is hence done under the hood often (e.g. via .clone).

All logic should be put where it is first needed (aka in detect or train method)

@AKuederle
Copy link
Member Author

Here as well:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant