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

Fall back to PyTorch default dtype if no explicit type is provided #253

Open
Hespe opened this issue Sep 17, 2024 · 0 comments · May be fixed by #254
Open

Fall back to PyTorch default dtype if no explicit type is provided #253

Hespe opened this issue Sep 17, 2024 · 0 comments · May be fixed by #254
Assignees
Labels
enhancement New feature or request

Comments

@Hespe
Copy link
Member

Hespe commented Sep 17, 2024

Currently, a number of methods use torch.float32 as their default dtype if no explicit choice is provided. While this is often a reasonable choice, some applications require more (or less) precision, which the current default inhibits. Instead, the methods should query torch.get_default_dtype() such that the user can globally configure the desired level of precision.

@Hespe Hespe added the enhancement New feature or request label Sep 17, 2024
@Hespe Hespe self-assigned this Sep 17, 2024
@Hespe Hespe linked a pull request Sep 17, 2024 that will close this issue
14 tasks
@Hespe Hespe linked a pull request Sep 17, 2024 that will close this issue
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant