-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
[RFC] who should drive the dtype of the computations X or y ? #8976
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
Comments
I suggest that X should drive the choice: as X is usually the big
dataset. It should be documented somewhere.
|
X should drive the choice as y needs to be derived from X... I think that
logic is correct
|
For tree based regressors the |
still, for trees, every node stores a comparison with the dtype of X, but just the leaves store outputs, right? I don't think there can be any problems with using X.dtype consistently. |
we could add |
@glemaitre. Thx |
Description
This question arises after the PR #8835 addressing IS #8769.
Roughly if
X.dtype
isnp.float32
andy.dtype
isnp.float64
, (or the other way arround) should we:a) convert both to
np.float32
b) convert both to
np.float64
c) convert them to
X.dtype
d) convert them to
y.dtype
The text was updated successfully, but these errors were encountered: