-
Notifications
You must be signed in to change notification settings - Fork 218
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
Support for Float32 #2212
Comments
Update: I just did a quick scan across the ecosystem in the TuringLang org and I see a couple of issues/PRs attacking this (TuringLang/Bijectors.jl#266) so maybe I am just looking in the wrong place? |
I don't think there is a unifying issue unfortunately, but we can make this the one:) It is definitively possible to achieve. For example, it's already possible to evaluate a model using, say, There are a few aspects to this:
|
I see in various places issues using
Float32
(i.e. https://discourse.julialang.org/t/issue-with-float32-precision-in-turing-model-sampling/108160) with the problem being that areas of the code hard codeFloat64
.I've looked but can't see an issue for this. Is there one? If not what work would need to be done to make this possible and could it be itemised to make it easier to chunk out into small parts?
In principle this seems like something that could be tackled by newer contributors and so making that easy seems like it would be worth the effort? That being said I have no idea and it could be far more complicated.
The text was updated successfully, but these errors were encountered: