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

why _model is reset each time fit is called ? #31

Closed
12rambau opened this issue Jul 1, 2021 · 3 comments
Closed

why _model is reset each time fit is called ? #31

12rambau opened this issue Jul 1, 2021 · 3 comments

Comments

@12rambau
Copy link

12rambau commented Jul 1, 2021

I would create one instance of BFASTMonitor for each GPU (you can use device_id to choose GPU), then run fit() on each window. Alternatively, you can use bigger windows, and use n_chunks, to let BFASTMonitor split the window into smaller chunks. Depends on the size of the datasets that you are using and the available RAM.

I checked the BFASTMonitor object and _model is not set once and for all when BFASTMonitor is instantiated but every time the fit method is called. Meaning that for GPU implementation the setting of the device is reset every time.

I don't see any parameter relative to the _model in the the fit method, wouldn't it be more semantic to move it to the __init__ method ?

Happy to create a PR

@mortvest
Copy link
Collaborator

mortvest commented Jul 1, 2021

That is a actually an interesting question. I didn't write this part of the code, so I need to look into that.

@mortvest
Copy link
Collaborator

mortvest commented Jul 1, 2021

It is actually a problem, nice catch. Fixed it.

@mortvest mortvest closed this as completed Jul 1, 2021
@12rambau
Copy link
Author

12rambau commented Jul 2, 2021

Can you point me to the commit that implemented the change ? It useful to follow up with your devs and to pull this kind of improvement in my branches.

If you have not yet pushed the modification to github, would you mind letting the issue open, for me closing means both "fixed" and "available to developers".

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

2 participants