You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing an issue with xt::where that I do not understand, and that seems like a bug in xtensor 0.23.10. I would assume that the following block of code give the same result for vFiltered1 and vFiltered2. That is, that xt::where() and xt::filtration() produce the same result. In godbolt with xtensor 0.19.4 this works, but locally with xtensor 0.23.10 I get all zeros for xt::where().
Currently I can't upgrade due to xtensor-stack/xsimd#625. But if I have the choice between the two issues, I'd rather have you look at the one with xsimd :-)
I am experiencing an issue with
xt::where
that I do not understand, and that seems like a bug in xtensor 0.23.10. I would assume that the following block of code give the same result forvFiltered1
andvFiltered2
. That is, thatxt::where()
andxt::filtration()
produce the same result. In godbolt with xtensor 0.19.4 this works, but locally with xtensor 0.23.10 I get all zeros forxt::where()
.The text was updated successfully, but these errors were encountered: